In Oracle GoldenGate (OGG), the message "OGG capture client successfully detached from GoldenGate capture"
The "detached" message is unique to Integrated Capture because it involves a formal registration with the Oracle kernel. Classic Capture is like reading a flat file—you just close the file when done.
: If this message appears without a manual command, it indicates the Extract has "abended" (crashed) or been terminated by a system process. In this case, you should immediately check the OGG Error Log ggserr.log Extract Report File view report ) for the specific error code, such as Oracle Forums Common Root Causes for Unexpected Detachment Root Cause for Database Shutdown - Oracle Forums In Oracle GoldenGate (OGG), the message "OGG capture
You will most often see this in the OGG error log ( ggserr.log ) or the process report file immediately after issuing a STOP EXTRACT command. Common Scenarios
: If you manually stopped the process, this message confirms a successful and clean exit. Unexpected Detachment In this case, you should immediately check the
If this message appears without a manual stop command, it may indicate an underlying issue that caused the Extract to end its session prematurely: OGG-02028 - Oracle GoldenGate Capture for Oracle
To successfully detach and reattach the OGG capture client, follow these steps: Instead, it "attaches" as a client to an
In , the OGG Extract process does not read redo logs directly. Instead, it "attaches" as a client to an Oracle LogMining server, which sends data changes in the form of Logical Change Records (LCRs).