Direct links to fixes
8.1.6.000-IBM-SPSRV-AIX
8.1.6.000-IBM-SPSRV-Linuxppc64le
8.1.6.000-IBM-SPSRV-Linuxs390x
8.1.6.000-IBM-SPSRV-Linuxx86_64
8.1.6.000-IBM-SPSRV-WindowsX64
8.1.6.000-IBM-SPOC-AIX
8.1.6.000-IBM-SPOC-LinuxPPC64le
8.1.6.000-IBM-SPOC-Linuxs390x
8.1.6.000-IBM-SPOC-Linuxx86_64
8.1.6.000-IBM-SPOC-WindowsX64
8.1.6.000-IBM-SPCMS-Linuxx86_64
8.1.6.000-IBM-SPCMS-WindowsI32
8.1.6.000-IBM-SPCMS-WindowsX64
7.1.9.100-TIV-TSMSRV-AIX
7.1.9.100-TIV-TSMSRV-HP-UX
7.1.9.100-TIV-TSMSRV-Linuxppc64
7.1.9.100-TIV-TSMSRV-Linuxs390x
7.1.9.100-TIV-TSMSRV-Linuxx86_64
7.1.9.100-TIV-TSMSRV-SolarisSPARC
7.1.9.100-TIV-TSMSRV-WIN
8.1.1.400-IBM-SPSRV-AIX
8.1.1.400-IBM-SPSRV-Linuxppc64le
8.1.1.400-IBM-SPSRV-Linuxs390x
8.1.1.400-IBM-SPSRV-Linuxx86_64
8.1.1.400-IBM-SPSRV-WindowsX64
7.1.7.500-TIV-TSMSRV-AIX
7.1.7.500-TIV-TSMSRV-HP-UX
7.1.7.500-TIV-TSMSRV-Linuxppc64
7.1.7.500-TIV-TSMSRV-Linuxs390x
7.1.7.500-TIV-TSMSRV-Linuxx86_64
7.1.7.500-TIV-TSMSRV-SolarisSPARC
7.1.7.500-TIV-TSMSRV-WIN
7.1.10.000-TIV-TSMSRV-AIX
7.1.10.000-TIV-TSMSRV-HP-UX
7.1.10.000-TIV-TSMSRV-Linuxppc64
7.1.10.000-TIV-TSMSRV-Linuxs390x
7.1.10.000-TIV-TSMSRV-Linuxx86_64
7.1.10.000-TIV-TSMSRV-SolarisSPARC
7.1.10.000-TIV-TSMSRV-WIN
IBM Spectrum Protect Server V8.1 Fix Pack 6 (V8.1.6) Downloads
IBM Spectrum Protect Server V7.1.9.X interim fix downloads
IBM Spectrum Protect Server V8.1.1.X interim fix downloads
IBM Spectrum Protect Server V7.1.7.X interim fix downloads
IBM Spectrum Protect Server V7.1 Fix Pack 10 (7.1.10.000) Downloads
APAR status
Closed as program error.
Error description
When a client ingest session, storage pool protection session, or node replication session to a container storage pool references extents that are nearing their reuse delay period, or are supplying replacements for damaged extents, data loss may occur. An extent nearing its reuse delay period is an extent that is not referenced by any objects stored in the storage pool, and remains unreferenced for the period of time for extent reuse as defined on the storage pool. Although the client or replication sessions complete successfully, you may not be able to recover some of the data in the storage pool. Upon restore or retrieval by the client the following error message will appear: ANS4035W File '/Users/jdoe/file.txt' currently unavailable on server. If the error is detected by REPLICATE NODE from the source replication server, the following error may appear: ANR0106E sddedup.c(3494): Unexpected error 4517 fetching row in table "SD.Chunk.Locations". (SESSION: 92124, PROCESS: 879) The restore or retrieval of the affected object will fail, and REPLICATE NODE session will end in failure. IDENTIFYING AFFECTED DATA: To determine if you might be affected by the problem described in this document, run the following commands by using the same instance user ID that is used to start the IBM Spectrum Protect server: 1. If the database manager is not already active, start it. db2 start database manager 2. Open a connection to the server database: db2 connect to tsmdb1 3. Set the default database schema to tsmdb1. db2 set schema tsmdb1 4. To identify objects affected by the problem described in this document, run the following DB2 SQL command: db2 "select distinct objid from sd_recon_order sdro where chunktype=0 and not exists (select 1 from sd_chunk_locations sdcl where sdro.chunkid=sdcl.chunkid) for read only with cs" 5. If the DB2 command outputs any object IDs, you might be affected by the problem described in this document. To obtain information about which objects might be affected, including node name, filespace name, state, creation date, and inactivation date, issue the following command using an IBM Spectrum Protect Command Line Administrative Interface: SHOW INVO OBJID Replace OBJID with the object IDs in the output from step 4. To identify if there are any source servers affected by the storage pool protection scenario, replace SQL command in step 4 above with the following, and execute on the target server: db2 "select distinct rs.servername,sdrc.poolid from sd_replicated_chunks sdrc, replicating_servers rs where rs.serverid=sdrc.srvid and flags=2 and not exists (select 1 from sd_all_chunks sdac where sdrc.chunktype=sdac.chunktype and sdrc.chunkid=sdac.chunkid and sdrc.poolid=sdac.poolid) for read only with ur" REPAIRING DAMAGED DATA To rectify the storage pool protection scenario, follow steps 1-3 above, run the identification SQL and make note of affected source servers and pool IDs, and then: 1. Run the following DB2 SQL command: db2 "delete from sd_replicated_chunks sdrc where flags=2 and not exists (select 1 from sd_all_chunks sdac where sdrc.chunktype=sdac.chunktype and sdrc.chunkid=sdac.chunkid and sdrc.poolid=sdac.poolid)" 2. On each server identified above as affected, run this SQL statement: db2 "select poolname from ss_pools where poolid=<poolid>" Replace <poolid> with the pool ID identified in the identification SQL. 3. Run the PROTECT STGPOOL <poolname> FORCERECONCILE=YES command on the affected source server.
Local fix
There is no local fix for this problem.
Problem summary
**************************************************************** * USERS AFFECTED: * * All IBM Spectrum Protect server users of container storage * * pools * **************************************************************** * PROBLEM DESCRIPTION: * * See error description * **************************************************************** * RECOMMENDATION: * * Recommendation: Apply fixing level when available. This * * problem is currently projected to be fixed in levels * * 7.1.7.400, 7.1.9.100, 7.1.10.000, 8.1.1.200, 8.1.5.100, * * 8.1.6.000. * ****************************************************************
Problem conclusion
This problem was fixed. Affected Platforms: AIX, Linux, Solaris, and Windows.
Temporary fix
Comments
APAR Information
APAR number
IT26255
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
81A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-09-11
Closed date
2018-09-11
Last modified date
2018-09-17
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:
06 September 2023