PI68813: ABEND @ DSNIDM.DSNISHPI:2002 WHEN INSERT INTO HASH UTS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When PBG grows a new part for HASH Access, the new part is not
  formatted as HASH org access.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All DB2 12 for z/OS users of Partition-By-Growth table       *
  * spaces (PBG) containing tables organized by hash             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * ABEND04E at DSNIDM DSNISHPI ERQUAL5002 when inserting data   *
  * to a table organized by hash and the table space is an       *
  * explicitly defined PBG table space.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  DB2 may incorrectly format partitions for explicitly defined PBG
  table spaces if the partition was implicitly added as a result
  of creating a hash-organized table.
  For example,
  
  CREATE TABLESPACE TEST01TS IN TEST01DB
    MAXPARTITIONS 256
    SEGSIZE 4
    MAXROWS 1
    DSSIZE 1G
    LOCKSIZE ROW;
  COMMIT;
  
  CREATE TABLESPACE TEST01TS IN TEST01DB
    MAXPARTITIONS 256
    SEGSIZE 4
    MAXROWS 1
    DSSIZE 1G
    LOCKSIZE ROW;
  COMMIT;
  CREATE TABLE TEST01TB (
  
                C1 CHAR(4) NOT NULL,
  
                C2 VARCHAR(8) NOT NULL,
  
                C3 CHAR(4))
  
    ORGANIZE BY HASH UNIQUE (C1, C2) HASH SPACE x M
  
    IN TEST01DB.TEST01TS;
  
  When the table space TEST01TS is created only one part is
  created. When table TEST01TB is create in the table space
  TEST01TS with x M size HASH SPACE, DB2 calculates that a total
  of y parts are needed to hold x M data. So internally DB2
  implicitly
  adds y-1 parts. However only the first part is formatted with
  hash organization.
  
  
  
  ABEND04E DSNISHPI:5002 may occur on the INSERT or LOAD to the
  part not being formatted as hash correctly.
  

Problem conclusion

• DB2 code has been changed to format all the parts in
  hash-organized access.
  
  Applying APAR  does not fix problems that were introduced
  before applying the fix. There are two ways to fix the problem,
  
     A. run REORG with SHRLEVEL REFERENCE against the table
  
        spaces.
  
     B. after applying the APAR, drop and re-create the table
  
        spaces can also fix the problem.
  
  
  Addiotnal keywords:
  SQLPBG
  SQLCREATE
  SQLINSERT
  
  APAR PI68832 fixes the same problem for DB2 11 for z/OS
  

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:

  UI43353

Modules/Macros

• DSNGDAPT
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI43353

     UP17/01/05 P F701

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.