IBM Support

IC73165: SERVER ABEND WHEN SIMULTANEOUS WRITES PERFORMED TO ACTIVE DATA STORAGE POOL

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When performing simultaneous writes to an active data storage
    pool the TSM Server may abend and produce a core dump containing
    the following call stack:
    
       0x0000000100644e80 pkShowCallChain
       0x0000000100038654 pkAbort
       0x000000010003d4e4 TrapSyncError
       0x000000010003de5c pkReleaseMutexTracked
       0x00000001000c8498 tbOpenX
       0x000000010083904c InsertNewSegment
       0x0000000100839c1c AsApplySeg
       0x000000010085b570 DoApplySeg
       0x000000010085d46c SinkStore
       0x000000010085d94c SsSWThread
       0x000000010003d2c4 StartThread
    
    The problem occurs when one thread attempts to release a mutex
    that was created by another thread.  In some instances the TSM
    Server will not crash, but will produce mutex destruction errors
    similar to the following:
    
       ANR9999D_2637115035 pkDestroyMutex(pkmon.c:676) Thread<X>:
       Failed to destroy mutex 0xf73c580:txnP->mutex rc=16, held=0
       by dbitxn.c:1340 45611940 0.
       ANR9999D Thread<X> issued message 9999 from:
       ANR9999D Thread<X> 0x0000000000c46893 OutDiagToCons+0x0x143
       ANR9999D Thread<X> 0x0000000000c493e5 outDiagfExt+0x0x195
       ANR9999D Thread<X> 0x0000000000cba9dd pkDestroyMutex+0x0x10d
       ANR9999D Thread<X> 0x0000000000751c69 FreeTxnDesc+0x0x99
       ANR9999D Thread<X> 0x000000000075313f dbiEndTxn+0x0x3ff
       ANR9999D Thread<X> 0x0000000000c165c3 tmDiscardTxn+0x0x3d3
       ANR9999D Thread<X> 0x0000000000cb821a FinishThread+0x0x5a
       ANR9999D Thread<X> 0x000000374e20673d *UNKNOWN*
       ANR9999D Thread<X> 0x000000374d6d3d1d *UNKNOWN*
    
       ANR9999D_3218000281 pkDestroyMutex(pkmon.c:687) Thread<X>:
       Retries failed to destroy busy mutex 0xf73c580:txnP->mutex
       rc=16
       ANR9999D Thread<X> issued message 9999 from:
       ANR9999D Thread<X> 0x0000000000c46893 OutDiagToCons+0x0x143
       ANR9999D Thread<X> 0x0000000000c493e5 outDiagfExt+0x0x195
       ANR9999D Thread<X> 0x0000000000cbaa28 pkDestroyMutex+0x0x158
       ANR9999D Thread<X> 0x0000000000751c69 FreeTxnDesc+0x0x99
       ANR9999D Thread<X> 0x000000000075313f dbiEndTxn+0x0x3ff
       ANR9999D Thread<X> 0x0000000000c165c3 tmDiscardTxn+0x0x3d3
       ANR9999D Thread<X> 0x0000000000cb821a FinishThread+0x0x5a
       ANR9999D Thread<X> 0x000000374e20673d *UNKNOWN*
       ANR9999D Thread<X> 0x000000374d6d3d1d *UNKNOWN*
    
       ANR9999D_0261614031 FreeTxnDesc(dbitxn.c:1442) Thread<X>:
       Attempt to destroy busy mutex (nil) held by txn
       smnode.c:25049.
       ANR9999D Thread<X> issued message 9999 from:
       ANR9999D Thread<X> 0x0000000000c46893 OutDiagToCons+0x0x143
       ANR9999D Thread<X> 0x0000000000c493e5 outDiagfExt+0x0x195
       ANR9999D Thread<X> 0x0000000000751dfb FreeTxnDesc+0x0x22b
       ANR9999D Thread<X> 0x000000000075313f dbiEndTxn+0x0x3ff
       ANR9999D Thread<X> 0x0000000000c165c3 tmDiscardTxn+0x0x3d3
       ANR9999D Thread<X> 0x0000000000cb821a FinishThread+0x0x5a
       ANR9999D Thread<X> 0x000000374e20673d *UNKNOWN*
       ANR9999D Thread<X> 0x000000374d6d3d1d *UNKNOWN*
    
    Platforms affected:
    All TSM 6.1.x and 6.2.x Servers
    Additional Keywords:
    adp
    

Local fix

  • Disable simultaneous writes for active data storage pools
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Tivoli Storage Manager server users      *
    *                 performing simultaneous writes.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
    ****************************************************************
    * RECOMMENDATION: Apply fixing level when available. This      *
    *                 problem is currently projected to be fixed   *
    *                 in levels 6.1.4.4, 6.1.5, and 6.2.3.         *
    *                 Note that this is subject to change at the   *
    *                 discretion of IBM.                           *
    ****************************************************************
    See ERROR DESCRIPTION.
    Affected Platforms: AIX, HP-UX, Linux, Sun Solaris, and Windows.
    

Problem conclusion

  • The described problem has been resolved.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC73165

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    62L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-12-09

  • Closed date

    2010-12-16

  • Last modified date

    2010-12-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

  • 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

[{"Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"62L"}]

Document Information

Modified date:
17 September 2021