Direct links to fixes
8.1.10.000-IBM-SPOC-WindowsX64
8.1.10.000-IBM-SPOC-Linuxx86_64
8.1.10.000-IBM-SPOC-Linuxs390x
8.1.10.000-IBM-SPOC-LinuxPPC64le
8.1.10.000-IBM-SPOC-AIX
8.1.10.000-IBM-SPCMS-WindowsX64
8.1.10.000-IBM-SPCMS-WindowsI32
8.1.10.000-IBM-SPCMS-Linuxx86_64
8.1.10.000-IBM-SPSRV-WindowsX64
8.1.10.000-IBM-SPSRV-Linuxx86_64
8.1.10.000-IBM-SPSRV-Linuxs390x
8.1.10.000-IBM-SPSRV-Linuxppc64le
8.1.10.000-IBM-SPSRV-AIX
8.1.9.200-IBM-SPSRV-WindowsX64
8.1.9.200-IBM-SPSRV-Linuxx86_64
8.1.9.200-IBM-SPSRV-Linuxs390x
8.1.9.200-IBM-SPSRV-Linuxppc64le
8.1.9.200-IBM-SPSRV-AIX
IBM Spectrum Protect Server V8.1.9.X interim fix downloads
IBM Spectrum Protect Server V8.1 Fix Pack (V8.1.10) Downloads
APAR status
Closed as program error.
Error description
After upgrade to 8.1.7, expiration can run for days instead of hours. This problem is unrelated to directory container pools. In the reported case, the acltog reporting good expiration before the upgrade. Example: ANR0167I Inventory file expiration process y processed for 89 minutes. ANR0987I Process y for EXPIRE INVENTORY running in the BACKGROUND processed 3,160,491 items with a completion state of SUCCESS After the upgrade, the same expiration took days. ANR0167I Inventory file expiration process z processed for 2454 minutes. In this case it even processed fewer objects: ANR0987I Process z for EXPIRE INVENTORY running in the BACKGROUND processed 2,333,479 items with a completion state of SUCCESS Servermon data shows the expire thread has a consistent slow response from "DB2 Reg Exec". Example: Thread x ExpirationProcessThread parent=z Operation Count Tottime Avgtime Mintime Maxtime ------------ ------- -------- ------- ------- ------- ... DB2 Reg Exec 10764 1300.836 0.121 0.000 751.561 ... The expire process select reported a long wait time from the DB. Example: Execution Time: 1388.296 sec, Number of Executions: 5192, RowsReturned: 3139, Rows Read: 7143461 SELECT IMBK.OBJID, IMBK.BFSIZE, CASE WHEN IMBK.GROUPTYPE IS NOT NULL AND BITAND(IMBK.GROUPTYPE,458752)>0 THEN 1 END AS ISIMGLLEAD, CASE WHEN IMBK.GROUPTYPE IS NOT NULL AND BITAND(IMBK.GROUPTYPE,7)>0 THEN 1 END AS ISIMGLMEMB, CASE WHEN IMBK.GROUPTYPE IS NOT NULL AND BITAND(IMBK.GROUPTYPE,131074)>0 THEN 1 END AS ISIMGLPEER, IMBK.OBJCHGID, IMBK.FLAGS, IMBK.DEACDATE, IMBK.INSDATE, IMBK.STATE FROM TSMDB1.BACKUP_OBJECTS IMBK WHERE IMBK.NODEID=? AND IMBK.FSID=? AND IMBK.OBJTYPE=? AND IMBK.MCID=? AND ( IMBK.STATE=5 OR ( IMBK.STATE=2 AND ( BITAND(IMBK.GROUPTYPE,CAST(? AS INT))=0 OR IMBK.GROUPTYPE=131072 OR IMBK.GROUPTYPE IS NULL ) AND ( IMBK.DEACDATE<='1956-09-05 00:00:00' OR ( IMBK.DEACDATE<=? AND imbk.objtype!=12 AND not exists ( select 1 from TSMDB1.backup_objects imbkother1 where imbkother1.state=1 and imbkother1.nodeid=imbk.nodeid and imbkother1.fsid=imbk.fsid and imbkother1.objtype=imbk.objtype and imbkother1.hl=imbk.hl and imbkother1.ll=imbk.ll ) and not exists ( select 1 from TSMDB1.backup_objects imbkother2 IBM Spectrum Protect versions affected: Server versions 8.1.7 and above on all supported platforms | MDVREGR 8.1.7.0 5698MSV | Keywords: TSM TS003085170 dramatic slow down
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 levels 8.1.9.200 and 8.1.10. Note * * that this is subject to change at the discretion of IBM. * ****************************************************************
Problem conclusion
This problem was fixed. Affected platforms for reported release: AIX, Linux, and Windows.
Temporary fix
Comments
APAR Information
APAR number
IT31595
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
2020-01-20
Closed date
2020-03-11
Last modified date
2020-03-11
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:
28 September 2021