Oracle GoldenGate Best Practices: Configuring Oracle GoldenGate Monitor 12c

Transcription

1 An Oracle White Paper August 2014 Oracle GoldenGate Best Practices: Configuring Oracle GoldenGate Monitor 12c Document ID:

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 Install Oracle JDK 7 Update 15 or higher Install WebLogic Server 12c (12.1.3) Install Database Software to be used for Repository Execute the OGG Monitor Server Installer Execute the WebLogic Repository Creation Utility (RCU) Execute the WebLogic Configuration Utility for Monitor Start the WebLogic Admin Server & Monitor Server Create OGG Monitor Admin User in WebLogic OGG Monitor Agent Installation Steps Make sure Java 7 update 15 or higher exist on the server Execute the Monitor 12c Installer to install the Agent Create the OGG Monitor Agent Instance for the OGG Core Create the Wallet Credentials for the Monitor Agent Instance Enable Monitoring support on the OGG Core Instance Create the Datastore to persist monitoring data CONFIGURATION Monitor Server monitor.properties Monitor Agent Config.properties

3 Monitor Server Web Interface Monitoring Points OGG Objects Capture Metrics Delivery Metrics Solution Metrics Alert Notification Configure Alert Definition Multiple OGG Monitor Agent Instances REFERENCES APPENDIX A SAMPLE OGG MONITOR CONFIGURATION FILES Monitor Server Property File Monitor Agent Property File APPENDIX B SAMPLE OGG MONITOR ALERT Monitor Alter Definition Name: Capture Latency Monitor Alter Definition Name: Delivery Latency Monitor Alter Definition Name: Solution Latency Monitor Alter Definition Name: Capture Status Monitor Alter Definition Name: Delivery Status Monitor Alter Definition Name: Solution Status

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 4

5 Executive Overview This document is an introduction to Oracle GoldenGate s 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 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 6.5 for the Operating System and Oracle Database Release 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 , SNMP, and CLI clients. 5

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. 6

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 this can also be downloaded from Oracle edelivery site under the Fusion Middleware 12c Media Pack named Oracle Fusion Middleware 12c ( ) Infrastructure Install anyone of the following Database Software for the Repository o Oracle 11gR1, Oracle 11gR2, or Oracle 12c o MySQL 5.5 Monitor Agent o MS SQL Server 2008 or MS SQL Server 2012 Here are the 3 major prerequisites needed for installing the OGG Monitor Agent component: The Oracle GoldenGate Core product version 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. 7

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 (12.1.3) 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 Oracle Fusion Middleware Infrastructure 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 5.5 MySQL 5.5 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. 8

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 Installation Screens for Oracle GoldenGate Monitor 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 Repository Creation Utility (RCU) Screens for Oracle GoldenGate Monitor 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 Configuration Wizard Screens for Oracle GoldenGate Monitor documentation link. 9

10 7. Start the WebLogic Admin Server & 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 startweblogic.sh can be found in $MW_HOME/user_projects/domains/base_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 startmanagedweblogic.sh 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_HOME/user_projects/domains/base_domain/bin directory. Sample Syntax for the startup script: /u01/app/oracle/product/wls/user_projects/domains/base_domain/bin/startmanagedweb Logic.sh MONITORSERVER_server1 10

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 there s no OGG Monitor Admin defined in the system, however there s 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 Security Realms under the Domain Structure. 11

12 C. Select and Click myrealm under the Summary of Security Realms. D. Select and Click the Tab Users and Groups under Settings for myrealm. 12

13 E. Select and Click New 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 ggadmin. 13

14 G. You will see a message User created successfully, and then click the username ggadmin to go to the ggadmin user page. H. Select and Click the Groups tab to go to the group role page and start assigning group roles to ggadmin user group. 14

15 I. Under Available Parent Group select and click OGGAdministrator, OGGOperator, OGGPowerOperator, and OGGSuperAdmin and click the > sign to move it to the Chosen column. J. Now, you will see those Group Roles under the Chosen columns, then select and click Save to update the security settings for ggadmin user. 15

