-
Notifications
You must be signed in to change notification settings - Fork 61
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
Bequeath connections are failing with ORA-12545 #114
Labels
Comments
Thanks for the report. I'll get that corrected! |
anthony-tuininga
added a commit
that referenced
this issue
Jan 10, 2023
I have pushed a patch that should correct this issue and added a relevant test case. If you are able to build from source you can verify that it corrects your issue as well. |
anthony-tuininga
added a commit
that referenced
this issue
Jan 18, 2023
I can confirm that the issue is fixed with this patch included. Thanks! |
This patch is included in version 1.2.2 which was just released. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Database version: Oracle
19.17.0.0.0
platform.platform:
Linux-5.4.17-2136.313.6.el7uek.x86_64-x86_64-with-glibc2.17
sys.maxsize > 2**32:
True
platform.python_version:
3.9.16
oracledb.version:
1.2.1
Is it an error or a hang or a crash?
Error
What error(s) or behavior you are seeing?
When calling the
connect
function for a bequeath connection, like:The following error occurs:
Does your application call init_oracle_client()?
Yes, running in thick mode.
Include a runnable Python script that shows the problem.
When running in debug mode I found that the connection is being made using the connect_string:
This explains the ORA-12545 error message.
It looks like a regression bug in
src/oracledb/impl/base/connect_params.pyx
, in theget_connect_string
function (commit 847004a) introduced in version 1.2.0.In version 1.0.1 a fix was included to 'restore support for bequeath connection` (commit 5852bae), but the change in 1.2.0 altered the same line. In version 1.1.1 the error does not occur.
Just for testing purposes, I changed the code as follows and then bequeath connections are working fine:
The text was updated successfully, but these errors were encountered: