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
IBM Tivoli Storage Manager (TSM) server V7.1.1.x interim fix downloads
IBM Tivoli Storage Manager V6.3 Fix Pack 6 (6.3.6.000) Server Downloads
APAR status
Closed as program error.
Error description
Migration fails with the following error: ANR9999D_2629611565 SelectCluster(dfmigr.c:2827) Thread<53>: Process 1 detected a discrepancy in the database for cluster srvId=0, ck1=1457 while migrating from pool DISK(16). (PROCESS: 8) This problem occurs due to a serialization issue with the migration code. The behavior can be mitigated by: 1) Restricting concurrent migration processes for a storage pool to 1. 2) Avoid backing up to a disk pool while simultaneously migrating from it. The HIGHMIG threshold should be set to 100 to prevent migration when backups are utilizing the disk pool. Customer/L2 Diagnostics: A server trace with traceflags DFMOVE DFTXN DFLOCK ADDMSG can be collected and reviewed for the following: 15:13:33.203 [66][dfmigr.c][3170][MigrateCluster]:Process 1 migrating cluster srvId=0, ck1=1537 ck2=9for pool DISK(16). 15:13:33.204 [66][dfmigr.c][3275][MigrateCluster]:Empty cluster detected 15:13:33.204 [66][dfmigr.c][6167][ReleaseCluster]:Process 1 releasing cluster srvId=0, ck1=1537 for migration from pool DISK(16). 15:13:33.205 [66][output.c][7407][PutConsoleMsg]:ANR9999D_0320705208 SelectCluster(dfmigr.c:3073) Thread<66>: Process 1 detected a discrepancy in the database for cluster srvId=0, ck1=1537 ck2=9 while migrating from pool DISK(16).~ 15:13:33.212 [66][output.c][7407][PutConsoleMsg]:ANR9999D Thread<66> issued message 9999 from:~ 15:13:33.212 [66][output.c][7407][PutConsoleMsg]:ANR9999D Thread<66> 00007FFAF3050825 OutDiagToCons()+155~ 15:13:33.213 [66][output.c][7407][PutConsoleMsg]:ANR9999D Thread<66> 00007FFAF304A75C outDiagfExt()+10c~ 15:13:33.213 [66][output.c][7407][PutConsoleMsg]:ANR9999D Thread<66> 00007FFAF2A18BD3 SelectCluster()+503~ 15:13:33.213 [66][output.c][7407][PutConsoleMsg]:ANR9999D Thread<66> 00007FFAF2A180FB DfMigrationThread()+6ab~ 15:13:33.213 [66][output.c][7407][PutConsoleMsg]:ANR9999D Thread<66> 00007FFAF277707C startThread()+13c~ 15:13:33.213 [66][output.c][7407][PutConsoleMsg]:ANR9999D Thread<66> 00007FFAFF823FEF beginthreadex()+107~ 15:13:33.213 [66][output.c][7407][PutConsoleMsg]:ANR9999D Thread<66> 00007FFAFF824196 endthreadex()+192~ 15:13:33.214 [66][output.c][7407][PutConsoleMsg]:ANR9999D Thread<66> 00007FFB072416AD BaseThreadInitThunk()+d~ 15:13:33.214 [66][output.c][7407][PutConsoleMsg]:ANR9999D Thread<66> 00007FFB098F4629 RtlUserThreadStart()+1d~ 15:13:33.214 [66][dfmigr.c][3080][SelectCluster]:Process 1 detected a discrepancy in the database for cluster srvId=0, ck1=1537 ck2=9 while migrating from pool DISK(16). 15:13:33.214 [66][dfmigr.c][5657][EndMigration]:ctlP=000000621653EFF0. cpyCtlP=0000006231BDFF50. stallRc=9979 15:13:33.215 [66][output.c][7407][PutConsoleMsg]:ANR1032W Migration Process 1 terminated for storage pool DISK - internal server error detected.~ Initial Impact: High Tivoli Storage Manager Versions Affected: 6.2, 6.3, 6.4, 7.1
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.6, 7.1.1.200, and 7.1.3. * * Note that this is subject to change at the discretion of * * IBM. * ****************************************************************
Problem conclusion
The problem was fixed. Affected Platforms: AIX, HP-UX, Solaris, Linux, and Windows.
Temporary fix
Comments
APAR Information
APAR number
IT04316
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
63W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-09-10
Closed date
2014-11-11
Last modified date
2015-01-26
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
Modified date:
26 January 2015