oracle goldengate best practices: configuring oracle ... · pdf fileoracle goldengate best...
TRANSCRIPT
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
An Oracle White Paper
August 2014
Oracle GoldenGate Best Practices Configuring Oracle
GoldenGate Monitor 12c
Document ID 19405961
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
2
EXECUTIVE OVERVIEW 5
INTRODUCTION 5
ORACLE GOLDENGATE (OGG) MONITOR ARCHITECTURE 6
Monitor Server 6
Monitor Agent 6
Repository 6
INSTALLATION OUTLINE 7
OGG Monitor Prerequisite 7 Monitor Server 7 Monitor Agent 7
OGG Monitor Server Installation Sequence 8 1 Install Oracle JDK 7 Update 15 or higher 8 2 Install WebLogic Server 12c (1213) 8 3 Install Database Software to be used for Repository 8 4 Execute the OGG Monitor Server Installer 9 5 Execute the WebLogic Repository Creation Utility (RCU) 9 6 Execute the WebLogic Configuration Utility for Monitor 9 7 Start the WebLogic Admin Server amp Monitor Server 10 8 Create OGG Monitor Admin User in WebLogic 11
OGG Monitor Agent Installation Steps 17 1 Make sure Java 7 update 15 or higher exist on the server 17 2 Execute the Monitor 12c Installer to install the Agent 17 3 Create the OGG Monitor Agent Instance for the OGG Core 17 4 Create the Wallet Credentials for the Monitor Agent Instance 18 5 Enable Monitoring support on the OGG Core Instance 18 6 Create the Datastore to persist monitoring data 18
CONFIGURATION 19
Monitor Server ndash monitorproperties 19
Monitor Agent ndash Configproperties 20
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
3
Monitor Server Web Interface 21
Monitoring Points 22 OGG Objects 22 Capture Metrics 23 Delivery Metrics 23 Solution Metrics 23
Alert Notification 24 Configure Alert Definition 25
Multiple OGG Monitor Agent Instances 28
REFERENCES 29
APPENDIX A ndash SAMPLE OGG MONITOR CONFIGURATION FILES 29
Monitor Server Property File 29
Monitor Agent Property File 31
APPENDIX B ndash SAMPLE OGG MONITOR ALERT EMAIL 34
Monitor Alter Definition Name Capture Latency 34
Monitor Alter Definition Name Delivery Latency 34
Monitor Alter Definition Name Solution Latency 34
Monitor Alter Definition Name Capture Status 35
Monitor Alter Definition Name Delivery Status 35
Monitor Alter Definition Name Solution Status 36
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
4
This document touches briefly on many important and complex concepts and does not provide
a detailed explanation of any one topic since the intent is to present the material in the most
expedient manner The goal is simply to help the reader become familiar enough with the
product to successfully design and implement a highly available Oracle GoldenGate
environment To that end it is important to note that the activities of design unit testing and
integration testing which are crucial to a successful implementation have been intentionally left
out of the guide All the examples are provided as is Oracle consulting service is highly
recommended for any customized implementation and a review of the specific production
documentation is required
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
5
Executive Overview
This document is an introduction to Oracle GoldenGatersquos best practices and guidelines for configuring
Oracle GoldenGate (OGG) Monitor Version 12c This document is intended for System
Administrators Oracle Database Administrators (DBAs) Oracle Developers with some basic
knowledge of Oracle GoldenGate software product and Oracle GoldenGate administrators The
document is intended to be an introductory supplement to the existing series of documentation
available from Oracle
The following assumptions have been made during the writing of this document
The reader is familiar with Web technologies and has a general understanding of Windows and
UNIX platforms
The reader has basic knowledge of Oracle GoldenGate products and concepts
Referencing Oracle GoldenGate Version 1121 and above
Referencing Oracle GoldenGate Monitor Version 12c
Referencing OS Oracle Linux x86-64
The example installation and configuration in this document was done on a Linux Environment
running Oracle Linux Server Release 65 for the Operating System and Oracle Database Release
12101 for the WebLogic Repository
Introduction
Oracle GoldenGate provides data capture from transaction logs and delivery for heterogeneous
databases and messaging systems Oracle GoldenGate (OGG) provides a flexible de-coupled
architecture that can be used to implement virtually all database replication scenarios
Oracle GoldenGate Monitor provides secure viewing management and alerting capabilities for
GoldenGate with end-to-end topology solution displays and customizable topology views
Oracle GoldenGate Monitor is a real-time Web-based monitoring console for the Oracle GoldenGate
replication solution Oracle GoldenGate Monitor delivers an at-a-glance graphical view of all of the
Oracle GoldenGate instances and their associated databases within your enterprise Instantly you can
view statistics targeted views and alerts that will help you to monitor the performance of all of the
objects in the Oracle GoldenGate configuration and detect problems such as lag or abended
processes the moment that they occur Oracle GoldenGate Monitor can send alert messages to its
own console workspaces as well as to e-mail SNMP and CLI clients
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
6
Oracle GoldenGate (OGG) Monitor Architecture The OGG Monitor uses a browser-based graphical user interface to monitor OGG instances remotely
It includes the components shown in the diagram
The OGG Monitor Server communicates with one or more OGG instances through either Java Management Extensions (JMX) or the Secure Sockets Layer (SSL) but not both The Manager process for each OGG instance is associated with an OGG Monitor Agent that supplies information about the instance to the OGG Monitor Server
Monitor Server
The OGG Monitor Server coordinates the monitoring of multiple OGG instances The OGG Monitor
Server is a Java application that does the following
Process information from OGG agents and communicates it to the web browser
Manage user access roles history the display of information and notifications triggered by
events
Monitor Agent
The OGG Monitor Agent is used with each OGG instance and it collects information about the
instance and sends it to the OGG Monitor Server
Repository
The OGG Monitor Server uses a database as a central repository to store information about users
groups process status events and other information
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
7
Installation Outline This section outlines the major steps required to install the Server and Agent components of Oracle
GoldenGate Monitor 12c including its prerequisites
OGG Monitor Prerequisite
Monitor Server
Here are the 3 major prerequisites needed for installing the OGG Monitor Server component
Oracle JDK 7 Update 15 or higher - this can be downloaded from Oracle eDelivery site under
the Fusion Middleware 12c Media Pack
Oracle WebLogic Server 12c with Oracle JRF Infrastructure Services ndash this can also be
downloaded from Oracle eDelivery site under the Fusion Middleware 12c Media Pack named
ldquoOracle Fusion Middleware 12c (121300) Infrastructurerdquo
Install anyone of the following Database Software for the Repository
o Oracle 11gR1 Oracle 11gR2 or Oracle 12c
o MySQL 55
o MS SQL Server 2008 or MS SQL Server 2012
Monitor Agent
Here are the 3 major prerequisites needed for installing the OGG Monitor Agent component
The Oracle GoldenGate Core product version 1121 or above needs to be installed and
configured
The Oracle GoldenGate Monitor Server 12c needs to be installed and configured
Java Runtime Environment (JRE) 7 Update 15 or higher needs to be installed and configured
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
8
OGG Monitor Server Installation Sequence
The following list outlines the steps to install the Monitor Server
1 Install Oracle JDK 7 Update 15 or higher
Install the JDK 7 on the machine where Monitor Server will be running Make sure JAVA_HOME and
the PATH environment variables are set to the JDK 7 path
For detail information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Install WebLogic Server 12c (1213)
The right version of the installer to use for WebLogic Server 12c for OGG Monitor Server is the one
that contains the Oracle Java Required Files (JRF) This installer is labeled as ldquoOracle Fusion
Middleware Infrastructurerdquo on Oracle eDelivery site under the Fusion Middleware 12c Media Pack
Execute the WebLogic Server OUI via java
For detailed information on installing WebLogic Server 12c with Oracle JRF see the Installing the
Oracle Fusion Middleware Infrastructure Software documentation link
3 Install Database Software to be used for Repository
A database repository is needed for OGG Monitor any of the following supported databases can be
installed
DATABASE VERSION DOCUMENTATION LINK
Oracle Database 11g Release 1
11g Release 2
12c Release 1
Oracle 11gR1 Documentation
Oracle 11gR2 Documentation
Oracle 12cR1 Documentation
MySQL Database MySQL 55 MySQL 55 Documentation
SQL Server Database SQL Server 2008
SQL Server 2012
SQL Server 2008 Documentation
SQL Server 2012 Documentation
Note For Oracle database repository it requires support for AL32UTF8 character set Make
sure that the Database Character Set is set to AL32UTF8
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
9
4 Execute the OGG Monitor Server Installer
The OGG Monitor 12c is installed via the Oracle Universal Installer (OUI) The installer for Oracle
GoldenGate Monitor 12c can be downloaded from the Oracle Technology Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Server Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitorrdquo documentation link
5 Execute the WebLogic Repository Creation Utility (RCU)
The OGG Monitor uses a database as a repository to store all OGG monitoring information the RCU
program which comes with the WebLogic server is used to create the OGG Monitor-specific
repository
Execute the WebLogic Server RCU script
For detail visual information on the Repository Creation Utility for OGG Monitor on an Oracle
database see the ldquoRepository Creation Utility (RCU) Screens for Oracle GoldenGate Monitorrdquo
documentation link
6 Execute the WebLogic Configuration Utility for Monitor
The GoldenGate Monitor Server runs as a domain within the WebLogic the domain configuration
wizard needs to be executed to create a separate domain server within WebLogic
Execute the WebLogic Server Domain Configuration Wizard script
For detail visual information on the WebLogic Configuration Utility Wizard for OGG Monitor see the
ldquoConfiguration Wizard Screens for Oracle GoldenGate Monitorrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
10
7 Start the WebLogic Admin Server amp Monitor Server
The Weblogic Administration server needs to be started to start configuring services and users within
WebLogic
By default the startup script for the WebLogic Server which is ldquostartWebLogicshrdquo can be found in
$MW_HOMEuser_projectsdomainsbase_domain directory The $MW_HOME is the directory
where you set the installation directory for the WebLogic
Execute the WebLogic Admin Server startup script
To start the Monitor Server execute the startup script for ManageServer named
ldquostartManagedWebLogicshrdquo passing the name of the Monitor Domain Server which was defined
during the installation process and the URL for the WebLogic Admin Server By default the startup
script can be found in the $MW_HOMEuser_projectsdomainsbase_domainbin directory
Sample Syntax for the startup script
u01apporacleproductwlsuser_projectsdomainsbase_domainbinstartManagedWeb
Logicsh MONITORSERVER_server1 httpslc08ggj7001
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
11
8 Create OGG Monitor Admin User in WebLogic
OGG Monitor Server process runs within WebLogic server all users for OGG Monitor need to be
created within WebLogic By default therersquos no OGG Monitor Admin defined in the system however
therersquos a pre-defined Groups with Oracle GoldenGate roles built-in within WebLogic
We need to create a user with the correct OGG group role to act as the OGG Monitor Admin via the
Security Realms within the WebLogic Administration Console
Here are the steps to create the OGG Admin User within WebLogic Admin Console
A Login as WebLogic on the WebLogic Server Admin Console (Default Port is 7001)
B Select and Click ldquoSecurity Realmsrdquo under the Domain Structure
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
12
C Select and Click ldquomyrealmrdquo under the Summary of Security Realms
D Select and Click the Tab ldquoUsers and Groupsrdquo under Settings for myrealm
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
13
E Select and Click ldquoNewrdquo under the Users Tab
F Fill-out the username description and provide the password for the user and click OK In
the screen example the username is ldquoggadminrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
14
G You will see a message ldquoUser created successfullyrdquo and then click the username
ldquoggadminrdquo to go to the ldquoggadminrdquo user page
H Select and Click the ldquoGroupsrdquo tab to go to the group role page and start assigning group
roles to ggadmin user group
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
15
I Under ldquoAvailable Parent Grouprdquo select and click OGGAdministrator OGGOperator
OGGPowerOperator and OGGSuperAdmin and click the ldquogtrdquo sign to move it to the
ldquoChosenrdquo column
J Now you will see those Group Roles under the ldquoChosenrdquo columns then select and click
ldquoSaverdquo to update the security settings for ggadmin user
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
16
K Now you will see a message ldquoSettings updated successfullyrdquo at this point you are done
with the WebLogic Admin console and you can select and click ldquoLog Outrdquo to exit
For more detailed information see ldquoInstalling and Configuring Oraclereg GoldenGate Monitor 12crdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
17
OGG Monitor Agent Installation Steps
These are the OGG Monitor Agent High Level Installation Steps
1 Make sure Java 7 update 15 or higher exist on the server
Make sure therersquos a Java (JDK or JRE) environment existing on the system where the Monitor agent
will be installed The Java version should be Java 7 update 15 or higher
For detailed information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Execute the Monitor 12c Installer to install the Agent
The OGG Monitor 12c Agent is installed via the same Oracle Universal Installer (OUI) file used for
Monitor Server You have to select the ldquoAgent Installrdquo only when installing the Agent component
The installer for Oracle GoldenGate Monitor 12c can be downloaded from the Oracle Technology
Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Agent Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitor Agentrdquo documentation link
3 Create the OGG Monitor Agent Instance for the OGG Core
The OGG Monitor 12c Agent installation copies all the necessary OGG Monitor files onto the server
To configure the Agent to monitor an OGG instance an agent instance needs to be created and
attached to an OGG core instance and this is done via a script
Execute the script create_ogg_agent_instancesh to create an OGG Monitor 12c Agent instance
from the directory where the Monitor Agent was installed on the server where OGG core is running
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
2
EXECUTIVE OVERVIEW 5
INTRODUCTION 5
ORACLE GOLDENGATE (OGG) MONITOR ARCHITECTURE 6
Monitor Server 6
Monitor Agent 6
Repository 6
INSTALLATION OUTLINE 7
OGG Monitor Prerequisite 7 Monitor Server 7 Monitor Agent 7
OGG Monitor Server Installation Sequence 8 1 Install Oracle JDK 7 Update 15 or higher 8 2 Install WebLogic Server 12c (1213) 8 3 Install Database Software to be used for Repository 8 4 Execute the OGG Monitor Server Installer 9 5 Execute the WebLogic Repository Creation Utility (RCU) 9 6 Execute the WebLogic Configuration Utility for Monitor 9 7 Start the WebLogic Admin Server amp Monitor Server 10 8 Create OGG Monitor Admin User in WebLogic 11
OGG Monitor Agent Installation Steps 17 1 Make sure Java 7 update 15 or higher exist on the server 17 2 Execute the Monitor 12c Installer to install the Agent 17 3 Create the OGG Monitor Agent Instance for the OGG Core 17 4 Create the Wallet Credentials for the Monitor Agent Instance 18 5 Enable Monitoring support on the OGG Core Instance 18 6 Create the Datastore to persist monitoring data 18
CONFIGURATION 19
Monitor Server ndash monitorproperties 19
Monitor Agent ndash Configproperties 20
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
3
Monitor Server Web Interface 21
Monitoring Points 22 OGG Objects 22 Capture Metrics 23 Delivery Metrics 23 Solution Metrics 23
Alert Notification 24 Configure Alert Definition 25
Multiple OGG Monitor Agent Instances 28
REFERENCES 29
APPENDIX A ndash SAMPLE OGG MONITOR CONFIGURATION FILES 29
Monitor Server Property File 29
Monitor Agent Property File 31
APPENDIX B ndash SAMPLE OGG MONITOR ALERT EMAIL 34
Monitor Alter Definition Name Capture Latency 34
Monitor Alter Definition Name Delivery Latency 34
Monitor Alter Definition Name Solution Latency 34
Monitor Alter Definition Name Capture Status 35
Monitor Alter Definition Name Delivery Status 35
Monitor Alter Definition Name Solution Status 36
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
4
This document touches briefly on many important and complex concepts and does not provide
a detailed explanation of any one topic since the intent is to present the material in the most
expedient manner The goal is simply to help the reader become familiar enough with the
product to successfully design and implement a highly available Oracle GoldenGate
environment To that end it is important to note that the activities of design unit testing and
integration testing which are crucial to a successful implementation have been intentionally left
out of the guide All the examples are provided as is Oracle consulting service is highly
recommended for any customized implementation and a review of the specific production
documentation is required
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
5
Executive Overview
This document is an introduction to Oracle GoldenGatersquos best practices and guidelines for configuring
Oracle GoldenGate (OGG) Monitor Version 12c This document is intended for System
Administrators Oracle Database Administrators (DBAs) Oracle Developers with some basic
knowledge of Oracle GoldenGate software product and Oracle GoldenGate administrators The
document is intended to be an introductory supplement to the existing series of documentation
available from Oracle
The following assumptions have been made during the writing of this document
The reader is familiar with Web technologies and has a general understanding of Windows and
UNIX platforms
The reader has basic knowledge of Oracle GoldenGate products and concepts
Referencing Oracle GoldenGate Version 1121 and above
Referencing Oracle GoldenGate Monitor Version 12c
Referencing OS Oracle Linux x86-64
The example installation and configuration in this document was done on a Linux Environment
running Oracle Linux Server Release 65 for the Operating System and Oracle Database Release
12101 for the WebLogic Repository
Introduction
Oracle GoldenGate provides data capture from transaction logs and delivery for heterogeneous
databases and messaging systems Oracle GoldenGate (OGG) provides a flexible de-coupled
architecture that can be used to implement virtually all database replication scenarios
Oracle GoldenGate Monitor provides secure viewing management and alerting capabilities for
GoldenGate with end-to-end topology solution displays and customizable topology views
Oracle GoldenGate Monitor is a real-time Web-based monitoring console for the Oracle GoldenGate
replication solution Oracle GoldenGate Monitor delivers an at-a-glance graphical view of all of the
Oracle GoldenGate instances and their associated databases within your enterprise Instantly you can
view statistics targeted views and alerts that will help you to monitor the performance of all of the
objects in the Oracle GoldenGate configuration and detect problems such as lag or abended
processes the moment that they occur Oracle GoldenGate Monitor can send alert messages to its
own console workspaces as well as to e-mail SNMP and CLI clients
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
6
Oracle GoldenGate (OGG) Monitor Architecture The OGG Monitor uses a browser-based graphical user interface to monitor OGG instances remotely
It includes the components shown in the diagram
The OGG Monitor Server communicates with one or more OGG instances through either Java Management Extensions (JMX) or the Secure Sockets Layer (SSL) but not both The Manager process for each OGG instance is associated with an OGG Monitor Agent that supplies information about the instance to the OGG Monitor Server
Monitor Server
The OGG Monitor Server coordinates the monitoring of multiple OGG instances The OGG Monitor
Server is a Java application that does the following
Process information from OGG agents and communicates it to the web browser
Manage user access roles history the display of information and notifications triggered by
events
Monitor Agent
The OGG Monitor Agent is used with each OGG instance and it collects information about the
instance and sends it to the OGG Monitor Server
Repository
The OGG Monitor Server uses a database as a central repository to store information about users
groups process status events and other information
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
7
Installation Outline This section outlines the major steps required to install the Server and Agent components of Oracle
GoldenGate Monitor 12c including its prerequisites
OGG Monitor Prerequisite
Monitor Server
Here are the 3 major prerequisites needed for installing the OGG Monitor Server component
Oracle JDK 7 Update 15 or higher - this can be downloaded from Oracle eDelivery site under
the Fusion Middleware 12c Media Pack
Oracle WebLogic Server 12c with Oracle JRF Infrastructure Services ndash this can also be
downloaded from Oracle eDelivery site under the Fusion Middleware 12c Media Pack named
ldquoOracle Fusion Middleware 12c (121300) Infrastructurerdquo
Install anyone of the following Database Software for the Repository
o Oracle 11gR1 Oracle 11gR2 or Oracle 12c
o MySQL 55
o MS SQL Server 2008 or MS SQL Server 2012
Monitor Agent
Here are the 3 major prerequisites needed for installing the OGG Monitor Agent component
The Oracle GoldenGate Core product version 1121 or above needs to be installed and
configured
The Oracle GoldenGate Monitor Server 12c needs to be installed and configured
Java Runtime Environment (JRE) 7 Update 15 or higher needs to be installed and configured
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
8
OGG Monitor Server Installation Sequence
The following list outlines the steps to install the Monitor Server
1 Install Oracle JDK 7 Update 15 or higher
Install the JDK 7 on the machine where Monitor Server will be running Make sure JAVA_HOME and
the PATH environment variables are set to the JDK 7 path
For detail information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Install WebLogic Server 12c (1213)
The right version of the installer to use for WebLogic Server 12c for OGG Monitor Server is the one
that contains the Oracle Java Required Files (JRF) This installer is labeled as ldquoOracle Fusion
Middleware Infrastructurerdquo on Oracle eDelivery site under the Fusion Middleware 12c Media Pack
Execute the WebLogic Server OUI via java
For detailed information on installing WebLogic Server 12c with Oracle JRF see the Installing the
Oracle Fusion Middleware Infrastructure Software documentation link
3 Install Database Software to be used for Repository
A database repository is needed for OGG Monitor any of the following supported databases can be
installed
DATABASE VERSION DOCUMENTATION LINK
Oracle Database 11g Release 1
11g Release 2
12c Release 1
Oracle 11gR1 Documentation
Oracle 11gR2 Documentation
Oracle 12cR1 Documentation
MySQL Database MySQL 55 MySQL 55 Documentation
SQL Server Database SQL Server 2008
SQL Server 2012
SQL Server 2008 Documentation
SQL Server 2012 Documentation
Note For Oracle database repository it requires support for AL32UTF8 character set Make
sure that the Database Character Set is set to AL32UTF8
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
9
4 Execute the OGG Monitor Server Installer
The OGG Monitor 12c is installed via the Oracle Universal Installer (OUI) The installer for Oracle
GoldenGate Monitor 12c can be downloaded from the Oracle Technology Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Server Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitorrdquo documentation link
5 Execute the WebLogic Repository Creation Utility (RCU)
The OGG Monitor uses a database as a repository to store all OGG monitoring information the RCU
program which comes with the WebLogic server is used to create the OGG Monitor-specific
repository
Execute the WebLogic Server RCU script
For detail visual information on the Repository Creation Utility for OGG Monitor on an Oracle
database see the ldquoRepository Creation Utility (RCU) Screens for Oracle GoldenGate Monitorrdquo
documentation link
6 Execute the WebLogic Configuration Utility for Monitor
The GoldenGate Monitor Server runs as a domain within the WebLogic the domain configuration
wizard needs to be executed to create a separate domain server within WebLogic
Execute the WebLogic Server Domain Configuration Wizard script
For detail visual information on the WebLogic Configuration Utility Wizard for OGG Monitor see the
ldquoConfiguration Wizard Screens for Oracle GoldenGate Monitorrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
10
7 Start the WebLogic Admin Server amp Monitor Server
The Weblogic Administration server needs to be started to start configuring services and users within
WebLogic
By default the startup script for the WebLogic Server which is ldquostartWebLogicshrdquo can be found in
$MW_HOMEuser_projectsdomainsbase_domain directory The $MW_HOME is the directory
where you set the installation directory for the WebLogic
Execute the WebLogic Admin Server startup script
To start the Monitor Server execute the startup script for ManageServer named
ldquostartManagedWebLogicshrdquo passing the name of the Monitor Domain Server which was defined
during the installation process and the URL for the WebLogic Admin Server By default the startup
script can be found in the $MW_HOMEuser_projectsdomainsbase_domainbin directory
Sample Syntax for the startup script
u01apporacleproductwlsuser_projectsdomainsbase_domainbinstartManagedWeb
Logicsh MONITORSERVER_server1 httpslc08ggj7001
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
11
8 Create OGG Monitor Admin User in WebLogic
OGG Monitor Server process runs within WebLogic server all users for OGG Monitor need to be
created within WebLogic By default therersquos no OGG Monitor Admin defined in the system however
therersquos a pre-defined Groups with Oracle GoldenGate roles built-in within WebLogic
We need to create a user with the correct OGG group role to act as the OGG Monitor Admin via the
Security Realms within the WebLogic Administration Console
Here are the steps to create the OGG Admin User within WebLogic Admin Console
A Login as WebLogic on the WebLogic Server Admin Console (Default Port is 7001)
B Select and Click ldquoSecurity Realmsrdquo under the Domain Structure
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
12
C Select and Click ldquomyrealmrdquo under the Summary of Security Realms
D Select and Click the Tab ldquoUsers and Groupsrdquo under Settings for myrealm
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
13
E Select and Click ldquoNewrdquo under the Users Tab
F Fill-out the username description and provide the password for the user and click OK In
the screen example the username is ldquoggadminrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
14
G You will see a message ldquoUser created successfullyrdquo and then click the username
ldquoggadminrdquo to go to the ldquoggadminrdquo user page
H Select and Click the ldquoGroupsrdquo tab to go to the group role page and start assigning group
roles to ggadmin user group
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
15
I Under ldquoAvailable Parent Grouprdquo select and click OGGAdministrator OGGOperator
OGGPowerOperator and OGGSuperAdmin and click the ldquogtrdquo sign to move it to the
ldquoChosenrdquo column
J Now you will see those Group Roles under the ldquoChosenrdquo columns then select and click
ldquoSaverdquo to update the security settings for ggadmin user
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
16
K Now you will see a message ldquoSettings updated successfullyrdquo at this point you are done
with the WebLogic Admin console and you can select and click ldquoLog Outrdquo to exit
For more detailed information see ldquoInstalling and Configuring Oraclereg GoldenGate Monitor 12crdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
17
OGG Monitor Agent Installation Steps
These are the OGG Monitor Agent High Level Installation Steps
1 Make sure Java 7 update 15 or higher exist on the server
Make sure therersquos a Java (JDK or JRE) environment existing on the system where the Monitor agent
will be installed The Java version should be Java 7 update 15 or higher
For detailed information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Execute the Monitor 12c Installer to install the Agent
The OGG Monitor 12c Agent is installed via the same Oracle Universal Installer (OUI) file used for
Monitor Server You have to select the ldquoAgent Installrdquo only when installing the Agent component
The installer for Oracle GoldenGate Monitor 12c can be downloaded from the Oracle Technology
Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Agent Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitor Agentrdquo documentation link
3 Create the OGG Monitor Agent Instance for the OGG Core
The OGG Monitor 12c Agent installation copies all the necessary OGG Monitor files onto the server
To configure the Agent to monitor an OGG instance an agent instance needs to be created and
attached to an OGG core instance and this is done via a script
Execute the script create_ogg_agent_instancesh to create an OGG Monitor 12c Agent instance
from the directory where the Monitor Agent was installed on the server where OGG core is running
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
3
Monitor Server Web Interface 21
Monitoring Points 22 OGG Objects 22 Capture Metrics 23 Delivery Metrics 23 Solution Metrics 23
Alert Notification 24 Configure Alert Definition 25
Multiple OGG Monitor Agent Instances 28
REFERENCES 29
APPENDIX A ndash SAMPLE OGG MONITOR CONFIGURATION FILES 29
Monitor Server Property File 29
Monitor Agent Property File 31
APPENDIX B ndash SAMPLE OGG MONITOR ALERT EMAIL 34
Monitor Alter Definition Name Capture Latency 34
Monitor Alter Definition Name Delivery Latency 34
Monitor Alter Definition Name Solution Latency 34
Monitor Alter Definition Name Capture Status 35
Monitor Alter Definition Name Delivery Status 35
Monitor Alter Definition Name Solution Status 36
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
4
This document touches briefly on many important and complex concepts and does not provide
a detailed explanation of any one topic since the intent is to present the material in the most
expedient manner The goal is simply to help the reader become familiar enough with the
product to successfully design and implement a highly available Oracle GoldenGate
environment To that end it is important to note that the activities of design unit testing and
integration testing which are crucial to a successful implementation have been intentionally left
out of the guide All the examples are provided as is Oracle consulting service is highly
recommended for any customized implementation and a review of the specific production
documentation is required
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
5
Executive Overview
This document is an introduction to Oracle GoldenGatersquos best practices and guidelines for configuring
Oracle GoldenGate (OGG) Monitor Version 12c This document is intended for System
Administrators Oracle Database Administrators (DBAs) Oracle Developers with some basic
knowledge of Oracle GoldenGate software product and Oracle GoldenGate administrators The
document is intended to be an introductory supplement to the existing series of documentation
available from Oracle
The following assumptions have been made during the writing of this document
The reader is familiar with Web technologies and has a general understanding of Windows and
UNIX platforms
The reader has basic knowledge of Oracle GoldenGate products and concepts
Referencing Oracle GoldenGate Version 1121 and above
Referencing Oracle GoldenGate Monitor Version 12c
Referencing OS Oracle Linux x86-64
The example installation and configuration in this document was done on a Linux Environment
running Oracle Linux Server Release 65 for the Operating System and Oracle Database Release
12101 for the WebLogic Repository
Introduction
Oracle GoldenGate provides data capture from transaction logs and delivery for heterogeneous
databases and messaging systems Oracle GoldenGate (OGG) provides a flexible de-coupled
architecture that can be used to implement virtually all database replication scenarios
Oracle GoldenGate Monitor provides secure viewing management and alerting capabilities for
GoldenGate with end-to-end topology solution displays and customizable topology views
Oracle GoldenGate Monitor is a real-time Web-based monitoring console for the Oracle GoldenGate
replication solution Oracle GoldenGate Monitor delivers an at-a-glance graphical view of all of the
Oracle GoldenGate instances and their associated databases within your enterprise Instantly you can
view statistics targeted views and alerts that will help you to monitor the performance of all of the
objects in the Oracle GoldenGate configuration and detect problems such as lag or abended
processes the moment that they occur Oracle GoldenGate Monitor can send alert messages to its
own console workspaces as well as to e-mail SNMP and CLI clients
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
6
Oracle GoldenGate (OGG) Monitor Architecture The OGG Monitor uses a browser-based graphical user interface to monitor OGG instances remotely
It includes the components shown in the diagram
The OGG Monitor Server communicates with one or more OGG instances through either Java Management Extensions (JMX) or the Secure Sockets Layer (SSL) but not both The Manager process for each OGG instance is associated with an OGG Monitor Agent that supplies information about the instance to the OGG Monitor Server
Monitor Server
The OGG Monitor Server coordinates the monitoring of multiple OGG instances The OGG Monitor
Server is a Java application that does the following
Process information from OGG agents and communicates it to the web browser
Manage user access roles history the display of information and notifications triggered by
events
Monitor Agent
The OGG Monitor Agent is used with each OGG instance and it collects information about the
instance and sends it to the OGG Monitor Server
Repository
The OGG Monitor Server uses a database as a central repository to store information about users
groups process status events and other information
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
7
Installation Outline This section outlines the major steps required to install the Server and Agent components of Oracle
GoldenGate Monitor 12c including its prerequisites
OGG Monitor Prerequisite
Monitor Server
Here are the 3 major prerequisites needed for installing the OGG Monitor Server component
Oracle JDK 7 Update 15 or higher - this can be downloaded from Oracle eDelivery site under
the Fusion Middleware 12c Media Pack
Oracle WebLogic Server 12c with Oracle JRF Infrastructure Services ndash this can also be
downloaded from Oracle eDelivery site under the Fusion Middleware 12c Media Pack named
ldquoOracle Fusion Middleware 12c (121300) Infrastructurerdquo
Install anyone of the following Database Software for the Repository
o Oracle 11gR1 Oracle 11gR2 or Oracle 12c
o MySQL 55
o MS SQL Server 2008 or MS SQL Server 2012
Monitor Agent
Here are the 3 major prerequisites needed for installing the OGG Monitor Agent component
The Oracle GoldenGate Core product version 1121 or above needs to be installed and
configured
The Oracle GoldenGate Monitor Server 12c needs to be installed and configured
Java Runtime Environment (JRE) 7 Update 15 or higher needs to be installed and configured
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
8
OGG Monitor Server Installation Sequence
The following list outlines the steps to install the Monitor Server
1 Install Oracle JDK 7 Update 15 or higher
Install the JDK 7 on the machine where Monitor Server will be running Make sure JAVA_HOME and
the PATH environment variables are set to the JDK 7 path
For detail information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Install WebLogic Server 12c (1213)
The right version of the installer to use for WebLogic Server 12c for OGG Monitor Server is the one
that contains the Oracle Java Required Files (JRF) This installer is labeled as ldquoOracle Fusion
Middleware Infrastructurerdquo on Oracle eDelivery site under the Fusion Middleware 12c Media Pack
Execute the WebLogic Server OUI via java
For detailed information on installing WebLogic Server 12c with Oracle JRF see the Installing the
Oracle Fusion Middleware Infrastructure Software documentation link
3 Install Database Software to be used for Repository
A database repository is needed for OGG Monitor any of the following supported databases can be
installed
DATABASE VERSION DOCUMENTATION LINK
Oracle Database 11g Release 1
11g Release 2
12c Release 1
Oracle 11gR1 Documentation
Oracle 11gR2 Documentation
Oracle 12cR1 Documentation
MySQL Database MySQL 55 MySQL 55 Documentation
SQL Server Database SQL Server 2008
SQL Server 2012
SQL Server 2008 Documentation
SQL Server 2012 Documentation
Note For Oracle database repository it requires support for AL32UTF8 character set Make
sure that the Database Character Set is set to AL32UTF8
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
9
4 Execute the OGG Monitor Server Installer
The OGG Monitor 12c is installed via the Oracle Universal Installer (OUI) The installer for Oracle
GoldenGate Monitor 12c can be downloaded from the Oracle Technology Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Server Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitorrdquo documentation link
5 Execute the WebLogic Repository Creation Utility (RCU)
The OGG Monitor uses a database as a repository to store all OGG monitoring information the RCU
program which comes with the WebLogic server is used to create the OGG Monitor-specific
repository
Execute the WebLogic Server RCU script
For detail visual information on the Repository Creation Utility for OGG Monitor on an Oracle
database see the ldquoRepository Creation Utility (RCU) Screens for Oracle GoldenGate Monitorrdquo
documentation link
6 Execute the WebLogic Configuration Utility for Monitor
The GoldenGate Monitor Server runs as a domain within the WebLogic the domain configuration
wizard needs to be executed to create a separate domain server within WebLogic
Execute the WebLogic Server Domain Configuration Wizard script
For detail visual information on the WebLogic Configuration Utility Wizard for OGG Monitor see the
ldquoConfiguration Wizard Screens for Oracle GoldenGate Monitorrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
10
7 Start the WebLogic Admin Server amp Monitor Server
The Weblogic Administration server needs to be started to start configuring services and users within
WebLogic
By default the startup script for the WebLogic Server which is ldquostartWebLogicshrdquo can be found in
$MW_HOMEuser_projectsdomainsbase_domain directory The $MW_HOME is the directory
where you set the installation directory for the WebLogic
Execute the WebLogic Admin Server startup script
To start the Monitor Server execute the startup script for ManageServer named
ldquostartManagedWebLogicshrdquo passing the name of the Monitor Domain Server which was defined
during the installation process and the URL for the WebLogic Admin Server By default the startup
script can be found in the $MW_HOMEuser_projectsdomainsbase_domainbin directory
Sample Syntax for the startup script
u01apporacleproductwlsuser_projectsdomainsbase_domainbinstartManagedWeb
Logicsh MONITORSERVER_server1 httpslc08ggj7001
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
11
8 Create OGG Monitor Admin User in WebLogic
OGG Monitor Server process runs within WebLogic server all users for OGG Monitor need to be
created within WebLogic By default therersquos no OGG Monitor Admin defined in the system however
therersquos a pre-defined Groups with Oracle GoldenGate roles built-in within WebLogic
We need to create a user with the correct OGG group role to act as the OGG Monitor Admin via the
Security Realms within the WebLogic Administration Console
Here are the steps to create the OGG Admin User within WebLogic Admin Console
A Login as WebLogic on the WebLogic Server Admin Console (Default Port is 7001)
B Select and Click ldquoSecurity Realmsrdquo under the Domain Structure
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
12
C Select and Click ldquomyrealmrdquo under the Summary of Security Realms
D Select and Click the Tab ldquoUsers and Groupsrdquo under Settings for myrealm
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
13
E Select and Click ldquoNewrdquo under the Users Tab
F Fill-out the username description and provide the password for the user and click OK In
the screen example the username is ldquoggadminrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
14
G You will see a message ldquoUser created successfullyrdquo and then click the username
ldquoggadminrdquo to go to the ldquoggadminrdquo user page
H Select and Click the ldquoGroupsrdquo tab to go to the group role page and start assigning group
roles to ggadmin user group
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
15
I Under ldquoAvailable Parent Grouprdquo select and click OGGAdministrator OGGOperator
OGGPowerOperator and OGGSuperAdmin and click the ldquogtrdquo sign to move it to the
ldquoChosenrdquo column
J Now you will see those Group Roles under the ldquoChosenrdquo columns then select and click
ldquoSaverdquo to update the security settings for ggadmin user
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
16
K Now you will see a message ldquoSettings updated successfullyrdquo at this point you are done
with the WebLogic Admin console and you can select and click ldquoLog Outrdquo to exit
For more detailed information see ldquoInstalling and Configuring Oraclereg GoldenGate Monitor 12crdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
17
OGG Monitor Agent Installation Steps
These are the OGG Monitor Agent High Level Installation Steps
1 Make sure Java 7 update 15 or higher exist on the server
Make sure therersquos a Java (JDK or JRE) environment existing on the system where the Monitor agent
will be installed The Java version should be Java 7 update 15 or higher
For detailed information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Execute the Monitor 12c Installer to install the Agent
The OGG Monitor 12c Agent is installed via the same Oracle Universal Installer (OUI) file used for
Monitor Server You have to select the ldquoAgent Installrdquo only when installing the Agent component
The installer for Oracle GoldenGate Monitor 12c can be downloaded from the Oracle Technology
Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Agent Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitor Agentrdquo documentation link
3 Create the OGG Monitor Agent Instance for the OGG Core
The OGG Monitor 12c Agent installation copies all the necessary OGG Monitor files onto the server
To configure the Agent to monitor an OGG instance an agent instance needs to be created and
attached to an OGG core instance and this is done via a script
Execute the script create_ogg_agent_instancesh to create an OGG Monitor 12c Agent instance
from the directory where the Monitor Agent was installed on the server where OGG core is running
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
4
This document touches briefly on many important and complex concepts and does not provide
a detailed explanation of any one topic since the intent is to present the material in the most
expedient manner The goal is simply to help the reader become familiar enough with the
product to successfully design and implement a highly available Oracle GoldenGate
environment To that end it is important to note that the activities of design unit testing and
integration testing which are crucial to a successful implementation have been intentionally left
out of the guide All the examples are provided as is Oracle consulting service is highly
recommended for any customized implementation and a review of the specific production
documentation is required
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
5
Executive Overview
This document is an introduction to Oracle GoldenGatersquos best practices and guidelines for configuring
Oracle GoldenGate (OGG) Monitor Version 12c This document is intended for System
Administrators Oracle Database Administrators (DBAs) Oracle Developers with some basic
knowledge of Oracle GoldenGate software product and Oracle GoldenGate administrators The
document is intended to be an introductory supplement to the existing series of documentation
available from Oracle
The following assumptions have been made during the writing of this document
The reader is familiar with Web technologies and has a general understanding of Windows and
UNIX platforms
The reader has basic knowledge of Oracle GoldenGate products and concepts
Referencing Oracle GoldenGate Version 1121 and above
Referencing Oracle GoldenGate Monitor Version 12c
Referencing OS Oracle Linux x86-64
The example installation and configuration in this document was done on a Linux Environment
running Oracle Linux Server Release 65 for the Operating System and Oracle Database Release
12101 for the WebLogic Repository
Introduction
Oracle GoldenGate provides data capture from transaction logs and delivery for heterogeneous
databases and messaging systems Oracle GoldenGate (OGG) provides a flexible de-coupled
architecture that can be used to implement virtually all database replication scenarios
Oracle GoldenGate Monitor provides secure viewing management and alerting capabilities for
GoldenGate with end-to-end topology solution displays and customizable topology views
Oracle GoldenGate Monitor is a real-time Web-based monitoring console for the Oracle GoldenGate
replication solution Oracle GoldenGate Monitor delivers an at-a-glance graphical view of all of the
Oracle GoldenGate instances and their associated databases within your enterprise Instantly you can
view statistics targeted views and alerts that will help you to monitor the performance of all of the
objects in the Oracle GoldenGate configuration and detect problems such as lag or abended
processes the moment that they occur Oracle GoldenGate Monitor can send alert messages to its
own console workspaces as well as to e-mail SNMP and CLI clients
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
6
Oracle GoldenGate (OGG) Monitor Architecture The OGG Monitor uses a browser-based graphical user interface to monitor OGG instances remotely
It includes the components shown in the diagram
The OGG Monitor Server communicates with one or more OGG instances through either Java Management Extensions (JMX) or the Secure Sockets Layer (SSL) but not both The Manager process for each OGG instance is associated with an OGG Monitor Agent that supplies information about the instance to the OGG Monitor Server
Monitor Server
The OGG Monitor Server coordinates the monitoring of multiple OGG instances The OGG Monitor
Server is a Java application that does the following
Process information from OGG agents and communicates it to the web browser
Manage user access roles history the display of information and notifications triggered by
events
Monitor Agent
The OGG Monitor Agent is used with each OGG instance and it collects information about the
instance and sends it to the OGG Monitor Server
Repository
The OGG Monitor Server uses a database as a central repository to store information about users
groups process status events and other information
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
7
Installation Outline This section outlines the major steps required to install the Server and Agent components of Oracle
GoldenGate Monitor 12c including its prerequisites
OGG Monitor Prerequisite
Monitor Server
Here are the 3 major prerequisites needed for installing the OGG Monitor Server component
Oracle JDK 7 Update 15 or higher - this can be downloaded from Oracle eDelivery site under
the Fusion Middleware 12c Media Pack
Oracle WebLogic Server 12c with Oracle JRF Infrastructure Services ndash this can also be
downloaded from Oracle eDelivery site under the Fusion Middleware 12c Media Pack named
ldquoOracle Fusion Middleware 12c (121300) Infrastructurerdquo
Install anyone of the following Database Software for the Repository
o Oracle 11gR1 Oracle 11gR2 or Oracle 12c
o MySQL 55
o MS SQL Server 2008 or MS SQL Server 2012
Monitor Agent
Here are the 3 major prerequisites needed for installing the OGG Monitor Agent component
The Oracle GoldenGate Core product version 1121 or above needs to be installed and
configured
The Oracle GoldenGate Monitor Server 12c needs to be installed and configured
Java Runtime Environment (JRE) 7 Update 15 or higher needs to be installed and configured
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
8
OGG Monitor Server Installation Sequence
The following list outlines the steps to install the Monitor Server
1 Install Oracle JDK 7 Update 15 or higher
Install the JDK 7 on the machine where Monitor Server will be running Make sure JAVA_HOME and
the PATH environment variables are set to the JDK 7 path
For detail information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Install WebLogic Server 12c (1213)
The right version of the installer to use for WebLogic Server 12c for OGG Monitor Server is the one
that contains the Oracle Java Required Files (JRF) This installer is labeled as ldquoOracle Fusion
Middleware Infrastructurerdquo on Oracle eDelivery site under the Fusion Middleware 12c Media Pack
Execute the WebLogic Server OUI via java
For detailed information on installing WebLogic Server 12c with Oracle JRF see the Installing the
Oracle Fusion Middleware Infrastructure Software documentation link
3 Install Database Software to be used for Repository
A database repository is needed for OGG Monitor any of the following supported databases can be
installed
DATABASE VERSION DOCUMENTATION LINK
Oracle Database 11g Release 1
11g Release 2
12c Release 1
Oracle 11gR1 Documentation
Oracle 11gR2 Documentation
Oracle 12cR1 Documentation
MySQL Database MySQL 55 MySQL 55 Documentation
SQL Server Database SQL Server 2008
SQL Server 2012
SQL Server 2008 Documentation
SQL Server 2012 Documentation
Note For Oracle database repository it requires support for AL32UTF8 character set Make
sure that the Database Character Set is set to AL32UTF8
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
9
4 Execute the OGG Monitor Server Installer
The OGG Monitor 12c is installed via the Oracle Universal Installer (OUI) The installer for Oracle
GoldenGate Monitor 12c can be downloaded from the Oracle Technology Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Server Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitorrdquo documentation link
5 Execute the WebLogic Repository Creation Utility (RCU)
The OGG Monitor uses a database as a repository to store all OGG monitoring information the RCU
program which comes with the WebLogic server is used to create the OGG Monitor-specific
repository
Execute the WebLogic Server RCU script
For detail visual information on the Repository Creation Utility for OGG Monitor on an Oracle
database see the ldquoRepository Creation Utility (RCU) Screens for Oracle GoldenGate Monitorrdquo
documentation link
6 Execute the WebLogic Configuration Utility for Monitor
The GoldenGate Monitor Server runs as a domain within the WebLogic the domain configuration
wizard needs to be executed to create a separate domain server within WebLogic
Execute the WebLogic Server Domain Configuration Wizard script
For detail visual information on the WebLogic Configuration Utility Wizard for OGG Monitor see the
ldquoConfiguration Wizard Screens for Oracle GoldenGate Monitorrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
10
7 Start the WebLogic Admin Server amp Monitor Server
The Weblogic Administration server needs to be started to start configuring services and users within
WebLogic
By default the startup script for the WebLogic Server which is ldquostartWebLogicshrdquo can be found in
$MW_HOMEuser_projectsdomainsbase_domain directory The $MW_HOME is the directory
where you set the installation directory for the WebLogic
Execute the WebLogic Admin Server startup script
To start the Monitor Server execute the startup script for ManageServer named
ldquostartManagedWebLogicshrdquo passing the name of the Monitor Domain Server which was defined
during the installation process and the URL for the WebLogic Admin Server By default the startup
script can be found in the $MW_HOMEuser_projectsdomainsbase_domainbin directory
Sample Syntax for the startup script
u01apporacleproductwlsuser_projectsdomainsbase_domainbinstartManagedWeb
Logicsh MONITORSERVER_server1 httpslc08ggj7001
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
11
8 Create OGG Monitor Admin User in WebLogic
OGG Monitor Server process runs within WebLogic server all users for OGG Monitor need to be
created within WebLogic By default therersquos no OGG Monitor Admin defined in the system however
therersquos a pre-defined Groups with Oracle GoldenGate roles built-in within WebLogic
We need to create a user with the correct OGG group role to act as the OGG Monitor Admin via the
Security Realms within the WebLogic Administration Console
Here are the steps to create the OGG Admin User within WebLogic Admin Console
A Login as WebLogic on the WebLogic Server Admin Console (Default Port is 7001)
B Select and Click ldquoSecurity Realmsrdquo under the Domain Structure
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
12
C Select and Click ldquomyrealmrdquo under the Summary of Security Realms
D Select and Click the Tab ldquoUsers and Groupsrdquo under Settings for myrealm
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
13
E Select and Click ldquoNewrdquo under the Users Tab
F Fill-out the username description and provide the password for the user and click OK In
the screen example the username is ldquoggadminrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
14
G You will see a message ldquoUser created successfullyrdquo and then click the username
ldquoggadminrdquo to go to the ldquoggadminrdquo user page
H Select and Click the ldquoGroupsrdquo tab to go to the group role page and start assigning group
roles to ggadmin user group
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
15
I Under ldquoAvailable Parent Grouprdquo select and click OGGAdministrator OGGOperator
OGGPowerOperator and OGGSuperAdmin and click the ldquogtrdquo sign to move it to the
ldquoChosenrdquo column
J Now you will see those Group Roles under the ldquoChosenrdquo columns then select and click
ldquoSaverdquo to update the security settings for ggadmin user
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
16
K Now you will see a message ldquoSettings updated successfullyrdquo at this point you are done
with the WebLogic Admin console and you can select and click ldquoLog Outrdquo to exit
For more detailed information see ldquoInstalling and Configuring Oraclereg GoldenGate Monitor 12crdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
17
OGG Monitor Agent Installation Steps
These are the OGG Monitor Agent High Level Installation Steps
1 Make sure Java 7 update 15 or higher exist on the server
Make sure therersquos a Java (JDK or JRE) environment existing on the system where the Monitor agent
will be installed The Java version should be Java 7 update 15 or higher
For detailed information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Execute the Monitor 12c Installer to install the Agent
The OGG Monitor 12c Agent is installed via the same Oracle Universal Installer (OUI) file used for
Monitor Server You have to select the ldquoAgent Installrdquo only when installing the Agent component
The installer for Oracle GoldenGate Monitor 12c can be downloaded from the Oracle Technology
Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Agent Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitor Agentrdquo documentation link
3 Create the OGG Monitor Agent Instance for the OGG Core
The OGG Monitor 12c Agent installation copies all the necessary OGG Monitor files onto the server
To configure the Agent to monitor an OGG instance an agent instance needs to be created and
attached to an OGG core instance and this is done via a script
Execute the script create_ogg_agent_instancesh to create an OGG Monitor 12c Agent instance
from the directory where the Monitor Agent was installed on the server where OGG core is running
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
5
Executive Overview
This document is an introduction to Oracle GoldenGatersquos best practices and guidelines for configuring
Oracle GoldenGate (OGG) Monitor Version 12c This document is intended for System
Administrators Oracle Database Administrators (DBAs) Oracle Developers with some basic
knowledge of Oracle GoldenGate software product and Oracle GoldenGate administrators The
document is intended to be an introductory supplement to the existing series of documentation
available from Oracle
The following assumptions have been made during the writing of this document
The reader is familiar with Web technologies and has a general understanding of Windows and
UNIX platforms
The reader has basic knowledge of Oracle GoldenGate products and concepts
Referencing Oracle GoldenGate Version 1121 and above
Referencing Oracle GoldenGate Monitor Version 12c
Referencing OS Oracle Linux x86-64
The example installation and configuration in this document was done on a Linux Environment
running Oracle Linux Server Release 65 for the Operating System and Oracle Database Release
12101 for the WebLogic Repository
Introduction
Oracle GoldenGate provides data capture from transaction logs and delivery for heterogeneous
databases and messaging systems Oracle GoldenGate (OGG) provides a flexible de-coupled
architecture that can be used to implement virtually all database replication scenarios
Oracle GoldenGate Monitor provides secure viewing management and alerting capabilities for
GoldenGate with end-to-end topology solution displays and customizable topology views
Oracle GoldenGate Monitor is a real-time Web-based monitoring console for the Oracle GoldenGate
replication solution Oracle GoldenGate Monitor delivers an at-a-glance graphical view of all of the
Oracle GoldenGate instances and their associated databases within your enterprise Instantly you can
view statistics targeted views and alerts that will help you to monitor the performance of all of the
objects in the Oracle GoldenGate configuration and detect problems such as lag or abended
processes the moment that they occur Oracle GoldenGate Monitor can send alert messages to its
own console workspaces as well as to e-mail SNMP and CLI clients
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
6
Oracle GoldenGate (OGG) Monitor Architecture The OGG Monitor uses a browser-based graphical user interface to monitor OGG instances remotely
It includes the components shown in the diagram
The OGG Monitor Server communicates with one or more OGG instances through either Java Management Extensions (JMX) or the Secure Sockets Layer (SSL) but not both The Manager process for each OGG instance is associated with an OGG Monitor Agent that supplies information about the instance to the OGG Monitor Server
Monitor Server
The OGG Monitor Server coordinates the monitoring of multiple OGG instances The OGG Monitor
Server is a Java application that does the following
Process information from OGG agents and communicates it to the web browser
Manage user access roles history the display of information and notifications triggered by
events
Monitor Agent
The OGG Monitor Agent is used with each OGG instance and it collects information about the
instance and sends it to the OGG Monitor Server
Repository
The OGG Monitor Server uses a database as a central repository to store information about users
groups process status events and other information
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
7
Installation Outline This section outlines the major steps required to install the Server and Agent components of Oracle
GoldenGate Monitor 12c including its prerequisites
OGG Monitor Prerequisite
Monitor Server
Here are the 3 major prerequisites needed for installing the OGG Monitor Server component
Oracle JDK 7 Update 15 or higher - this can be downloaded from Oracle eDelivery site under
the Fusion Middleware 12c Media Pack
Oracle WebLogic Server 12c with Oracle JRF Infrastructure Services ndash this can also be
downloaded from Oracle eDelivery site under the Fusion Middleware 12c Media Pack named
ldquoOracle Fusion Middleware 12c (121300) Infrastructurerdquo
Install anyone of the following Database Software for the Repository
o Oracle 11gR1 Oracle 11gR2 or Oracle 12c
o MySQL 55
o MS SQL Server 2008 or MS SQL Server 2012
Monitor Agent
Here are the 3 major prerequisites needed for installing the OGG Monitor Agent component
The Oracle GoldenGate Core product version 1121 or above needs to be installed and
configured
The Oracle GoldenGate Monitor Server 12c needs to be installed and configured
Java Runtime Environment (JRE) 7 Update 15 or higher needs to be installed and configured
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
8
OGG Monitor Server Installation Sequence
The following list outlines the steps to install the Monitor Server
1 Install Oracle JDK 7 Update 15 or higher
Install the JDK 7 on the machine where Monitor Server will be running Make sure JAVA_HOME and
the PATH environment variables are set to the JDK 7 path
For detail information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Install WebLogic Server 12c (1213)
The right version of the installer to use for WebLogic Server 12c for OGG Monitor Server is the one
that contains the Oracle Java Required Files (JRF) This installer is labeled as ldquoOracle Fusion
Middleware Infrastructurerdquo on Oracle eDelivery site under the Fusion Middleware 12c Media Pack
Execute the WebLogic Server OUI via java
For detailed information on installing WebLogic Server 12c with Oracle JRF see the Installing the
Oracle Fusion Middleware Infrastructure Software documentation link
3 Install Database Software to be used for Repository
A database repository is needed for OGG Monitor any of the following supported databases can be
installed
DATABASE VERSION DOCUMENTATION LINK
Oracle Database 11g Release 1
11g Release 2
12c Release 1
Oracle 11gR1 Documentation
Oracle 11gR2 Documentation
Oracle 12cR1 Documentation
MySQL Database MySQL 55 MySQL 55 Documentation
SQL Server Database SQL Server 2008
SQL Server 2012
SQL Server 2008 Documentation
SQL Server 2012 Documentation
Note For Oracle database repository it requires support for AL32UTF8 character set Make
sure that the Database Character Set is set to AL32UTF8
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
9
4 Execute the OGG Monitor Server Installer
The OGG Monitor 12c is installed via the Oracle Universal Installer (OUI) The installer for Oracle
GoldenGate Monitor 12c can be downloaded from the Oracle Technology Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Server Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitorrdquo documentation link
5 Execute the WebLogic Repository Creation Utility (RCU)
The OGG Monitor uses a database as a repository to store all OGG monitoring information the RCU
program which comes with the WebLogic server is used to create the OGG Monitor-specific
repository
Execute the WebLogic Server RCU script
For detail visual information on the Repository Creation Utility for OGG Monitor on an Oracle
database see the ldquoRepository Creation Utility (RCU) Screens for Oracle GoldenGate Monitorrdquo
documentation link
6 Execute the WebLogic Configuration Utility for Monitor
The GoldenGate Monitor Server runs as a domain within the WebLogic the domain configuration
wizard needs to be executed to create a separate domain server within WebLogic
Execute the WebLogic Server Domain Configuration Wizard script
For detail visual information on the WebLogic Configuration Utility Wizard for OGG Monitor see the
ldquoConfiguration Wizard Screens for Oracle GoldenGate Monitorrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
10
7 Start the WebLogic Admin Server amp Monitor Server
The Weblogic Administration server needs to be started to start configuring services and users within
WebLogic
By default the startup script for the WebLogic Server which is ldquostartWebLogicshrdquo can be found in
$MW_HOMEuser_projectsdomainsbase_domain directory The $MW_HOME is the directory
where you set the installation directory for the WebLogic
Execute the WebLogic Admin Server startup script
To start the Monitor Server execute the startup script for ManageServer named
ldquostartManagedWebLogicshrdquo passing the name of the Monitor Domain Server which was defined
during the installation process and the URL for the WebLogic Admin Server By default the startup
script can be found in the $MW_HOMEuser_projectsdomainsbase_domainbin directory
Sample Syntax for the startup script
u01apporacleproductwlsuser_projectsdomainsbase_domainbinstartManagedWeb
Logicsh MONITORSERVER_server1 httpslc08ggj7001
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
11
8 Create OGG Monitor Admin User in WebLogic
OGG Monitor Server process runs within WebLogic server all users for OGG Monitor need to be
created within WebLogic By default therersquos no OGG Monitor Admin defined in the system however
therersquos a pre-defined Groups with Oracle GoldenGate roles built-in within WebLogic
We need to create a user with the correct OGG group role to act as the OGG Monitor Admin via the
Security Realms within the WebLogic Administration Console
Here are the steps to create the OGG Admin User within WebLogic Admin Console
A Login as WebLogic on the WebLogic Server Admin Console (Default Port is 7001)
B Select and Click ldquoSecurity Realmsrdquo under the Domain Structure
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
12
C Select and Click ldquomyrealmrdquo under the Summary of Security Realms
D Select and Click the Tab ldquoUsers and Groupsrdquo under Settings for myrealm
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
13
E Select and Click ldquoNewrdquo under the Users Tab
F Fill-out the username description and provide the password for the user and click OK In
the screen example the username is ldquoggadminrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
14
G You will see a message ldquoUser created successfullyrdquo and then click the username
ldquoggadminrdquo to go to the ldquoggadminrdquo user page
H Select and Click the ldquoGroupsrdquo tab to go to the group role page and start assigning group
roles to ggadmin user group
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
15
I Under ldquoAvailable Parent Grouprdquo select and click OGGAdministrator OGGOperator
OGGPowerOperator and OGGSuperAdmin and click the ldquogtrdquo sign to move it to the
ldquoChosenrdquo column
J Now you will see those Group Roles under the ldquoChosenrdquo columns then select and click
ldquoSaverdquo to update the security settings for ggadmin user
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
16
K Now you will see a message ldquoSettings updated successfullyrdquo at this point you are done
with the WebLogic Admin console and you can select and click ldquoLog Outrdquo to exit
For more detailed information see ldquoInstalling and Configuring Oraclereg GoldenGate Monitor 12crdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
17
OGG Monitor Agent Installation Steps
These are the OGG Monitor Agent High Level Installation Steps
1 Make sure Java 7 update 15 or higher exist on the server
Make sure therersquos a Java (JDK or JRE) environment existing on the system where the Monitor agent
will be installed The Java version should be Java 7 update 15 or higher
For detailed information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Execute the Monitor 12c Installer to install the Agent
The OGG Monitor 12c Agent is installed via the same Oracle Universal Installer (OUI) file used for
Monitor Server You have to select the ldquoAgent Installrdquo only when installing the Agent component
The installer for Oracle GoldenGate Monitor 12c can be downloaded from the Oracle Technology
Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Agent Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitor Agentrdquo documentation link
3 Create the OGG Monitor Agent Instance for the OGG Core
The OGG Monitor 12c Agent installation copies all the necessary OGG Monitor files onto the server
To configure the Agent to monitor an OGG instance an agent instance needs to be created and
attached to an OGG core instance and this is done via a script
Execute the script create_ogg_agent_instancesh to create an OGG Monitor 12c Agent instance
from the directory where the Monitor Agent was installed on the server where OGG core is running
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
6
Oracle GoldenGate (OGG) Monitor Architecture The OGG Monitor uses a browser-based graphical user interface to monitor OGG instances remotely
It includes the components shown in the diagram
The OGG Monitor Server communicates with one or more OGG instances through either Java Management Extensions (JMX) or the Secure Sockets Layer (SSL) but not both The Manager process for each OGG instance is associated with an OGG Monitor Agent that supplies information about the instance to the OGG Monitor Server
Monitor Server
The OGG Monitor Server coordinates the monitoring of multiple OGG instances The OGG Monitor
Server is a Java application that does the following
Process information from OGG agents and communicates it to the web browser
Manage user access roles history the display of information and notifications triggered by
events
Monitor Agent
The OGG Monitor Agent is used with each OGG instance and it collects information about the
instance and sends it to the OGG Monitor Server
Repository
The OGG Monitor Server uses a database as a central repository to store information about users
groups process status events and other information
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
7
Installation Outline This section outlines the major steps required to install the Server and Agent components of Oracle
GoldenGate Monitor 12c including its prerequisites
OGG Monitor Prerequisite
Monitor Server
Here are the 3 major prerequisites needed for installing the OGG Monitor Server component
Oracle JDK 7 Update 15 or higher - this can be downloaded from Oracle eDelivery site under
the Fusion Middleware 12c Media Pack
Oracle WebLogic Server 12c with Oracle JRF Infrastructure Services ndash this can also be
downloaded from Oracle eDelivery site under the Fusion Middleware 12c Media Pack named
ldquoOracle Fusion Middleware 12c (121300) Infrastructurerdquo
Install anyone of the following Database Software for the Repository
o Oracle 11gR1 Oracle 11gR2 or Oracle 12c
o MySQL 55
o MS SQL Server 2008 or MS SQL Server 2012
Monitor Agent
Here are the 3 major prerequisites needed for installing the OGG Monitor Agent component
The Oracle GoldenGate Core product version 1121 or above needs to be installed and
configured
The Oracle GoldenGate Monitor Server 12c needs to be installed and configured
Java Runtime Environment (JRE) 7 Update 15 or higher needs to be installed and configured
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
8
OGG Monitor Server Installation Sequence
The following list outlines the steps to install the Monitor Server
1 Install Oracle JDK 7 Update 15 or higher
Install the JDK 7 on the machine where Monitor Server will be running Make sure JAVA_HOME and
the PATH environment variables are set to the JDK 7 path
For detail information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Install WebLogic Server 12c (1213)
The right version of the installer to use for WebLogic Server 12c for OGG Monitor Server is the one
that contains the Oracle Java Required Files (JRF) This installer is labeled as ldquoOracle Fusion
Middleware Infrastructurerdquo on Oracle eDelivery site under the Fusion Middleware 12c Media Pack
Execute the WebLogic Server OUI via java
For detailed information on installing WebLogic Server 12c with Oracle JRF see the Installing the
Oracle Fusion Middleware Infrastructure Software documentation link
3 Install Database Software to be used for Repository
A database repository is needed for OGG Monitor any of the following supported databases can be
installed
DATABASE VERSION DOCUMENTATION LINK
Oracle Database 11g Release 1
11g Release 2
12c Release 1
Oracle 11gR1 Documentation
Oracle 11gR2 Documentation
Oracle 12cR1 Documentation
MySQL Database MySQL 55 MySQL 55 Documentation
SQL Server Database SQL Server 2008
SQL Server 2012
SQL Server 2008 Documentation
SQL Server 2012 Documentation
Note For Oracle database repository it requires support for AL32UTF8 character set Make
sure that the Database Character Set is set to AL32UTF8
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
9
4 Execute the OGG Monitor Server Installer
The OGG Monitor 12c is installed via the Oracle Universal Installer (OUI) The installer for Oracle
GoldenGate Monitor 12c can be downloaded from the Oracle Technology Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Server Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitorrdquo documentation link
5 Execute the WebLogic Repository Creation Utility (RCU)
The OGG Monitor uses a database as a repository to store all OGG monitoring information the RCU
program which comes with the WebLogic server is used to create the OGG Monitor-specific
repository
Execute the WebLogic Server RCU script
For detail visual information on the Repository Creation Utility for OGG Monitor on an Oracle
database see the ldquoRepository Creation Utility (RCU) Screens for Oracle GoldenGate Monitorrdquo
documentation link
6 Execute the WebLogic Configuration Utility for Monitor
The GoldenGate Monitor Server runs as a domain within the WebLogic the domain configuration
wizard needs to be executed to create a separate domain server within WebLogic
Execute the WebLogic Server Domain Configuration Wizard script
For detail visual information on the WebLogic Configuration Utility Wizard for OGG Monitor see the
ldquoConfiguration Wizard Screens for Oracle GoldenGate Monitorrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
10
7 Start the WebLogic Admin Server amp Monitor Server
The Weblogic Administration server needs to be started to start configuring services and users within
WebLogic
By default the startup script for the WebLogic Server which is ldquostartWebLogicshrdquo can be found in
$MW_HOMEuser_projectsdomainsbase_domain directory The $MW_HOME is the directory
where you set the installation directory for the WebLogic
Execute the WebLogic Admin Server startup script
To start the Monitor Server execute the startup script for ManageServer named
ldquostartManagedWebLogicshrdquo passing the name of the Monitor Domain Server which was defined
during the installation process and the URL for the WebLogic Admin Server By default the startup
script can be found in the $MW_HOMEuser_projectsdomainsbase_domainbin directory
Sample Syntax for the startup script
u01apporacleproductwlsuser_projectsdomainsbase_domainbinstartManagedWeb
Logicsh MONITORSERVER_server1 httpslc08ggj7001
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
11
8 Create OGG Monitor Admin User in WebLogic
OGG Monitor Server process runs within WebLogic server all users for OGG Monitor need to be
created within WebLogic By default therersquos no OGG Monitor Admin defined in the system however
therersquos a pre-defined Groups with Oracle GoldenGate roles built-in within WebLogic
We need to create a user with the correct OGG group role to act as the OGG Monitor Admin via the
Security Realms within the WebLogic Administration Console
Here are the steps to create the OGG Admin User within WebLogic Admin Console
A Login as WebLogic on the WebLogic Server Admin Console (Default Port is 7001)
B Select and Click ldquoSecurity Realmsrdquo under the Domain Structure
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
12
C Select and Click ldquomyrealmrdquo under the Summary of Security Realms
D Select and Click the Tab ldquoUsers and Groupsrdquo under Settings for myrealm
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
13
E Select and Click ldquoNewrdquo under the Users Tab
F Fill-out the username description and provide the password for the user and click OK In
the screen example the username is ldquoggadminrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
14
G You will see a message ldquoUser created successfullyrdquo and then click the username
ldquoggadminrdquo to go to the ldquoggadminrdquo user page
H Select and Click the ldquoGroupsrdquo tab to go to the group role page and start assigning group
roles to ggadmin user group
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
15
I Under ldquoAvailable Parent Grouprdquo select and click OGGAdministrator OGGOperator
OGGPowerOperator and OGGSuperAdmin and click the ldquogtrdquo sign to move it to the
ldquoChosenrdquo column
J Now you will see those Group Roles under the ldquoChosenrdquo columns then select and click
ldquoSaverdquo to update the security settings for ggadmin user
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
16
K Now you will see a message ldquoSettings updated successfullyrdquo at this point you are done
with the WebLogic Admin console and you can select and click ldquoLog Outrdquo to exit
For more detailed information see ldquoInstalling and Configuring Oraclereg GoldenGate Monitor 12crdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
17
OGG Monitor Agent Installation Steps
These are the OGG Monitor Agent High Level Installation Steps
1 Make sure Java 7 update 15 or higher exist on the server
Make sure therersquos a Java (JDK or JRE) environment existing on the system where the Monitor agent
will be installed The Java version should be Java 7 update 15 or higher
For detailed information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Execute the Monitor 12c Installer to install the Agent
The OGG Monitor 12c Agent is installed via the same Oracle Universal Installer (OUI) file used for
Monitor Server You have to select the ldquoAgent Installrdquo only when installing the Agent component
The installer for Oracle GoldenGate Monitor 12c can be downloaded from the Oracle Technology
Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Agent Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitor Agentrdquo documentation link
3 Create the OGG Monitor Agent Instance for the OGG Core
The OGG Monitor 12c Agent installation copies all the necessary OGG Monitor files onto the server
To configure the Agent to monitor an OGG instance an agent instance needs to be created and
attached to an OGG core instance and this is done via a script
Execute the script create_ogg_agent_instancesh to create an OGG Monitor 12c Agent instance
from the directory where the Monitor Agent was installed on the server where OGG core is running
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
7
Installation Outline This section outlines the major steps required to install the Server and Agent components of Oracle
GoldenGate Monitor 12c including its prerequisites
OGG Monitor Prerequisite
Monitor Server
Here are the 3 major prerequisites needed for installing the OGG Monitor Server component
Oracle JDK 7 Update 15 or higher - this can be downloaded from Oracle eDelivery site under
the Fusion Middleware 12c Media Pack
Oracle WebLogic Server 12c with Oracle JRF Infrastructure Services ndash this can also be
downloaded from Oracle eDelivery site under the Fusion Middleware 12c Media Pack named
ldquoOracle Fusion Middleware 12c (121300) Infrastructurerdquo
Install anyone of the following Database Software for the Repository
o Oracle 11gR1 Oracle 11gR2 or Oracle 12c
o MySQL 55
o MS SQL Server 2008 or MS SQL Server 2012
Monitor Agent
Here are the 3 major prerequisites needed for installing the OGG Monitor Agent component
The Oracle GoldenGate Core product version 1121 or above needs to be installed and
configured
The Oracle GoldenGate Monitor Server 12c needs to be installed and configured
Java Runtime Environment (JRE) 7 Update 15 or higher needs to be installed and configured
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
8
OGG Monitor Server Installation Sequence
The following list outlines the steps to install the Monitor Server
1 Install Oracle JDK 7 Update 15 or higher
Install the JDK 7 on the machine where Monitor Server will be running Make sure JAVA_HOME and
the PATH environment variables are set to the JDK 7 path
For detail information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Install WebLogic Server 12c (1213)
The right version of the installer to use for WebLogic Server 12c for OGG Monitor Server is the one
that contains the Oracle Java Required Files (JRF) This installer is labeled as ldquoOracle Fusion
Middleware Infrastructurerdquo on Oracle eDelivery site under the Fusion Middleware 12c Media Pack
Execute the WebLogic Server OUI via java
For detailed information on installing WebLogic Server 12c with Oracle JRF see the Installing the
Oracle Fusion Middleware Infrastructure Software documentation link
3 Install Database Software to be used for Repository
A database repository is needed for OGG Monitor any of the following supported databases can be
installed
DATABASE VERSION DOCUMENTATION LINK
Oracle Database 11g Release 1
11g Release 2
12c Release 1
Oracle 11gR1 Documentation
Oracle 11gR2 Documentation
Oracle 12cR1 Documentation
MySQL Database MySQL 55 MySQL 55 Documentation
SQL Server Database SQL Server 2008
SQL Server 2012
SQL Server 2008 Documentation
SQL Server 2012 Documentation
Note For Oracle database repository it requires support for AL32UTF8 character set Make
sure that the Database Character Set is set to AL32UTF8
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
9
4 Execute the OGG Monitor Server Installer
The OGG Monitor 12c is installed via the Oracle Universal Installer (OUI) The installer for Oracle
GoldenGate Monitor 12c can be downloaded from the Oracle Technology Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Server Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitorrdquo documentation link
5 Execute the WebLogic Repository Creation Utility (RCU)
The OGG Monitor uses a database as a repository to store all OGG monitoring information the RCU
program which comes with the WebLogic server is used to create the OGG Monitor-specific
repository
Execute the WebLogic Server RCU script
For detail visual information on the Repository Creation Utility for OGG Monitor on an Oracle
database see the ldquoRepository Creation Utility (RCU) Screens for Oracle GoldenGate Monitorrdquo
documentation link
6 Execute the WebLogic Configuration Utility for Monitor
The GoldenGate Monitor Server runs as a domain within the WebLogic the domain configuration
wizard needs to be executed to create a separate domain server within WebLogic
Execute the WebLogic Server Domain Configuration Wizard script
For detail visual information on the WebLogic Configuration Utility Wizard for OGG Monitor see the
ldquoConfiguration Wizard Screens for Oracle GoldenGate Monitorrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
10
7 Start the WebLogic Admin Server amp Monitor Server
The Weblogic Administration server needs to be started to start configuring services and users within
WebLogic
By default the startup script for the WebLogic Server which is ldquostartWebLogicshrdquo can be found in
$MW_HOMEuser_projectsdomainsbase_domain directory The $MW_HOME is the directory
where you set the installation directory for the WebLogic
Execute the WebLogic Admin Server startup script
To start the Monitor Server execute the startup script for ManageServer named
ldquostartManagedWebLogicshrdquo passing the name of the Monitor Domain Server which was defined
during the installation process and the URL for the WebLogic Admin Server By default the startup
script can be found in the $MW_HOMEuser_projectsdomainsbase_domainbin directory
Sample Syntax for the startup script
u01apporacleproductwlsuser_projectsdomainsbase_domainbinstartManagedWeb
Logicsh MONITORSERVER_server1 httpslc08ggj7001
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
11
8 Create OGG Monitor Admin User in WebLogic
OGG Monitor Server process runs within WebLogic server all users for OGG Monitor need to be
created within WebLogic By default therersquos no OGG Monitor Admin defined in the system however
therersquos a pre-defined Groups with Oracle GoldenGate roles built-in within WebLogic
We need to create a user with the correct OGG group role to act as the OGG Monitor Admin via the
Security Realms within the WebLogic Administration Console
Here are the steps to create the OGG Admin User within WebLogic Admin Console
A Login as WebLogic on the WebLogic Server Admin Console (Default Port is 7001)
B Select and Click ldquoSecurity Realmsrdquo under the Domain Structure
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
12
C Select and Click ldquomyrealmrdquo under the Summary of Security Realms
D Select and Click the Tab ldquoUsers and Groupsrdquo under Settings for myrealm
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
13
E Select and Click ldquoNewrdquo under the Users Tab
F Fill-out the username description and provide the password for the user and click OK In
the screen example the username is ldquoggadminrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
14
G You will see a message ldquoUser created successfullyrdquo and then click the username
ldquoggadminrdquo to go to the ldquoggadminrdquo user page
H Select and Click the ldquoGroupsrdquo tab to go to the group role page and start assigning group
roles to ggadmin user group
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
15
I Under ldquoAvailable Parent Grouprdquo select and click OGGAdministrator OGGOperator
OGGPowerOperator and OGGSuperAdmin and click the ldquogtrdquo sign to move it to the
ldquoChosenrdquo column
J Now you will see those Group Roles under the ldquoChosenrdquo columns then select and click
ldquoSaverdquo to update the security settings for ggadmin user
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
16
K Now you will see a message ldquoSettings updated successfullyrdquo at this point you are done
with the WebLogic Admin console and you can select and click ldquoLog Outrdquo to exit
For more detailed information see ldquoInstalling and Configuring Oraclereg GoldenGate Monitor 12crdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
17
OGG Monitor Agent Installation Steps
These are the OGG Monitor Agent High Level Installation Steps
1 Make sure Java 7 update 15 or higher exist on the server
Make sure therersquos a Java (JDK or JRE) environment existing on the system where the Monitor agent
will be installed The Java version should be Java 7 update 15 or higher
For detailed information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Execute the Monitor 12c Installer to install the Agent
The OGG Monitor 12c Agent is installed via the same Oracle Universal Installer (OUI) file used for
Monitor Server You have to select the ldquoAgent Installrdquo only when installing the Agent component
The installer for Oracle GoldenGate Monitor 12c can be downloaded from the Oracle Technology
Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Agent Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitor Agentrdquo documentation link
3 Create the OGG Monitor Agent Instance for the OGG Core
The OGG Monitor 12c Agent installation copies all the necessary OGG Monitor files onto the server
To configure the Agent to monitor an OGG instance an agent instance needs to be created and
attached to an OGG core instance and this is done via a script
Execute the script create_ogg_agent_instancesh to create an OGG Monitor 12c Agent instance
from the directory where the Monitor Agent was installed on the server where OGG core is running
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
8
OGG Monitor Server Installation Sequence
The following list outlines the steps to install the Monitor Server
1 Install Oracle JDK 7 Update 15 or higher
Install the JDK 7 on the machine where Monitor Server will be running Make sure JAVA_HOME and
the PATH environment variables are set to the JDK 7 path
For detail information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Install WebLogic Server 12c (1213)
The right version of the installer to use for WebLogic Server 12c for OGG Monitor Server is the one
that contains the Oracle Java Required Files (JRF) This installer is labeled as ldquoOracle Fusion
Middleware Infrastructurerdquo on Oracle eDelivery site under the Fusion Middleware 12c Media Pack
Execute the WebLogic Server OUI via java
For detailed information on installing WebLogic Server 12c with Oracle JRF see the Installing the
Oracle Fusion Middleware Infrastructure Software documentation link
3 Install Database Software to be used for Repository
A database repository is needed for OGG Monitor any of the following supported databases can be
installed
DATABASE VERSION DOCUMENTATION LINK
Oracle Database 11g Release 1
11g Release 2
12c Release 1
Oracle 11gR1 Documentation
Oracle 11gR2 Documentation
Oracle 12cR1 Documentation
MySQL Database MySQL 55 MySQL 55 Documentation
SQL Server Database SQL Server 2008
SQL Server 2012
SQL Server 2008 Documentation
SQL Server 2012 Documentation
Note For Oracle database repository it requires support for AL32UTF8 character set Make
sure that the Database Character Set is set to AL32UTF8
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
9
4 Execute the OGG Monitor Server Installer
The OGG Monitor 12c is installed via the Oracle Universal Installer (OUI) The installer for Oracle
GoldenGate Monitor 12c can be downloaded from the Oracle Technology Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Server Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitorrdquo documentation link
5 Execute the WebLogic Repository Creation Utility (RCU)
The OGG Monitor uses a database as a repository to store all OGG monitoring information the RCU
program which comes with the WebLogic server is used to create the OGG Monitor-specific
repository
Execute the WebLogic Server RCU script
For detail visual information on the Repository Creation Utility for OGG Monitor on an Oracle
database see the ldquoRepository Creation Utility (RCU) Screens for Oracle GoldenGate Monitorrdquo
documentation link
6 Execute the WebLogic Configuration Utility for Monitor
The GoldenGate Monitor Server runs as a domain within the WebLogic the domain configuration
wizard needs to be executed to create a separate domain server within WebLogic
Execute the WebLogic Server Domain Configuration Wizard script
For detail visual information on the WebLogic Configuration Utility Wizard for OGG Monitor see the
ldquoConfiguration Wizard Screens for Oracle GoldenGate Monitorrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
10
7 Start the WebLogic Admin Server amp Monitor Server
The Weblogic Administration server needs to be started to start configuring services and users within
WebLogic
By default the startup script for the WebLogic Server which is ldquostartWebLogicshrdquo can be found in
$MW_HOMEuser_projectsdomainsbase_domain directory The $MW_HOME is the directory
where you set the installation directory for the WebLogic
Execute the WebLogic Admin Server startup script
To start the Monitor Server execute the startup script for ManageServer named
ldquostartManagedWebLogicshrdquo passing the name of the Monitor Domain Server which was defined
during the installation process and the URL for the WebLogic Admin Server By default the startup
script can be found in the $MW_HOMEuser_projectsdomainsbase_domainbin directory
Sample Syntax for the startup script
u01apporacleproductwlsuser_projectsdomainsbase_domainbinstartManagedWeb
Logicsh MONITORSERVER_server1 httpslc08ggj7001
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
11
8 Create OGG Monitor Admin User in WebLogic
OGG Monitor Server process runs within WebLogic server all users for OGG Monitor need to be
created within WebLogic By default therersquos no OGG Monitor Admin defined in the system however
therersquos a pre-defined Groups with Oracle GoldenGate roles built-in within WebLogic
We need to create a user with the correct OGG group role to act as the OGG Monitor Admin via the
Security Realms within the WebLogic Administration Console
Here are the steps to create the OGG Admin User within WebLogic Admin Console
A Login as WebLogic on the WebLogic Server Admin Console (Default Port is 7001)
B Select and Click ldquoSecurity Realmsrdquo under the Domain Structure
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
12
C Select and Click ldquomyrealmrdquo under the Summary of Security Realms
D Select and Click the Tab ldquoUsers and Groupsrdquo under Settings for myrealm
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
13
E Select and Click ldquoNewrdquo under the Users Tab
F Fill-out the username description and provide the password for the user and click OK In
the screen example the username is ldquoggadminrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
14
G You will see a message ldquoUser created successfullyrdquo and then click the username
ldquoggadminrdquo to go to the ldquoggadminrdquo user page
H Select and Click the ldquoGroupsrdquo tab to go to the group role page and start assigning group
roles to ggadmin user group
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
15
I Under ldquoAvailable Parent Grouprdquo select and click OGGAdministrator OGGOperator
OGGPowerOperator and OGGSuperAdmin and click the ldquogtrdquo sign to move it to the
ldquoChosenrdquo column
J Now you will see those Group Roles under the ldquoChosenrdquo columns then select and click
ldquoSaverdquo to update the security settings for ggadmin user
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
16
K Now you will see a message ldquoSettings updated successfullyrdquo at this point you are done
with the WebLogic Admin console and you can select and click ldquoLog Outrdquo to exit
For more detailed information see ldquoInstalling and Configuring Oraclereg GoldenGate Monitor 12crdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
17
OGG Monitor Agent Installation Steps
These are the OGG Monitor Agent High Level Installation Steps
1 Make sure Java 7 update 15 or higher exist on the server
Make sure therersquos a Java (JDK or JRE) environment existing on the system where the Monitor agent
will be installed The Java version should be Java 7 update 15 or higher
For detailed information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Execute the Monitor 12c Installer to install the Agent
The OGG Monitor 12c Agent is installed via the same Oracle Universal Installer (OUI) file used for
Monitor Server You have to select the ldquoAgent Installrdquo only when installing the Agent component
The installer for Oracle GoldenGate Monitor 12c can be downloaded from the Oracle Technology
Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Agent Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitor Agentrdquo documentation link
3 Create the OGG Monitor Agent Instance for the OGG Core
The OGG Monitor 12c Agent installation copies all the necessary OGG Monitor files onto the server
To configure the Agent to monitor an OGG instance an agent instance needs to be created and
attached to an OGG core instance and this is done via a script
Execute the script create_ogg_agent_instancesh to create an OGG Monitor 12c Agent instance
from the directory where the Monitor Agent was installed on the server where OGG core is running
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
9
4 Execute the OGG Monitor Server Installer
The OGG Monitor 12c is installed via the Oracle Universal Installer (OUI) The installer for Oracle
GoldenGate Monitor 12c can be downloaded from the Oracle Technology Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Server Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitorrdquo documentation link
5 Execute the WebLogic Repository Creation Utility (RCU)
The OGG Monitor uses a database as a repository to store all OGG monitoring information the RCU
program which comes with the WebLogic server is used to create the OGG Monitor-specific
repository
Execute the WebLogic Server RCU script
For detail visual information on the Repository Creation Utility for OGG Monitor on an Oracle
database see the ldquoRepository Creation Utility (RCU) Screens for Oracle GoldenGate Monitorrdquo
documentation link
6 Execute the WebLogic Configuration Utility for Monitor
The GoldenGate Monitor Server runs as a domain within the WebLogic the domain configuration
wizard needs to be executed to create a separate domain server within WebLogic
Execute the WebLogic Server Domain Configuration Wizard script
For detail visual information on the WebLogic Configuration Utility Wizard for OGG Monitor see the
ldquoConfiguration Wizard Screens for Oracle GoldenGate Monitorrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
10
7 Start the WebLogic Admin Server amp Monitor Server
The Weblogic Administration server needs to be started to start configuring services and users within
WebLogic
By default the startup script for the WebLogic Server which is ldquostartWebLogicshrdquo can be found in
$MW_HOMEuser_projectsdomainsbase_domain directory The $MW_HOME is the directory
where you set the installation directory for the WebLogic
Execute the WebLogic Admin Server startup script
To start the Monitor Server execute the startup script for ManageServer named
ldquostartManagedWebLogicshrdquo passing the name of the Monitor Domain Server which was defined
during the installation process and the URL for the WebLogic Admin Server By default the startup
script can be found in the $MW_HOMEuser_projectsdomainsbase_domainbin directory
Sample Syntax for the startup script
u01apporacleproductwlsuser_projectsdomainsbase_domainbinstartManagedWeb
Logicsh MONITORSERVER_server1 httpslc08ggj7001
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
11
8 Create OGG Monitor Admin User in WebLogic
OGG Monitor Server process runs within WebLogic server all users for OGG Monitor need to be
created within WebLogic By default therersquos no OGG Monitor Admin defined in the system however
therersquos a pre-defined Groups with Oracle GoldenGate roles built-in within WebLogic
We need to create a user with the correct OGG group role to act as the OGG Monitor Admin via the
Security Realms within the WebLogic Administration Console
Here are the steps to create the OGG Admin User within WebLogic Admin Console
A Login as WebLogic on the WebLogic Server Admin Console (Default Port is 7001)
B Select and Click ldquoSecurity Realmsrdquo under the Domain Structure
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
12
C Select and Click ldquomyrealmrdquo under the Summary of Security Realms
D Select and Click the Tab ldquoUsers and Groupsrdquo under Settings for myrealm
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
13
E Select and Click ldquoNewrdquo under the Users Tab
F Fill-out the username description and provide the password for the user and click OK In
the screen example the username is ldquoggadminrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
14
G You will see a message ldquoUser created successfullyrdquo and then click the username
ldquoggadminrdquo to go to the ldquoggadminrdquo user page
H Select and Click the ldquoGroupsrdquo tab to go to the group role page and start assigning group
roles to ggadmin user group
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
15
I Under ldquoAvailable Parent Grouprdquo select and click OGGAdministrator OGGOperator
OGGPowerOperator and OGGSuperAdmin and click the ldquogtrdquo sign to move it to the
ldquoChosenrdquo column
J Now you will see those Group Roles under the ldquoChosenrdquo columns then select and click
ldquoSaverdquo to update the security settings for ggadmin user
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
16
K Now you will see a message ldquoSettings updated successfullyrdquo at this point you are done
with the WebLogic Admin console and you can select and click ldquoLog Outrdquo to exit
For more detailed information see ldquoInstalling and Configuring Oraclereg GoldenGate Monitor 12crdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
17
OGG Monitor Agent Installation Steps
These are the OGG Monitor Agent High Level Installation Steps
1 Make sure Java 7 update 15 or higher exist on the server
Make sure therersquos a Java (JDK or JRE) environment existing on the system where the Monitor agent
will be installed The Java version should be Java 7 update 15 or higher
For detailed information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Execute the Monitor 12c Installer to install the Agent
The OGG Monitor 12c Agent is installed via the same Oracle Universal Installer (OUI) file used for
Monitor Server You have to select the ldquoAgent Installrdquo only when installing the Agent component
The installer for Oracle GoldenGate Monitor 12c can be downloaded from the Oracle Technology
Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Agent Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitor Agentrdquo documentation link
3 Create the OGG Monitor Agent Instance for the OGG Core
The OGG Monitor 12c Agent installation copies all the necessary OGG Monitor files onto the server
To configure the Agent to monitor an OGG instance an agent instance needs to be created and
attached to an OGG core instance and this is done via a script
Execute the script create_ogg_agent_instancesh to create an OGG Monitor 12c Agent instance
from the directory where the Monitor Agent was installed on the server where OGG core is running
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
10
7 Start the WebLogic Admin Server amp Monitor Server
The Weblogic Administration server needs to be started to start configuring services and users within
WebLogic
By default the startup script for the WebLogic Server which is ldquostartWebLogicshrdquo can be found in
$MW_HOMEuser_projectsdomainsbase_domain directory The $MW_HOME is the directory
where you set the installation directory for the WebLogic
Execute the WebLogic Admin Server startup script
To start the Monitor Server execute the startup script for ManageServer named
ldquostartManagedWebLogicshrdquo passing the name of the Monitor Domain Server which was defined
during the installation process and the URL for the WebLogic Admin Server By default the startup
script can be found in the $MW_HOMEuser_projectsdomainsbase_domainbin directory
Sample Syntax for the startup script
u01apporacleproductwlsuser_projectsdomainsbase_domainbinstartManagedWeb
Logicsh MONITORSERVER_server1 httpslc08ggj7001
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
11
8 Create OGG Monitor Admin User in WebLogic
OGG Monitor Server process runs within WebLogic server all users for OGG Monitor need to be
created within WebLogic By default therersquos no OGG Monitor Admin defined in the system however
therersquos a pre-defined Groups with Oracle GoldenGate roles built-in within WebLogic
We need to create a user with the correct OGG group role to act as the OGG Monitor Admin via the
Security Realms within the WebLogic Administration Console
Here are the steps to create the OGG Admin User within WebLogic Admin Console
A Login as WebLogic on the WebLogic Server Admin Console (Default Port is 7001)
B Select and Click ldquoSecurity Realmsrdquo under the Domain Structure
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
12
C Select and Click ldquomyrealmrdquo under the Summary of Security Realms
D Select and Click the Tab ldquoUsers and Groupsrdquo under Settings for myrealm
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
13
E Select and Click ldquoNewrdquo under the Users Tab
F Fill-out the username description and provide the password for the user and click OK In
the screen example the username is ldquoggadminrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
14
G You will see a message ldquoUser created successfullyrdquo and then click the username
ldquoggadminrdquo to go to the ldquoggadminrdquo user page
H Select and Click the ldquoGroupsrdquo tab to go to the group role page and start assigning group
roles to ggadmin user group
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
15
I Under ldquoAvailable Parent Grouprdquo select and click OGGAdministrator OGGOperator
OGGPowerOperator and OGGSuperAdmin and click the ldquogtrdquo sign to move it to the
ldquoChosenrdquo column
J Now you will see those Group Roles under the ldquoChosenrdquo columns then select and click
ldquoSaverdquo to update the security settings for ggadmin user
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
16
K Now you will see a message ldquoSettings updated successfullyrdquo at this point you are done
with the WebLogic Admin console and you can select and click ldquoLog Outrdquo to exit
For more detailed information see ldquoInstalling and Configuring Oraclereg GoldenGate Monitor 12crdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
17
OGG Monitor Agent Installation Steps
These are the OGG Monitor Agent High Level Installation Steps
1 Make sure Java 7 update 15 or higher exist on the server
Make sure therersquos a Java (JDK or JRE) environment existing on the system where the Monitor agent
will be installed The Java version should be Java 7 update 15 or higher
For detailed information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Execute the Monitor 12c Installer to install the Agent
The OGG Monitor 12c Agent is installed via the same Oracle Universal Installer (OUI) file used for
Monitor Server You have to select the ldquoAgent Installrdquo only when installing the Agent component
The installer for Oracle GoldenGate Monitor 12c can be downloaded from the Oracle Technology
Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Agent Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitor Agentrdquo documentation link
3 Create the OGG Monitor Agent Instance for the OGG Core
The OGG Monitor 12c Agent installation copies all the necessary OGG Monitor files onto the server
To configure the Agent to monitor an OGG instance an agent instance needs to be created and
attached to an OGG core instance and this is done via a script
Execute the script create_ogg_agent_instancesh to create an OGG Monitor 12c Agent instance
from the directory where the Monitor Agent was installed on the server where OGG core is running
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
11
8 Create OGG Monitor Admin User in WebLogic
OGG Monitor Server process runs within WebLogic server all users for OGG Monitor need to be
created within WebLogic By default therersquos no OGG Monitor Admin defined in the system however
therersquos a pre-defined Groups with Oracle GoldenGate roles built-in within WebLogic
We need to create a user with the correct OGG group role to act as the OGG Monitor Admin via the
Security Realms within the WebLogic Administration Console
Here are the steps to create the OGG Admin User within WebLogic Admin Console
A Login as WebLogic on the WebLogic Server Admin Console (Default Port is 7001)
B Select and Click ldquoSecurity Realmsrdquo under the Domain Structure
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
12
C Select and Click ldquomyrealmrdquo under the Summary of Security Realms
D Select and Click the Tab ldquoUsers and Groupsrdquo under Settings for myrealm
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
13
E Select and Click ldquoNewrdquo under the Users Tab
F Fill-out the username description and provide the password for the user and click OK In
the screen example the username is ldquoggadminrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
14
G You will see a message ldquoUser created successfullyrdquo and then click the username
ldquoggadminrdquo to go to the ldquoggadminrdquo user page
H Select and Click the ldquoGroupsrdquo tab to go to the group role page and start assigning group
roles to ggadmin user group
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
15
I Under ldquoAvailable Parent Grouprdquo select and click OGGAdministrator OGGOperator
OGGPowerOperator and OGGSuperAdmin and click the ldquogtrdquo sign to move it to the
ldquoChosenrdquo column
J Now you will see those Group Roles under the ldquoChosenrdquo columns then select and click
ldquoSaverdquo to update the security settings for ggadmin user
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
16
K Now you will see a message ldquoSettings updated successfullyrdquo at this point you are done
with the WebLogic Admin console and you can select and click ldquoLog Outrdquo to exit
For more detailed information see ldquoInstalling and Configuring Oraclereg GoldenGate Monitor 12crdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
17
OGG Monitor Agent Installation Steps
These are the OGG Monitor Agent High Level Installation Steps
1 Make sure Java 7 update 15 or higher exist on the server
Make sure therersquos a Java (JDK or JRE) environment existing on the system where the Monitor agent
will be installed The Java version should be Java 7 update 15 or higher
For detailed information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Execute the Monitor 12c Installer to install the Agent
The OGG Monitor 12c Agent is installed via the same Oracle Universal Installer (OUI) file used for
Monitor Server You have to select the ldquoAgent Installrdquo only when installing the Agent component
The installer for Oracle GoldenGate Monitor 12c can be downloaded from the Oracle Technology
Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Agent Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitor Agentrdquo documentation link
3 Create the OGG Monitor Agent Instance for the OGG Core
The OGG Monitor 12c Agent installation copies all the necessary OGG Monitor files onto the server
To configure the Agent to monitor an OGG instance an agent instance needs to be created and
attached to an OGG core instance and this is done via a script
Execute the script create_ogg_agent_instancesh to create an OGG Monitor 12c Agent instance
from the directory where the Monitor Agent was installed on the server where OGG core is running
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
12
C Select and Click ldquomyrealmrdquo under the Summary of Security Realms
D Select and Click the Tab ldquoUsers and Groupsrdquo under Settings for myrealm
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
13
E Select and Click ldquoNewrdquo under the Users Tab
F Fill-out the username description and provide the password for the user and click OK In
the screen example the username is ldquoggadminrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
14
G You will see a message ldquoUser created successfullyrdquo and then click the username
ldquoggadminrdquo to go to the ldquoggadminrdquo user page
H Select and Click the ldquoGroupsrdquo tab to go to the group role page and start assigning group
roles to ggadmin user group
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
15
I Under ldquoAvailable Parent Grouprdquo select and click OGGAdministrator OGGOperator
OGGPowerOperator and OGGSuperAdmin and click the ldquogtrdquo sign to move it to the
ldquoChosenrdquo column
J Now you will see those Group Roles under the ldquoChosenrdquo columns then select and click
ldquoSaverdquo to update the security settings for ggadmin user
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
16
K Now you will see a message ldquoSettings updated successfullyrdquo at this point you are done
with the WebLogic Admin console and you can select and click ldquoLog Outrdquo to exit
For more detailed information see ldquoInstalling and Configuring Oraclereg GoldenGate Monitor 12crdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
17
OGG Monitor Agent Installation Steps
These are the OGG Monitor Agent High Level Installation Steps
1 Make sure Java 7 update 15 or higher exist on the server
Make sure therersquos a Java (JDK or JRE) environment existing on the system where the Monitor agent
will be installed The Java version should be Java 7 update 15 or higher
For detailed information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Execute the Monitor 12c Installer to install the Agent
The OGG Monitor 12c Agent is installed via the same Oracle Universal Installer (OUI) file used for
Monitor Server You have to select the ldquoAgent Installrdquo only when installing the Agent component
The installer for Oracle GoldenGate Monitor 12c can be downloaded from the Oracle Technology
Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Agent Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitor Agentrdquo documentation link
3 Create the OGG Monitor Agent Instance for the OGG Core
The OGG Monitor 12c Agent installation copies all the necessary OGG Monitor files onto the server
To configure the Agent to monitor an OGG instance an agent instance needs to be created and
attached to an OGG core instance and this is done via a script
Execute the script create_ogg_agent_instancesh to create an OGG Monitor 12c Agent instance
from the directory where the Monitor Agent was installed on the server where OGG core is running
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
13
E Select and Click ldquoNewrdquo under the Users Tab
F Fill-out the username description and provide the password for the user and click OK In
the screen example the username is ldquoggadminrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
14
G You will see a message ldquoUser created successfullyrdquo and then click the username
ldquoggadminrdquo to go to the ldquoggadminrdquo user page
H Select and Click the ldquoGroupsrdquo tab to go to the group role page and start assigning group
roles to ggadmin user group
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
15
I Under ldquoAvailable Parent Grouprdquo select and click OGGAdministrator OGGOperator
OGGPowerOperator and OGGSuperAdmin and click the ldquogtrdquo sign to move it to the
ldquoChosenrdquo column
J Now you will see those Group Roles under the ldquoChosenrdquo columns then select and click
ldquoSaverdquo to update the security settings for ggadmin user
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
16
K Now you will see a message ldquoSettings updated successfullyrdquo at this point you are done
with the WebLogic Admin console and you can select and click ldquoLog Outrdquo to exit
For more detailed information see ldquoInstalling and Configuring Oraclereg GoldenGate Monitor 12crdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
17
OGG Monitor Agent Installation Steps
These are the OGG Monitor Agent High Level Installation Steps
1 Make sure Java 7 update 15 or higher exist on the server
Make sure therersquos a Java (JDK or JRE) environment existing on the system where the Monitor agent
will be installed The Java version should be Java 7 update 15 or higher
For detailed information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Execute the Monitor 12c Installer to install the Agent
The OGG Monitor 12c Agent is installed via the same Oracle Universal Installer (OUI) file used for
Monitor Server You have to select the ldquoAgent Installrdquo only when installing the Agent component
The installer for Oracle GoldenGate Monitor 12c can be downloaded from the Oracle Technology
Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Agent Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitor Agentrdquo documentation link
3 Create the OGG Monitor Agent Instance for the OGG Core
The OGG Monitor 12c Agent installation copies all the necessary OGG Monitor files onto the server
To configure the Agent to monitor an OGG instance an agent instance needs to be created and
attached to an OGG core instance and this is done via a script
Execute the script create_ogg_agent_instancesh to create an OGG Monitor 12c Agent instance
from the directory where the Monitor Agent was installed on the server where OGG core is running
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
14
G You will see a message ldquoUser created successfullyrdquo and then click the username
ldquoggadminrdquo to go to the ldquoggadminrdquo user page
H Select and Click the ldquoGroupsrdquo tab to go to the group role page and start assigning group
roles to ggadmin user group
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
15
I Under ldquoAvailable Parent Grouprdquo select and click OGGAdministrator OGGOperator
OGGPowerOperator and OGGSuperAdmin and click the ldquogtrdquo sign to move it to the
ldquoChosenrdquo column
J Now you will see those Group Roles under the ldquoChosenrdquo columns then select and click
ldquoSaverdquo to update the security settings for ggadmin user
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
16
K Now you will see a message ldquoSettings updated successfullyrdquo at this point you are done
with the WebLogic Admin console and you can select and click ldquoLog Outrdquo to exit
For more detailed information see ldquoInstalling and Configuring Oraclereg GoldenGate Monitor 12crdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
17
OGG Monitor Agent Installation Steps
These are the OGG Monitor Agent High Level Installation Steps
1 Make sure Java 7 update 15 or higher exist on the server
Make sure therersquos a Java (JDK or JRE) environment existing on the system where the Monitor agent
will be installed The Java version should be Java 7 update 15 or higher
For detailed information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Execute the Monitor 12c Installer to install the Agent
The OGG Monitor 12c Agent is installed via the same Oracle Universal Installer (OUI) file used for
Monitor Server You have to select the ldquoAgent Installrdquo only when installing the Agent component
The installer for Oracle GoldenGate Monitor 12c can be downloaded from the Oracle Technology
Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Agent Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitor Agentrdquo documentation link
3 Create the OGG Monitor Agent Instance for the OGG Core
The OGG Monitor 12c Agent installation copies all the necessary OGG Monitor files onto the server
To configure the Agent to monitor an OGG instance an agent instance needs to be created and
attached to an OGG core instance and this is done via a script
Execute the script create_ogg_agent_instancesh to create an OGG Monitor 12c Agent instance
from the directory where the Monitor Agent was installed on the server where OGG core is running
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
15
I Under ldquoAvailable Parent Grouprdquo select and click OGGAdministrator OGGOperator
OGGPowerOperator and OGGSuperAdmin and click the ldquogtrdquo sign to move it to the
ldquoChosenrdquo column
J Now you will see those Group Roles under the ldquoChosenrdquo columns then select and click
ldquoSaverdquo to update the security settings for ggadmin user
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
16
K Now you will see a message ldquoSettings updated successfullyrdquo at this point you are done
with the WebLogic Admin console and you can select and click ldquoLog Outrdquo to exit
For more detailed information see ldquoInstalling and Configuring Oraclereg GoldenGate Monitor 12crdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
17
OGG Monitor Agent Installation Steps
These are the OGG Monitor Agent High Level Installation Steps
1 Make sure Java 7 update 15 or higher exist on the server
Make sure therersquos a Java (JDK or JRE) environment existing on the system where the Monitor agent
will be installed The Java version should be Java 7 update 15 or higher
For detailed information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Execute the Monitor 12c Installer to install the Agent
The OGG Monitor 12c Agent is installed via the same Oracle Universal Installer (OUI) file used for
Monitor Server You have to select the ldquoAgent Installrdquo only when installing the Agent component
The installer for Oracle GoldenGate Monitor 12c can be downloaded from the Oracle Technology
Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Agent Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitor Agentrdquo documentation link
3 Create the OGG Monitor Agent Instance for the OGG Core
The OGG Monitor 12c Agent installation copies all the necessary OGG Monitor files onto the server
To configure the Agent to monitor an OGG instance an agent instance needs to be created and
attached to an OGG core instance and this is done via a script
Execute the script create_ogg_agent_instancesh to create an OGG Monitor 12c Agent instance
from the directory where the Monitor Agent was installed on the server where OGG core is running
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
16
K Now you will see a message ldquoSettings updated successfullyrdquo at this point you are done
with the WebLogic Admin console and you can select and click ldquoLog Outrdquo to exit
For more detailed information see ldquoInstalling and Configuring Oraclereg GoldenGate Monitor 12crdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
17
OGG Monitor Agent Installation Steps
These are the OGG Monitor Agent High Level Installation Steps
1 Make sure Java 7 update 15 or higher exist on the server
Make sure therersquos a Java (JDK or JRE) environment existing on the system where the Monitor agent
will be installed The Java version should be Java 7 update 15 or higher
For detailed information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Execute the Monitor 12c Installer to install the Agent
The OGG Monitor 12c Agent is installed via the same Oracle Universal Installer (OUI) file used for
Monitor Server You have to select the ldquoAgent Installrdquo only when installing the Agent component
The installer for Oracle GoldenGate Monitor 12c can be downloaded from the Oracle Technology
Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Agent Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitor Agentrdquo documentation link
3 Create the OGG Monitor Agent Instance for the OGG Core
The OGG Monitor 12c Agent installation copies all the necessary OGG Monitor files onto the server
To configure the Agent to monitor an OGG instance an agent instance needs to be created and
attached to an OGG core instance and this is done via a script
Execute the script create_ogg_agent_instancesh to create an OGG Monitor 12c Agent instance
from the directory where the Monitor Agent was installed on the server where OGG core is running
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
17
OGG Monitor Agent Installation Steps
These are the OGG Monitor Agent High Level Installation Steps
1 Make sure Java 7 update 15 or higher exist on the server
Make sure therersquos a Java (JDK or JRE) environment existing on the system where the Monitor agent
will be installed The Java version should be Java 7 update 15 or higher
For detailed information on installing Oracle JDK see the JDK 7 and JRE 7 Installation Guide
documentation link
2 Execute the Monitor 12c Installer to install the Agent
The OGG Monitor 12c Agent is installed via the same Oracle Universal Installer (OUI) file used for
Monitor Server You have to select the ldquoAgent Installrdquo only when installing the Agent component
The installer for Oracle GoldenGate Monitor 12c can be downloaded from the Oracle Technology
Network website
Execute the OGG Monitor 12c OUI via Java
For detail visual information of OGG Monitor Agent Install see the ldquoInstallation Screens for Oracle
GoldenGate Monitor Agentrdquo documentation link
3 Create the OGG Monitor Agent Instance for the OGG Core
The OGG Monitor 12c Agent installation copies all the necessary OGG Monitor files onto the server
To configure the Agent to monitor an OGG instance an agent instance needs to be created and
attached to an OGG core instance and this is done via a script
Execute the script create_ogg_agent_instancesh to create an OGG Monitor 12c Agent instance
from the directory where the Monitor Agent was installed on the server where OGG core is running
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
18
4 Create the Wallet Credentials for the Monitor Agent Instance
The OGG Monitor 12c Agent uses the security wallet to store the password for connecting to the
Monitor server
Execute the script pw_agent_utilsh from the bin directory where the Monitor Agent Instance was
created to create the wallet to store the security credentials
5 Enable Monitoring support on the OGG Core Instance
The ldquoENABLEMONITORINGrdquo parameter must be added if it doesnrsquot exist in the GLOBALS file of the OGG Core instance to activate Oracle GoldenGate monitoring support
6 Create the Datastore to persist monitoring data
The Datastore must be created if it doesnrsquot exist within the OGG core instance where the Monitoring Agent has been installed Use GGSCI to check (info datastore) and create (create datastore) Sample GGSCI session to check and create datastore
For more detailed information see ldquoInstalling Configuring and Upgrading Oraclereg GoldenGate Monitor 12c Agentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
19
Configuration The configuration files for both Monitor Server and Monitor Agent needs to be customized for your
environment before you can start running and configuring OGG objects to be monitored
Monitor Server ndash monitorproperties
Unless otherwise specified by default the WebLogic Server Configuration Wizard creates the domain
in the FMW_HOMEuser_projectsdomainsbase_domain directory so the monitorproperties file
will resides by default on
FMW_HOMEuser_projectsdomainsbase_domainconfigmonitorservercfg
Most of the time the only thing you need to modify is the JMX Server properties and SMTP Alert
properties for Email Alert notification to customize it for your environment
JMX Server Properties
monitorjmxserverhost=hostname
monitorjmxserverport=port
The hostname is the name of the server on which you are running the Monitor Server (eg slc08ggj) and
port is the number of the serverrsquos listening port (eg 5502)
SMTP Alert Properties
monitorsmtpalertsenabled=true
monitorsmtpsecure=false
o Set this to true if the SMTP server yoursquoll be using is configured to use secured
protocol such as SSL or TLS when connecting
monitorsmtphost=hostname
monitorsmtpport=port
monitorsmtpfrom=sender_name_email
The hostname is the name of the SMTP Mail server on which you are running the Mail Server (eg
internal-mail-routeroraclecorpcom) port is the number of the SMTP serverrsquos mail listening port (eg
25 443) sender_name_email is the Senderrsquos Name and Email you want to set on the Email alert (eg
OGG Admin ltoggadminslc08ggjusoraclecomgt)
If you need to support and configure the Alert Notification for SNMP and CLI then see the following
documentation links
Configure SNMP Alert ndash Oracle GoldenGate Monitor 12c Configure SNMP Alert
Configuring CLI Alert ndash Oracle GoldenGate Monitor 12c Configure CLI Alert
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
20
For more detailed information on the rest of the properties defined in the OGG Monitor Server
ldquomonitorpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Server
Propertiesrdquo documentation link
Monitor Agent ndash Configproperties
The configuration file ldquoConfigpropertiesrdquo for the Monitor Agent is located in the ldquocfgrdquo directory
where the Monitor Agent instance was created (eg oggcorev1121mon_agentcfg)
Most of the time the following properties are the ones that needs to be customized
jagenthost=hostname
jagentjmxport=port
monitorhost=monitor_host_server
monitorjmxusername=jmxuser
jagentusername=jagentuser
The hostname is the name of the server on which you are running the Monitor Agent (eg slc08ggk) and
port is the number of the serverrsquos listening port (eg 5502) The monitor_host_name is the name of the
server where the Monitor server is running and this value should match the value defined in the
monitorjmxserverhost of the Monitor Server properties file The jmxuser is the name of the user
specified on the JMX Server Configuration screen during the Oracle GoldenGate Monitor
installation The jagentuser is a name used by the JMX connection to the agent
For the OGG core instance there are two things that need to be verified First make sure the
ldquoGLOBALSrdquo file exist in the OGG core instance directory and therersquos an entry
ldquoENABLEMONITORINGrdquo inside
Second the Datastore for the OGG core instance needs to exist before the Monitor Agent process can
successfully monitor OGG objects To verify if a Datastore exist for the OGG core instance you can
check this via the ldquoinfo datastorerdquo command within ggsci If you need to create the data store you
can create it via the ldquocreate datastorerdquo command within ggsci
For more detailed information on the rest of the properties defined in the OGG Monitor Agent
ldquoConfigpropertiesrdquo file see the ldquoAdministering Oracle GoldenGate Monitor12c Monitor Agent
Propertiesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
21
Monitor Server Web Interface
The Monitor Server Web Interface is the place to go to start monitoring Oracle GoldenGate processes
and to start configuring alert notifications for OGG monitored objects You need to login to the
Monitor Web Server interface to monitor and configure OGG processes
By default the URL for the Monitor Server is httpserver_hostportmonitor (eg
httpslc08ggjusoraclecom7003monitor) The server_host is the hostname where the Monitor
server is running and the port is the TCP port where the Monitor server is listening by default it
listens on port 7003
Herersquos a sample Login Screen
Upon successful login if the monitor agents have been configured and started properly on the OGG
instances the Monitor Server will automatically detect all OGG processes defined within the OGG
instance and will display it on to the Monitor System Screen page which is the default page once you
login
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
22
Herersquos a sample of the Monitor System Screen page upon successful login
For more detailed information on the OGG Monitor interface and all its objects on the OGG
Monitoring Screen see the ldquoOverview of the Oracle GoldenGate Monitor Interfacerdquo documentation
link
Monitoring Points
Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or
Monitoring MetricsAttributes Currently there are a total of 10 OGG object types that are supported
and can be defined and monitored by the OGG Monitor Server You can configure different types of
metricsattributes to monitor for each OGG object For simplicity purposes itrsquos best to start with the
most common OGG objects and itrsquos most common monitoring attributes which easily represent the
general status of the replication solution or process
OGG Objects
Here are the 3 most commonly used OGG object types configured in the Monitor Interface
Capture ndash represents an Oracle GoldenGate Extract group This can be an Online Change
Capture process or a DataPump Capture process
Delivery ndash represents an Oracle GoldenGate Replicat group This is the Delivery process
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
23
Solution - represents a complete Oracle GoldenGate source-to-target(s) topology and shows
all of the Oracle GoldenGate components in that topology including the source and target
databases
Capture Metrics
Here are the commonly used Metric Attributes to be defined for the Capture Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
There are more attributes available for the Capture process but the above metrics are enough to give
you a general idea or picture of your replication process
Delivery Metrics
Here are the Metric Attributes to be defined for the Delivery Process
Group Name
Status
Lag
Total Operations
Delta Operations Per Second
Seconds Since Last OGG Checkpoint
Checkpoint Position
Solution Metrics
Here are the Metric Attributes to be defined which are the only available attributes for a ldquoSolutionrdquo
Status
Lag
There are more attributes available for the Capture and Delivery object types but the above metrics for
Capture and Delivery are enough to give a general idea or picture of the replication process
For more detailed information or explanation regarding all OGG Monitoring Points attributes see the
ldquoOGG Monitor Attributesrdquo documentation link
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
24
Alert Notification
There are a lot of alert notifications you can defined for each OGG object but generally there are just
two common monitoring categories that most of the OGG objects fall into How far behind is the
process ndash which is Latency and if the process is still running ndash which is the Status
Generally there would be Latency and Status alert notifications defined for the 3 most commonly used
OGG object types (Capture Delivery and Solution)
The following are the list of the alert definitions for Capture Delivery and Solution OGG objects
Capture Latency
Delivery Latency
Solution Latency
Capture Status
Delivery Status
Solution Status
Alert Definition Screen Sample with Common Metric Alerts defined
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
25
Configure Alert Definition
Herersquos how to configure an Alert Definition for the ldquoCapture Latencyrdquo Alert Notification
1 From the OGG Monitor Web Interface select and click ldquoAlert Definitionrdquo tab
2 From the ldquoAlert Definitionrdquo menu select and click the button ldquoNew Alert Definitionrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
26
3 From the ldquoNew Alert Definitionrdquo type in the (1) Definition Name you want for the alert
definition in this case we will use ldquoCapture Latencyrdquo Select the (2) Alert Severity (ldquoWarningrdquo or
ldquoErrorrdquo) in this case we use ldquoWarningrdquo Use 15 minutes for the (3) Suppression Time which
means to send the alert every 15 minutes For the (4) Object Type in this example select
ldquoCapturerdquo and the (5) Attribute to use for the criteria selection is ldquoLagrdquo Use 3 seconds for the
(6) Value of Lag Next scroll down and go to the ldquoUser Assignmentrdquo
4 For the User Assignment section select and click the user you want this alert to be assigned to In
this case we only have one user which is ldquoggadminrdquo so select and click ldquoggadminrdquo and move it to
the ldquoAssigned Usersrdquo section by clicking the ldquogtrdquo button Next scroll down and go to the ldquoObject
Assignmentrdquo
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
27
5 For the Object Assignment section select and click the button for ldquoAssign to all objects of this
object typerdquo to cover all Capture processes Next scroll down and go to the ldquoAdditional Notice
Attributesrdquo section
6 From the ldquoAdditional Notice Attributesrdquo section (1) scroll down the list of the ldquoAvailable
Attributesrdquo and (2) select the following attributes
a Checkpoint Position
b Delta Operations Per Second
c Group Name
d Lag
e Seconds Since Last OGG Checkpoint
f Status
g Total Operations
(3) Move it to the ldquoAdditional Attributesrdquo section
7 Verify that your selected attributes were moved to the ldquoAdditional Attributesrdquo section and then
select and click Submit (1) to create the New Alert ldquoCapture Latencyrdquo Definition
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
28
Multiple OGG Monitor Agent Instances
It is common to have multiple OGG Core instances on one system and to monitor these instances A
separate Monitor agent needs to be created for each OGG core instance
You can create additional instances by re-running the script create_ogg_agent_instancesh You
have to make sure that you create them in unique directories For example you might use
u01oggcorev1121025_ora11gmon_agent and u01oggcorev121200_ora12cmon_agent
For each agent instance the jmxjagentport value in each ldquoConfigPropertiesrdquo must be unique for
each instance
Sample u01oggcorev1121025_ora11gmon_agent instance creation
Sample u01oggcorev1212000_ora12cmon_agent instance creation
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
29
References
The following publications were utilized as reference materials for information presented in this
document
Installing and Configuring Oracle GoldenGate Monitor 12c
Installing Configuring and Upgrading Oracle GoldenGate Monitor Agent 12c
Administering Oracle GoldenGate Monitor 12c
Using Oracle GoldenGate Monitor 12c
Appendix A ndash Sample OGG Monitor Configuration Files
This is a sample working configurationproperty files for both OGG Monitor Server and Agent
Monitor Server Property File Copyright (c) 2009 2014 Oracle andor its affiliates All rights reserved
Oracle GoldenGate Monitor
JMX server is enabled by default so property is optional
monitorjmxserverenabled=true
JMX servers host name
underscore in JMX servers hostname is not valid eg XXX_YZW
monitorjmxserverhost=slc08ggj
Port that is bound by the JMX server
monitorjmxserverport=5502
JMX servers user
monitorjmxserveruser=oggmsjmxusr
monitorjmxserveruser=jmxusr
Whether internal components are exposed as MBeans - useful for troubleshooting
monitorjmxinternalmbeansenabled=false
Senders nameemail Mr Postman ltfoogoldengatecomgt
monitorsmtpfrom=Oracle GoldenGate Monitor ltoracleslc08ggjusoraclecomgt
SMTP servers hostnameip
monitorsmtphost=internal-mail-routeroraclecorpcom
SMTP servers port
monitorsmtpport=25
SMTP secure mode flag
monitorsmtpsecure=false
SMTP username for auth
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
30
monitorsmtpuser=
Whether email alerts are generated or not
monitorsmtpalertsenabled=true
Number of attempts before giving up (0 or negative numbers means unlimited attempts)
monitordefault_agent_connectionmax_attempts=0
Interval (in seconds) between each attempt
monitordefault_agent_connectioninterval=30
interval (in seconds) before each attempt to reconnect (after connection was broken)
monitordefault_agent_connectionreconnect_interval=5
The version of meta-data currently supported by CM when the agents attempt to register
monitorsupportedagentmetadataversion=10
Whether SNMP alerts are enabled or not
monitorsnmpalertsenabled=true
Number of threads for the event dispatcher
monitoreventsdispatcherthreads_size=30
Flavor of the EclipseLink dialect
This property underlines the database that eclipselink will be talking to
Please use this property value when the Monitor repository database is Oracle
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseOraclePlatform
Please use this property value when the Monitor repository database is MySql
eclipselinktarget-database=orgeclipsepersistenceplatformdatabaseMySQLPlatform
EclipseLink weaving mode
eclipselinkweaving=static
Enable this property to create database objects on server re-start if the
administrator wants to re-point the server install to a new database
eclipselinkddl-generation=create-tables
Interval for Interval Renderer in seconds To disable interval renderer set to 0
monitorwebrendering_interval=15
Whether CLI (Command Line Interface) alerts are enabled or not
monitorclialertsenabled=true
Time out in milli seconds for Solution Discovery to pick up events
monitorcmeventtimeout=2000
Monitor SSL Enabled property
monitorssl=false
Keystore file - value for SSL property javaxnetsslkeyStore
monitorkeystorefile=monitorKeyStore
truststore file - value for SSL property javaxnetssltrustStore
monitortruststorefile=jagentKeyStore
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
31
Maximum events before Solution Discovery to pick up
monitorcmeventmaxsize=1000
SSO WEB PARAMETERS
This property specifies the SSO (Single Sign On) Log Out URL
monitorssoLogOutUrl=oamssologouthtmlend_url=monitor
Monitor Agent Property File
jagenthost Host name of the machine where jAgent is running
Note This host name has to be reachable from Monitor Server
jagenthost=localhost
jagentjmxport jAgents JMX port number
jagentjmxport=5555
intervalregular intervalquick
jAgents regular and quick polling interval for new
Monitoring Point values
Default values are 60 and 30 seconds
intervalregular=60
intervalquick=30
monitorhost Monitor Server host name
Note This property has to be the same with the property
monitorjmxserverhost in monitorproperties file
on Monitor Server side
monitorhost=localhost
monitorjmxport Monitor Server JMX port number
monitorjmxport=5502
monitorjmxusername Monitor Server JMX username
This is the JMX username defined during Monitor Installation
monitorjmxusername=oggmsjmxusr
jagentusername jAgent username
It can be any name This jAgent username will be passed to
Monitor Server during jAgent registration
jagentusername=oggmajmxusr
regretryinterval jAgent incremental registration
retry interval in seconds when connection exception
occurs while jAgent is connecting to Monitor Server for the
first time
Default value is 60 seconds
regretryinterval=10
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
32
instancequeryinitialinterval
If only manager process is running jAgent will wait for
15 seconds by default before starting to register
to Monitor Server After this waiting period of time
if there are still no other running processes such as
extract and replicat beside the manager process JAgent will
go ahead and register to Monitor Server
instancequeryinitialinterval=5
incrementalregistrationquietinterval
jAgent will incrementally register to Monitor Server after
a new process is configured However jAgent will wait for
a period of 5 seconds by default before each
incremental registration started
incrementalregistrationquietinterval=5
maximummessageretrieval
Maximum number of message to retrieve from cagentcore when
jagent starts
maximummessageretrieval=500
mgrhost Host name of the machine where Manager is running
Note This host name has to be reachable from JAgent
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrhost=localhost
mgrport Manager port number
There is no need to define this property if JAgent is
running on the same machine with OGG Deployment
mgrport=7089
jagentrmiport
RMI Port which EM Agent will use to connect to JAgent
RMI Port will only be used if agenttypeenabled=OEM
jagentrmiport=5559
agenttypeenabled Choose either OEM or OGGMON
Choosing OGGMON will allow JAgent to register to
Monitor Server and JMX RMI connector will not be enabled
Choosing OEM will enable JMX RMI connector which will be used
by EM Agent to connect to JAgent and JAgent will not register
to Monitor Server
agenttypeenabled=OGGMON
statuspollinginterval polling interval for status changes
in second Newly added process will be detected based on this
polling intervalDefault is 5 seconds
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
33
statuspollinginterval=5
messagepollinginterval polling interval for message
changes in second Default is 5 seconds
messagepollinginterval=5
This property is not being used at the moment
regretrytimes=-1
jagent backward compatibility
jagentbackwardcompatibility=false
Start SSL Properties
jagent SSL Enabled property
jagentssl=false
keystore file - value for SSL property javaxnetsslkeyStore
jagentkeystorefile=jagentKeyStore
truststore file-value for SSL property javaxnetssltrustStore
jagenttruststorefile=jagentKeyStore
End SSL Properties
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
34
Appendix B ndash Sample OGG Monitor Alert Email
These are sample OGG Monitor Alert Notification emails generated by Monitor Server that were
configured and defined in the OGG Monitor Alert Definition page
Monitor Alter Definition Name Capture Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 528 PM
To Mike Papio
Subject Capture Latency on QTPCA
Alert Capture Latency occured on QTPCA at Mon Aug 25 202746 EDT 2014
The alert was triggered because
Lag = 4080 sec
Additional Information
Group Name QTPCA
Lag 4080 sec
Status RUNNING_STATE
Total Operations 465822589
Delta Operations Per Second 20213
Seconds Since Last OGG Checkpoint 31
Checkpoint Position Current read position
Sequence 1615
RBA 16235308
Timestamp 2014-08-25 202643000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 615 PM
To Mike Papio
Subject Delivery Latency on RTPCA
Alert Delivery Latency occured on RTPCA at Mon Aug 25 211433 EDT 2014
The alert was triggered because
Lag = 3170 sec
Additional Information
Group Name RTPCA
Lag 3170 sec
Status RUNNING_STATE
Total Operations 469332254
Delta Operations Per Second 12923
Seconds Since Last OGG Checkpoint 35
Checkpoint Position Current read position
Sequence 1627
RBA 9694203
Timestamp 2014-08-25 211359000157
Extract Trail dirdatzp
Monitor Alter Definition Name Solution Latency -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Monday August 25 2014 300 PM
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
35
To Mike Papio
Subject Solution Latency on Solution2
Alert Solution Latency occured on Solution2 at Mon Aug 25 175954 EDT 2014
The alert was triggered because
Lag = 9170 sec
Additional Information
Lag 9170 sec
Status RUNNING_STATE
Monitor Alter Definition Name Capture Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 116 PM
To Mike Papio
Subject Capture Status on PTPCA
Alert Capture Status occured on PTPCA at Fri Aug 29 161629 EDT 2014
The alert was triggered because
Status = KILLED_STATE
Additional Information
Group Name PTPCA
Status KILLED_STATE
Lag 0000 sec
Total Operations 475361976
Delta Operations Per Second 1775
Seconds Since Last OGG Checkpoint 20
Checkpoint Position Current read position
Sequence 1630
RBA 41313092
Timestamp 2014-08-25 213149000000
Extract Trail dirdatze
Monitor Alter Definition Name Delivery Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Wednesday August 27 2014 902 AM
To Mike Papio
Subject Delivery Status on RTPCA
Alert Delivery Status occured on RTPCA at Wed Aug 27 120200 EDT 2014
The alert was triggered because
Status = FORCESTOP_STATE
Additional Information
Group Name RTPCA
Status FORCESTOP_STATE
Lag 0000 sec
Total Operations 470656637
Delta Operations Per Second 2196
Seconds Since Last OGG Checkpoint 30
Checkpoint Position Current read position
Sequence 1631
RBA 25704344
Timestamp 2014-08-25 213149000693
Extract Trail dirdatzp
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
36
Monitor Alter Definition Name Solution Status -----Original Message-----
From Oracle GoldenGate Monitor [mailtooracleslc08ggjusoraclecom]
Sent Friday August 29 2014 117 PM
To Mike Papio
Subject Solution Status on Solution2
Alert Solution Status occured on Solution2 at Fri Aug 29 161644 EDT 2014
The alert was triggered because
Status = ABEND_STATE
Additional Information
Status ABEND_STATE
Lag 0000 sec
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410
Oracle GoldenGate Best Practices Configuring Oracle GoldenGate Monitor 12c
37
Oracle GoldenGate Best Practices Configuring
Oracle GoldenGate Monitor 12c
August 2014
Author Mike Papio
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2012 Oracle andor its affiliates All rights reserved This document is provided for information purposes only and the
contents hereof are subject to change without notice This document is not warranted to be error-free nor subject to any other
warranties or conditions whether expressed orally or implied in law including implied warranties and conditions of merchantability or
fitness for a particular purpose We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document This document may not be reproduced or transmitted in any form or by any
means electronic or mechanical for any purpose without our prior written permission
Oracle and Java are registered trademarks of Oracle andor its affiliates Other names may be trademarks of their respective
owners
AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International Inc UNIX is a registered trademark licensed through XOpen
Company Ltd 0410