IBM Support

IT01030: SERVER ABEND DURING DATABASE RESTORE OPERATION

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The Tivoli Storage Manager server may abend during a database
    restore operation if the dsmserv.opt file contains an invalid
    reference to a volume history file that does not exist.  If the
    dsmserv.opt file contains both a valid and invalid volume
    history reference, the database restore operation may
    successfully read data from the valid volume history file,
    however, the database restore operation will still fail after
    validating the database backup volume, as seen below:
    
       ANR0152I Database manager successfully started.
       ANR4636I Starting roll-forward database restore.
       ANR4591I Selected backup series 5 from 04/04/2014 and
       02:02:39 PM as best candidate available for restore database
       processing.
       ANR4592I Restore database backup series 5 includes eligible
       operation 0 with volume /dbbackups/99999999.DBV having
       sequence 10001 and using device class DBBACKUP.
       ANR4598I Validating database backup information for selected
       backup series 5 and operation 0 using volume
       /dbbackups/99999999.DBV.
       ANR8340I FILE volume /dbbackups/99999999.DBV mounted.
       ANR1363I Input volume /dbbackups/99999999.DBV opened
       (sequence number 1).
       ANR4609I Restore database process found FULL database backup
       timestamp 20140404140239 from database backup media.
       ANR1364I Input volume /dbbackups/99999999.DBV closed.
       ANR3008I Database backup was written using client API:
       6.3.0.0.
       Memory fault(coredump)
    
    The call stack from the core dump will resemble the following:
    
       Core was generated by `/opt/tivoli/tsm/server/bin/dsmserv
       RESTORE DB'.
       Program terminated with signal 11, Segmentation fault.
       #0  0x00007ffff49a6ea7 in fclose () from /lib64/libc.so.6
       #1  0x0000000000aa0c7c in AssignRestoreStanzaFromVolHist
           (isPIT=False, isSnapshot=False, searchDate=...,
           restStanzaPP=0x7fffffffabc8, fullClassName=0x7fffffffb7e0
           "DBBACKUP", incrClassName=0x7fffffffb7c0 "") at
           icvolhst.c:8957
       #2  0x0000000000aa389d in icGetRestoreList (inDate=...,
           opType=<value optimized out>,
           restStanzaPP=0x7fffffffabc8, fullClassName=0x7fffffffb7e0
           "DBBACKUP", incrClassName=0x7fffffffb7c0 "") at
           icvolhst.c:1040
       #3  0x0000000000b456cd in RdbAdmRestoreDB (toDateFound=False,
           isSourceDBSnapshot=False, isPreview=True, toDate=...,
           inCmdP=<value optimized out>,
           overflowLogDir=0x7fffffffb6f0 "",
           activeLogDir=0x7fffffffb640 "", targetDirList=0x0,
           fullClassName=0x7fffffffabc8 "??\v??\177",
           incrClassName=0x7fffffffb7c0 "") at rdbicrst.c:690
       #4  0x00000000004fbfab in AdmRestoreDb (cmdP=0x174e488,
           inIsPreview=0x7fffffffb89c,
           dbJustRestoredPit=0x7fffffffb898) at admdbbk.c:2121
       #5  0x0000000000495136 in admRestoreDatabase
           (commandString=<value optimized out>) at admstart.c:3816
       #6  0x0000000000483779 in main (argCount=3, argVector=0x3)
           at dsmserv.c:1530
    
    Tivoli Storage Manager Versions Affected:
    Server versions 6.2.5, 6.3.3 and 7.1.0 or higher on all
    platforms
    
    Initial Impact:
    Medium
    
    Additional Keywords:
    IC90897 IC78481 restore crash core volhist volumehistory
    | MDVPARTL 6.2.5.0-TIV_5698MSV | IC78481
    | MDVPARTL 6.3.3.0-TIV_5698MSV | IC78481
    | MDVPARTL 7.1.0.0-TIV_5698MSV | IC78481
    

Local fix

  • Remove or correct any invalid volume history entries in the
    dsmserv.opt file
    

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

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IT01030

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    63L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-04-14

  • Closed date

    2014-07-16

  • Last modified date

    2014-07-16

  • 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

  • R71A PSY

       UP

  • R71H PSY

       UP

  • R71L PSY

       UP

  • R71S PSY

       UP

  • R71W PSY

       UP



Document information

More support for: Tivoli Storage Manager

Software version: 63L

Reference #: IT01030

Modified date: 16 July 2014