Inactive Sessions In The Database
(Doc ID 2636405.1)
Last updated on FEBRUARY 07, 2020
Applies to:Oracle Real-Time Scheduler - Version 22.214.171.124.0 and later
Oracle Utilities Mobile Workforce Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On : 188.8.131.52.0 version, Mobile Communications Platform
Inactive sessions in the database
using ORS version 184.108.40.206 and observed many database sessions are in Inactive status which were created almost a month back. These sessions are from the following users: SYS, CISUSER, PUBLIC, CISADM, DBSNMP (Maximum are from CISUSER).
need your help to tackle this as saw inactive sessions if not cleared causes issues in the application performance and normal way of working (for other applications like Siebel).
1) Why do the inactive sessions not get cleared out automatically?
2) For some sessions you see LAST_CALL_ET is not much so it was created in the past for example: 16th June but the LAST_CALL_ET value is '2' or '103'. Does this mean these sessions get Active as well.
3) Based on the application internal behaviour, can you please confirm if user can put an IDLE time setting for such sessions to terminate them from the database? Is there an ideal setting you recommend for ORS v2 application?
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