Home » RDBMS Server » Server Administration » Reg. Deadlock detected
Reg. Deadlock detected [message #143402] Thu, 20 October 2005 05:55 Go to next message
d.dineshkumar
Messages: 211
Registered: April 2005
Location: Kolkatta
Senior Member
hi all,
how can i know from the trace file where the deadlock is detected and what can be the reason.trace file is giving me library object lock and library object handle.

Whats the difference between these two terms.

How to interpret the trace file.

Regds
Dinesh
Re: Reg. Deadlock detected [message #143584 is a reply to message #143402] Fri, 21 October 2005 00:55 Go to previous message
girish.rohini
Messages: 744
Registered: April 2005
Location: Delhi (India)
Senior Member
library cache lock:

The library cache lock Oracle metric event controls the concurrency between clients of the library cache. It acquires a lock on the object handle so that either:

1. one client can prevent other clients from accessing the same object
2. the client can maintain a dependency for a long time (e.g., no other client can change the object)

This lock is also obtained to locate an object in the library cache.

Now by looking at the tracefile you get to know deadlock is due to contention on which particular objects.

--Girish
Previous Topic: Reinstating tablespace using datafile
Next Topic: application tuning
Goto Forum:
  


Current Time: Sat Jan 25 09:39:36 CST 2025