JDBC Connections Jump(Fail Over) to 3'd Node Incorrectly When Stopping 1'st Node on Oracle DB RAC with 3 Nodes
(Doc ID 2988165.1)
Last updated on NOVEMBER 20, 2023
Applies to:JDBC - Version 184.108.40.206.0 to 220.127.116.11.1 [Release 12c to 21]
Information in this document applies to any platform.
JDBC connections jump to 3'nd Node when stopping 1'st Node on Oracle 19c DB RAC with 3 Nodes.
Client code defined 3 DB node address(host/port) as parameter in JDBC connection string with JDBC 19.20 Driver.
When all 3 DB node keep running, it is expected behavior that all DB connection created on 1'st Node
But incorrect behavior occurred that all of JDBC connections fail over to 3'rd Node, not 2'nd Node, when shutting down 1'st DB node.
According to address order, correct behavior should be that connections should jump to 2nd Node when stopping 1'st Node.
Also tested with different version of JDBC driver. Same behavior existed on multi JDBC version , including 11g, 19c and 21c JDBC driver. No issue only on 23.2 driver.
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