IBM Support

IT26085: LOAD'S SQL3227W MESSAGE AFTER HITTING WARNINGCOUNT LIMIT MAY GIVE INCORRECT LINE NUMBER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • When running LOAD with CPU_PARALLELISM > 1 (and when "modified
    by anyorder" option is not used explicitly or implicitly), LOAD
    ridder thread emits SQL3227W messages to map tokens such as
    "F6-1368" to row number.
    
    When WARNINGCOUNT option is used, LOAD should stop processing as
    soon as WARNINGCOUNT limit is reached, and for technical reasons
    LOAD ridder can no longer keep track of row number accurately
    after WARNINGCOUNT limit is first reached.  However, because
    LOAD runs multiple formatter threads asynchronously when
    CPU_PARALLELISM > 1, after the first formatter thread hits
    WARNINGCOUNT limit (and LOAD begins to terminate), other
    formatter threads may also hit WARNINGCOUNT limit before they
    receive notification to terminate, and they emit warning
    messages that cause ridder thread to emit SQL3227W messages, and
    these SQL3227W messages (after the one at the time when
    WARNINCOUNT limit is first hit) may contain incorrect row
    number.
    
    This fix is to make LOAD stop emitting SQL3227W messages after
    we hit WARNINCOUNT limit the first time, thus avoid giving
    SQL3227W messages with incorrect row numbers.
    
    Secondly, if dumpfile option is used, then we also stop any
    subsequent formatter threads that hit WARNINGCOUNT limit (after
    the first formatter that hit it) from writing the
    row-that-caused-warning into the dumpfile, thus the dumpfile
    will only contain one row that is written due to hitting
    WARNINGCOUNT limit.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * some RFE request,  give more error.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * REF and delivered                                            *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT26085

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-08-27

  • Closed date

    2019-07-08

  • Last modified date

    2019-07-08

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

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

Fix information

Applicable component levels

  • RB10 PSN

       UP

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

Document Information

Modified date:
08 July 2019