IBM Support

IT22386: DB2 : IF ANY COMMAND WITH RECLAIM EXTENTS OPTION IS RUN ON AN MDC TABLE DURING A BACKUP, A ROLLFORWARD ON IT COULD FAIL

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • - When one or more commands like "TRUCATE TABLE with REUSE
    STORAGE option" or "AUTO or MANUAL REORG TABLE with RECLAIM
    EXTENTS option" i.e. commands which perform a "reclaim extents"
    operation are executed on an MDC table while an online backup is
    in progress,
    DB2 frees those extents for the table, but the operation is not
    logged correctly.
    The backup completes successfully.
    
    - Restore of this backup is also successful.
    
    - When the Rollforward is executed, DB2 tries to replay a
    "create new block" operation in logs for the table in question
    and fails with following error as these extents are no more
    available, they were already freed .
    
    db2diag.log will have LEVEL: Error message:
    
    FUNCTION: DB2 UDB, buffer pool services, sqlbExtendObject,
    probe:650
    MESSAGE : ZRC=0x8402001A=-2080243686=SQLB_EMP_MAP_INFO_END "EMP
    MAP INFO END"
    
    The fix will ensure that the "reclaim extent" operations run
    during backup are logged correctly so replay during rollforward
    will not fail.
    

Local fix

  • As a workaround, please avoid running the following when there
    is an online backup in progress:
    
    1) TRUCATE TABLE with the REUSE STORAGE option on an MDC table
    2) REORG TABLE with the RECLAIM EXTENTS option (AUTO or MANUAL)
    on an MDC table
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 2 Fix Pack 2 iFix002 or higher       *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 2 Fix Pack 2 iFix002
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT22386

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-09-13

  • Closed date

    2017-12-22

  • Last modified date

    2017-12-22

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

    IT22352

  • 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

[{"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":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
22 December 2017