Skip to main content

Cyclic blocking session removal script written by me for Oracle Database.

Plenty of times we have cyclic database blocking sessions. We have the script which runs in loop and kills them , only to see new blocking sessions have resurfaced.

This is a classic scenario that happens many time due to poor application design.

A was blocking B , B was blocking C.

Unless you have some automated blocking session clearing script.

You would run a script at point in time killing session of A.
Giving the lock ownership to B.   B could realize it late that he has the lock and not commit his work.
So DBA again goes in and sees block kills B's session.

In meantime Frustrated A logs in and start his activity again queuing him up in wait for lock retrieval . This goes on and you end up running the script 5-10 times to kill these sessions to finally clear the blocks.

Note this is not a deadlock which is normally apprehended and identified by oracle.

In such case we had written below plsql to clear the sessions. This basically goes in and check for locks every 2 seconds until all blocks are cleared.

BEWARE YOU WILL NOT HAVE CONTROL ON WHICH SESSION ARE BEING KILLED AS SOON AS SESSION BECOMES BLOCKING IT WILL BE REMOVED IF YOU USE BELOW SCRIPT. IMPORTANT SESSIONS COULD BE KILLED SO BE EXTREMELY CAREFUL AND I RECOMMEND NOT USING IT ON PRODUCTION WITHOUT TWEAKING THE FILTER FOR SPECIFIC SESSIONS OR USERNAMES IN WHERE CLAUSE.
set serverout on
declare
cursor c1 is
select  v.process,b.SQL_ID,  v.SID ,v.SERIAL#,b.SECONDS_IN_WAIT,v.username 
from        v$session v,user_definition_table ud,v$session b ,user_definition_table ubd
where      v.username not in ('SYS')
 and v.username=ud.user_name(+)
 and b.username=ubd.user_name
 and v.SID=b.FINAL_BLOCKING_SESSION
 and b.FINAL_BLOCKING_SESSION_STATUS='VALID'
 and v.status <> 'KILLED';
begin
for i in 1 ..100 
loop
dbms_lock.sleep(2);
for c1_rec in c1
loop
begin
dbms_output.put_line('USER ' || c1_rec.username);
execute immediate 'alter system kill session '''||  c1_rec.SId ||','|| c1_rec.SERIAL# ||''' immediate';
exception when others then
null;
end;
end loop;
end loop;
end;
/

Comments

Popular posts from this blog

Use the Microsoft Visual Studio Code(VScode) with Java Maven project.

The VS Code is the go to editor now a days for the latest technologies and scripting options. VS Code as we all know works seamlessly with Python and JavaScripts, and offcourse the .NET family. But VS Code has many extensions which makes it big Java IDEs run for their money. Lets explore what we could do with VSCode if we are Java developer. Install VScode , no brainer. Jus type download Visual Studio code in google. Alrright once we have VSCode. Open it. Install Maven and Java extension. 2. Go to files and a small window will now appear on left side navigation bar. 3. Select New Maven project. 4. Select the archtype from dropdown. 5. As usual input the grpid, artifactid etc. 6. Done. Go through a video which has much detailed navigation flow. Till next time !!!

New version of QueryLight is out !!

Here are the fixes and new development done. Latest Update and Fixes Added ability to write xlsx in new office xlsx format. Added ability to view code with F4. Added additional describe capabilities with F4. Download Page :  Go to Project HomePage https://sourceforge.net/projects/query-light-light-orcl-client/

Oracle Procedures to delete the parent child table rows with integrity constraints.

With some very hard work and innovative thinking we came up with the procedures (can be easily clubbed into package) to delete the parent child relationship row with any number of levels. Below code would find the child row of the parent row being deleted and delete it first , if the child row has its own child then that childs children are fetched and deleted so its basically a recursive algorithm There are not many situations where you would want to use this. We had a customer mstr record to be deleted which had 20 levels of child records held tight by (ORA-02292: integrity constraint   violated - child record found ) with their parent child constraints. Since this only was a delete for 1 Master record we went ahead and used this script. If you have more than 20 levels Wise course would be to disable constraints and really think why you want to delete such master record. Note of caution : BE CAREFUL using this on production environment. The procedures create the insert ...