ORA-01482: unsupported character set

Hello,
does anybody have an experience with error message "ORA-01482: unsupported character set" which is displayed instead of the content of page region, which is of type select SQL.
The strange thing with this is that e.g. LOVs are rendered/displayed without such error message and they are also of the same type SQL select - no mater how complex.
- APEX version 3.0.1 in Database version 9.2.0.7.
Thank you for helpful info.
Petr

What version of Oracle XE did you install?
-Oracle Database 10g Express Edition (Western European) Single-byte LATIN1 database for Western European language storage.
-Oracle Database 10g Express Edition (Universal) Multi-byte Unicode database for all language deployment.
Give us an example of a query that goes wrong.
Regards, Marc

Similar Messages

ORA-12712: new character set must be a superset of old character ...-

Dear all ,
i have a problem with oracle database,
server configuration oracle 10g, solaris 9, sparc processor 64 bit,
i altered database character set to UTF8, whe i return database to old seeting ISO 8859-6
i got this error ORA-12712: new character set must be a superset of old character set.
anyone can help me and let me know how can i solve this error?
thanks
Gasir

You should recreate a new database and use export/import to transfer data from the existing UTF8 database to the new ISO 8859-6 database according to the ]Globalization Guide.

CHARACTER SET 문제에 대한 CHECK LIST

제품 : ORACLE SERVER
작성날짜 : 1998-04-13
환경 변수들이 모두 올바른 데도 character set 에 문제가 있는 경우
=============================================================
Oracle version 7.2 에서부터 사용되는 환경변수인 ORA_NLS 를 잘못 setting
하면, 다음과 같은 character set 문제가 발생할 수 있습니다.
server version 환경변수
============== =========
7.2 ORA_NLS
7.3 ORA_NLS32
8.0 ORA_NLS33
즉, 다음의 경우에 위처럼 환경 변수 ORA_NLS 가 DB version 과 일치하는
지를 확인해야 합니다.
1) US7ASCII 에서 KO16KSC5601 로 character set 을 변경하기 전에
변경이 되는지 확인하는 조회에서 다음과 같은 에러 발생하는 경우
select convert('a','KO16KSC5601','US7ASCII') from dual;
Ora-1482 "unsupported character set"
2) props$, v$nls_parameters 의 character set 이 서로 다른 값을
가질 경우
3) v$nls_valid_values 에 default value 만 조회되는 경우
(즉, select count(*) from v$nls_valid_values; 의 결과가
4 인 경우 ORA_NLS 가 setting 되어 있지 않기 때문)
4) table 생성시에 ora-911 "invalid character",
ora-904 "invalid column name" 빌생하는 경우
5) NLS_LANG 을 올바로 setting 하였는 데도, 한글이 ??? 로 나오는 경우
$ env | grep ORA_NLS
ORA_NLS=$ORACLE_HOME/ocommon/nls/admin/data
$ cd $ORA_NLS
ls -l boot
-rw-r--r-- 1 rctest72 dba 13572 Dec 2 1995 lx0boot.d
-rw-r--r-- 1 rctest72 dba 13572 Dec 2 1995 lx1boot.d
이 두개의 화일이 ORA_NLS 디렉토리에 있어야 합니다.
(version 에 따라 size 는 다를 수 있습니다.)
해결 방법
========
만약,ORA_NLS(ORA_NLS32,ORA_NLS33) 이 setting 되지 않았거나,rdbms version
과 맞지 않을 경우 다시 수정한 후에 restartup 하면 이와 관련된 문제는
해결됩니다.
(특정 OS, Ticom 의 경우 OS 를 rebooting 해야 하는 경우도 있습니다.)
해결 방법은 ORA_NLS 를 정상적으로 setting 한 후에 restartup 하면,
v$nls_valid_values 에 KO16KSC5601 이 조회되었고, 한글 테이블명이나
컬럼명이 가능해지고, dictionary 도 KO16KSC5601 로 일치하게 됩니다.
다음의 CASE1, CASE2 를 통해 이 환경 변수가 DB 에 미치는 영향을
확인할 수 있습니다.
CASE1
=====
위의 lx0boot.d, lx1boot.d 화일을 ACCESS 할 수 있을 때, 기동된 instance 의
dictionary를 조회하면, 많이 사용하는 KO16KSC5601, US7ASCII 등의 character
set 을 조회할 수 있습니다.
SQLDBA> select * from v$nls_valid_values;
313 rows selected.
SQLDBA> select * from v$nls_valid_values where value='KO16KSC5601';
PARAMETER VALUE
CHARACTERSET KO16KSC5601
1 row selected.
; 즉, total 313 row 가 있고 그 중에 KO16KSC5601,US7ASCII 도 있음
CASE2
=====
그러나, lx0boot.d, lx1boot.d 화일을 ACCESS 할 수 없을 때, 기동된
instance 의 dictionary 를 조회하면, default value 들만 조회됩니다.
SQLDBA> select * from v$nls_valid_values;
PARAMETER VALUE
LANGUAGE AMERICAN
TERRITORY AMERICA
CHARACTERSET US7ASCII
SORT BINARY
4 rows selected.
;즉, lx0boot.d, lx1boot.d 를 access 할 수 없을 경우에는 위의 US7ASCII 만
지원합니다.

Hi Amos,
It should work but you will need to use a Unicode font. Try setting your field fonts in CR to MS Ariel Unicode and test again.
Thank you
Don

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

Character set AL32UTF8;

Hello All,
I have oracle 10gr2 and i want to get support of Portuguese character set, for that , i suppose AL32UTF8 is recommended, but when i try to modify the character set i get this error.
SQL> select value from nls_database_parameters where parameter='NLS_CHARACTERSET';
VALUE
WE8ISO8859P1
SQL> alter database character set AL32UTF8;
alter database character set AL32UTF8
ERROR at line 1:
ORA-12712: new character set must be a superset of old character set
what should i do now? any idea?
thanks

