My Oracle Support Banner

Self Deadlock in Job Queue Coordinator Process (CJQ0) Prevents a Propagation Schedule from Being Unscheduled (Doc ID 1597635.1)

Last updated on FEBRUARY 26, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 11.2.0.4 [Release 11.2]
Oracle Database Cloud Schema 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
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Unable to unschedule an Advance Queueing propagation schedule. The schedule the session performing the unschedule is being blocked by the CJQ0 process on one of the nodes. 

Systemstate analysis indicates the following 

               Resource Holder State
     PIN: Handle=0x62501e68    ??? Blocker
    LOCK: Handle=0x6aa6a408    66: 66: is waiting for 66:
  Rcache object=0x6f7f8e30,    66: Self-Deadlock

Object Names
~~~~~~~~~~~~
PIN: Handle=0x62501e68                                
LOCK: Handle=0x6aa6a408                                
Rcache object=0x6f7f8e30, cid=8(dc_objects)            

Process 66 is the CJQ0 process which is the Job Queue Coordinator process.

 

NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

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
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.