A: Yes, absolutely. Filter on severity: Info level. Alert only on ERROR or WARNING . But log retention of these "detach" events helps when auditing change windows.
The message "OGG capture client successfully detached from GoldenGate capture"
2021-06-06 07:54:22 ERROR OGG-02028 Failed to attach to logmining server 2021-06-06 07:54:22 ERROR OGG-01668 PROCESS ABENDING 2021-06-06 07:54:22 INFO OGG Capture client successfully detached...
In the clamorous world of database administration, where the roar of transactions never ceases and the pressure for zero downtime is a constant hum, rare is the moment of genuine tranquility. We chase uptime percentages, wrestle with data drift, and monitor replication lag like a heartbeat. Yet, occasionally, the log file offers a message that transcends mere status update. It reads: OGG Capture Client successfully detached from Goldengate capture . A: Yes, absolutely
A single massive transaction can cause the capture client to struggle. Use SEND EXTRACT , SHOWTRANS to see if a specific transaction is causing a bottleneck.
A: This indicates a mis-timestamped log or a zombie process. In normal cases, a detached client = stopped process. Use kill -3 on the process ID to verify.
Network blips can cause temporary detachments. Configure the GoldenGate Manager process to automatically restart the Extract after a brief delay: AUTORESTART ER *, RETRIES 3, WAITMINUTES 2, RESETMINUTES 60 Use code with caution. But log retention of these "detach" events helps
In an environment, the Extract process does not read redo logs directly; instead, it "attaches" to a Logmining Server within the Oracle database. This "detached" message typically appears in the database alert logs when the Extract stops normally or is manually shut down using the STOP EXTRACT command. Common Scenarios
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
If the detach occurs (e.g., capture stops mid-run): We chase uptime percentages, wrestle with data drift,
Closely examine the Checkpoint Lag and the Recovery Checkpoint . If the lag is constantly growing, the Extract may be effectively "stuck" despite being in a DETACHED state.
The successful detachment of the OGG capture client from the GoldenGate capture process implies that:
The database STREAMS_POOL_SIZE was insufficient, causing the database side of the capture process to terminate. Troubleshooting Step-by-Step