My Oracle Support Banner

Import Mapping Rule Failed with Error FileSource could not be Located (Doc ID 457397.1)

Last updated on MARCH 26, 2019

Applies to:

Oracle Enterprise Performance Foundation - Version 11.5.10.2 to 11.5.10.2 [Release 11.5]
Information in this document applies to any platform.
FEM

Symptoms

When attempting to migrate a mapping rule the following error occurs:

ERROR
Temporary driver xml file for restart is saved to AZI193172021.xml after each api call.
Problem while downloading shapshot to local File System.
** ERROR **: FileSource 3 could not be located.
** ERROR **: FileSource 3 could not be located.
** ERROR **: file could not be located: driver.xml

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Migrate a rule successfully but failed on import.
2. Create a new condition, and export import into the same environment and it failed with the same
error.

Cause

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
Symptoms
Cause
Solution
References


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