Ogg Capture — Client Successfully Detached From Goldengate Capture ((new))

OGG Capture Client Detachment Confirmation

The Oracle GoldenGate (OGG) capture client has been successfully detached from the GoldenGate capture process.

What does this mean?

This message indicates that the OGG capture client, which is responsible for capturing data changes from a source database, has been cleanly separated from the GoldenGate capture process. This detachment is a normal operation that can occur for various reasons, such as maintenance, troubleshooting, or configuration changes.

Implications

The successful detachment of the OGG capture client from the GoldenGate capture process implies that:

1. No further data changes will be captured: The capture client will no longer receive data changes from the source database.
2. Data replication will be paused: Any ongoing data replication processes will be paused until the capture client is reattached or reconfigured.

Next Steps

To resume data replication, you may need to:

1. Verify the detachment reason: Check the system logs and configuration files to understand why the detachment occurred.
2. Reattach the capture client: If necessary, reattach the capture client to the GoldenGate capture process.
3. Reconfigure the capture client: If required, reconfigure the capture client to ensure proper data replication.

Troubleshooting Tips

If you encounter issues during or after the detachment, refer to the Oracle GoldenGate documentation and troubleshooting guides for assistance.

By confirming the successful detachment of the OGG capture client, you can ensure that your data replication processes are properly managed and resumed if necessary.

What Does “Detaching a Capture Client” Mean?

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.

This is common in:

• Microservices architecture where a capture process runs independently.
• Upgrading or patching OGG components.
• Reconfiguring capture parameters without full downtime.
• Troubleshooting a stuck or misbehaving client.

6. How to Respond

| Situation | Action | |-----------|--------| | Planned stop | No action needed. | | Unexpected detach | Review logs before the message. Restart Extract if needed. | | Recurring detach | Check network stability, disk space, and system load. | | During troubleshooting | Ignore if followed by a restart or graceful shutdown. |

Case C: The Overzealous Script (Human Error)

Symptom: Every 15 minutes, the extract stops and restarts. Log shows "successfully detached" followed by "starting extract".
Analysis: A cron job was running STOP EXTRACT ext1 and START EXTRACT ext1 incorrectly.
Resolution: Removed the cron job.

1. What Does This Message Mean?

To understand the message, we must first understand the architecture of a GoldenGate Capture process (Extract).