IT31782: EXPIRATION RUNNING AT THE SAME TIME AS CONVERT STGPOOL CAN CAUSE EXCESSIVE DIRECTORY-CONTAINER SPACE UTILIZATION

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

• Error Description:
  
  Running expiration at the same time as running "convert stgpool"
  can cause a problem in that expiration skips the file deletion
  in the directory-container pool, but removes the reference to
  the object, which causes the object to become orphaned and will
  never be removed in the future.
  This leads to seeing an increased amount of space being utilized
  within the directory-container pool that the convert is
  processing as a target pool.
  
  
  Customer/Support Diagnostics (If Applicable)
  
  
  To see if this APAR is affecting an environment,  issue the
  following SQL from the DB2 instance account :
  
  db2 connect to TSMDB1
  db2 set schema TSMDB1
  
  Obtain the poolid of your storage pool, replacing POOL with the
  appropriate name :
  
  db2 "select poolid from ss_pools where poolname='POOL'"
  
  Replace X in the following statement with the pool id number
  obtained above :
  
  
  db2 "select count_big from sd_recon_order sdro where chunktype=1
   and not exists (select 1 from backup_objects imbk where
  sdro.objid=imbk.objid) and not exists (select 1 from
  archive_objects imar where imar.objid=sdro.objid) and not exists
   (select 1 from Spaceman_Objects imsm where
  sdro.objid=imsm.objid) and not exists (select 1 from
  bf_super_aggregates bfsa where (bfsa.objid=sdro.objid or
  bfsa.fragid=sdro.objid) ) and exists (select 1 from
  sd_non_dedup_locations sdndl where sdndl.poolid=X and
  sdndl.chunkid=sdro.chunkid) for read only"
  
  
  This issue will be more noticeable in an environment, if the
  number returned from the above SQL is in the thousands.
  
  This APAR will stop the creation of orphaned extents if "convert
  stgpool" is ran at the same time as expiration, but IBM support
  should be contacted to manually remove the orphaned objects that
  have already been created.
  
  Once at the fixing level, manual removal of the orphaned objects
  would still need to be performed.
  
  It is recommended to apply the fixing level of this APAR before
  performing a "convert stgpool" command.
  
  IBM Spectrum Protect Versions Affected:
  Spectrum Protect Server versions 7.1.6 and 8.1 onwards.
  
  Initial Impact:
  Medium
  
  Additional Keywords:
  TSM, TS003287559, utilisation, full, orphan, util, utilization,
  bloat
  

Local fix

• Avoid running expiration at the same time as running "convert
  stgpool"
  

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.
  Platforms fixed:   AIX, Linux, Windows.
  

Temporary fix

Comments

APAR Information

• 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