Kill session in Oracle RAC
In various critical situations Oracle DBA has to decide to kill existing session or kill the background process of Oracle RAC database. At this moment remote Oracle DBA should need to terminate session/process called as murder of session of any instance.
Some basic syntax is changed for killing session in Oracle RAC instance. Oracle RAC database contains one or more instances. First oracle RAC DBA should need to identify which session has be killed and in which instance contains said target session.
Kill Session: Terminate process/session in Oracle RAC using SQLPLUS command. View large
We use v$session for indetifying target session to kill in non-rac database.Here in Oracle RAC instance we should need to check and identify session using gv$session. Because only gv$session contains rac instance identifier column. After identifying target session from gv$session we need command "alter system kill session" with session identifier (sid), serial number (serial#) and instance number of Oracle RAC (instance_no). Here is example to kill or terminate active session from Oracle RAC database or instance.
And terminated user session will get message in sqlplus that "your session has been killed" in Oracle RAC instance. We can get output of status as "killed" from gv$session for terminated session.
Dbametrix is expert remote dba service provider team. Dbametrix has solid understanding to make SLA as per specification and requirement of client and end users. Dbametrix believes to provide remote DBA services of database administration using SLA. Due to this reason Dbametrix offers SLA based cost effective remote dba plans. Client of Dbametrix can able to put trust on company because Dbametrix delivers low cost remote dba plans using Service Level Agreement SLA and response time matrix.
Check another articles on same topic of different execution type.