IBM Support

IC96718: A LOAD COMMAND WITH LOW WARNINGCOUNT MIGHT HANG

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The Load hang might occur under the following conditions:
    1) Low WARNINGCOUNT is specified (e.g. 1).
    2) High CPU_PARALLELISM and/or DISK_PARALLELISM are specified
    explicitly or implicitly.
    3) Data file contains lots of consecutive invalid rows that can
    cause Load Formatters to hit the WARNINGCOUNT very quickly.
    
    When the Load is hanging, you can see the following stack for
    db2agent (i.e. Load agent), but other Load EDUs have exited
    already:
    msgsnd
    uninterruptableMsgSnd
    sqlowqueInternal
    sqlowqueWrapper
    sqlowque
    sqluWriteQueue
    sqlulSndTermMsg
    sqlulTerminate
    sqlulPrcErr
    sqlulFRMResponse
    sqlulPollMsg
    sqluvload
    call_sqluvload
    sqluLoadPartition
    sqlu_register_table_load
    sqluvtld_route_in
    sqlesrvr
    sqleMappingFnServer
    sqlerKnownProcedure
    
    Please note that you might not be able to interrupt the hanging
    Load.
    

Local fix

  • Workaround:
     1)Use Load without the warningcount
     2)Reduce CPU_PARALLELISM and/or DISK_PARALLELISM
     3)Correct the input data to avoid too many warnings generated.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Problem Description above.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version V9.7 Fix Pack 9                       *
    ****************************************************************
    

Problem conclusion

  • First Fixed in DB2 Version V9.7 Fix Pack 9
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC96718

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-10-08

  • Closed date

    2014-02-04

  • Last modified date

    2014-02-04

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

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

    IC96847 IC96848 IC97046 IC97065

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP

  • RA10 PSN

       UP

  • RA50 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
04 February 2014