suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT35678 Status: Closed

UNDER CERTAIN CONDITIONS, THE "NUMBER OF ROWS ..." MESSAGE FROM INGEST
UTILITY ARE INCORRECT.

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Under certain conditions, the "Number of rows ..." messages that
the ingest utility prints at the end of each ingest job can show
values that are incorrect.  (Likewise, fields oRowsRead,
oRowsInserted and similar fields that the db2Ingest API returns
can have values that are incorrect.)
.
- Under certain rare conditions that depend on internal thread
timing, the "Number of rows read" can be 1 less than the actual
number.
.
- When input records are rejected by DB2 and depending on
internal thread timing, the "Number of rows inserted" can be
less than the actual number.  The amount by which the value is
off can be from 1 to the actual number of rows rejected.  For
example, if DB2 rejects a total of 3 input records due to
duplicate keys, the "Number of rows inserted" could be too small
by anywhere from 1 to 3 rows.
.
- When the ingest utility ends because the number of errors
exceeds the WARNINGCOUNT parameter (message SQL3502N), the
"Number of rows rejected" can be 1 too small.
.
- When the ingest utility ends because of a terminating error
(including exceeding the WARNINGCOUNT), the "Number of rows
rejected" might be higher than the number of previous error
messages you see that report rejected rows.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to db2_v111m4fp6 or higher                           *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to db2_v111m4fp6 or higher                           *
****************************************************************
Comment
Upgrade to db2_v111m4fp6 or higher
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.01.2021
31.03.2021
31.03.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)