Direct links to fixes
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.6.X interim fix downloads
IBM Spectrum Protect Server V8.1 Fix Pack 7 (V8.1.7) Downloads
APAR status
Closed as program error.
Error description
When runnng a client backup to a cloud container the following SQL statment is run. Instead of running the select against the container ID it is running against the container name: . SELECT CNTRID,TYPE,STATE FROM "TSMDB1"."SD_CONTAINERS" WHERE (CNTRNAME=?) FETCH FIRST 1 ROW ONLY FOR READ ONLY WITH UR . Customer L2 Diagnostics: Run the performance diagnostic tool servermon while a backup is running. . Note the the following select running for a long period of time: Execution Time: 872.201 sec, Number of Executions: 5889, RowsReturned: 5889, Rows Read: 5889 SELECT CNTRID,TYPE,STATE FROM "TSMDB1"."SD_CONTAINERS" WHERE (CNTRNAME=?) FETCH FIRST 1 ROW ONLY FOR READ ONLY WITH UR --127832 <---Note the thread number . . In the show.txt the following can be seen when the thread is matched: . Thread 127832, Parent 127831: SdCQSinkThread, Storage 2808, AllocCnt 126781 HighWaterAmt 14412150 tid=140087741998848, ptid=140076171749120, det=1, zomb=0, join=0, result=0, sess=0, procToken=0, sessToken=56313 lwp=369729 . Additional Keywords: SdCQSinkThread cloud performance backup
Local fix
Apply server fix when available.
Problem summary
**************************************************************** * USERS AFFECTED: * * All IBM Spectrum Protect server users of cloud object * * storage using local storage pool directories. * **************************************************************** * PROBLEM DESCRIPTION: * * See error description. * **************************************************************** * RECOMMENDATION: * * Apply fixing level when available. This problem is currently * * projected to be fixed in levels 8.1.6.100 and 8.1.7. Note * * that this is subject to change at the discretion of IBM. * ****************************************************************
Problem conclusion
This problem was fixed.?Affected platforms for reported releases: AIX, Linux, and Windows.?Platforms fixed: AIX, Linux, Windows.
Temporary fix
Comments
APAR Information
APAR number
IT26619
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-10-15
Closed date
2018-10-18
Last modified date
2018-10-18
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