![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||
Solution Type Technical Instruction Sure Solution 2195415.1 : How To Address SPR Alarm 6145 - CoreDumpDetected and 7052 -
In this Document
Created from <SR 3-13475034991> Applies to:Oracle Communications Subscriber Data Management (SDM) - Version SDM 9.3 and laterInformation in this document applies to any platform. These Alarm events can also be seen in the sdmlogs. e.g. 7010 GoalThis document provides information on why alarm 6145 and 7052 were seen together.
#7052 - Critical - The maximum number of SPR subscribers authorized by the license is reached SolutionAlarms In the event you receive alarm 6145 and 7052, the following document should be referenced http://docs.oracle.com/cd/E48805_01/doc.93/910-6539-001_rev_f.pdf Alarm 6145 This alarm provides customer notice that a process has failed. The system may work abnormally. A new core dump file has been detected under /blue/var/debug. For investigation, this core dump should be attached to SR for investigation. Alarm 7052 This alarm is not in the Alarm Manual, however this alarm provides customer notice that the maximum number of SPR subscribers authorized by the license is reached. (i.e. Active subscribers license violation.) Analysis Upon analysis of the Core file and alarm information, in this case, the customer has exceeded the license capacity. After further customer investigation, it was found that the customer provisioning team mistakenly caused a spike in the provisioning rate which cause an "overload" condition which caused RAS Core dump. Recovery The DataAccess service has to be manually restarted if stopped. Once the provisioning rate was corrected the Alarms cleared and the system returned to a normal state.
Attachments This solution has no attachment |
||||||||||||||
|