Ogg Capture Client Success[top] Fully Detached From Goldengate Capture

| Capture Type | Log Entry Equivalent | Behavior on Shutdown | | :--- | :--- | :--- | | | OGG capture client successfully detached | Explicit handshake with DB | | Classic (Redo logs) | Stopping Extract ... Log read checkpoint file | Simply closes log file handles; no DB detachment | | Microservices (Distributed) | Service state changed from RUNNING to STOPPED | Detaches from the Administration Server but not database directly |

View the full report for specific errors by running VIEW REPORT . | Capture Type | Log Entry Equivalent |

Run STATUS EXTRACT in GGSCI to see if it is STOPPED or ABENDED . Conversely, if the Extract crashes or the OS

Conversely, if the Extract crashes or the OS kills the process (an "abend"), you will see this message. You will see an error like ERROR OGG-00446 followed by cleanup procedures. The absence of the "successfully detached" message during a crash is expected but indicates that the database might hold lingering session states. The message confirms no open, unresolved transactions were

The message confirms no open, unresolved transactions were left in the "prepared" state with the database. It is a stamp of approval for data safety.