During investigation of customer's environment revealed that the INACTIVE session count is over 1500 always, Should the INACTIVE session be killed automatically when the idle time expired?
Checked the Database profile IFS_INETRNAL which is used for Database users, the IDLE_TIME is set to DEFAULT. Should this be set to UNLIMITED ?
Should there be a time on MAX IDLE TIME parameter OR leave as is where it always maintain 1500 odd INACTIVE sessions. This inactive sessions will hold on to resources with no legitimate reason and will create Possible performance issue.
Any recommendations/changes needs to stop INACTIVE session count getting higher values ?
Best answer by Ragaventhan Sathananda
View original