Alarm Stored With alarm_type_id "-1" in SMF_ALARM_MESSAGE Table Despite It Is Defined in SMF_ALARM_DEFN Table
(Doc ID 2166568.1)
Last updated on AUGUST 01, 2016
Applies to:Oracle Communications Network Charging and Control - Version 5.0.2 and later
Information in this document applies to any platform.
On the Oracle Communications Network Charging and Control(OC-NCC) versions where the interim <patch 22507564> - Patch to fix 22392174 (No alarm defined in SMF_ALARM_DEFN for m3ua_if receiving Unrecognised Trans. ID) was installed, or versions including permanent fix for <bug 22392174> (the current plan is to be included in first release patch after OC-NCC 6.0.0) the following problem can be noticed:
Despite fix for <bug 22392174> has defined two alarm_type_id’s in SMF_ALARM_DEFN table for unrecognized transaction id’s received by m3ua interface, alarms of this type are stored in SMF_ALARM_MESSAGE table with “-1” (unknown alarm) value for alarm_type_id.
Here it is one example of how alarms for one day interval are stored on an environment where this problem is noticed:
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