Direct connect using service name fails
Posted: Tue 22 Mar 2016 14:59
I'm trying to connect to a server that is RAC with 2xinstances in direct mode and I'm getting this error:
NET: Network error (Cannot change host for the active connection) <Host = xxxxxx.xxxx.xx:1521>
It fails when using the alias to the scan listener, but works when using one of the instances as host.
I've basicly tried a version of my program that uses an older version of ODAC (9.5.18) and that works so from that version to the current (9.6.22) something broke. I have also another program that uses ODAC (9.6.20) and that works as well.
These are my more detailed test results:
ODAC (9.6.22) OCI from inside network works
ODAC (9.6.22) OCI over VPN works
ODAC (9.6.22) Direct from inside network works
ODAC (9.6.22) Direct over VPN fails
SQLDeveloper from inside network basic works
SQLDeveloper over VPN basic works
SQLDeveloper from inside network advanced jdbc works
SQLDeveloper over VPN advanced jdbc works
So I think that this proves that it's not the VPN connection that causes this error.
-Update
I'm using Seattle
I downgraded to 9.6.21 with the same result.
Then I downgraded to 9.6.20 and that version works.
- Arni Thor
NET: Network error (Cannot change host for the active connection) <Host = xxxxxx.xxxx.xx:1521>
It fails when using the alias to the scan listener, but works when using one of the instances as host.
I've basicly tried a version of my program that uses an older version of ODAC (9.5.18) and that works so from that version to the current (9.6.22) something broke. I have also another program that uses ODAC (9.6.20) and that works as well.
These are my more detailed test results:
ODAC (9.6.22) OCI from inside network works
ODAC (9.6.22) OCI over VPN works
ODAC (9.6.22) Direct from inside network works
ODAC (9.6.22) Direct over VPN fails
SQLDeveloper from inside network basic works
SQLDeveloper over VPN basic works
SQLDeveloper from inside network advanced jdbc works
SQLDeveloper over VPN advanced jdbc works
So I think that this proves that it's not the VPN connection that causes this error.
-Update
I'm using Seattle
I downgraded to 9.6.21 with the same result.
Then I downgraded to 9.6.20 and that version works.
- Arni Thor