FAQ's on Configuring OAM Data Source For RAC Database Failover
(Doc ID 2561170.1)
Last updated on FEBRUARY 04, 2020
Applies to:Oracle Access Manager - Version 22.214.171.124.181016 and later
Information in this document applies to any platform.
On : 126.96.36.199.181016 version, Configuration Service
Clarification for queries about how To Configure an OAM Data Source For RAC Database Failover (Doc ID 2367224.1).
if the HOST value in the below can be replaced with scan hostname, in which case only additional parameter would be Failover_mode, which explicitly allows application to perform TAF ( Transparent Application Failover)
Or should the scan host be ignored and each host has to be explicitly defined as in below statement.
Also in the above KM, the type is select and method is basic. Now in type there are two options, SESSION & SELECT.
SESSION: Fails over the session; that is, if a user's connection is lost, a new session is automatically created for the user on the backup. This type of failover does not attempt to recover selects.
SELECT: Enables users with open cursors to continue fetching on them after failure. However, this mode involves overhead on the client side in normal select operations
What happens if Session instead of select, in which a session itself is not lost if RAC node fails, does this have any overhead in MDC or only select type is selected and not the session.
Does the above changes on JDBC side warrants any changes in configuration in DB to be amended to support this failover?
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