here it is:
SQL> select news_detail from news_tbl;
NEWS_DETAIL
A Directora nacional-Adjunta do Patrim?nio ligado ao Minist?rio das Finan?as
de Mo?ambique, Albertina Fruquia, esteve nesta quarta-feira, do dia 22 de Novemb
ro, na Secretaria de Log?stica e Tecnologia de Informa??o ( SLTI )para conhecer
o sistema de compras do Governo Federal Brasileiro e verificar a possibilidade d
e estabelecer acordos de coopera??o nessa ?rea.
 
Na opini?o da Directora Mo?ambicana, o Brasil tem uma experi?ncia importante
em compras p?blicas que pode colaborar com Mo?ambique nesta ?rea. Ela lembrou qu
e o pa?s Africano est? imlpementando um novo regulamento de compras que constitu
i o preg?o presencial, modalidade regulamentada no Brasil desde 2000.
 
you can see that even in sqlplus the data is not shown the portugueses language chars, now what you think, that whether this data is stored wrong or either i can recover it by changing chars set or language?
Message was edited by:
nayyares
Message was edited by:
nayyares

Oracle11g: how I change character set to AL32UTF8?

Hi, a software is requiring to have a database with AL32UTF8 character set.
For what I understand I have an instance of db with
nls_language=american
I tried:
SQL> alter database character set AL32UTF8;
alter database character set AL32UTF8
ERROR at line 1:
ORA-12712: new character set must be a superset of old character set
what's wrong? How can I achieve this?
Thanks a lot.
Warning: you are talking with a non expert. :)

802428 wrote:
Hi schavali,
I am new bee to oracle and BPM so i am unable to get which database you are talking about to drop & recreate and also how to do so.
Any help over this will be highly appreciable.
Regards,
ITM CrazyWe are referring to OP's database (where the characterset is set to WE8MSWIN1252)
Srini

Unable to migrate table, character set from WE8MSWIN1252 to AL32UTF8

Hi,
On our source db the character set is AL32UTF8
On our own db, we used the default character set of WE8MSWIN1252 .
When migrating one of the table, we get an error of this: ORA-29275: partial multibyte character
So in to alter our character set from WE8MSWIN1252 to AL32UTF8, we get this error:
ALTER DATABASE CHARACTER SET AL32UTF8
ERROR at line 1:
ORA-12712: new character set must be a superset of old character set
I would sure not like to reinstall the db and migrate the tables again. Thanks.

See this related thread - Re: Want to change characterset of DB
You can use the ALTER DATABASE CHARACTER SET command in very few cases. You will most likely have to recreate the database and re-migrate the data.
HTH
Srini

Can i Change Character set WE8ISO8859P1 TO AR8MSWIN1256 IN ORACLE 8i

I tried to change character set from WE8ISO8859P1 TO AR8MSWIN1256 on oracle 8i database.
Getting the follwoing error for both character set and National character set.
ORA-12712:New character set must be a superset of old character set.
My question can i change or have to do export and import in arabic character set DB.
null

Hello Sarath,
There is an extension CODE PAGE with OPEN DATASET stmt.
Can you please elaborate which character set you want to write to the application server?
BR,
Suhas

How to change character set

hi my database character set is non-AL32UTF8 HOW can i change this to be AL32UTF8 am in database 11g
SQL> select * from v$nls_parameters where parameter like '%CHARACTERSET%';
PARAMETER
VALUE
NLS_CHARACTERSET
WE8MSWIN1252
NLS_NCHAR_CHARACTERSET
AL16UTF16
there is something in database i cannot drop database

i did this
SQL> @C:\app\Tshifhiwa\product\11.2.0\dbhome_1\RDBMS\ADMIN\csalter.plb
insert into csm$dictusers
ERROR at line 1:
ORA-00942: table or view does not exist
Function created.
Warning: Function created with compilation errors.
Warning: Procedure created with compilation errors.
This script will update the content of the Oracle Data Dictionary.
Please ensure you have a full backup before initiating this procedure.
Would you like to proceed (Y/N)?y
old 6: if (UPPER('&conf') <> 'Y') then
new 6: if (UPPER('y') <> 'Y') then
 csm$main();
ERROR at line 10:
ORA-06550: line 10, column 5:
PLS-00905: object SYS.CSM$MAIN is invalid
ORA-06550: line 10, column 5:
PL/SQL: Statement ignored
 select value into svalue from csm$parameters where name='CSALTER_FINISHED';
ERROR at line 9:
ORA-06550: line 9, column 35:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 9, column 5:
PL/SQL: SQL Statement ignored
ORA-06550: line 18, column 35:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 18, column 5:
PL/SQL: SQL Statement ignored
ORA-06550: line 21, column 38:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 21, column 8:
PL/SQL: SQL Statement ignored
ORA-06550: line 27, column 35:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 27, column 5:
PL/SQL: SQL Statement ignored
ORA-06550: line 30, column 38:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 30, column 8:
PL/SQL: SQL Statement ignored
delete from csm$dictusers where username in ('PM', 'SH', 'HR', 'OE')
ERROR at line 1:
ORA-00942: table or view does not exist
Function dropped.
Function dropped.
Procedure dropped.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> ALTER SYSTEM ENABLE RESTRICTED SESSION;
ALTER SYSTEM ENABLE RESTRICTED SESSION
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 4360
Session ID: 139 Serial number: 6
SQL> ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
ERROR:
ORA-01034: ORACLE not available
Process ID: 4360
Session ID: 139 Serial number: 6
ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 4360
Session ID: 139 Serial number: 6
SQL> ALTER SYSTEM SET AQ_TM_PROCESSES=0;
ERROR:
ORA-01034: ORACLE not available
Process ID: 4360
Session ID: 139 Serial number: 6
ALTER SYSTEM SET AQ_TM_PROCESSES=0
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 4360
Session ID: 139 Serial number: 6
SQL> ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
ERROR:
ORA-01034: ORACLE not available
Process ID: 4360
Session ID: 139 Serial number: 6
ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 4360
Session ID: 139 Serial number: 6
SQL> connect /as sysdba
Connected to an idle instance.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 535662592 bytes
Fixed Size 1375792 bytes
Variable Size 373293520 bytes
Database Buffers 155189248 bytes
Redo Buffers 5804032 bytes
Database mounted.
SQL> ALTER SYSTEM ENABLE RESTRICTED SESSION;
System altered.
SQL> ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
System altered.
SQL> ALTER SYSTEM SET AQ_TM_PROCESSES=0;
System altered.
SQL> ALTER DATABASE OPEN;
Database altered.
SQL> ALTER DATABASE CHARACTER SET 'AL32UTF8';
ALTER DATABASE CHARACTER SET 'AL32UTF8'
ERROR at line 1:
ORA-24329: invalid character set identifier
SQL> ALTER DATABASE CHARACTER SET AL32UTF8;
ALTER DATABASE CHARACTER SET AL32UTF8
ERROR at line 1:
ORA-12712: new character set must be a superset of old character set
SQL> select * from v$nls_parameters where parameter like '%CHARACTERSET%';
PARAMETER
VALUE
NLS_CHARACTERSET
WE8MSWIN1252
NLS_NCHAR_CHARACTERSET

