DB2 CONNECT / DB2CONNCT / B10 - DB2

While you use Compound SQL statements(statement chaining)
execution from a .NET
application and when certain rows in the batch of statements are
in error,
application might see incorrect numbers for the rows that are in
error/warnings.



e.g:
            // OK
            sql = new StringBuilder();
            sql.AppendLine("UPDATE employee");
            sql.AppendLine("SET LAST_NAME = 'Tom'");
            sql.AppendLine("WHERE EMPLOYEE_CODE = 20000");
            queries.Add(sql.ToString());

            // ERROR: SQL-Statement XUPDATE...
            sql = new StringBuilder();
            sql.AppendLine("XUPDATE employee");
            sql.AppendLine("SET LAST_NAME = 'Tom'");
            sql.AppendLine("WHERE EMPLOYEE_CODE = 20000");
            queries.Add(sql.ToString());

            // OK
            sql = new StringBuilder();
            sql.AppendLine("UPDATE employee");
            sql.AppendLine("SET LAST_NAME = 'Tom'");
            sql.AppendLine("WHERE EMPLOYEE_CODE = 20000");
            queries.Add(sql.ToString());

            // ERROR: SQL-Statement XUPDATE...
            sql = new StringBuilder();
            sql.AppendLine("XUPDATE employee");
            sql.AppendLine("SET LAST_NAME = 'Tom'");
            sql.AppendLine("WHERE EMPLOYEE_CODE = 20000");
            queries.Add(sql.ToString());

           // WARNING: Leeres Ergebnis
            sql = new StringBuilder();
            sql.AppendLine("UPDATE ts$$004.employee");
            sql.AppendLine("SET LAST_NAME = 'Manni'");
            sql.AppendLine("WHERE EMPLOYEE_CODE = 120000");
            queries.Add(sql.ToString());

            dbConnector.ExecuteWithChaining(queries);

You might see incorrect row numbers for rows in error/warning.
e.g: 2, 4, 6 instead of 2, 4, 5

****************************************************************
* USERS AFFECTED:                                              *
* .NET applications                                            *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 version 11.1.4.4                              *
****************************************************************

NA

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

16.05.2018
02.12.2018
02.12.2018