AQ/PLSQL Notifications Do Not Maintain FIFO or Priority Ordering
(Doc ID 225810.1)
Last updated on MARCH 13, 2025
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.8 to 11.2.0.3 [Release 9.2 to 11.2]Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
Information in this document applies to any platform.
Purpose
To discuss the unpublished bug 1567187 PL/SQL Notification cannot be serialized and a workaround to it.
Scope
This article is intended for anyone interested in maintaining first-in first-out (FIFO) or priority ordering of callbacks when using AQ PL/SQL notifications.
Details
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
| Purpose |
| Scope |
| Details |
| Serialization of AQ PL/SQL Notifications |
| Notification example demonstrating that Priority ordering is not maintained using a standard callback procedure |
| Notification example demonstrating that Priority ordering is maintained using a modified callback procedure |
| References |