In OGG, a capture client (e.g., an OGG Extract process or a microservices-based capture component) is typically attached to a log mining or change capture mechanism. Detaching means disconnecting the client from the underlying capture source (e.g., Redo Logs, integrated capture in Oracle DB, or a trail file reader) without necessarily stopping the capture engine itself.
If the detachment was unexpected, investigate the following: OGG-02028 - Oracle GoldenGate Capture for Oracle In OGG, a capture client (e
A: Almost never. A "successful" detach requires a final checkpoint. However, if you force-killed the extract, you wouldn’t see this message – you’d see an OGG error instead. A "successful" detach requires a final checkpoint
(the GoldenGate Extract process) interacts directly with a database-level server (the LogMiner / GoldenGate Capture server ). The message The message The short answer: However, understanding why
The short answer: However, understanding why this message appears, when it appears, and what it implies about your replication architecture is crucial to maintaining a healthy OGG environment.
In Oracle Integrated Capture mode, if the Extract is idle for an extended period (defined by database resource manager settings), the database server may detach the client session to free up resources. While the Extract process remains running on the OS level, the database session is detached. OGG will typically attempt to re-attach automatically when new data arrives.
In an Oracle database, the GoldenGate capture is handled by a background process (often part of the Streams or LogMiner pool) that reads the online and archived redo logs. The Capture Client (Extract): This is the GoldenGate process ( extract.exe