Direct links to fixes
7.1.4.100-TIV-TSMSRV-AIX
7.1.4.100-TIV-TSMSRV-HP-UX
7.1.4.100-TIV-TSMSRV-Linuxppc64
7.1.4.100-TIV-TSMSRV-Linuxs390
7.1.4.100-TIV-TSMSRV-Linuxx86_64
7.1.4.100-TIV-TSMSRV-SolarisSPARC
7.1.4.100-TIV-TSMSRV-WIN
7.1.5.000-TIV-TSMSRV-AIX
7.1.5.000-TIV-TSMSRV-HP-UX
7.1.5.000-TIV-TSMSRV-Linuxppc64
7.1.5.000-TIV-TSMSRV-Linuxs390x
7.1.5.000-TIV-TSMSRV-Linuxx86_64
7.1.5.000-TIV-TSMSRV-SolarisSPARC
7.1.5.000-TIV-TSMSRV-WIN
IBM Spectrum Protect Server V7.1.4.X interim fix downloads
IBM Spectrum Protect Server V7.1 Fix Pack 5 (7.1.5.000) Downloads
APAR status
Closed as program error.
Error description
Fastback DR or restore from DR location using an IBM Spectrum Protect (formerly Tivoli Storage Manager) as the target location fails. The IBM Spectrum Protect Server is using a directory container pool to store the data. The following is seen in the DR hub log: I6.DR:AFS::TSM_ReadFile: Error on DSM_GetData 14: ANS1314E (RC14) File data currently unavailable on server I6.DR:AFS::TSM_File::Read: Failed TSM_ReadFile for file IBM Spectrum Protect activity log: ANR0542W Retrieve or restore failed for session 134576 for node <nodename> (WinNT) - storage media inaccessible. (SESSION: 134576) "Q CONTAINER" on the IBM SP server shows some containers unavailable. Tivoli Storage Manager Versions Affected: IBM Spectrum Protect server 7.1.3 and above, All Platforms Customer/L2 Diagnostics: IBM Spectrum Protect server SD trace indicates container is unavailable: Ýsdrtrv.c¨Ý2510¨ÝOpenContainer¨:Exit, rc 4808, cntrId 1397 Return code 4808 = GRC_CONTAINER_UNAVAILABLE The following may also be seen when the containers are being marked unavailable: ANR9999D_1624690145 SdAcquireRange(sdcntr.c:5896) Thread<4225767>: Invalid parameter(s): 18dfbd0e8 18dfbcf68 False. (SESSION: 388809) ANR9999D Thread<4225767> issued message 9999 from: (SESSION: 388809) ANR9999D Thread<4225767> 0x000000010001e30c StdPutText (SESSION: 388809) ANR9999D Thread<4225767> 0x000000010001ef40 OutDiagToCons (SESSION: 388809) ANR9999D Thread<4225767> 0x000000010000a2f4 outDiagfExt (SESSION: 388809) ANR9999D Thread<4225767> 0x00000001007677c8 SdAcquireRange (SESSION: 388809) ANR9999D Thread<4225767> 0x000000010094de1c SdWrite (SESSION: 388809) ANR9999D Thread<4225767> 0x0000000100938e14 SdWriteNonDedupData (SESSION: 388809) ANR9999D Thread<4225767> 0x000000010094b2c0 SdCQSinkThread (SESSION: 388809) ANR9999D Thread<4225767> 0x000000010000d5f4 StartThread 388809) ANR0204I The container state for /poolname/05/00000000000001.dcf is updated from AVAILABLE to UNAVAILABLE. (SESSION: 388809) ANR3660E An unexpected error occured while opening or writing to the container. Container /poolname/05/00000000000001.dcf in stgpool <stgpoolname> has been marked as UNAVAILABLE and should be audited to validate accessibility and content. (SESSION: 388809) ANR0530W Transaction failed for session 388809 for node <nodename> (WinNT) - internal server error detected. (SESSION: 388809) Initial Impact: High Additional Keywords: FSBK DR drhub upgrade 7.1.3
Local fix
Run "AUDIT CONTAINER" command on unavailable containers from administrative command line to mark containers as available again.
Problem summary
**************************************************************** * USERS AFFECTED: * * All Tivoli Storage Manager server users utilizing FastBack. * **************************************************************** * PROBLEM DESCRIPTION: * * See ERROR DESCRIPTION. * **************************************************************** * RECOMMENDATION: * * Apply fixing level when available. This problem is currently * * projected to be fixed in level 7.1.5. Note that this is * * subject to change at the discretion of IBM. * ****************************************************************
Problem conclusion
This problem was fixed. Affected platforms: AIX, Solaris, Linux, and Windows.
Temporary fix
Comments
APAR Information
APAR number
IT12320
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
71A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-11-17
Closed date
2015-12-14
Last modified date
2015-12-14
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
Document Information
Modified date:
28 August 2023