My Oracle Support Banner

OEM shows incorrect status/ Jagent reports false OGG status/ MGR hangs with ENABLEMONITORING enabled (Doc ID 2275696.1)

Last updated on JUNE 05, 2019

Applies to:

Management Pack for Oracle GoldenGate - Version and later
Information in this document applies to any platform.


Several issues were seen with Monitoring enabled

1) OGG MGR hangs and

ggrepo.threads.failchk | 2017-01/12 00:30:02.637 ggrepo.threads.failchk|WARN
| 1058 ggrepo/PersistenceBDB.cp | Calling Environment fail check
ggrepo.threads.failchk | 2017-01/12 00:30:02.637
ggrepo.threads.failchk|ERROR| 1350 ggrepo/PersistenceBDB.cp | Error (dirbdb):
BDB0113 Thread/process 97443/97483 failed: BDB1507 Thread died in Berkeley DB

2)  Jagent reports false status

[2016-12-13T12:01:22.544-08:00] [JAGENT] [NOTIFICATION] [OGGMON-20405] [] [tid: StatusCollector] [ecid: 0000LZeAnmj2NQt5Gfs1yf1OJ5J9000003,0] Load pseudo Objects for Process Name:RBSPRD1 and Status Code:8

3) OEM shows wrong status although OGG runs fine

goldengate.jar debug script shows following when querying mgr/webservices
Download Webservice(registry, mpoints, messages/last) results Yes(1) No(2)
[1] :Enter Manager host [psin10p582] :Enter Manager port [7089] :Manager host
= psin10p582
Manager port = 7891
registry Webservice output from MGR(7891)
**** Unable to Access Registry webservice. Please check Manager is UP and running


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.