IBM Support

IC82886: EXCESSIVE DATABASE GROWTH EXPERIENCED WHEN DEDUPLICATION IS ENABLED UNDER CERTAIN WORKLOADS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customers running Server versions 6.x along with deduplication
    may observe unexplained database growth under certain workloads.
    
    This can be observed when there is very high rate of deletions
    and insertions into bf_aggregated_bitfiles in comparison with
    the total number of rows in that table.
    
    L2 diagnostic:
    If there is unexplainable database growth being seen, this
    particular issue  is suggested by inspecting the output of the
    command below over a certain period of time like a week:
      'db2pd -d tsmdb1 -tcbstats all -full'
    
    Seeing a very high rate of insertions and deletions from
    bf_aggregated_bitfiles suggests that this might be the issue.
    
    Reorganizing bf_aggregated_bitfiles, either the table or the
    indices, does not cause the growth to cease, nor does it make
    any any space available.  Because of the size of this table and
    the impact to the overall system when doing reorganization,
    attempting to reorganize it is not recommended as a diagnostic
    step.
    
    Versions Affected: Server 6.1, 6.2 and 6.3 using deduplication
    Initial Impact: medium
    Additional Keywords: tsm bf db dedup
    

Local fix

Problem summary

  • ***************************************************************
    * USERS AFFECTED: All Tivoli Storage Manager server users.    *
    ***************************************************************
    * PROBLEM DESCRIPTION: See error description                  *
    ***************************************************************
    * RECOMMENDATION: Apply fixing level when available. This     *
    * problem is currently projected to be fixed in levels        *
    * 6.2.5 and 6.3.3. Note that this is subject to change at the *
    * discression of IBM                                          *
    ***************************************************************
    

Problem conclusion

  • This problem was fixed.
    If there is a clustering index on the
    BF_AGGREGATED_BITFILES table, the following select will
    return CLUS for INDEXTYPE.
    
    db2 connect to tsmdb1
    
    db2 "select INDEXTYPE from sysibm.sysindexes
    where name='BFBF_NDX'"
    
    If CLUS is returned, follow the instructions in the Local
    Fix section of the APAR. If REG is returned, no further
    action is needed.
    
    See Technote 1592404 for Local Fix Information:
    http://www.ibm.com/support/docview.wss?uid=swg21592404
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC82886

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    62W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-04-25

  • Closed date

    2012-05-25

  • Last modified date

    2016-08-18

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

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

Fix information

  • Fixed component name

    TSM SERVER

  • Fixed component ID

    5698ISMSV

Applicable component levels

  • R62A PSY

       UP

  • R62H PSY

       UP

  • R62L PSY

       UP

  • R62S PSY

       UP

  • R62W PSY

       UP

  • R63A PSY

       UP

  • R63H PSY

       UP

  • R63L PSY

       UP

  • R63S PSY

       UP

  • R63W PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"62W","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
18 August 2016