Re: Character set blues...

Jeremy wrote:
> Environment: Oracle 9i / Solaris 8 / Oracle http server with mod_plsql
>
>
> Can someone enlighten me please as to what is going on in the scenario
> below?
>
> We are being sent an XML document via an HTTP post - the XML doc content
> is sent as the "value" for the field "xml_doc".
>
> The POST is being sent via the Oracle http server into mod_plsql and
> then into a procedure defined thus:
>
> procedure job
> (xml_doc in clob default null)
> is
> ...
> ...
>
>
> All is OK so far. Problem is that in the XML doc there are sometimes
> some accented characters such as "ori๋nterend" (hope that came out!).
>
> Whe we look into the CLOB we don't see these - instead we see e.g.
> "ori?nterend". So it appears that there is some character set
> translation being performed *before* we get to see the data.... any
> ideas why this might be?
>
> What further confuses things is that from within our web app (same
> technology) I can type "ori๋nterend" into a field and it is saved and
> redisplayed in the correct format.
>
> So I am mightily puzzled. Any clues as to what might be going on and how
> to work around it?
>
>

*How* do you look inside your clob? Just an hint: could it be your *tool* to inspect your clob does not recognize the "๋" in ori๋nterend and displays a question mark?

The http post is in what character set?
The NLS_LANG environment variable of the client, that picks it (the XML message) up, has what setting? Your database uses what settings as characterset? The tool you use, uses what for NLS_LANG?

Another hint: use the dump() function

-- 
Regards,
Frank van Bortel