IC63860: UNABLE TO DELETE A BACKUPSET VOLUME FROM THE VOLUME HISTORY IF THE BACKUPSET WAS GENERATED WITH MULTIPLE NODE NAMES.

IBM Tivoli Storage Manager V6.1 Fix Pack 3 (6.1.3) Server Downloads

APAR status

• Closed as program error.

Error description

• A backupset volume may not be deleted from the volume history
  and therefore will not return to scratch. When a backupset
  volume is deleted from the volume history, the command may fail
  with following error:
  .
  Example:
  "ANR2143E GENERATE BACKUPSET: Invalid node name - NODE_A,
   NODE_B"
  .
  Example from actlog:
   .
  10/14/2009 15:31:13 ANR2017I Administrator ADMIN issued command:
     DELET VOLHISTORY type=backupset todate=today volume=VOLUME001
     force=yes  (SESSION: 1)
  10/14/2009 15:31:13 ANR2143E GENERATE BACKUPSET: Invalid node
   name NODE_A,NODE_B (SESSION: 1)
  10/14/2009 15:31:13 ANR9999D_2802072450 (icvolhst.c:3731)
     Thread<20>: unexpected rc=14 from admResolveObjectSet
     (SESSION: 1)
  10/14/2009 15:31:13 ANR9999D Thread<20> issued message 9999
     from: (SESSION: 1)
  10/14/2009 15:31:13 ANR2468E DELETE VOLHISTORY: An internal
     server error was encountered while deleting server sequential
     volume history information. (SESSION: 1)
  .
  Note: APAR IC60162 fixed the case if  the following error
  occurred:
  "ANR2143E GENERATE BACKUPSET: Invalid node name - *"
  .
  TSM Versions Affected:
  TSM 5.4, 5,5 and 6.1 on all platforms
  .
  Initial Impact:
  medium
  .
  Additional Keywords:
  IC60162 delete volhist  ANR2143E ANR9999D ANR2468E  rc 14
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users      *
  *                 issuing DELETE VOLHISTORY command against    *
  *                 orphan backupset volume.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in levels 5.4.6, 5.5.5 and 6.1.3. Note       *
  *                 that this is subject to change at the        *
  *                 discretion of IBM.                           *
  ****************************************************************
  *
  

Problem conclusion

• This problem was fixed.
  Affected platforms:  AIX, HP-UX, Sun Solaris, Linux, z/OS, and
  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:

  PM01702 PM01709

Fix information

• Fixed component name

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels

• R54A PSY

     UP

• R54H PSY

     UP

• R54L PSY

     UP

• R54S PSY

     UP

• R54W PSY

     UP

• R55A PSY

     UP

• R55H PSY

     UP

• R55L PSY

     UP

• R55S PSY

     UP

• R55W PSY

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61L PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP