How To Configure Client Failover For Data Guard Connections Using Database Services
(Doc ID 1429223.1)
Last updated on MARCH 12, 2021
Applies to:Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
In a Data Guard environment primary database is open in read write mode and the standby database in read only mode for reporting purpose.
This document describes how to setup clients to connect to Data Guard databases (primary and standby) and configure automatic client failover such that in case there is role change due to switchover or failover, the client connections should still be valid i.e. the clients that need to connect to read only standby should always connect to the current standby irrespective of which database in the Data Guard configuration is currently in standby role and same for primary connections.
This goal is achieved via database services.
In 11gR2, we have the concept of role-based database services. For Data Guard environments running older release, this is achieved via a database startup trigger.
Pre 11.2 Configuration
11.2 or later Configuration
Also check below whitepaper for latest information on this topic:
Client Failover Best Practices for Highly Available Oracle Databases
Application Continuity with Oracle Database12c Release 2
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Pre 11.2 Configuration:|
|Configuration in 11.2 or later release:|