Release Notes for Oracle GoldenGate Monitor
This document introduces Oracle GoldenGate Monitor 12c (184.108.40.206). It comprises the following:
Oracle GoldenGate Monitor doesn’t support MySQL database as RCU database. Oracle GoldenGate for MySQL support is present in Oracle GoldenGate Monitor from a monitoring perspective.
Oracle GoldenGate Monitor supports monitoring OGG for Informix from Oracle GoldenGate Monitor release 220.127.116.11.0 onwards.
A new Java agent for Oracle GoldenGate Monitor 12c (18.104.22.168) with iSeries support was added in Release 22.214.171.124.170425, May 2017.
Support for Monitor JAgent to withstand the Oracle GoldenGate Manager RESTful API unavailability was added.
Support for monitoring instances of Oracle GoldenGate for Big Data was added.
The Monitor UI layout was redesigned for improved information conveyance as follows:
Monitor Home Page Enhancements
Data and Alerts View is renamed to Metrics and Alerts
Historical Data and Alert History Tabs are consolidated as the History Tab
Alert Definition is renamed to Alert Management
Metrics and Alerts Enhancements
Clicking on an Instance node results in the following tabs displaying in right-hand panel replacing the 'Instance' diagram, Attributes table, and Alerts table:
Process Metrics Tab
Manager Metrics Tab
Capture Node Enhancements
Clicking on a Capture node results in the following tabs displaying in right-hand panel replacing the Capture diagram, Attributes table, and Alerts table.
Delivery Node Enhancements
Clicking on Delivery node results in the following tabs displaying in right-hand panel replacing the Delivery diagram, Attributes table, and Alerts table.
Database Node Enhancements
Clicking on a Database node results in the Metrics tab displaying in right-hand panel replacing the Database's diagram, Attributes table, and Alerts table.
Trial Node Enhancements
Clicking on a Trial node results in the Metrics tab displaying in right-hand panel replacing the Trial diagram, Attributes table, and Alerts table.
Instance Node Enhancements
Clicking on an Instance Node results in the Configuration tab displaying in right-hand panel replacing the Trial diagram, Attributes table, and Alerts table.
The mgr.prm and GLOBALS subtabs are displayed on the Configuration Tab. The
mgr.prm subtab displays the contents of this file. You can refresh the contents of the
mgr.prm file using the Refresh button and edit it using the Edit button.
Capture' Node/Delivery Node – 'Configuration' Tab
The Capture process related parameter file is displayed on the Configuration' Tab You can refresh the contents of this file using the Refresh button and edit it using the Edit button.
The configuration of Email, SNMP, and CLI for alert actions was redesigned so that the User Interface (UI) is used.
The Solution Graph was enhanced to bookend databases.
The instance diagram is replaced by a tabular layout.
The Problem Summary and Solution title icon were removed.
The UI tab and subtabs appearance was modified to condense the information for better classification and ease of use.
Compact domain support was replaced with Extended Domain support for SQL Server.
Ability to run GGSCI commands from the UI was added.
Ability to alert on more Monitor Points was added.
In addition to the
Message.Severity attributes, you can now configure alerts using the
Message.Text attribute. This new metric was added in the Metrics drop-down list on the Alert Definition Tab.
Monitor Alerts now include additional existing monitoring points. By default, all Monitor Alerts include the following Oracle GoldenGate Monitor instance Metrics for the 'Instance', 'Capture', and 'Delivery' object types :
OGG Instance Details: OGG Hostname =abc.host.com OGG Working Directory = /root/core OGG Manager Port = 7650
Instance Level security for the Alert Module.
Ability to run multiple Monitor Agents to services both Oracle GoldenGate Monitor and Oracle GoldenGate Monitor Enterprise Management Plug-In.
For more information on these feature and additional links to their documentation elsewhere in the product library, see "What's New?" in Administering Oracle GoldenGate Monitor.
Oracle GoldenGate provides a cohesive platform for a sharded Oracle Database.
Sharding is only available with Oracle Database 126.96.36.199 or later, over a secure MA deployment. You need to make sure that you setup your SSL certificate before you setup sharding. To configure a sharded Oracle Database with Oracle GoldenGate, see Configuring Sharding for Oracle GoldenGate.
Advantages of Oracle GoldenGate Sharding
Oracle GoldenGate provides a complete data replication platform for sharded databases.
This is a powerful capability with the following advantages:
Horizontally partitions data and workload across numerous discrete Oracle databases that do not share hardware or software
Enables automatic partitioning and replication, elastic scaling, rebalancing, data-dependent routing for single-shard and cross-shard queries
Provides an enterprise-class database platform for new generation developers who:
Explicitly design applications to scale linearly with fault tolerance
Assume schema flexibility with JSON
See benefits in the power of relational SQL and ACID
Active replication within and across shardgroups
Flexible Deployment, which could have single shardgroup for high availability, multiple shardgroups with varying replication factors
Different shardgroups can have different replication factors, different number of shards, different hardware platforms and OS versions, or different database versions and patch sets.
Oracle GoldenGate Monitor 12c (188.8.131.52.0) requires that the following are installed:
Java SE, JDK 8u40 and greater
WebLogic Server 12c (12.2.1) with JRF
One of the following supported databases:
Oracle 11gR2, 12c
Microsoft SQL Server 2008, 2012
For more information, see "Preparing to Install" in Installing and Configuring Oracle GoldenGate Monitor.
This section contains information about bugs that have been corrected. For questions on specific bugs or ticket numbers, consult Oracle Customer Support.
SR is the Oracle Support SR number, and
BugDB is the bug identification number. The information in this section is divided into the following releases:
Bug 22179784 - Edit Big Data Handler Properties Files from Monitor
The issue of editing the Big Data parameter properties files was fixed.
Bug 20714185 - Improve Oracle GoldenGate Monitor Server's Data Purging Options
The issue with the data purging options has been fixed. After applying the Oracle GoldenGate Monitor patch 184.108.40.206.171115 (PS2 BP3), optionally, you can execute a table re-partition script to optimize the history purging feature when the Oracle GoldenGate Monitor uses the Oracle database. Once the script execution is completed, it reduces the time needed to purge historical data by using the Oracle GoldenGate Monitor server user interface.
Stop the Oracle GoldenGate Monitor Server.
Apply patch 220.127.116.11.171115 (PS2 BP3) if you have not yet applied it.
Run the following script as
SYSDBA user and enter the Oracle GoldenGate Monitor Repository User Name when asked for parameter 1 –
Run the following script as Monitor Repository User –
Start the Oracle GoldenGate Monitor Server.
BUG 26630294 - OEM Plug-in Support for Non-default Report and Parameter File Directory Location
The issue with the Oracle GoldenGate Monitor Java Agent parameter files not being visible to the customers was fixed.
Bug 25798253- Need to Make JAgent Compatible with Oracle GoldenGate 12.3 Classic Mode
Starting with the Oracle GoldenGate Monitor patch 18.104.22.168.171115 and for the upcoming releases, JAgent is compatible with the Oracle GoldenGate 12c (22.214.171.124) Classic Architecture.
Bug 25507045 - The goldengate.jar script hangs, unable to discover OGG/sql server targets OEM 13c
A reentrant lock was added for an MBeans update to correct this issue.
Bug 21909349 - Unable to create alerts after upgrading MSSQL MON121300 to 122100
An issue where alerts were not created after upgrading from MSSQL MON121300 to MSSQL MON122100 was fixed.
Bug 21943985 - Pre-upgrade alerts throwing "An unresolvable error " after upgrading to 122100
An issue where the pre-upgrade alert An unresolvable error was thrown after upgrading to 122100 was fixed.
Bug 22004103 - Handling of missing metric by JAgent
An issue with JAgent and missing metric in Oracle GoldenGate Core was fixed.
Bug 23564507 - JAgent should stop if RMI/JMX ports are not available
An issue where JAgent continued to run without available RMI/JMX ports was fixed.
Bug 23756494 - Unavailability of Manager process by JAgent
An issue with unavailability of the Manager process was fixed.
Bug 24324655 - MON:ogg_agent.log includes warning related to monitor.jmx.port even in OEM mode
An issue where the
MON:ogg_agent.log included warnings related to
monitor.jmx.port in OEM mode was fixed.
Bug 24477119 - Instance status changing from "Stopped" to "Running" after Re-login
An issue where the status of Oracle GoldenGate Monitor instance was changed from Stopped to Running after re-login was fixed.
Bug 24525589 - JAgent needs to print its version in the ogg_jagent.log with any debug level
An issue where the JAgent version was not updated in the
ogg_jagent.log was fixed.
Bug 25101869 - MON:ogg.agent.log is not generated if JAgent is started by startMonitorAgtInstance.sh
An issue where the
MON:ogg.agent.log was not generated when JAgent was started using startMonitorAgtInstance.sh was fixed.
Bug 25289835 - JAgent support for remote monitoring using JMX
You can use JAgent to remotely monitor in OEM mode using static ports. By default, remote monitoring is disabled. You can enable this by changing the two properties
jmx.broker.port=default (any valid port number).
Bug 23285087 - Issue with Query String, unable to discover OGG
An issue with the query string where Oracle GoldenGate Monitor was not able to discover Oracle GoldenGate targets was fixed.
Bug 22593701 - Spelling issue in StartMonitorAgent Script
A spelling issue in
startMonitorAgentInstance.sh was fixed.
Bug 20545508 - JAgent does not work with Oracle GoldenGate for Java adapter
An issue where JAgent was not functioning properly with Oracle GoldenGate for Java adapter was fixed.
This chapter describes issues that are known to exist in Oracle GoldenGate Monitor. The information in this section is divided into the following releases:
The following is a Known Issue in this version:
Bug 26577251 - Monitor Server writes too many logs in Archive log.
Ensure not to install monitor server with the Archive log mode on. If you install the Monitor server with the Archive mode on, then the archive log growth is relatively higher. Therefore, you need to clean up archive log periodically. To avoid this, it is recommended that you to install the Monitor server with no archive mode.
Bug 25507045 - goldengate.jar script stops responding and is unable to discover OGG/SQL Server targets in OEM 13c
You may encounter intermittent thread deadlock issue with Oracle GoldenGate Monitor Agent during target discovery on Windows platform.
Bug 24735971 - Jagent log display "Invalid username/password" after upgrade to 126.96.36.199.0
JAgent log can display “Invalid username/password after upgrade to 188.8.131.52.0. As a workaround, after Oracle GoldenGate Monitor Server upgrade, copy the following three property values from
monitor.properties file located in
The property values to be replaced are:
Next, manually verify all the other property values in
monitor.properties file and replace them with the older values from
Schema upgrade not required for Oracle GoldenGate Monitor
Schema upgrade from 184.108.40.206.0 to 220.127.116.11.0 is not required and messages ALREADY_UPGRADED and Upgrade not necessary are displayed during readiness check. This is the standard functionality.
oggmon.properties in the WebLogic Server Domain After T2P
After T2P, if the target machine does not have the
oggmon.properties file in the
/cfg directory, then you must run the
updateOGGMonitorConfig script on target machine in T2P.
Jagent on Windows Does Not Connect to the Monitor Server.
For Windows, if the JAgent s not connecting to the Monitor Server, then you need to add the absolute Java JDK8 path explicitly in the
For DB2 on Z/OS: JAgent Stops Unexpectedly
If JAgent should stop unexpectedly, modify the memory options in the
jagent. prm file using these steps:
jagent.prm file in the
Xmx memory options then change them to
Go to the Oracle GoldenGate Core GGSCI console, and stop the Oracle GoldenGate Monitor Agent by executing the
GGSCI> stop jagent
Start JAgent from GGSCI:
GGSCI> start jagent
For more information, see the following documents in the Oracle GoldenGate Monitor 12c (18.104.22.168.170215) documentation set:
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Fusion Middleware Release Notes for Oracle GoldenGate Monitor, 12c (22.214.171.124)
Copyright © 2011, 2017, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
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. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.