• From: "Herring Dave - dherri" <Dave.Herring@xxxxxxxxxx>
  • To: <ric.van.dyke@xxxxxxxxxx>, "Oracle L" <oracle-l@xxxxxxxxxxxxx>
  • Date: Tue, 29 Dec 2009 09:41:10 -0600

Maybe I'm way off on this, but for session auditing, isn't there just 1 row per 
session?  So for the most part, if the session ends properly, TIMESTAMP and 
LOGOFF_TIME should be the same.  If these dates aren't the same, then the 
session abnormally terminated in some way.

Dave Herring  | DBA, Acxiom Database Services

630-944-4762 office | 630-430-5988 cell | 630-944-4989 fax
1501 Opus Pl | Downers Grove, IL, 60515 | U.S.A. |
Service Desk: 888-243.4566

From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Ric Van Dyke
Sent: Monday, December 28, 2009 1:49 PM
To: Oracle L
Subject: AUD$ TIMESTAMP and LOGOFF_TIME are equal

Database on a 6 way RAC, each node has 16 CPUs.  (That's all the info 
I have on the system, I'm working remote) 

Data collected from AUD$ via the DBA_AUDIT_SESSION view has the TIMESTAMP and 
LOGOFF_TIME equal for the vast majority of the sessions collected.  Which is 
not possible, some of these sessions did over a billion LIOs in what appears to 
be "no time".  

I've been searching Metalink and Google with no success on finding anything. 
 Anyone out there seen anything like this?  

Thanks much and have a great New Year! 

Ric Van Dyke
Hotsos Enterprises

Hotsos Symposium 
March 7 - 11, 2010 
Be there.


The information contained in this communication is confidential, is
intended only for the use of the recipient named above, and may be legally

If the reader of this message is not the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.

If you have received this communication in error, please resend this
communication to the sender and delete the original message or any copy
of it from your computer system.

Thank You.


Other related posts: