Getting Fake Email Alerts From OEM 13c For GoldenGate Targets
(Doc ID 2626544.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle GoldenGate - Version 12.3.0.1.3 and laterManagement Pack for Oracle GoldenGate - Version 11.2.1.0.0 and later
Information in this document applies to any platform.
Symptoms
Using GoldenGate 18.1.x "targets" registered with OEM 13c/GoldenGate Plugin 13.2.x for OEM see one or more of the following symptoms:
- GoldenGate targets show wrong process status in OEM 13c console
- GoldenGate targets show wrong and/or old/stale metric data/information in OEM 13c console
- OEM 13c email alerts send email regarding GoldenGate targets being down when they are really up.
- GoldenGate targets show wrong and/or old/stale metric data/information in OEM 13c console
- OEM 13c email alerts send email regarding GoldenGate targets being down when they are really up.
- $OGGMON_AGENT_INSTANCE_HOME/ogg_agent.log show errors like:
[JAGENT] [ERROR] [OGGMON-20497] [com.goldengate.monitor.jagent.comm.ws.NotificationsCollector] [tid: StatusCollector] [ecid: 0000MjQ4VPx2zGjSD2Zf4w1T9MJD000004,0] Failed to get Status Information. RESTful Web Service might not be available.
[JAGENT] [ERROR] [OGGMON-20603] [com.goldengate.monitor.jagent.comm.ws.ManagerService] [tid: quickUpdates] [ecid: 0000MnBsq4k6ESBxnWedKZ1TJrlS00000K,0] OGG Core RESTful Web Service
with name mpoints has become unresponsive, javax.xml.ws.WebServiceException:
- $OGG_HOME/pmsrvr.log shows errors like:
2019-07-11T20:18:24.729-0500 WARN | Database 'registry.db': Next operation failed - BDB0068 DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock
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 |