My Oracle Support Banner

SARM Crashes Immediately After Startup (Doc ID 2353157.1)

Last updated on FEBRUARY 15, 2019

Applies to:

Oracle Communications ASAP - Version 7.0.1 to 7.0.2 [Release 7.0.0]
Information in this document applies to any platform.

Symptoms

On ASAP 7.0.1 version:

SARM server  is repeatedly crashing on startup.

The following errors were found in the <SARM_SERVER_NAME>.diag file:-

1st Error :
3 : reason = Error: Work Order(<WO_ID>) Found with Incomplete Loading Status.
Error - errcode[0]
Error: SSP_save_rtn_parm Failed

2nd Error :
>> 101448.720:27:SHUT:System Event :3326:sarm/sarm/sarm/provision.c
Application <SARM_SERVER_NAME> Terminating Due to SYS_TERM Event
Error: SSP_save_rtn_parm Failed.

As per the documentation found for Bug 13035719 on MOS, this issue can occur due to an inconsistent order in ASAP Database.

We think WO_ID "<WORK_ORDER-xxx>" might have been the "culprit" order, as we've never observed the 1st error before.

Steps taken till now to resolve this issue:-

1. Datastore of Admin Server (Weblogic) cleaned
2. WL_Store table truncated
3. For <WO_ID>, WO_STAT updated to 104 in TBL_WRK_ORD
4. <WO_ID> deleted from TBL_SRQ
5. <WO_ID> deleted from TBL_SRQ_LOG
6. <WO_ID> deleted from TBL_WRK_ORD

1st Error has now stopped occurring but 2nd Error still observed in logs.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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