To check the NLS_CHARACTERSET and all localization parameters of your source database, you can query the NLS_DATABASE_PARAMETERS table:
SQL> select * from NLS_DATABASE_PARAMETERS;
PARAMETER VALUE
------------------------------ ----------------------------------------
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET WE8ISO8859P1
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT dd-mon-yyyy
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_RDBMS_VERSION 10.2.0.1.0
20 rows selected.
Having the NLS_LANGUAGE, NLS_TERRITORY and NLS_CHARACTERSET parameter values you can set environment variable NLS_LANG accordingly, or you can just set it in the target database the same way as the source database provided the value in NLS_LANG variable matches the NLS database parameter values:
oracle@myserver:~$ export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
And if you're creating a database, don't forget to declare the character set properly:
CREATE DATABASE mydb
...
CHARACTER SET WE8ISO8859P1
...
More information:
Oracle Database Globalization Support Guide
No comments:
Post a Comment