GoldenGate Monitor Agent (JAgent) Terminates With Broken Pipe (13) And Exit Code 255 (Doc ID 2543584.1)

Last updated on APRIL 17, 2023

Applies to:

Symptoms

GoldenGate Monitor agents has been configured in OEM setup as below:

- GoldenGate Monitor agent for GG 18.1 on Oracle database 12c on AIX 7.1 (JAgent_1)
- GoldenGate Monitor agent for GG 12.1.2 on Oracle database 12c on AX 7.1 (JAgent_2)

JAgent_1 has been successfully setup and it is running ok. When started JAgent_2, it abended with following messages in ggserr.log file:

2019-05-05 19:29:36 INFO OGG-00975 Oracle GoldenGate Manager for Oracle, mgr.prm: GGCMD JAGENT starting.
2019-05-05 19:29:36 INFO OGG-01927 Oracle GoldenGate Command Tool for Oracle, jagent.prm: Child process started, process ID 46991752, command line 'java -Dconfig.dir=<path>/cfg -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=<path>/cfg/logging-config.xml -Doracle.core.ojdl.logging.componentId=JAGENT -jar -Xms512m -Xmx1024m <path>/ogg_agent/dirjar/jagent.jar'.
2019-05-05 19:29:44 ERROR OGG-01117 Oracle GoldenGate Command Interpreter for Oracle: Received signal: Broken pipe (13).
2019-05-05 19:29:44 ERROR OGG-01668 Oracle GoldenGate Command Interpreter for Oracle: PROCESS ABENDING.
2019-05-05 19:29:44 ERROR OGG-01117 Oracle GoldenGate Command Interpreter for Oracle: Received signal: Illegal instruction (4).
2019-05-05 19:29:44 ERROR OGG-01668 Oracle GoldenGate Command Interpreter for Oracle: PROCESS ABENDING.
2019-05-05 19:29:44 INFO OGG-01928 Oracle GoldenGate Command Tool for Oracle, jagent.prm: Child process terminated with exit code 255.
2019-05-05 19:29:44 INFO OGG-00979 Oracle GoldenGate Command Tool for Oracle, jagent.prm: GGCMD JAGENT is down (gracefully).

Java version is 1.8. LIBPATH is set to $JAVA_HOME/bin:$GG_HOME:$ORACLE_HOME/lib.

Changes

Cause

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