Ogg Capture Client Successfully Detached From Goldengate Capture Guide

A: "Attached" occurs when you start an extract. It establishes the connection to the LogMining server. "Detached" is the inverse – the clean termination.

The "detach" message is the final step in a controlled shutdown of this client-server relationship. Let's break down the exact log entry. A: "Attached" occurs when you start an extract

This is healthy behavior for a controlled environment shutdown. Scenario 3: End of a Batch Processing Window In some architectures (e.g., batch-oriented replication), an extract might be configured to run for a specific duration or stop after processing a specific log sequence number (e.g., USING LOGFILE or END parameter). When the extract reaches its defined endpoint, it self-initiates a detach. The "detach" message is the final step in

2025-05-23 14:00:01 ERROR OGG-02717 Unable to allocate LogMiner session. 2025-05-23 14:00:01 INFO OGG-06408 OGG capture client successfully detached... Here, the detach is . The primary issue is the LogMiner allocation failure. The detach is just the cleanup response. Common Related Errors Guiding the Detach | Error | Meaning | DBA Action | | --------------------------------- | ------------------------------------------------- | ---------------------------------------------------------------------- | | OGG-02912 (Insufficient SGA) | Database’s streams_pool_size too small. | Increase streams_pool_size or sga_target . Restart extract. | | OGG-02902 (Timeout) | LogMiner server didn’t respond. | Check database alert log for bottlenecks or deadlocks. | | OGG-06439 (No capture resources) | Too many concurrent LogMining servers. | Stop other extracts or increase MAX_SERVERS in the database config. | Scenario 3: End of a Batch Processing Window