When this detachment occurs unexpectedly, follow these steps to isolate and resolve the issue. Step 1: Check the GoldenGate Report File

Integrated Capture relies heavily on the Oracle Shared Pool, specifically the Streams Pool. If the Streams Pool ( STREAMS_POOL_SIZE ) runs out of memory, the database logmining server will crash or force-kill the client connection, leading to an abrupt detachment. 3. Database Instance Failure or Switchover

A background process running inside the Oracle Database instance. It utilizes the database LogMiner engine to mine the redo logs, filter the changes, and stage logical change records (LCRs) in the database Streams Pool memory.

The most common reason for a successful detachment is intentional maintenance. If an administrator issues a STOP EXTRACT command in GGSCI or the Admin Client, the Extract process gracefully winds down. It notifies the database logmining server that it is leaving, resulting in a successful detachment log entry. 2. Database Shutdown or Restart