Which workflow runs this query? Opslogix query tags and database load
Every Opslogix query starts with a comment tag. Use this article to find which SCOM workflow runs a query on your Oracle database, and how to reduce its load.
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
Every query that the Oracle Management Pack runs on your database starts with a comment tag, for example /* Opslogix Datafile details library */. When your DBA sees an Opslogix query in v$sql, AWR or Oracle Enterprise Manager, the tag tells you which SCOM workflow runs it. The monitoring sessions also identify themselves in v$session with module name OPSLOGIX.IMP.ORACLE.
Query tags and the workflows that use them
| Query tag | Used by | Default interval |
|---|---|---|
| Opslogix SysStat library | All instance performance monitors and rules: hit ratios, sessions, process and session utilization, FRA usage, invalid objects and indexes, memory, sorts, commits, rollbacks, redo log switches, long-running operations, data file I/O time | 300 s |
| Opslogix tablespace usages V6 -- SYSTEM safe version | Table Space Used %, Table Space Free MBs (disabled), Table Space Used/Free (MB) and Used (Pct) rules, average data file I/O read and write time | 300 s |
| Opslogix tablespace usages bypassing DBA_TABLESPACE_USAGE_METRICS because of 16 GB size limit | Table Space Used MBs (disabled by default) | 300 s |
| Opslogix temp tablespaces usage library | Temp Table Space Usage Pct, Table Space Temp Used/Free (MB) and Used (Pct) rules | 300 s |
| Opslogix Datafile details library | Data file status, Data file online status | 300 s |
| Opslogix RMAN Last Full, Last Incremental, datafile Full, Controlfile, SPFILE, BACKUPSET Last, ArchiveBackup Last | The 7 backup monitors (one shared query) | 3600 s |
| Opslogix Oracle Discovery ... (Instance Properties, UpSince, SGA Size, Memory Count, CPU Count, Instance Count, Database size Logical, Backup, ControlFile, Redo Group, Datafile details) | Discoveries of instance properties, tablespaces, data files, redo logs, control files and backups | 28800 s (8 hours) |
| Opslogix Oracle Discovery Database size physical | Instance attribute discovery - physical database size | 86400 s (24 hours) |
| Opslogix Data Guard module - ... | Data Guard monitors (apply lag, transport lag, apply finish time, archive gap, standby data files, recovery processes, archive destinations, standby redo logs) and discoveries | 300 s (lag rules 900 s) |
| Opslogix Log Reader module - check new log messages | Alert Log Messages Monitoring (disabled by default) | 120 s |
| OPSLOGIX TOP 10 SQL CPU USAGE | Task "Query TOP 10 Querys By CPU" | on demand |
For all workflows and their settings, see Oracle Management Pack Monitors, Discoveries and Rules.
Reducing the load of a query
- Many monitors and rules share one query (SCOM cook-down): the query runs once and its result is used by all of them. For example, all 7 backup monitors use one RMAN query, and most instance monitors and rules use the SysStat query.
- To run a query less often, override IntervalSeconds on the workflows that use it. Give all workflows that share the query the same new interval; if the intervals differ, SCOM runs the query separately for each of them, which increases the load.
- To stop a query for one instance, disable the workflows that use it for that instance with an override.