Ogg Capture Client Successfull ((hot))y Detached From Goldengate Capture May 2026

Integrated Capture lives in the Streams Pool. If the STREAMS_POOL_SIZE is too small, the database may kick the GoldenGate client to save system stability.

The message is, by itself, a sign of a healthy, communicative relationship between GoldenGate and the Oracle Database. It confirms that the session ended without leaving "zombie" processes or orphaned locks in the database.

If there is a brief network flicker between the GoldenGate hub and the database server, the client might detach. If GoldenGate is configured with AUTORESTART , it may reconnect so quickly that you only notice the detachment message in the logs. 4. Database Maintenance Integrated Capture lives in the Streams Pool

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

When you see the message "OGG capture client successfully detached," it indicates that the with the database’s capture engine. It confirms that the session ended without leaving

If the source database is being shut down or put into a state where the LogMiner server is no longer available, the GoldenGate client will be forced to detach. Is it an Error? How to Tell.

However, if you see this message appearing repeatedly or accompanied by an ABENDED status, it is a red flag to investigate your database’s and LogMiner health . How to Tell. However

Detachment issues are occasionally linked to bugs in the LogMiner engine. Ensure both your GoldenGate home and your Oracle Database have the latest "Database Release Update" (RU).