Unable to alter character set from WE8MSWIN1252 to AL32UTF8

Hi,
I am trying to migrate some tables to my database.
On the source DB, the character set is AL32UTF8
On My database, the character set is WE8MSWIN1252.
When I tried to alter the character set, I get this error message:
ALTER DATABASE CHARACTER SET AL32UTF8
ERROR at line 1:
ORA-12712: new character set must be a superset of old character set
Any help? Thanks.

Pl refrain from posting duplicate threads :-)
Unable to migrate table, character set from WE8MSWIN1252 to AL32UTF8
Srini

Change existing character set

Hi All,
I want to change current character set of my DB.
My DB version is 8.1.7 and character set is US7ASCII.
This character set does not support to store Euro symbol (â¬). So I want to change to another charset.
Currently I also have another DB, version 9.2.0 and charset is AL32UTF8 and National charset is AL16UTF16. This charset supports â¬ symbol.
But when I tried change chatset of 8i US7ASCII to AL32UTF8, an error happened: "ORA-12712 new character set must be a supersetof old character set".
Character set WE8ISO8859P1 support â¬ symbol.
I tried to change character set of 8i from US7ASCII to WE8ISO8859P1 successfully but change character set of 9i from AL32UTF8 to WE8ISO8859P1 unsuccessfully, error is "ORA-12712 new character set must be a supersetof old character set".
Please let me know which character set is superset of US7ASCII and AL32UTF8.
I want to change character set of 8i and 9i to the same another character set that support â¬ symbol.
Thanks in advanced,
Thi Nguyen

