IBM Support

JR31186: DB2 CONTROL CENTER INCORRECTLY SHOWING AUTO-RESIZE AS NO FOR TABLESPACES WHICH ARE NOT LOCATED ON THE CO-ORDINATOR PARTITION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The DB2 Control Center GUI is showing Auto-Resize as NO for
    tablespaces which are not located on the co-ordinator partition.
    
    The behaviour can be reproduced using following steps:
    
    1. Create a partitioned database (e.g. 2 logical partitions)
    2. Create a partition group on partition 1 only
    
       CREATE DATABASE PARTITION GROUP my_group
        ON DBPARTITIONNUM (1)
    
    3. Create a tablespace within that partition group as follows:
    
       CREATE LARGE TABLESPACE my_tbs
        IN DATABASE PARTITION GROUP my_group
        PAGESIZE 4K
        MANAGED BY DATABASE
        USING (FILE '/dpf/contp1' 10 M) ON DBPARTITIONNUMS (1)
        EXTENTSIZE 32
        PREFETCHSIZE AUTOMATIC
        OVERHEAD 4.970000
        NO FILE SYSTEM CACHING
        TRANSFERRATE 2.130000
        DROPPED TABLE RECOVERY ON
        AUTORESIZE YES
        INCREASESIZE 10 M
        MAXSIZE NONE;
    
    If you go to the Control Center AUTO RESIZE is showing as NO.
    
    Currently function SYSPROC.SNAP_GET_TBSP( ' ', -1 ) is used to
    obtain this information. As of dbpartitionnum parameter being
    set to -1 it will only get the information from the current
    partition which is catalog partition 0 in the example above.
    
    This APAR addresses a change on how DB2 Control Center obtains
    the auto-resize information for tablespaces. It will be changed
    to use function SNAP_GET_TBSP_V91('', -2) instead. Specified
    dbpartitionnum paramater -2 will result in an aggregate of all
    active database partitions.
    
    This way DB2 Control Center will get tablespace auto-resize
    information from tablespaces which do not reside on the catalog
    partition without trying to receive data from not activated
    partitions.
    

Local fix

Problem summary

  • USERS AFFECTED: All running DPF database environments
    
    PROBLEM DESCRIPTION:
    The DB2 Control Center GUI is showing Auto-Resize as NO for
    tablespaces which are not located on the co-ordinator partition.
    
    PROBLEM SUMMARY:
    The DB2 Control Center GUI is showing Auto-Resize as NO for
    tablespaces which are not located on the co-ordinator partition.
    
    The behaviour can be reproduced using following steps:
    
    1. Create a partitioned database (e.g. 2 logical partitions)
    2. Create a partition group on partition 1 only
    
       CREATE DATABASE PARTITION GROUP my_group
        ON DBPARTITIONNUM (1)
    
    3. Create a tablespace within that partition group as follows:
    
       CREATE LARGE TABLESPACE my_tbs
        IN DATABASE PARTITION GROUP my_group
        PAGESIZE 4K
        MANAGED BY DATABASE
        USING (FILE '/dpf/contp1' 10 M) ON DBPARTITIONNUMS (1)
        EXTENTSIZE 32
        PREFETCHSIZE AUTOMATIC
        OVERHEAD 4.970000
        NO FILE SYSTEM CACHING
        TRANSFERRATE 2.130000
        DROPPED TABLE RECOVERY ON
        AUTORESIZE YES
        INCREASESIZE 10 M
        MAXSIZE NONE;
    
    If you go to the Control Center AUTO RESIZE is showing as NO.
    
    Currently function SYSPROC.SNAP_GET_TBSP( ' ', -1 ) is used to
    obtain this information. As of dbpartitionnum parameter being
    set to -1 it will only get the information from the current
    partition which is catalog partition 0 in the example above.
    
    This APAR addresses a change on how DB2 Control Center obtains
    the auto-resize information for tablespaces. It will be changed
    to use function SNAP_GET_TBSP_V91('', -2) instead. Specified
    dbpartitionnum paramater -2 will result in an aggregate of all
    active database partitions.
    
    This way DB2 Control Center will get tablespace auto-resize
    information from tablespaces which do not reside on the catalog
    partition without trying to receive data from not activated
    partitions.
    
    LOCAL FIX:
    none
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.1, FixPak 7 (s090308)
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR31186

  • Reported component name

    DB2 UDB ESE WIN

  • Reported component ID

    5765F4101

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-11-20

  • Closed date

    2009-04-07

  • Last modified date

    2009-04-07

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

    JR31185

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

Fix information

  • Fixed component name

    DB2 UDB ESE WIN

  • Fixed component ID

    5765F4101

Applicable component levels

  • R810 PSN

       UP

  • R820 PSN

       UP

  • R910 PSN

       UP

  • R950 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 October 2021