4 Upgrading Oracle GoldenGate Monitor Agent

This chapter describes the tasks you perform to install and upgrade Oracle GoldenGate Monitor Agent from 11g to 12c or when upgrading the original JAgent that was delivered with 12c.

Note:

Do not follow the instructions in this chapter if you have installed Oracle GoldenGate Monitor Agent 12c for the first time; the upgrade occurs automatically.

Use the following tasks to upgrade your existing Oracle GoldenGate Monitor Agent($OGG_HOME/dirjar) 11g to 12c:

Task 1   Obtain Oracle GoldenGate Monitor Agent

Obtain the product distribution by following the instructions in Section 1.4, "Downloading Oracle GoldenGate Monitor Agent."

Task 2   Backup the Existing Oracle GoldenGate Monitor Agent

Create a backup copy of your entire pre-upgrade Oracle GoldenGate Monitor Agent environment before you upgrade by copying the following to a backup location:

  • OGG_HOME/cfg directory

  • OGG_HOME/dirjar directory

  • OGG_HOME/pw_agent_util.* files

  • OGG_HOME/jagent.* files

  • OGG_HOME/dirwlt directory

Task 3   Configuring the JRE

Configure your JRE as follows:

  1. Set your $JAVA_HOME environment variable to use JRE 1.7 or greater.

  2. Set $JAVA_HOME/bin first in your $PATH environment variable.

  3. Verify that $JAVA_HOME and $JAVA_HOME/bin are setup correctly by running the following command:

    java -version

    The Java version is displayed and should be similar to the following:

    java version "1.7.0_60"
Java(TM) SE Runtime Environment (build 1.7.0_60-b19)
Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)
Task 4   Installing Oracle GoldenGate Monitor Agent

Execute the OUI to install Oracle GoldenGate Monitor Agent:

java -jar -Xmx1024m /path/to/jar/file/fmw_12.1.3.0.0_ogg.jar

Install Oracle GoldenGate Monitor Agent in a separate, standalone location using the instructions in one of the following dependent on your database:

For non-z/OS platforms, use Section 2, "Installing and Configuring Oracle GoldenGate Monitor Agent."

For z/OS platforms, use Section 3, "Installing and Configuring Oracle GoldenGate Monitor Agent for z/OS and DB2 for i."

Task 5   Stopping JAgent

Go to the Oracle GoldenGate Core GGSCI terminal and stop the Oracle GoldenGate Monitor Agent by executing the stop jagent command:

GGSCI>stop jagent

Verify that there are no remaining jagent processes after by running the following command:

ps -ef |grep jagent

Use the kill -9 command to stop if any stray jagent processes.

Task 6   Create a New Instance

Create a new instance using the instructions in one of the following dependent on your operating system:

For non-z/OS platforms, use Section 2.2.1, "Create the Instance."

For z/OS platforms, use Section 3.4.1, "Create the Instance."

This modifies the $OGG_HOME/dirprm/jagent.prm file as in the following example:

COMMAND java -Dconfig.dir=/home/oracle/oggmon_agent/oggmon/cfg -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=/home/oracle/oggmon_
agent/oggmon/cfg/logging-config.xml -Doracle.core.ojdl.logging.componentId=JAGENT -jar -Xms512m -Xmx1024m /home/oracle/oggmon_agent/oggmon/ogg_agent/dirjar/jagent.jar

In this example, the jagent that will now be used is in /home/oracle/oggmon_agent/oggmon/ogg_agent/dirjar/jagent.jar and its configuration file is in the /home/oracle/oggmon_agent/oggmon/cfg directory.

Task 7   Copying Files to the New Agent Directories

Copy the existing $OGG_HOME/dirwlt directory, including all content, to the new Agent directory, $AGENT_HOME/oggmon/ogg_agent.

Copy the existing $OGG_HOME/cfg/Config.properties file into the new Agent directory, $AGENT_HOME/oggmon/cfg.

Task 8   Starting the Agent

Go to the Oracle GoldenGate Core GGSCI terminal and restart the Oracle GoldenGate Monitor Agent by executing the following commands:

stop manager
start manager
stop jagent
start jagent

Monitor the new Agent log file, $AGENT_HOME/logs/ogg_agent.log and resolve any issues.

If you are using the Oracle GoldenGate EM Plug-in, after jagent starts correctly you must restart the Oracle Enterprise Manager (OEM) Agent then login to the OEM 12c console to ensure that the out of sync status issues for Oracle GoldenGate registered targets are resolved.

Task 9   Removing the Previous Oracle GoldenGate Monitor Agent Software

Remove the previous Oracle GoldenGate Monitor Agent software that was bundled with Oracle GoldenGate Software by deleting the following:

  • OGG_HOME/cfg directory

  • OGG_HOME/dirjar directory

  • OGG_HOME/pw_agent_util.* files

  • OGG_HOME/jagent.* files

  • (Optional) If you do not store anything related to Oracle GoldenGate Instance in Oracle Wallet, then delete the OGG_HOME/dirwlt directory.