Hi Alok,
I have seen this issue with Oracle 11g way back with Maximo 6 and 7.1. This a known problem that Maximo environment with Oracle.
Maximo has its own connection pooling and it clears the session from MAXSESSION table but can't clear them from V$SESSION table which is managed by Oracle. There are a set of properties related to connection pooling which you can find in System Properties application -

This is what I also got a response from IBM over discussion related to the explanation of this issue -
https://www.ibm.com/support/pages/why-are-my-oracle-sessions-inactiveYou should revisit automation scripts if any available, or reports to ensure that you are not leaving DB connection open. Also, check the oracle parameters on DB is set per best practices guidelines from IBM. These parameters impact Maximo performance and Oracle session management -
CURSOR_SHARING
FORCE
NLS_LENGTH_SEMANTICS
CHAR
WORKAREA_SIZE_POLICY=AUTO
PROCESSES=4000
OPEN_CURSORS=3000
SESSIONS=4000
TRANSACTIONS=2425
SESSION_CACHED_CURSORS=400
SESSION_MAX_OPEN_FILES=300
You can read more about connection pooling and tuning -
https://www.ibm.com/support/pages/explanation-maximo-application-server-connection-pooling-and-managementhttps://www.ibm.com/support/pages/tuning-connection-pool-properties-websphere-application-serverHope this helps!
------------------------------
Prashant Sharma
EAM360
------------------------------