My Oracle Support Banner

Frequent Ges: Potential Blocker (Pid=nnnn) On Resource TM-<id1>-<id2> (Doc ID 473124.1)

Last updated on MARCH 07, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Oracle Server Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4


Symptoms

Frequent messages in alert log like:
GES: Potential blocker (pid=<pid>) on resource TM-<id1>-<id2>

For example:
GES: Potential blocker (pid=24172) on resource TM-0000A7BA-00000000;
enqueue info in file /u00/oracle/admin/RAC/udump/rac1_ora_2919.trc and DIAG trace file

Global Enqueue Services Deadlock detected. More info in file
/u00/oracle/admin/RAC/udump/rac1_ora_15389.trc.

In trace file generated, it shows:

Single resource deadlock: blocking enqueue which blocks itself, f 0
Granted global enqueue 0x89368260
----------resource 0x0x7fbf77e4----------------------
resname : [0x0A7BA][0x0],[TM]

The deadlock causes excessive trace dumps to be generated in the background_dump_dest, filling up the disk space.

Changes

New implementation.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.