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

: While usually benign, seeing this message unexpectedly—without a manual stop command—can signal that the OGG process or the underlying database session was killed or terminated by a resource manager. Oracle Blogs Troubleshooting if Unexpected If the detachment occurs frequently or leads to an status, consider these steps: OGG-02028 - Oracle GoldenGate Capture for Oracle 20 Oct 2016 —

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).

However, context is everything. When accompanied by ORA errors, network disconnects, or unexpected abends, this message serves as the final log entry before a failure. By understanding the architecture—where the capture client (OGG) detaches from the internal capture process (database)—you can quickly distinguish routine maintenance from critical incidents.

It is an informational message with severity level INFO . When accompanied by ORA errors, network disconnects, or

The database is shutting down, and OGG processes are detaching to preserve state. Automated Restarts:

2025-03-11 10:23:45 INFO OGG-00999 OGG capture client successfully detached from GoldenGate capture.

Here’s a technical guide to understanding and handling the message. The database is shutting down, and OGG processes

GGSCI> STOP EXTRACT EXT1

Run this every 5 minutes via a scheduled job. This keeps the capture client active without idle timeout.

-- Configure your RMAN deletion policy to respect GoldenGate CONFIGURE DELETION POLICY TO APPLIED ON MINING SITE TO STANDBY; Use code with caution. Conclusion Use code with caution.

While the message itself dictates a successful detachment, the context in which it appears determines whether action is required. Scenario 1: It follows a manual STOP command. Normal behavior. Action: No action required.

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