2 Installing and Configuring Oracle GoldenGate Monitor Agent
If you are installing Oracle GoldenGate Monitor Agent on a z/OS platform, see Installing Oracle GoldenGate Monitor Agent for z/OS.
This chapter contains the following sections:
2.1 Installing Oracle GoldenGate Monitor Agent
Use the Oracle Universal Installer (OUI) to install Oracle GoldenGate Monitor Agent for all non-z/OS platforms. Perform the following steps:
2.1.1 Start the Installer
To start the installation program:
Where fmw_12.2.1.2.0_ogg.jar
is the name of the file that you
downloaded for your operating system.
When the installation program appears, you are ready to begin the installation. See Install the Product for a description of each installation program screen.
Note:
Oracle GoldenGate Monitor installer will not run on shared disk.
2.1.2 Install the Product
To install the product, navigate through the Installer screens, providing the necessary information as described on the following table. This table lists the screens in the order they will appear and provides instructions for completing any necessary fields. If you want further information on any screen, click its name in the left-hand column.
Screen | Description |
---|---|
This screen introduces you to the product installer. Click Next. |
|
Use this screen to specify the location of your Oracle home directory.
|
|
Use this screen to select an installation type.
|
|
This screen verifies that your system meets the minimum necessary requirements. If there are any warning or error messages, you can refer to one of the documents referenced in "Verifying Certification, System Requirements, and Interoperability" in Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware. Click Next. |
|
Use this screen to verify the installation options you selected. Note: To display an individual component's approximate installed size, click its name. Click Install. |
|
This screen shows the progress of the installation. When the progress bar reaches 100%, the installation is complete. Be aware that the Generating Libraries process can take up to 70% of the total installation time on some systems. When the installation progress is 100%, click Next. |
|
This screen appears at the conclusion of the installation and provides a summary of the products and features that were installed. Click Finish. With this step, OUI installs the Oracle GoldenGate Monitor Agent binaries and configuration files, along with OUI specific file set, in the |
2.2 Creating and Configuring an Oracle GoldenGate Monitor Agent Instance
This topic describes the procedures for creating and configuring an Oracle GoldenGate Monitor Agent instance. This process requires these six steps:
2.2.1 Create the Oracle GoldenGate Monitor Agent Instance
You can create additional instances using this same process though you must ensure that you create them in unique directories. For example, you can point a new Monitor Agent instance to the same Oracle GoldenGate Instance directory (such as, /u01/ogg/replication/oggcore1
) or a different Oracle GoldenGate Monitor Agent Instance, and the Oracle GoldenGate Monitor Agent Instance directory must always be a new directory (such as, /u01/ogg/agents/oggmon/agent2
). The Oracle GoldenGate Monitor Agent reports Oracle GoldenGate monitoring statistics to the Oracle GoldenGate Monitor Server based on how it is configured.
Note:
Ensure that for Oracle GoldenGate 12.3.x, the minimum required JAgent version is 12.2.1.2.171115.2.2.2 Update the Configuration Properties
Oracle GoldenGate Monitor Agent operates in one of two modes, Oracle GoldenGate Monitor Server or Oracle GoldenGate Enterprise Management Plug-In. You set the configuration properties for the mode you want to operate in using the following steps:
The oggmon.properties
file is required to create the wallet.
Note:
If you use the Oracle GoldenGate Monitor UI to change a configuration file, you must reopen the file by clicking the Edit button. The tab title is changed to prefix with an asterisk symbol (*), which means that the text area is in edit mode. If you change any value and navigate to other sections without saving, then a confirmation dialog is displayed to inform you to save the change. Otherwise, the changed value is not retained and no messages are displayed.
2.2.3 Create Wallet Credentials
Navigate to the OGG_AGENT_INST_HOME/bin
directory, and then use one of the following sections to create the Oracle Wallet for your operating mode, Oracle GoldenGate Monitor or Oracle GoldenGate Enterprise Management Plug-In.
2.2.4 Copy the SSL Certificate Files
Note:
This step is required only if the Oracle GoldenGate Monitor Agent is running in SSL mode.
Go to the OGG_AGENT_INST_HOME
/dircrt
and copy the Keystore and Truststore files.
After copying the keystore and truststore files, do the following:
Note:
If you are using a self-signed certificate, you can use the same file for both keystore file and truststore. If you are using a third-party signed certificate, you need to update your property file with the appropriate keystore and trust store files.
2.2.6 Starting the Oracle GoldenGate Monitor Agent
- Go to the Oracle GoldenGate GGSCI
console and start Oracle GoldenGate Monitor Agent by
executing the following commands:
For GoldenGate 12.2.x and older versions:
start manager start * start jagent
For GoldenGate 12.3.x and newer versions:
start pmsrvr start manager start * start jagent
You can also add
autostart jagent
to themgr.prm
file. In this case, you can skip thestart jagent
command. - Monitor the new Agent log file,
$AGENT_HOME/logs/ogg_agent.log
and resolve any issues.If you are using the Oracle GoldenGate Enterprise Manager Plug-In, after jAgent starts correctly you must restart the Oracle Enterprise Manager (OEM) Agent and then login to the OEM 12c console to ensure that the out-of-sync status issues for Oracle GoldenGate registered targets are resolved.
- When Web Services become unresponsive due to BDB corruption and errors, you can recreate the datastore and restart all services.
stop jagent stop * stop manager delete datastore create datastore start manager start * start jagent
stop jagent stop * stop manager stop pmsrvr start pmsrvr -initds start manager start * start jagent
2.2.7 Check Oracle GoldenGate Monitor Agent Instance Log Files
Once you have completed the preceding steps and Oracle GoldenGate Monitor Agent is running,
the OracleOracle GoldenGate Monitor Agent log details are written to
ogg_agent.log
, which is in
OGG_AGENT_INST_HOME/logs
.
Starting with 12.2.1.2.0 release, Oracle GoldenGate Agent log file only includes
errors and warnings. You can edit the
OGG_AGENT_INST_HOME/cfg/logging-config.xml
file to customize
the log level.
2.3 Starting Multiple Oracle GoldenGate Monitor Instances
To monitor the Oracle GoldenGate Core instance through Oracle GoldenGate Monitor and Oracle GoldenGate Enterprise Manager Plug-in, multiple Oracle GoldenGate Monitor instances can be installed.
To run multiple Oracle GoldenGate Monitor Agent Instances from a single install Oracle GoldenGate Core instance:
-
Install the Oracle GoldenGate Core product.
-
Install standalone Oracle GoldenGate Monitor Agent instance 1 pointing to Oracle GoldenGate Core Instance. You can set the mode=OEM.
-
Configure Oracle GoldenGate Agent properties (
Config.properties
) as required for OGGPLG 12.1.0.2.0 which is underOGG_AGENT_HOME1/cfg
directory.-
The absolute path of Oracle GoldenGate home directory:
OGG_CORE_HOME
-
absolute path of first OGG Agent instance directory:
OGG_AGENT_HOME1
-
-
Change the mgr.host to the host name of the machine where Manager is running and mgr.port to the mgr port of the OGGCORE instance.
-
Make a copy of the JAVA command from OGG Core instance which is available in
OGG_CORE_HOME/dirprm/jagent.prm
file. -
Create a standalone Oracle GoldenGate Monitor Agent Instance 2 pointing to the same Oracle GoldenGate Core Instance You can set the mode =OGGMON.
-
The absolute path of Oracle GoldenGate home directory:
OGG_CORE_HOME
-
The absolute path of second OGG Agent instance directory:
OGG_AGENT_HOME2
Note:
If the jagent.prm is already exists under
OGG_CORE_HOME/dirprm/
the jagent.prm file will be replaced with the latest jagent.prm file. -
-
Configure Oracle GoldenGate Agent properties (
Config.properties
) as need for Monitor 12.1.3 which is underOGG_AGENT_HOME2/cfg
directory. -
Start Oracle GoldenGate Monitor Agent instance 2 from GGSCI.
-
Execute the Java command copied in step 5 for the Monitor agent instance 1 from
OGG_AGENT_HOME1
folder created in step 3 or run the scriptstartMonitorAgentInstance_*.sh
present underOGG_AGENT_HOME2/bin
from theOGG_CORE_HOME
location for starting the Monitor agent instance 1.For example:
OGG_AGENT_HOME2/bin/startMonitorAgentInstance_*.sh
Note:
JAgent should be always be started from the
OGG_CORE_HOME
location because internally based on the usr.dir (the directory where Java was run) system property are used from setting the OGGC CORE location.