Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
ORA-24816 with cx_Oracle 6.0rc1 #50
When using cx_Oracle 6.0rc1, I encounter the ORA-24816 DatabaseError on specific queries:
The query does not seem special and the error is only triggered inside Django (not when it is run from the command line, even if the code is the same) so I think this may be related to previous queries, the context or configuration settings.
I have the same error when using Oracle Client 11.2, 12.1 or 12.2.
The error description is somewhat cryptic for me, so I don't know how to continue the analysis.
Is there a reason it is now raised by cx_Oracle 6.0rc1? What information can be retrieved to diagnose this issue?
I have finally achieved to reproduce the problem with only a few queries.
Arguments order and content is important in my case, so I hope you can also reproduce it on your side with the following script.
Yes, the problem is also not reproduced with non-empty strings. In fact, if only one of the two unicode empty strings is either non-empty or non-unicode, the issue is not triggered.
I have tried to investigate the issue but I don't know exactly what to search, as I don't understand the Oracle error message and I don't understand why the previous two queries are important to trigger the issue.
The only thing I have found is that the variable size is set to 4000 (default size of vt_String) due to size being 0 (empty) in Variable_New. This does not seem to be the case in 5.3 but I'm not sure this is a problem.