Does DBCA (or Other Potentially Long Running Clients) Require Load Balancer Persistence (Sticky Routing) to OIDs in High Availability (HA)?
(Doc ID 2140569.1)
Last updated on OCTOBER 05, 2019
Applies to:Oracle Internet Directory - Version 9.0.4 and later
Oracle Database Configuration Assistant - Version 10.1.0.2 and later
Information in this document applies to any platform.
Oracle Internet Directory (OID) with F5 load balancer (LBR) to connect to OID on a 2 node cluster.
Using Oracle Database Configuration Assistant (DBCA) to add databases to OID.
During the DBCA registration process, DBCA creates multiple connections to OID.
For client processes such as DBCA, which may take a sizeable amount of time when run, do all the connections that are established have to be redirected to one OID server only ?
Can DBCA support each connection load balanced during the registration process or does it require persistence?
Do all connections for a given DBCA process need to be directed to one server from the load balancer?
Does the load balancer need to be set for "persistence", i.e., timeout periods in case of long running transactions?
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