Disk space requirements for historical data tables

You can calculate the amount of DASD required to support the persistent data store for storing historical data in Tivoli® Data Warehouse.

This section provides the information you will need to determine space allocations in the persistent data store for each monitoring agent. Therefore, the disk space requirements in the tables in this section are for short-term history, which is stored on z/OS® systems in the OMEGAMON® XE persistent data store.

Network size and the type of network resources managed vary widely between enterprises. The amount and type of historical data that you choose to retain will greatly affect the amount of storage required. Wide differences between networks make it difficult to provide one size for the persistent data store that reflects the needs of most enterprises.

The default storage allocation is efficient for a very small network. Most users will need to allocate additional storage and data sets. Increase the default number of data sets from 3 to 5 or more. Increasing the number of data sets, using the Group Count parameter in the Control Program, is explained in the following section under Allocating additional storage and data sets.

This appendix provides you with the following information:
  • Alternative methods for determining storage
  • Effective allocation of additional storage and data sets (if needed)
  • A list of attribute tables supported by short-term history
  • Record size for each attribute table
  • Worksheets to help you estimate the storage required
Note: If you are upgrading from V4.1 or 4.2 and did this exercise for one of these releases, it is recommended that you do it again for V5.1. The upgraded versions contain new attribute tables, and new attributes are included in existing tables.