This is the GoldenGate Extract process (specifically Integrated Extract).
When this detachment occurs unexpectedly, follow these steps to isolate and resolve the issue. Step 1: Check the GoldenGate Report File
A successful detachment occurs in several operational contexts: If memory exhaustion is suspected, check the current
When new redo logs arrive, it will reattach automatically.
If memory exhaustion is suspected, check the current allocation of the Streams Pool. You can query the database using: SELECT purpose, status, bytes FROM v$streams_pool_advice; Use code with caution. For further analysis, consider sharing: The output of
If you are still experiencing this issue, please check the database alert log for the specific ORA-error code and ensure your GoldenGate version is patched to the latest recommended release. For further analysis, consider sharing: The output of VIEW REPORT The specific ORA- errors from the database alert log. OGG-02028 - Oracle GoldenGate Capture for Oracle
2025-05-23 14:00:01 ERROR OGG-02717 Unable to allocate LogMiner session. 2025-05-23 14:00:01 INFO OGG-06408 OGG capture client successfully detached... it will usually "abend" (abnormally end).
The message should not invoke fear. Instead, it should be viewed as a stamp of approval from the GoldenGate engine that a shutdown sequence was handled with integrity.
This is entirely normal. You will always see this message when you manually stop a running Integrated Extract.
The database logmining server releases SGA memory allocations (streams pool) and background processes (like readers and preparers) that were dedicated to serving that specific GoldenGate Extract.
If an Extract fails to detach successfully, it will usually "abend" (abnormally end). This happens if: The database crashes suddenly. An administrator issues a KILL EXTRACT or a hard OS