This is almost certainly an encoding problem of some kind. Please send us your workspace and a log file and we'll take a look. For fastest response please use https://support.safe.com/knowledgeSubmitCase

Note -- we'll be looking to see what release of FME and what exact reader was used.

Also -- in the meantime, do try reading the data directly using an Oracle reader. You won't be able to get geometry with this technique, and it might be hard to find the table, but if you could read the attribute data via one of our Oracle readers and output that to a non-spatial geodatabase, that would tell us if the Oracle system is configured correctly or not.

Thank you for your response.

I am using [Edition: FME Oracle Edition] [ Version: FME 2010 (20100211- Build 6206- Win32)].

I emailed https://support.safe.com/knowledgeSubmitCase .

Thanks for this info. I'm quite certain FME 2010 did not have nearly the level of support for encodings as we do today in FME. If you are able to, try FME 2016.0 beta (or FME 2015 release) from http://www.safe.com/downloads . In the meantime our support team will check but I expect this issue is long ago resolved.