faqts : Computers : Management Systems : TCSI : Catalant : Server Development : Performance/QoS Manager

+ Search
Add Entry AlertManage Folder Edit Entry Add page to http://del.icio.us/
Did You Find This Entry Useful?

2 of 2 people (100%) answered Yes

Entry

How does Catalant PM use dataRetentionTime and dbMaxRecords?

Apr 10th, 2001 09:55
Engineer TCSI,


pmDataSourceType::dataRetentionTime specifices how long PM will 
  keep data in DB. Is this independent of dbMaxRecords? I.e., if 
  the data is over 24 hours old, will it be deleted no matter 
  how "full" the DB is? When does the delete occur (every 24 
  hours, every 10 minutes)?
Your understanding of pmDataSourceType::dataRetentionTime is correct. 
Yes its independent of dbMaxRecords. The older records are deleted no 
matter how "full" the DB is. The delete frequency is determined by
pmDataSourceType::dbTableSizeCheckInterval. This is consistent with PM's
architecture.
Also dbMaxRecords is used for pmDataSourceType::tableFullPolicy=1 (i.e.
raise alarm). In other words it is used to determine whether the DB is
full for the purpose of raising alarm.
  pmDataSourceType::tableFullPolicy:
  What determines if "table is full", dbMaxRecords? If so, what 
  does option 0, delete old data, really do? How old does the 
  data have to be?
  How much is deleted? What if the data is not old enough for the
  retention time (e.g., is is not yet 24 hours old)?
The option 0 is based on the dataRetentionTime logic as explained in the
previous answer.