16 K. Now, you will see a message Settings updated successfully, at this point you are done with the WebLogic Admin console and you can select and click Log Out to exit. For more detailed information, see Installing and Configuring Oracle GoldenGate Monitor 12c. 16

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 there s 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 Agent Install 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 Installation Screens for Oracle GoldenGate Monitor Agent 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_instance.sh 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. 17

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_util.sh 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 ENABLEMONITORING parameter must be added, if it doesn t 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 doesn t 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 Installing, Configuring and Upgrading Oracle GoldenGate Monitor 12c Agent. 18

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 monitor.properties Unless otherwise specified, by default, the WebLogic Server Configuration Wizard creates the domain in the FMW_HOME/user_projects/domains/base_domain directory, so the monitor.properties file will resides by default on FMW_HOME/user_projects/domains/base_domain/config/monitorserver/cfg. Most of the time, the only thing you need to modify is the JMX Server properties and SMTP Alert properties for Alert notification to customize it for your environment. JMX Server Properties: monitor.jmx.server.host=hostname monitor.jmx.server.port=port The hostname is the name of the server on which you are running the Monitor Server (e.g., slc08ggj) and port is the number of the server s listening port (e.g., 5502) SMTP Alert Properties: monitor.smtp.alerts.enabled=true monitor.smtp.secure=false o Set this to true if the SMTP server you ll be using is configured to use secured protocol such as SSL or TLS when connecting. monitor.smtp.host=hostname monitor.smtp.port=port monitor.smtp.from=sender_name_ The hostname is the name of the SMTP Mail server on which you are running the Mail Server (e.g., internal-mail-router.oraclecorp.com), port is the number of the SMTP server s mail listening port (e.g., 25, 443), sender_name_ is the Sender s Name and you want to set on the alert (e.g., OGG Admin <oggadmin@slc08ggj.us.oracle.com>). If you need to support and configure the Alert Notification for SNMP and CLI, then see the following documentation links: Configure SNMP Alert Oracle GoldenGate Monitor 12c: Configure SNMP Alert Configuring CLI Alert Oracle GoldenGate Monitor 12c: Configure CLI Alert 19

