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 | |
Understanding how the ConfigUpdate parameter operates
When one or both of the rules are applied to a rule set, the ConfigUpdate Parameter performs as follows:
- The ConfigUpdate parameter checks (every 10 minutes, by default) for the POKKMConfigUpdated and POKKMConfigInstanceRemoved rules.
- Upon detection of one or both of these rules, the ConfigUpdate parameter changes from a default value of 0 to one of the following values:
- If an update request is applied, the ConfigUpdate parameter sets a value of 1 and goes into a warning state to let you know that a change was sent through the PATROL Configuration Manager.
- If an instance removal request is applied, the ConfigUpdate parameter sets a value of 2 and goes into a warning state to let you know that an instance removal request was sent through the PATROL Configuration Manager.
If an update request fails the validation tests performed by PATROL for Oracle, the parameter goes into an alarm state and it sets a value of 3.
- Upon detection of the POKKMConfigUpdated or POKKMConfigInstanceRemoved rule, the ConfigUpdate parameter takes the following actions:
- Forces the Oracle KM to deactivate and reactivate the monitoring of each configured and actively monitored instance, even instances that were not modified. This causes the instance icons to disappear briefly and then reappear.
- Removes the POKKMConfigUpdated and POKKMConfigInstanceRemoved rules or variables from the instance.
After completion of 1 polling cycle (by default, 10 minutes), the ConfigUpdate parameter returns to a value of 0.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*