IC67884: SERVER CRASH IN RESOLVEVOLNAME DURING DELETE VOLHISTORY COMMAND.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The Tivoli Storage Manager server may crash when attempting
    to handle an error during delete volhist.
    
    The call stack may resemble this:
    #0  0x000000000093bfd6 in ResolveVolName (dcP=0x7f407c454e08,
        volNameP=0x7f4082b38ae0 "GFC8.20081105.083845",
    bufP=0x7f4082b37a80
    "",
        bufSize=4097) at pvrmp.c:8066
     in pvrmp.c
    ==========================================
    
    #0  0x000000000093bfd6 in ResolveVolName (dcP=0x7f407c454e08,
        volNameP=0x7f4082b38ae0 "GFC8.20081105.083845",
    bufP=0x7f4082b37a80
    "",
        bufSize=4097) at pvrmp.c:8066
    #1  0x000000000093fde4 in PvrDismountVolume (
        volNameP=0x7f4082b38ae0 "GFC8.20081105.083845",
    resolvedBufP=0x0)
        at pvrmp.c:5438
    #2  0x0000000000921d29 in pvrDelete (devClass=5,
        volNameP=0x7f4082b39b90 "GFC8.20081105.083845",
    volNameLen=20,
        usageFlag=<value optimized out>, volAttrP=<value optimized
    out>,
        volAttrLen=<value optimized out>, stgPoolNameP=0x0,
    poolId=0,
    volId=0,
        serverId=0, returnScratch=True) at pvr.c:3971
    #3  0x000000000070f3e3 in DeleteFromPvr
    (volNameListP=0x7f407403ef48,
        classNameListP=0x7f407403ecf8) at icvolhst.c:6900
    #4  0x0000000000710ec6 in icDeleteVolumeHistory (maxDate=
          {year = 110 'n', mon = 3 '\003', day = 5 '\005', hour = 14
    '\016',
    min = 40 '(', sec = 8 '\b'}, volumeType=icvhRPFS,
    delLatestVer=True,
        delLatestSeries=False, devClass=0x7f4082b3bc00 "",
    deleted=0x7f4082b3abec)
        at icvolhst.c:2104
    #5  0x00000000004bb8fa in AdmDeleteVolumeHistory
    (cmdP=0x14a68e8)
        at admic.c:905
    #6  0x00000000004824a1 in AdmCommandLocal (cmdP=0x14a68e8,
    cmdMode=admAnyCmd,
        impliedCommit=True, confirmReq=<value optimized out>,
    validateOnly=False)
        at admcmd.c:2163
    #7  0x0000000000483308 in admCommand (cmdP=0x14a68e8,
    cmdMode=admAnyCmd,
        impliedCommit=True, confirmReq=False, validateOnly=False) at
    admcmd.c:1904
    #8  0x00000000009f18eb in SmExecuteCommand (blockP=0x14a54e8) at
    smlcons.c:644
    #9  0x00000000009f1dbc in SmLocalConsoleSession (nullPtr=<value
    optimized out>)
        at smlcons.c:531
    #10 0x0000000000c7ba2b in StartThread
    (startInfoP=0x7f4074c5e778)
        at pkthread.c:3323
    #11 0x00007f408b5d4070 in start_thread () from
    /lib64/libpthread.so.0
    #12 0x00007f4089a1610d in clone () from /lib64/libc.so.6
    #13 0x0000000000000000 in ?? ()
    
    
    ===================================================
    
    L2 Diagnostics:
    The crash is caused by the device class in question having it's
    devtype blank.
    
    ie show devclass:
    Device Class DEVCLASS_NAME (5) at CC425648:
      next=CC41CF38, prev=00000000, isLatched False
      mpAlloc=0, mpTableSize=8, mpTable=CC3E6028,
      mpReserved=0, mpOpen=0, mpOpening=0,
      mpIdle=0, mpDismounting=0, mpDismounted=0,
      mpDismountFailures=0, mpWaitingOtherMp=0, Sync Dismount=0,
      estCapacity=0, maxCapacity=8589934592,
      mountRet=60, mountLimit=20, mountWait=60,
      hla=,
      devType=, format=DRIVE, library=<>,
      dir=</tsm/tsminst1>, worm=0, scaledCapacity=0
    
    
    
    Tivoli Storage Manager Versions Affected:
    6.1 and 6.2 on all platforms
    
    Initial Impact:
    Medium
    
    Additional Keywords:
    TSM delete volhist devclass zz61
    

Local fix

  • If you have the issue with devclass devtype being blank, then
    you can delete the device class and associated volumes in
    volhistory.
    .
    1.  Query the device classes
    .
    db2 => SELECT classname,classid FROM DB6131.SS_CLASSES
    .
    CLASSNAME                       CLASSID
    ------------------------------- -----------
    DISK                                      0
    FILECLASS                                 1
    FILECLASS1                                4
    .
      3 record(s) selected.
    2.  Find the classid associated with the device class to be
    deleted
    from the
    .
    3.  Delete the row
    .
    db2 => delete from db6131.ss_classes where classid=4
    DB20000I  The SQL command completed successfully.
    .
    4.  Confirm the deletion
    db2 => SELECT classname,classid FROM DB6131.SS_CLASSES
    .
    CLASSNAME                       CLASSID
    ------------------------------- -----------
    DISK                                      0
    FILECLASS                                 1
    .
      2 record(s) selected.
    .
    Delete the volume history related to the deleted device class:
    .
    1.  See what we have in the volume history:
    .
    db2 => SELECT devclass   FROM DB6131.seq_volume_history
    .
    DEVCLASS
    ----------------------------------------------------------------
    FILECLASS
    FILECLASS
    FILECLASS
    FILECLASS
    FILECLASS1
    FILECLASS1
    .
      6 record(s) selected.
    .
    2.  Delete all volume history related to FILECLASS1
    db2 => delete  FROM DB6131.seq_volume_history where
    devclass='FILECLASS1'
    DB20000I  The SQL command completed successfully.
    .
    3. Confirm the results
    db2 => SELECT devclass   FROM DB6131.seq_volume_history
    .
    DEVCLASS
    ----------------------------------------------------------------
    FILECLASS
    FILECLASS
    FILECLASS
    FILECLASS
    .
      4 record(s) selected.
    .
    Verify in TSM server to make sure they are deleted:
    .
    TSM:SERVER1>
    q devc
    ANR2017I Administrator SERVER_CONSOLE issued command: QUERY
    DEVCLASS
    .
    Device        Device         Storage     Device        Format
    Est/Max      M
    Class         Access            Pool     Type
    Capacity      L
    Name          Strategy         Count
    (MB)
    ---------     ----------     -------     ---------     ------
    --------     --
    DISK          Random               2
    FILECLASS     Sequential           1     FILE          DRIVE
    200.0
    
    The entries will be deleted in TSM database, as can be checked
    with q volhist.
    But, this will not update the volhistory file saved on disk. The
    file will need to be manually edited
    to delete the entries that were deleted in the database.
    Then the device class can be recreated and used again for new
    volumes.
    

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

Problem conclusion

  • This problem was fixed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC67884

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    61L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-14

  • Closed date

    2010-04-29

  • Last modified date

    2010-04-29

  • 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



Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Storage Manager

Software version:

61L

Reference #:

IC67884

Modified date:

2010-04-29

Translate my page

Machine Translation

Content navigation