What (like ORA- or OGG-) appear right before this message in your ggserr.log or database alert log?
Compare lag before and after the detachment. Reattachment should take < 2 seconds. If longer, check database load.
When you restart an Extract, it must first shut down the old session. You will see a "detached" message for the stopping process, followed shortly by a "bound" or "attached" message for the new process. 3. Network or Timeout Issues
The Extract encounters an error after a specific transaction fetch, causing it to initiate a clean exit. Step-by-Step Diagnostic Workflow
Use the following query to see how long reattachment takes: What (like ORA- or OGG-) appear right before
When this message appears, especially in a production environment, your immediate concern is whether the Extract client reattached or remains detached. A prolonged detached state will cause replication lag as LCRs accumulate in the LogMining server queue but are not being written to the trail.
This message is most frequently seen in the following scenarios:
Recommendation: Ensure STREAMS_POOL_SIZE is explicitly set and has enough headroom (minimum 1GB to 2GB per Integrated Extract thread). Step 4: Examine Database Mining Views
Use grep or less on the Extract report file ( .rpt ). Look for: If longer, check database load
To help troubleshoot this specific issue on your system, let me know:
The process reached a specified end point (e.g., THREAD or EOF ) and closed safely. 🛠️ Related GGSCI Commands
Think of this message as a "Goodbye" handshake. It confirms the database has successfully cleaned up after a GoldenGate process. If the stop was intentional, the message is proof of a healthy system. If it was unintentional, it serves as the timestamp for when your replication halted, guiding you to look deeper into the Extract’s specific error logs. database alert logs
To help find the exact cause of your Extract stopping, could you share the listed right before this message? If you noticed any recent database changes or high system workloads , sharing those details would also help narrow it down. Share public link STATS EXTRACT <
Every 15 minutes, the extract stops and restarts. Log shows "successfully detached" followed by "starting extract" . Analysis: A cron job was running STOP EXTRACT ext1 and START EXTRACT ext1 incorrectly. Resolution: Removed the cron job.
Open the GoldenGate home directory and inspect the ggserr.log file, or use the GoldenGate command line: VIEW GGSEVT Use code with caution.
ggsci> STATS EXTRACT <extract_name>, TOTAL
SELECT capture_name, state, status FROM v$goldengate_capture; Use code with caution.