ColdFusion MX: Data source verification fails for Oracle JDBC Thin DriverProducts affected
Issue
When configuring a data source using the Oracle JDBC Thin Driver per the instructions in TechNote 18344, the data source fails to verify.
If either ColdFusion MX Updater 3 or higher, or the ColdFusion MX pre-Updater 3 diagnostic JAR is installed, the following error is generated in the ColdFusion Administrator after creating a data source that uses dot notation in the Oracle System Identifier (SID) name in the JDBC URL field:
Connection verification failed for data source: data source name []java.sql.SQLException: SQLException while attempting to connect: java.sql.SQLException: Io exception: Connection refused(DESCRIPTION=(TMP=) (VSNNUM=135294976)(ERR=12505)(ERROR_STACK=(ERROR= (CODE=12505)(EMFI=4)))) The root cause was that: java.sql.SQLException: SQLException while attempting to connect: java.sql.SQLException: Io exception: Connection refused(DESCRIPTION=(TMP=) (VSNNUM=135294976)(ERR=12505)(ERROR_STACK=(ERROR= (CODE=12505)(EMFI=4))))
Client-based Oracle database connections, such as ODBC or oci8 drivers, are dependent on the tnsnames.ora file for connecting to the Oracle database. For these connections, dot notation for the SID Name does not cause a problem. For the Oracle Thin JDBC driver however, dot notation in the SID Name will cause the data source verification to fail with the error above.
Solution
For the Oracle Thin JDBC Driver data source definition, the JDBC URL field should not include any dot notation in the SID. To successfully verify the data source, follow these steps:
- In the ColdFusion Administrator, choose edit for the specific data source.
- Modify the JDBC URL field so that the SID no longer contains dot notation.
For example, for a database connection that has a SID Name ofpslager.world, modify the JDBC URL as follows:
From
jdbc:oracle:thin:@10.1.204.111:1521:pslager.world
to
jdbc:oracle:thin:@10.1.204.111:1521:pslager - Click Submit to save the changes.
Assuming the remaining information for the Oracle JDBC Thin Driver data source is correct, it will now verify.
Additional Information
Doc ID
(tn_18649)
Last updated
2005-05-12
Products affected
