Extract Did Not Abend When Node Was Down
(Doc ID 2703099.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle GoldenGate - Version 19.1.0.0.4 and laterInformation in this document applies to any platform.
Integrated extract is running on a local node, while connected to logminer at a remote node.
Logminer failed but the extract was not aware the logminer connection was lost. As such the extract did not fail and continued to run although logminer was not sending data.
The purpose of this note is to describe how to notify the extract that logminer is not sending data and force the extract to abend.
Symptoms
Problem Summary
---------------------------------------------------
Extract did not abend when logminer failed on remote node .
Extract was running on a local node (node1) and connected to a remote node (node 2). When node2 failed the extract did not abend or error out.
Below is the description of the issue
1.Extract EXT01 stuck
2.On checking we found node2 to which EXT01 extract connected had crashed.
3.EXT01 extract did not abend or error when the db on node2 crashed.
OGG environment:
------
DB01 database is 4 Node RAC
19c DB and 19c OGG.
OGG processes are running on Node1 at OS level.
EXT01 Integrated extract is connected to instance-2 as ggadm@<connect string>
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |