My Oracle Support Banner

Critical Fatal Error And Core Dump Signal Causing SARM To Crash (Doc ID 1236424.1)

Last updated on AUGUST 20, 2018

Applies to:

Oracle Communications ASAP - Version 4.6.3 and later
Information in this document applies to any platform.


SARM terminates with following error messages in diag file:

----------------------- 082836.402:3:PROG:Fatal Open Server Error :1361:main.c
SARM_PRD Server: Fatal Server Error:
Open Server Error # [16151] Severity [20] State [0] Error Text [Thread '50' has overflowed or corrupted its stack -- aborting]

Jul 27 08:29:42 2010: 16331 - Recursive Calls to srv__seterr() in spid: 3. Thread terminated.
Jul 27 08:29:42 2010: ASAP System Event: SYS_ERR
SARM_PRD(9613): Core Dump Signal 10 Received in Thread 2
Jul 27 08:30:45 2010: SARM_PRD: Msg 0 Severity 0 State 1 Server 'CTRL_PRD' Proc '' @ 0

SARM server crashed and BEA Weblogic stopped sending the orders to ASAP.>>




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.