Is it possible to set character set at instance level?

hi all,
I have some confusion.
say my database character set is AL32UTF8.
and i want tio set charcter set of instance is WE8MSWIN1252
Is it passible to set character set at instance level?
Please reply with yes or No or why?
Thanks & Regards,

Hi,
It's DataBase Level. One best example would be when you try to change the character or characterset conversion by using "Csscan" you can check the log or report. Which can guide what the things are happening. Instance - I think you might be referring to "Session".
- Pavan Kumar N
- ORACLE OCP - 9i/10g
https://www.oracleinternals.blogspot.com

Similar Messages

How to SET CHARACTER SET UTF8

I am looking to execute something like the stmt "SET CHARACTER SET UTF8"
However if i put the above stmt in a SQLDBC_Statement_execute call, i get fail message.
I should also mention here that, SQLDBC_Connection_connect call provides a way to provide the character set as one of the parameter. Is that the only way we can set character set from an application while using SQLDBC ?
Regards
Raj

Hi Lars,Elke and Thomas,
Thanks to all of you for your valuable input. Honestly speaking i'm little lost on how to go about this requirement of unicode support for my application. Please allow me some more time to investigate this and then get back to you.
In my application for all other databases a simple execution of "SET CHARACTER SET UTF8" is all that's been done to set the support for UTF-8. So, I really need to figure out what all changes needs to be done in the app if this is not going to work.
In the meantime something more caught my attention while i was using this command:
sqlcli MAXDB1=> \dc domain.columns
Table "DOMAIN.COLUMNS"
Column Name
Type
Length
Nullable
KEYPOS
SCHEMANAME
CHAR UNICODE
32
YES
OWNER
CHAR UNICODE
32
YES
What does the type 'CHAR UNICODE' for Type means here?
Regards
Raj

OracleXE setting character set

Hi,
during installation of Oracle Express Edition the NLS_NCHAR_CHARACTERSET is automatically set to AL16UTF16 which means that the size of NVARCHAR2 fields is limited to 2000 characters.
Is there any way to create the database setting NLS_NCHAR_CHARACTERSET to UTF8
instead to being able to use the full 4000 characters size?
Thanks a lot for your advice!

A simmilar problem was addressed here: Re: Export using ISO-8859-1 in XE Apex
~ Madrid.

Can we change the DB character set at session level

hi,
Please help me
when iam giving the alter session command iam getting the error:
SQL> ALTER SESSION set NLS_CHARACTERSE
T =WE8MSWIN1252;
ALTER SESSION set NLS_CHARACTERSET =WE8MSWIN1252
ERROR at line 1:
ORA-00922: missing or invalid
i need to enter Arabic names in using the xml file.
here i have two questions
1)is it is possible to set character set at session level. because my client is not allowing to bounce the database. DB version is 10.2.0.4
Right now my DB is in US7ascii
2)is this "WE8MSWIN1252" set supports Arabic.
Regards,
Naresh

You cannot change the characterset at the session level. If you want to store ARABIC characters in your database then you should change the characterset of your database to any other characterset that supports Arabic characters or to a Unicode characterset like UTF8 or AL32UTF8.
If you try to insert Arabic characters with your present US7ASCII charancterset then the characters would be stored as junk.

Default Character Set using JSObject

Hi All,
This problem has been nagging me for a while and am now resorting to this forum for an answer.
I have a jsp page with an embedded applet. Inside the applet, I read the HTML page using JSObject.
The problem is when using the JSObject to get values of controls from the HTML page with Japanese characters.
The HTML page is encoded in UTF-8, however, when I get values from the controls using JSObject in the applet, the values returns as ???. Latin characters are supported but not Japanese characters. So.. I'm wondering what character set the JSObject supports when converting a Javascript string to a Java String.
The following code is executed:
          JSObject win = JSObject.getWindow(this);
          JSObject doc = (JSObject) win.getMember("document");
          JSObject forms = (JSObject) doc.getMember("forms");
     JSObject form = (JSObject)forms.getSlot(0);
          JSObject title = (JSObject)form.getMember("title");
String titleValue = (String)title.getMember("value");
I've also tried form.eval("document.forms[0].title.value") and that returns the same ??? for japanese characters.
Any ideas?
Kent

Hi Larry,
The characters that appear at the beginning of each file - ï»¿ - is the BOM or byte order mark for UTF-8, which is automatically added to the file on creation. These files are UTF-8 encoded, to allow for the support of multi-byte characters. An updated version of the Exporter Tool removes these BOM characters. Please contact Support to obtain this updated version of the Exporter tool.
Alternatively, you can try the following:
If the character set of your Oracle database is not UTF-8, then you have two options:
1) If possible, change the character set of your database to UTF-8. To check the current database characterset, check the "NLS_DATABASE_PARAMETERS" table.
or
2) Open the generated .dat files using Notepad, then use the File | Save As menu option, and set the "Encoding" to ANSI, then save the file. The BOM will now be removed from the .dat files.
I hope this helps.
Regards,
Hilary

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의 관계와 같음.

Backup failure due to Character set problem

Hi,
I am manually running a COLD backup script in Windows NT environment and all the logs has been captured below:
Recovery Manager: Release 8.1.6.0.0 - Production
RMAN-06005: connected to target database: db1 (DBID=754030292)
RMAN-06009: using target database controlfile instead of recovery catalog
RMAN> shutdown immediate;
2> startup mount;
3> RUN {
4> ALLOCATE CHANNEL disk1 TYPE disk;
5> BACKUP DATABASE TAG 'db1_db_full' FORMAT 'e:\backup\db1\db1_backup';
6> copy current controlfile to 'e:\backup\db1\Control_db1.ctl';
7> }
8>
RMAN-06405: database closed
RMAN-06404: database dismounted
RMAN-06402: Oracle instance shut down
RMAN-06193: connected to target database (not started)
RMAN-06196: Oracle instance started
RMAN-06199: database mounted
Total System Global Area 934143244 bytes
Fixed Size 70924 bytes
Variable Size 260554752 bytes
Database Buffers 673439744 bytes
Redo Buffers 77824 bytes
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: disk1
RMAN-08500: channel disk1: sid=13 devtype=DISK
RMAN-03022: compiling command: backup
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: backup
RMAN-06003: ORACLE error from target database: ORA-06550: line 1, column 166:
PLS-00553: character set name is not recognized
ORA-06550: line 0, column 0:
PL/SQL: Compilation unit analysis terminated
RMAN-06031: could not translate database keyword
Recovery Manager complete.
As the above log shown, I cannot do any backup command in the RUN bracket and it complains that the character set is not recognized.
This set of error happens when I have create six other Oracle databases in my NT box. Before that, I can manually run the backup with no problem and a backupset has been generated.
If you have come across this problem and have solutions of it. That will be great.
Thanks !!
null

kk001 wrote:
Hi ,
The export Backup failing due to character set problem
. . exporting table ravidlx
EXP-00008: ORACLE error 6552 encountered
ORA-06552: PL/SQL: Compilation unit analysis terminated
ORA-06553: PLS-553: character set name is not recognized
P
Please suggest how to set character set
I don't know what you have.
I don't know what you do.
I don't know what you see.
It is really, Really, REALLY difficult to fix a problem that can not be seen.
use COPY & PASTE so we can see what you do & how Oracle responds.
do as below so we can know complete Oracle version & OS name.
Post via COPY & PASTE complete results of
SELECT * from v$version;

Polish character sets

Hi reader,
do you have a clue how to set character set or how to to switch between character sets? e.g. from cp1252 to 1250 and vice versa
I'd like to display polish characters within a swing GUI and do not know how to switch....
internationalization works fine (based upon Messages_iso.properties) but the character set does not switch to something fitting.
thx
Message was edited by:
digit

Java-internal character set is UTF-16, there should be no need for "switching". Property files, however, are restricted to ISO-8859-1 and may use Unicode escape sequences (\uxxxx). Maybe you should check the contents of your property file.

EXPORT Backup failing due to character set problem

Hi ,
The export Backup failing due to character set problem
. . exporting table ravidlx
EXP-00008: ORACLE error 6552 encountered
ORA-06552: PL/SQL: Compilation unit analysis terminated
ORA-06553: PLS-553: character set name is not recognized
P
Please suggest how to set character set
Regards,
kk
Edited by: kk001 on Aug 29, 2011 7:22 PM

kk001 wrote:
Hi ,
The export Backup failing due to character set problem
. . exporting table ravidlx
EXP-00008: ORACLE error 6552 encountered
ORA-06552: PL/SQL: Compilation unit analysis terminated
ORA-06553: PLS-553: character set name is not recognized
P
Please suggest how to set character set
I don't know what you have.
I don't know what you do.
I don't know what you see.
It is really, Really, REALLY difficult to fix a problem that can not be seen.
use COPY & PASTE so we can see what you do & how Oracle responds.
do as below so we can know complete Oracle version & OS name.
Post via COPY & PASTE complete results of
SELECT * from v$version;

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

Reports 9i and character set

We have reports in character set WINDOWS 1251
But iAS do they in UTF 8.
We tried to set character set in uifont.ali, but there was not effect.
How to change default character set from UTF8 to WINDOWS 1251 ?
Environment:
iAS 9i R2
nls_lang=AMERICAN.CL8MSWIN1251
uifont.ali:
COURIER....UTF8=COURIER....CL8MSWIN1251

Laura,
First, You can run the 6i reports with OGD in reports 9i, provided you have your Oracle 6i home is in system path
and the regsitry variable ORACLE_GRAPHICS6I_HOME is set to pint your 6i oracle home
Now, if you wan to open these 6i report with OGD and modify the report in 9i builder, then the OGDs are loast when saving this reports from 9i
buikder, so you would need to recreate the graphs using the graph wizard
Thanks
The Oracle Reports Team

It's possible to convert 'WE8MSWIN1252' character to chinese character set?

Hi All,
Is anyone know how to convert "WE8MSWIN1252" character to chinese character set in order to display chinese word in oracle apex?
My problem is i can't display chinese character set in oracle apex. The chinese field is showed like °×ÑªÇò¼ÆÊý. I'm using WE8MSWIN1252 database character set.
I'm wondering it's possible to show character word?
I'm appreciating if anyone have a good solution to share with me.
Thanks a lot in advance!
Edited by: Apex Junior on Jul 16, 2010 2:18 PM

WE8 is a Western European character set. If you wish to store and access a globalized multibyte character set you must have a database that supports it: You don't have one at the moment.
Given this is Apex I'd suggest you read the docs and reinstall.
Alternatively you could try CSSCAN and CSALTER and perhaps you can make the change but be very careful and have a good backup before you try.
http://www.morganslibrary.org/reference/character_sets.html

Is it possible to add new character set encodings?

Hello,
is it possible to add new character set encodings in Mac OS?
Practically, i need to add "Russian (DOS)" encoding to Tiger, but is it at all possible even in newer versions of Mac OS?
Where to find the missing encodings and how to install them?
Google search did not return much.
Thanks.

Well, it was a general question about possibility of adding new encodings in Mac OS, but i posted a more specific question about Tiger here:
http://discussions.apple.com/thread.jspa?threadID=2692557&tstart=0
On Tiger i do not have Russian (DOS) in TextEdit, only Cyrillic (DOS).
The same about TextWrangler on Tiger.
Strangely, i have Russian (DOS) in TeXShop on Tiger.

Server uses WE8ISO8859P15 character set (possible charset conversion)

Hi,
when EXP in 9i I receive :
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export done in WE8PC850 character set and AL16UTF16 NCHAR character set
server uses WE8ISO8859P15 character set (possible charset conversion)What is the problem ?
Thank you.
I exported just a table, how to see if it is exported ?

Dear user522961,
You have not defined or misdefined the NLS_LANG environmental variable before trying to run the export command.
Here is a little illustration;
*$ echo $NLS_LANG*
*AMERICAN_AMERICA.WE8ISO8859P9*
$ exp system/password@opttest file=ogan.dmp owner=OGAN
Export: Release 10.2.0.4.0 - Production on Mon Jul 12 18:10:47 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
*Export done in WE8ISO8859P9 character set and AL16UTF16 NCHAR character set*
About to export specified users ...
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user OGAN
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user OGAN
About to export OGAN's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. about to export OGAN's tables via Conventional Path ...
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting materialized views
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting statistics
Export terminated successfully without warnings.
*$ export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P15*
$ exp system/password@opttest file=ogan.dmp owner=OGAN
Export: Release 10.2.0.4.0 - Production on Mon Jul 12 18:12:41 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
*Export done in WE8ISO8859P15 character set and AL16UTF16 NCHAR character set*
*server uses WE8ISO8859P9 character set (possible charset conversion)*
About to export specified users ...
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user OGAN
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user OGAN
About to export OGAN's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. about to export OGAN's tables via Conventional Path ...
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting materialized views
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting statistics
Export terminated successfully without warnings.Hope it Helps,
Ogan

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

Is it possible to set character set at instance level?

Similar Messages

Maybe you are looking for