PM73165: CATMAINT UPDATE VCAT SWITCH TAKING MUCH LONGER UNDER DB2 10 AND MAY ABEND WITH REASON=X'00E20013'

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A CATMAINT UPDATE VCAT SWITCH that involes a very large number
  of objects being renamed is taking much longer under DB2 10 then
  it was under DB2 9. In some cases is may abend with REASON
  X'00E20013'.
  
  RC00E20013 indicates "unable to obtain sufficient storage in
  private area".
  
  The Utility address space may also abend with a S322.
  

Local fix

• No work around for the 00E20013 abend.
  A TIME=NOLIMIT on the Utility job can prevent the S322 abend.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
  *                 utility users of CATMAINT UPDATE VCAT        *
  *                 SWITCH                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: CATMAINT UPDATE VCAT SWITCH fails       *
  *                      with ABEND04E RC00E20013 in             *
  *                      DSNSGMN+1104                            *
  ****************************************************************
  * RECOMMENDATION: Apply corrective PTF when available          *
  ****************************************************************
  CATMAINT UPDATE VCAT SWITCH failed with an ABEND04E RC00E20013
  in DSNSGMN+1104 when altering an index pageset OBD. This was
  due to a storage shortage. The shortage was a result of
  altering a large number of objects prior to the failure.
  Storage was allocated when altering objects and it was released
  only after the work was committed. Due to a logic error in the
  code, the commits were not done as frequently as expected and
  therefore excessive storage was accumulated.
  
  This error could also occur when using CATMAINT UPDATE SCHEMA
  SWITCH or CATMAINT UPDATE OWNER FROM (...) TO ROLE.
  

Problem conclusion

• CATMAINT code has been changed to prevent excessive storage
  accumulation.
  

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:

  UK83808 UK83809

Modules/Macros

• DSNUESCM
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK83809

     UP12/12/14 P F212

• R910 PSY UK83808

     UP12/12/14 P F212

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.