Why does a Scheduled Job Require the 'Output folder path' (for job type = 'Process Input Files')?
(Doc ID 2682429.1)
Last updated on JUNE 19, 2020
Applies to:Oracle Warehouse Management Enterprise Edition Cloud Service - Version 19.4 and later
Information in this document applies to any platform.
A WMS Cloud environment was upgraded from 19C to 20B.
When running a scheduled job (job type = Process input files), the job failed.
Verified the following error in the log file:
Scheduled job J000000256 failed. Error: Output Directory <Client Code>_if does not exist!
This error was fixed by setting a value for 'Output folder path'.
Observed the following pattern when upgrading from version 9.0.0 to 19C to 20B. Support tested and verified the same.
For scheduled jobs where job type = Process input files:
9.0.0 - 'Output folder path' is required
19C - 'Output folder path' has to be blank.
20B - 'Output folder path' is again required
In 19C, it makes sense since no output is generated in this case.
Also, we have decommissioned the internal Oracle SFTP.
Why is 'Output folder path' required again in 20B?
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