Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Tue, 22 Nov 2005 @ 21:17:31 GMT


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


Subj:   Re: Excessive Delays between DBQLogTbl's StartTime and FirstStepTime
 
From:   Ballinger, Carrie

Hi Mark,

In response to your question on DBQL:

  Since we are on the subject of DBQL could you shed any light on why the dbc.dbqlogtbl.CollectTimeStamp values are dated several hours prior to the dbc.dbqlogtbl.Startime and other time fields?  


The row in the DBQLogTbl cache is built at the time the cache entry is made. But the header of that default cache is the CollectTimeStamp that reflects the time that cache was initialized. When the cache is flushed, that CollectTimeStamp in the header becomes the value for CollectTimeStamp carried in each row that is written to disk from this cache.

In your case, after the upgrade, the DBQL cache was initialized at system startup, so the collectstamps for all entries in that first cache will be the time the system became active, not the time the user queries were actually executed.

I hope that clears up your confusion, and sorry for the delayed response. -Carrie



     
  <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: 15 Jun 2023