20 For more detailed information on the rest of the properties defined in the OGG Monitor Server monitor.properties file, see the Administering Oracle GoldenGate Monitor12c: Monitor Server Properties documentation link. Monitor Agent Config.properties The configuration file Config.properties for the Monitor Agent is located in the cfg directory where the Monitor Agent instance was created (e.g. /ogg/core/v1121/mon_agent/cfg). Most of the time, the following properties are the ones that needs to be customized: jagent.host=hostname jagent.jmx.port=port monitor.host=monitor_host_server monitor.jmx.username=jmxuser jagent.username=jagentuser The hostname is the name of the server on which you are running the Monitor Agent (e.g., slc08ggk) and port is the number of the server s listening port (e.g., 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 monitor.jmx.server.host 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 GLOBALS file exist in the OGG core instance directory and there s an entry ENABLEMONITORING 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 info datastore command within ggsci. If you need to create the data store, you can create it via the create datastore command within ggsci. For more detailed information on the rest of the properties defined in the OGG Monitor Agent Config.properties file, see the Administering Oracle GoldenGate Monitor12c: Monitor Agent Properties documentation link. 20

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 (e.g. 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 Here s 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:. 21

22 Here s 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 Overview of the Oracle GoldenGate Monitor Interface documentation link. Monitoring Points Each Oracle GoldenGate object or component is associated with a specific set of Monitoring points or Monitoring Metrics/Attributes. 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 metrics/attributes to monitor for each OGG object. For simplicity purposes, it s best to start with the most common OGG objects and it s 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 represents an Oracle GoldenGate Extract group. This can be an Online Change Capture process or a DataPump Capture process. Delivery represents an Oracle GoldenGate Replicat group. This is the Delivery process. 22

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 Solution : 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 OGG Monitor Attributes documentation link. 23

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 which is Latency and if the process is still running 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: 24

25 Configure Alert Definition Here s how to configure an Alert Definition for the Capture Latency Alert Notification. 1. From the OGG Monitor Web Interface, select and click Alert Definition tab. 2. From the Alert Definition menu, select and click the button New Alert Definition. 25

26 3. From the New Alert Definition, type in the (1) Definition Name you want for the alert definition, in this case, we will use Capture Latency. Select the (2) Alert Severity ( Warning or Error ), in this case we use Warning. 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 Capture and the (5) Attribute to use for the criteria selection is Lag. Use 3 seconds for the (6) Value of Lag. Next, scroll down and go to the User Assignment. 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 ggadmin, so select and click ggadmin and move it to the Assigned Users section by clicking the > button. Next, scroll down and go to the Object Assignment. 26

27 5. For the Object Assignment section, select and click the button for Assign to all objects of this object type to cover all Capture processes. Next, scroll down and go to the Additional Notice Attributes section. 6. From the Additional Notice Attributes section, (1) scroll down the list of the Available Attributes 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 Additional Attributes section. 7. Verify that your selected attributes were moved to the Additional Attributes section, and then select and click Submit (1) to create the New Alert Capture Latency Definition 27

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_instance.sh. You have to make sure that you create them in unique directories. For example, you might use /u01/ogg/core/v _ora11g/mon_agent and /u01/ogg/core/v121200_ora12c/mon_agent. For each agent instance, the jmx.jagent.port value in each Config.Properties must be unique for each instance. Sample /u01/ogg/core/v _ora11g/mon_agent instance creation: Sample /u01/ogg/core/v _ora12c/mon_agent instance creation: 28

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 Sample OGG Monitor Configuration Files This is a sample working configuration/property files for both OGG Monitor Server and Agent. Monitor Server Property File # Copyright (c) 2009, 2014, Oracle and/or its affiliates. All rights reserved. #Oracle GoldenGate Monitor #JMX server is enabled by default, so property is optional monitor.jmx.server.enabled=true #JMX server's host name # underscore in JMX server's hostname is not valid e.g. XXX_YZW monitor.jmx.server.host=slc08ggj #Port that is bound by the JMX server monitor.jmx.server.port=5502 #JMX server's user #monitor.jmx.server.user=oggmsjmxusr monitor.jmx.server.user=jmxusr #Whether internal components are exposed as MBeans - useful for troubleshooting #monitor.jmx.internal.mbeans.enabled=false #Sender's name/ Mr. Postman <foo@goldengate.com> monitor.smtp.from=oracle GoldenGate Monitor <oracle@slc08ggj.us.oracle.com> #SMTP server's hostname/ip monitor.smtp.host=internal-mail-router.oraclecorp.com #SMTP server's port monitor.smtp.port=25 #SMTP secure mode flag monitor.smtp.secure=false #SMTP username for auth 29

30 monitor.smtp.user= #Whether alerts are generated or not monitor.smtp.alerts.enabled=true #Number of attempts before giving up (0 or negative numbers means unlimited attempts) #monitor.default_agent_connection.max_attempts=0 #Interval (in seconds) between each attempt monitor.default_agent_connection.interval=30 #interval (in seconds) before each attempt to reconnect (after connection was broken) #monitor.default_agent_connection.reconnect_interval=5 #The version of meta-data currently supported by CM when the agents attempt to register monitor.supported.agent.metadata.version=1.0 #Whether SNMP alerts are enabled or not monitor.snmp.alerts.enabled=true #Number of threads for the event dispatcher monitor.events.dispatcher.threads_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. eclipselink.target-database=org.eclipse.persistence.platform.database.oracleplatform #Please use this property value when the Monitor repository database is MySql. #eclipselink.target-database=org.eclipse.persistence.platform.database.mysqlplatform #EclipseLink weaving mode eclipselink.weaving=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 #eclipselink.ddl-generation=create-tables #Interval for Interval Renderer in seconds. To disable interval renderer set to 0 #monitor.web.rendering_interval=15 #Whether CLI (Command Line Interface) alerts are enabled or not monitor.cli.alerts.enabled=true #Time out in milli seconds for Solution Discovery to pick up events monitor.cm.event.timeout=2000 #Monitor SSL Enabled property monitor.ssl=false #Keystore file - value for SSL property javax.net.ssl.keystore monitor.keystore.file=monitorkeystore #truststore file - value for SSL property javax.net.ssl.truststore monitor.truststore.file=jagentkeystore 30

31 #Maximum events before Solution Discovery to pick up monitor.cm.event.max.size=1000 # SSO WEB PARAMETERS # This property specifies the SSO (Single Sign On) Log Out URL. monitor.ssologouturl=/oamsso/logout.html?end_url=/monitor Monitor Agent Property File ## jagent.host: Host name of the machine where jagent is running ### ## Note: This host name has to be reachable from Monitor Server ### jagent.host=localhost ## jagent.jmx.port: jagent's JMX port number ### jagent.jmx.port=5555 ## interval.regular, interval.quick: ### ## jagent's regular and quick polling interval for new ### ## Monitoring Point values. ### ## Default values are 60 and 30 seconds ### interval.regular=60 interval.quick=30 ## monitor.host: Monitor Server host name. ### ## Note: This property has to be the same with the property: ### ## monitor.jmx.server.host in monitor.properties file ### ## on Monitor Server side ### monitor.host=localhost ## monitor.jmx.port: Monitor Server JMX port number ### monitor.jmx.port=5502 ## monitor.jmx.username: Monitor Server JMX username ### ## This is the JMX username defined during Monitor Installation ### monitor.jmx.username=oggmsjmxusr ## jagent.username: jagent username ### ## It can be any name. This jagent username will be passed to ### ## Monitor Server during jagent registration. ### jagent.username=oggmajmxusr ## reg.retry.interval: 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 ### reg.retry.interval=10 31

32 ## instance.query.initial.interval: ### ## 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. ### instance.query.initial.interval=5 ## incremental.registration.quiet.interval: ### ## 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. ### incremental.registration.quiet.interval=5 ## maximum.message.retrieval: ### ## Maximum number of message to retrieve from cagent/core when ### ## jagent starts ### maximum.message.retrieval=500 ## mgr.host: 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 ### #mgr.host=localhost ## mgr.port: Manager port number ### ## There is no need to define this property if JAgent is ### ## running on the same machine with OGG Deployment ### #mgr.port=7089 ## jagent.rmi.port ### ## RMI Port which EM Agent will use to connect to JAgent ### ## RMI Port will only be used if agent.type.enabled=oem ### jagent.rmi.port=5559 ## agent.type.enabled : 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. ### agent.type.enabled=oggmon ## status.polling.interval: polling interval for status changes ### ## in second. Newly added process will be detected based on this ### ## polling interval.default is 5 seconds. ### 32

33 status.polling.interval=5 ## message.polling.interval: polling interval for message ### ## changes in second. Default is 5 seconds. ### message.polling.interval=5 ## This property is not being used at the moment reg.retry.times=-1 ## jagent backward compatibility ### jagent.backward.compatibility=false ################## Start SSL Properties ############################ ## jagent SSL Enabled property ### jagent.ssl=false ## keystore file - value for SSL property javax.net.ssl.keystore ### jagent.keystore.file=jagentkeystore ## truststore file-value for SSL property javax.net.ssl.truststore # jagent.truststore.file=jagentkeystore ################### End SSL Properties ############################# 33

34 Appendix B Sample OGG Monitor Alert These are sample OGG Monitor Alert Notification s 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 [mailto:oracle@slc08ggj.us.oracle.com] Sent: Monday, August 25, :28 PM To: Mike Papio Subject: Capture Latency on QTPCA Alert Capture Latency occured on QTPCA at Mon Aug 25 20:27:46 EDT The alert was triggered because: Lag = sec. Additional Information: Group Name: QTPCA Lag: sec Status: RUNNING_STATE Total Operations: Delta Operations Per Second: Seconds Since Last OGG Checkpoint : 31 Checkpoint Position: Current read position: Sequence #: 1615 RBA: Timestamp: :26: Extract Trail:./dirdat/ze Monitor Alter Definition Name: Delivery Latency -----Original Message----- From: Oracle GoldenGate Monitor [mailto:oracle@slc08ggj.us.oracle.com] Sent: Monday, August 25, :15 PM To: Mike Papio Subject: Delivery Latency on RTPCA Alert Delivery Latency occured on RTPCA at Mon Aug 25 21:14:33 EDT The alert was triggered because: Lag = sec. Additional Information: Group Name: RTPCA Lag: sec Status: RUNNING_STATE Total Operations: Delta Operations Per Second: Seconds Since Last OGG Checkpoint : 35 Checkpoint Position: Current read position: Sequence #: 1627 RBA: Timestamp: :13: Extract Trail:./dirdat/zp Monitor Alter Definition Name: Solution Latency -----Original Message----- From: Oracle GoldenGate Monitor [mailto:oracle@slc08ggj.us.oracle.com] Sent: Monday, August 25, :00 PM 34

35 To: Mike Papio Subject: Solution Latency on Solution2 Alert Solution Latency occured on Solution2 at Mon Aug 25 17:59:54 EDT The alert was triggered because: Lag = sec. Additional Information: Lag: sec Status: RUNNING_STATE Monitor Alter Definition Name: Capture Status -----Original Message----- From: Oracle GoldenGate Monitor [mailto:oracle@slc08ggj.us.oracle.com] Sent: Friday, August 29, :16 PM To: Mike Papio Subject: Capture Status on PTPCA Alert Capture Status occured on PTPCA at Fri Aug 29 16:16:29 EDT The alert was triggered because: Status = KILLED_STATE. Additional Information: Group Name: PTPCA Status: KILLED_STATE Lag: sec Total Operations: Delta Operations Per Second: 1775 Seconds Since Last OGG Checkpoint : 20 Checkpoint Position: Current read position: Sequence #: 1630 RBA: Timestamp: :31: Extract Trail:./dirdat/ze Monitor Alter Definition Name: Delivery Status -----Original Message----- From: Oracle GoldenGate Monitor [mailto:oracle@slc08ggj.us.oracle.com] Sent: Wednesday, August 27, :02 AM To: Mike Papio Subject: Delivery Status on RTPCA Alert Delivery Status occured on RTPCA at Wed Aug 27 12:02:00 EDT The alert was triggered because: Status = FORCESTOP_STATE. Additional Information: Group Name: RTPCA Status: FORCESTOP_STATE Lag: sec Total Operations: Delta Operations Per Second: 2196 Seconds Since Last OGG Checkpoint : 30 Checkpoint Position: Current read position: Sequence #: 1631 RBA: Timestamp: :31: Extract Trail:./dirdat/zp 35

36 Monitor Alter Definition Name: Solution Status -----Original Message----- From: Oracle GoldenGate Monitor Sent: Friday, August 29, :17 PM To: Mike Papio Subject: Solution Status on Solution2 Alert Solution Status occured on Solution2 at Fri Aug 29 16:16:44 EDT The alert was triggered because: Status = ABEND_STATE. Additional Information: Status: ABEND_STATE Lag: sec 36

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 U.S.A. Worldwide Inquiries: Phone: Fax: oracle.com \ Copyright 2012, Oracle and/or 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 and/or 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 X/Open Company, Ltd