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
8.1.6.100-IBM-SPSRV-Linuxppc64le
8.1.6.100-IBM-SPSRV-AIX
8.1.6.100-IBM-SPSRV-Linuxs390x
8.1.6.100-IBM-SPSRV-Linuxx86_64
8.1.6.100-IBM-SPSRV-WindowsX64
IBM Spectrum Protect Server V8.1 Fix Pack 6 (V8.1.6) Downloads
IBM Spectrum Protect Server V8.1.6.X interim fix downloads
APAR status
Closed as program error.
Error description
Protect process may complete with ANR4002W message that states some extents may not be protected, ANR0986I message indicating WARNING and ANR1892W message saying success but warning of severe messages being issued. This error can occur against both types of protect, local and replserver. For example: ANR4002W The protect storage pool process for CONTAINERSTG on TSM1 to CONTAINER_TAPE on TSM1 is complete. Some extents might not have been protected. Extents protected: 26721619 of 26721619. Extents failed to protect: 0. Amount protected: 4,238 GB of 4,238 GB. Amount failed to protect: 0 bytes. Extents deleted: 339427 of 339427. Extents failed to delete: 0. Extents moved: 0 of 0. Extents failed to move: 0. Amount moved: 0 bytes of 0 bytes. Amount failed to move: 0 bytes. Elapsed time: 0 Days, 14 Hours, 22 Minutes. (SESSION: 161206, PROCESS: 6811) ANR0986I Process 6811 for PROTECT STGPOOL (SUMMARY) running in the BACKGROUND processed 26,721,619 items for a total of 4,551,564,283,419 bytes with a completion state of WARNING at 03:40:30. (SESSION: 161206, PROCESS: 6811) ANR1892W Process 6811 for PROTECT STGPOOL (SUMMARY) completed with a completion state of SUCCESS but warning or more-severe messages were issued. (SESSION: 161206, PROCESS: 6811) There are no other message in the actlog or the dsmffdc.log that indicates any reason for the warning indications or reason why some extents were not protected. Analysis of this situation revealed that prior to the start of the protect processing there were one or more containers with all the extents residing on them having 0 refcounts. This means that the container was eligible for removal. If the removal of that container occurred after protect put the container on the list of those needing protection but before the worker threads got to a point of actually protecting the container then the container was not found resulting in the warning situation that is not externalized at any level. Diag code was required to output ffdc entries to determine this was the problem. Since there are no messages output indicating this issue exists the following DB2 select can be run just prior to a protect ending with the above messages to see if containers exist whose extents all have 0 refcounts: select distinct cntrid from tsmdb1.sd_containers sdcn where (sdcn.type=1 and not exists (select 1 from tsmdb1.sd_chunk_locations cl where cl.poolid=sdcn.poolid and cl.cntrid=sdcn.cntrid and cl.refcount>=1)) or (sdcn.type=2 and not exists (select 1 from tsmdb1.sd_non_dedup_locations cl2 where cl2.poolid=sdcn.poolid and cl2.cntrid=sdcn.cntrid and (cl2.refcount is null or cl2.refcount>=1))) for read only with ur /*<OPTGUIDELINES><IXSCAN TABLE='cl2' INDEX='SDNDL_REFCOUNT_NDX' /></OPTGUIDELINES>*/ If the above select returns any container ids (CNTRID) then this APAR may apply. Please note that APAR IT23744 has recently been opened to address the more global issue of local protect ending with these warning message but no other external messages being issue to indicate why. This APAR will address this specific container deletion while protect is in-flight issue IBM Spectrum Protect Versions Affected: 7,1,3 and above Initial Impact: High
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All IBM Spectrum Protect server users * **************************************************************** * PROBLEM DESCRIPTION: * * See error description. * **************************************************************** * RECOMMENDATION: * * Apply fixing level when available. This problem is currently * * projected to be fixed in level 8.1.6. * ****************************************************************
Problem conclusion
The problem was fixed. Affected platforms for reported release: AIX, Linux, and Windows Platforms fixed: AIX, Linux, and Windows
Temporary fix
Comments
APAR Information
APAR number
IT24062
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-02-13
Closed date
2018-05-21
Last modified date
2018-05-21
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