Ogg Capture Client Successfully Detached From Goldengate Capture Portable

: If an Extract process fails due to an error (e.g., ORA-03113 or OGG-02028), the logs will show this detachment as the process terminates.

| Scenario | Description | |----------|-------------| | | 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. |

: 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

INFO OGG-00999 OGG capture client successfully detached from GoldenGate capture. INFO OGG-00998 Extract EXT1 stopped gracefully.

If this happened unexpectedly, review the GoldenGate ggserr.log for preceding events. : If an Extract process fails due to an error (e

Bad: STOP EXTRACT * ABORT (if used on a single extract unnecessarily). Good: STOP EXTRACT ext_sales .

: If this message is preceded by an "ERROR" or "PROCESS ABENDING" in the GoldenGate report file, it means the Extract encountered a critical failure (like a missing log file or permission issue) and detached as part of its failure sequence. Next Steps for Troubleshooting

is included in the logs, it acts as a confirmation that the checkpoint was safely written and the handshake with the database was closed without errors. 4. Technical & Operational Implications Data Integrity

Was this detachment triggered by a , or did it happen unexpectedly ? | | Microservices – stopping a deployment |

Understanding the context of when the message appears will demystify it completely.

(found in the OGG home directory) or the process report file to find the actual error that preceded the detachment. www.oracle-scn.com GGSCI> view report [EXTRACT_NAME] Use code with caution. Copied to clipboard Step 2: Check Database Health

2021-06-06 07:54:22.697000000 AM +02:00 OGG Capture client successfully detached from GoldenGate Capture OGG$CAP_INEXT1 (OS pid=17884).

When you encounter the log message "Capture client successfully detached," follow these steps to ensure system health: | : Run select capture_name, state from dba_capture;

The message "OGG capture client successfully detached from GoldenGate capture" is rarely a problem by itself. In most cases, it is a sign of a well-behaved client-server disconnection during a normal stop, idle timeout, or transient database operation.

You can check the status of the capture server by querying the database:

Configure the GoldenGate Manager process to automatically restart Extracts that detach due to transient network or database hiccups. Add the following to your mgr.prm file: