Successful detachment is critical. If the client fails to detach (e.g., during a crash), the database may continue to hold archive logs, leading to RMAN-08137 errors because the database believes the logs are still needed by a downstream process.
If this message occurred during an unexpected crash, follow these steps to isolate the root cause: Step 1: Check the Extract Report File
Ensure the Oracle Streams Pool has sufficient memory allocated via STREAMS_POOL_SIZE to prevent forced database evictions.
When this detachment occurs unexpectedly, follow these steps to isolate and resolve the issue. Step 1: Check the GoldenGate Report File Successful detachment is critical
In specific GoldenGate configurations, if there is a prolonged period of absolute inactivity (no transactions occurring in the source database), the client and server may temporarily suspend or cycle their connection to save system resources, resulting in a detachment followed by a re-attachment when new transaction volume resumes. D. Database Maintenance or Rolling Upgrades
“If this is the case go grab your network admin, could be a firewall thing then... your communication link basically dropped out.” Oracle Forums · 9 years ago Comparison of Capture Methods Classic Capture Integrated Capture Directly from redo/archive logs Interacts with logmining server Detachment Local file system disconnect Client-server detachment from DB Complexity Simple, but restricted data types High integration, supports RAC/ASM/TDE Root Cause for Database Shutdown - Oracle Forums
Configure the GoldenGate Manager process to automatically restart Extracts that detach due to transient network or database hiccups. Add the following to your mgr.prm file: When this detachment occurs unexpectedly, follow these steps
When an administrator issues the command to gracefully stop an Extract process, the client must unregister its active session from the database mining server. GGSCI> stop extract EXTNAMES Use code with caution.
Or, if removing permanently, delete the capture client.
The Extract process has stopped reading data from the database mining server and has severed the programmatic connection. Common Triggers for Detachment Database Maintenance or Rolling Upgrades “If this is
In Oracle GoldenGate (OGG) environments using , stability is paramount. A common, yet often critical, alert that administrators encounter is the message indicating that the Integrated Capture client has detached from the GoldenGate capture process.
Sometimes, a DDL (Data Definition Language) operation is captured, but due to a configuration setting or filter, the Extract needs to ignore it. To do this cleanly, it detaches from the capture session to reset the state.
: 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
The "OGG capture client successfully detached" message is often a symptom, not the root cause. It usually signifies that the background database connection has died unexpectedly. 1. Oracle Database Session Crash (ORA-03113)