Ok,

- user logs on at time x
- User does nothing i.e. session is idle.
- 10 minutes later, you look at the last activity and its BEFORE X!

Ran the following script off metalink (Doc id = 16728.1):

select sid, to_char((sysdate - (hsecs - value)/(100*60*60*24)),
'dd-mon-yy hh:mi:ss') last, to_char(sysdate, 'dd-mon-yy hh:mi:ss') curr,
(hsecs - value)/(100) secs, (hsecs - value)/(100*60) mins
from v$timer, v$sesstat
where statistic# = (select statistic# from v$statname
where name = 'process last non-idle time');

and get the following:


SID Last non-idle time
--- -------------------
1 03-nov-04 07:53:48
2 03-nov-04 07:53:47
3 03-nov-04 07:53:47
4 03-nov-04 07:53:47
5 03-nov-04 07:53:47
6 03-nov-04 07:53:47
7 03-nov-04 07:53:47
8 03-nov-04 07:53:47
9 03-nov-04 07:53:47
15 11-mar-05 02:15:27
16 11-mar-05 02:15:31
18 11-mar-05 02:14:54
19 11-mar-05 02:15:28
23 11-mar-05 02:14:54

(the ouput is edited to only show last non idle time). Note the 2005 entries

Ok, this is tru64 unix, running 'date'on the server brings the correct date and time, i.e. today's date and time in gmt.

What could cause this? The knock on effect is that we have a job that kills idle sessions after 60 mintes, but in reality these sessions are being wiped out much earlier than this.

Any help, this is kinda urgent!

Bazza