Last updated on AUGUST 07, 2017
Applies to:Management Pack for Oracle GoldenGate - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
The JAGENT is running, but the following errors are captured in the jagent logs:
[2016-02-17T15:29:43.106+04:00] [JAGENT] [NOTIFICATION] [OGGMON-20288][com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid:
getInstanceList] [ecid: 0000LBizZI9A9TBprWo2yY1Ml5aW000003,0] Jagent Mode:Monitor-Integrated
[2016-02-17T15:29:43.788+04:00] [JAGENT] [NOTIFICATION] [com.goldengate.monitor.jagent.config.impl.CmDelegateImpl] [tid:
agentRegistration] [ecid: 0000LBizZTgA9TBprWo2yY1Ml5aW000004,0] Closing client connection after registration ==
[2016-02-17T15:29:43.802+04:00] [JAGENT] [ERROR] [OGGMON-20269][com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid:
agentRegistration] [ecid: 0000LBizZTgA9TBprWo2yY1Ml5aW000004,0] com.goldengate.monitor.MonitorRuntimeException: Could not decrypt Agent JMX
Monitor Server 12.2.1 has also been installed and is running. We are able to login to the Monitor Server Web UI and discover the GoldenGate target, but the GoldenGate process is displayed as grayed out. A screen shot will be attched along with the jagent logs, Monitor Server logs and properties files.
Tried reseting the wallet password to no avail.
Monitor Agent (JAGENT) 184.108.40.206 was installed and configured according to the documentation:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms