IT17266: DELETE OF CONTAINER STG FAILS WITH ANR2383E DELETE STGPOOL: STG IN USE BY CLIENTS AND/OR DATA MANAGEMENT OPERATIONS

8.1.1.000-IBM-SPSRV-Linuxx86_64
8.1.1.000-IBM-SPSRV-AIX
8.1.1.000-IBM-SPSRV-Linuxs390x
8.1.1.000-IBM-SPSRV-WindowsX64
8.1.1.100-IBM-SPOC-AIX
8.1.1.100-IBM-SPOC-Linuxs390x
8.1.1.100-IBM-SPOC-Linuxx86_64
8.1.1.100-IBM-SPOC-WindowsX64
7.1.8.000-TIV-TSMSRV-AIX
7.1.8.000-TIV-TSMSRV-HP-UX
7.1.8.000-TIV-TSMSRV-Linuxppc64
7.1.8.000-TIV-TSMSRV-Linuxs390x
7.1.8.000-TIV-TSMSRV-Linuxx86_64
7.1.8.000-TIV-TSMSRV-SolarisSPARC
7.1.8.000-TIV-TSMSRV-WIN
7.1.8.000-TIV-TSMOC-AIX
7.1.8.000-TIV-TSMOC-Linuxx64
7.1.8.000-TIV-TSMOC-Windows
7.1.8.000-TIV-TSMOC-LinuxPPC64
7.1.8.000-TIV-TSMOC-LinuxPPC64le
7.1.8.000-TIV-TSMOC-LinuxS390
IBM Spectrum Protect Server V8.1 Fix Pack 1 (V8.1.1) Downloads

APAR status

• Closed as program error.

Error description

• Deletion of a container storage pool fails with an ANR2383E
  DELETE STGPOOL: Storage pool CONTAINERVPOOL is currently in use
  by clients and/or data management operations. This message is
  issued because the pool being deleted is a deduplicated storage
  pool (which will be the case for all container storage pools),
  and there are also active dedup deletion threads running at the
  same time as this storage pool delete. For this problem to occur
  the server must have legacy file dedup storage pools defined
  with data residing in the file dedup pool that may possibly need
  to be deleted. The show dedupdeleteinfo output will indicate
  that there are dedup deletion threads running.
  Because the delete storage pool is processing a container pool
  that does not use dedup deletion threads the check for this
  concurrent activity is not valid. The check for active dedup
  deletion threads should only occur during delete storage pool
  processing when the storage pool being deleted is a legacy dedup
  file pool.
  Tivoli Storage Manager Versions Affected: IBM Spectrum Protect
  7.1.3 and above all platforms
  Initial Impact: Medium
  Additional Keywords: TSM removal
  

Local fix

• Wait for the dedup deletion threads processing to complete all
  its work then run the delete storage pool command for the
  container pool again. The command show dedupdeleteinfo can be
  used to display the status of the dedup deletion threads.
  OR
  Use the server option dedupdeletionthreads 0 to tell the server
  not to run any dedup deletionthreds. A server recycle is needed
  to enable this option. After the del stg this option shoud be
  removed so dedup deletions can run again. Another server restart
  is needed to remove this 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 level 8.1.1. Note that this is                            *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  Affected platforms:  AIX, Linux, and 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