Advanced Control Services (ACS) reports "ERROR: Fatal Engine Error" in slee_acs Log (Doc ID 1274308.1)

Last updated on JULY 24, 2017

Applies to:

Oracle Communications Network Charging and Control - Version 2.4.0 and later
Information in this document applies to any platform.

Symptoms

All events which trigger to slee_acs running on the Service Logic Controller (SLC) will - if configured - always produce ACS EDRs (Event Data Records).

Likely symptoms include (but are not limited to):

  1. Fatal ACS Engine Errors - Fatal errors can happen during call processing and will result in no ACS EDR being produced irrespective of configuration.  They are an indication that a call within ACS has ended in an unexpected manner.
  2. No ACS EDRs - Fatal ACS engine errors will always result in no ACS EDR being written for the failed call.  This is less obvious than the errors in the slee_acs log.
  3. Incomplete Call Flows - Depending on where in the call flow the error occurs, signalling anomalies may also occur.
  4. In Open Services Development (OSD) versions 1.0.0.1 and earlier, osdInterface may core
It is strongly recommended that ACS Call Dumps are enabled whenever Fatal Engine Errors are present to have the Call Context information logged for only the failed calls.  Further information on how to enable ACS Call Dumps can be found in the ACS Technical Guide.  Details on how to download the Technical Documentation can be found here.


This article will discuss possible circumstances which can cause these fatal errors and how to resolve them.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms