I'm having an issue using the schema mapper to remap the schema of a Oracle 11g database and write thte data into a file geodatabase using FME 2017.0.0.0 Build 17236. I have succesfully mapped the SQL Server version of the same schema and data with no problems. If I set up the Oracle mapping I can get it to map successfully but it will fail to output to the geodatabase and will automatically output to an .ffs file. I can then open up the .ffs file and everything is mapped properly, just not outputting to the right location. Any advice regarding this issue would be much appreciated.
Question
Issue mapping Oracle 11g database using schema mapper to a geodatabase
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+2Assume the Workspace parameter Writer Redirect isn't set to FFS File?
Attach the log file here if you can.
+26- Contributor
Have you used the right Oracle reader (Spatial or Non-spatial)?
Just another thing to check.
oracle-spatial2filegdb2.txt - log file
I'm not getting any errors it doesnt look like. Just a bunch of warnings (blue text) telling my that the "FileGDB Writer: The 'FID_CIRCUIT' (**my attribute) could not be written. The containing feature has been dropped."
+2The attribute FID_CIRCUIT is a string in the data. Is it defined as a Text on the GDB Feature Type, if not that can cause issue similar to that in the log.
+26- Contributor
I have reported a bug in the File geodatabase writer (API) that will be fixed in the new release. It concerns a wrong mapping in the code for certain datatypes.
Safe Software is testing the bug fix and hopes to release this early April.
Could well be the same (or related) issue you are running into.