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
Tivoli Storage Manager client restore/retrieve commands might fail for dedup objects that have copies in multiple storage pools. A server trace with traceflags BF AF SS SESSION will show the following: 09:56:43.579 [61][bfrtrv.c][4115][RtrvOne]:Retrieving bitfile 2820756247, offset 15201197, length 5302733, useRtrvInfo: True, sessP->lastRtrvInfo: True 09:56:43.580 [61][bfrtrv.c][4142][RtrvOne]:Attempting to retrieve bitfile 2820756247 using lastRtrvInfo and best index of 0 . Note how bitfile 2820756247 changes to 4695555685 when moving from RtrvOne to ssRtrv . 09:56:43.580 [61][sstrans.c][2339][ssRtrv]:Retrieving bitfile 4695555685, offset=15201197, length=5302733, poolId=8, numSegs=1, format=22, mountWaitMode=0, estSize=12829283. 09:56:43.580 [61][sstrans.c][2499][ssRtrv]:Partial object retrieve values are: framesize=262096, userBytesPerFrame=262064, framesToSkip=58. 09:56:43.580 [61][sstrans.c][2504][ssRtrv]:Setting up for partial object retrieve: bytesToSkip=15201568, bytesToSkipInFirstFrame=1485, startingFrame=59. 09:56:43.580 [61][bfrtrv.c][4157][RtrvOne]:rc 3022 from lastRtrvInfo attempt 09:56:43.580 [61][bfrtrv.c][4181][RtrvOne]:rc 3022 from rtrv. 09:56:43.580 [61][bfrtrv.c][2445][RtrvFragment]:rc 3022 (sinkRc 0) from RtrvOne retrieving bitfile 2820756247, offset 15201197, length 5302733. 09:56:43.581 [61][bfrtrv.c][2972][RtrvFragment]:Skipping end-to-end digest check for bitfile 2250311450 09:56:43.581 [61][bfrtrv.c][3026][RtrvFragment]:Exiting, bitfile 2250311450, rc=3022. 09:56:43.584 [61][smnqr.c][2192][SmRetrieveBitfile]:rc 3022 from bfRtrv 09:56:43.584 [61][smnqr.c][2335][SmRetrieveBitfile]:Partial retrieval (offset 0, length 0) failed (3022) for bitfile 2250311450. 09:56:43.584 [61][output.c][7474][PutConsoleMsg]:ANR0546W Retrieve or restore failed for session 23211 for node EGVBRVFS1V3 (WinNT) - internal server error detected.~ The rc 3022 from bfRtrv translates to GRC_INVALID_OFFSET, it would also be possible to see rc 2516, GRC_INVALID_LENGTH. Both of these could happen if the bitfile processed in ssRtrv does not have data at the specified offset and/or length. If the bitfile processed in ssRtrv does have data at the specified offset and length, you would potentially see: ANR9999D_2644193874 BfCheckEndToEnd(bfdedup.c:6416) Thread<32>: Data integrity error detected for deduplicated object <OBJECTID> (SESSION: <SESSID>). When doing NQR restore, you might also see: ANR0836W No query restore processing session <SESSID> for node <NODEID> and <FILESPACE> failed to retrieve file <HL\LL> - file being skipped. (SESSION: <SESSID>). Tivoli Storage Manager Versions Affected: all supported Initial Impact: Medium Additional Keywords: TSM DEDUP
Local fix
Update the copy storage pools to ACCESS=UNAVAILABLE and resubmit the restore/retrieve command.
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
The problem was fixed. Affected Platforms: AIX, HP-UX, Solaris, Linux, and Windows.
Temporary fix
Comments
APAR Information
APAR number
IT05720
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
71W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-11-21
Closed date
2015-01-19
Last modified date
2015-01-19
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:
24 September 2021