If this message appears unexpectedly while the Extract should be running, it indicates an abnormal termination . The detachment is a , not the cause. You should investigate: Extract Abends: $GG_HOME/dirrpt/ .rpt
This message indicates that a downstream extraction process—typically an Integrated Extract—has disconnected from its logmining server component inside the source database. It confirms a clean shutdown or suspension of the capture activity, meaning the detachment happened gracefully without corrupting the process state. Core Architecture: Why Detachment Happens If this message appears unexpectedly while the Extract
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 It confirms a clean shutdown or suspension of
The message indicates a break in the link between the GoldenGate Extract and the Oracle database. While it is a alarming message, it is usually resolved by identifying the root cause of the session crash in the database alert logs and restarting the Extract process. Ensuring your database and GoldenGate versions are up-to-date with the latest patches is the best preventative measure against these types of detachments. a memory exhaustion issue (SGA/Streams Pool)
| Client Status | Interpretation | | :--- | :--- | | | The Log Mining Server is running and actively connected to the Extract client. This is the normal operational state for an active Extract process. | | DETACHED | The Log Mining Server is still running, but no Extract client is currently attached. This is the state the log message describes. | | DISABLED | The Log Mining Server itself is not running. | | ABORTED | The Log Mining Server encountered a fatal error and stopped. |