IC84550: RESTORE DB NOT VERIFYING DB INFO BEING RESTORED BEFORE STARTING

APAR status

• Closed as program error.

Error description

• At the startup of a RESTORE DB process it lacks a
  validation check of the DB candidate to be restored.
    Such items to be validated are the series numbers in the
    volume header of the image and the backup timestamp in
    the DB2 image. The reason for this is if we continue and
    let DB2 start the restore operation, DB2 can fail with SQL
    codes that are not meaningful.
  Tivoli Storage Manager Versions Affected:
    All versions on all platforms
  
  Customer/L2 Diagnostics (if applicable)
    Capturing a trace with following flags will show examples of
    the checks that can fail during a RESTORE DB:
      ICBACK ICREST ICVOLHST VERBDUMP
  
    [EvaluateRestoreStatus]:Restore database failed with sqlcode
                            -2532 sqlerrmc token is TSMDB1?
                            2012053106513 sqlerrml is 21.
    The sql2532 means the Tivoli Storage Manager is asking DB2 to
    restore a DB with an image that is not the same. The image is
    for DB backup at timestamp 2012053106513. However, the volhist
    file showed a completely different timestamp. In this
    particular case the volhist file needs to be modified to show
    the same timestamp.
    Another example from the same trace classes:
    [PutConsoleMsg]:ANR1363I Input volume CB0103L3 opened
                    (sequence number 1).~
    [icIsValidDBRestoreVol]:Exiting with rc 3319 and failingLine
                            1167.
    [SetupInputStream]:Volume header failed to validate with
                       rc=3319.
    This error indicates the Tivoli Storage Manager failed to
    compare the series number on the DB backup tape volume header
    with the series number found in the volhist.
  Initial Impact:
    Low
  Additional Keywords:
    RESTORE DB series
  

Local fix

• N/A
  

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 level 6.3.3. Note that this is            *
  *                 subject to change at the discretion of IBM.  *
  ****************************************************************
  *
  

Problem conclusion

• This problem was fixed.
  
  New server messages are created.
  
  ANR4604E Restore database volume header magic number
  <magicNumber> does not match the
  expected volume header magic number of <magicNumber>.  This
  volume cannot be used to restore the database.
  
  Explanation: Each volume contains a Tivoli Storage Manager
  volume header that begins with a header magic number.
  A bad magic number indicates that this volume is either
  corrupted or not suitable for restoring the database.
  
  System action: The server does not process the DSMSERV RESTORE
  DB command.
  
  User response: Check the volume history file to make sure that
  this volume is a valid database backup volume.
  If the volume is corrupted,  restore the database to a
  different time using a different set of backup volumes.
  
  
  ANR4605E Restore database volume header version number
  <versionNumber> does not match the
  expected volume version number of <versionNumber>. This volume
  cannot be used to restore the database.
  
  Explanation: Each database backup volume contains a Tivoli
  Storage Manager version number in the volume header.
   A mis-matched version number indicates that this volume is
  either corrupted or not suitable for restoring the database.
  This volume may be a pre Version 6.3.0 database backup volume.
   It cannot be used to restore a Tivoli Storage Manager V6.3
  database.
  
  System action: The server does not process the DSMSERV RESTORE
  DB command.
  
  User response: Check the volume history file to make sure that
  this volume is a valid database backup volume.
  If the volume is corrupted,  restore the database to a
  different time using a different set of backup volumes.
  
  
  ANR4606E Restore database volume header backup series number
  <seriesNumber> does not match
  the expected backup series number of <seriesNumber>.  This
  volume cannot be used to restore the database.
  
  Explanation:Each database backup volume contains a Tivoli
  Storage Manager backup series number in the volume header.
  A mis-matched backup series number indicates that this volume
  is either corrupted or not suitable for restoring the database.
  
  System action: The server does not process the DSMSERV RESTORE
  DB command.
  
  User response: Check the volume history file to make sure this
  volume is valid for a database backup operation.
  If the volume is valid, the volume history file can be
  modified to match this series number and you can reissue the
  DSMSERV RESTORE DB command.
  If the problem persists, this volume may be corrupted.
  Restore the database to a different time using a different set
  of backup volumes.
  
  
  ANR4607E Restore database volume header backup operation
  number <operationNumber> does not match
  the expected backup operation number of <operationNumber>.
  This volume cannot be used to restore the database.
  
  Explanation: Each database backup volume contains a Tivoli
  Storage Manager backup operation number
  in the volume header. A mis-matched backup operation number
  indicates that this volume is either corrupted
  or not suitable for restoring the database.
  
  System action: The server does not process the DSMSERV RESTORE
  DB command.
  
  User response: Check the volume history file to make sure this
  volume is valid for a database backup operation.
  If the volume is valid, the volume history file can be
  modified to match this operation number and you can
  reissue the DSMSERV RESTORE DB command.  If the problem
  persists, this volume may be corrupted.
  Restore the database to a different time using a different set
  of backup volumes.
  
  
  ANR4608E Restore database volume header backup type
  <backupType> is invalid.  This volume cannot be used to
  restore the database.
  
  Explanation: Each database backup volume contains a Tivoli
  Storage Manager backup operation number
  in the volume header. A mis-matched backup operation number
  indicates that this volume is either corrupted
  or not suitable for restoring the database.
  
  System action: The server does not process the DSMSERV RESTORE
  DB command.
  
  User response: Check the volume history file to make sure this
  volume is valid for a database backup operation.
  If the volume is valid, the volume history file can be
  modified to match this operation number and you can reissue
  the DSMSERV RESTORE DB command.  If the problem persists, this
  volume may be corrupted.
  Restore the database to a different time using a different set
  of backup volumes.
  
  
  ANR4609I Restore database process found FULL database backup
  timestamp
  <timestamp in YYYYMMDDHHMMSS> from database backup media.
  
  Explanation: This is the backup timestamp that is used for a
  database restore operation.
  
  System action:
  
  User response:
  
  
  ANR4613E Restore database volume <volumeName> meta data is not
  valid.  This volume cannot be used to restore the database.
  
  Explanation: Backup volumes contain Tivoli Storage Manager
  meta data.
  Invalid meta data indicates that this volume is either
  corrupted or not suitable for restoring the database.
  
  System action:  The server does not process the DSMSERV
  RESTORE DB command.
  
  User response:  Check the volume history file to make sure
  this volume is valid for a database backup operation.
  If this volume is corrupted, restore the database to a
  different time using a different set of backup volumes.
  
  
  ANR4614E The database backup timestamp of <timestamp in
  YYYYMMDDHHMMSS> on database backup media with backup type
  <backup type>
  does not match the backup timestamp <timestamp in
  YYYYMMDDHHMMSS> from the volume history file.
  This volume cannot be used to restore the database.
  
  Explanation:  Mis-matched timestamps indicates that this
  volume is either corrupted or not suitable for restoring the
  database.
  
  System action:  The server does not process the DSMSERV
  RESTORE DB command.
  
  User response:  Check the volume history file to make sure
  this volume is valid for a database backup operation.
  If this volume is corrupted, restore the database to a
  different time using a different set of backup volumes.
  

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

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP

• R63Z PSY

     UP