NLS character set

Hi,
We have datawarehouse environment..
Currently the NLS Character set in our database is WE8MSWIN1252 which is non multibyte character set.But since this is a datawarehouse environment datawill be coming from source which is multi byte character set.Could you please let us know whether this will be supported in WE8MSWIN1252 character set or not??
Thanks,
Nab

user10124609 wrote:
For changing the NLS character set by export and import do we need to install the database again???yes,you can create new database with Unicode character set and can import there.But for full steps please refer
http://download.oracle.com/docs/cd/E11882_01/server.112/e10729/ch11charsetmig.htm#CEGDHJFF
Changing the Database Character Set ( NLS_CHARACTERSET ) [ID 225912.1]
Changing the Database Character Set - Frequently Asked Questions [ID 227337.1]
Edited by: Chinar on Nov 29, 2010 3:21 AM

Similar Messages

NLS CHARACTER SET 변경 방법 (ORACLE 7)

제품 : ORACLE SERVER
작성날짜 : 2004-11-09
NLS CHARACTER SET 변경 방법 (ORACLE 7)
======================================
PURPOSE
이 자료는 Oracle RDBMS SERVER에서 NLS CHARACTER SET 변경 방법에 대한
내용을 소개한다.
[ ORACLE 7 에서만 가능 ]
데이타베이스의 CHARACTER SET은 데이타 딕셔너리 테이블인 sys.props$에
들어 있다.
SQL>desc sys.props$
Name Null? Type
NAME NOT NULL VARCHAR2(30)
VALUE$ VARCHAR2(2000)
COMMENT$ VARCHAR2(2000)
SQL>column c1 format a30
SQL>select name c1, value$ c1 from sys.props$;
C1 C1
DICT.BASE 2
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_DATE_FORMAT DD-MON-YY
NLS_DATE_LANGUAGE AMERICAN
NLS_CHARACTERSET US7ASCII
NLS_SORT BINARY
GLOBAL_DB_NAME NLSV7.WORLD
여기서 NLS_CHARACTERSET에 현재 DB의 CHARACTER SET이 들어 있는데
이 값을 변경하여 DB의 CHARACTER SET을 변경할 수 있다.
여기서는 US7ASCII에서 KO16KSC5601로 옮기는 경우를 알아보자.
우선 바꾸고자 하는 CHRACTER SET이 지원되는 지를 다음 명령으로
확인한다.
select convert('a','KO16KSC5601','US7ASCII') from dual;
만약 이 Select 문에서 ORA-01482 에러가 발생하면 지정한 CHARACTER
SET이 지원되지 않는 경우이며 에러가 발생하지 않으면 CHARACTER
SET을 변경할 수 있다.
작업을 하기 전에는 만약을 위해서 DB 전체를 백업 받아두도록 한다.
CHARACTER SET 을 잘못 변경하면 DB 를 OPEN 할 수가 없기 때문이다.
1. 다음의 Update문을 실행하여 CHARACTER SET을 변경한다.
UPDATE sys.props$
SET value$ = 'KO16KSC5601'
WHERE name = 'NLS_CHARACTERSET';
Update 시에 NLS_CHARACTERSET을 지원되지 않는 값으로 잘못 설정하거나
실수로 콘트롤 문자 같은 것이 들어가게 되면 DB가 Shutdown 된 다음에는
Startup 이 안되므로 Update 후에 다음 명령으로 확인을 한 다음에
Commit을 하도록 한다.
select name, value$
from sys.props$
where value$ = 'KO16KSC5601';
Select가 제대로 출력되면 Commit 하고 Shutdown 했다가 Startup 하게
되면 새로운 CHARACTER SET 값을 갖게 된다. SELECT가 안 되면 ROLLBACK
하고 UPDATE부터 다시 하도록 한다.
2. 환경 변수 NLS_LANG 을 변경한다.
.profile 에서
NLS_LANG=American_America.KO16KSC5601; export NLS_LANG
또는 .cshrc 에서.
setenv NLS_LANG American_America.KO16KSC5601
*** win95 및 winnt의 client에서는 registry editor에서 NLS_LANG 값을
맞추어준다.
주의 !!!
: 위의 작업을 하기 전에 발생할 가능성이 있는 문제점
1) update 중 KO16KSC5601 이나 US7ASCII 등에서 철자를 잘못 입력하시면,
db 재기동 후에, 다음과 같은 에러가 발생합니다.
ora-12708
12708, 00000, "error while loading create database NLS parameter %s"
2) KO16KSC5601과 US7ASCII의 비교
Character set : KO16KSC5601 인 경우
===================================
: double byte encoding schema 이므로, 한글의 경우 2 bytes 를 크기 1로
계산하는 함수들이 있습니다.
그리고, table , column name에 한글을 double quote 없이 사용할 수 있습니다.
예)
SQL> create table 시험1
2 (컬럼1 varchar(10));
가
a
홍길동
SQL> select length(컬럼1) from 시험1;
1
1
3
SQL> select lengthb(컬럼1) from 시험1;
2
1
6
Character set : US7ASCII 인 경우
=================================
: single byte 7 bit encoding 을 사용합니다.
한글로 된 table, column 이름 사용 시 double quote를 반드시 사용해야 한다.
예)
SQL> create table "사원"
2 ("사원이름" varchar2(10));
가
a
홍길동
SQL> select length("사원이름") from "사원";
2
1
6
SQL> select lengthb("사원이름") from "사원";
2
1
6
US7ASCII일 때에는 vsize, lengthb function의 결과가 length 함수와 모두
동일합니다.
cf) substr, substrb 함수도 위의 length, lengthb의 관계와 같음.

