Saturday, 2 July 2016

TAF In DR configuration

Configuring Transparent Application Failover (TAF) with Data Guard
Background
Transparent Application Failover (TAF) can be configured with Data Guard to allow clients who connect through a TAF specific Service Name to always connect to the active database.   This greatly simplifies failovers and switchovers as no application, Oracle Service Name (i.e. tnsnames.ora), or DNS entries need to be adjusted.  Rather client connections will automatically and seamlessly connect to the currently active database.

TAF connections rely on database "services" and the parameters for these services differ depending on whether an OCI or JDBC connection is used. Consequently unique OCI and JDBC services are recommended.

The Oracle NET Service Name simply lists both PRIMARY and STANDBY databases - once TAF is configured correctly the connection will automatically be routed to whichever database is active.

No comments:

Post a Comment

Optimizer Access Paths using Indexes

Introduction In this tutorial you will use the Optimizer Access Paths for the following cases (scenarios): Case 1: With and Without Index Ca...