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

Last updated on OCTOBER 03, 2019

Applies to:

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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.