Sie sind auf Seite 1von 8

Configuring Transparent Application Failover

Transparent Application Failover (TAF) instructs Oracle Net to fail over a failed connection to a different
listener. This enables the user to continue to work using the new connection as if the original connection
had never failed.

TAF involves manual configuration of a net service name that includes the FAILOVER_MODE parameter
included in the CONNECT_DATA section of the connect descriptor.

This section contains the following topics:

 About Transparent Application Failover

 What Transparent Application Failover Restores
 About FAILOVER_MODE Parameters
 Implementing Transparent Application Failover
 Verifying Transparent Application Failover

About Transparent Application Failover

TAF is a client-side feature that allows clients to reconnect to surviving databases in the event of a
failure of a database instance. Notifications are used by the server to trigger TAF callbacks on the client-

TAF is configured using either client-side specified Transparent Network Substrate (TNS) connect string
or using server-side service attributes. If both methods are used to configure TAF, then the server-side
service attributes supersede the client-side settings. Server-side service attributes are the preferred way
to set up TAF.

TAF can operate in one of two modes, Session Failover and Select Failover. Session Failover re-creates
lost connections and sessions. Select Failover replays queries that were in progress.

When there is a failure, callback functions are initiated on the client-side using Oracle Call Interface (OCI)
callbacks. This works with standard OCI connections as well as Connection Pool and Session Pool

TAF operates with Oracle Data Guard to provide automatic failover. TAF works with the following
database configurations to effectively mask a database failure:

 Oracle Real Application Clusters

 Replicated systems
 Standby databases
 Single instance Oracle database
See Also:

 Oracle Real Application Clusters Installation and Configuration Guide

 Oracle Real Application Clusters Administration and Deployment Guide
 Oracle Call Interface Programmer's Guide for more details on callbacks, connection pools, and
session pools

What Transparent Application Failover Restores

TAF automatically restores some or all of the following elements associated with active database
connections. Other elements may need to be embedded in the application code to enable TAF to
recover the connection.

 Client-server database connections: TAF automatically reestablishes the connection using the
same connect string or an alternate connect string that you specify when configuring failover.
 Users' database sessions: TAF automatically logs a user in with the same user ID as was used
before the failure. If multiple users were using the connection, then TAF automatically logs
them in as they attempt to process database commands. Unfortunately, TAF cannot
automatically restore other session properties. These properties can be restored by invoking a
callback function.
 Completed commands: If a command was completed at the time of connection failure, and it
changed the state of the database, then TAF does not resend the command. If TAF reconnects in
response to a command that may have changed the database, then TAF issues an error message
to the application.
 Open cursors used for fetching: TAF allows applications that began fetching rows from a cursor
before failover to continue fetching rows after failover. This is called select failover. It is
accomplished by re-running a SELECT statement using the same snapshot, discarding those rows
already fetched and retrieving those rows that were not fetched initially. TAF verifies that the
discarded rows are those that were returned initially, or it returns an error message.
 Active transactions: Any active transactions are rolled back at the time of failure because TAF
cannot preserve active transactions after failover. The application instead receives an error
message until a ROLLBACK is submitted.
 Server-side program variables: Server-side program variables, such as PL/SQL package states,
are lost during failures, and TAF cannot recover them. They can be initialized by making a call
from the failover callback.

See Also:
Oracle Call Interface Programmer's Guide

About FAILOVER_MODE Parameters

The FAILOVER_MODE parameter must be included in the CONNECT_DATA section of a connect

descriptor. FAILOVER_MODE can contain the parameters described in Table 13-4.
Table 13-4 Additional Parameters of the FAILOVER_MODE Parameter

Parameters Description
BACKUP A different net service name for backup connections. A backup should be
specified when using preconnect to pre-establish connections.
DELAY The amount of time in seconds to wait between connect attempts. If RETRIES is
specified, then DELAY defaults to one second.

If a callback function is registered, then this parameter is ignored.

METHOD Setting for fast failover from the primary node to the backup node:

 basic: Set to establish connections at failover time. This option requires

almost no work on the backup server until failover time.
 preconnect: Set to pre-established connections. This provides faster
failover but requires that the backup instance be able to support all
connections from every supported instance.

RETRIES The number of times to attempt to connect after a failover. If DELAY is specified,
then RETRIES defaults to five retry attempts.

If a callback function is registered, then this parameter is ignored.

TYPE The type of failover. Three types of Oracle Net failover functionality are available
by default to Oracle Call Interface (OCI) applications:

 session: Set to failover the session. If a user's connection is lost, then a

