SQL Developer

>>can't connect to a remote (on Oracle Cloud DB)
Please tell us more about this database.
Also, the only real difference between those versions in terms of connections is the JDBC driver. It would be interesting to see what happens if you try to connect to your Cloud database using SQLcl 21.4.

So no firewalls, private endpoints, bastions, ssh tunnels...and you can ping the machine?
I think you need to open a Service Request with My Oracle Support. I'd also still like to hear if SQLcl on the same Windows machine (it's in the sqldev bin directory) can connect.

Hi Jeff, interestingly enough on the same Windows machine where SQL Dev 19.2 works, the sqlcl version 19.2.1 also works.
There are firewalls between us and our Cloud DB, but they are properly configured and the fact that older version of SQL Dev and my mac works, seems to confirm this fact.
A change seems to have occur when SQL Dev/SQLcl were bump up to version 20.x. Since we installed and tried SQL Dev 20.2 and it does not work either, same error message.
Thanks
Jean-François Brodeur

Hi Jeff, we dug a little more into this issue and oddly enough even TNS connection does not work, with version of SQL Dev higher than 19.2, something in the networking of SQL Dev seems to be at play, what do you think, shall I create a SR, btw if you need us to test something or provide a log of some sort we will gladly help since we want to use this configuration with 3 or 4 more users at JBM.
Thanks
Jean-François Brodeur

Again, I come back to the JDBC drivers, they have changed between those versions mentioned. SQLcl version 20.2 - what does that do?

I was under the impression that using the TNS connection would bypass the JDBC drivers. So there might be a timing issue with the drivers, so an SR is the last thing we should try?
Thanks
Jean-François

The only way to do what you're describing is to enable OCI for the application OR connection. IF you use TNS Connect Identifier, that can also trip a 'Thick Connection' - but most people use Network Alias, and that's 100% JDBC Thin.

Hi Jeff, let me thank you immensly for your assistance, I've created an SR.
Have a nice evening
Jean-François

We are experiencing the same issue. Did Oracle ever provide a resolution for the SR?

Hello,
Is anyone found a solution to this issue yet? If so, can you please share as we are experiencing the same issue.
Thank you.

Hi,
I am having the same issue. Could someone share a solution that resolves this problem?

Hi, Oracle made some changes in their DB drivers and I was never able to get to the bottom of the issue, sorry no solution so far.

Hi, the SR was moving at a snail pace, moved between two Oracle department tools and BD, in the end I could not pursue this issue it was too demanding, tried to make appointment with two different developer etc...

You opened the SR on the 13th and you've already given up on it?

Hi Jeff, no it's been a while if you look at my original post, +/- 6 months. I am now using a VPN and the problem does not happen when I use the VPN.
Thanks

Sorry, no support case should linger for 6 months, or even 60 days. I can help, if you want. But I would need to know the SR#

Hi Jeff,
My SR 3-30759592711 was more recent (2 months + ago). It was closed because I was told it was my firewall issue, but none of my coworkers have the same issue. Will you be able to help?

@User_2SCER -
Before I jump into your case, which I'm happy to do, please confirm that
1)You can ping the database server from your machine
2)you can make a connection with either SQL*Plus or SQLcl from the same machine
If either of those questions is 'no' then it is probably the network. Just having colleagues that can connect doesn't rule out the network, either a firewall or ACL rule could come into play that affects you and not your co-workers.

Hi Jeff and User_2CER, here is the exact situation that we ended up stop pursuing after a lot of back and forth, it took months to get to that point, in short the issue seems to be that a change in the DB connection regarding OOB handshake creates an issue on client connection, the issue was partly resolved by changing the DB configuration which for us was not an ideal situation. Why was a client connection validation introduced that cause existing configuration to fail, and why is it not configurable on the client side?
Thanks
Jean-François
Problem Description for SR 3-28417039891
---------------------------------------------------
SQL Developer 21.4.1 gives IO error while 19.2.1.247 works fine same settings
SQL Dev 21.4.x can't connect to a remote (on Oracle Cloud DB) database 19.3 fully patched, installed on Oracle Linux 8 using TCP/IP SQL*Net port 1521.
Status : Failure -Test failed: IO Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond, Authentication lapse 0 ms.
The exact same setting works fine on SQL Dev 19.2, error on SQL Developer 21.2.1. SQL Developer 21.4.1 on macOS all version of SQL Dev work fine on the same network.
When we tried using SQL*Plus from the Instant client, it gave us a more interesting error message ORA-12637: Packet receive failed. Doing some research on this message lead us to Doc ID 2662778.1 support document about OOB test failing. We created an sqlnet.ora file with only one line DISABLE_OOB=on. We then restarted the listner and we were able to connect with Oracle SQL Developer 21.4 from Windows.
I think that an issue with OOB shall raise a warning and not stop the connection from establishing, more so it should be configurable from the client side.
You can refer to SR: SR 3-28278568961 they are the one that confirm this is a DB connectivity issue.

Hi Jeff,
The problem I have is that when I am connecting to VPN, I cannot connect to the database. The technician who was assigned to my SR mentioned that it's my network issue. However, I have our network technician do a compare with my old machine (which it works) and check all the network settings and we couldn't find any problems.
To your questions:
1)You can ping the database server from your machine -- Yes, I can ping the database server with or without VPN.
2)you can make a connection with either SQL*Plus or SQLcl from the same machine -- I can only connect when I am not connecting VPN. Once I am connected via VPN, I cannot connect with SQL Plus.

Regards,
Joanne

I would agree with the technician, the problem is with your network.
You can't connect once you're on the VPN, even with SQL*Plus. I would open a support ticket with your networking staff.

Hi, I agree with Jeff, you can also tell the networking team to activate a do not inspect rule on SQL*Net traffic.
Have a nice day :)
Jean-François