Direct links to fixes
8.1.6.200-IBM-SPSRV-WindowsX64
8.1.6.200-IBM-SPSRV-Linuxx86_64
8.1.6.200-IBM-SPSRV-Linuxs390x
8.1.6.200-IBM-SPSRV-Linuxppc64le
8.1.6.200-IBM-SPSRV-AIX
8.1.7.000-IBM-SPSRV-Linuxppc64le
8.1.7.000-IBM-SPCMS-WindowsX64
8.1.7.000-IBM-SPCMS-WindowsI32
8.1.7.000-IBM-SPCMS-Linuxx86_64
8.1.7.000-IBM-SPOC-WindowsX64
8.1.7.000-IBM-SPOC-Linuxx86_64
8.1.7.000-IBM-SPOC-Linuxs390x
8.1.7.000-IBM-SPOC-LinuxPPC64le
8.1.7.000-IBM-SPOC-AIX
8.1.7.000-IBM-SPSRV-WindowsX64
8.1.7.000-IBM-SPSRV-Linuxx86_64
8.1.7.000-IBM-SPSRV-Linuxs390x
8.1.7.000-IBM-SPSRV-AIX
IBM Spectrum Protect Server V8.1 Fix Pack 7 (V8.1.7) Downloads
IBM Spectrum Protect Server V8.1.6.X interim fix downloads
APAR status
Closed as program error.
Error description
When running Protect Stgpool with the Forcereconcile=yes parameter, no reconcile activity is performed due to extraneous reconcile status database entries. At levels 8.1.6 and 8.1.6.100, Protect Stgpool will run Forcereconcile on a given server and pool pair one time. Subsequent attempts to run with Forcereconcile=yes results in no reconcile activity being performed. If you attempt to run reconcile because of a failure of PROTECT STGPOOL or REPLICATE NODE, the process will end in FAILURE repeatedly even with Forcereconcile=yes. If you run reconcile for any other reason, Protect Stgpool will silently skip the reconcile processing. No other error messages are given. This APAR can be detected by running the following SQL queries on the source server as the IBM Spectrum Protect instance user after running with Forcereconcile=yes: db2 connect to tsmdb1 db2 set schema tsmdb1 db2 "select * from sd_reconcile_status" db2 "select poolname,poolid from ss_pools" db2 "select servername,serverid from replicating_servers" And on the target server run these SQL queries: db2 connect to tsmdb1 db2 set schema tsmdb1 db2 "select poolname,poolid from ss_pools" Correlate the server ID to the server name, and pool IDs to pool names to check the entries in sd_reconcile_status. If all entries have both INSDATE and ENDDATE values, this APAR applies. IBM Spectrum Protect versions affected: Server 8.1.6 and 8.1.6.100 on all supported platforms Initial Impact: Low Additional keywords TSM IBM Spectrum Protect replication Protect Stgpool reconcile forcereconcile failure
Local fix
On the source server, issue the following SQL query: db2 "delete from sd_reconcile_status where serverid=? and poolid=? and replpoolid=?" Fill the question marks with the appropriate server and pool IDs as identified above.
Problem summary
**************************************************************** * USERS AFFECTED: * * All IBM Spectrum Protect server users of PROTECT STGPOOL. * **************************************************************** * PROBLEM DESCRIPTION: * * See error description. * **************************************************************** * RECOMMENDATION: * * Apply fixing level when available. This problem is projected * * to be fixed in level 8.1.7. Note that this is subject to * * change at the discretion of IBM. * * * * After applying the fixing level, run PROTECT STGPOOL with * * FORCERECONCILE=YES twice if it was previously ending in * * FAILURE. If it was ending in FAILURE, the first run of * * FORCERECONCILE will end quickly, and the second will perform * * all reconcile work. * ****************************************************************
Problem conclusion
The problem was fixed.
Temporary fix
Comments
APAR Information
APAR number
IT27239
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
2018-12-07
Closed date
2018-12-07
Last modified date
2018-12-07
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
R81L PSY
UP
R81A PSY
UP
R81W PSY
UP
Document Information
Modified date:
27 September 2021