Detached From Goldengate Capture ((new)) | Ogg Capture Client Successfully

Troubleshooting Oracle GoldenGate: "OGG Capture Client Successfully Detached from GoldenGate Capture"

The OGG OS-level process that requests data.

This message is most frequently seen in the following scenarios:

: When a user issues a STOP EXTRACT command, the process finishes its current task and detaches from the database capture service. The architecture consists of two main parts: Expected

Unlike Classic Capture, which reads online redo logs directly from the file system, Integrated Capture leverages the database logmining server. The architecture consists of two main parts:

Expected behavior. No action required.

The message is a standard informational log entry in Oracle GoldenGate. It indicates that an Extract process (the "capture client") has cleanly disconnected from the database logmining server. Overview of the Message It indicates that an Extract process (the "capture

Transient state. Monitor but usually harmless.

The extract process is actively receiving LCRs (Logical Change Records) from the Capture process.

When this message appears, especially in a production environment, your immediate concern is whether the Extract client reattached or remains detached. A prolonged detached state will cause replication lag as LCRs accumulate in the LogMining server queue but are not being written to the trail. a downstream mining

It usually follows a primary error (like OGG-00664, OGG-01044, or OGG-01668) that caused the Extract to stop. Significance:

This is common in:

It indicates that a (e.g., a downstream mining, logdump, or custom application) has cleanly disconnected from the GoldenGate Capture process (e.g., Extract in classic or integrated capture mode, or the Local Capture in Microservices).

Replication lag grows to hours. Log shows detachment but no errors. Analysis: The OGG client detached due to idle timeout, but a network ACL change blocked the reattachment socket. OGG waited forever for a connection that never returned. Resolution: Set TRANLOGOPTIONS INTEGRATEDPARAMS (MAXCONNECTIONS 5) and IDLETIMEOUT 15 . Also fixed firewall rules.