Ogg Capture — Client Successfully Detached From Goldengate Capture [top]

You will see a command like STOP EXTRACT executed right before this entry. 2. Graceful Shutdown Due to EOT (End of Trail)

This is entirely normal. You will always see this message when you manually stop a running Integrated Extract.

server, which mines redo logs for the Extract, has successfully closed its session with the OGG client. Oracle Forums Integrated Architecture

A: First, stop the Extract with STOP EXTRACT <group> . Then, unregister it from the database with UNREGISTER EXTRACT <group> DATABASE before deleting it with DELETE EXTRACT <group> . You will see a command like STOP EXTRACT

If you’ve ever seen the message Capture client successfully detached from GoldenGate capture and wondered if you did it right – now you know. Yes, you did.

For database administrators (DBAs) and Oracle GoldenGate (OGG) engineers, the log files are the pulse of the replication environment. While most log entries are routine, some, like the status message "OGG capture client successfully detached from GoldenGate capture," often trigger a mix of confusion and concern.

command or a graceful system shutdown. It indicates that the You will always see this message when you

The message "OGG capture client successfully detached from GoldenGate capture" is rarely a problem by itself. In most cases, it is a sign of a well-behaved client-server disconnection during a normal stop, idle timeout, or transient database operation.

For Integrated Capture, relying entirely on Automatic Memory Management (AMM) can sometimes result in laggy allocations. It is best practice to set a minimum floor for the Streams Pool. ALTER SYSTEM SET STREAMS_POOL_SIZE = 2G SCOPE=BOTH; Use code with caution.

component within the Oracle Database. In an Integrated Capture setup, the GoldenGate Extract process doesn't read the redo logs directly; instead, it acts as a client to a database-level "Capture Server." Then, unregister it from the database with UNREGISTER

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.

SELECT capture_name, status, error_number, error_message FROM dba_capture; Use code with caution.

If you want to reattach later:

Unlike Classic Capture, which reads online redo logs directly from the file system, Integrated Capture leverages the database logmining server. The architecture consists of two main parts: