IBM Support

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

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error 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.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * all                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to db2_v111m4fp6 or higher                           *
    ****************************************************************
    

Problem conclusion

  • Upgrade to db2_v111m4fp6 or higher
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT35678

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-01-22

  • Closed date

    2021-03-31

  • Last modified date

    2021-03-31

  • APAR is sysrouted FROM one or more of the following:

    IT11417

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1"}]

Document Information

Modified date:
01 April 2021