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.
In the high-stakes world of real-time data replication, Oracle GoldenGate (OGG) stands as a titan. It powers mission-critical operations like zero-downtime migrations, high-availability setups, and real-time analytics. For administrators managing these environments, the GoldenGate log files are the central nervous system, providing a constant stream of status updates, warnings, and informational messages. This is where the message becomes misleading
If the process crashes due to an error (e.g., OGG-01668 for missing transaction info), the client will "detach" as the process shuts down. If the detachment was temporary (e
If the detachment was temporary (e.g., a restart), look for the corresponding "Capture client successfully attached" message immediately following the detachment in the Report file. If the detachment was temporary (e.g.
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.