01-12-2004 07:21 AM
I need to change NLS_LANG (Oracle Parameter) for HP Service Desk.
I have to have the same value of NLS_LANG at both sides - in database
and in Oracle client software.
It's necessary for properly display of non-english text.
Service Desk doesn't use the value of current Oracle client NLS_LANG and
I'm not able to find where Service Desk saves value for NLS_LANG.
May be Service Desk uses some configuration files, may be registry.
Any help would be very appreciated,
01-12-2004 08:21 PM
By default SD app server uses thin JDBC drivers (it doesn't need Oracle client to run!!!) which uses the JAVA settings to choose its NLS_LANG, something like duser.region=
I just learned that you can use the JDBC thick driver which uses local Oracle client. I think this option will use the default NLS_LANG of Oracle client like you are used to. To use OCI driver with sd45 app server, have a look here:
See also for general Oracle info:
P.S. 4.0 uses normal OCI Oracle client
01-13-2004 03:29 AM
Thank you for your answer!
It's seems there are no simple solutuion.
May be someone who did installation had forgotten to read
install guide (I believe in this case database should be created in utf8).
If SD server works through JDBC I beleive
there are no solution because JDBC using
utf-covertions on client side(jdbc-side) and there is no possible for driver to convert properly from code of chars from WE8ISO8859P15 to UTF8 for non-english chars.
If the value of NLS_LANG is set to a non-
US7ASCII or non-WE8ISO8859P1 character
set, then the driver changes the value of
the NLS_LANG parameter on the client to
So if I will use normal NLS_LANG with the SD server, I will have wrong chars converting in the jdbc driver.
>P.S. 4.0 uses normal OCI Oracle client
Yes, with OCI all works properly.
I have database in 'WE8ISO8859P15' and
windows client with NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P15.
There are no problems with entering in database and reading(sqlplus) from tables non-english chars.
01-13-2004 07:23 AM
You need to set right value ( AmERICAN_AMERICA....) in windows registry on the appl server.
But there is the problem on ORACLE (SQL works normal) with jdbc driver if you use 2 byte characters (and you use). But it is not encoding problem.
OCI driver works normal but you need right NLA parameter in regestry
01-14-2004 03:34 AM
>You need to set right value ( >AmERICAN_AMERICA....) in windows registry >on the appl server.
It's HP Unix.
>But there is the problem on ORACLE (SQL >works normal) with jdbc driver if you use 2 >byte characters (and you use).
Where I use 2 bytes characters(database in WE8ISO8859P15 )?
>But it is >not encoding problem.
>OCI driver works normal but you need right >NLA parameter in regestry
Vasily, can you explain me this encoding operation is right:
char from db in 'WE8ISO8859P15' -> Utf8(jdbc in SD server with nls_lang american_america.?) and vice versa.
Have you got such configuration with properly displaying non-english chars?
(database in western codepage, and in jdbc side(SD Server) nls_lang = america_american.WE8ISO8859P15(cl8mswin1251,(utf8,
If you could write me,pls by e-mail email@example.com