Pipeline Stopped After There Was a DB Node Failure in RAC

(Doc ID 2054051.1)

Last updated on JULY 25, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 7.5.0.0.0 version, Pipeline Manager

ACTUAL BEHAVIOR
---------------------
The Pipelines stopped after one of the Node in RAC stopped.

EXPECTED BEHAVIOR
-----------------------
When RAC node failed, all processes should fail over to the standby node.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
A) DB NODE A failed

B) Pipeline stopped

C) Passed a semaphore
     ifw.DataPool.Login.Module.Reconnect {}
     ifw.DataPool.LoginInfranet.Module.Reconnect {}
     ifw.DataPool.LoginQueue.Module.Reconnect {}

D) Passed a semaphore to make all the Pipelines active
     ifw.Pipelines.PRE_PROCESS_TEL.Active = True
     ifw.Pipelines.PRE_PROCESS_DATA.Active = True
     ifw.Pipelines.PRE_PROCESS_SMSMMS.Active = True
     ifw.Pipelines.RATING_TEL.Active = True
     ifw.Pipelines.RATING_SMSMMS.Active = True
     ifw.Pipelines.RATING_DATA.Active = True

Process remained stuck!



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