ODBC Arithmetic overflow error Accessing AS400 DB2 (Update, Delete, Insert)

[BockTim91]

We are trying to hit our AS400 running a DB2 instance. When we run a OdbcCommand.ExecuteNonQuery() for select, everything works no issue. However, when executing a simple update, or delete command, we encounter the below error. Our current workaround is to just squish all arithmetic errors out of our execute command, which is unacceptable.

Arithmetic operation resulted in an overflow.
   at System.Data.Odbc.OdbcDataReader.FirstResult()
   at System.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior behavior, String method, Boolean needReader, Object[] methodArguments, SQL_API odbcApiMethod)
   at System.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior behavior, String method, Boolean needReader)
   at System.Data.Odbc.OdbcCommand.ExecuteNonQuery()

We are using VS 2017 with netcore 2.2

[danmoseley]

Is it possible to attach a debugger to figure out exactly where (what line/values) this is coming from in the code?

VS should be able to resolve symbols and sources when you debug.

[BockTim91]

In enabling full debugging, it appears the issue occurs at line 1912 and 1913 of OdbcDataReader.

            cRowsAffected = GetRowCount();              // get rowcount of the current resultset (if any)
            CalculateRecordsAffected(cRowsAffected);    // update recordsaffected

When running a select statement cRowsAffected gets -1 as expected, however when running a delete it appears to be overloading the int causing it to crash into SR GetResourceString.

        internal static string GetResourceString(string resourceKey, string defaultString)
        {
            string resourceString = null;
            try { resourceString = InternalGetResourceString(resourceKey); }
            catch (MissingManifestResourceException) { }

            if (defaultString != null && resourceKey.Equals(resourceString, StringComparison.Ordinal))
            {
                return defaultString;
            }

            return resourceString;
        }

Upon trying to add cRowsAffected into my watch and casting as an int or long it gives a, "Cannot obtain value of the local variable or argument because it is not available." when doing a delete. However when running a Select it returns a -1 as expected.

Let me know if there is anything else you need.

[Clockwork-Muse]

CalculateRecordsAffected is takes an int:

internal int CalculateRecordsAffected(int cRowsAffected)
{
    if (0 <= cRowsAffected)
    {
        if (-1 == _recordAffected)
        {
            _recordAffected = cRowsAffected;
        }
        else
        {
            _recordAffected += cRowsAffected;
        }
    }
    return _recordAffected;
}

this is causing cRowsAffected (which is a wrapper around an IntPtr) to call this operator:

public static unsafe implicit operator int(SQLLEN value)
{
#if WIN32
    return (int)value._value.ToInt32();
#else
    long l = (long)value._value.ToInt64();
    return checked((int)l);
#endif
}

I'm assuming it's the return checked((int)l); line that is actually throwing, which implies that your statement affected 2 billion+ rows.

Which is certainly in a believable range (I'm not sure if they're all stored in the same or partitioned tables, but we definitely have cause for that many rows on an iSeries database here). Unfortunately DbDataReader.RowsAffected is a strict 32-bit int...

---

GetResourceString is almost certainly just from reporting the overflow, an not at issue.

[BockTim91]

I can safely say the table I was updating has less than 12 million records in it. The statement I am running is on the key affecting only one record.

[tb-mtg]

I too am having this problem.

I created a simple test project and with basic insert, update & delete OdbcCommands. They only work when the following is set:

<PlatformTarget>x86</PlatformTarget>.

The problem is our real application platform target is x64.

[danmoseley]

@saurabh500

[saurabh500]

I think this one suffers from the lack of an WIN32 build for System.Data.Odbc, which has surfaced in System.Data.OleDb also. I will look into it.

[tb-mtg]

Turns out I had an out of date IBM Client Access ODBC driver 13.0.1.0.

I downloaded and installed the latest AS400 Client Access service pack si68573 from IBM and I think it may have fixed the problem.

The IBM i Access ODBC drivers versions are now:

• 13.0.21.0 for 32 bit (C:\Windows\SysWOW64\cwbodbc.dll)
• 13.64.21.0 for 64 bit (C:\Windows\System32\cwbodbc.dll)

[ajcvickers]

@saurabh500 Do you believe that there is still work to be done here?