Successfully detaching an OGG capture client is straightforward when you follow the correct sequence: . It’s a powerful tool for maintenance, troubleshooting, and reconfiguration without a full pipeline tear-down.
The actual GoldenGate Extract operating system process (e.g., extract or ext1 ). This process acts as a client that attaches to the database-side logmining server to pull the pre-filtered LCRs and write them to the local GoldenGate trail files. 2. Deciphering the Message This process acts as a client that attaches
A detachment can be a completely normal operational event, or it can be the symptom of an underlying database crash. Here are the most frequent causes: 1. Routine Administrator Actions Here are the most frequent causes: 1
Look for Attachment Status: DETACHED or Client: NONE . The mining server cannot proceed
If a DBA or a backup script accidentally deletes an archive log required by the capture server, the database throws an error, usually ORA-01292: LogMiner for upstream capture cannot find the log file . The mining server cannot proceed, so it detaches from the OGG client and aborts. This results in the detachment message being followed by an OGG abend.
The database is shutting down, and OGG processes are detaching to preserve state. Automated Restarts: