IC58881: EXCESSIVE # OF PM SNAPSHOTS TAKEN WHEN PROBE INOPERATIVE

APAR status

• Closed as program error.

Error description

• The problem is that we are taking too many snapshots, which
  makes the snapshot tables grow very large.  This is not good for
  performance or database size, particularly since the snapshots
  end up with the same info.
  

Local fix

Problem summary

• Users Affected:
  Any TPC users collecting performance data on storage subsystems
  or switches, when the device's configuration has changed but no
  new probe has yet been done on the device.
  
  Problem Description:
  TPC is designed to take a new historical snapshot of the
  device's configuration, in order to be able to later correlate
  the collected performance data.  However, the logic to determine
  if the device has been probed (before taking a new snapshot) is
  not working properly.  This can result in many superfluous
  snapshots being taken, which will needlessly increase the amount
  of database space used, and can also result in performance
  degradation of TPC, when generating performance reports.
  

Problem conclusion

• The faulty logic has been corrected, such that a new
  configuration snapshot is only taken when a probe has been done
  (i.e. the new snapshot actually contains different or new
  information than the previous snapshot).
  
  A fix will be available in an upcoming IBM TotalStorage
  Productivity Center fix pack.
  
  version 3.3.1 - target January 2009
  version 3.3.2 - target February 2009
  

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

  MDM PERFORMANCE

• Fixed component ID

  5648GPC01

Applicable component levels

• R331 PSY

     UP