In all these cases, you will see the line after the failure, acting as a confirmation that the client gave up and disconnected cleanly. Part 6: Best Practices for Managing Integrated Extracts To ensure that "detached" always remains a benign message and never a sign of a forced disconnect, follow these best practices: 1. Use Graceful Stop Commands Always use STOP EXTRACT <name> (without ! or ABORT ). Aborting an extract bypasses the graceful detach and can leave orphaned LogMining sessions on the database.
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. | In all these cases, you will see the
-- In the database: SELECT * FROM V$LOGMNR_PROCESSES; If a mining server exists for an extract that is no longer running, remove it: or ABORT )
One message that frequently appears in these logs—often causing a momentary heart palpitation for new or even intermediate DBAs—is: Is this a symptom of failure? A hidden warning? Or just noise? In all these cases
Bad: STOP EXTRACT * ABORT (if used on a single extract unnecessarily). Good: STOP EXTRACT ext_sales . After a detach, confirm the restart position:
INFO EXTRACT ext_sales, DETAIL Look for Current Checkpoint – it should be recent relative to the stop time. If an extract crashes and does not detach gracefully, you may see a database session lingering: