RE: Killed session
- From: "Goulet, Richard" <Richard.Goulet@xxxxxxxxxxx>
- To: <Mayen.Shah@xxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 12 Nov 2008 12:41:32 -0500
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.
Dick Goulet
Senior Oracle DBA
PAREXEL International
978.313.3426
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@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of
Mayen.Shah@xxxxxxxxxx
Sent: Wednesday, November 12, 2008 9:24 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Killed session
Hi Listers,
Oracle 9.2.0.8 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.
Thanks
Mayen
Other related posts:
