Skip to Main Content
Return to Navigation

Working With Oracle Transparent Application Failover

PeopeTools provides limited support for Oracle Transparent Application Failover (TAF). PeopleTools TAF support includes:

Note: In most cases, other than a slight pause in the operation, the failover is transparent to the application end user.

Note: The Oracle TAF feature as implemented in Oracle 11g and earlier versions of Oracle only supports recoverability of in-flight SELECT statements. SELECT statements that are part of an uncommitted transaction block are not supported with TAF. Recoverability of INSERTs, UPDATEs, and DELETEs are not supported with TAF. Given these limitations, PeopleSoft does not support TAF for non-query operations.

PeopleTools is designed to listen for Oracle fast application notification (FAN) events to derive the failover behavior. Upon receipt of a FAN event, PeopleSoft servers break their existing TCP connections and initiate TAF, which references the TNSNAMES.ORA connect alias address list and establishes a connection to the surviving instance.

See Your Oracle RAC and database administration guides for the details of implementing and managing Oracle RAC clusters.

End-User System Behavior With TAF Configured

The following table summarizes PeopleSoft behavior during RAC or Data Guard failover when TAF is configured.

PeopleSoft Client Scenario

Behavior

End user is inserrting, updating, or deleting data and submits or saves the inserts/updates/deletes during or just after the database failure.

Oracle reconnects and reconstructs the database session on a surviving node and the end user must resubmit the transaction.

End user is paging through queried data (SELECTs) when the database failure occurs.

Oracle reconnects and reconstructs the database session on a surviving node, re-executes the query, repositions the SQL cursor, and returns the next set of rows.

End user is issuing a new query (SELECTs) or switching screens just after the database failure.

Oracle reconnects and reconstructs the database session on a surviving node.

Batch System Behavior With TAF Configured

The following table summarizes PeopleSoft batch system behavior during RAC or Data Guard failover when TAF is configured.

PeopleSoft Batch System Scenario

Behavior

Process Scheduler

Oracle reconnects and reconstructs the session on a surviving node. The Process Scheduler fails over with no administration intervention required.

Application Engine job submitted just before primary instance failure

Oracle reconnects and reconstructs the session on a surviving node but Application Engine job may fail and appear in the PeopleSoft Process Monitor with a status of No Success. These jobs will need to be resubmitted.

If the Application Engine job has been implemented to be restartable, the Process Scheduler will automatically restart the job.

If the Application Engine job was not in an open-transaction and was performing only SELECT statements, it will fail over and complete successfully.

Application Engine submitted during or just after primary instance failure

Oracle reconnects and reconstructs the session on a surviving node, the Application Engine job is then submitted on the new primary database and completes successfully.

COBOL jobs just before primary instance failure

If the COBOL program does pure queries (SELECT statements), then it will fail over to the surviving node and complete successfully.

If the COBOL program executes INSERTS, UPDATEs and DELETEs, it will not complete successfully on the surviving node.

Manual intervention is required to restart the COBOL jobs.

Crystal and SQR reports

The behavior is the same as COBOL

PSQUERY, Tree Viewer, BI Publisher Query Report Viewer

Will fail over and complete successfully.