IBM Support

PI27932: DATA CORRUPTION WITH BRF DATA

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Abends seen were :
    ABENDS0C7 in DSNXGRDS DSNXROHB OFFSET2550
    ABEND 0C7 in DSNUTILA DSNUULVA OFFSET212A
    ABEND0C7  in DSNXGRDS DSNXRTIM OFFSET6B98
    after UPDATE in DB2 version 11 with these conditions:
    - the data are in basic row format ( BRF )
    - one of the updated rows has a length larger then 4096 bytes
    
    - there is a mixture of varying length columns and fixed length
    columns being updated
    

Local fix

  • n.a.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 11 for z/os users using tables with  *
    *                 basic row format(BRF) and the maximal row    *
    *                 size is greater than 4096 bytes.             *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABND0C7,LOC=DSNXGRDS.DSNXROHB,          *
    *                      ABND0C7,LOC=DSNUTILA.DSNUULVA or        *
    *                      other DB2 ABEND or incorrect output may *
    *                      occur when processing a row that was    *
    *                      corrupted by UPDATE statement.          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This problem occurs when doing an UPDATE to a row with maximal
    row size greater than 4096 bytes, and the row being updated is
    in basic row format(BRF) and it has both varying length and
    fixed length columns. This problem only happens when optimized
    UPDATE code(UPROC) is used. The optimized UPDATE code(UPROC) is
    generated based upon the attributes of a given table definition.
    The UPROC code was incorrectly building an instruction that
    caused the updated row to be corrupted. The data corruption
    could cause different DB2 ABENDs or incorrect output.
    

Problem conclusion

  • Code has been changed to update the row correctly when the row
    is in basic row format and the maximal row length is greater
    than 4096 bytes.
    Additional Keywords:
    SQLUPDATE INCORROUT
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI27932

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-10-20

  • Closed date

    2014-12-05

  • Last modified date

    2015-01-02

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

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

    UI23666

Modules/Macros

  •    DSNILREP DSNIZREP
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RB10 PSY UI23666

       UP14/12/20 P F412 Ž

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

Document Information

Modified date:
06 May 2020