Direct links to fixes
6.3.6.000-TIV-TSMRPT-AGENT-Linux
6.3.6.000-TIV-TSMRPT-AGENT-AIX
6.3.6.000-TIV-TSMRPT-AIX
6.3.6.000-TIV-TSMRPT-AGENT-Windows
6.3.6.000-TIV-TSMRPT-Linuxx86
6.3.6.000-TIV-TSMRPT-Linuxx86_64
6.3.6.000-TIV-TSMRPT-WindowsI32
6.3.6.000-TIV-TSMRPT-WindowsX64
6.3.6.000-TIV-TSMAC-WindowsX64
6.3.6.000-TIV-TSMAC-WindowsI32
6.3.6.000-TIV-TSMAC-SolarisSPARC
6.3.6.000-TIV-TSMAC-Linuxx86
6.3.6.000-TIV-TSMAC-Linuxs390x
6.3.6.000-TIV-TSMAC-AIX
6.3.6.000-TIV-TSMALL-SolarisSPARC
6.3.6.000-TIV-TSMALL-WindowsX64
6.3.6.000-TIV-TSMSTA-WindowsI32
6.3.6.000-TIV-TSMALL-HP-UX
6.3.6.000-TIV-TSMALL-Linuxppc64
6.3.6.000-TIV-TSMALL-AIX
6.3.6.000-TIV-TSMALL-Linuxs390x
6.3.6.000-TIV-TSMALL-Linuxx86_64
7.1.3.000-TIV-TSMSRV-WIN
7.1.3.000-TIV-TSMSRV-SolarisSPARC
7.1.3.000-TIV-TSMSRV-Linuxx86_64
7.1.3.000-TIV-TSMSRV-Linuxs390x
7.1.3.000-TIV-TSMSRV-Linuxppc64
7.1.3.000-TIV-TSMSRV-HP-UX
7.1.3.000-TIV-TSMSRV-AIX
IBM Tivoli Storage Manager V6.3 Fix Pack 6 (6.3.6.000) Server Downloads
APAR status
Closed as program error.
Error description
Backups or server operations may fail indicating an internal Tivoli Storage Manager server error. This issue manifests typically when simultaneous write to multiple storage pools is allowed. The Tivoli Storage Manager client log may report similar messages to : ANS1301E (RC1) This operation cannot continue due to an error on the TSM server. See your TSM server administrator for assistance. While the server activity log may report: ANR9999D_2192502038 tmParticipate(tmtxn.c:640) Thread<61>: partId=0, defined=1; numParts=4, Max=13 (SESSION: 1524) ANR9999D Thread<61> issued message 9999 from: (SESSION: 1524) ANR9999D Thread<61> 000007FEF2FF5E45 OutDiagToCons()+155 (SESSION: 1524) ANR9999D Thread<61> 000007FEF2FEFD7C outDiagfExt()+10c (SESSION: 1524) ANR9999D Thread<61> 000007FEF2FAC6C6 tmParticipate()+1a6 (SESSION: 1524) ANR9999D Thread<61> 000007FEF2D12C70 DbiParticipate()+e0 (SESSION: 1524) ANR9999D Thread<61> 000007FEF2CFB057 tbOpenX()+107 (SESSION: 1524) ANR9999D Thread<61> 000007FEF2F8EFC5 InsertNewSegment()+265 (SESSION: 1524) ANR9999D Thread<61> 000007FEF2F870D7 AsApplySeg()+487 (SESSION: 1524) ANR9999D Thread<61> 000007FEF2F5AB83 SinkStore()+1183 (SESSION: 1524) ANR9999D Thread<61> 000007FEF2F58D2E SsSWThread()+21e (SESSION: 1524) ANR9999D Thread<61> 000007FEF26C72EC startThread()+13c (SESSION: 1524) ANR9999D Thread<61> 000007FEF8DF3FEF beginthreadex()+107 (SESSION: 1524) ANR9999D Thread<61> 000007FEF8DF4196 endthreadex()+192 (SESSION: 1524) ANR9999D Thread<61> 0000000076B559ED BaseThreadInitThunk()+d (SESSION: 1524) ANR9999D Thread<61> 0000000076D8C541 RtlUserThreadStart()+21 (SESSION: 1524) ANR9999D_4185701700 DbiParticipate(dbitxn.c:1530) Thread<61>: tmParticipate returned 9999. (SESSION: 1524) ANR9999D Thread<61> issued message 9999 from: (SESSION: 1524) ANR9999D Thread<61> 000007FEF2FF5E45 OutDiagToCons()+155 (SESSION: 1524) ANR9999D Thread<61> 000007FEF2FEFD7C outDiagfExt()+10c (SESSION: 1524) ANR9999D Thread<61> 000007FEF2D12C98 DbiParticipate()+108 (SESSION: 1524) ANR9999D Thread<61> 000007FEF2CFB057 tbOpenX()+107 (SESSION: 1524) ANR9999D Thread<61> 000007FEF2F8EFC5 InsertNewSegment()+265 (SESSION: 1524) ANR9999D Thread<61> 000007FEF2F870D7 AsApplySeg()+487 (SESSION: 1524) ANR9999D Thread<61> 000007FEF2F5AB83 SinkStore()+1183 (SESSION: 1524) ANR9999D Thread<61> 000007FEF2F58D2E SsSWThread()+21e (SESSION: 1524) ANR9999D Thread<61> 000007FEF26C72EC startThread()+13c (SESSION: 1524) ANR9999D Thread<61> 000007FEF8DF3FEF beginthreadex()+107 (SESSION: 1524) ANR9999D Thread<61> 000007FEF8DF4196 endthreadex()+192 (SESSION: 1524) ANR9999D Thread<61> 0000000076B559ED BaseThreadInitThunk()+d (SESSION: 1524) ANR9999D Thread<61> 0000000076D8C541 RtlUserThreadStart()+21 (SESSION: 1524) ANR9999D_0645605689 tbOpenX(tbtbl.c:5183) Thread<61>: Failure participating on transaction. (SESSION: 1524) ANR9999D Thread<61> issued message 9999 from: (SESSION: 1524) ANR9999D Thread<61> 000007FEF2FF5E45 OutDiagToCons()+155 (SESSION: 1524) ANR9999D Thread<61> 000007FEF2FEFD7C outDiagfExt()+10c (SESSION: 1524) ANR9999D Thread<61> 000007FEF2CFB07F tbOpenX()+12f (SESSION: 1524) ANR9999D Thread<61> 000007FEF2F8EFC5 InsertNewSegment()+265 (SESSION: 1524) ANR9999D Thread<61> 000007FEF2F870D7 AsApplySeg()+487 (SESSION: 1524) ANR9999D Thread<61> 000007FEF2F5AB83 SinkStore()+1183 (SESSION: 1524) ANR9999D Thread<61> 000007FEF2F58D2E SsSWThread()+21e (SESSION: 1524) ANR9999D Thread<61> 000007FEF26C72EC startThread()+13c (SESSION: 1524) ANR9999D Thread<61> 000007FEF8DF3FEF beginthreadex()+107 (SESSION: 1524) ANR9999D Thread<61> 000007FEF8DF4196 endthreadex()+192 (SESSION: 1524) ANR9999D Thread<61> 0000000076B559ED BaseThreadInitThunk()+d (SESSION: 1524) ANR9999D Thread<61> 0000000076D8C541 RtlUserThreadStart()+21 (SESSION: 1524) ANR0101E asalloc.c(10235): Error 9991 opening table "AS.Segments". (SESSION: 1524) Server trace BFTXN DFTXN AFTXN SSTRANS DSTXN ASTXN MMSTXN DBITXN TXN will show the timing window that caused the error: 14:58:00.479 [64][dbitxn.c][1707][AllocTxnDesc]: tid 0:2508165, allocated txn extension 0000000019A9F990 using connection 000000000D9C2080. 14:58:00.479 [64][tmtxn.c][608][tmParticipate]: Adding participant "DB" to transaction 0:2508165. 14:58:00.510 [63][dbitxn.c][1707][AllocTxnDesc]: tid 0:2508165, allocated txn extension 000000000443C510 using connection 000000000CDE35F0. 14:58:00.510 [63][tmtxn.c][608][tmParticipate]: Adding participant "DB" to transaction 0:2508165. 14:58:00.510 [63][output.c][7474][PutConsoleMsg]: ANR9999D_2192502038 tmParticipate(tmtxn.c:640) Thread<63>: partId=0, defined=1; numParts=4, Max=13~ This is a timing window issue. Thread 63 and thread 64 are trying to add a "DB" participant on the same transaction id 0:2508165 and since thread 64 completes first, thread 63 reports the error and transaction fails. Tivoli Storage Manager versions affected: 6.2, 6.3, 6.4, and 7.1, on all platforms. Initial Impact: Medium Additional Keywords: tsm simultaneous write COPYSTGPOOLS ANR0101E
Local fix
Disable simultaneous write to the copy stgpools: upd stg primary_pool_name COPYSTGpools="" AUTOCOPY=NONE And ensure that primary stgpools are regularily backed up to the copy stgpools: ba stg primary_pool_name copy_pool_name
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.6 and 7.1.3. 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
IT05449
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
71L
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-11-10
Closed date
2014-12-17
Last modified date
2015-02-05
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
[{"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":"7.1.3"}]
Document Information
Modified date:
24 September 2021