TAPRating Pipeline Becomes Unusable Following A ERR_INPUT_FILE_NOT_MOVED Error (Doc ID 2052075.1)

Last updated on JANUARY 05, 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.

Goal

Scenario:
------------
In production environment the TAPRating Pipeline sometimes becomes unusable following a ERR_INPUT_FILE_NOT_MOVED error:

The recurrence is once in every couple weeks. In this case it’s only the TAPRating pipeline that became unusable but Customer have to restart the entire ifw process to resume operations in the Production.

Qn: How to avoid these errors?
 

Note: This issue is occurring only in TAPRating pipeline but not with other pipelines.

Solution

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