Missing Alarm Definitions from SMF_ALARM_DEFN Table Causes Big Number of Alarms Being Stored With "-1" ALARM_TYPE_ID in SMF_ALARM_MESSAGE Table
(Doc ID 2129831.1)
Last updated on MARCH 07, 2019
Applies to:Oracle Communications Network Charging and Control - Version 5.0.2 and later
Information in this document applies to any platform.
There are 2 types of errors in m3ua_if log which are inserted with "-1" ALARM_TYPE_ID in SMF_ALARM_MESSAGE table:
There are cases when this error is considered "normal", as it is generated in situation when one of the call parties is loosing the signal.
The problem is that having a big number of these alarms stored as "-1" in the SMF_ALARM_MESSAGE table will make impossible filtering these type of alarms in order not to miss some other important alarms.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document