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 | |
Changing parameter thresholds
Using the PATROL Configuration Manager, you can change the thresholds for most of the PATROL for Oracle parameters. You should use caution, however, before changing thresholds. PATROL for Oracle ships with the parameters set at thresholds that are appropriate for those parameters in the average environment. You should make changes to the thresholds in one instance and then test the results in that instance before exporting those changes throughout your entire enterprise.
Do not change parameters with fixed thresholds
You cannot change parameters that have fixed thresholds. Some PATROL for Oracle consumer parameters have thresholds that are not on a sliding scale, but are fixed at a particular value because that value is directly connected to the KM. For example, all parameters that have a Boolean output are created to react only to a setting of 0 or 1.
The following table provides a list of the PATROL for Oracle parameters that have fixed thresholds that you should never modify. For complete descriptions and the default values for these parameters, see the BMC PATROL for Oracle Monitor types. The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.