MFT Source Error “no Matching Transfer Found With Matching Content Type"
(Doc ID 2255329.1)
Last updated on AUGUST 09, 2018
Applies to:Oracle Managed File Transfer - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Runtime issue in MFT when files with static names are processed multiple times.
MFT stores the files internally under a specific folder that it creates dynamically while processing them, it keeps those files there for some time (few days may be) and purges them eventually. When the same file is processed again by MFT it keeps it in a different internal folder but sometimes MFT is trying to keep it in same internal folder where the previously processed file is still sitting there in which case MFT is renaming the file to a different name to avoid conflict. This is causing the issue as that newly created file doesn’t match the content filter configured in any MFT transfer.
This means that even when the source system sends a valid file, the MFT transfer fails with the "no matching transfer found" due to its internal directory and file naming logic.
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