PI64330: A TABLESPACE THAT WAS STARTED WITH ACCESS(UT) BEFORE REORG, IS RESET TO RW IF THE REORG MATERIALIZES A PENDING ALTER

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A user starts a tablespace access(UT) before running Reorg
  utility on it. usually after Reorg has executed the object is
  still in UT access.
  But when a previous ALTER has been done and Reorg materializes
  the pending alter during its process, then the UT access is
  reset to RW unexpectedly.
  A DISPLAY before the REORG shows :
  DSNT397I  -DB2A
  NAME     TYPE PART  STATUS            PHYERRLO
  -------- ---- ----- ----------------- --------
  TS1      TS         UT,AREOR
  .
  After the REORG:
  NAME     TYPE PART  STATUS            PHYERRLO PHYERRH
  -------- ---- ----- ----------------- -------- -------
  TS1      TS    0001 RW,UTRW
  TS1      TS
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
  *                 users of online REORG TABLESPACE utility     *
  *                 with pending alter materialization           *
  ****************************************************************
  * PROBLEM DESCRIPTION: A REORG TABLESPACE SHRLEVEL CHANGE      *
  *                      utility to materialize a pending        *
  *                      definition change to convert a          *
  *                      segmented table space to a              *
  *                      partition-by-growth (PBG) table space   *
  *                      ran successfully but removed the        *
  *                      pre-existing utility access only        *
  *                      state (UT) from the target table space. *
  ****************************************************************
  * RECOMMENDATION: Apply corrective PTF when available          *
  ****************************************************************
  A simple / segmented table space was in an Advisory REORG
  pending state (AREOR) from a prior ALTER TABLESPACE
  MAXPARTITIONS nn.  A -START DB(dname) SP(tsname) ACCESS(UT)
  command was issued against the table space.  A subsequent online
  REORG TABLESPACE utility to materialize the pending ALTER ran
  successfully but removed the UT state unexpectedly.
  
  The problem also exists for REORG TABLESPACE SHRLEVEL
  CHANGE / REFERENCE against a table space in Read or Replication
  Only (RREPL) state or Read Only (RO) state.
  

Problem conclusion

• REORG TABLESPACE SHRLEVEL CHANGE or REFERENCE code is modified
  to preserve the UT, RO or RREPL state on the target objects that
  existed prior to the REORG.
  

Temporary fix

Comments

APAR Information

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

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

  UI40204 UI40205 PI69244

Modules/Macros

• DSNURSWD
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI40204

     UP16/09/05 P F609

• RB10 PSY UI40205

     UP16/09/05 P F609

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.