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
ORA-12162 when connecting to database since upgrade to 1.3.0 #178
Comments
I'm not immediately aware of any changes that might be relevant. Looking at your sample tnsnames.ora I see the service_name is |
We have been using the TEST_PRIM.WORLD in tnsnames.ora for quite some time now, while still connecting to TEST.WORLD. But I just tried to change TEST_PRIM.WORLD to TEST.WORLD and it does not change the behavior, i.e. ORA-12162. |
@glM26 would you be able to create a sqlnet.ora file (on the machine where your tnsnames.ora file is) and add some tracing like:
Then execute Can you check that the connect descriptor is what you are expecting? There might be a few extra, expected attributes including CID and CONNECTION_ID. |
@cjbj
With this I get the following trace-log (only first 64 lines) with oracledb 1.2.2:
When running with oracledb 1.3.0 it looks similar in the beginning, but then it just stops at
There are no further lines after that, so no connect descriptor is shown. |
@glM26, the level of trace provided is insufficient to figure out the issue. Can you change the line in |
@anthony-tuininga I changed trace_level_client to support and reran the program:
oracledb 1.3.0 (complete log-file:
|
Thanks for the traces. That was helpful. I have pushed a patch that should correct this issue and a relevant test case. If you are able to build from source you can verify that it corrects your issue as well. Someone else noted that if you do this it will also work (without the patch):
|
@anthony-tuininga thank you for help, I can confirm that both suggestions (building the newest version from source as well as adding @ in front of the dsn) solved my issue. |
Thanks, @glM26. We will discuss internally but generally we like to make a release that contains bug fixes within a few weeks at most. I will post here when a release is made that contains this patch. |
This has been fixed in python-oracledb 1.3.2 which was just released. |
python-oracledb 1.3.1
Oracle DB 19c
RHEL 7.9
Python 3.8
error
We are using python-oracledb in thick-mode to connect to an Oracle database specified in a tnsnames.ora file (i.e. TNS_ADMIN is set to point to the tnsnames.ora file).
We are also using a sqlnet.ora file that contains a reference to a wallet that contains the DB user and password.
We connect to the database in the following way:
This is working in python-oracledb up to version 1.2.2.
Since version 1.3.0 (as well as 1.3.1) the same code now results in an error:
The tnsnames.ora file:
I can still connect to the database in 1.3.1 with all parameters in the connect-statement:
Have there been any changes in release 1.3.0 that I overlooked or is there a bug in release 1.3.0?
The text was updated successfully, but these errors were encountered: