IBM Support

PM51663: DATA CAPTURE BIT NOT ON FOR SYSTABLESPACE UPDATE IN REORG SHRLEVEL REFERENCE.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Create a segmented tablespace, insert some rows, then ALTER it
    to UTS tablespace via SQL:
     ALTER TABLESPACE SXPDB.TAB2PART  MAXPARTITIONS 2         ;
    
    The above ALTER causes the tablespace to be placed in AREOR
    status, then performed a REORG to activate the change requested
    by the prior ALTER.
    
    The above REORG causes updates to be done to
    SYSIBM.SYSTABLESPACE, SYSIBM.SYSCOLUMNS, and SYSIBM.SYSTABLES.
    (PS: These tables already ALTERed to Data Capture CHANGES) The
    problem occurs here: the log records generated for these
    updates do *not* have the Data Capture flag turned on, even
    though SYSIBM.SYSTABLESPACE, SYSIBM.SYSCOLUMNS, and
    SYSIBM.SYSTABLES are defined with the DATA CAPTURE CHANGES
    option.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 10 for z/OS users of REORG SHRLEVEL  *
    *                 REFERENCE with deferred ALTER materilization *
    *                 on CDC catalog table objects.                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Data Capture flag is not logged for     *
    *                      catalog table updates by REORG SHRLEVEL *
    *                      REFERENCE with deferred ALTER           *
    *                      materialization.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A REORG SHRLEVEL REFERENCE is run on a table space after it has
    been altered to a partitioned-by-growth attribute.  The REORG
    modifies catalog tables which have DATA CAPTURE CHANGES defined,
    but those log records generated for these updates have not been
    logged as 'Data Capture'.
    

Problem conclusion

  • DB2 code has been fixed to log 'Data Capture' flag on catalog
    update during the REORG materializing pending ALTER.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PM51663

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-11-06

  • Closed date

    2012-03-15

  • Last modified date

    2012-04-03

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

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

    UK77096

Modules/Macros

  • DSNIDILS DSNILREP DSNIQGSE DSNIREPR DSNISDLE
    DSNISGRT DSNISMRT DSNUGPAM
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK77096

       UP12/03/31 P F203

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":"10.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":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 April 2012