Skip to main content
Solved

Set character encoding on Oracle writer


redgeographics
Celebrity
Forum|alt.badge.img+49

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)?

Best 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

View original
Did this help you find an answer to your question?

5 replies

ebygomm
Influencer
Forum|alt.badge.img+32
  • Influencer
  • Best Answer
  • December 3, 2020

"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


redgeographics
Celebrity
Forum|alt.badge.img+49
  • Author
  • Celebrity
  • December 3, 2020

Thanks!


ebygomm
Influencer
Forum|alt.badge.img+32
  • Influencer
  • December 3, 2020
redgeographics wrote:

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.


redgeographics
Celebrity
Forum|alt.badge.img+49
  • Author
  • Celebrity
  • December 3, 2020
ebygomm wrote:

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.

They're actually getting an error and it's aborting the write operation. unnamedThis 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.


ebygomm
Influencer
Forum|alt.badge.img+32
  • Influencer
  • December 3, 2020
ebygomm wrote:

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.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings