- 3,727,075 Users
- 2,245,315 Discussions
- 7,852,569 Comments
Forum Stats
Discussions
Howdy, Stranger!
Categories
- 380.8K All Categories
- 16 Data
- 362.2K Big Data Appliance
- 7 Data Science
- 2.3K Databases
- 670 General Database Discussions
- 3.7K Java and JavaScript in the Database
- 32 Multilingual Engine
- 499 MySQL Community Space
- 8 NoSQL Database
- 7.7K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 424 SQLcl
- 68 SQL Developer Data Modeler
- 185.2K SQL & PL/SQL
- 21.1K SQL Developer
- 2.7K Development
- 3 Developer Projects
- 32 Programming Languages
- 135.9K Development Tools
- 18 DevOps
- 3K QA/Testing
- 379 Java
- 15 Java Learning Subscription
- 14 Database Connectivity
- 72 Java Community Process
- 2 Java 25
- 13 Java APIs
- 141.2K Java Development Tools
- 14 Java EE (Java Enterprise Edition)
- 153K Java Essentials
- 135 Java 8 Questions
- 86.2K Java Programming
- 270 Java Lambda MOOC
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 18 Java SE
- 13.8K Java Security
- 4 Java User Groups
- 22 JavaScript - Nashorn
- 18 Programs
- 156 LiveLabs
- 36 Workshops
- 11 Software
- 5 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 4 Deutsche Oracle Community
- 17 Español
- 1.9K Japanese
- 4 Portuguese
Connection error after upgrade to 4.1
Hi -
I have upgraded to 4.1 EA2, but when I connect to 12c pluggable database, which was previously working fine with older version, I am getting the following error.
"An error was encountered performing the requested operation: IO Error: Invalid connection string format, a valid format is: "host:port:sid" Vendor code 17002"
Regards,
Omar
Answers
-
Open the connection properties.
Is the host correct - can you ping it?
Is the port correct - does the listener listen on that port?
Is the sid or service correct?
Do you still have the older version of SQLDev installed - does the connection still work there?
Are you using TNSNames? It's possible the option to define which tns directory we're reading services from got messed up somehow, but that's just a wild guess.
-
Hi -
The same config and connections were working fine, and I can connect to other databases, this is only with Oracle12c with pluggable db. I am not using tnsnames.ora file, everything is correct.
FYI I am using MAC OS version.
Regards,
Omar
-
Everything is NOT correct, or we'd be able to connect.
>>Do you still have the older version of SQLDev installed - does the connection still work there?
Or, are you able to connect to your 12c PDB with any other client?
By the way, 12c PDB connections require you use SERVICE, not a SID.
It might help if you show us your connection properties.
-
Hi Omar,
can you please tell us if your database is a single instance, with only one Listener? Or do you have a RAC with SCAN listeners?
Just want to sort things out.
Martin
-
Hi -
1. The connection properties was before the same and I was able to connect, I have migrated the preferences.
2. I can connect with TOAD.
3. I am using single instance not RAC with SCAN.
4. I am using SERVICE name, fully qualified with the host.
5. I can ping the server.
6. I can connect to Oracle 11g.
7. If you have direct mail I can send you screen shot with the connection properties.
Regards,
Omar
-
-
So, it appears we have found a bug with the 12c JDBC driver we're shipping with.
Two things to try:
- Change the service name, IF you can, to no have a hyphen in the name.
- Try a thick connection using an 11203/4 client - this will force an 11gR2 JDBC driver and should let you connect
-
A better workaround
using the Advanced sub panel for the connection, specify the URL in TNS format
this works for thin as well
jdbc:oracle:thin:@(DESCRIPTION=
(ADDRESS=
(PROTOCOL=tcp)(HOST=foo.bar)(PORT=1521))
(CONNECT_DATA=(SERVICE_NAME=zed-test.local.net)))
