Database Networking (MOSC)

MOSC Banner

Any idea, on how we can force the Oracle database to kill a session where the client died abnormally

edited Jun 12, 2014 12:00PM in Database Networking (MOSC) 1 commentAnswered

Please we need to kill the sessions and rollback transaction of clients that died abnormally. This requirement is needed to resolve an issue of ACTIVE/ACTIVE application.

The application team tested to disconnect/crash one application node abnormally, we found that all the session connected from the crashed node are still there in the database, and if any session is updating a record it keeps locking this record.

Therefore I have set the SQLNET.EXPIRE_TIME to 1 minute in the sqlnet.ora on my RAC database and tried to simulate this client disconnection abnormally after running an update statement without commit. I found that the session remained connected and locking the table it is updating between 10 to 13 minutes then it got cleaned. This enhanced the situation to clean client sessions that might remain locking records/table forever; but 10 minutes is still a high value for the application requirement, we are looking to reduce this time.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center