Direct links to fixes
8.1.1.100-IBM-SPOC-WindowsX64
8.1.1.100-IBM-SPOC-Linuxx86_64
8.1.1.100-IBM-SPOC-Linuxs390x
8.1.1.100-IBM-SPOC-AIX
8.1.1.000-IBM-SPSRV-WindowsX64
8.1.1.000-IBM-SPSRV-Linuxs390x
8.1.1.000-IBM-SPSRV-AIX
8.1.1.000-IBM-SPSRV-Linuxx86_64
7.1.7.100-TIV-TSMSRV-WIN
7.1.7.100-TIV-TSMSRV-SolarisSPARC
7.1.7.100-TIV-TSMSRV-Linuxx86_64
7.1.7.100-TIV-TSMSRV-Linuxs390x
7.1.7.100-TIV-TSMSRV-Linuxppc64
7.1.7.100-TIV-TSMSRV-HP-UX
7.1.7.100-TIV-TSMSRV-AIX
IBM Spectrum Protect Server V8.1 Fix Pack 1 (V8.1.1) Downloads
IBM Spectrum Protect Server V7.1.7.X interim fix downloads
IBM Spectrum Protect Server V7.1 Fix Pack 8 (7.1.8.000) Downloads
APAR status
Closed as program error.
Error description
The problem appears as a lack of space in a target server replication stgpool. Some sequential volumes show nothing with a "QUERY CONTENT" command, but are still shown in the Tivoli Storage Manager Server with a full status and space used. This APAR applies when 1.) A file that is not fragmented on the source replication server but is fragmented on the target replication server - and - 2.) A subsequent replication updates the "flags" field in the inventory table causing the server to lose the fact that the object was fragmented on the target replication server Tivoli Storage Manager Versions Affected: V7.1.3.0 and higher on all supported platforms | MDVREGR 7.1.3.0-TIV_5698MSV | Customer/L2 Diagnostics: Example for a tape volume: "q vol" still shows volume is being utilized tsm: TSMSRV>q vol TAPEXX f=d Volume Name: TAPEXX Storage Pool Name: STGXX Device Class Name: DEVCXX Estimated Capacity: 1.8 T Scaled Capacity Applied: Pct Util: 42.2 Volume Status: Full Access: Read/Write Pct. Reclaimable Space: 57.8 Scratch Volume?: Yes ....... But Q CONTENT shows nothing: tsm: TSMSRV>q content TAPEXX followl=yes ANR2034E QUERY CONTENT: No match found using this criteria. ANS8001I Return code 11. "Select from content" shows a lot of fragments of type UNKNOWN for the same single object_id => VOLUME_NAME: TAPEXX NODE_NAME: TYPE: UNKNOWN FILESPACE_NAME: AGGREGATED: No FILE_SIZE: SEGMENT: 1/1 FRAGMENT: 2 CACHED: NO FILESPACE_ID: 13 FILESPACE_HEXNAME: BITFILE_ID: 581841724 OBJECT_ID: 581841033 COPIED: No DAMAGED: No FILE_NAME: FILE_HEXNAME: VOLUME_NAME: TAPEXX NODE_NAME: TYPE: UNKNOWN FILESPACE_NAME: AGGREGATED: No FILE_SIZE: SEGMENT: 1/1 FRAGMENT: 3 CACHED: NO FILESPACE_ID: 13 FILESPACE_HEXNAME: BITFILE_ID: 581841735 OBJECT_ID: 581841033 COPIED: No DAMAGED: No FILE_NAME: FILE_HEXNAME: ... etc .. A select from backups or archives table for this object id shows nothing => tsm: TSMSRV>select * from backups where object_id='581841033' ANR2034E SELECT: No match found using this criteria. ANS8001I Return code 11. tsm: TSMSRV>select * from archives where object_id='581841033' ANR2034E SELECT: No match found using this criteria. ANS8001I Return code 11. To identify affected objects: The following command creates a macro of SHOW INVO commands for objects that should be marked as being fragmented but are not: db2 connect to tsmdb1 db2 set schema tsmdb1 db2 -x "select distinct 'show invo' || bfsa.objid from bf_super_aggregates bfsa inner join backup_objects imbk on (imbk.objid=bfsa.objid) where imbk.flags is null or imbk.flags=65535 or BITAND(imbk.flags, 16)=0" > showinvo.mac In the output of this first macro, each SHOW INVO command reports a replica objid, issuing a SHOW INVO on the source server for that replica objid shows the source file is not fragmented. Next do a: db2 "select poolname, poolid from tsmdb1.ss_pools" to get the pool id associated with this storage pool and use that value to replace the ? in the next select statement. If several stgpools are affected, several select must be done, one per stgpool. The following can be used to identify files that are deleted but still have existing fragments: db2 "select distinct( 'show invo ' || cast( bfsa.objid as char(24) ) ) from tsmdb1.bf_super_aggregates bfsa where bfsa.poolid=? and bfsa.bfid not in ( select afbf.bfid from tsmdb1.af_bitfiles afbf where afbf.srvid=0 and afbf.bfid=bfsa.bfid and afbf.poolid=bfsa.poolid )" > showinvo2.mac The SHOW INVO output from this second macro should show the inventory object does not exist, the first fragment does not exist but subsequent fragments do exist. Initial Impact: Medium Additional Keywords: TSM lack space Spectrum Protect
Local fix
Contact IBM support to do a manual cleanup if the space used by those objects is too important, and waiting for APAR correction and upgrade is not an option.
Problem summary
**************************************************************** * USERS AFFECTED: * * All Tivoli Storage Manager server users. * **************************************************************** * PROBLEM DESCRIPTION: * * See error description. * **************************************************************** * RECOMMENDATION: * **************************************************************** Apply fixing level when available. This problem is currently projected to be fixed in levels 7.1.7.100, 7.1.8.0, and 8.1.1.0. Note that this is subject to change at the discretion of IBM.
Problem conclusion
This problem was fixed. Affected platforms: AIX, HP-UX, Solaris, Linux, and Windows.
Temporary fix
Comments
APAR Information
APAR number
IT17285
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
71L
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-09-30
Closed date
2017-02-01
Last modified date
2017-02-01
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
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.3","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
01 February 2017