Queue Spillage issues after Dropping a Streams Propagation
(Doc ID 1072787.1)
Last updated on AUGUST 30, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.1.0 [Release 10.2 to 11.2]Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
If you drop a Streams propagation when there is queue spill on the capture site, you may experience 2 different problems related to queue spillage that can both be present or exist separately.
The first is related to queue spill for LCRs associated with the propagation that just has been dropped. The clean up process may leave orphan LCRs spilled onto the the spillover queue table (always less than 32) for the dropped propagation.
The second is related to queue spill for LCRs associated with any surviving propagation schedules using the same source queue for which a propagation has been dropped. In this case, you may observe that the queue spill for the surviving site grows constantly.
Changes
Dropped propagation in a Streams environment when there was queue spillage.
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 |