In , 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).
What and GoldenGate version are you running? Share public link
You see "Stopping Extract," followed by "Successfully detached," followed by the process status showing as STOPPED . Reason: This is a standard clean shutdown. Situation B: Critical (Action Required)
In conclusion, OGG Capture client detachment from GoldenGate Capture can cause significant issues with data replication. By understanding the causes of detachment, troubleshooting symptoms, and following best practices, organizations can prevent and resolve detachment issues, ensuring that data replication is continuous and accurate.
Normal, if part of a scheduled job.
If you see a detach message that you didn’t initiate, you need to check the lines immediately above and below it.
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.
: When a user issues a STOP EXTRACT command, the process finishes its current task and detaches from the database capture service.
GGSCI> DETACH EXTRACT <extract_name>
Essentially, the database is acknowledging that the GoldenGate process has stopped requesting data and the session has been closed cleanly. Common Scenarios Where This Occurs
If you are dealing with a live issue, I can help you fix it if you let me know: Is the Extract currently in an or STOPPED state?
While less common, network interruptions can cause an involuntary, yet successful, detachment. The Extract process may decide to gracefully terminate its connection due to upstream network timeouts, rather than waiting indefinitely and eventually abending.
| | Symptoms & Log Evidence | Resolution Steps | | :--- | :--- | :--- | | Network Instability | Repeated OGG-01676, connection timeouts. Intermittent detachment and reattachment. | 1. Verify network stability between the GoldenGate server and the database host. Check for firewalls, VPN drops, or switch issues. 2. Increase GoldenGate's TCP keepalive settings in the GLOBALS file. | | Extract Process Termination | Extract in ABENDED state. OGG-01194 with an Oracle error. | 1. Review the Extract parameter file for errors. 2. Ensure the user in the DELOGIN command has all required privileges ( EXECUTE on DBMS_FLASHBACK , SELECT on V$DATABASE , etc.). 3. Attempt to START EXTRACT <name> . If it fails again, you may need to ALTER EXTRACT <name> ... BEGIN NOW if data re-sync is feasible or consult Oracle support. | | Database LogMiner Session Hang | Capture process is stuck in BUSY state. Lag increases without Extract failing. | 1. In the database, find the SID of the hung LogMiner session. 2. Terminate it: ALTER SYSTEM KILL SESSION '<sid>,<serial>' IMMEDIATE . GoldenGate will start a fresh mining session on next restart. | | Improper Environment Configuration | Extract fails to start after a reboot. Detach occurs immediately on start. | 1. Verify the bequeath_detach parameter. For bequeath connections, your sqlnet.ora must contain bequeath_detach=true . 2. Re-add the extract: DELETE EXTRACT <name> , then ADD EXTRACT <name> INTEGRATED TRANLOG, BEGIN NOW . 3. Re-register with the database: REGISTER EXTRACT <name> DATABASE . | In , GoldenGate leverages the database engine
If your Extract is abending (crashing) with this message, follow these steps:
However, for a GoldenGate administrator, seeing this message can sometimes be a double-edged sword. While it indicates a successful detachment, the event's unplanned occurrence could point to underlying system issues. Therefore, it's critical to not only know what this message means but also to quickly determine why it happened and how to resolve any resulting replication lag or process failures. This article provides a deep dive into this specific event, covering the architecture behind it, the scenarios that trigger it, and a step-by-step guide to troubleshooting and resolution.
When you see the message that the client has detached (often accompanied by OGG-02028 or ORA-03113 errors), it means that the , but the disconnection was not necessarily a clean, intended shutdown.
Replication lag grows to hours. Log shows detachment but no errors. Analysis: The OGG client detached due to idle timeout, but a network ACL change blocked the reattachment socket. OGG waited forever for a connection that never returned. Resolution: Set TRANLOGOPTIONS INTEGRATEDPARAMS (MAXCONNECTIONS 5) and IDLETIMEOUT 15 . Also fixed firewall rules. What and GoldenGate version are you running