Re: Resolve TM lock

By the time you see this message, I'm sure you already successfully dropped the table. Next time you have this problem, you can find who was holding the session before it was killed. After you kill it, go to his terminal and try to connect again (or run select * from dual). You'll be told session has been killed. That should clear the entry in v$session. If not, go to the operating system and kill the corresponding process, found by joining v$session.paddr with v$process.addr. Use orakill.exe instead on NT to do this. If it still hangs in, get in svrmgrl and wake up PMON: oradebug wakeup <the PMON PID>. If everything fails, just wait.

Yong Huang
yong321_at_yahoo.com

In article <uFHS5.8$MI4.160808_at_news.interact.net.au>,   "Chuan Zhang" <chuan_at_asiaonline.net> wrote:
> Hi, all
>
> I got an error when I drop a table "ORA-00054: resource busy and
 acquire
> with NOWAIT specified".
>
> I figure out that table was locked by a session. Therefore, I
 use "alter
> system kill session 'sid,serial#' " to kill session. Finally, that
 session
> is marked "killed".
>
> Again, I still cannot drop that table.
>
> Have any idea what anything I can do for this situation.
>
> My platform is on Solaris 2.7, Oracle EE 8.1.5.
>
> Many Thanks
>
> Chuan
>
>

--
Yong Huang

(yong321_at_yahoo.com)
(http://www.stormloader.com/yonghuang/)


Sent via Deja.com http://www.deja.com/
Before you buy.