This is from Oracle metalink documentation.Hope this helps:
=========================================
This note defines character set combinations which are valid for the 'ALTER DATABASE CHARACTER SET xxxx;' command. A superset, in this context, is a character set where every character in the subset character set is defined and is defined at the same code point. Changing the Database Character Set or the Database National Character Set . If the change you want to do (change from <current> -> <new> characterset) is not listed here, then you need to use Export/Import. Export/Import and NLS Considerations for more info. SCOPE & APPLICATION ------------------- This note is relevant to anyone wishing to change the database character set or the database national character set. Note : this note is relevant from 8.1.6 to 9.2.0. Changing Database Character set - valid superset definitions ------------------------------------------------------------ Where the current character set does not have a corresponding match in the new character set column, it is not possible to change the definition by the above command alone; export / import into a new database with the new character set (not in the following list) will be required. 8.1.6 Subset/Superset Pairs =========================== A. Current Char set B. New Char set (Superset of A.) ------------------- -------------------------------- US7ASCII WE8DEC US7ASCII US8PC437 US7ASCII WE8PC850 US7ASCII IN8ISCII US7ASCII WE8PC858 US7ASCII WE8ISO8859P1 US7ASCII EE8ISO8859P2 US7ASCII SE8ISO8859P3 US7ASCII NEE8ISO8859P4 US7ASCII CL8ISO8859P5 US7ASCII AR8ISO8859P6 US7ASCII EL8ISO8859P7 US7ASCII IW8ISO8859P8 US7ASCII WE8ISO8859P9 US7ASCII NE8ISO8859P10 US7ASCII TH8TISASCII US7ASCII BN8BSCII US7ASCII VN8VN3 US7ASCII VN8MSWIN1258 US7ASCII WE8ISO8859P15 US7ASCII WE8NEXTSTEP US7ASCII AR8ASMO708PLUS US7ASCII EL8DEC US7ASCII TR8DEC US7ASCII LA8PASSPORT US7ASCII BG8PC437S US7ASCII EE8PC852 US7ASCII RU8PC866 US7ASCII RU8BESTA US7ASCII IW8PC1507 US7ASCII RU8PC855 US7ASCII TR8PC857 US7ASCII CL8MACCYRILLICS US7ASCII WE8PC860 US7ASCII IS8PC861 US7ASCII EE8MACCES US7ASCII EE8MACCROATIANS US7ASCII TR8MACTURKISHS US7ASCII EL8MACGREEKS US7ASCII IW8MACHEBREWS US7ASCII EE8MSWIN1250 US7ASCII CL8MSWIN1251 US7ASCII ET8MSWIN923 US7ASCII BG8MSWIN US7ASCII EL8MSWIN1253 US7ASCII IW8MSWIN1255 US7ASCII LT8MSWIN921 US7ASCII TR8MSWIN1254 US7ASCII WE8MSWIN1252 US7ASCII BLT8MSWIN1257 US7ASCII N8PC865 US7ASCII BLT8CP921 US7ASCII LV8PC1117 US7ASCII LV8PC8LR US7ASCII LV8RST104090 US7ASCII CL8KOI8R US7ASCII BLT8PC775 US7ASCII WE8DG US7ASCII WE8NCR4970 US7ASCII WE8ROMAN8 US7ASCII WE8MACROMAN8S US7ASCII TH8MACTHAIS US7ASCII HU8CWI2 US7ASCII EL8PC437S US7ASCII LT8PC772 US7ASCII LT8PC774 US7ASCII EL8PC869 US7ASCII EL8PC851 US7ASCII CDN8PC863 US7ASCII HU8ABMOD US7ASCII AR8ASMO8X US7ASCII AR8NAFITHA711T US7ASCII AR8SAKHR707T US7ASCII AR8MUSSAD768T US7ASCII AR8ADOS710T US7ASCII AR8ADOS720T US7ASCII AR8APTEC715T US7ASCII AR8NAFITHA721T US7ASCII AR8HPARABIC8T US7ASCII AR8NAFITHA711 US7ASCII AR8SAKHR707 US7ASCII AR8MUSSAD768 US7ASCII AR8ADOS710 US7ASCII AR8ADOS720 US7ASCII AR8APTEC715 US7ASCII AR8MSAWIN US7ASCII AR8NAFITHA721 US7ASCII AR8SAKHR706 US7ASCII AR8ARABICMACS US7ASCII LA8ISO6937 US7ASCII JA16VMS US7ASCII JA16EUC US7ASCII JA16SJIS US7ASCII KO16KSC5601 US7ASCII KO16KSCCS US7ASCII KO16MSWIN949 US7ASCII ZHS16CGB231280 US7ASCII ZHS16GBK US7ASCII ZHT32EUC US7ASCII ZHT32SOPS US7ASCII ZHT16DBT US7ASCII ZHT32TRIS US7ASCII ZHT16BIG5 US7ASCII ZHT16CCDC US7ASCII ZHT16MSWIN950 US7ASCII AL24UTFFSS US7ASCII UTF8 US7ASCII JA16TSTSET2 US7ASCII JA16TSTSET 8.1.7 Additions =============== US7ASCII ZHT16HKSCS US7ASCII KO16TSTSET WE8DEC TR8DEC WE8DEC WE8NCR4970 WE8PC850 WE8PC858 D7DEC D7SIEMENS9780X I7DEC I7SIEMENS9780X WE8ISO8859P1 WE8MSWIN1252 AR8ISO8859P6 AR8ASMO708PLUS AR8ISO8859P6 AR8ASMO8X IW8EBCDIC424 IW8EBCDIC1086 IW8EBCDIC1086 IW8EBCDIC424 LV8PC8LR LV8RST104090 DK7SIEMENS9780X N7SIEMENS9780X N7SIEMENS9780X DK7SIEMENS9780X I7SIEMENS9780X I7DEC D7SIEMENS9780X D7DEC WE8NCR4970 WE8DEC WE8NCR4970 TR8DEC AR8SAKHR707T AR8SAKHR707 AR8MUSSAD768T AR8MUSSAD768 AR8ADOS720T AR8ADOS720 AR8NAFITHA711 AR8NAFITHA711T AR8SAKHR707 AR8SAKHR707T AR8MUSSAD768 AR8MUSSAD768T AR8ADOS710 AR8ADOS710T AR8ADOS720 AR8ADOS720T AR8APTEC715 AR8APTEC715T AR8NAFITHA721 AR8NAFITHA721T AR8ARABICMAC AR8ARABICMACT AR8ARABICMACT AR8ARABICMAC KO16KSC5601 KO16MSWIN949 WE16DECTST2 WE16DECTST WE16DECTST WE16DECTST2 9.0.1 Additions =============== US7ASCII BLT8ISO8859P13 US7ASCII CEL8ISO8859P14 US7ASCII CL8ISOIR111 US7ASCII CL8KOI8U US7ASCII AL32UTF8 BLT8CP921 BLT8ISO8859P13 US7ASCII AR8MSWIN1256 UTF8 AL32UTF8 (added in patchset 9.0.1.2) Character Set Subset/Superset Pairs Obsolete from 9.0.1 ======================================================= US7ASCII AR8MSAWIN AR8ARABICMAC AR8ARABICMACT 9.2.0 Additions =============== US7ASCII JA16EUCTILDE US7ASCII JA16SJISTILDE US7ASCII ZHS32GB18030 US7ASCII ZHT32EUCTST WE8ISO8859P9 TR8MSWIN1254 LT8MSWIN921 BLT8ISO8859P13 LT8MSWIN921 BLT8CP921 BLT8CP921 LT8MSWIN921 AR8ARABICMAC AR8ARABICMACT ZHT32EUC ZHT32EUCTST UTF8 AL32UTF8 Character Set Subset/Superset Pairs Obsolete from 9.2.0 ======================================================= LV8PC8LR LV8RST104090

Default character set

I installed the database 10.2.01 with basic installation (not advanced option).
what is the default charater set in the basic installation?
how to show character set in command line?
Can I change it to AL32UTF8?
like:
SQL>alter database character set AL32UTF8;
Thanks

thanks.
I'm using Linux
So default character is "WE8ISO8859P1".
But it seems I can not alter to AL32UTF8, which has the globalization support.
SQL> select value from nls_database_parameters where parameter='NLS_CHARACTERSET';
VALUE
WE8ISO8859P1
SQL> alter database character set AL32UTF8;
alter database character set AL32UTF8
ERROR at line 1:
ORA-12712: new character set must be a superset of old character set
----------------------

Change character set

Hi
is anyone can tell me how to change characterset.
i try with alter session but it doesnt work.
thanks

Article from Metalink
Doc ID: Note:66320.1
Subject: Changing the Database Character Set or the Database National Character Set
Type: BULLETIN
Status: PUBLISHED
 Content Type: TEXT/PLAIN
