EMPIRE-ORAMOD :: oramodMetricsCHR

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › EMPIRE-ORAMOD › oramodMetricsCHR

oramodMetricsCHR

Module: EMPIRE-ORAMOD

OID (symbolic): EMPIRE-ORAMOD::oramodMetricsCHR

OID (numeric): 1.3.6.1.4.1.546.16.4.11.2.1.1.5

Node type: OBJECT-TYPE

Type: Gauge

Access: read-only

Description: Cache Hit Ratio scaled by 100. Measures the effectiveness of the hits against the buffer cache. Whenever Oracle reads data from disk, it places that data into the buffer cache. Data is aged out of the buffer cache using a least recently used algorithm. Oracle looks in the buffer cache first for data requests. If the data is not there, Oracle searches the disk based data files that comprise the database. On most production systems, Oracle should not have to resort to disk reads more than 20% of the time. So, if the buffer cache hit ratio is less than 80%, you should consider increasing the database buffer cache in the System Global Area. This can be done by increasing the value for DBBLOCKBUFFER in the initialization parameter file.

What is oramodMetricsCHR?

The buffer Cache Hit Ratio, scaled by 100, measuring how often Oracle finds a requested block already in the buffer cache instead of reading from disk. The description gives the operational rule directly: production systems should keep this above 80%, and a lower ratio means increasing DB_BLOCK_BUFFERS (oramodDbCfgDBBLKBUFF) in the init file.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.546.16.4.11.2.1.1.5
snmpwalk -v2c -c public <target> EMPIRE-ORAMOD::oramodMetricsCHR

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.546.16.4.11.2.1.1.5.1
snmpget -v2c -c public <target> EMPIRE-ORAMOD::oramodMetricsCHR.1

Start monitoring Server running Oracle database, monitored by CA/Empire SystemEDGE agent with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the EMPIRE-ORAMOD::oramodMetricsCHR OID value, configure state conditions and alerts, and monitor any Server running Oracle database, monitored by CA/Empire SystemEDGE agent from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.546empireCAHYPERV-AIM-MIB
1.3.6.1.4.1.546.16applicationsCAHYPERV-AIM-MIB
Numeric OIDNameModule
1.3.6.1.4.1.546.16.4oracledbEMPIRE-ORAMOD
1.3.6.1.4.1.546.16.4.11oramodPerfEMPIRE-ORAMOD
1.3.6.1.4.1.546.16.4.11.2oramodMetricsEMPIRE-ORAMOD
1.3.6.1.4.1.546.16.4.11.2.1oramodMetricsTableEMPIRE-ORAMOD
1.3.6.1.4.1.546.16.4.11.2.1.1oramodMetricsEntryEMPIRE-ORAMOD
1.3.6.1.4.1.546.16.4.11.2.1.1.5oramodMetricsCHREMPIRE-ORAMOD