Asking on behalf of a client: they're writing to Oracle and getting an error regarding an UTF-8 string that can't be converted to Windows-1252. I can't seem to find a way to set the encoding on the Oracle writer, is this handled in the database definition itself (i.e. outside of FME)?
Solved
Set character encoding on Oracle writer
+63Best answer by ebygomm
"I can't seem to find a way to set the encoding on the Oracle writer, is this handled in the database definition itself (i.e. outside of FME)?"
Yes, it's set at the DB level.
You can use nvarchar columns if you want to put utf-8 strings into a DB set to windows-1252
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.
+51- Evangelist
- Best Answer
"I can't seem to find a way to set the encoding on the Oracle writer, is this handled in the database definition itself (i.e. outside of FME)?"
Yes, it's set at the DB level.
You can use nvarchar columns if you want to put utf-8 strings into a DB set to windows-1252
+51- Evangelist
Thanks!
Are they actually getting an error? I'd be interested if so, as in my experience the non allowed characters just get quietly converted to something else.
+63Are they actually getting an error? I'd be interested if so, as in my experience the non allowed characters just get quietly converted to something else.
They're actually getting an error and it's aborting the write operation. 
This is all I have unfortunately, and I've had to edit out the actual string because it's a person's name (erring on the side of caution perhaps, better safe than sorry). Either way, I can't quite make out what that character is... The name appears to be Eastern European (Polish? Czech?)
Customer is in the process of migrating from FME 2017 to 2020, I assume that this error has nothing to do with that and it's just pure coincidence that they're running in to that character for the first time right now.
+51- Evangelist
Are they actually getting an error? I'd be interested if so, as in my experience the non allowed characters just get quietly converted to something else.
Interesting to know. I don't know whether it could be down to a database setting or something new in 2020. I've not played with Oracle databases and 2020 yet.
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.