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.
The report contains detailed logs from the process's last run cycle, including any warnings about log files or permission issues.
Or, from the command line, use:
It indicates that a (e.g., a downstream mining, logdump, or custom application) has cleanly disconnected from the GoldenGate Capture process (e.g., Extract in classic or integrated capture mode, or the Local Capture in Microservices).
A: This is possible. The message indicates a past successful detachment event. If the Extract has restarted and reattached since then, it will be running, but the historical log entry will remain. Check the timestamps in your log files. While less common, network interruptions can cause an
If it transitions back to a RUNNING state and begins checkpointing, the detachment was likely a transient issue.
Detachment command varies by deployment type: Or, from the command line, use: It indicates that a (e
Log output:
Because Integrated Extract relies on database background processes (like MS00 or LOGMNR ), the root cause is often recorded inside the Oracle Database, not GoldenGate. Open the Oracle Database alert.log . Search for timestamps matching the GoldenGate detachment. If the Extract has restarted and reattached since
This implies the detachment was involuntary. Something—like a database crash, a memory exhaustion issue (SGA/Streams Pool), or a permissions change—forced the client off. Troubleshooting Forced Detachments
If your Extract is abending (crashing) with this message, follow these steps: