RETRY_COUNT Parameter Works Differently In JDBC Thin Driver (Doc ID 1364297.1)

Last updated on JUNE 08, 2022

Applies to:

Symptoms

When the JDBC Thin Driver uses RETRY_COUNT in the connection URL,  the behavior is incorrect and differs from that of SQL*Plus:

1) Specifying RETRY_COUNT=0  throws a NullPointerException

2) RETRY_COUNT is the total number of trials, not the number of additional attempts.
     For example, for RETRY_COUNT=2 , JDBC thin driver will try all the Addresses in
     the Address List 2 times, instead of 3 times (1 initial attempt + 2 Retries)

3) Each address in the address list is tried for RETRY_COUNT times before proceeding to the
    next address in the list.   For example, in a JDBC connection URL, if the first address
    cannot be contacted (machine down), this first entry is retried even before trying the other addresses.
    The correct behavior is to iterate over all addresses, and if none works, retry the list.

Cause

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