Direct links to fixes
8.1.10.300-IBM-SPSRV-WindowsX64
8.1.10.300-IBM-SPSRV-Linuxx86_64
8.1.10.300-IBM-SPSRV-Linuxs390x
8.1.10.300-IBM-SPSRV-Linuxppc64le
8.1.10.300-IBM-SPSRV-AIX
8.1.12.100-IBM-SPCMS-WindowsX64
8.1.12.100-IBM-SPCMS-WindowsI32
8.1.12.100-IBM-SPCMS-Linuxx86_64
8.1.12.100-IBM-SPOC-WindowsX64
8.1.12.100-IBM-SPOC-Linuxx86_64
8.1.12.100-IBM-SPOC-Linuxs390x
8.1.12.100-IBM-SPOC-LinuxPPC64le
8.1.12.100-IBM-SPOC-AIX
8.1.12.100-IBM-SPSRV-WindowsX64
8.1.12.100-IBM-SPSRV-Linuxx86_64
8.1.12.100-IBM-SPSRV-Linuxs390x
8.1.12.100-IBM-SPSRV-Linuxppc64le
8.1.12.100-IBM-SPSRV-AIX
IBM Spectrum Protect Server V8.1.12.X interim fix downloads
IBM Spectrum Protect Server V8.1 Fix Pack 13 (V8.1.13) Downloads
APAR status
Closed as program error.
Error description
The replication process might fail on Source Server with message: ANR0327I Replication of node xxxxx, yyyyy, completed. Files current: 8,234,167. Files replicated: 144,276 of 144,270. Files updated: 110,593 of 110,593. Files deleted: 144,530 of 144,530. Amount replicated: 122 GB of 121 GB. Amount transferred: 122 GB. Elapsed time: 0 Days, 0 Hours, 52 Minutes. (SESSION: 98677, PROCESS: 911) ANR1893E Process 911 for Replicate Node completed with a completion state of FAILURE. (SESSION: 98677, PROCESS: 911) Moreover the following messages are reported in the activity log on the source replication server: ANR0102E Error 1202 inserting row in table "Replicated.Objects".~ ANR2183W Transaction 0:1143321614 was aborted.~ The failure is seen when a replication process retries the replication of some objects before a batch of deletes for the same filespace is finished running. This results in the source server having one version of an object, and target server having two (or more) versions of that object. To see if the server is affected of this APAR perform the following actions: On the source, db2 connect to tsmdb1; db2 set schema tsmdb1; db2 "select count_big AS count from replicated_objects" save outputs. On the target, db2 connect to tsmdb1; db2 set schema tsmdb1; db2 "select count_big AS count, REPL_OBJID from replicated_objects group by REPL_OBJID having count > 1" db2 "select count_big AS count from replicated_objects" save outputs. If there is any non-zero count from the first SQL on the target: db2 "select count_big AS count, REPL_OBJID from replicated_objects group by REPL_OBJID having count > 1" that indicates that duplicate versions are present on the target for the same object on the source. Note: Duplicate objects on the target should have little affect on storage utilization in container pools because the data would be deduplicated. IBM Spectrum Protect Server version Affected: Spectrum Protect Servers 8.1.10 and later on all supported platforms. Initial Impact: low Additional Keywords: ANR1893E replication ANR0102E TS004488648
Local fix
On the source server, set the option REPLDELETEPRIORITY to LOW. This should help prevent creation of more duplicates while waiting for the fix. On the source server, perform a replicate node with FORCERECONCILE=FULL periodically to cleanup existing duplicates. Run the above replicate node once a week or at least once a month.
Problem summary
**************************************************************** * USERS AFFECTED: * * All IBM Spectrum Protect server users who use Replicate Node * **************************************************************** * PROBLEM DESCRIPTION: * * See error description. * **************************************************************** * RECOMMENDATION: * * Apply fixing level when available. This problem is currently * * projected to be fixed in levels 8.1.13, 8.1.10.300, * * 8.1.11.200, and 8.1.12.100. Note that this is subject to * * change at the discretion of IBM. * ****************************************************************
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
IT35505
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
81L
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-02-03
Closed date
2021-03-12
Last modified date
2021-03-25
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
R81A PSY
UP
R81L PSY
UP
R81W PSY
UP
Document Information
Modified date:
17 December 2021