| Pitfall | Solution | |---------|----------| | Detaching while transactions are open | Stop client gracefully first | | Forgetting to reattach | Document maintenance windows | | No backup of checkpoint | Use INFO CAPTURE ... SHOWCHECKPOINTS before detach | | Microservices: orphaned clients | Use DELETE CAPTURE if reattach fails |
When this event occurs, you will typically see a sequence of messages in the GoldenGate ggserr.log or the Extract's report file ( ). A healthy, successful detachment looks like this: Stop Signal Received: STOP request handled for Extract . State Save:
A common scenario that database administrators and data engineers encounter is finding that the OGG Extract process has stopped, with the alert log showing the message: .
SELECT capture_name, status, error_number, error_message FROM dba_capture; Use code with caution. | Pitfall | Solution | |---------|----------| | Detaching
If your integrated capture has detached and stopped, follow these steps to diagnose and remediate the issue. Step 1: Check the Extract Report and Alert Log
The source database often has more information. Look for ORA-errors (like ORA-01341: LogMiner out of memory ) occurring at the exact same timestamp.
To ensure that your capture clients detach and attach smoothly without disrupting your business-critical data pipelines, consider the following best practices: State Save: A common scenario that database administrators
From the database's perspective, when a GoldenGate Extract client is up and running, the capture process is marked as . Conversely, if the Extract client stops normally (e.g., via STOP EXTRACT in GGSCI), the capture process remains active but enters a DETACHED state. This is an important and often-misunderstood nuance: the detachment itself is usually normal . The capture process continues to mine the logs and hold the position, waiting for the Extract client to reattach and resume reading.
Connect to the source database as a DBA and query the DBA_CAPTURE view:
SELECT component, current_size/1024/1024 AS size_mb FROM v$sga_dynamic_components WHERE component = 'streams pool'; Use code with caution. Step 1: Check the Extract Report and Alert
While it says "successfully detached," it is usually the result of an abrupt termination. Key causes include: 1. Database Session Crash (ORA-03113)
To understand the ogg capture client successfully detached message, we first need to demystify how Oracle GoldenGate captures data changes. In modern, integrated capture setups (the standard for Oracle 12c and later), the extraction process is split into two components that work closely together:
Look for Attachment Status: DETACHED or Client: NONE .