dba_audit_trail session duration problem
889367Nov 15 2012 — edited Nov 21 201211.2.0.2 standard edition
audit_trail=db
auditing create session by accesss
I'm trying to determine session durations and the resource usage of those sessions, but I'm seeing that all the logoff records in dba_audit_trail have the same value for timestamp & logoff_time and I know that it's impossible to be true from the resource usage that those records are showing.
for example, on our quad core machine I have the following records
select sessionid,
to_char(timestamp,'DD-MON-YY HH24:MI:SS'),
to_char(logoff_time,'DD-MON-YY HH24:MI:SS'),
to_char(extended_timestamp,'DD-MON-YY HH24:MI:SS'),
action,action_name,
logoff_lread,logoff_pread,logoff_lwrite,session_cpu*.01
from dba_audit_trail
where action in ( 100,101, 102 )
order by sessionid,action;
15750655 17-OCT-12 22:25:42 17-OCT-12 22:25:42 17-OCT-12 22:25:42 102 LOGOFF BY CLEANUP 1602201159 1238192717 941059 11113.38
15790652 14-OCT-12 11:02:52 (null) 14-OCT-12 11:02:52 100 LOGON
15790652 14-OCT-12 11:03:03 14-OCT-12 11:03:03 14-OCT-12 11:03:03 101 LOGOFF 10357 16248 4 3.22
you can see the first record shows the session didn't last over a second but yet it used 11113.38 seconds of cpu. The second and third records are the same session and the logon record shows the correct login time, but that didn't follow through to the logoff record.
Not sure if I'm doing something wrong, or if I found a bug. I did search meta link and found nothing yet that looks related.