Oracle GoldenGate Best Practices: Oracle GoldenGate failover with Clusterware using an agent script

April 11, 2013 | 1 minute read
Text Size 100%:

Introduction

Oracle GoldenGate is often used in mission-critical systems with stringent high availability requirements. In an Oracle to Oracle scenario, minimal latency between the source and the destination databases is important to achieve minimal downtime and minimal data loss in case of a failover. In an Oracle Real Application Cluster (RAC) configuration access to the database is not dependent on the availability of any one of the servers in the cluster. Oracle GoldenGate however could be impacted by the non-availability of a single server since many critical components run only on one of the cluster servers.

Main Article

This document outlines how to achieve high availability for Oracle GoldenGate in a cluster configuration using Oracle Clusterware. Oracle Clusterware will ensure that Oracle GoldenGate can tolerate server failures by moving processing to another available server in the cluster. As a result Oracle GoldenGate processing is dependent on database availability rather than server availability thereby ensuring minimal latency.

The document includes sample code that can be used to configure Oracle Clusterware to manage Oracle GoldenGate manager. The example is generic and can serve as a starting point for a more customized Oracle GoldenGate high availability implementation.

The complete document can be found on the Oracle Support site under the document ID:1313703 1.

Sourav Bhattacharya


Previous Post

Oracle GoldenGate - A Guide to Globalization aspects when working with OGG

Steven George | 1 min read

Next Post


Oracle GoldenGate Best Practices: Oracle GoldenGate with Oracle Data Guard -- Switchover/failover operations

Sourav Bhattacharya | 2 min read