Ogg Capture Client Successfully Detached From Goldengate Capture !free!

In Oracle GoldenGate (OGG), the message "OGG Capture Client successfully detached from GoldenGate Capture"

Integrated Capture Mode

Modern OGG (12c and later) uses Integrated Capture. Here, the Extract process does not directly read the redo logs. Instead, it acts as a client to a background server process inside the Oracle database known as the GoldenGate Capture process (also part of the logical replication framework inside the database engine). In Oracle GoldenGate (OGG), the message "OGG Capture

3. Is It an Error or Warning?

No. It is an informational message with severity level INFO. in GGSCI or via Admin Client

2. Extract Restart or Rolling Upgrade

During maintenance windows, an Extract may be stopped and started to refresh parameters or apply patches. The detachment message confirms the "stop" phase is complete, allowing the environment to prepare for the new instantiation (attachment) of the process. state from dba_capture

Implications

INFO EXTRACT ext_sales, DETAIL

2. Common Scenarios Where You See This Message

| Scenario | Description | |----------|-------------| | Stopping an Extract | When you run STOP EXTRACT <name> in GGSCI or via Admin Client, the capture client detaches cleanly. | | Logdump exit | Exiting logdump after attaching to a capture process. | | Microservices – stopping a deployment | Stopping a GoldenGate Microservices deployment gracefully. | | Downstream capture client disconnect | A client (e.g., remote mining tool) disconnects from the capture process. | | End of a script | A script that opened a connection to the capture process terminates normally. |

Check Capture Status: Run select capture_name, state from dba_capture; in the database to see if the underlying capture process is still active or has also stopped.  Root Cause for Database Shutdown - Oracle Forums