Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2195415.1
Update Date:2016-11-04
Keywords:

Solution Type  Technical Instruction Sure

Solution  2195415.1 :   How To Address SPR Alarm 6145 - CoreDumpDetected and 7052 -  


Related Items
  • Oracle Communications Subscriber Data Management (SDM)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Broadband Network Solutions>SN-SND: Tekelec SDM
  •  




In this Document
Goal
Solution


Created from <SR 3-13475034991>

Applies to:

Oracle Communications Subscriber Data Management (SDM) - Version SDM 9.3 and later
Information in this document applies to any platform.
These Alarm events can also be seen in the sdmlogs.
e.g.


Oamp
7010
OampManager
ALARM_CRITICAL
LOG
Active subscribers license violation. (clear-0)
2016-10-11T1:59:59Z
OampManagerLicenseHandler.cpp
186
105
1

Goal

This document provides information on why alarm 6145 and 7052 were seen together.


#6145 - Major - Core dump for process [ras] has been detected on slot [1] of shelf [1]

#7052 - Critical - The maximum number of SPR subscribers authorized by the license is reached
 

Solution

Alarms

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
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback