My Oracle Support Banner

USER_USAGE_HISTORY.LOGOUT_TIME Is Kept Null Even After User Session Is Killed (Doc ID 2559527.1)

Last updated on DECEMBER 04, 2019

Applies to:

Oracle Agile PLM Framework - Version 9.3.5.0 and later
Information in this document applies to any platform.

Symptoms

Actual Behavior

Even though the user's session was killed, can see USER_USAGE_HISTORY records with LOGOUT_TIME kept null forever for those user


Expected Behavior

USER_USAGE_HISTORY.LOGOUT_TIME to be filled in when user's session is killed

Agile implements a feature where server checks for the record where logout_time is null even though the user is not logged in, and fills in logout_time with current time for every 5 min




Steps to Reproduce

The issue can be reproduced at will with the following steps:

  1. Login to Web Client as user1
  2. Shutdown Agile database instance
  3. When user tries to do something through Web Client, user gets logged out
  4. Restart Agile database instance
  5. Login to Web Client as user1
  6. Login to sqlplus as agile database user, and run below sql:
    * Change the value for TO_DATE so that you can get the result of the record which was created today
  7. You can see two records for user1 where LOGIN_TIME is today's date and LOGIN_TIME =null
  8. Click × button and close the browser
  9. Run the sql in step 6
    You can still see two records for user1 where LOGIN_TIME is today's date and LOGOUT_TIME =null
  10. Wait for more than 15 min, and run the same sql again.
    You can see one of the record gets LOGOUT_TIME filled in, however LOGOUT_TIME is kept null for the other record.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.