Ogg Capture Client Successfully Detached From Goldengate Capture -
Detachment command varies by deployment type:
For Classic/Integrated Extract:
GGSCI> DETACH EXTRACT <extract_name>
For Microservices Capture: Use the REST endpoint or Admin Client:
oggadmin> DETACH CAPTURE <capture_name>
Confirmation message:
Capture client successfully detached from GoldenGate capture.
This message is specific to Integrated Capture mode.
In Classic Capture mode, GoldenGate reads the redo logs directly at the Operating System level. It does not rely on the database's LogMiner server, so you would generally not see this specific "client detached" terminology in Classic Capture setups.
In Integrated Capture, GoldenGate leverages the database engine. The relationship is more intimate. The "detachment" is essentially GoldenGate cleaning up the V$LOGMNR session resources within the Oracle Database SGA (System Global Area). For Microservices Capture: Use the REST endpoint or
This message is most frequently observed in three scenarios:
The message "OGG capture client successfully detached from GoldenGate capture" is the GoldenGate equivalent of a polite employee clocking out. It indicates that the Extract process has cleanly disconnected its session from the Oracle LogMiner server.
Key Takeaways:
As a GoldenGate Administrator, seeing this message during a STOP command should bring comfort, knowing that your process is shutting down cleanly without leaving zombie sessions in the database.
In Oracle GoldenGate (OGG), the message "OGG capture client successfully detached from GoldenGate capture"
is generally a positive status update rather than an error. It signifies that a "capture client" (typically an process) has cleanly disconnected from the underlying Logmining Server in the database. This usually happens during a controlled shutdown or a planned restart of the Extract process. Review: OGG Capture Client Detachment Status Status Summary: Message Type: Informational / Lifecycle Significance: the detachment was a consequence
High. It confirms that the integrated capture process didn't just crash; it successfully communicated its departure to the database's logmining server. Process Impact:
None (if intentional). The database will now hold onto the required redo logs until the client re-attaches, preventing data loss. Common Scenarios for this Message: Manual Stop: You issued a STOP EXTRACT command in GGSCI. Maintenance:
The database is shutting down, and OGG processes are detaching to preserve state. Automated Restarts:
A script or manager process is recycling the Extract for performance or log rotation reasons. What to Check if this was Unexpected: Alert Logs: Oracle Alert Log for corresponding SHUTTING DOWN WAITING FOR CLIENT REQUESTS messages from the V$GOLDENGATE_CAPTURE Report Files: VIEW REPORT command to see if a fatal error occurred the detachment. Process Status: INFO EXTRACT
Was this detachment part of a planned maintenance window, or did it happen unexpectedly during live replication? Root Cause for Database Shutdown - Oracle Forums
Either Oracle is correct & client is mistaken. or. Client is correct & Oracle has a bug & you need to submit Bug Report to Oracle. Oracle Forums V$GOLDENGATE_CAPTURE - Oracle Help Center not a clean shutdown.
| Error | Meaning | DBA Action |
| --------------------------------- | ------------------------------------------------- | ---------------------------------------------------------------------- |
| OGG-02912 (Insufficient SGA) | Database’s streams_pool_size too small. | Increase streams_pool_size or sga_target. Restart extract. |
| OGG-02902 (Timeout) | LogMiner server didn’t respond. | Check database alert log for bottlenecks or deadlocks. |
| OGG-06439 (No capture resources) | Too many concurrent LogMining servers. | Stop other extracts or increase MAX_SERVERS in the database config. |
In all these cases, you will see the "successfully detached" line after the failure, acting as a confirmation that the client gave up and disconnected cleanly.
Use grep or less on the Extract report file (.rpt). Look for:
Example of a bad sequence:
2025-03-15 10:00:05 ERROR ORA-03114: not connected to ORACLE.
2025-03-15 10:00:06 OGG capture client successfully detached from GoldenGate capture.
Interpretation: The database connection was lost first; the detachment was a consequence, not a clean shutdown.
