Oracle Capture in state "WAITING FOR TRANSACTION", excessive time spent in LOGMNR_DICT_CACHE.SAVE_OBJ()
(Doc ID 2030973.1)
Last updated on JULY 01, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.1 [Release 11.2 to 12.1]Oracle GoldenGate - Version 11.2.0.0.0 to 12.1.3.0.0 [Release 11.2 to 12.1]
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
Information in this document applies to any platform.
Symptoms
The following products;
- Streams Replication Capture
- GoldenGate INTEGRATED EXTRACT
may be in the state "WAITING FOR TRANSACTION".
The Alert log for the Oracle database may also show the following:
Thu Jun 18 13:10:22 2015
krvxenq: Failed to acquire logminer dictionary lock. pid=330 OS id=6554046. Retrying...
An AWR report will show that the LogMiner BUILDER process (typically, process name MS01) is executing the PL/SQL routine LOGMNR_DICT_CACHE.SAVE_OBJ() many times.
The database contains tables with a high number of partitions, where Partition Maintenance operations are being performed on these tables, specifically ALTER TABLE operations involving MERGE, SPLIT, or MOVE.
These operations would then be captured by the LogMiner.
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 |