TAPRating Pipeline Becomes Unusable Following A ERR_INPUT_FILE_NOT_MOVED Error
(Doc ID 2052075.1)
Last updated on MARCH 11, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
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.
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