PK52136: XML TABLE SPACE NOT INHERITING INSTANCE NUMBER FROM BASE TABLE SPACE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• XML table space not inheriting instance number from base table
  space
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 V9 users of XML tables with clone    *
  *                 tables.                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: REPAIR DBD DIAGNOSE issues warning      *
  *                      message DSNU920I for various fields,    *
  *                      including OBDPSINS.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  DB2 is incorrectly setting the instance number to 1 for the
  implicitly created XML table space in the following scenario:
  1. ALTER TABLE ADD CLONE
  2. EXCHANGE DATA
  3. ALTER TABLE DROP CLONE
  4. ALTER TABLE ADD XML column
  
  After ALTER TABLE ADD CLONE and EXCHANGE DATA, the instance
  number for the base table space becomes 2.  However, when an XML
  table space is implicitly created from adding an XML column, it
  is not correctly inheriting the instance number from the base
  table space, and the default value of 1 is used instead.  The
  wrong value is stored in the OBD and in the catalog table
  SYSIBM.SYSTABLESPACE, column INSTANCE.  This inconsistency is
  reported by REPAIR DBD and could result in other unexpected
  behaviors.
  

Problem conclusion

• DB2 code has been fixed to inherit the instance number from the
  base table space correctly for XML table spaces.
  
  This PTF will not fix existing XML table spaces with incorrect
  instance number.  To recreate an XML table space with correct
  instance number, the base table would have to be dropped and
  recreated after applying this PTF.
  
  ADDITIONAL KEYWORDS:
  SQLALTER
  

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:

  UK31510

Modules/Macros

• DSNXIATB DSNXICTB DSNXICTS
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• R910 PSY UK31510

     UP07/12/11 P F712

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.