Creation Date: 23-OCT-1998
Last Revision Date: 12-DEC-2003
PURPOSE ======= To explain how to change the database character set or national character set of an existing Oracle8(i) or Oracle9i database without having to recreate the database. 1. SCOPE & APPLICATION ====================== The method described here is documented in the Oracle 8.1.x and Oracle9i documentation. It is not documented but it can be used in version 8.0.x. It does not work in Oracle7. The database character set is the character set of CHAR, VARCHAR2, LONG, and CLOB data stored in the database columns, and of SQL and PL/SQL text stored in the Data Dictionary. The national character set is the character set of NCHAR, NVARCHAR2, and NCLOB data. In certain database configurations the CLOB and NCLOB data are stored in the fixed-width Unicode encoding UCS-2. If you are using CLOB or NCLOB please make sure you read section "4. HANDLING CLOB AND NCLOB COLUMNS" below in this document. Before changing the character set of a database make sure you understand how Oracle deals with character sets. Before proceeding please refer to [NOTE:158577.1] "NLS_LANG Explained (How Does Client-Server Character Conversion Work?)". See also [NOTE:225912.1] "Changing the Database Character Set - an Overview" for general discussion about various methods of migration to a different database character set. If you are migrating an Oracle Applications instance, read [NOTE:124721.1] "Migrating an Applications Installation to a New Character Set" for specific steps that have to be performed. If you are migrating from 8.x to 9.x please have a look at [NOTE:140014.1] "ALERT: Oracle8/8i to Oracle9i Using New "AL16UTF16"" and other referenced notes below. Before using the method described in this note it is essential to do a full backup of the database and to use the Character Set Scanner utility to check your data. See the section "2. USING THE CHARACTER SET SCANNER" below. Note that changing the database or the national character set as described in this document does not change the actual character codes, it only changes the character set declaration. If you want to convert the contents of the database (character codes) from one character set to another you must use the Oracle Export and Import utilities. This is needed, for example, if the source character set is not a binary subset of the target character set, i.e. if a character exists in the source and in the target character set but not with the same binary code. All binary subset-superset relationships between characters sets recognized by the Oracle Server are listed in [NOTE:119164.1] "Changing Database Character Set - Valid Superset Definitions". Note: The varying width character sets (like UTF8) are not supported as national character sets in Oracle8(i) (see [NOTE:62107.1]). Thus, changing the national character set from a fixed width character set to a varying width character set is not supported in Oracle8(i). NCHAR types in Oracle8 and Oracle8i were designed to support special Oracle specific fixed-width Asian character sets, that were introduced to provide higher performance processing of Asian character data. Examples of these character sets are : JA16EUCFIXED ,JA16SJISFIXED , ZHT32EUCFIXED. For a definition of varying width character sets see also section "4. HANDLING CLOB AND NCLOB COLUMNS" below. WARNING: Do not use any undocumented Oracle7 method to change the database character set of an Oracle8(i) or Oracle9i database. This will corrupt the database. 2. USING THE CHARACTER SET SCANNER ================================== Character data in the Oracle 8.1.6 and later database versions can be efficiently checked for possible character set migration problems with help of the Character Set Scanner utility. This utility is included in the Oracle Server 8.1.7 software distribution and the newest Character Set Scanner version can be downloaded from the Oracle Technology Network site, http://otn.oracle.com The Character Set Scanner on OTN is available for limited number of platforms only but it can be used with databases on other platforms in the client/server configuration -- as long as the database version matches the Character Set Scanner version and platforms are either both ASCII-based or both EBCDIC-based. It is recommended to use the newest Character Set Scanner version available from the OTN site. The Character Set Scanner is documented in the following manuals: - "Oracle8i Documentation Addendum, Release 3 (8.1.7)", Chapter 3 - "Oracle9i Globalization Support Guide, Release 1 (9.0.1)", Chapter 10 - "Oracle9i Database Globalization Support Guide, Release 2 (9.2)", Chapter 11 Note: The Character Set Scanner coming with Oracle 8.1.7 and Oracle 9.0.1 does not have a separate version number. It reports the database release number in its banner. This version of the Scanner does not check for illegal character codes in a database if the FROMCHAR and TOCHAR (or FROMNCHAR and TONCHAR) parameters have the same value (i.e. you simulate migration from a character set to itself). The Character Set Scanner 1.0, available on OTN, reports its version number as x.x.x.1.0, where x.x.x is the database version number. This version adds a few bug fixes and it supports FROMCHAR=TOCHAR provided it is not UTF8. The Character Set Scanner 1.1, available on OTN and with Release 2 (9.2) of the Oracle Server, reports its version number as v1.1 followed by the database version number. This version adds another bug fixes and the full support for FROMCHAR=TOCHAR. None of the above versions of the Scanner can correctly analyze CLOB or NCLOB values if the database or the national character set, respectively, is multibyte. The Scanner reports such values randomly as Convertible or Lossy. The version 1.2 of the Scanner will mark all such values as Changeless (as they are always stored in the Unicode UCS-2 encoding and thus they do not change when the database or national character set is changed from one multibyte to another). Character Set Scanner 2.0 will correctly check CLOBs and NCLOBs for possible data loss when migrating from a multibyte character set to its subset. To verify that your database contains only valid codes, specify the new database character set in the TOCHAR parameter and/or the new national character set in the TONCHAR parameter. Specify FULL=Y to scan the whole database. Set ARRAY and PROCESS parameters depending on your system's resources to speed up the scanning. FROMCHAR and FROMNCHAR will default to the original database and national character sets. The Character Set Scanner should report only Changless data in both the Data Dictionary and in application data. If any Convertible or Exceptional data are reported, the ALTER DATABASE [NATIONAL] CHARACTER SET statement must not be used without further investigation of the source and type of these data. In situations in which the ALTER DATABASE [NATIONAL] CHARACTER SET statement is used to repair an incorrect database character set declaration rather than to simply migrate to a new wider character set, you may be advised by Oracle Support Services analysts to execute the statement even if Exceptional data are reported. For more information see also [NOTE:225912.1] "Changing the Database Character Set - a short Overview". 3. CHANGING THE DATABASE OR THE NATIONAL CHARACTER SET ====================================================== Oracle8(i) introduces a new documented method of changing the database and national character sets. The method uses two SQL statements, which are described in the Oracle8i National Language Support Guide: ALTER DATABASE [<db_name>] CHARACTER SET <new_character_set> ALTER DATABASE [<db_name>] NATIONAL CHARACTER SET <new_NCHAR_character_set> The database name is optional. The character set name should be specified without quotes, for example: ALTER DATABASE CHARACTER SET WE8ISO8859P1 To change the database character set perform the following steps. Note that some of them have been erroneously omitted from the Oracle8i documentation: 1. Use the Character Set Scanner utility to verify that your database contains only valid character codes -- see "2. USING THE CHARACTER SET SCANNER" above. 2. If necessary, prepare CLOB columns for the character set change -- see "4. HANDLING CLOB AND NCLOB COLUMNS" below. Omitting this step can lead to corrupted CLOB/NCLOB values in the database. If SYS.METASTYLESHEET (STYLESHEET) is populated (9i and up only) then see [NOTE:213015.1] "SYS.METASTYLESHEET marked as having convertible data (ORA-12716 when trying to convert character set)" for the actions that need to be taken. 3. Make sure the parallel_server parameter in INIT.ORA is set to false or it is not set at all. 4. Execute the following commands in Server Manager (Oracle8) or sqlplus (Oracle9), connected as INTERNAL or "/ AS SYSDBA": SHUTDOWN IMMEDIATE; -- or NORMAL <do a full database backup> STARTUP MOUNT; ALTER SYSTEM ENABLE RESTRICTED SESSION; ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0; ALTER SYSTEM SET AQ_TM_PROCESSES=0; ALTER DATABASE OPEN; ALTER DATABASE CHARACTER SET <new_character_set>; SHUTDOWN IMMEDIATE; -- OR NORMAL STARTUP RESTRICT; 5. Restore the parallel_server parameter in INIT.ORA, if necessary. 6. Execute the following commands: SHUTDOWN IMMEDIATE; -- OR NORMAL STARTUP; The double restart is necessary in Oracle8(i) because of a SGA initialization bug, fixed in Oracle9i. 7. If necessary, restore CLOB columns -- see "4. HANDLING CLOB AND NCLOB COLUMNS" below. To change the national character set replace the ALTER DATABASE CHARACTER SET statement with ALTER DATABASE NATIONAL CHARACTER SET. You can issue both statements together if you wish. Error Conditions ---------------- A number of error conditions may be reported when trying to change the database or national character set. In Oracle8(i) the ALTER DATABASE [NATIONAL] CHARACTER SET statement will return: ORA-01679: database must be mounted EXCLUSIVE and not open to activate - if you do not enable restricted session - if you startup the instance in PARALLEL/SHARED mode - if you do not set the number of queue processes to 0 - if you do not set the number of AQ time manager processes to 0 - if anybody is logged in apart from you. This error message is misleading. The command requires the database to be open but only one session, the one executing the command, is allowed. For the above error conditions Oracle9i will report one of the errors: ORA-12719: operation requires database is in RESTRICTED mode ORA-12720: operation requires database is in EXCLUSIVE mode ORA-12721: operation cannot execute when other sessions are active Oracle9i can also report: ORA-12718: operation requires connection as SYS if you are not connect as SYS (INTERNAL, "/ AS SYSDBA"). If the specified new character set name is not recognized, Oracle will report one of the errors: ORA-24329: invalid character set identifier ORA-12714: invalid national character set specified ORA-12715: invalid character set specified The ALTER DATABASE [NATIONAL] CHARACTER SET command will only work if the old character set is considered a binary subset of the new character set. Oracle Server 8.0.3 to 8.1.5 recognizes US7ASCII as the binary subset of all ASCII-based character sets. It also treats each character set as a binary subset of itself. No other combinations are recognized. Newer Oracle Server versions recognize additional subset/superset combinations, which are listed in [NOTE:119164.1]. If the old character set is not recognized as a binary subset of the new character set, the ALTER DATABASE [NATIONAL] CHARACTER SET statement will return: - in Oracle 8.1.5 and above: ORA-12712: new character set must be a superset of old character set - in Oracle 8.0.5 and 8.0.6: ORA-12710: new character set must be a superset of old character set - in Oracle 8.0.3 and 8.0.4: ORA-24329: invalid character set identifier You will also get these errors if you try to change the characterset of a US7ASCII database that was started without a (correct) ORA_NLSxx parameter. See [NOTE:77442.1] It may be necessary to switch off the superset check to allow changes between formally incompatible character sets to solve certain character set problems or to speed up migration of huge databases. Oracle Support Services may pass the necessary information to customers after verifying the safety of the change for the customers' environments. If in Oracle9i an ALTER DATABASE NATIONAL CHARACTER SET is issued and there are N-type colums who contain data then this error is returned: ORA-12717:Cannot ALTER DATABASE NATIONAL CHARACTER SET when NCLOB data exists The error only speaks about Nclob but Nchar and Nvarchar2 are also checked see [NOTE:2310895.9] for bug [BUG:2310895] 4. HANDLING CLOB AND NCLOB COLUMNS ================================== Background ---------- In a fixed width character set codes of all characters have the same number of bytes. Fixed width character sets are: all single-byte character sets and those multibyte character sets which have names ending with 'FIXED'. In Oracle9i the character set AL16UTF16 is also fixed width. In a varying width character set codes of different characters may have different number of bytes. All multibyte character sets except those with names ending with FIXED (and except Oracle9i AL16UTF16 character set) are varying width. Single-byte character sets are character sets with names of the form xxx7yyyyyy and xxx8yyyyyy. Each character code of a single-byte character set occupies exactly one byte. Multibyte character sets are all other character sets (including UTF8). Some -- usually most -- character codes of a multibyte character set occupy more than one byte. CLOB values in a database whose database character set is fixed width are stored in this character set. CLOB values in an Oracle 8.0.x database whose database character set is varying width are not allowed. They have to be NULL. CLOB values in an Oracle >= 8.1.5 database whose database character set is varying width are stored in the fixed width Unicode UCS-2 encoding. The same holds for NCLOB values and the national character set. The UCS-2 storage format of character LOB values, as implemented in Oracle8i, ensures that calculation of character positions in LOB values is fast. Finding the byte offset of a character stored in a varying width character set would require reading the whole LOB value up to this character (possibly 4GB). In the fixed width character sets the byte offsets are simply character offsets multiplied by the number of bytes in a character code. In UCS-2 byte offsets are simply twice the character offsets. As the Unicode character set contains all characters defined in any other Oracle character set, there is no data loss when a CLOB/NCLOB value is converted to UCS-2 from the character set in which it was provided by a client program (usually the NLS_LANG character set). CLOB Values and the Database Character Set Change ------------------------------------------------- In Oracle 8.0.x CLOB values are invalid in varying width character sets. Thus you must delete all CLOB column values before changing the database character set to a varying width character set. In Oracle 8.1.5 and later CLOB values are valid in varying width character sets but they are converted to Unicode UCS-2 before being stored. But UCS-2 encoding is not a binary superset of any other Oracle character set. Even codes of the basic ASCII characters are different, e.g. single-byte code for "A"=0x41 becomes two-byte code 0x0041. This implies that even if the new varying width character set is a binary superset of the old fixed width character set and thus VARCHAR2/LONG character codes remain valid, the fixed width character codes in CLOB values will not longer be valid in UCS-2. As mentioned above, the ALTER DATABASE [NATIONAL] CHARACTER SET statement does not change character codes. Thus, before changing a fixed width database character set to a varying width character set (like UTF8) in Oracle 8.1.5 or later, you first have to export all tables containing non-NULL CLOB columns, then truncate these tables, then change the database character set and, finally, import the tables back to the database. The import step will perform the required conversion. If you omit the steps above, the character set change will succeed in Oracle8(i) (Oracle9i disallows the change in such situation) and the CLOBs may appear to be correctly legible but as their encoding is incorrect, they will cause problems in further operations. For example, CREATE TABLE AS SELECT will not correctly copy such CLOB columns. Also, after installation of the 8.1.7.3 server patchset the CLOB columns will not longer be legible. LONG columns are always stored in the database character set and thus they behave like CHAR/VARCHAR2 in respect to the character set change. BLOBs and BFILEs are binary raw datatypes and their processing does not depend on any Oracle character set setting. NCLOB Values and the National Character Set Change -------------------------------------------------- The above discussion about changing the database character set and exporting and importing CLOB values is theoretically applicable to the change of the national character set and to NCLOB values. But as varying width character sets are not supported as national character sets in Oracle8(i), changing the national character set from a fixed width character set to a varying width character set is not supported at all. Preparing CLOB Columns for the Character Set Change --------------------------------------------------- Take a backup of the database. If using Advanced Replication or deferred transactions functionality, make sure that there are no outstanding deferred transactions with CLOB parameters, i.e. DEFLOB view must have no rows with non-NULL CLOB_COL column; to make sure that replication environment remains consistent use only recommended methods of purging deferred transaction queue, preferably quiescing the replication environment. Then: - If changing the database character set from a fixed width character set to a varying with character set in Oracle 8.0.x, set all CLOB column values to NULL -- you are not allowed to use CLOB columns after the character set change. - If changing the database character set from a fixed width character set to a varying width character set in Oracle 8.1.5 or later, perform table-level export of all tables containing CLOB columns, including SYSTEM's tables. Set NLS_LANG to the old database character set for the Export utility. Then truncate these tables. Restoring CLOB Columns after the Character Set Change ----------------------------------------------------- In Oracle 8.1.5 or later, after changing the character set as described above (steps 3. to 6.), restore CLOB columns exported in step 2. by importing them back into the database. Set NLS_LANG to the old database character set for the Import utility to avoid IMP-16 errors and data loss. RELATED DOCUMENTS: ================== [NOTE:13856.1] V7: Changing the Database Character Set -- This note has limited distribution, please contact Oracle Support [NOTE:62107.1] The National Character Set in Oracle8 [NOTE:119164.1] Changing Database Character set - Valid Superset definitions [NOTE:118242.1] ALERT: Changing the Database or National Character Set Can Corrupt LOB Values <Note.158577.1> NLS_LANG Explained (How Does Client-Server Character Conversion Work?) [NOTE:140014.1] ALERT: Oracle8/8i to Oracle9i using New "AL16UTF16" [NOTE:159657.1] Complete Upgrade Checklist for Manual Upgrades from 8.X / 9.0.1 to Oracle9i (incl. 9.2) [NOTE:124721.1] Migrating an Applications Installation to a New Character Set Oracle8i National Language Support Guide Oracle8i Release 3 (8.1.7) Readme - Section 18.12 "Restricted ALTER DATABASE CHARACTER SET Command Support (CLOB and NCLOB)" Oracle8i Documentation Addendum, Release 3 (8.1.7) - Chapter 3 "New Character Set Scanner Utility" Oracle8i Application Developer's Guide - Large Objects (LOBs), Release 2 - Chapter 2 "Basic Components" Oracle8 Application Developer's Guide, Release 8.0 - Chapter 6 "Large Objects (LOBs)", Section "Introduction to LOBs" Oracle9i Globalization Guide, Release 1 (9.0.1) Oracle9i Database Globalization Guide, Release 2 (9.2) For further NLS / Globalization information you may start here: [NOTE:150091.1] Globalization Technology (NLS) Library index .
 Copyright (c) 1995,2000 Oracle Corporation. All Rights Reserved. Legal Notices and Terms of Use.
