How To Configure Client Failover For Data Guard Connections Using Database Services
Last updated on FEBRUARY 20, 2018
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.
In a Data Guard environment you have primary database which is open in read write mode and the standby database which can be in mount mode or open 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
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