Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Thu, 18 Sep 2003 @ 12:53:08 GMT


     
  <Prev Next>  
<<First
<Prev
Next> Last>>  


Subj:   COGNOS Impromptu Scheduler
 
From:   Tony Howe

I have a customer that recently was switch to access her data on Teradata instead of DB2. She uses the "Scheduler" feature which apparently leaves her logged on all night and must leave "read" locks against tables. When trying to do our nightly "Load" I ran into contention with her "idle" session. She says she has always done this when her data was on DB2 and it never cause a problem. She has been shown a way to utilize the Impromptu scheduler without having to leave herself logged on, but apparently wasn't happy about it! I'm curious why her "idle" session still had a "read" lock on the table? Does anyone known of something that can be changed within Impromptu to release these locks when her query completes.


Thanks,

Anthony S. Howe
Advanced Teradata Certified Professional
Teradata Database Administrator
Highmark, Inc.



     
  <Prev Next>  
<<First
<Prev
Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 27 Dec 2016