Bug: DPY-5003: internal error: read a negative integer when expecting a positive integer

[RuleEngine]

Hi,
I am running dbt (data build tool) as a function in Oracle OCI.
Yesterday I pushed some new logic into one of my sql models and suddenly I get this very annoying bug:
"DPY-5003: internal error: read a negative integer when expecting a positive integer"
This stopped me from releasing data for a second day now and I'm going nuts.
I have no Idea what changed other than the addition of a new logic.
By the way, if I am taking my new logic into sql developer it runs ok and everything is fine..
This is just so frustrating.
Has anyone encountered this?

[anthony-tuininga]

This can occur if the data the server is sending is not understood by the client (or a bug in the client causes the client to be unsynchronized with the server). Which version are you using? Can you provide the full traceback? Can you also get this consistently and are you able to share the test case? I can take a look.

You can also try thick mode by enabling it.

[anthony-tuininga]

Thanks for the update! I will try with 15+ UNION ALL clauses and see if I can replicate the issue that way -- I'll let you know once I get a chance to do that testing.

[anthony-tuininga]

Ok. I tried with a simple select frion dual and 16 of these queries with a UNION ALL clause between them. I did not, unfortunately, see the problem. Do you see the problem with this script?

cursor = conn.cursor()
frags = [f"select {i + 1} as num, 'String {i + 1}' as str from dual" \
        for i in range(16)]
sql = " union all ".join(frags)
cursor.execute(sql)
for row in cursor:
    print(row)

I even bumped the number of union all clauses up to 500 and still didn't notice an issue, unfortunately. Are you able to share the SQL you are executing that is cause the problem?

[anthony-tuininga]

I just pushed a change that may correct this issue for you. If you are able to build from source you can verify that it corrects your issue. If so, please let me know! Thanks.

[RuleEngine]

Hi man
I have no idea what you did.
Maybe I can figure it out on my own but I couldn't locate it.
This error returned again on my project, and I used this incident to try and run it again after downloading the updated oracledb package.
Same code - only package version changed.
Aaaaand - IT WORKED!
So - this is great.
If you can elaborate on what you did that would be amazing and also interesting.

[anthony-tuininga]

The issue I found was corrected in this commit. I wasn't sure if it would resolve your situation but I am glad to hear that it did!

At issue is that the database can send back a negative error position under some circumstances. It is unknown what those circumstances are exactly but ensuring that the driver can accommodate negative values was the solution.