How To Set Up Monitoring Of GoldenGate Targets Installed On High Availability? [VIDEO] (Doc ID 2070789.1)

Last updated on APRIL 25, 2016

Applies to:

Management Pack for Oracle GoldenGate - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Goal

The goal of this document is to provide the minimum steps required to use high availability features of 

- GoldenGate Monitor Plugin 12.1.0.3.0 for Oracle Enterprise Manager 12c R3+
- GoldenGate Monitor Agent (replaces jagent) 12.1.3.0.4

as well as providing a demo of this new functionality.  

When these versions are used and failover/relocation of GoldenGate targets occur on High Availability deployments
monitoring of such targets will sync automatically.  

With GoldenGate Monitor Plugin 12.1.0.3.0, the Oracle Management Agent (OMA) on the discovery/promotion "node"
is setup as a "master" OMA.  Then, 1 or more OMAs can be setup as "slave" nodes.  If failover occurs, then "slave" OMA on the failover node
detects the GoldenGate started on that node and will report the correct status to OEM console.

This document also contains a video recording/demo of how this process works by showing a target relocation of GoldenGate "app"
to a second node and OEM console sync correctly with a "slave" OMA.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms