[OGGMON-20269] Could not decrypt Agent JMX Password (Doc ID 2109022.1)

Last updated on JANUARY 04, 2021

Applies to:

Symptoms

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: 0000abcdefg000003,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: 0000abcdefg000004,0] Closing client connection after registration ==
ClientConnectionImpl(com.goldengate.monitor.jagent.client.MonitorJmxConnection Info@abcd)

[2016-02-17T15:29:43.802+04:00] [JAGENT] [ERROR] [OGGMON-20269][com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid:
agentRegistration] [ecid: 0000abcdefg000004,0] com.goldengate.monitor.MonitorRuntimeException: Could not decrypt Agent JMX
Password (<password>=)[[

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. 

Changes

 Monitor Agent (JAGENT) 12.2.1.0 was installed and configured according to the documentation:

https://docs.oracle.com/goldengate/m1221/gg-monitor/GGAIN/GGAIN.pdf

Cause

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