PI47967: COPY UTILITY CORRUPTS SPACE MAP PAGE IN CERTAIN SCENARIOS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When some parts of a partitioned table space have been converted
  to extended RBA format, but not all, a COPY utility run at the
  full table space level can truncate entries in the space map
  page.  The resulting corruption means that any table space scan
  operation may miss data.  A subsequent REORG that unloads data
  via a table space scan will not include rows on the pages that
  are no longer pointed to by the space map page, resulting in
  data loss.
  
  REORG that unloads data via index will extract all the rows, and
  correct the space map page.
  
  DB2EXTRBA/K ExtendedRBA
  

Local fix

• If not converting all parts of a partitioned table space to
  extended format at the same time, then use only part level image
  copies until the full table space has been converted
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 11 for z/OS users of COPY utility    *
  *                 on partitioned table spaces                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Missing or corrupted data following     *
  *                      FULL COPY utility with DSNUM ALL on a   *
  *                      partitioned table space when some, but  *
  *                      not all partitions are in extended      *
  *                      RBA / LRSN page format.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
    User ran a full COPY utility (FULL YES) with DSNUM ALL
  against a partitioned table space in which some, but not all
  partitions had been converted to extended page format.
    The COPY completed normally, but later certain queries
  and operations accessing the data failed due to rows not
  found which should have been there.
    This happened because COPY incorrectly used information from
  the first partition to derive the offset to the page modified
  bits for all space map pages in all partitions.  Since some
  of the partitions had been converted to extended RBA/LRSN page
  format, this offset was not the same in all partitions.
  This led to missing data because COPY, as it reset all page
  modified bits in subsequent partitions, inadvertently cleared
  some segment data information residing on space map pages.
    In addition to missing data, symptoms could include various
  abends from queries, vendor products, or other utilities.
    This problem may also occur for TRACKMOD NO table spaces
  during COPY if the TRACKMOD attribute has been altered more
  than once.
  

Problem conclusion

• COPY utility code was changed to recalculate the offset to
  the page modified bits in the space map pages for each partition
  of a partitioned table space.
  

Temporary fix

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

Comments

APAR Information

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

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

  UI31412

Modules/Macros

• DSNUBAID DSNUBASM
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RB10 PSY UI31412

     UP15/10/08 P F510

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.