IBM Support

IC43796: TSM SERVER MANAGES LAST INACTIVE VERSION BY "RETEXTRA" AFTER DELETING ACTIVE VERSION WITH "DELETE VOLUME" OR "DELETE OBJECT"

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • TSM is incorrectly managing  the last inactive backup object
    using "retextra" value instead of "retonly" value of the
    management class's copygroup.
    .
    This matches the same symptoms reported in APAR IC41352 but is
    unrelated, and can occur when the Active version of a backup is
    deleted from TSM server with DELETE VOLUME or DELETE OBJECT
    commands.
    .
    TSM is not updating the field in Expiring.Objects table to track
    if an active copy of the file exists in TSM server storage for
    the
    last inactive copy when a deletion is done with above commands.
    This results in the last inactive copy being  managed by
    "retextra"
    parameter instead of  "retonly" parameter.
    .
    To diagnose this issue, identify inactive versions of files that
    are not expiring as expected and confirm the policy definitions
    being used to manage the object are not being honored.
    .
    If TSM is not honoring the "retonly" setting for last inactive
    backup version, perform following:
    .
    1) confirm that the inactive copy is the last version of the
    file
       by examining "show versions" output for the HL and LL
    qualifier
       (path and filename)
    .
    2) confirm that "expire inventory" is completing and attempting
    to
       process the file in question.  On TSM server enable IMEXP,
    IMDEL,
       IMFS traceclasses and capture trace covering expiration
    processing.
       Check the trace output based on the Object ID for the
    inactive
       version that is not expiring:
    .
    [imexp.c][3156]: Expiration examining the following entry:
      (11)(34)(1)(1)(1)(104/3/28 21:8)(0.8723048)
    [imexp.c][3353]: ProcessExp: Expiration Qualifies False for 0
    8723048
    .
    3) If the object does not qualify for expiration in the trace,
    map
       temprary SQL table to Expiring.Objects table and gather
    following
       select output:
    .
    create sqltable Expiring.Objects MyExp
    select c6,c7 from MyExp where c6=<object ID>
    drop sqltable MyExp
    .
    If the value of C7 is 1, TSM will manage the object as if an
    active
    version of the file exists, and manage it based on "retextra"
    value.
    .
    Affected Platforms: 5.1 and 5.2 TSM servers on all platforms
    Initial Impact: Medium
    Additional Keywords:
    Tivoli Storage Manager IMEX_HASACTIVE IC38105 nolimit
    

Local fix

  • If these objects should be expired but are being maintained
    due to a longer retextra than retonly value, use "delete object"
    command to manually delete the version that should have been
    removed during expiration processing.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM Tivoli Storage Manager      *
    *                 Server for any platform.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: See Error Description.                  *
    ****************************************************************
    * RECOMMENDATION: Apply fixing level when available.  This     *
    *                 problem is currently projected to be fixed   *
    *                 in levels 5.1.10, 5.2.4.2, 5.2.5, 5.3.0.1,   *
    *                 and 5.3.1.  Note that this is subject to     *
    *                 change at the discretion of IBM.             *
    ****************************************************************
    Inventory expiration is incorrectly using RETEXTRA to manage the
    last inactive version of an object.  This can only occur when
    the active version of the object is deleted, either using DELETE
    VOLUME or DELETE OBJECT, and the object is not backed up again,
    either because the object was deleted on the client system or
    because no more backups of the client object are attempted.  The
    last inactive version of an object should be managed with
    RETONLY.  If RETONLY is less than RETEXTRA, the result is that
    objects will not be expired when they should be.  If RETONLY
    is greater than RETEXTRA, the result is that objects are expired
    prematurely.
    

Problem conclusion

  • Users who may have deleted the active version of any object that
    is not subsequently backed up again should perform one of the
    following corrective actions after applying the fixing level:
    1.  Run AUDITDB INVENTORY FIX=YES.
    2.  Run the CLEANUP EXPTABLE utility.  This utility replaces the
        SHOW VERIFYEXPTABLE utility.  You may optionally specify
        BEGINNODEID=n and ENDNODEID=m parameters to limit the scope
        of the cleanup.  The CLEANUP EXPTABLE and SHOW
        VERIFYEXPTABLE utilities may only be used at the direction
        of IBM.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC43796

  • Reported component name

    TSM SERVER 510

  • Reported component ID

    5698ISMSV

  • Reported release

    52A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2004-12-06

  • Closed date

    2005-01-13

  • Last modified date

    2005-01-13

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

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

    PQ98755 PK00198

Modules/Macros

  • im imutil imaudit imexp admct admshow dsmameng
    

Fix information

Applicable component levels

  • R51A PSY

       UP

  • R51H PSY

       UP

  • R51L PSY

       UP

  • R51P PSY

       UP

  • R51S PSY

       UP

  • R51W PSY

       UP

  • R52A PSY

       UP

  • R52H PSY

       UP

  • R52L PSY

       UP

  • R52P PSY

       UP

  • R52S PSY

       UP

  • R52W PSY

       UP

  • R53A PSY

       UP

  • R53H PSY

       UP

  • R53L PSY

       UP

  • R53S PSY

       UP

  • R53W 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":"52A","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
13 January 2005