We have a JDBC configuration against a scan address with client load balancing enabled.
Example:
jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=xxxxxxxxxxxx.de)(PORT=xxxx))(CONNECT_DATA=(SERVICE_NAME=xxxxxx)))
From what I understand from Diference between Client-Side and Server-Side Load BalancingIf you do not want to use server load balancing, you can bypass it by connecting to the service name that identifies a particular RAC node.
My question is, if you have a connection pool set up against this configuration and if the node the service name maps to goes down, what happens to the connection pool connections ?
Question 1) Does the scan address fail over the service name to the next available node, then the JDBC driver on the client has to drop all stale connections and reconnect to the next available node ? or is it all client agnostic to the node fail over and all old available connections in the pool are available for use ?