Printable View
Hi,
I have 2 databases on the same machine which has Oracle 10G 10.2.0.4 installed. Both databases have different NLS_LANG. Every time when I try to use one database the other one can't be used since NLS_LANG is not correct.
Is there a way to specify NLS_LANG for each database in order to avoid changing this parameter in registry.
Regards
You use NLS_LANG to let Oracle know what characterset the OS is using. This is important so that Oracle would do characterset conversion from client characterset to the database characterset.
The question here would be why do you have two different NLS_LANG setting on the same server?
I have two databases that use different NLS_LANG and ceach time when I switch from one database to another I have to change NLS_LANG parameter in registry.Quote:
Originally Posted by hany
Please re-read my post. NLS_LANG tells Oracle what the OS characterset is. It's not the other way around, you do not specify the database characterset through NLS_LANG.Quote:
Originally Posted by crysu
You can't have two OS charactersets at the same time, can you?
Please review Note 158577.1 on metalink. It explains NLS_LANG very well.
Quote:
Originally Posted by hany
Seems that you didn't understood my problem (or I don't understand you). I have two databases on the same machine DB1 and DB2. When I use DB1 I have to set NLS_LANG to WE8MSWIN1252... when I use DB2 I have to set NLS_LANG to AL32UTF8... I wonder if there is a parameter to specify for each database what NLS_LAG to use... I understood from you that I can't have two NLS_LANG at the same time, but I wonder if there is another parameter that specify NLS_LANG for each database not for all.
Regards
I think this is the point you have to clear... Why do you have to use different NLS_LANG settings for the different DBs? You should be using a unique NLS_LANG for both, depending on your operating system charset, and it should work fine.Quote:
When I use DB1 I have to set NLS_LANG to WE8MSWIN1252... when I use DB2 I have to set NLS_LANG to AL32UTF8...
What happens if you use the same NLS_LANG setting for both, that makes you change in for each DB?
In unix, here is what gets loaded when I type in a SID:
>DPMCDEV
export ORACLE_HOME=/u16/oracle/product/10.2.0
export ORACLE_BASE=/u16/oracle/product/10.2.0
export LD_LIBRARY_PATH=/u16/oracle/product/10.2.0/lib
export OB=/u16/oracle/product
export OH=/u16/oracle/product/10.2.0
export ORACLE_ADMIN=/u01/app/oracle/local/admin/DPMCDEV
export OA=/u01/app/oracle/local/admin/DPMCDEV
export ORACLE_SID=DPMCDEV
export TNS_ADMIN=/u16/oracle/product/10.2.0/network/admin
export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
export ORA_NLS33=$ORACLE_HOME/nls/data
export NLS_DATE_FORMAT=DD-MON-RR
export NLS_DATE_LANGUAGE=AMERICAN
export NLS_NUMERIC_CHARACTERS=".,"
umask 022
export SHLIB_PATH=$ORACLE_HOME/lib
When I change db's it's unique settings are exported. You have to fully set the environment each time you change from one instance to another.
Jim
it's not my decision, this is what client want and I can't do anythingQuote:
Originally Posted by jignacio
you say that every time when you change database NLS_LANG change automatically ?Quote:
Originally Posted by ridges54
No. Process that set environmentals when you change instances e.g. proper ORACLE_HOME, proper ORACLE_SID, etc - has to set ALL environmentals as they are needed to access targetted instance.Quote:
Originally Posted by crysu