Ogg Capture Client Success!link! Fully Detached From Goldengate Capture Jun 2026

Set appropriate parameters so the extract doesn’t detach due to age:

SELECT capture_name, state, status FROM v$goldengate_capture; Use code with caution.

| | Symptoms & Log Evidence | Resolution Steps | | :--- | :--- | :--- | | Network Instability | Repeated OGG-01676, connection timeouts. Intermittent detachment and reattachment. | 1. Verify network stability between the GoldenGate server and the database host. Check for firewalls, VPN drops, or switch issues. 2. Increase GoldenGate's TCP keepalive settings in the GLOBALS file. | | Extract Process Termination | Extract in ABENDED state. OGG-01194 with an Oracle error. | 1. Review the Extract parameter file for errors. 2. Ensure the user in the DELOGIN command has all required privileges ( EXECUTE on DBMS_FLASHBACK , SELECT on V$DATABASE , etc.). 3. Attempt to START EXTRACT <name> . If it fails again, you may need to ALTER EXTRACT <name> ... BEGIN NOW if data re-sync is feasible or consult Oracle support. | | Database LogMiner Session Hang | Capture process is stuck in BUSY state. Lag increases without Extract failing. | 1. In the database, find the SID of the hung LogMiner session. 2. Terminate it: ALTER SYSTEM KILL SESSION '<sid>,<serial>' IMMEDIATE . GoldenGate will start a fresh mining session on next restart. | | Improper Environment Configuration | Extract fails to start after a reboot. Detach occurs immediately on start. | 1. Verify the bequeath_detach parameter. For bequeath connections, your sqlnet.ora must contain bequeath_detach=true . 2. Re-add the extract: DELETE EXTRACT <name> , then ADD EXTRACT <name> INTEGRATED TRANLOG, BEGIN NOW . 3. Re-register with the database: REGISTER EXTRACT <name> DATABASE . |

Ensure that there is enough space in the for log archiving and that the server has sufficient CPU and memory for logminer . Best Practices to Prevent Future Detachment To ensure a stable OGG environment:

INFO EXTRACT <extract_group_name>

| Error | Meaning | DBA Action | | --------------------------------- | ------------------------------------------------- | ---------------------------------------------------------------------- | | OGG-02912 (Insufficient SGA) | Database’s streams_pool_size too small. | Increase streams_pool_size or sga_target . Restart extract. | | OGG-02902 (Timeout) | LogMiner server didn’t respond. | Check database alert log for bottlenecks or deadlocks. | | OGG-06439 (No capture resources) | Too many concurrent LogMining servers. | Stop other extracts or increase MAX_SERVERS in the database config. |

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

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.

Log output:

The EXTRACT process is connected to the database to read change data.

Several factors can contribute to the OGG Capture client detachment from GoldenGate Capture. Some of the common causes include:

If it transitions back to a RUNNING state and begins checkpointing, the detachment was likely a transient issue.

STOP EXTRACT ext_capture

To understand the ogg capture client successfully detached message, we first need to demystify how Oracle GoldenGate captures data changes. In modern, integrated capture setups (the standard for Oracle 12c and later), the extraction process is split into two components that work closely together:

If you see a status of DETACHED , the capture server is running but waiting for an Extract client to attach to it. This is normal if an Extract is stopped, but abnormal if you expected the process to be running.

cat $OGG_HOME/ggserr.log