IBM Support

IC98023: SERVER CAN ABEND DURING CLIENT OPERATION WHEN OBJECT HAS NO DEACTIVE DATE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The server has the record of an inactive backup object but there
    is no deactived date for this object., When performing a client
    backup/restore/query backup, the server may crash.
    
    Customer/L2 Diagnostics (if applicable)
    Activity log may show ANR9999D with DATE002 issue.
         ANR9999D_1285327590  pkLogicAbort(pkthread.c:710)
    Thread<20494>:Run-time assertion failed:
         "date.mon >= 1 && date.mon <= 12", Thread 20494 (tid
    250e),File date.c, Line 703, reason: DATE002. (SESSION: 9627)
    
    Stack from core may look like the following:
    IOT/Abort trap in pthread_kill at 0x9000000007ceb50 ($t20494)
    0x9000000007ceb50 (pthread_kill+0xb0) e8410028          ld
    r2,0x28(r1)
    (dbx) where
    pthread_kill(??, ??) at 0x9000000007ceb50
    _p_raise(??) at 0x9000000007ce3c8
    raise.raise(??) at 0x90000000002bf2c
    abort() at 0x90000000007cdc4
    PsAbortServer(??) at 0x100026a20
    pkLogicAbort(??, ??, ??, ??) at 0x100020324
    IncrDate(??, ??, ??) at 0x10001a270             <---- abort with
    date
    SetBackupQueryResponse(??, ??, ??, ??) at 0x100924888
    imGetNextGroupMember(??) at 0x100928408
    DoBackQryGroups(??, ??, ??) at 0x10078a734
    SmNodeSession(??, ??) at 0x10077775c
    HandleNodeSession(??, ??, ??) at 0x1001aa118
    DoNodeGeneral(??, ??) at 0x1001a1a90
    smExecuteSession(??, ??, ??, ??, ??, ??, ??, ??) at 0x10019cacc
    psSessionThread(??) at 0x100059558
    StartThread(??) at 0x100020bdc
    (dbx)
    
    *NOTE*
    This APAR is only to address the abend/crash not the deactived
    correction.
    
    Platforms affected:
    5.5, All 6.x, Windows, Unix, Linux.
    
    Initial Impact: Medium
    
    Additional Keywords: crash core TSM ITSM ADSM
    

Local fix

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

    IC98023

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    63A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-11-29

  • Closed date

    2014-01-03

  • Last modified date

    2014-01-03

  • 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: 63A

Reference #: IC98023

Modified date: 03 January 2014