Reply from SteveFLHSMV on Jul 3 at 2:42 AM Active sessions are those which the DB is currently servicing. If a user is getting subsecond responses, you're not likely to catch the session in an active status. Full scans of large tables, joins of several large tables without benefit of indexes, and sorting millions of rows of data are a just a few of the things that might characterize a session you catch with an active status.
Inactive sessions are waiting, Most likely they are waiting on a user who may be in the middle of a multistep transaction, between transactions, or idle. Users can remain inactive indefinitely unless limits have been set on idle time. Limits are often set to reduce the chance of unauthorized access hen a user leaves a device unattended without terminating the session. If connection is lost, the user loses control of the session. Dead connection detection can be set to check for abandoned connections. Keep in mind that inactive sessions are not a bad thing unless there are a large number abandoned or waiting on the DB (not the session owner).
Killed sessions have been marked for removal. As you noted, this can take a long time. It is not a priority for pmon; just housekeeping to do as time is available. Killed sessions don't require a lot of resources.
See Oracle's documentation concerning terminating sessions at
http://docs.oracle.com/cd/B28359_01/server.111/b28 310/manproc008.htm
| | | ---------------Original Message---------------
From: Master216
Sent: Thursday, May 24, 2012 3:15 AM
Subject: How to Remove the Inactive Sessions in Oracle 10g
How can we remove the inactive sessions in Oracle 10g? |
| Reply to this email to post your response. __.____._ |   _.____.__ |
No comments:
Post a Comment