IBM Support

IT28615: DB2PD -TABLESPACE DOES NOT INDICATE LOCAL OFFLINE STATE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • If a Connection is interrupted, while implicitly activating the
    Database in a Purescale environment, a table space can be marked
    as Locally Offline in SD mode. (This isn't true for the system
    catalog table space.)
    
    Startup does not fail altogether and continues to start other
    table spaces that this member is able to access.
    
    The administrator will need to use the ALTER TABLESPACE SWITCH
    ONLINE command to bring the table space back online.
    
    The following messages can be seen in the db2diag.log :
    
    FUNCTION: DB2 UDB, buffer pool services, sqlbStartPools,
    probe:2542
    MESSAGE : ADM6023I The table space "USERSPACE1" (ID "2") is in
    state "0x00000000".
     The table space cannot be accessed. Refer to the documentation
    for
     SQLCODE -290.
    
    
    FUNCTION: DB2 UDB, buffer pool services,
    sqlbStartPoolsErrorHandling, probe:4151
    MESSAGE : ADM6081W The table space "USERSPACE1" (ID "2") is in
    the OFFLINE state
     and is not accessible. The table space state is "0x00004000".
    Refer
     to the documentation for SQLCODE -293.
    
    However db2pd -tablespaces shows that the table space in
    question is in normal state (0x00000000) which can be confusing.
    This is because db2pd -tablespaces only shows the Global table
    space State not the Local State.
    
    MON_GET_TABLESPACE will report the Local State of the Table
    space but the output does not make it clear whether it is
    reporting Global or Local table space States.
    
    db2pd and MON_GET_TABLESPACE need to be more clear about
    local/global tablespace states.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL DB2 Purescale Users                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 for LUW 11.1 Mod 4 Fix Pack 5 or later        *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 for LUW 11.1 Mod 4 Fix Pack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT28615

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-03-29

  • Closed date

    2019-10-31

  • Last modified date

    2019-10-31

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

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

    IT28665 IT30811

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSN

       UP

  • RB10 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
31 October 2019