IBM Support

PM44307: ABEND0C7 ON DICTIONARY EXPANSION OF COMPRESSED ROW

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An 0C7 on an expansion instruction, CMPSC . Some modules that
    may get an 0C7 DSNISRID DSNIONX2 DSNURWBF
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: DB2 for z/OS users of Partition By Growth    *
    *                 ( PBG ) table spaces that make use of data   *
    *                 compression or that may have different row   *
    *                 formats (RRF, BRF) in each partition.        *
    ****************************************************************
    * PROBLEM DESCRIPTION: S0C7 ABEND0C7 during read of compressed *
    *                      PBG table space in DSNUULXA+4A34.       *
    *                      ABND04E RC00C90101 DSNIKESR ERQUAL500B. *
    *                      ABND0C7 DSNIONX2+4DD2.                  *
    *                      ABND0C7 DSNISRID+5304.                  *
    *                      ABND04E RC00E4D5D2 DSNUULVA+0C9A.       *
    *                      ABND0C7 DSNURWBF+DC68.                  *
    *                                                              *
    *                      Other similar abends resulting from a   *
    *                      broken data row.                        *
    ****************************************************************
    * RECOMMENDATION: This problem occurred in DB2 during INSERT   *
    *                 processing when space search algorithms      *
    *                 rotated back to a starting partition. On     *
    *                 this condition, DB2 code avoided the row     *
    *                 reformatting logic. Should the compression   *
    *                 dictionaries differ or the partitions        *
    *                 have a mix of RRF or BRF row format, the     *
    *                 data row can be inserted in the wrong row    *
    *                 format. This then leads to sundry abends     *
    *                 when the row is read at a later point.       *
    *                                                              *
    *                 The problem can be avoided if the same       *
    *                 compression dictionary is used by all PBG    *
    *                 partitions and the row format for all the    *
    *                 partitions are either Reordered Row Format   *
    *                 ( RRF ) or Basic Row format ( BRF ). The     *
    *                 compression dictionaries for a PBG table     *
    *                 space can differ when REORG by PART is run   *
    *                 on individual partitions.                    *
    ****************************************************************
    Various DB2 abends were seen during decompression of some
    data rows in a PBG table. The broken rows were compressed
    using a dictionary other than the one in use for the PBG
    partition. Problems may also be seen with invalidly formatted
    rows (RRF or BRF) ending up in the wrong partition.
    These problems originated when there was insufficient space in
    the PBG partitions and space search rotated back to the starting
    partition. The logic to reformat the row correctly was not
    getting executed for this condition. This led to broken data
    rows.
    

Problem conclusion

  • DB2 code has been changed to ensure that a row will always be
    reformatted correctly when space search algorithms rotate back
    to the starting partition.
    
    Additional keywords: ABEND04E SQLPBG SQLINSERT
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PM44307

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-07-22

  • Closed date

    2011-08-31

  • Last modified date

    2011-10-03

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

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

    UK71476 UK71477

Modules/Macros

  • DSNDINPL DSNDLGB  DSNDQJ00 DSNISGRT
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK71476

       UP11/09/15 P F109

  • R910 PSY UK71477

       UP11/09/15 P F109

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 October 2011