PM30991: PROHIBIT RECOVER BACKOUT YES AFTER MASS DELETE ON SEGMENTED OR U TS

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Prohibit the RECOVER utility with the BACKOUT YES option if a
    SQL mass delete has occurred on a segmented tablespace or UTS
    (Universal table space).
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 10 for z/OS utility users of the     *
    *                 RECOVER utility with the BACKOUT YES         *
    *                 option.                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Prohibit the RECOVER utility with the   *
    *                      BACKOUT YES option from executing       *
    *                      after a mass DELETE, TRUNCATE TABLE,    *
    *                      DROP TABLE, or ALTER TABLE ROTATE       *
    *                      PARTITION on a table in a segmented     *
    *                      table space or universal table          *
    *                      space (UTS).                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
      When a SQL mass DELETE (DELETE without a WHERE clause),
    TRUNCATE TABLE, DROP TABLE, or ALTER TABLE ROTATE PARTITION
    is executed on a segmented table space or UTS, the deleted,
    truncated, or dropped data is not logged.  The mass delete,
    TRUNCATE TABLE, DROP TABLE, and ALTER TABLE ROTATE PARTITION
    cannot always be correctly backed out by RECOVER BACKOUT YES.
    The results are unpredictable.  Incorrect output, data loss,
    or abends could occur.
      This APAR also addresses an additional problem where RECOVER
    BACKOUT YES on an index is allowed to execute when activity on
    its underlying table space should disallow the recovery of the
    index.  A sample scenario:
      - LOAD LOG(NO) on the table space
      - RECOVER BACKOUT YES TOLOGPOINT X'...' on an index over
          the tablespace is allowed, but should receive
          msgDSNU556I (RECOVER CANNOT PROCEED FOR ... BECAUSE
          A SYSIBM.SYSCOPY RECORD HAS BEEN ENCOUNTERED ...) with
          RC8.
    Additional keywords:  ABEND04E RC00C90101 DSNIBHUN MSGDSNI012I
    

Problem conclusion

  •   A SYSIBM.SYSCOPY record with an ICTYPE of 'L', an SYTPE of
    'M', and LOWDSNUM equal to the OBID of the affected table is
    now inserted during SQL mass DELETE, TRUNCATE TABLE, DROP
    TABLE, or ALTER TABLE ROTATE PARTITION on a segmented table
    space or UTS.
      When a RECOVER with the BACKOUT YES option is requested
    after a mass DELETE, TRUNCATE TABLE, DROP TABLE, or
    ALTER TABLE ROTATE PARTITION has occurred on a segmented
    table space or UTS, msgDSNU556I (RECOVER CANNOT
    PROCEED FOR ... BECAUSE A SYSIBM.SYSCOPY RECORD HAS BEEN
    ENCOUNTERED ...) with RC8 will be issued and the recovery of
    the object will not be allowed.  Note that if the table
    space has indexes or auxiliary objects (LOB or XML table
    spaces and all auxiliary indexes) RECOVER BACKOUT YES is
    also not supported on these objects when mass DELETE,
    TRUNCATE TABLE, DROP table, or ALTER TABLE ROTATE PARTITION
    has occurred on the base table space.
      The additional problem has also been addressed.  RECOVER
    BACKOUT YES on an index now checks correctly for activity
    on its underlying table space which would prohibit recovery.
    In this case, msgDSNU556I with RC8 will be issued and the
    recovery will not be allowed.
      The following documentation changes have been requested
    for PM30991.
    ..
      DB2 10 SQL Reference Manual, Appendix DB2 Catalog Tables,
      SYSIBM.SYSCOPY:
        ICTYPE column 'L' = SQL (type of operation)
          STYPE column 'M' = mass DELETE, TRUNCATE TABLE,
            DROP TABLE, or ALTER TABLE ROTATE PARTITION
          LOWDSNUM column contains table OBID of affected table
    ..
      DB2 10 Messages Manual, DSNU556I explanation:
        ICTYPE=L, STYPE=M
          Indicates that a SQL mass DELETE, TRUNCATE TABLE,
          DROP TABLE, or ALTER TABLE ROTATE PARTITION on a
          segmented table space or universal table space
          occurred.  The LOWDSNUM column contains the OBID
          of the affected table.  The BACKOUT YES option for
          RECOVER is not supported.
    ..
      DB2 10 Utility Guide and Reference, Chapter 23
      RECOVER, section "Planning for point-in-time
      recovery", a new bullet is added under "Restrictions":
       -RECOVER cannot backout (BACKOUT YES) the changes for a
        SQL mass DELETE (DELETE without a WHERE clause),
        TRUNCATE TABLE, DROP TABLE, or ALTER TABLE ROTATE
        PARTITION on a segmented table space or
        universal table space.  Note that if the table space
        has indexes or auxiliary objects (LOB or XML table
        spaces), RECOVER BACKOUT YES is also not supported on
        these objects, when mass DELETE, TRUNCATE TABLE,
        DROP TABLE, or ALTER TABLE ROTATE PARTITION has
        occurred on the base table space.
    

Temporary fix

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

Comments

  • ž**** PE12/01/04 FIX IN ERROR. SEE APAR PM52724  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PM30991

  • 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-01-21

  • Closed date

    2011-03-30

  • Last modified date

    2012-07-03

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

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

    UK66327

Modules/Macros

  •    DSNDUAIN DSNISEGD DSNUADP1 DSNUAINS DSNUBINS
    DSNUCASA DSNUYAS2
    

Publications Referenced
GC19297101 SC19298401 SC19298301    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK66327

       UP11/05/05 P F105

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.



Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for z/OS

Software version:

A10

Reference #:

PM30991

Modified date:

2012-07-03

Translate my page

Machine Translation

Content navigation