My Oracle Support Banner

FAILOVER_TYPE and FAILOVER_METHOD Are Null When Connecting With JDBC Thin With FAILOVER_MODE (Doc ID 2264622.1)

Last updated on DECEMBER 14, 2018

Applies to:

JDBC - Version 11.2.0.1.0 and later
Information in this document applies to any platform.

Symptoms

JDBC thin client does not use failover configuration to connect to the database, and it is not failing over to available database instance when original instance is down.
The JDBC connection string used is:

Checking out gv$session, those connections from JDBC thin show failover_type => NULL and failover_method=>NULL, and they do not switch over to available instance.

 
JDBC connections are expected to fail over to available node.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Configure connection string as:
jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=on)(FAILOVER=on)(ADDRESS=(PROTOCOL=TCP)(HOST=<scan host>)(PORT=<port>))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=<service name>)(FAILOVER_MODE=(TYPE=SELECT)(METHOD=BASIC)(RETRIES=5)(DELAY=180))))
2. Run connections.
3. Check out gv$session, those connections from JDBC thin -- failover_type => NULL and failover_method=>NULL
4. Bring one node down -- those connections do not switch over to available instance.



Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.