Overriding NLS_LANG for ODBC

chulett · Post by **chulett** » Wed Jun 21, 2006 4:23 pm

We're working through the trials and tribulations of consuming UTF8 XML data in a MSWIN1252 world. Have no problem with jobs that leverage the OCI stages to connect to Oracle, that was a simple matter of overriding the NLS_LANG and LC_CTYPE environment variables in any jobs that source the XML. Conversion takes place great and the data survives the trip from XML to Oracle.

Now we have some jobs that use ODBC to connect to Oracle and that same 'fix' isn't fixing anything - the data is corrupted on the way in. Does anyone know how I could override these two environment variables for ODBC?

I don't see anything in the docs that makes it look like I could include something in the .odbc.ini file for this. We are currently using the Wire Driver... and I'm wondering if I switch to using the 'thick' driver would it then recognize the new NLS_LANG and LC_CTYPE settings I'd added as job parameters like the OCI stages do?

I'll give this a shot, but wondering if anyone has any words of wisdom to share on this topic. Thanks!

chulett · Post by **chulett** » Wed Jun 21, 2006 5:23 pm

FYI... switching to the thick drivers didn't change the job's behaviour. :cry:

chulett · Post by **chulett** » Tue Jun 27, 2006 2:50 pm

For what it's worth, Dancing with Support right now. I'm told that the thick drivers should have worked and respected the override of the environment variables, however they did not. Or perhaps something else is going on.

Hasn't anyone else had to worry about something like this before?