Frequent TNS-12514 Alerts from JDBC Connections to Oracle RAC with Primary and Standby Databases (Doc ID 2113133.1)

Last updated on JULY 07, 2017

Applies to:

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

Symptoms

On : 12.1.0.2.0 version, Thin JDBC driver

Frequent TNS-12514 alerts from monitoring tools (SiteScope).

A database 12.1.0.2 monitoring tool uses JDBC connections with the following connection string using multiple SCAN listeners. The first entry is the active primary database and the second entry is the SCAN listener for the physical standby.
The database service is ONLY running on the primary instance.


The JDBC connection makes connections to both the primary and standby SCAN listeners. When it tries to connect to the standby SCAN listener, the tool reports TNS-12514 and users are falsely alerted the service is down.

listener_scan2.log:01-MAR-2016 15:28:54 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=was))(SERVICE_NAME=db)) * (ADDRESS=(PROTOCOL=tcp)(HOST=x.x.x.53)(PORT=35819)) * establish * db * 12514
listener_scan2.log:01-MAR-2016 15:49:27 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=was))(SERVICE_NAME=db)) * (ADDRESS=(PROTOCOL=tcp)(HOST=x.x.x.37)(PORT=41492)) * establish * db * 12514
listener_scan2.log:01-MAR-2016 15:54:12 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=was))(SERVICE_NAME=db)) * (ADDRESS=(PROTOCOL=tcp)(HOST=x.x.x.37)(PORT=41570)) * establish * db * 12514


ERROR
-----------------------
TNS-12514 TNS:listener could not resolve SERVICE_NAME given in connect descriptor


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms