UC4Vers2-MIB :: databaseError

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsUC4Vers2-MIBdatabaseError

databaseError

Module: UC4Vers2-MIB

OID (symbolic): UC4Vers2-MIB::databaseError

OID (numeric): 3536

Node type: NOTIFICATION-TYPE

Description: Serious error when accessing the UC4 database. Access no longer possible.

Examples

Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):

snmptrap -v2c -c public <manager> '' UC4Vers2-MIB::databaseError
snmptrap -v2c -c public <manager> '' 3536

Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):

snmptrapd -f -Lo -c /dev/null authCommunity log public

Example snmptrapd log entry:

zoo11-linux.zoo [UDP: [192.168.30.111]:57217->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (108984193) 12 days, 14:44:01.93
  SNMPv2-MIB::snmpTrapOID.0 = OID: UC4Vers2-MIB::databaseError

Start monitoring UC4 (Automic/Broadcom) workload-automation platforms (agent uptime/connection-count status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the UC4Vers2-MIB::databaseError OID value, configure state conditions and alerts, and monitor any UC4 (Automic/Broadcom) workload-automation platforms (agent uptime/connection-count status) from a single console.