IT15296: REPAIR STGPOOL DOES NOT REPAIR ALL EXTENTS IN DIRECTORY-CONTAINER POOLS

7.1.6.000-TIV-TSMSRV-Linuxs390x
7.1.6.000-TIV-TSMSRV-Linuxppc64
7.1.6.000-TIV-TSMSRV-WIN
7.1.6.000-TIV-TSMSRV-SolarisSPARC
7.1.6.000-TIV-TSMSRV-Linuxx86_64
7.1.6.000-TIV-TSMSRV-HP-UX
7.1.6.000-TIV-TSMSRV-AIX
IBM Spectrum Protect Server V7.1 Fix Pack 6 (7.1.6.000) Downloads

APAR status

• Closed as program error.

Error description

• Problem Description:
  REPAIR STGPOOL may not repair all extents in directory-container
  pools, despite claiming to have done so. After running REPAIR
  STGPOOL to repair damaged data in a directory container storage
  pool, the data remains unrestorable. In addition, QUERY DAMAGED
  will not show any damaged extents, files, nodes or containers in
  the pool.
  
  Customer/L2 Diagnostics:
  Search the activity log to determine if REPAIR STGPOOL was run.
  Use the following db2 query on the source server to find out if
  damaged extents remain in the pool:
  
  select 1 from tsmdb1.sd_chunk_locations sdcl inner join
  tsmdb1.sd_replicated_chunks sdrc on (sdcl.poolid=sdrc.poolid and
  sdcl.chunkid=sdrc.chunkid) where sdcl.poolid=XXXX and
  sdrc.chunktype=0 and bitand(sdcl.flags,1)=1 fetch first row only
  for ur
  
  select 1 from tsmdb1.sd_non_dedup_locations sdndl inner join
  tsmdb1.sd_replicated_chunks sdrc on (sdndl.poolid=sdrc.poolid
  and sdndl.chunkid=sdrc.chunkid) where sdndl.poolid=XXXX and and
  sdrc.chunktype=1 and bitand(sdndl.flags,1)=1 fetch first row
  only for ur
  
  These queries will identify if there are still extents that are
  damaged, although they protected to a target server. Run these
  queries for each directory-container pool on the source server
  that has had Protect Stgpool run, and this issue is suspected.
  Use SHOW SDPOOL and and make note of the poolids for each
  suspected pool. Replace "XXXX" in the queries with this number
  and repeat for each pool individually. If either query results
  in a return of 1 record, this APAR is in effect for that pool.
  
  Tivoli Storage Manager Versions Affected: 7.1.3, 7.1.4 and 7.1.5
  
  Initial Impact: Medium
  
  Additional Keywords: protect repair restore damage fail failure
  

Local fix

• Install fix when available.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Tivoli Storage Manager users of directory-container      *
  * storage pools.                                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. After applying fixing     *
  * level, run REPAIR STGPOOL twice. The first time REPAIR       *
  * STGPOOL is run, it will make a one time repair of database   *
  * entries that will allow the second repair to succeed. It     *
  * will appear to do nothing, yet it will report that it ended  *
  * in SUCCESS. This problem is projected to be fixed in 7.1.6.  *
  * Note that this is subject to change at the discretion of     *
  * IBM.                                                         *
  ****************************************************************
  

Problem conclusion

• The problem was fixed.
  Affected Platforms: AIX, Linux, Windows, Sun
  

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