IC73005: TIVOLI STORAGE MANAGER SERVER CAN MISMANAGE NODE CLUSTER TRACKING RECORDS LEADING TO INVALID OCCUPANCY VALUES

APAR status

• Closed as program error.

Error description

• In Tivoli Storage Manager server version 6.x, the cluster
  records that are used to track occupancy values for a given
  node may become invalidated such that occupancy values being
  reported are inaccurate. One result of this problem could be
  seen in the Query OCCupancy command where the Physical and
  Logical Space Occupied values are incorrect. Also, the Query
  STGpool F=D could show an incorrect value for Duplicate Data
  Not Stored.
  
  Another result of this problem is that a select on the occupancy
  table can report back NULL values for node names and filespace
  names. The example below shows valid output for TESTNODE1 but
  the second entry is missing both the node name and the filespace
  name:
  
  tsm>select * from occupancy
  NODE_NAME        TYPE      FILESPACE_NAME         STGPOOL_NAME
  --------------   -----     ------------------     ------------
  TESTNODE1        Arch      /tmp                   FILEPOOL
                   Bkup                             FILEPOOL
  
  This condition might be encountered when a node or filespace is
  deleted and the cluster tracking record is orphaned in the
  database.
  
  Customer/L2 Diagnostics:
  The following selects can be run to determine if there are
  NULL values:
  
  select * from occupancy where node_name is NULL
  select * from occupancy where filespace_name is NULL
  
  Initial Impact: Low
  Tivoli Storage Manager Versions Affected: All 6.x Servers
  Additional Keywords: TSM zz61 zz62 QUERY OCC storage pool
  

Local fix

• Contact IBM Tivoli Storage Manager support for clean up steps.
  

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.1.5, 6.2.2.3 and 6.2.3.          *
  *                 Note that this is subject to change at the   *
  *                 discretion of IBM.                           *
  ****************************************************************
  *
  

Problem conclusion

• The described problem has been resolved.
  

Temporary fix

Comments

APAR Information

• 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

• R61A PSY

     UP

• R61H PSY

     UP

• R61L PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R62A PSY

     UP

• R62H PSY

     UP

• R62L PSY

     UP

• R62S PSY

     UP

• R62W PSY

     UP