CQN Fails When Setting DCN_CLIENT_INIT_CONNECTION Property and Connecting Via SCAN Listener or LDAP
(Doc ID 2741894.1)
Last updated on JANUARY 11, 2021
Applies to:JDBC - Version 19.3 and later
Information in this document applies to any platform.
When using the JDBC driver with CQN (Continuous Query Notification), this registration fails when the property OracleConnection.DCN_CLIENT_INIT_CONNECTION is set, and a URL specifying a SCAN listener is used. This also reproduces when using an LDAP-based URL.
For example, the following JDBC URL/connect string, specifying VIP, is successful:
This problem only occurs when setting the OracleConnection.DCN_CLIENT_INIT_CONNECTION property to “true”.
If this is not set, then any of the above connect strings work.
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