|
Problem IT03433
|
Status: Closed |
ROW NUMBER 1 RETURNED ALWAIS AS ROW IN ERROR WHEN DURING CHAINED INSERT ERROR CLI0113E GOT REPORTED FOR ANY ROW |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
When using the DB2BulkCopy.WriteToServer() method of the .Net
provider, if a CLI error is thrown because of bad data the
DB2Error.RowNumber does
not return the number of the row that has the bad data.
DB2Error.RowNumber is always set to 1 in this case.
The problem is happening on the CLI layer. Incorrect row number
is being propagated to .Net application from the CLI layer. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to v10.5 fp5 or later *
**************************************************************** |
| Local Fix: |
|
| Solution |
First fixed in v10.5fp5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.07.2014
27.03.2015
27.03.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.5
|
 |
