PI15667: ABEND04E RC00C90110 DSNIPTYM ERQUAL5005 RUNNING ALTER

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• ABEND04E RC00C90110 DSNIPTYM ERQUAL5005 on ALTER INDEX.
  Dump Title: DA11,ABND=04E-00C90110,U=DBM1PXT ,M=N  ,C=101.DMC
  -DSNIMPTY,M=DSNTFRCV,LOC=DSNIDM  .DSNIPTYM:5005
  1) REPAIR DBD DIAGNOSE before alter - 0 errors
  2) ALTER INDEX D414P00.IOPKGSC1 NOT CLUSTER fails
  3) REPAIR DBD DIAGNOSE after alter - 13 errors
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 9, 10 and 11 for z/OS users of       *
  *                 index-controlled partitioning table.         *
  ****************************************************************
  * PROBLEM DESCRIPTION: User received the following abend:      *
  *                      ABEND04E RC00C90110                     *
  *                      DSNIDM.DSNIPTYM:5005 during an ALTER    *
  *                      INDEX statement that converts the       *
  *                      table from index-controlled to table-   *
  *                      controlled partitioning.                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During the conversion processing from index-controlled
  partitioning to table-controlled partitioning, if user has
  the zparm IX_TB_PART_CONV_EXCLUDE set and the object being
  converted was created prior to V6 with a 40 bytes limit key
  limit, DB2 did not handle the conversion properly.  This
  resulted in user receiving the reported abend during the
  conversion.
  
  Please note that this problem can result in other unexpected
  DB2 errors, abends, and behaviors.  Some of the known ones are:
  
  - REPAIR DBD reporting error after conversion:
    For example:
      OBDS DIFFER AT OFFSET X'000002FE' OBDPSNXT(7) -
      INFORMATION NOT IN D
        EXISTING VALUE  X'0000'
        REBUILT  VALUE  X'0358'
      OBDS DIFFER AT OFFSET X'00000300' OBDPSPRV(7) -
      INFORMATION NOT IN D
        EXISTING VALUE  X'0000'
        REBUILT  VALUE  X'0288'
      OBDS DIFFER AT OFFSET X'00000666' OBDLMKY(1:XMINLN)
  - data being placed in wrong partition after conversion
  - SYSTABLEPART.LIMITKEY_INTERNAL might contain incorrect
    value
  
  Since the problem occurs during the conversion processing
  from index-controlled to table-controlled partitioning, other
  paths might be affected also.  The following are potential
  paths that might be affected:
  
  - ALTER TABLE ADD PARTITION
  - ALTER TABLE ALTER PARTITION
  - ALTER TABLE ROTATE PARTITION
  - ALTER TABLE ADD CLONE
  - ALTER INDEX
  - DROP INDEX
  
  
  This APAR also addresses the issue where the 'MAXVALUE'
  external limit key value for the last partition was
  populated incorrectly during the conversion from
  index-controlled partitioning to table-controlled.
  
  For example:
   SYSTABLEPART.LIMITKEY contains 'MAXVALUE, MAXVALUE, MAXVAL'
  
  This particular 'MAXVALUE' issue is not related to the 40
  bytes limit.  Please note that this external limit key value
  is for reference purpose only and does not affect DB2
  functionality.
  

Problem conclusion

• DB2 has been fixed to handle pre-V6 objects with 40 bytes
  limit properly during the index-controlled to table-
  controlled partitioning conversion when user has the zparm
  IX_TB_PART_CONV_EXCLUDE set to YES to exclude insignificant
  key columns.
  
  DB2 has been fixed to populate 'MAXVALUE' properly for the
  last partition during the index-controlled to table-
  controlled partitioning conversion.
  
  Please note that applying this apar will not fix any existing
  objects.  Customer will need to drop and recreate the table
  to correct the problem.
  
  Additional Keywords:
  SQLCODE663
  SQLALTER
  SQLCREATE
  SQLDROP
  SQLTABLE
  SQLINDEX
  SQLINCORR
  SQLINCORROUT
  INCORROUT
  DB2INCORR/K
  DB2OVRLAY/K
  

Temporary fix

• *********
  * HIPER *
  *********
  PI15667
  

Comments

• ž**** PE15/04/16 PTF IN ERROR. SEE APAR PI39264  FOR DESCRIPTION
  

APAR Information

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

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

  UI20172 UI20173 UI20174

Modules/Macros

• DSNXIAB6 DSNXIAB7 DSNXISB6
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI20172

     UP14/08/18 P F408

• RB10 PSY UI20173

     UP14/08/18 P F408

• R910 PSY UI20174

     UP14/08/18 P F408

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.