May 4, 2010 at 11:53 am
Hi,
I`m trying to consume a webservice from an oracle procedure using the UTL_http, I build the request print and it`s OK but the request sent in the network is wrong the special characters are changed by escape chars Ó is \303\223 🙁
The request is in utf-8 encoding and the oracle settings are:
NLS_LANGUAGE =AMERICAN
NLS_CHARACTERSET= WE8MSWIN1252
Any idea how to resolve this problem?
Thanks in advance.
May 18, 2010 at 10:56 pm
is it possible to change the character-encoding of the data one receives
from an oracle-DB at runtime? i.e. is it possible to have connections to
two oracle-DBs in one perl-application where from one DB you want to
receive utf8-data and from the other iso-8859-1 data?
we were not able to do this.
we tried to do the following:
* set ORACLE_HOME, ORA_NLS33 to correct values
* set NLS_LANG to e.g. american_america.WE8ISO8859P1
* start the application and within that:
May 19, 2010 at 6:20 am
chico_rpereira (5/4/2010)
I`m trying to consume a webservice from an oracle procedure using the UTL_http, I build the request print and it`s OK but the request sent in the network is wrong the special characters are changed by escape chars Ó is \303\223 🙁The request is in utf-8 encoding and the oracle settings are:
NLS_LANGUAGE =AMERICAN
NLS_CHARACTERSET= WE8MSWIN1252
You have to set appropriate NLS_LANG at client side.
In the Oracle world one thing is database encoding and other very different thing is client "localization" which is handled by NLS_LANG. I know, this is confusing and certainly not trivial - please check here for details http://www.oracle.com/technology/tech/globalization/htdocs/nls_lang%20faq.htm#_Toc110410543
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.July 27, 2010 at 11:39 pm
I have an application that is unable to deal with utf-8 during data import from an external database. So I figured I could do a workaround by importing from a view that kind of converts encoding on the external database instead.
August 2, 2010 at 3:39 pm
sunloyhimmon (7/27/2010)
So I figured I could do a workaround by importing from a view that kind of converts encoding on the external database instead.
:blink: This is very confusing. There is not such a thing as importing from a view in the Oracle world - would you mind in elaborating a little more?
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply