Pipleline Engine Not Started in Clustered Database Environment (Doc ID 1119803.1)

Last updated on AUGUST 01, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 and later
Information in this document applies to any platform.
Checked for relevance on 25-Jan-2012.
Checked for relevance on 11-Sep-2013.
Checked for relevance on 1-Aug-2017.

Symptoms

How to resolve the following error occurred when starting the Pipeline:

Attempt to exit due to signal caught: SIGSEGV
Aborted

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