How to change thresholds and intervals with overrides
Change the default thresholds, intervals and enabled state of the Oracle monitors, rules and discoveries with standard SCOM overrides.
Applies to: Opslogix Oracle Management Pack (all versions)
Last updated: October 2026 · Latest version: 26.4.4517.0
See also: Upgrade guide for 26.4.4517.0 · Version support · Release notes
All thresholds, intervals and the enabled state of the Oracle monitors, rules and discoveries can be changed with standard SCOM overrides. This article shows the most common changes. For all default values, see Oracle Management Pack Monitors, Discoveries and Rules.
Where to save overrides
Save your overrides in a separate, unsealed management pack. The release includes an empty one for this: "OpsLogix.IMP.Oracle.Overrides". Never save overrides in the Default Management Pack.
How to create an override
- In the Operations Manager console, go to Authoring > Monitors (or Rules, or Object Discoveries).
- Use "Change Scope" to select the Oracle class, for example "Instance", "Table Space", "Table Space Temp" or "Oracle Backup" (from the Opslogix Oracle management pack), and find the monitor or rule.
- Right-click it, choose Overrides > Override the Monitor (or Rule), and select whether the override applies to all objects of the class, a group or one specific object.
- Select the parameter, enter the new value, choose the override management pack and click OK.
Common overrides
| What you want to change | Monitor / rule | Parameter | Default |
|---|---|---|---|
| Tablespace usage thresholds | Table Space Used % | HealthyThreshold (warning above) / CriticalThreshold | 85 / 95 |
| Temp tablespace usage thresholds | Temp Table Space Usage Pct | HealthyThreshold / CriticalThreshold | 85 / 95 |
| Maximum backup age (hours) | Full DB Backup, Incremental DB Backup and the other backup monitors | HealthyThreshold / CriticalThreshold | 25 / 99 |
| Flash Recovery Area usage | % FRA usage Monitor | HealthyThreshold / CriticalThreshold | 75 / 85 |
| Session and process utilization | % Instance Session Utilization / % Instance Process Utilization | HealthyThreshold / CriticalThreshold | 90 / 98 |
| Data Guard apply lag (seconds) | DataGuard Monitor Apply Lag | Threshold | 30 |
| Data Guard transport lag (seconds) | DataGuard Monitor Transport Lag | Threshold | 2 |
| Connection retries before alert | Instance connection | NumberOfRetrys | 2 |
| How often a monitor runs | any Oracle monitor | IntervalSeconds | see the overview article |
| Tablespace free space in MB instead of % | Table Space Free MBs (disabled by default) | Enabled = True, HealthyThreshold (warning below) / CriticalThreshold | 50 / 5 MB |
| Alert log monitoring | Alert Log Messages Monitoring (disabled by default) | Enabled = True, QueryForInLog | see "How to enable Oracle alert log monitoring" |
For monitors where a low value is healthy (usage, backup age), HealthyThreshold is the value above which the monitor turns Warning, and CriticalThreshold the value at or above which it turns Critical. For hit-ratio monitors and Table Space Free MBs, where a high value is healthy, it works the other way round. Data Guard monitors turn Critical at or above their Threshold.
Discovery intervals can be changed in the same way: override IntervalSeconds of the discovery (default 28800 seconds, 8 hours).