Configure the GoldenGate Manager process to automatically restart Extracts if they detach due to transient database or network blips.
Then comes the command: STOP EXTRACT . Or perhaps a planned maintenance window. The gears grind. For a terrifying second, the DBA holds their breath—will it hang? Will it throw an ORA- error? Will it orphan a checkpoint and force a laborious rebuild?
Confirmation message: Capture client successfully detached from GoldenGate capture.
Integrated Capture lives in the Streams Pool. If the STREAMS_POOL_SIZE is too small, the database may kick the GoldenGate client to save system stability.
Run the following query in the source database to check the state of the capture process: The gears grind
The detachment was successful, but the shutdown was forced by an error.
Is this happening on a or in a downstream deployment configuration? Share public link
Essentially, the database is acknowledging that the GoldenGate process has stopped requesting data and the session has been closed cleanly. Common Scenarios Where This Occurs
Oracle frequently releases Bundle Patches (BPs) for the database database log-mining engine and Oracle GoldenGate. Keeping both engines updated resolves known memory leaks and edge-case crashes. To help find the exact cause of your detachment, tell me: Will it orphan a checkpoint and force a laborious rebuild
At first glance, this is a dry, technical epitaph for a process. It signals the end of a Change Data Capture (CDC) session. But for those who have stared into the abyss of data synchronization, this line is not an ending; it is a lullaby. It is the sound of a clean break, a controlled stop, and a rare triumph over the chaos of logistics.
SELECT component, current_size/1024/1024 AS size_mb FROM v$sga_dynamic_components WHERE component = 'streams pool'; Use code with caution.
Look for entries around the same timestamp as the detach message. Search for ERROR or WARNING .
What and GoldenGate version are you currently running? ERROR FROM DBA_CAPTURE
If the source Oracle database is shut down ( SHUTDOWN IMMEDIATE or SHUTDOWN NORMAL ), the database will instruct all attached clients to disconnect. The Extract process will log a successful detachment before terminating itself because the database is no longer available. 3. Extract Process Timeout or Idle States
2025-03-15 10:00:05 ERROR ORA-03114: not connected to ORACLE. 2025-03-15 10:00:06 OGG capture client successfully detached from GoldenGate capture.
SELECT CAPTURE_NAME, STATUS, ERROR FROM DBA_CAPTURE;