RE: Killed session
Date: Wed, 12 Nov 2008 13:46:48 -0500
No distributed transaction involved.
"Goulet, Richard" <Richard.Goulet_at_parexel.com> Nov 12 2008 12:41 PM
Mayen Shah/ITS/Lazard_at_Lazard NYC, oracle-l_at_freelists.org cc
RE: Killed session
First thing I'd look at is if a distributed transaction is in process. Look in dba_2pc_pending as the session may be looking for a foreign database that is where this session started. Otherwise you may have one of those instances where a database restart is the only way you'll clear the locks.
Senior Oracle DBA
information transmitted in this communication is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please destroy any copies, contact the sender and delete the material from any computer.
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
On Behalf Of Mayen.Shah_at_lazard.com
Sent: Wednesday, November 12, 2008 9:24 AM To: oracle-l_at_freelists.org
Subject: Killed session
Oracle 220.127.116.11 on Solaris 9
In one of my production database session was long running. Session was killed last night. Since then session is marked as KILLED in v$session. This killed session is holding locks on few tables and causing further problems.
USED_UBLK in v$transaction is constant at 287 since late last night.
I identified unix process and killed at os level two hours ago, still session would not go away. (os process is gone already)
What else should I be looking at? How do I get rid of KILLED session?
I do not have luxury to recycle database.
Your help is greatly appreciated.