IBM Support

PK51752: IMPLICIT TABLE SPACE CREATION FOR RANGE-PARTITIONED TABLES.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Implicit table space creation for range-partitioned tables.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: DB2 users of CREATE TABLE.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Implicit partition by range table space *
    *                      creation on CREATE TABLE.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This APAR is for the implementation of DK310 that enhances
    CREATE TABLE to support implicit table space creation for
    range-partitioned tables.
    
    Reason for change:
    Currently, for a CREATE TABLE with range-partitioning, and no
    table space name is specified, DB2 issues SQLCODE -20183 (THE
    PARTITIONED, ADD PARTITION, ADD PARTITIONING KEY, ALTER
    PARTITION, ROTATE PARTITION, OR PARTITION BY RANGE CLAUSE
    SPECIFIED ON CREATE OR ALTER FOR name IS NOT VALID) to put a
    restriction on implicitly creating a table space for the table.
    The user would first need to create a partitioned table space,
    then create the table with range-partitioning, instead of being
    able to take advantage of the implicit table space creation that
    is currently put in place for other kinds of tables. The change
    would help to stream-line the table and table space processing
    and provide ease of use.
    
    Change description:
    Prior to V9 NFM, if a user tried to CREATE TABLE with range-
    partitioning and without specifying the table space name, DB2
    would issue -20183. With this enhancement in V9 NFM, the
    implicit table space creation will create a partition by range
    universal table space (PBR UTS) based on the number of parts
    specified on the CREATE TABLE statement with defaults SEGSIZE
    4, LOCKSIZE ROW, and LOCKMAX SYSTEM. Other attributes of the
    table space are determined from the following ZPARM values:
    
       - IMPTSCMP: determines if the table space is defined as
                   COMPRESS YES or COMPRESS NO. The default is
                   COMPRESS NO.
       - IMPDSDEF: determines if the table space is defined as
                   DEFINE YES or DEFINE NO. The default is DEFINE
                   YES.
       - Use TBSBPOOL, TBSBP8K, TBSBP16K, and TBSBP32K to name the
         default buffer pools for implicitly created 4-KB, 8-KB,
         16-KB, and 32-KB page size table spaces, respectively. In
         addition, use the existing TBSBPOOL parameter to specify
         the default buffer pool name for implicitly created
         databases without the BUFFERPOOL clause. When a table space
         is implicitly created, DB2 chooses the correct buffer pool
         according to the maximum record size of the table and the
         name specified by TBSBPOOL, TBSBP8K, TBSBP16K, or TBSBP32K.
    
    For a CREATE TABLE LIKE a range-partitioned table where the
    table space is not specified, a new table is created on a
    partition by growth table space with no partitioning key.
    
    As in the implicit PBG case, for the implicit PBR, if the
    containing table space is implicitly created, DB2 will create
    all system required objects for the user, such as enforcing
    primary key index, enforcing unique key index, ROWID index on
    which the column is defined as ROWID GENERATED BY DEFAULT, and
    LOB objects.
    

Problem conclusion

  • Users can now have partition by range table spaces implicitly
    created from a CREATE TABLE statement based on the number of
    parts specified on the create and if no table space name is
    specified.
    
    Additional Keywords:
    SQLCREATE
    SQLCODE20183
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK51752

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function

  • Submitted date

    2007-08-24

  • Closed date

    2008-03-17

  • Last modified date

    2008-05-02

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

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

    UK34665

Modules/Macros

  • DSNDXSB7 DSNXICTB DSNXISB7
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R910 PSY UK34665

       UP08/04/03 P F804

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 May 2008