Connection with Advanced - custom JDBC URL fails with some valid JDBC-URLs

Question

Hi,
I am trying to create a connection with a custom JDBC connection string, but SQL*Developer throws the error message:
Status : Failure -Test failed: Required property 'hostname' is not set on the DatabaseProvider my tests are:
<li> with connection via Connection Type set to TNS and a proper alias - it works fine
<li> with connection via Connection Type set to Advanced and exactly the same values from tns in the url: jdbc:oracle:thin:@(DESCRIPTION=(enable=broken)(ADDRESS=(PROTOCOL=tcp)(HOST=172.24.32.113)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=RESTSVP_SITE1))) - it fails with Status : Failure -Test failed: Required property 'hostname' is not set on the DatabaseProvider<li> with JDBC URL set to jdbc:oracle:thin:@172.24.32.113:1521/RESTSVP_SITE1 - it works fine
As my jdbc url is quite close to the example in [url http://docs.oracle.com/cd/E11882_01/java.112/e16548/apxtblsh.htm#CHDBBDDA]Using JDBC with Firewalls maybe someone can help me to fix it?
Martin
Edited by: berx on Oct 12, 2012 11:32 AM - fixed typos

Answer 1

Hi Martin,
1/oci/thick
2/RAC options
3/TNS connection
1/oci/thick
OCI driver has a slightly different set of features than thin:
-try oci/thick (requires Oracle Client, server or instant client) (It requires SQLDeveloper java and .dll, .so libraries to match)Re: SQL developer 3.1 shows error Incompatible version of libocijdbc
jdbc:oracle:oci:@(DESCRIPTION=(enable=broken)(ADDRESS=(PROTOCOL=tcp)(HOST=your_host_name)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=your_service_name)))
2/RAC options
More speculatively:
-Try sid instead of service name (will disable some networking features on that connection), try switching load balancing off.
From: Unable to access RAC from SQL Developer!
In general and especially for RAC database you should use SERVICE_NAME to connect and not SID (because only SERVICE_NAME can use load balancing and failover features):
3/TNS connection
with connection via Connection Type set to TNS and a proper alias - it works fine(Which Connection Type TNS did you use? TNS Connect Identifier = oci/thick, TNS Network alias (can be thin (I should check, might depend on oci/thick checkbox))
Is this issue stopping your work i.e. is this workaround unacceptable?
-Turloch
SQLDeveloper team