Direct links to fixes
8.1.8.000-IBM-SPOC-Linuxs390x
8.1.8.000-IBM-SPSRV-Linuxppc64le
8.1.8.000-IBM-SPCMS-WindowsX64
8.1.8.000-IBM-SPCMS-WindowsI32
8.1.8.000-IBM-SPCMS-Linuxx86_64
8.1.8.000-IBM-SPOC-WindowsX64
8.1.8.000-IBM-SPOC-Linuxx86_64
8.1.8.000-IBM-SPOC-LinuxPPC64le
8.1.8.000-IBM-SPOC-AIX
8.1.8.000-IBM-SPSRV-WindowsX64
8.1.8.000-IBM-SPSRV-Linuxx86_64
8.1.8.000-IBM-SPSRV-Linuxs390x
8.1.8.000-IBM-SPSRV-AIX
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
IBM Spectrum Protect Server V8.1.6.X interim fix downloads
IBM Spectrum Protect Server V8.1 Fix Pack 8 (V8.1.8) Downloads
APAR status
Closed as program error.
Error description
In S3 type cloud pools stored in Amazon Web Services (AWS), if a CloudURL is improperly configured to include a bucket name, some of the containers might be unreadable because of an incorrectly saved container name. In this improper configuration, there is the bucket name from the CLOUDURL, but there is also a BUCKETNAME parameter on the stgpool. When referring to these two names, the bucket name from the CLOUDURL will be referred to as 'BUCKETNAME from CLOUDURL', and the BUCKETNAME parameter on the stgpool will be referred to as 'BUCKETNAME from stgpool'. Under the APAR condition you might see the following message reported in the actlog: ANR3660E An unexpected error occurred while opening or writing to the container. Container <BUCKETNAME fom CLOUDURL>/<BUCKETNAME from stgpool>/<subdirname>/<objectkey> in stgpool <AWSPOOL> has been marked as UNAVAILABLE and should be audited to validate accessibility and content. If you are exposed to the symptom documented with this APAR you might also see the symptom as documented with IT26780: S3 AWS TYPE CLOUD CONTAINERS MIGHT REMAIN IN THE CLOUD AFTER BEING DELETED FROM SPECTRUM PROTECT SERVER https://www-01.ibm.com/support/docview.wss?uid=swg1IT26780 IBM Spectrum Protect Versions Affected: 7.1.7 and newer servers Customer/L2 Diagnostics (If Applicable) As server instance user you can use the following DB2 commands to confirm you are exposed to the symptom documented with this APAR: db2 connect to tsmdb1 db2 set schema tsmdb1 db2 "select count from sd_containers where type=3 and cntrname LIKE '<BUCKETNAME from CLOUDURL>/<BUCKETNAME from stgpool>%' " If the select returns a count > 0 you are facing the symptom documented here. Initial Impact: Medium Additional Keywords: AWS container SD cloud tsm TS000892900
Local fix
contact IBM support to get instructions to rename the affected containers.
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.6.200 and 8.1.8. 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. Platforms fixed: AIX, Linux, and Windows.
Temporary fix
Comments
APAR Information
APAR number
IT28146
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
2019-02-18
Closed date
2019-03-04
Last modified date
2019-03-04
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:
09 September 2021