In various critical situations, Oracle DBA has to decide to kill the existing sessions or kill the background process of Oracle.
Then the question is raised that in which type of situation remote dba should need to kill session and process. We are explaining those situations and incidences here.
When blocking lock occurs and other sessions are waiting to acquire a lock on the same object. But the blocker session doesn’t end the transaction. At this moment Remote oracle dba should need to identify blocking sessions and terminate it for clearing resources for other sessions.
When maximum connections reached error occurs. No room available for any new connection or session. At this time Remote Oracle DBA should need to kill some of the idle processes from the Oracle database.
When database found in hang status and shutdown abort command also doesn’t work, at the same time Remote Dba should need to terminate instance abnormally with murdering background processes.
In the above critical situation, we need to kill or terminate or murder some session or process using the command line or GUI utility like OEM, TOAD, etc. But the command line is more easy and helpful to solve such critical situations in remote DBA support services.
Please find the following new articles on the same topic.
Article explains how to kill session in Oracle using sqlplus utility.
Article explains how to kill session in Oracle 11g using new feature.
Article explains how to kill session in Oracle RAC databases.
Article explains how to kill session using only operating system commands in Unix,Linux & Windows without Sqlplus.
All the best,