new session is automatically created for the user on the backup. This
type of failover does not attempt to recover select operations.
 select: Set to enable users with open cursors to continue fetching on
them after failure. However, this mode involves overhead on the client
side in normal select operations.
 none: This is the default. No failover functionality is used. This can also be
explicitly specified to prevent failover from happening.

Oracle Net Manager does not provide support for TAF parameters. These parameters must be set
Implementing Transparent Application Failover

Do not set the GLOBAL_DBNAME parameter in the SID_LIST_listener_name section of the listener.ora
file. A statically configured global database name disables TAF.

Depending on the FAILOVER_MODE parameters, you can implement TAF in several ways. Oracle
recommends the following methods:

 TAF with Connect-Time Failover and Client Load Balancing

 TAF Retrying a Connection
 TAF Pre-establishing a Connection

TAF with Connect-Time Failover and Client Load Balancing

Implement TAF with connect-time failover and client load balancing for multiple addresses. In the
following example, Oracle Net connects randomly to one of the protocol addresses on sales1-server or
sales2-server. If the instance fails after the connection, then the TAF application fails over to the other
node's listener, reserving any SELECT statements in progress.

TAF Retrying a Connection

TAF also provides the ability to automatically retry connecting if the first connection attempt fails with
the RETRIES and DELAY parameters. In the following example, Oracle Net tries to reconnect to the
listener on sales1-server. If the failover connection fails, then Oracle Net waits 15 seconds before trying
to reconnect again. Oracle Net attempts to reconnect up to 20 times.

TAF Pre-establishing a Connection

A backup connection can be pre-established. The initial and backup connections must be explicitly
specified. In the following example, clients that use net service name to connect
to the listener on sales1-server are also preconnected to sales2-server. If sales1-server fails after the
connection, then Oracle Net fails over to sales2-server, preserving any SELECT statements in progress.
Similarly, Oracle Net preconnects to sales1-server for those clients that use to
connect to the listener on sales2-server.

Verifying Transparent Application Failover

You can query the FAILOVER_TYPE, FAILOVER_METHOD, and FAILED_OVER columns in the V$SESSION
view to verify that TAF is correctly configured. To view the columns, use a query similar to the following:



The output before failover looks similar to the following:


-------------------- ------------- ---------- --- ----------
sales1 NONE NONE NO 11

The output after failover looks similar to the following:


-------------------- ------------- ---------- --- ----------
sales2 NONE NONE NO 10
Configuring Transparent Application Failover for ITSON

Create a service
srvctl add service –d <db_unique_name> -s <service_name> -r <preferred_instances_list> -P
srvctl add service –d IODB –s iodb –r inst1,inst2 –P basic
Start the service
srvctl start service –d IODB –s iodb
srvctl config service –d IODB
SQL> select name, service_id from dba_services where name = ‘iodb’;
SQL> select name, failover_method, failover_type, failover_retries, goal, clb_goal, aq_ha_notifications
from dba_services where service_id = 3;
SQL> execute dbms_service.modify_service (service_name => ‘iodb’ -
, aq_ha_notifications => true -
, failover_method => dbms_service.failover_method_basic -
, failover_type => dbms_service.failover_type_select -
, failover_retries => 180 -
, failover_delay => 5 -
, clb_goal => dbms_service.clb_goal_long);
Check if the service is registered with the listener

lsnrctl status

lsnrctl status LISTENER_SCAN1

lsnrctl status LISTENER_SCAN2

lsnrctl status LISTENER_SCAN3

In the client tnsnames.ora file add below entry

(ADDRESS= (PROTOCOL=tcp) (HOST= sjciodb-cluster-scan.itson.qts) (PORT=1521))
(FAILOVER_MODE= (TYPE=select) (METHOD=basic))))

Test the connection

sqlplus system/passwd@iodb

After configuring the client for TAF, a SELECT query returning a large no of rows would be fired. The
select query would try and return the result set using the primary node iosjcldb01, while the rows are
being returned the primary instance needs to be stopped abruptly. This would force the failover to
trigger and the second node iosjcldb02 would come into the picture.

LOGON TO CLUSTER NODE1 as “grid” user:

srvctl stop service -d IODB -n iosjcldb01

srvctl stop instance -d iodb -n iosjcldb01

crsctl stat res -t

And when you go back to your client connection, you can see that the query is still executing without the
connection being lost.



Don’t forget to start the service again

srvctl start instance -d IODB -n iosjcldb01

srvctl start service -d IODB -n iosjcldb01