Plugin info

name: ora-sql-patches

Collects Oracle database SQL patch information

Summary

Collects the last SQL patches that have been applied to this instance

Prerequisites

• Linux
  • User Groups: oinstall, dba
• Windows
  • Group Memeberships: ORA_HOMENAME_DBA

Important, the connection to the database/ASM takes place over BEQ. This means that the process resource limits for myrmex-ad must match those set for the oracle database/ASM processes. Set these limits in the systemd unit file for myrmex-ad and then reload and restart the myrmex-ad service. Refer to https://www.man7.org/linux/man-pages/man5/systemd.exec.5.html#PROCESS_PROPERTIES (opens new window) for the process limit directives and their ulimit equivalents.

Events

• myrmex/oracle/db/patch/sid/patch/descr/sql-patch set to 1 when a patch has been applied
  • Dimensions
    • sid: the SID the patch was applied to
    • patch: the ID of the patch applied
    • desce: the description for the path
• myrmex/plugins/error/plugin/msg set to error message on plugin execution failure
  • Dimensions
    • plugin the name of the plugin that failed

Configuration

Plugin is configured with a yaml file:

• source: the value that will appear as the source of metrics generated by this configuration. defaults to plugin hostname
• oracle_home: path to database instance ORACLE_HOME
• timeout: execution timeout in duration format (opens new window). Defaults to 2m
• sid: the SID to connect to
• connect_as: (optional) one of sysdba, sysoper, sysasm. Default is sysdba

Example Configuration

# path to oracle_home for this instance
oracle_home: /u01/app/oracle/product/12.2.0.1/dbhome_1
# sid to connect to
sid: suwpdb1

Validate Configuration

ora-sql-patches --run-conf /path/to/config/file.yaml --validate

Testing

Run the plugin from the command line and get any emmited events on stdout

ora-sql-patches --run-conf /path/to/config/file.yaml

List events emmited by this plugin

ora-sql-patches --events