Ogg Capture Client Successfully Detached From Goldengate Capture __link__ Jun 2026

is adequately configured. Memory starvation in the streams pool can cause forced detachments. Check Database Alert Logs:

in GGSCI or Admin Client. The process completes its current transaction read and safely detaches. Extract Restart:

From the database's perspective, when a GoldenGate Extract client is up and running, the capture process is marked as . Conversely, if the Extract client stops normally (e.g., via STOP EXTRACT in GGSCI), the capture process remains active but enters a DETACHED state. This is an important and often-misunderstood nuance: the detachment itself is usually normal . The capture process continues to mine the logs and hold the position, waiting for the Extract client to reattach and resume reading.

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

The log message becomes critical when it appears unexpectedly, particularly when followed immediately by a process (Abnormal End) or database errors.

Sometimes the detachment is incomplete. You may need to manually unregister and re-register the Extract if it won't restart. Unregister: UNREGISTER EXTRACT [EXTNAME] DATABASE Re-register: REGISTER EXTRACT [EXTNAME] DATABASE Step 5: Restart the Extract

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. The process completes its current transaction read and

If you are running an older version, consult Oracle Support. Bugs in the Integrated Capture feature are frequently patched. Ensure you are on a stable patch set (e.g., higher than 12.2.0.1.160517). 5. Check Archivelog Mode

This is the expected behavior of Integrated Capture.

While the message says successfully , there is a nuance. In rare edge cases, an abnormal termination (e.g., KILL -9 on the extract process, or a database session timeout) will produce this message. However, if the database's LogMining server detects the client is dead and performs a cleanup, it might log a variation. But the standard successfully detached suggests a polite, application-level goodbye. This is an important and often-misunderstood nuance: the

Integrated Capture relies heavily on the Oracle Database Streams Pool. Ensure your STREAMS_POOL_SIZE is adequately configured (minimum 1GB to 2GB per Integrated Extract, depending on volume) to prevent unexpected disconnections.

Understanding the "OGG Capture Client Successfully Detached" Message

If this occurs unexpectedly (i.e., the process "abends"), look for these root causes in the report file ( view report [extract_name] Streams Pool Exhaustion: The database STREAMS_POOL_SIZE