Joel P�rez

Error while running package ORA-06553: PLS-553 character set name is not re

Hi all.
I have a problem with a package, when I run it returns me code error:
ORA-06552: PL/SQL: Compilation unit analysis terminated
ORA-06553: PLS-553: character set name is not recognized
The full context of the problem is this:
Previously I had a developing data base, then was migrated to a new server. After that I started to receive the error, so I began to check for the solution.
My first move was compare the “old database” with the “new database”, so I check the nls parameters, and this was the result:
select * from nls_database_parameters;
Result from the old
NLS_LANGUAGE     AMERICAN
NLS_TERRITORY     AMERICA
NLS_CURRENCY     $
NLS_ISO_CURRENCY     AMERICA
NLS_NUMERIC_CHARACTERS     .,
NLS_CHARACTERSET     US7ASCII
NLS_CALENDAR     GREGORIAN
NLS_DATE_FORMAT     DD-MON-RR
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
Result from the new
NLS_LANGUAGE     AMERICAN
NLS_TERRITORY     AMERICA
NLS_CURRENCY     $
NLS_ISO_CURRENCY     AMERICA
NLS_NUMERIC_CHARACTERS     .,
NLS_CHARACTERSET     US7ASCII
NLS_CALENDAR     GREGORIAN
NLS_DATE_FORMAT     DD-MON-RR
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
As the result was identical, I decided to look for more info in the log file of the new database. What I find was this:
Database Characterset is US7ASCII
Threshold validation cannot be done before catproc is loaded.
Threshold validation cannot be done before catproc is loaded.
alter database character set INTERNAL_CONVERT WE8MSWIN1252
Updating character set in controlfile to WE8MSWIN1252
Synchronizing connection with database character set information
Refreshing type attributes with new character set information
Completed: alter database character set INTERNAL_CONVERT WE8MSWIN1252
alter database character set US7ASCII
ORA-12712 signalled during: alter database character set US7ASCII...
alter database character set US7ASCII
ORA-12712 signalled during: alter database character set US7ASCII...
Errors in file e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_3132.trc:
Regards

