GLOBAL ENQUEUE SERVICES DEADLOCK DETECTED

GLOBAL ENQUEUE SERVICES DEADLOCK DETECTED [ID 973178.1]
		修改時間 03-DEC-2009     型別 PROBLEM     狀態 MODERATED

In this Document
  
  
  
  

---

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Symptoms

Running Oracle 10gR2, release 10.2.0.4 CRS/RAC

The following message is being seen in the Alert logs of RAC instances:

       Global Enqueue Services Deadlock detected. More info in file

Cause

The Alert log contains the message " Global Enqueue Services Deadlock detected"

The corresponding trace file contains the following messages:

      Single resource deadlock: blocking enqueue which blocks itself, f 1

      resname : [0xbb7cc5db][0x82d0d4b5],[IV]

There are no reported external errors like:

      ORA-60 deadlock detected while waiting for resource
      ORA-4020 "deadlock detected while trying to lock object %s%s%s%s%s"

The symptoms match the following bug report:

      SINGLE RESOURCE DEADLOCK IS DETECTED

The bug states:

Hence you will see the text 'f 1' in the Single resource deadlock message and the 'resname' entry later in the FG trace file will reflect the text '[IV]'

If ALL these conditions are met then these deadlock messages can be ignored.

The message printed in the alert.log and FG trace file are for internal diagnostic purposes and can be ignored.

These messages will no longer be reported from Oracle release 11.1 onwards.

Solution

These messages can be ignore.

They do not represent a failure or problem.

References

- SINGLE RESOURCE DEADLOCK IS DETECTED