IBM Support

IC67565: IN RARE TIMING SCENARIOS, LOAD UTILITY INTO A RANGE PARTITIONED TABLE MAY TRAP WITH BAD PAGE ERROR IN SQLB_VERIFY_PAGE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When using Load utility to add data into a range partitioned
    table, a BAD PAGE error can be reported by one of the db2lbm
    processes.
    db2diag.log will include an entry similar to this::
    
    2010-02-05-02.24.11.305740+540 I60623A3957        LEVEL: Severe
    PID     : 1151192              TID  : 511867      PROC : db2sysc
    0
    INSTANCE: XXXXXXXX             NODE : 000         DB   : XXXXX
    APPHDL  : 0-18593              APPID:
    XXX.XXX.XXX.XXX.41515.100204113503
    AUTHID  : XXXXX
    EDUID   : 511867               EDUNAME: db2lbm0 0
    FUNCTION: DB2 UDB, buffer pool services, sqlb_verify_page,
    probe:2
    MESSAGE : ZRC=0x86020001=-2046689279=SQLB_BADP "page is bad"
              DIA8400C A bad page was encountered.
    
    Stack trace generated by error may contain entries like this:
    
    sqlb_verify_page
    [...]
    sqluDirectRead
    sqluTransformSendToCopyRequest
    sqluSetCBitsAndWriteBuf
    sqlulBMCont
    sqlulbuf
    sqloEDUEntry
    
    
    The problem may be more suseptible when the COPY YES option is
    used.
    Per usual Load recovery usage, execute a Load Terminate to bring
    the table back to consistent state, then you can try the Load
    again.
    

Local fix

  • Use DISK_PARALLELISM 1 to avoid the problem (this may have some
    performance impact).
    Avoiding COPY YES option may also reduce the probability of
    hitting the problem.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When using Load utility to add data into a range partitioned *
    *                                                              *
    * table, a BAD PAGE error can be reported by one of the db2lbm *
    *                                                              *
    * processes.                                                   *
    *                                                              *
    * db2diag.log will include an entry similar to this::          *
    *                                                              *
    *                                                              *
    *                                                              *
    * 2010-02-05-02.24.11.305740+540 I60623A3957        LEVEL:     *
    * Severe                                                       *
    * PID    : 1151192              TID  : 511867      PROC :      *
    * db2sysc                                                      *
    * 0                                                            *
    *                                                              *
    * INSTANCE: XXXXXXXX            NODE : 000        DB  : XXXXX  *
    * APPHDL  : 0-18593              APPID:                        *
    *                                                              *
    * XXX.XXX.XXX.XXX.41515.100204113503                           *
    *                                                              *
    * AUTHID  : XXXXX                                              *
    *                                                              *
    * EDUID  : 511867              EDUNAME: db2lbm0 0              *
    * FUNCTION: DB2 UDB, buffer pool services, sqlb_verify_page,   *
    *                                                              *
    * probe:2                                                      *
    *                                                              *
    * MESSAGE : ZRC=0x86020001=-2046689279=SQLB_BADP "page is bad" *
    *                                                              *
    * DIA8400C A bad page was encountered.                         *
    *                                                              *
    *                                                              *
    *                                                              *
    * Stack trace generated by error may contain entries like      *
    * this:                                                        *
    *                                                              *
    *                                                              *
    * sqlb_verify_page                                             *
    *                                                              *
    * [...]                                                        *
    *                                                              *
    * sqluDirectRead                                               *
    *                                                              *
    * sqluTransformSendToCopyRequest                               *
    *                                                              *
    * sqluSetCBitsAndWriteBuf                                      *
    *                                                              *
    * sqlulBMCont                                                  *
    *                                                              *
    * sqlulbuf                                                     *
    *                                                              *
    * sqloEDUEntry                                                 *
    *                                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    * The problem may be more suseptible when the COPY YES option  *
    * is                                                           *
    * used.                                                        *
    *                                                              *
    * Per usual Load recovery usage, execute a Load Terminate to   *
    * bring                                                        *
    * the table back to consistent state, then you can try the     *
    * Load                                                         *
    * again.                                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 UDB version 9.7 fix pack 3.                   *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in DB2 UDB Version 9.7 Fix Pack 3.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC67565

  • 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

    2010-03-31

  • Closed date

    2010-09-23

  • Last modified date

    2010-09-23

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

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

    IC67623 IC67624

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC67565

Modified date: 23 September 2010