Monitor SNMP Messages Sent Have 'wrong' OID.

(Doc ID 1490340.1)

Last updated on JULY 17, 2017

Applies to:

Management Pack for Oracle GoldenGate - Version and later
Information in this document applies to any platform.


 We are using OGG Monitor v11. configured with SNMP alerts to trigger when certain alert criteria is triggered.  However, the SNMP alerts don't reflect the identifier in the MIP. SNMP MIB has identifier

os> cd <monitor install>/cfg
os> cat GoldenGate-Monitor-mib.mib

 OracleGoldenGateMonitorMibModule MODULE-IDENTITY
     LAST-UPDATED "201010220000Z"
          "postal:   Oracle corp.
                     500 Oracle Parkway
                     Redwood Shores CA  94065
         "MIB objects module for Oracle GoldenGate Monitor Server"
     ::= { enterprises 111 1 }

         STATUS current
                 "Oracle GoldenGate Monitor server side objects root."
         ::= { enterprises 111 17 }

But in SNMP traps, the identifiers for each message are based on entries in <Monitor install>/cfg/SNMPJMXMapping.xml:

<OID1. name="alertName"
<OID1. name="alertTime"
<OID1. name="alertObjectName"
<OID1. name="alertSeverity"
<OID1. name="alertMessage"

These appear in each SNMP trap as:

 #0 enterprises.18657. sfo310000_message
 #1 enterprises.18657. 08282012111721901
 #2 enterprises.18657. EX_AA
 #3 enterprises.18657. 1
 #4 enterprises.18657. The alert was triggered because:
 Lag = 4.540 sec.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms