Changing database character set

Can anyone help with the way to change the database character set.
I am runn into problem while exporting with error message exp-00091
Thanks

You don't need to change the database character set. You have only to set the correct character set at
OS level before doing the export. Execute the following at Sql prompt as DBA :
SQL> select * from v$nls_parameters
2* where parameter in ('NLS_LANGUAGE', 'NLS_TERRITORY', 'NLS_CHARACTERSET')
SQL> /
PARAMETER            VALUE
NLS_LANGUAGE         AMERICAN
NLS_TERRITORY        AMERICA
NLS_CHARACTERSET     WE8ISO8859P15
SQL>then at OS prompt :
$ export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P15
$ exp ..............
Of course you have to use your values.

Similar Messages

Changing database character set from US7ASCII to AL32UTF8

Our database is running on Oracle database 10.1.0.4.0 (AIX) The following are its parameters:
SQL> select value from NLS_DATABASE_PARAMETERS where parameter='NLS_CHARACTERSET';
VALUE
US7ASCII
We would like to change the database character set to AL32UTF8. After following Metalink notes: 260192.1 (which helped us resolve "Lossy" and "Truncated" data, the final output of the CSSCAN utility is:
[Scan Summary]
All character type data in the data dictionary are convertible to the new character set
All character type application data are convertible to the new character set
[Data Dictionary Conversion Summary]
The data dictionary can be safely migrated using the CSALTER script
We have no (0) Truncation and Lossy entries on the .txt file. We only have Changeless and Convertible. Now accdg to the documentation, we can do a FULL EXP and FULL IMP. But it did not detail how to do the conversion on the same database. The discussion on the document tells how to do it from one database to another database. But how about on the same database?
We cannot use CSALTER as stated on the document.
(Step 6
Step 12
12.c) When using Csalter/Alter database to go to AL32UTF8 and there was NO "Truncation" data, only "Convertible" and "Changeless" in the csscan done in point 4:)
After performing a FULL export of the database, how can we change its character set? What do we need to do the the existing database to change its character set to AL32UTF8 before we import back our dump file into the same database?
Please help.

There you are! Thanks! Seems like I am right in my understanding about the Oracle Official Documentation. Thanks!
Hmmmmm...when you say:
*"you can do selective export of only convertible tables, truncate the tables, use CSALTER, and re-import."*
This means that:
1. After running csscan on database PROD, i will take note of the convertible tables in the .txt output file.
2. Perform selective EXPORT on PROD (EXP the convertible tables)
3. Truncate the convertible tables on PROD database
4. Use CSALTER on PROD database
5. Re-import the tables into PROD database
6. Housekeeping.
Will you tell me if these steps are the correct one? Based on our scenario: This is what i have understood referring to the Official Doc.
Am i correct?
I really appreciate your help Sergiusz.

Want to change Database Character set

I have installed Oracle 10g in my system.
But while installing Oracle 10g i have selected the Database Character set as English but now i want it to change it to West European WE8MSWIN1252
can anyboby suggest how to modify it.

http://oracle.ittoolbox.com/documents/popular-q-and-a/changing-the-character-set-of-an-oracle-database-1601
Best Practices
http://www.oracle.com/technology/tech/globalization/pdf/TWP_Character_Set_Migration_Best_Practices_10gR2.pdf

How to change Database character set?

Hi,
We are planning to make a clone of production Database which has:
select value$ from sys.props$ where name='NLS_CHARACTERSET';
AL32UTF8
We have set up a new server for that purpose and installed database, but by default it has
select value$ from sys.props$ where name='NLS_CHARACTERSET';
WE8ISO8859P1
So after making full import from full backup file we have some broken character in database.
How can I change from WE8ISO8859P1 to AL32UTF8?
I expect that I need to shutdown the clone database or even make from scratch full import.
Thanks

I made a full backup from production database which has AL32UTF8
My new database is fresh and it has WE8ISO8859P1
I think the reason why I'm having some corrupted characters is because of difference in Character set between two database, right?
so I will need to change new database Character set to AL32UTF8 then make again full import.

Change Database Character Set to Arabic!

Dear All,
My database is Oracle 11gR2 On Linux platform.
I am trying to change the character set of my database to store Arabic characters.
This is what I am doing:
SHUTDOWN IMMEDIATE;
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 INTERNAL_USE AR8ISO8859P6;
SHUTDOWN IMMEDIATE;
STARTUP;
When i check:
SQL> select value from NLS_DATABASE_PARAMETERS where parameter='NLS_CHARACTERSET';
VALUE
AR8ISO8859P6
But still when i query data it shows it like this:
"¿¿¿¿¿¿ç ¿¿ê ¿¿¿¿çê¿ ¿¿¿¿ ¿¿¿ ¿¿¿¿¿¿ ¿¿¿¿ ¿¿¿èê¿ ¿¿¿è¿ ¿¿¿¿ê¿¿ ¿¿¿ ¿¿â¿¿ ¿¿é ¿¿¿ è¿¿¿ ¿ê ¿¿¿¿ êè¿ ¿¿¿¿¿¿ 28/9 ¿ê ¿ ¿¿é ¿¿¿¿ ¿è¿¿ê èç¿¿¿ ¿è¿¿¿ âê¿¿ ¿¿¿ è¿¿â¿ ¿¿è¿"
Can you help me to understand where is the problem and how to get through it.
Regards, Imran

Why on earth are you using the undocumented INTERNAL_USE command? The name alone should strongly imply that this isn't something that normal users should be playing with. It is extremely likely that you've corrupted your database.
Do you have a backup of your database taken before you corrupted it? If so, can you restore that backup? Once you do that, tell us what character set you're starting with. If you are implying that there is existing data in the database, what character set is that data encoded with? Can you DUMP the data to verify this?
Justin

OWB 11.1.0.6.0 with database character set AL32UTF8 is not working

Hi ,
we are working for a project for Turkey.
if we insert Turkish characters in database ,in sqldevelpoer we are able to see the correct data. but when i load a file from preprocessor in OWB Process Flow, the characters which are in Turkish got changed to different characters in database. our databse character set is AL32UTF8. could you please throw some light on this please.
Many thanks,
kiranmai.

hi ,
ya we are using the correct dataset only in preprocessr configuration. actually it was a problem with OWB only ,
i have changed database character set to WE8ISO8859P9,then i am able to se correct Trukey chars in database. i think it was a SR for oracle .

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

How to Change National character set for a database

Hi All,
My database is Oracle 10G. Stand alone DB.
National character set for my DB is "WE8ISO8859P1" and need to change national character set to UTF8.
Need Help on this.
Thanks in advance.
Regards,
Suresh

Please go through the topic,
[http://arjudba.blogspot.com/2009/02/what-is-national-character-set.html|http://arjudba.blogspot.com/2009/02/what-is-national-character-set.html] [http://arjudba.blogspot.com/2009/03/unicode-characterset-in-oracle-database.html|http://arjudba.blogspot.com/2009/03/unicode-characterset-in-oracle-database.html]
and decide whether you need migration . If you need migration then have a look at,
[http://arjudba.blogspot.com/2009/03/difference-between-we8mswin1252-and.html|http://arjudba.blogspot.com/2009/03/difference-between-we8mswin1252-and.html]
[http://arjudba.blogspot.com/2009/03/difference-between-we8iso8859p1-and.html|http://arjudba.blogspot.com/2009/03/difference-between-we8iso8859p1-and.html]
[http://arjudba.blogspot.com/2009/03/difference-between-we8iso8859p1-and_11.html|http://arjudba.blogspot.com/2009/03/difference-between-we8iso8859p1-and_11.html]
And always check for reports in csscan.
Edited by: user9533551 on 07-Jul-2009 04:29

How to review implication of database character set change on PL/SQL code?

Hi,
We are converting WE8ISO8859P1 oracle db characterset to AL32UTF8. Before conversion, i want to check implication on PL/SQL code for byte based SQL functions.
What all points to consider while checking implications on PL/SQL code?
I could find 3 methods on google surfing, SUBSTRB, LENGTHB, INSTRB. What do I check if these methods are used in PL/SQL code?
What do we check if SUBSTR and LENGTH functions are being used in PL/SQl code?
What all other methods should I check?
What do I check in PL/SQL if varchar and char type declarations exist in code?
How do i check implication of database characterset change to AL32UTF8 for byte bases SQL function.
Thanks in Advance.
Regards,
Rashmi

There is no quick answer. Generally, the problem with PL/SQL code is that once you migrate from a single-byte character set (like WE8ISO8859P1) to a multibyte character set (like AL32UTF8), you can no longer assume that one character is one byte. Traditionally, column and PL/SQL variable lengths are expressed in bytes. Therefore, the same string of Western European accented letters may no longer fit into a column or variable after migration, as it may now be longer than the old limit (2 bytes per accented letter compared to 1 byte previously). Depending on how you dealt with column lengths during the migration, for example, if you migrated them to character length semantics, and depending on how relevant columns were declared (%TYPE vs explicit size), you may need to adjust maximum lengths of variables to accommodate longer strings.
The use of SUBSTR, INSTR, and LENGTH and their byte equivalents needs to be reviewed. You need to understand what the functions are used for. If the SUBSTR function is used to truncate a string to a maximum length of a variable, you may need to change it to SUBSTRB, if the variable's length constraint is still declared in bytes. However, if the variable's maximum length is now expressed in characters, SUBSTR needs to be used. However, if SUBSTR is used to extract a functional part of a string (e.g. during parsing), possibly based on result from INSTR, then you should use SUBSTR and INSTR independently of the database character set -- characters matter here, not bytes. On the other hand, if SUBSTR is used to extract a field in a SQL*Loader-like fixed-format input file (e.g. read with UTL_FILE), you may need to standardize on SUBSTRB to make sure that fields are extracted correctly based on defined byte boundaries.
As you see, there is universal recipe on handling these functions. Their use needs to be reviewed and understood and it should be decided if they are fine as-is or if they need to be replaced with other forms.
Thanks,
Sergiusz

Database Character Set Change

Hi,
I am trying to change my database's(9i) character set US7ASCII to UTF8 .
There are some tables having CLOB columns which are stopping this from happening .
So I exported all those tables having CLOB columns and truncated them .
But there are some views also which have CLOB columns which are restricting me from changing the characterset further.
Any help will be appreciated.
Thanx

Hi,
I used the following after export and truncate of tables containing CLOB columns .
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 UTF8;
SQL> ALTER DATABASE CHARACTER SET UTF8;
ALTER DATABASE CHARACTER SET UTF8
ERROR at line 1:
ORA-12716: Cannot ALTER DATABASE CHARACTER SET when CLOB data exists
Pls help me out.
Thanx

Changing the Database Character Set From WE8MSWIN1252 to AR8MSWIN1256

good morning everybody,
I need your help to know all step which it is necessary to follow to change the Database Character Set From WE8MSWIN1252 to AR8MSWIN1256
thank you

If you have not already done so, read up on Character Set Migration and using the CSSCAN tool to verify the database before making any changes.

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

Precautions i need to take when changing the Character set

Hi,
ORACLE VERSION: 10G Release 1 (10.1.0.3.0)
I am going to change my database's characterset from AL32UTF8 to WE8MSWIN1252 character set and AL16UTF16 NCHAR character set. So i have few questions for you.
1. What is the difference between Character Set and National Character set? Do i have to set both?
2. What are precautions that i need to take while changing the characterset?
3. What are JOB_QUEUE_PROCESSES and AQ_TM_PROCESSES parameters in Plain English? Why do i have to set these parameters to 0 as mentioned in this post below.
Storing Chinese in Oracle Database

1) The database character set controls (and specifies) the character set of CHAR & VARCHAR2 columns. The national character set controls the character set of NCHAR & NVARCHAR2 columns.
2) Please make sure that you read the section of the Globalization manual that discusses character set migration. In particular, going from UTF-8 to Windows-1252 is going to require a bit more work since the latter is a subset (and not a strict binary subset) of the former.
Justin

Changing DB character set for only one schema

We are interested in changing the characterset of only one user from Western European to AL32UTF8.
Could you please verify if the following steps will be correct to do the same.
1. Run CSScan on the one user
2. Fix any issues
3. Export that one user (with NLS_LANG set to <your old database character set>)
4. Create a new database in the AL32UTF8 character set
5. Import that one user into the new database (with NLS_LANG set to <your old database character set>)

Actually your title is a little incorrect. You are not changing CS for only one schema in existing DB which is not possible. You are trying to migrate a schema to new CS DB. Which is totally doable and your approach is mostly correct.
Database Character Set Scanner provide user scan mode
http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ch12scanner.htm#i1006013
Mostly the issue could be data truncation, especially if you have column defined using char or varchar2 vs nchar and nvarchar2
because char/varchar is defined in bytes, AL32UTF8 is multi-bytes char set, some character of your old data could saved more than 1 bytes in new DB and can't fit into the column size.

How to change the character set of the D/b

Hello All,
When i issue the command
ALTER DATABASE CHARACTER SET UTF8
It gives me the error that I can only change the character set to a superset of the existing character set.
Is there any way i can change the character set without recreating the database.
TIA
Naveen

The existing character set is the basis for the new character set. This is fair enough, because the character set determines how the actual data is stored in the database. Allowing new characters is a minor change: completely re-encoding your entire database is not.
I'm afraid export, recreate and import is your only option.
Cheers, APC

Changing database character set

Similar Messages

Maybe you are looking for