Ogg Capture Client Successfully Detached From Goldengate Capture |best| Now
Never troubleshoot this message in isolation. Always review the surrounding log context, the status of the database capture process, and the network stability. When in doubt, treat it as an informational message, but let your monitoring systems alert on the behavior after the detachment, not the detachment itself.
Scenario 2: It is immediately preceded or followed by an ABEND message.
[ Oracle Database / LogMiner Server ] │ ▲ (Detachment happens here) │ [ OGG Capture Client (Extract) ] │ ▼ [ Trail Files ]
Essentially, the message confirms that the GoldenGate Extract process has stopped interacting with the database logmining server, and the database has acknowledged this separation. 2. Common Scenarios That Trigger This Message
SELECT CAPTURE_NAME, STATUS, ERROR FROM DBA_CAPTURE; Never troubleshoot this message in isolation
Unlike Classic Capture, which directly reads online redo logs at the OS level, Integrated Capture leverages the database logmining infrastructure. The architecture splits the workload into two primary components:
In Oracle GoldenGate (OGG) integrated capture deployments, the Capture Client
DBA sees "successfully detached" every night at 2 AM. Analysis: A maintenance window runs index rebuilds, causing massive redo generation. The database’s capture process dynamically rebalances and briefly detaches clients. Resolution: No action. Changed log level from INFO to WARNING for this specific event.
The database trace log only tells you that the client detached, not why . Open the GoldenGate report file to see what the Extract was doing right before the split. view report Use code with caution. Scenario 2: It is immediately preceded or followed
This article provides a deep dive into what this message means, the scenarios in which it appears (including graceful shutdowns, network timeouts, and parameter misconfigurations), and how to determine whether it represents normal operations or a hidden problem.
If the GoldenGate Extract client is running on a different machine than the database engine (Downstream Deployment), ensure a high-bandwidth, low-latency network connection exists between the systems to prevent network-induced client detachments.
Is this happening on a or in a downstream deployment configuration? Share public link
What is the current configuration of your database? Share public link INFO EXTRACT <
To minimize unexpected client detachments and ensure smooth replication performance, implement the following operational best practices:
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
ggsci> INFO EXTRACT <extract_name>
: You manually issued a STOP EXTRACT command in GGSCI to perform maintenance or update parameters.
This is where the message becomes misleading. If the database’s internal Capture process dies, crashes, or is killed (e.g., ALTER SYSTEM KILL SESSION ), the OGG client will also log "successfully detached" — even though the detachment was not initiated by the client.