PH60403: RC 8 AND MESSAGE INZC004E OR INZI503E USING DDLDDN OPTION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Db2 HPU terminates in error with after having issued either of
  the following messages:
  
  - INZC004E INCOMPLETE OBJECT DEFINITION FOR TABLESPACE
    dbname.tsname    PARTITIONNING INDEX MISSING
  
  - INZI503E DDL ANALYSING: SYNTAX ERROR AT POS(n, p)
  
  This occurs when all the following conditions are fulfilled:
  
  - unload using the DDLDDN option
  
  - the input DDL defines a partitioned index having at least one
  partition with a range value (START or END) that exceeds the
  maximum value of an INTeger (i.e. 2,147,483,647) expressed as a
  BIGINT value (i.e. with no decimal point).
  
  For example, the input DDL contains:
  
  CREATE UNIQUE INDEX creator.ixname
  ON dbname.tsname
  
  (COL1             ASC,
  COL2              ASC,
  COL3              ASC)
  
  ...
  
  PARTITION 1 ENDING AT (1019999999999999),
  with COL1 having the following definition:
  
  COL1                DECIMAL(17, 0) NOT NULL,
  

Local fix

• Alter the input DDL to replace the range value(s) triggering the
  issue by any INTEGER (integer less or equal to 2,147,483,647)
  or DECIMAL value (value with a decimal point). As the range
  values are not used by Db2 HPU, a fake value can be specified.
  A solution for the above example is to replace
  PARTITION 1 ENDING AT (1019999999999999),
  by
  PARTITION 1 ENDING AT (1019999999999999.),
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 High Performance Unload for     *
  *                 z/OS                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: Db2 HPU terminates in error with        *
  *                      completion code of 8 after having       *
  *                      issued either of the following          *
  *                      messages :                              *
  *                      - INZC004E INCOMPLETE OBJECT            *
  *                      DEFINITION FOR TABLESPACE               *
  *                      dbname.tsname                           *
  *                      PARTITIONNING INDEX MISSING             *
  *                      - INZI503E DDL ANALYSING: SYNTAX ERROR  *
  *                      AT POS(n, p)                            *
  *                                                              *
  *                      This occurs when all the following      *
  *                      conditions are fulfilled:               *
  *                      - the unload specifies the DDLDDN       *
  *                      option                                  *
  *                      - the input DDL defines a partitioned   *
  *                      index having at least one partition     *
  *                      with a range value (START or END) that  *
  *                      exceeds the maximum value of an         *
  *                      INTeger (i.e. 2,147,483,647) expressed  *
  *                      as a BIGINT value (i.e. with no         *
  *                      decimal point).                         *
  *                                                              *
  *                      Note : the issue occurs whenever the    *
  *                      key value is expressed as a BIGINT      *
  *                      value even if the related key column    *
  *                      has a decimal type.                     *
  *                                                              *
  *                      For example, the issue occurs if the    *
  *                      following DDL is provided to Db2 HPU    *
  *                      through the DDLDDN option:              *
  *                      CREATE UNIQUE INDEX NGDBA.BICRHIS0      *
  *                      ON me.mytable                           *
  *                      (COL1              ASC,                 *
  *                      COL2               ASC,                 *
  *                      COL3               ASC)                 *
  *                      ---                                     *
  *                      PARTITION 1 ENDING AT                   *
  *                      (1019999999999999),                     *
  *                                                              *
  *                      with COL1 having the following          *
  *                      definition:                             *
  *                                                              *
  *                      COL1                DECIMAL(17, 0) NOT  *
  *                      NULL,                                   *
  *                                                              *
  *                      Local fix: Alter the input DDL to       *
  *                      replace the range value(s) triggering   *
  *                      the issue by any INTEGER (integer less  *
  *                      or equal to 2,147,483,647) or DECIMAL   *
  *                      value (value with a decimal point).     *
  *                      As the range values are not used by     *
  *                      Db2 HPU, a fake value can be specified. *
  *                                                              *
  *                      A solution for the above example is to  *
  *                      replace :                               *
  *                      PARTITION 1 ENDING AT                   *
  *                      (1019999999999999),                     *
  *                      by                                      *
  *                      PARTITION 1 ENDING AT                   *
  *                      (1019999999999999.),                    *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF                                *
  ****************************************************************
  rc 8 and message INZC004E or INZI503E using DDLDDN option
  

Problem conclusion

• Code has been changed to fix this problem
  

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:

  UI96999

Modules/Macros

• INZUTILK
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R510 PSY UI97000

     UP24/05/24 P F405

• R520 PSY UI96999

     UP24/05/24 P F405

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.