Ohselotl wrote:
Hi all.
I have a problem with a package, when I run it returns me code error:
ORA-06552: PL/SQL: Compilation unit analysis terminated
ORA-06553: PLS-553: character set name is not recognized
The full context of the problem is this:
Previously I had a developing data base, then was migrated to a new server. After that I started to receive the error, so I began to check for the solution.
My first move was compare the “old database” with the “new database”, so I check the nls parameters, and this was the result:
select * from nls_database_parameters;
Result from the old
NLS_LANGUAGE     AMERICAN
NLS_TERRITORY     AMERICA
NLS_CURRENCY     $
NLS_ISO_CURRENCY     AMERICA
NLS_NUMERIC_CHARACTERS     .,
NLS_CHARACTERSET     US7ASCII
NLS_CALENDAR     GREGORIAN
NLS_DATE_FORMAT     DD-MON-RR
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
Result from the new
NLS_LANGUAGE     AMERICAN
NLS_TERRITORY     AMERICA
NLS_CURRENCY     $
NLS_ISO_CURRENCY     AMERICA
NLS_NUMERIC_CHARACTERS     .,
NLS_CHARACTERSET     US7ASCII
NLS_CALENDAR     GREGORIAN
NLS_DATE_FORMAT     DD-MON-RR
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
As the result was identical, I decided to look for more info in the log file of the new database. What I find was this:
Database Characterset is US7ASCII
Threshold validation cannot be done before catproc is loaded.
Threshold validation cannot be done before catproc is loaded.
alter database character set INTERNAL_CONVERT WE8MSWIN1252
Updating character set in controlfile to WE8MSWIN1252
Synchronizing connection with database character set information
Refreshing type attributes with new character set information
Completed: alter database character set INTERNAL_CONVERT WE8MSWIN1252
*********************************************************************This is an unsupported method to change the characterset of a database - it has caused the corruption of your database beyond repair. Hopefully you have a backup you can recover from. Whoever did this did not know what they were doing.
alter database character set US7ASCII
ORA-12712 signalled during: alter database character set US7ASCII...
alter database character set US7ASCII
ORA-12712 signalled during: alter database character set US7ASCII...
Errors in file e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_3132.trc:
RegardsThe correct way to change the characterset of a database is documented - http://docs.oracle.com/cd/B19306_01/server.102/b14225/ch11charsetmig.htm#sthref1476
HTH
Srini

