USESSION_CLEANUP_EXPIRED logically deletes USESSION records that have not updated their last_active_time based on the Expired Session settings. Marking expired USESSION records as logically deleted maximizes the number of module access logins that are available. Since it is not cleaning up the underlying data (physically deleting rows), the task completes quickly.
Values in the SETTINGS table control the cleanup of expired sessions. By default, although the cleanup of expired sessions occurs every two hours, the SETTINGS table does not contain a value for this setting. Use the SETTINGS_WRITE_STRING (value, namespace, setting) stored procedure to change the default cleanup value.
For example, setting the value to "2d" deletes expired sessions older than two days.
Note: Oracle recommends that you set the ExpiredLongSessionTimeout sessions to at least one hour longer than your longest job. For example, if your longest job is a summarizer job that usually takes 12 hours, you should set the value in the SETTINGS table to at least 13.
Refer to the table below for information about the USESSION_CLEANUP_EXPIRED Settings.
USESSION_CLEANUP_EXPIRED Settings
Setting Description: ExpiredSessionTimeout determines how long an inactive user session will remain in the records before it is marked deleted. User sessions are created when a P6 Professional user logs into P6 Professional. | |
|---|---|
Namespace | database.cleanup.Usession |
Setting Name | ExpiredSessionTimeout |
Default Setting | 2h |
Type | Interval |
Setting Description: ExpiredLongSessionTimeout determines how long a session that is running a job-like operation (that is still processing) will remain in the records before it is marked deleted. Job-like operations are processed by job services and some are performed by logged in P6 Professional users. Operations that are considered job-like are:
| |
Namespace | database.cleanup.Usession |
Setting Name | ExpiredLongSessionTimeout |
Default Setting | 12h |
Type | Interval |