Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see MainView Middleware Monitor 9.2.

History, configuration, and other database objects

Other than the reference tables, there are tables and associated objects that store history data as it is collected, history data after it has been compressed, discovery, and journal data.

These tables and their indexes should have enough database cache memory allocated for their use to allow the hourly Performance and Availability history compression process to complete in a reasonable time (see the History compression details table in History compression) and support user queries, such as ad hoc reports that return data in a user-acceptable time frame.

As history and journal data are data that accumulate over time, capacity planning must be routinely performed. Keeping statistics current and the frequency and type of reorganizations are dependent upon the DMBS type.

Related topics

DB2-performance-and-maintenance-considerations

Oracle-performance-and-maintenance-recommendations

Database-performance-recommendations

Database-server-requirements

DB2-performance-and-maintenance-considerations

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*