3.19.136 70353 – Routing DB Inconsistency Exists
- Alarm Group:
- vSTP
- Description:
- Raised when routing database synchronization is disrupted or the update log overruns; the product performs an audit of the impacted sub-resource (or all sub-resources after an overrun).
- Severity:
- Critical
- Instance:
- Table Name
- HA Score:
- Normal
- Auto Clear Seconds:
- 0 (zero)
- Throttle (Seconds)
- 86400
- OID:
- vSTPVstpRoutingDbInconsistencyExistsNotify
- Recovery:
-
- Record the alarm instance (table name), timestamp, affected VSTP-MP(s), and any concurrent database, synchronization, or platform alarms before making changes.
- Check for a recent bulk configuration change, replication/synchronization disruption, or update-log overrun affecting the named routing table.
- Allow the product audit to complete and confirm a clear event.
- Do not make parallel routing-database changes while the audit is running.
- In case alarms still exists and configuration table impacted is known then try deleting the specific configuration and then resetting VSTP Process on impacted MP (pm.set off vstp , pm.set on vstp) and then re-add the configuration.
- If the alarm remains active or returns after the audit, preserve relevant logs and engage My Oracle Support; use the approved database-recovery procedure rather than manual database repair.
- It is recommended to contact My Oracle Support if further assistance is needed.