Problem with Query on Oracle, after updating LEGACY

Hello.
Today the processes have been updated to Legacy and when running them I encounter problems when making queries in Oracle.
I use a 64-bit driver and I see that it connects but when I make the query I get this error: “arithmetic operation resulted in an overflow” the query I am trying is quite simple:
“select sysdate from dual”
Until Friday everything was perfect, it was today with the Legacy update.
Any idea what the problem is?
Thanks.

Query ok:

Hi @Aguirre

Could you please clarify what you mean here? Do you mean that you converted the Studio Legacy project to a Studio Windows one?

Today, when I opened a project that I had to modify, a window popped up asking me to upgrade to Legacy and it wouldn’t let me do anything else. After upgrading, I ran my process and when I got to the ODBC connection, it failed. I did this simple example to see if anyone knows the reason, as it always worked correctly before.

1 Like

Would it be possible for you to share the entire error stack of this exception?

It would be really helpful if you could also:

  • share the Diagnostic Tool output with me via a private message:
  • share a zip of the dummy project that reproduces the issue (please mock the sensitive info, but please include the connection string structure with that mocked data)

I have done more tests and it works with “Oracle Managed Data Access” but the strange thing is that it does not work with the latest version, it must be with the previous one. I’ll try to send you more things

DATABASE 1.9

DATABASE 1.7.1

Thank you for the extra information.

To summarize so far:

  • ODBC doesn’t work for neither Database 1.7.1 nor Database 1.9.0 package versions
  • Oracle.ManagedDataAccess:
    • works for Database 1.7.1 which has this dependency version: Oracle.ManagedDataAccess.Core [3.21.1, )
    • does not work with Database 1.9.0 which has this dependency version: Oracle.ManagedDataAccess.Core [23.5.0, )

Could you also share the driver versions that you are currently using?
As far as the ORA-28040 error, I found this suggestion: oracle database - ORA-28040: No matching authentication protocol exception - Stack Overflow
It could be that the driver update could solve it though, given that the topic above is quite old.

Ok, we have Oracle version 11g, it is old. But since it works with “Oracle.ManagedDataAccess” we can consider the problem solved. Thank you very much for your help.

By the way, I’m adding the screenshot that appears when I open old processes.
Thanks.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.