The ADO NET Source was unable to process the data. ORA-64203: Destination buffer too small to hold CLOB data after character set conversion.

We developed a SSIS Package to pull the data From Oracle source to Sql Server 2012. Here we used ADO.Net source to pull the records from Source but getting the below error after pulling some 40K records.
[ADO NET Source [2]] Error: The ADO NET Source was unable to process the data. ORA-64203: Destination buffer too small to hold CLOB data after character set conversion.
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED.
The PrimeOutput method on ADO NET Source returned error code 0xC02090F5.
The component returned a failure code when the pipeline engine called PrimeOutput().
The meaning of the failure code is defined by the component,
but the error is fatal and the pipeline stopped executing.
There may be error messages posted before this with more
information about the failure.
Anything that we can do to fix this?

Hi,
Tried both....
* Having schema type as Nvarchar(max). - Getting the same error.
* Instead of ADO.Net Source used OLEDB Source with driver as " Oracle Provide for OLE DB" Getting error as below.
[OLE DB Source [478]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on OLE DB Source returned error code 0xC0202009. The component returned a failure
code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the
failure.
Additional Info:
* Here the Source task is getting failed not the conversion or destination task.
Thanks,
Loganathan A.

ORA-01482: unsupported character set

Similar Messages

Maybe you are looking for