IC63642: DRM PREPARE COMMAND FAILS AFTER A TIVOLI STORAGE MANAGER SERVER IS UPGRADED TO V6.1 WHEN RECOVERY MEDIA ASSOCIATION EXISTS.

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

APAR status

• Closed as program error.

Error description

• A DRM PREPARE command fails after a Tivoli Storage Manager
  server is upgraded to V6.1. The command fails if there is at
  least one recovery media association that was defined prior to
  the upgrade. The TSM server activity log will show :
  
  ANR2017I Administrator ADMIN issued command: PREPARE wait=yes
  ANR0984I Process NN for PREPARE started in the FOREGROUND at ...
  ANR9999D_4025923594 DrmGetAssociatedMachines(drmutil.c:1716)
   Thread<nnn>: Unable to get machine name for machineid X.
  ANR9999D Thread<nnn> issued message 9999 from:
  ANR9999D Thread<nnn> 0x0000000100012440 StdPutText
  ANR9999D Thread<nnn> 0x0000000100012cfc OutDiagToCons
  ANR9999D Thread<nnn> 0x000000010000e51c outDiagfExt
  ANR9999D Thread<nnn> 0x0000000100574f10 DrmGetAssociatedMachines
  ANR9999D Thread<nnn> 0x00000001008d41e8 drmGetOneRecMediaDef
  ANR9999D Thread<nnn> 0x0000000100afe4b0 DrmPrQRecMedia
  ANR9999D Thread<nnn> 0x0000000100af99a0 DrmPrCreateRecMediaList
  ANR9999D Thread<nnn> 0x0000000100ae9bf4 drmPrCreatePlanFile
  ANR9999D Thread<nnn> 0x00000001000094a4 StartThread
  ANR2032E PREPARE: Command failed - internal server error
   detected.
  
  The QUERY MACHINE F=D command will report the machine(s)
  defined in DRM and their recovery media. For example :
  
  ANS8000I Server command: 'q machine f=d'
  
            Machine Name: MACHINE_ABC
        Machine Priority: 1
                Building: BULDING_A
                   Floor:
                    Room:
                 Server?: Yes
             Description:
               Node Name:
     Recovery Media Name: VOLUME_123
        Characteristics?: Yes
  Recovery Instructions?: No
  
  The output shows that the MACHINE_ABC machine has a recovery
  media associated to it, VOLUME_123.
  
  The prepare command fails when it tries to process the recovery
  media. Other DRM commands fail with similar errors. For example:
  
  The "DELETE RECOVERYMEDIA VOLUME_123" command fails with the
  following errors :
  
  ANR2017I Administrator ADMIN issued command:
   DELETE RECOVERYMEDIA VOLUME_123
  ANR9999D_3721692130 drmDelRmMachAssocForRm(drmrmmaa.c:708)
    Thread<nnn>: Unable to get machine name for machine id  X.
  ANR9999D Thread<nnn> issued message 9999 from:
   ANR9999D Thread<nnn>  0x0000000100012440 StdPutText
   ANR9999D Thread<nnn>  0x0000000100012cfc OutDiagToCons
   ANR9999D Thread<nnn>  0x000000010000e51c outDiagfExt
   ANR9999D Thread<nnn>  0x00000001008d07fc drmDelRmMachAssocForRm
   ANR9999D Thread<nnn>  0x00000001008d2478 drmDeleteRecoveryMedia
   ANR9999D Thread<nnn>  0x0000000100ab9be0 AdmDeleteRecoveryMedia
   ANR9999D Thread<nnn>  0x000000010016e400 AdmCommandLocal
   ANR9999D Thread<nnn>  0x000000010016cbd8 admCommand
   ANR9999D Thread<nnn>  0x0000000100819934 SmAdminCommandThread
   ANR9999D Thread<nnn>  0x00000001000094a4 StartThread
  
  The "DELETE MACHINE MACHINE_ABC" command fails with the
  following errors:
  
  ANR2017I Administrator ADMIN issued command:
   DELETE MACHINE MACHINE_ABC
  ANR0104E drmmach.c(915): Error 2 deleting row from table
   "DRM.MachName.MachId".
  ANR2032E DELETE MACHINE: Command failed - internal server
   error detected.
  
  The "DEFINE MACHINE MACHINE_ABC" command fails with the
  following errors:
  
  ANR2017I Administrator ADMIN issued command:
   DEFINE MACHINE MACHINE_ABC
  ANR6607E DEFINE MACHINE: Machine MACHINE_ABC is already defined.
  
  The "DELETE RECMEDMACHASSOCIATION VOLUME_123 MACHINEA_ABC"
  command fails with the following errors :
  
  ANR2017I Administrator ADMIN issued command:
   DELETE RECMEDMACHASSOCIATION VOLUME_123 MACHINEA_ABC
  ANR6623W DELETE RECMEDMACHASSOCIATION: Machine MACHINE_ABC
   cannot be processed because it is not defined.
  ANR6624E DELETE RECMEDMACHASSOCIATION: No matching machine
   defined.
  
  Customer/L2 Diagnostics:
  The upgrade process does not correctly handle all of the machine
  definition information needed for DRM to operate correctly after
  the upgrade to 6.1. The following commands may be used from a
  shell or command prompt to verify that the required information
  is missing :
  
  db2 connect to tsmdb1
  db2 select "*" from TSMDB1.DRM_MACHNAME_MACHID
  
  The output from the select command should show an empty table.
  
  TSM Versions Affected:
  TSM 6.1 servers on all supported platforms that have recovery
  media associations defined prior to upgrade. It does not affect
  media associations defined after the upgrade.
  
  Additional Keywords:
  disaster recovery manager zz61
  

Local fix

• A) take a full back up of the server's database
  B) halt the server
  C) login as the TSM instance's userid (e.g., TSMINST1)
  D) issue the following commands from a unix shell or windows
     command prompt :
  ---------
  1) db2start
  2) db2 connect to tsmdb1
  3) db2 "select * from tsmdb1.drm_machname_machid"
  4) db2 "insert into tsmdb1.DRM_MACHNAME_MACHID(machname, machid)
      select machname, machid from tsmdb1.DRM_MACHINE_DEFINITION"
  5) db2 "select * from tsmdb1.drm_machname_machid"
  6) db2 disconnect current
  ---------
  Restart the TSM server
  NOTE : Command in step 4 should be entered on 1 line.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users of   *
  *                 Disaster Recovery Manager who upgrade from   *
  *                 version 5 to version 6.                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Internal information related to DRM     *
  *                      machine definitions is not transferred  *
  *                      to the version 6 database, resulting in *
  *                                                              *
  *                      errors in the                           *
  *                      DRM PREPARE,                            *
  *                      DELETE RECOVERYMEDIA,                   *
  *                      DELETE RECMEDMACHASSOCIATION,           *
  *                      DELETE MACHINE, and                     *
  *                      DEFINE MACHINE commands.  In addition,  *
  *                      DRM machine-node associations are not   *
  *                      transferred during the upgrade process. *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in levels 5.5.4 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, and
  Windows.
  
  Both the version 6 server and the version 5 upgrade utilities
  must be updated for this change to resolve the reported problem.
  

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

• 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