-
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
TypeError: cannot convert 'NoneType' object to bytearray when connecting to oracledb server 19.2 in thin mode #51
Comments
That looks like some unexpected output from the server is occurring. Can you set the environment variable |
@abma Can you get us the trace? |
the oracle listener was configured incorrectly: it had some db server/instance configured which didn't exist. i can try to reproduce the issue, but this will take a bit. |
@abma if you can, we'd love it. Then @anthony-tuininga may be able to squash a bug - even if it is only a missing "can't connect" case that should generate a DPY error. |
If you can indicate what the configuration of the listener was before you fixed it, that would also be helpful, as then we can try to reproduce the problem ourselves. :-) |
listener.ora:
and then connect to server.some.domain/ORCL.some.domain can you provide me a mail address or so, so i can send the trace in private or is this info enough? |
You can e-mail me directly at anthony.tuininga@gmail.com (or anthony.tuininga@oracle.com). Both of these e-mail addresses are noted in the Python package information. Thanks! In the listener.ora configuration above, what was incorrect? What did you have to do to fix it? What error do you get when using the thick driver? |
GLOBAL_DBNAME + SID_NAME was incorrect. to fix it i just removed SID_LIST_LISTENER. i didn't test the thick driver: lsnrctl status says
|
Ok. I'll see if I can reproduce here, but the traces would be very helpful if you are able to provide them. Thanks! |
Ok. I am able to reproduce here using the contents of the listener.ora you posted. The thick driver gives the following output, for reference:
I'll see about adding the necessary code to the thin driver to handle this situation gracefully. Thanks for the report! |
when connecting to a database that the listener configuration file states exists but actually doesn't (#51).
I've pushed a patch for this issue. Thanks for your help in resolving it! |
Thank you! |
server:
client:
thats the script:
The text was updated successfully, but these errors were encountered: