In some architectures (e.g., batch-oriented replication), an extract might be configured to run for a specific duration or stop after processing a specific log sequence number (e.g., USING LOGFILE or END parameter). When the extract reaches its defined endpoint, it self-initiates a detach.
Conclusion: Normal, if part of a scheduled job.
While a "successful detach" is usually positive, the following conditions require attention:
This message indicates that an Oracle GoldenGate (OGG) Extract process has successfully disconnected from the source database. 📌 Meaning of the Message
Successful shutdown: The Extract process was stopped normally by a user or script.
Database disconnection: The GoldenGate capture client detached cleanly from the Oracle database.
No action required: This is an informational message (INFO), not an error. 🔍 Common Causes
Manual Stop: An administrator issued the STOP EXTRACT command.
System Maintenance: The GoldenGate instance or the source database was being restarted.
Graceful Exit: The process reached a specified end point (e.g., THREAD or EOF) and closed safely. 🛠️ Related GGSCI Commands
To check the current status or restart the process, use these commands in the GGSCI or Admin Client console: View status: STATUS EXTRACT Start process: START EXTRACT View logs: VIEW REPORT 💡 Best Practices
Verify state: Ensure the extract is in a STOPPED state and not ABENDED.
Check alert logs: If this happened unexpectedly, review the GoldenGate ggserr.log for preceding events. In some architectures (e
Blog: Understanding the "OGG Capture Client Successfully Detached" Message
If you are monitoring your Oracle GoldenGate (OGG) environment and spot the message "OGG Capture client successfully detached from GoldenGate Capture" in your database alert logs or GoldenGate report files, you might wonder if something has gone wrong.
Here is a quick guide on what this message means and how to handle it. What Does This Message Mean?
This message is typically informational rather than an error. In an Integrated Capture setup, the GoldenGate Extract process acts as a "client" to the database's LogMiner server.
When the Extract process stops—whether manually, due to a scheduled maintenance window, or because of a database shutdown—it "detaches" from the mining server. The message confirms that the handshake between GoldenGate and the database engine has ended cleanly. Common Scenarios Manual Stop: You issued a STOP EXTRACT command in GGSCI.
Database Shutdown: The database was closed or restarted, forcing the capture process to disconnect.
Process Abending: If accompanied by an error (like OGG-01668), it indicates the process stopped unexpectedly due to a missing trail file or privilege issue. Troubleshooting Steps
If this message appeared unexpectedly and your Extract is now in an ABENDED status, follow these steps to diagnose the root cause: OGG-02028 - Oracle GoldenGate Capture for Oracle
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:
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: This message indicates that an Oracle GoldenGate (OGG)
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
In Oracle GoldenGate (OGG), the message "OGG capture client successfully detached from GoldenGate capture" typically signifies a normal state transition or the graceful termination of an Integrated Capture (Integrated Extract) process. Understanding the Component
Integrated Capture differs from the traditional "Classic Capture" by interacting with a LogMiner server inside the Oracle database rather than reading redo logs directly.
Capture Client: This refers to the OGG Extract process itself.
GoldenGate Capture: This is the LogMiner server (the mining engine) residing within the database. What the "Detached" Message Means
This message is an informational update indicating that the communication link between the OGG Extract process and the database-level mining server has been severed.
Normal Termination: If you manually stop the Extract (STOP EXTRACT ), this message confirms that the client has disconnected cleanly from the database resources.
Abnormal Termination (Abend): If the process crashes due to an error (e.g., OGG-01668 for missing transaction info), the client will "detach" as the process shuts down.
Status Check: If you see "Detached" as a status in the database views (like DBA_CAPTURE), it means the Capture process is currently stopped and needs to be restarted from the Oracle GoldenGate Command Interface (GGSCI). Troubleshooting Checklist due to a scheduled maintenance window
If the detachment was unexpected, investigate the following: OGG-02028 - Oracle GoldenGate Capture for Oracle
The message "OGG Capture client successfully detached from GoldenGate Capture" is a standard informational log entry in Oracle GoldenGate, typically appearing when an Integrated Extract process stops or restarts. It indicates that the Extract client has cleanly disconnected from the database's LogMiner server. Context and Meaning
This message is most frequently seen in the following scenarios:
Graceful Shutdown: When a user issues a STOP EXTRACT command, the process finishes its current task and detaches from the database capture service.
Process Abend: 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.
LogMiner Session Cleanup: In Integrated Capture mode, the database manages a "capture" process (OGG$CAP_...) while the OGG Extract acts as a "client." This log confirms the client-server link has been severed. Troubleshooting
While the detachment message itself is informational, it often precedes or follows an actual error. If your Extract is not staying in a RUNNING state, check these common related issues:
Check for Preceding Errors: Review the GoldenGate event log (VIEW GGSEVT) or the Extract report file (VIEW REPORT ) for errors like ORA-03113 (End-of-file on communication channel) which may have triggered the detachment.
Database Session Issues: Investigating the database alert log is critical. If the detachment was unexpected, it may be due to a crashed database session or a LogMiner server that started and stopped too quickly.
Environment Variables: Ensure ORACLE_HOME and your PATH are correctly set to match the database version. Version mismatches between the OGG build and the Oracle binary can cause abrupt disconnections.
Resource Limits: In Integrated mode, ensure the STREAMS_POOL_SIZE is adequately sized, as the capture process consumes memory from this pool.
If the process continues to abend after detachment, you may need to unregister and re-register the Extract with the database to reset the capture session. OGG-02028 - Oracle GoldenGate Capture for Oracle
In Oracle Integrated Capture mode, if the Extract is idle for an extended period (defined by database resource manager settings), the database server may detach the client session to free up resources. While the Extract process remains running on the OS level, the database session is detached. OGG will typically attempt to re-attach automatically when new data arrives.