IC81638: DELETE VOLUME COMMAND WITHOUT THE OPTION DISCARDDATA=YES MIGHT DELETE A VOLUME WHILE IT STILL CONTAINS DATA

IBM Tivoli Storage Manager (TSM) server V6.1.5.x interim fix downloads

APAR status

• Closed as program error.

Error description

• The Tivoli Storage Manager Server command DELETE VOLUME without
  the option DISCARDDATA=YES might delete a volume although it
  still contains data. This can only happen if the volume has
  invalid utilization information such that it is shown as
  0% utilized when there is still data on the volume.
  
  One cause is that the server not properly updating the volume
  status table row under certain / rare timing windows such that
  the utilization of the volume would be incorrect.
  This would result in various symptoms depending on what was
  being done with the volume. For instance, it could cause the
  "segment overwrite" message to occur since the volume
  utilization would be 0.0% but at least one segment would be on
  the volume. It could also cause the volume to show as
  0.0% utilized and empty even though some data still resided
  on the volume.
  
  Customer/L2 Diagnostics :
  Here is an actlog example of an error that will be seen from
  this issue, after the volume was deleted:
  
  ANR9999D_0798380752 AfGetBestVolumes(afcputil.c:2100)
  Thread<xxx>: Volume 12345 is not defined for pool 5.
  
  ANR9999D FetchVolAttr(asvolacq.c:XXXX)
  Thread<XXXXXX>: Attempt to overwrite segment
  on volume 12345 with maxOcc=0, nextSeq XXXX.
  
  Tivoli Storage Manager Versions Affected:
  Tivoli Storage Manager Server version
  5,4, 5,5, 6.1, 6.2 and 6.3 on all platforms
  
  Initial Impact:
  high
  
  Additional Keywords:
  zz61 zz62 zz63 TSM delete discard IC81406
  

Local fix

• Run QUERY CONTENT <volume name> before
  DELETE VOLUME  <volume name> to verify,
  if no data will be on the volume.
  
  A move data will not be possible once the volume is deleted
  because the volume will not exist.
  Do a move data against the volume with 0% utilization.
  The volume is completely fine and accessible until a
  delete volume is issued.
  

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

Problem conclusion

• This problem was fixed.
  Affected platforms:  AIX, HP-UX, Linux, Solaris, Windows.
  

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

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP