Db2 Tables

ERO uses three Db2 tables to track release components, and it uses eleven Db2 tables to track relationships for Release Audit.

Db2 Space Calculations

Serena has a spreadsheet that helps you estimate the space you need for ERO Db2 tables. Contact Serena Customer Support and ask for the ERO Option Database DASD Space Estimator.

Performance Considerations

When you audit a release area, all data from the previous audit for that area is deleted from the release audit Db2 tables, and then data for the new audit is inserted. A release audit may delete and insert hundreds of thousands of rows for a large release.

All the Db2 tables are indexed for performance. However, it is quite usual for Db2 to choose not to use the indexes if it does not have up-to-date information on the data distribution in the tables. To provide this information and to update catalog statistics, your DBA should periodically monitor the Db2 catalog statistics for the ERO Db2 tablespaces, tables, and indexes and execute the Db2 RUNSTATS utility on a regular, scheduled basis against these tables.

It is particularly important that you execute RUNSTATS after the initial loading of the tables. If Db2 chooses not to use the indexes to access the tables, performance may be unacceptable.

Db2 Table Recovery

The ChangeMan ZMF ERO Db2 tables cannot be rebuilt from information in ChangeMan ZMF libraries. If ERO Db2 tables are lost or corrupted, use standard Db2 recovery techniques to restore the data.

Schedule regular image copies of the ERO tablespaces. Implement the same kind of recovery procedures for ChangeMan ZMF ERO Db2 tables that you use for other Db2 application tables.

Db2 Active Logs

ERO will generate additional Db2 activity which will result in additional logging to the active logs. The additional logging is dependent on the size of your releases and the frequency that you perform ERO tasks such as check-in, retrieve, and audit. Monitor this additional activity and adjust the size of your logs to fit your logging strategy.