The documentation of Oracle GoldenGate 12.2 does not mention it explicitly: before you start running the instance make sure that you have a Java environment correct & running. If not – you may later run into some strange errors which are difficult to solve. They will happen if the Java environment is set up correctly. This article is about one of those errors.
During the first run of jagent – the instance is creating a datastore which is needed to correctly connect jagent to mgr process. If the Java environment is missing or miss configured – the datastore (dirbdb forlder) might be created improperly. Later on – even if the Java JRE is provided correctly – the datastore previously created might be still faulty and cause problems. Jagent would start without errors but would not react as intended.
Running jagent might look ok:
2017-10-15 13:13:44 INFO OGG-00987 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (oracle): start jagent. 2017-10-15 13:13:44 INFO OGG-00963 Oracle GoldenGate Manager for Oracle, mgr.prm: Command received from GGSCI on host [10.1.1.1]:43210 (START GGCMD JAGENT). 2017-10-15 13:13:44 INFO OGG-00960 Oracle GoldenGate Manager for Oracle, mgr.prm: Access granted (rule #1). 2017-10-15 13:13:44 INFO OGG-00975 Oracle GoldenGate Manager for Oracle, mgr.prm: GGCMD JAGENT starting.
You might think that jagent is up and running. It actually is. It is binded to the port. No erros appear in ggserr.log. But Enterprise Manager Cloud Control might not be able to connect to it.
To find out what is wrong you should not look at the standard OGG log/discard file. You have to look at the jagent log which is located in $JAGENT_LOCATION/logs/ogg_agent.log
If the log would contain an an error – something like:
[2017-10-15T13:27:01.108+02:00] [JAGENT] [ERROR] [] [com.goldengate.monitor.jagent.JAgentWSMain] [tid: main] [ecid: 0000LwBC1Ga8PtfLxYo2yW1PrW05000001,0] ******************************************* [2017-10-15T13:27:01.169+02:00] [JAGENT] [ERROR] [] [com.goldengate.monitor.jagent.JAgentWSMain] [tid: main] [ecid: 0000LwBC1Ga8PtfLxYo2yW1PrW05000001,0] (NON-ERROR NOTIFICATION) Monitor Agent Release Version: 12.2.1.2.170601 [2017-10-15T13:27:01.169+02:00] [JAGENT] [ERROR] [] [com.goldengate.monitor.jagent.JAgentWSMain] [tid: main] [ecid: 0000LwBC1Ga8PtfLxYo2yW1PrW05000001,0] (NON-ERROR NOTIFICATION) Build Label: OGGMON_12.2.1.2.0_PLATFORMS_RELEASE [2017-10-15T13:27:01.169+02:00] [JAGENT] [ERROR] [] [com.goldengate.monitor.jagent.JAgentWSMain] [tid: main] [ecid: 0000LwBC1Ga8PtfLxYo2yW1PrW05000001,0] ******************************************* [2017-10-15T13:27:04.815+02:00] [JAGENT] [ERROR] [OGGMON-20614] [com.goldengate.monitor.jagent.comm.ws.ManagerService] [tid: ManagerConnectionKeeper] [ecid: 0000LwBC29j8PtfLxYo2yW1PrW05000002,0] OGG Core Web Service is unavailable. java.net.SocketException: Unexpected end of file from server [2017-10-15T13:27:04.829+02:00] [JAGENT] [ERROR] [OGGMON-20614] [com.goldengate.monitor.jagent.comm.ws.ManagerService] [tid: ManagerConnectionKeeper] [ecid: 0000LwBC29j8PtfLxYo2yW1PrW05000002,0] OGG Core Web Service is unavailable. java.net.SocketException: Unexpected end of file from server [2017-10-15T13:27:04.829+02:00] [JAGENT] [ERROR] [OGGMON-20348] [com.goldengate.monitor.jagent.jmx.ManagerConnectionKeeperThread] [tid: ManagerConnectionKeeper] [ecid: 0000LwBC29j8PtfLxYo2yW1PrW05000002,0] Failed to establish a connection to the OGG Core Web Service-Host:10.1.1.1 Port:4,321. Stop all polling tasks. Wait for 0 second(s) and retry again.
The messages go into loop. It is not working.
This means that the datastore is created improperly. What you must do is to:
- stop jagent
- delete datastore
- create datastore
- start jagent
Afterwards if you look at the log you should see that this time jagent is working correctly:
[2017-10-15T19:49:13.059+02:00] [JAGENT] [ERROR] [] [com.goldengate.monitor.jagent.JAgentWSMain] [tid: main] [ecid: 0000Lw5G_4I8PtfLxYo2yW1Pr7ht000001,0] *******************************************
[2017-10-15T19:49:13.119+02:00] [JAGENT] [ERROR] [] [com.goldengate.monitor.jagent.JAgentWSMain] [tid: main] [ecid: 0000Lw5G_4I8PtfLxYo2yW1Pr7ht000001,0] (NON-ERROR NOTIFICATION) Monitor Agent Release Version: 12.2.1.2.170601
[2017-10-15T19:49:13.119+02:00] [JAGENT] [ERROR] [] [com.goldengate.monitor.jagent.JAgentWSMain] [tid: main] [ecid: 0000Lw5G_4I8PtfLxYo2yW1Pr7ht000001,0] (NON-ERROR NOTIFICATION) Build Label: OGGMON_12.2.1.2.0_PLATFORMS_RELEASE
[2017-10-15T19:49:13.119+02:00] [JAGENT] [ERROR] [] [com.goldengate.monitor.jagent.JAgentWSMain] [tid: main] [ecid: 0000Lw5G_4I8PtfLxYo2yW1Pr7ht000001,0] *******************************************
[2017-10-15T19:49:16.612+02:00] [JAGENT] [NOTIFICATION] [OGGMON-20292] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: ManagerConnectionKeeper] [ecid: 0000Lw5G_v48PtfLxYo2yW1Pr7ht000002,0] Start Message Polling Thread...
[2017-10-15T19:49:16.615+02:00] [JAGENT] [NOTIFICATION] [OGGMON-20294] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: ManagerConnectionKeeper] [ecid: 0000Lw5G_v48PtfLxYo2yW1Pr7ht000002,0] Start Status Polling Thread...
[2017-10-15T19:49:21.594+02:00] [JAGENT] [NOTIFICATION] [OGGMON-20286] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: getInstanceList] [ecid: 0000Lw5Gb8u8PtfLxYo2yW1Pr7ht000003,0] Registering MBean Capture[localId=:type=capture,name=EXTR] as :type=capture,name=EXTR
[2017-10-15T19:49:21.604+02:00] [JAGENT] [NOTIFICATION] [OGGMON-20286] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: getInstanceList] [ecid: 0000Lw5Gb8u8PtfLxYo2yW1Pr7ht000003,0] Registering MBean Database[localId=:type=database,name=DBORA] as :type=database,name=DBORA
[2017-10-15T19:49:21.606+02:00] [JAGENT] [NOTIFICATION] [OGGMON-20286] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: getInstanceList] [ecid: 0000Lw5Gb8u8PtfLxYo2yW1Pr7ht000003,0] Registering MBean Agent[localId=:type=agent,name=MGR] as :type=agent,name=MGR
[2017-10-15T19:49:21.611+02:00] [JAGENT] [NOTIFICATION] [OGGMON-20591] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: getInstanceList] [ecid: 0000Lw5Gb8u8PtfLxYo2yW1Pr7ht000003,0] JAgent connection info: [[
jagent.host=myhost
jagent.jmx.port=oggmajmxusr
monitor.host=5555
monitor.jmx.port=OEM
monitor.jmx.username=false
jagent.username={5}
jagent.rmi.port={6}
jagent.type.enabled={7}
jagent.ssl={8}
]]
[2017-10-15T19:49:21.611+02:00] [JAGENT] [NOTIFICATION] [OGGMON-20287] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: getInstanceList] [ecid: 0000Lw5Gb8u8PtfLxYo2yW1Pr7ht000003,0] Jagent Mode: Stand-Alone
[2017-10-15T19:49:21.612+02:00] [JAGENT] [NOTIFICATION] [OGGMON-20293] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: getInstanceList] [ecid: 0000Lw5Gb8u8PtfLxYo2yW1Pr7ht000003,0] Resume Message Polling Thread...
[2017-10-15T19:49:21.612+02:00] [JAGENT] [NOTIFICATION] [OGGMON-20295] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: getInstanceList] [ecid: 0000Lw5Gb8u8PtfLxYo2yW1Pr7ht000003,0] Resume Status Polling Thread...
The problem is solved and jagent should work correctly.