제품 : ORACLE SERVER
작성날짜 : 2004-11-09
NLS CHARACTER SET 변경 방법 (ORACLE 7)
======================================
PURPOSE
이 자료는 Oracle RDBMS SERVER에서 NLS CHARACTER SET 변경 방법에 대한
내용을 소개한다.
[ ORACLE 7 에서만 가능 ]
데이타베이스의 CHARACTER SET은 데이타 딕셔너리 테이블인 sys.props$에
들어 있다.
SQL>desc sys.props$
Name Null? Type
NAME NOT NULL VARCHAR2(30)
VALUE$ VARCHAR2(2000)
COMMENT$ VARCHAR2(2000)
SQL>column c1 format a30
SQL>select name c1, value$ c1 from sys.props$;
C1 C1
DICT.BASE 2
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_DATE_FORMAT DD-MON-YY
NLS_DATE_LANGUAGE AMERICAN
NLS_CHARACTERSET US7ASCII
NLS_SORT BINARY
GLOBAL_DB_NAME NLSV7.WORLD
여기서 NLS_CHARACTERSET에 현재 DB의 CHARACTER SET이 들어 있는데
이 값을 변경하여 DB의 CHARACTER SET을 변경할 수 있다.
여기서는 US7ASCII에서 KO16KSC5601로 옮기는 경우를 알아보자.
우선 바꾸고자 하는 CHRACTER SET이 지원되는 지를 다음 명령으로
확인한다.
select convert('a','KO16KSC5601','US7ASCII') from dual;
만약 이 Select 문에서 ORA-01482 에러가 발생하면 지정한 CHARACTER
SET이 지원되지 않는 경우이며 에러가 발생하지 않으면 CHARACTER
SET을 변경할 수 있다.
작업을 하기 전에는 만약을 위해서 DB 전체를 백업 받아두도록 한다.
CHARACTER SET 을 잘못 변경하면 DB 를 OPEN 할 수가 없기 때문이다.
1. 다음의 Update문을 실행하여 CHARACTER SET을 변경한다.
UPDATE sys.props$
SET value$ = 'KO16KSC5601'
WHERE name = 'NLS_CHARACTERSET';
Update 시에 NLS_CHARACTERSET을 지원되지 않는 값으로 잘못 설정하거나
실수로 콘트롤 문자 같은 것이 들어가게 되면 DB가 Shutdown 된 다음에는
Startup 이 안되므로 Update 후에 다음 명령으로 확인을 한 다음에
Commit을 하도록 한다.
select name, value$
from sys.props$
where value$ = 'KO16KSC5601';
Select가 제대로 출력되면 Commit 하고 Shutdown 했다가 Startup 하게
되면 새로운 CHARACTER SET 값을 갖게 된다. SELECT가 안 되면 ROLLBACK
하고 UPDATE부터 다시 하도록 한다.
2. 환경 변수 NLS_LANG 을 변경한다.
.profile 에서
NLS_LANG=American_America.KO16KSC5601; export NLS_LANG
또는 .cshrc 에서.
setenv NLS_LANG American_America.KO16KSC5601
*** win95 및 winnt의 client에서는 registry editor에서 NLS_LANG 값을
맞추어준다.
주의 !!!
: 위의 작업을 하기 전에 발생할 가능성이 있는 문제점
1) update 중 KO16KSC5601 이나 US7ASCII 등에서 철자를 잘못 입력하시면,
db 재기동 후에, 다음과 같은 에러가 발생합니다.
ora-12708
12708, 00000, "error while loading create database NLS parameter %s"
2) KO16KSC5601과 US7ASCII의 비교
Character set : KO16KSC5601 인 경우
===================================
: double byte encoding schema 이므로, 한글의 경우 2 bytes 를 크기 1로
계산하는 함수들이 있습니다.
그리고, table , column name에 한글을 double quote 없이 사용할 수 있습니다.
예)
SQL> create table 시험1
2 (컬럼1 varchar(10));
가
a
홍길동
SQL> select length(컬럼1) from 시험1;
1
1
3
SQL> select lengthb(컬럼1) from 시험1;
2
1
6
Character set : US7ASCII 인 경우
=================================
: single byte 7 bit encoding 을 사용합니다.
한글로 된 table, column 이름 사용 시 double quote를 반드시 사용해야 한다.
예)
SQL> create table "사원"
2 ("사원이름" varchar2(10));
가
a
홍길동
SQL> select length("사원이름") from "사원";
2
1
6
SQL> select lengthb("사원이름") from "사원";
2
1
6
US7ASCII일 때에는 vsize, lengthb function의 결과가 length 함수와 모두
동일합니다.
cf) substr, substrb 함수도 위의 length, lengthb의 관계와 같음.

