IC70741: IDENTIFY DUPLICATES CAN GET INTO A LOOP WHEN ATTEMPTING TO DE-DUPLICATE VERY SMALL OBJECTS.

APAR status

• Closed as program error.

Error description

• A loop occurs as the process tries to remove the "pending"
  status for a given bitfile, but no rows
  were inserted into the DB, since the object is so small and this
  results in a RC=2 (object not
  found) which is not being tolerated. This should be expected
  for objects too small to be de-duplicated.
  
  
  Level 2 diagnostics:
  q process will show the identify duplicates process staying on
  the same filesize.
  
  show dedupthread will show a thread staying on the same bitfile
  id.
  
  A server trace with adm af pvr mms dedup dedup1 dedup2 flags
  will show:
  
  [bfdedup.c][10237][BfRemovePendingStatus]:Error 2
  removing pending state of ID 1282053781
  [pvrntp.c][5394][NtpBuildComBlockHdr]:Building NTP
  Block Header - block ID = 1050886 and data bytes = 262096.
  [bfdedup.c][10244][BfRemovePendingStatus]:Remove
  complete, rc: 87, 0 rows updated
  [bfdedup.c][10248][BfRemovePendingStatus]:Exiting, rc: 87
  
  
  [bfdedup.c][8186][BfDedupVolumeThread]:Retrying
  object 518143736 due to rc = 87 - retries left 3.
  
  
  
  
  Tivoli Storage Manager Versions Affected:
  Server versions 6.x on all platforms
  
  Initial Impact:
  Medium
  
  Additional Keywords:
  zz62 zz61 identify duplicates hang hung slow loop
  

Local fix

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 6.2.2.                              *
  *                 Note that this is subject to change at the   *
  *                 discretion of IBM.                           *
  ****************************************************************
  See ERROR DESCRIPTION.
  

Problem conclusion

• The described problem has been resolved.
  

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

• R62A PSY

     UP

• R62H PSY

     UP

• R62L PSY

     UP

• R62S PSY

     UP

• R62W PSY

     UP