Forum Stats

  • 3,734,282 Users
  • 2,246,937 Discussions
  • 7,857,218 Comments

Discussions

Connection error after upgrade to 4.1

Omar M. Sawalhah
Omar M. Sawalhah Member Posts: 41 Blue Ribbon
edited Mar 19, 2015 1:53PM in SQL Developer

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

1ebdc802-a4e2-4237-a687-009896c9f2deuser1125375

Answers

  • thatJeffSmith-Oracle
    thatJeffSmith-Oracle Distinguished Product Manager Posts: 7,701 Employee
    edited Mar 15, 2015 10:11AM

    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.

  • Omar M. Sawalhah
    Omar M. Sawalhah Member Posts: 41 Blue Ribbon
    edited Mar 17, 2015 5:51AM

    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

  • thatJeffSmith-Oracle
    thatJeffSmith-Oracle Distinguished Product Manager Posts: 7,701 Employee
    edited Mar 17, 2015 9:35AM

    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.


  • berx
    berx Member Posts: 218 Silver Badge
    edited Mar 17, 2015 3:59PM

    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

  • Omar M. Sawalhah
    Omar M. Sawalhah Member Posts: 41 Blue Ribbon
    edited Mar 17, 2015 6:01PM

    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

  • thatJeffSmith-Oracle
    thatJeffSmith-Oracle Distinguished Product Manager Posts: 7,701 Employee
    edited Mar 17, 2015 10:12PM
  • thatJeffSmith-Oracle
    thatJeffSmith-Oracle Distinguished Product Manager Posts: 7,701 Employee
    edited Mar 19, 2015 1:43PM

    So, it appears we have found a bug with the 12c JDBC driver we're shipping with.

    Two things to try:

    1. Change the service name, IF you can, to no have a hyphen in the name.
    2. Try a thick connection using an 11203/4 client - this will force an 11gR2 JDBC driver and should let you connect
  • thatJeffSmith-Oracle
    thatJeffSmith-Oracle Distinguished Product Manager Posts: 7,701 Employee
    edited Mar 19, 2015 1:53PM

    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)))

    1ebdc802-a4e2-4237-a687-009896c9f2deuser1125375
This discussion has been closed.