Hi Guys,
I have a couple of questions regard to session status and the limit of session numbers which is set in parameter SESSIONS.
1) these are the Status of the session:
ACTIVE - Session currently executing SQL
INACTIVE
KILLED - Session marked to be killed
CACHED - Session temporarily cached for use by Oracle*XA
SNIPED - Session inactive, waiting on the client
My question is, are the resource consumed by the sessions which are in 'SNIPED', 'KILLED' released?
what about 'INACTIVE'?
2) there is a parameter called 'SESSIONS' which is used to set the limit of session numbers.
So, my question is, the sessions in which status, will be counted into the total number of sessions, which in turn, will be compared against parameter SESSIONS?
any input will be highly appreciated.
Thanks in advance!