-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection with TNS name doesn't work when DEFAULT_DOMAIN is defined in sqlnet.ora #90
Comments
utPLSQL-cli uses At the moment I'm not sure about whether we should add support for oci-driver. It looks like much added complexity to me. |
Maybe we could check if sqlcl work with thus configuration. If it dies we can ask the sqlcl team how to do this. |
@pesse, are you able to reproduce that error locally (TNS & jdbc with DEFAULT_DOMAIN)? |
I'll try to reproduce it tomorrow evening. |
I can reproduce it. SQLcl seems to overcome the issues, though. |
@SebGt you have a pretty old version of Java 8 installed:
Can you update it? I can reproduce DEFAULT_DOMAIN not getting populated, but I can't reproduce the Docs for SQLcl recommend "Java Runtime Environment (JRE) version 8 update 161 or later." |
Got some info from the phenomenal Jeff Smith: in SQLcl they actually try a THICK connection first and just fall back to thin afterwards. |
Thanks a lot for your investigations. |
Hey @SebGt |
Hi, |
It is working with command line and I need to give the full name db_test_dev.world in command line.
|
Do we change requirements and now additional ocijdbc library is needed from Oracle |
No. We support thick driver, but we don't require it. |
I put ojdbc8.jar in lib folder of utPLSQL-CLI folder and in command line it is working fine. Command line is executed from cmd window on server where jenkins is running. (sorry ;-) ) What means full-qualified connect-string ? |
something like localhost:1521/service |
I found. For Jenkins, all network mapping are not available. Thanks again for your help and all the job you do to provide this test API and all related components . |
You're welcome - great it works now for you. And thanks for helping making the tooling even better ;) |
Hi,
Following the investigation done for #88 , I still have an issue with connection using TNSNAME.
When TNS alias is defined without DEFAULT_DOMAIN it is working fine.
Command used is like :
utplsql run user/pswd@DB_TEST_DEV ...
Config details:
But when DEFAULT_DOMAIN is defined, the alias is not found by java API used to connect:
Command used is like :
utplsql run user/pswd@DB_TEST_DEV ...
Config details:
In such config, connect string should be user/pswd@DB_TEST_DEV and when client opens the connection the TNS alias is determined using connect string + DEFAULT_DOMAIN in sqlnet.ora.
It seems that the java API doesn't use sqlnet.ora (googled but I found nothing about that).
So I tried to give the full alias name in connect string but API thought I pass an IP because there is a dot in connect string (it is what I guess)
Example:
utplsql run user/pswd@DB_TEST_DEV.WORLD ...
(see #88 for full stack)
Any chance to have a look because config with DEFAULT_DOMAIN can't be changed ?
Thanks in advance.
The text was updated successfully, but these errors were encountered: