IBM Support

IT17642: SLOW EXPIRATION AFTER UPGRADE TO 6.3.6.000 SERVER

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • After upgrading the server to 6.3.6.000 (or higher)  and
    7.1.3(or higher) expiration might "hang" on a node while
    expiring backup data only.   Expiration is not actually hung it
    is still processing but very slowly due to a non-optimized
    SQL/Select.   A change to this SQL/Select occurred between
    6.3.5.0 and 6.3.6.0.   This code change was implemented in
    servers 6.3.6.0+ and 7.1.3.0 to 7.1.7.   There have been no
    reported problems at 7.1.3 or above.
    
    Customer/L2 Diagnostics (if applicable)
    From the server activity log - review expiration entries.
    Expiration processes by node/filespace.  If it is seen that 1
    node does not complete expiration in a timely manner your server
    may be experiencing this issue.  By default Expiration restarts
    where it left off.  If it starts on the same node repeatedly
    this may also be another indicator you are hitting this issue.
    
    Servermon.pl output can be gathered for 1 hour and needs to
    collect the db2 information.   From the *db2.txt output search
    for the "ELAPSED_TIME_SEC" section. If you are experiencing this
    issue you will find the following select and a high Elapsed
    execution time - in this example 25310 seconds (which is a
    little over 7 hrs):
    
     ELAPSED_TIME_SEC STATE STMT_TEXT
     ---------------- -----
    ----------------------------------------------------------------
    -------------------------
    25310 EXEC  SELECT IMBK.OBJID, IMBK.BFSIZE, CASE WHEN
    IMBK.GROUPTYPE IS NOT NULL AND BITAND(IMBK.GROUPTYPE,458752)>0
    THEN 1 END AS ISIMGLLEAD, CASE WHEN IMBK.GROUPTYPE IS NOT NULL
    AND BITAND(IMBK.GROUPTYPE,7)>0 THEN 1 END AS ISIMGLMEMB FROM
    TSMDB1.BACKUP_OBJECTS IMBK WHERE IMBK.NODEID=? AND IMBK.FSID=?
    AND IMBK.OBJTYPE=? AND IMBK.STATE=2 AND IMBK.MCID=? AND (
    BITAND(IMBK.GROUPTYPE,CAST(? AS INT))=0 OR IMBK.GROUPTYPE=131072
    OR IMBK.GROUPTYPE IS NULL ) AND ( IMBK.DEACDATE<='1956-10-11
    00:00:00' OR ( IMBK.DEACDATE<=? AND
    
       1 record(s) selected.
    
    *NOTE*
    The ELAPSED_TIME_SEC select has been truncated in the DB2
    collection and this is how it will appear in the output.
    
    Platforms affected:
    Windows, Unix/Linux 6.3.6, 7.1.3 and higher
    
    Initial Impact: Medium
    
    Additional Keywords: IT07612
    
     |MDVREGR 6.3.6.0| |MDVREGR 7.1.3.0|
    

Local fix

  • 1) Contact Tivoli Storage Manager Support for a "Diagnostic"
    server (6.3.6.000 only)  which has been made available to
    correct this problem until the fix is available
    2) If you can not apply the DIAG server the work-around would be
    to run expiration:
         excluding the "slow" node(s) and  restarting expiration at
    the first node.   This can be done by adding the 2 following
    undocumented parameters to the Expire Inventory command:
        restart=no
        excludenodes=node1,node2,etc (where node1, node2 are the
    names of the slow nodes)
    

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.3.6.100, 7.1.7.100, 7.1.8  *
    * and 8.1.1. Note that this is subject to change at the        *
    * discretion of IBM.                                           *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT17642

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    63A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-24

  • Closed date

    2016-11-10

  • Last modified date

    2017-01-09

  • 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

  • R63A PSY

       UP

  • R63H PSY

       UP

  • R63L PSY

       UP

  • R63S PSY

       UP

  • R63W PSY

       UP

  • R71A PSY

       UP

  • R71H PSY

       UP

  • R71L PSY

       UP

  • R71S PSY

       UP

  • R71W PSY

       UP



Document information

More support for: Tivoli Storage Manager

Software version: 63A

Reference #: IT17642

Modified date: 09 January 2017