AQ$_PLSQL_NTFN Scheduler Jobs Executed in large numbers affecting Database performance
(Doc ID 2001165.1)
Last updated on APRIL 10, 2023
Applies to:
Oracle Database Cloud Exadata Service - Version N/A and laterOracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 11.2.0.4 to 12.1.0.2 [Release 11.2 to 12.1]
Oracle Database - Standard Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]
Information in this document applies to any platform.
Symptoms
25 thousand Scheduler jobs with the job_name AQ$_PLSQL_NTFN_% are being executed and affecting database performance.
From Notification tracing these are related to two subscribers on the SYS.SCHEDULER$_EVENT_QUEUE queue.
The first is related to an ILM_AGENT subscriber which is invoking the internal callback procedure SYS.PRVT_ILM.ILM_CALLBACK and the second to a SCHED$_AGT2$_% subscriber which is invoking the internal callback procedure SYS.SCHEDULER$_JOB_EVENT_HANDLER as per the following trace entries
The messages with the msgid no longer exist in user queue SYS.SCHEDULER$_EVENT_QUEUE and the AQ$_PLSQL_NTFN_% jobs do not end.
There may also be a large numbers of EXPIRED messages in the notification exception queue AQ$_AQ_SRVNTFN_TABLE_%_E.
Changes
Using Advanced Queue Notification system.
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 |