Lock Conflict error
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 2 of 2

Thread: Lock Conflict error

  1. #1
    Join Date
    Mar 2001
    Hi all,

    I am getting the following error while shutting down my oracle server.this is pmon trace file.

    << Oracle process number: 2
    Unix process pid: 7266, image:

    *** SESSION ID:(1.1) 2001.
    *** 2001.
    found process 4300bc74 pid=15 serial=1 dead
    *** 2001.
    deleting process 4300bc74 pid=15 seq=1
    Lock conflict, transaction wait xid: 0x0004.02a.00101333
    deletion of process 4300bc74 pid=15 seq=1 unsuccessful>>

    I understood this is because of lock conflict,but don't know how to appoach further.could u please suggest me

  2. #2
    Join Date
    Aug 2001
    Waterloo, On
    UTLLOCKT.SQL script in RDBMS/Admin dir can be run after logging in as sys user to determine lock contention.

    This script uses DD views like V$Access and V$Session_wait to determine lock contention. A potential drawback is that this utility itself acquires some locks.

    Another method:
    Select * from V$session_wait where LOCKWAIT is not null;

    Value in COMMAND column tells what operation is happening.

    Raminder Singh

    Oracle Certified DBA: Oracle 8i, 9i

    Mail me at raminderahluwalia@rediffmail.com.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Click Here to Expand Forum to Full Width