How to set NLS character set for report 9i servlet output?

Hi,
I am running a Reports 9i report. My problem is that the output HTML file is UTF8 encoded while ALL my 9iASR2 registry setting are set to EEISO8859P2. When I issued the http://<host:port>/reports/rwservlet/showenv?server=servername command it returned that the NLS setting is UTF8.
Can somebody please help me, how to set this environment variable for the report servlet to EE..P1? Thank you in advance.
Regards,
Tamas Szecsy

Dmitry,
recently I got this from Oracle support. :-(. Currently when I set the Windows 2000 local and default local to Hungarian and the charset to EE..P2 then I get Central-European encoded charset. I think you will have to experience around to get correct result (if it is possible at all).
+++++++++++++++++++++++++++++++++++++++++++++++++++++
This is bug Number 2472932 NLS:RWSERVLET SETS INVALID CHARSET AT THE HTTP HEADER
marked as fixed in 9.0.2.2 . unfortunately this bug is not published so I will not be able to sent you the bug as a whole but here is problem description in bug:
iAS9.0.2.0.1 (Reports9.0.2.0.1) on Solaris2.8
Running rdf with rwservlet sends the invalid charset at the http header.
Say ias is up with LANG=C, http header for the rwservlet
is always sent as "iso-8859-1" regardless of rwserver's NLS_CHARACTERSET.
This is the TCP/IP packet for the GET /reports/rwservlet?report=xxx&....
HTTP/1.1 200 OK Date: Sat, 20 Jul 2002 01:15:37 GMT Cache-Cont
rol: private Content-Language: en Server: Oracle9iAS/9.0.2 Ora
cle HTTP Server Oracle9iAS-Web-Cache/9.0.2.0.0 (N) Content-Leng
th: 6908 Content-Type: text/html; charset=ISO-8859-1 Set-Cooki
In this example, to produce a html with other charset than
iso-8859-1,usually the outputted html has the charset information at
meta tag by setting "Before Report Value" property in rdf.
However charset in meta tag is less priority than http header, browser
such as IE6 or Netscape7 firstly displays the page in iso-8859-1.
Hence the characters other than iso8859p1 gets garbage.
To workaround it with IE6/NS7, set proper encoding manually.
('View'-'Encoding' for IE 'View'-'Character coding' for NS7 )
However, NS4.7 does not have workaround for it.
Besides, starting opmn in LANG=ja, the rwservlet's http header becomes
Shift_JIS!!. Thus rwserver seems to set the http header based on the
LANG on Solaris.
To fix these issues,
- The http header for rwservlet shold be based on the nls_characterset
for the rwserver.
This is no problem for reprots jsp run.

ORA-12712 error while changing nls character set to AL32UTF8

Hi,
It is strongly recommend to use database character set AL32UTF8 when ever a database is going to used with our XML capabilities. The database character set in the installed DB is WE8MSWIN1252. For making use of XML DB features, I need to change it to AL32UTF8. But, when I try doing this, I'm getting ORA-12712: new character set must be a superset of old character set. Is there a way to solve this issue?
Thanks in advance,
Divya.

Hi,
a change from we8mswin1252 to al32utf8 is not directly possible. This is because al32utf is not a binary superset of we8mswin1252.
There are 2 options:
- use full export and import
- Use of the Alter in a sort of restricted way
The method you can choose depends on the characters in the database, is it only ASCII then the second one can work, in other cases the first one is needed.
It is all described in the Support Note 260192.1, "Changing the NLS_CHARACTERSET to AL32UTF8 / UTF8 (Unicode)". Get it from the support/metalink site.
You can also read the chapters about this issue in the Globalization Guide: [url http://download.oracle.com/docs/cd/E11882_01/server.112/e10729/ch11charsetmig.htm#g1011430]Change characterset.
Herald ten Dam
http://htendam.wordpress.com

NLS Character Set problem

Hi all,
I am getting very tricky kind of problem oracle 10G. When I am try to insert a special character like '?' in 180 degree opposite direction( means imagine if we rotate the given special character ' ? ' in 180 degree), its perfectly inserting and I am able to see that character in the same way which I inserted in my production database. But if I try to do the sme in my development database and try to view it using select statement, its showing like normal '?' , not in a rotated one. Can any one help me to figure out this problem.
thanks in advance.
Karthik

I suppose you are using a spanish database and this problem it's normal: database doesn't reconigzes this "special character" and it prints this as a "easy conversion" (but not usefull conversion). I want suggest you to use any of the 'NLS_....' parameters at session level (or statment level, if you can). With 'NLS_LANG' you can define country language characterset. If you type well your database can recognize this character among others, like 'ñ', 'á', 'à', etc. If this not runs well you probably will need to change the entire database character set.

NLS character set non AL32UTF8 versus AL32UTF8

Good morning Gurus,
RCU utility strongly recommends to have this parameter set to AL32UTF8.
My database by default was set as WE8MSWIN1252.
I have read a lot about these settings. and like to have exact steps to take to accomplish this. I posted this problem in "Problem with RCU utility' but did not get any response.
My question is why oracle makes things difficult. I only use american language, if both are good for that then why do RCU requires to change it.
I have seen people who have ignored this message had trouble down the road of installation process.
I appreciate if some one can explain to me the implications of not changing versus changing.
Is that means, my database has to be kept with AL32UTF8 parameter all the time after installation is done?
Also another question
I have 3 meg RAM on my laptop, Oracle requires 4, will this cause the problem during installation?
Thank you
j

Hi,
a change from we8mswin1252 to al32utf8 is not directly possible. This is because al32utf is not a binary superset of we8mswin1252.
There are 2 options:
- use full export and import
- Use of the Alter in a sort of restricted way
The method you can choose depends on the characters in the database, is it only ASCII then the second one can work, in other cases the first one is needed.
It is all described in the Support Note 260192.1, "Changing the NLS_CHARACTERSET to AL32UTF8 / UTF8 (Unicode)". Get it from the support/metalink site.
You can also read the chapters about this issue in the Globalization Guide: [url http://download.oracle.com/docs/cd/E11882_01/server.112/e10729/ch11charsetmig.htm#g1011430]Change characterset.
Herald ten Dam
http://htendam.wordpress.com

UTF8 character set conversion for chinese Language

Hi friends,
Would like to some basic explanation on UTF8 feature,what does it help while converting the data from chinese language.
Would like to know what all characters this UTF8 will not support while converting from chinese language.
Thanks & Regards
Ramya Nomula

Not exactly sure what you are looking for, but on MetaLink, there are numerous detailed papers on NLS character sets, conversions, etc.
Bottom line is that for traditional Chinese characters (since they are more complicated), they require 4 bytes to store the characters (such as UTF-8, and AL32UTF8). Some mid-eastern characters sets also fall in this category.
Do a google search on "utf8 al32utf8 difference", and you will get some good explanations.
e.g., http://decipherinfosys.wordpress.com/2007/01/28/difference-between-utf8-and-al32utf8-character-sets-in-oracle/
Recently, one of our clients had a question on the differences between these two character sets since they were in the process of making their application global. In an upcoming whitepaper, we will discuss in detail what it takes (from a RDBMS perspective) to address localization and globalization issues. As far as these two character sets go in Oracle, the only difference between AL32UTF8 and UTF8 character sets is that AL32UTF8 stores characters beyond U+FFFF as four bytes (exactly as Unicode defines UTF-8). Oracle’s “UTF8” stores these characters as a sequence of two UTF-16 surrogate characters encoded using UTF-8 (or six bytes per character). Besides this storage difference, another difference is better support for supplementary characters in AL32UTF8 character set.
You may also consider posting your question on the Globalization Suport forum which pertains more to these types of questions.
Globalization Support

BIG5 and HKSCS Character Set Support

Hi,
We're experiencing some problems inserting a string containing both BIG5 and HKSCS characters to a 7.3.4 Oracle DB using JDBC. The underlying character set used by the DB is ZHT16BIG5 (this cannot be changed). The characters can be inserted correctly if we use SQLPlus/WorkSheet.
Take note that the BIG5 character set can be inserted correctly. The problem occurs if we include HKSCS characters in the statement.
We have tried a number of ways already but failed to convert the data properly.
We tried converting the data using ByteToCharConverter.getConverter("Big5") but this cannot handle the HKSCS properly.
We even tried using the CharacterSet.ZHT16BIG5_CHARSET provided by the NLS character set but it cannot convert all HKSCS characters correctly.
Any ideas on how to solve this problem? Or is it because the HKSCS character set is NOT supported by the JDBC driver?
Below is a sample text containg both BIG5 and HKSCS characters:
'i$h%49D$G$Q$T89 Ize _ ^ S( R @ A Y q
Any help/suggestion is most welcome.
Thanks,
Cis
null

I got the exact same problem as you.
(The Oracle I using is 8.1.7)
Can any one help??

Re Character Set conversion

Hi all
I want to change my Character Set to UTF8 for an exisiting database. Can anyone please post me the steps to be followed.
Regds
Nirmal

As you can see in
Re: NLS Character Set problem
Change
NLS_LANG=NLS_LANGUAGE_NLS_TERRITORY.NLS_CHARACTERSET
Table of Nls parameters:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ch3globenv.htm#sthref195

May i use nls_charset12 to convert character set before executeQuery()?

i got a problem for the db nls character set
isn't us7ascii, so while retreiving data from database the data stored in ResultSet is changed to UTF-8 format. thus, my question is - how to convert character set before my executuing the method
executeQuery() or any other methods would be appreciated.
thanks in advice,

This is Tommy. I saw your post on Oracle Forum. Can you give me the classes12.zip, classes12_g.zip, and nls_charset12.zip ?!
Thx in advance !!
Tommy fromTaiwan ( July 3, 2001 )

Cdrtools package, support for nls/utf8 character sets

Hello ppl,
I've been trying desperetly to burn a cd/dvd(k3b) with greek filenames and directory names. I ended up with file names like "???????????????????? (invalid unicode)"
After a lot of searching, i managed to isolate and solve the problem. There has been a patch(http://bugs.gentoo.org/attachment.cgi?id=52097) for cdrtools to support nls/utf8 character sets.
I guess that 90%+ of people using arch and burning cd's/dvd's, ignore the problem cause they just burn cd's/dvd's using standard english characters.
For all others here it is :
# Patched cdrtools to support nls/utf8 character sets
# Contributor: Akis Maziotis <[email protected]>
pkgname=cdrtools-utf8support
pkgver=2.01.01
pkgrel=3
pkgdesc="Tools for recording CDs patched for nls/utf8 support!"
depends=('glibc')
conflicts=('cdrtools')
source=(ftp://ftp.berlios.de/pub/cdrecord/alpha/cdrtools-2.01.01a01.tar.gz http://bugs.gentoo.org/attachment.cgi?id=52097)
md5sums=('fc085b5d287355f59ef85b7a3ccbb298' '1a596f5cae257e97c559716336b30e5b')
build() {
cd $startdir/src/cdrtools-2.01.01
msg "Patching cdrtools ..."
patch -p1 -i ../attachment.cgi?id=52097
msg "Patching done "
make || return 1
make INS_BASE=$startdir/pkg/usr install
It's a modified pkgbuild of the official arch cdrtools package (http://cvs.archlinux.org/cgi-bin/viewcv … cvs-markup) patched to support nls/utf8 character sets.
Worked like a charm.
If u want to install it, u should uninstall the cdrtools package
pacman -Rd cdrtools
P.S.: I've issued this as a bug in http://bugs.archlinux.org/task/3830 but nobody seemed to care... :cry: :cry: :cry:

Hi Bharat,
I have created a Oracle 8.1.7 database with UTF8 character set
on WINDOWS 2000.
Now , I want to store and retrieve information in other languages
say Japanese or Hindi .
I had set the NLS Language and NLS Terrritory to HINDI and INDIA
in the SQL*PLUS session but could not see the information.You cannot view Hindi using SQL*Plus. You need iSQL*Plus.
(Available as a download from OTN, and requiring the Oracle HTTP
server).
Then you need the fonts (either Mangal from Microsoft or
Code2000).
Have your NLS_LANG settings in your registry to
AMERICAN_AMERICA.UTF8. (I have not tried with HINDI etc, because
I need my solution to work with 806,817 and 901, and HINDI was
not available with 806).
Install the language pack for Devanagari/Indic languages
(c_iscii.dll) on Windows NT/2000/XP.
How can I use the Forms 6i to support this languages ?I am not sure about that.
Do write back if this does not solve your problem.
--Shirish

NLS settings for a database link between DBs with different character sets

I am using a database link to move data from one database to another and I am seeing some strange data problems. The databases have different character sets and different NLS settings. I wonder if this could be causing my problem.
Here are the NLS parameters for the database where the database link exists. (the SOURCE database)
1     NLS_CALENDAR     GREGORIAN
2     NLS_CHARACTERSET     WE8MSWIN1252
3     NLS_COMP     BINARY
4     NLS_CURRENCY     $
5     NLS_DATE_FORMAT     DD-MON-RR
6     NLS_DATE_LANGUAGE     AMERICAN
7     NLS_DUAL_CURRENCY     $
8     NLS_ISO_CURRENCY     AMERICA
9     NLS_LANGUAGE     AMERICAN
10     NLS_LENGTH_SEMANTICS     BYTE
11     NLS_NCHAR_CHARACTERSET     AL16UTF16
12     NLS_NCHAR_CONV_EXCP     FALSE
13     NLS_NUMERIC_CHARACTERS     .,
14     NLS_SORT     BINARY
15     NLS_TERRITORY     AMERICA
16     NLS_TIMESTAMP_FORMAT     DD-MON-RR HH.MI.SSXFF AM
17     NLS_TIMESTAMP_TZ_FORMAT     DD-MON-RR HH.MI.SSXFF AM TZR
18     NLS_TIME_FORMAT     HH.MI.SSXFF AM
19     NLS_TIME_TZ_FORMAT     HH.MI.SSXFF AM TZR
Here are the NLS parameters for the database that the database link connects to. (the TARGET database)
1     NLS_CALENDAR     GREGORIAN
2     NLS_CHARACTERSET     AL32UTF8
3     NLS_COMP     BINARY
4     NLS_CURRENCY     $
5     NLS_DATE_FORMAT     DD-MON-RR
6     NLS_DATE_LANGUAGE     AMERICAN
7     NLS_DUAL_CURRENCY     $
8     NLS_ISO_CURRENCY     AMERICA
9     NLS_LANGUAGE     AMERICAN
10     NLS_LENGTH_SEMANTICS     BYTE
11     NLS_NCHAR_CHARACTERSET     AL16UTF16
12     NLS_NCHAR_CONV_EXCP     FALSE
13     NLS_NUMERIC_CHARACTERS     .,
14     NLS_SORT     BINARY
15     NLS_TERRITORY     AMERICA
16     NLS_TIMESTAMP_FORMAT     DD-MON-RR HH.MI.SSXFF AM
17     NLS_TIMESTAMP_TZ_FORMAT     DD-MON-RR HH.MI.SSXFF AM TZR
18     NLS_TIME_FORMAT     HH.MI.SSXFF AM
19     NLS_TIME_TZ_FORMAT     HH.MI.SSXFF AM TZR
The SOURCE database version is 10g Release 10.2.0.3.0 - Production
The TARGET database version is 11g Release 11.1.0.6.0 - 64bit Production
Do I need to modify the NLS settings in the SOURCE database before executing a script to insert data into the TARGET database?
Thanks, Jack

The difference in settings is not a problem by itself, especially that only the NLS_CHARACTERSET matters. Of course, this difference may lead to certain issues if not taken into consideration.
Please, describe symptoms of your problems.
-- Sergiusz

NLS LANG VS CHARACTER SET

Guys,
What's the difference between NLS lang and character set?
Thanks

http://download.oracle.com/docs/cd/B19306_01/server.102/b14215/et_params.htm#sthref1700
http://download.oracle.com/docs/cd/B19306_01/install.102/b15660/app_gblsupp.htm#sthref1304

Multiple Character set for NLS

Hi,
I'm using Oracle 8i database. Is it possible to set the different character set for the database? The requirement is to support the two different character set data, one (main) Japanese character set and other Simplified Japanese. Or is there any other way in which i can store these data (Japanese & Chinese)?
Thanks & Regards,
Jayesh

Please don't get me wrong. Currently it is set in the windows database. I did not set nls_lang at the command prompt before import into windows. However nls_lang is already set and it is character set WE8ISO8859P1 the same as the value I specified in creation script, besides the other two values AMERICAN, AMERICA. They are now same in both solaris and windows. Only the character sets are different because I specified a different one. So, is it ok or do I now need another fresh import this time with nls_lang set to AMERICAN_AMERICA.UTF8 ?

Is it necessary that the database nls be any given character set? My db is

WE8ISO8859P1.

Hello,
APEX itself doesn't demand a specific database characterset, however the DAD (Database Access Descriptor) that you setup for APEX needs to use AL32UTF8 in the character set portion of the PlsqlNLSLanguage setting, as per the installation instructions -
http://download.oracle.com/docs/cd/E14373_01/install.32/e13366/db_install.htm#CIHJIIIG
Hope this helps,
John.
Blog: http://jes.blogs.shellprompt.net
Work: http://www.apex-evangelists.com
Author of Pro Application Express: http://tinyurl.com/3gu7cd
REWARDS: Please remember to mark helpful or correct posts on the forum, not just for my answers but for everyone!

NLS character set

Similar Messages

Maybe you are looking for