Daniel, Perhaps someone else can explain this better but the documentation I've got on this says that the Oracle kernel emits timestamps when a long time has elapsed since the last line was emitted to the trace file. Long time is defined as tens of seconds.
Gudmundur > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Daniel Fink > Sent: 22. j�l� 2003 21:19 > To: Multiple recipients of list ORACLE-L > Subject: Timestamps in trace files > > > I was perusing a 10046 trace file and I noticed that > timestamps are written to the trace file. Sometimes they were > very regular (3 minutes apart give or take 30 seconds) while > other times they were hours apart. I have noticed that two > timestamps are never written without any intervening > activity. Anyone have any idea on the reasoning behind the > timestamps and the 'triggering event'? > > Daniel > -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Gudmundur Bjarni Josepsson INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
