My Oracle Support Banner

DapIF Core Dump (Doc ID 2927597.1)

Last updated on FEBRUARY 17, 2023

Applies to:

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

Symptoms

In Oracle Communications Network Charging and Control (NCC) and Oracle Communications Charging and Control (OC3C) Data Access Pack (DAP) provides the capability to send requests to external Application Service Providers (ASP) and optionally receive responses for further processing by the IN platform.

The main process for DAP is dapIF and it is a SLEE interface that sends and receives XML requests to external ASPs. It listens for SLEE requests and messages from ASPs. It can trigger a PI command from a control plan using the DAP Send Request feature node when communicating with an ASP using the PIXML protocol.

 There is a known issue where the DAP process is crashing while in a loopback connection.


From the dapif logs the behavior can be identified as following:

 The process is crashing from a SIGABRT signal sent from the watchdog.

 

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
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.