Import error due to character set difference?

hi,
hoping anyone to explain reason for the following import error.
here's the situation,
- export client used WE8MSWIN1252 charset (release v10.02.01)
- import server used WE8ISO8859P1 charset (release v10.1.0.4)
all tables appeared to be imported without error, except that import terminated unsuccesfully due to oracle error 2248
"ALTER SESSION SET PLSQL_OPTIMIZE_LEVEL =1 NLS-LENGTH_SEMANTICS = 'BYTE' PLSQL_CODE_TYPE = 'INTERPRETED' PLSQL_DEBUG = FALSE PLSQL_WARNING = 'DISABLE:ALL' PLSQL_CCFLAGS =''"
ORA-02248: invalid option for ALTER SESSION
was error due to the difference release version? char set conversion to non superset?
appreciate any help pls

It is difficult to say what is the current state of the database, so it is recommended to reexport and reimport the object definitions. You may miss some other stuff like object types, contraints, etc. Table data should be OK, so reexport should not include data.
As far as character sets are concerned, because of the difference between the export client character set and the import server character set, you may have lost some characters in the code range 0x80-0x9f. This includes Euro sign, TM, sign, "smart" quotes, en- and em-dash, etc. Use the Windows charmap.exe to see all the codes. If you have some of these codes in the source database, you have lost them on import (they got converted to the reverse quotation mark code 0xbf).
-- Sergiusz

Similar Messages

Import problem due to Character set

I did an export of an entire schema using Original export utility(not Datapump) in 10G Release 1 (10.1.0.3.0). When i tried to import it. I got the error mentioned below. It is something to do with the character set. What settings do i have to give during import to bypass this Character set problem? After taking the export dmp file i deleted the Schema. So i all i've got is the export dmp file.
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
. importing MOTORGM's objects into 'MOTORGM2'
. . importing table "SKU_DETAILS" 1872 rows imported
. . importing table "COMP_LLU_DETAILS" 1877 rows imported
. . importing table "SHIP_ROUTING" 0 rows imported
. . importing table "SHIP_ROUTING_CODE" 0 rows imported
. . importing table "AI_DETAILS" 103 rows imported
. . importing table "AI_DETAILS_BKP" 103 rows imported
IMP-00019: row rejected due to ORACLE error 12899.
IMP-00003: ORACLE error 12899 encountered.
ORA-12899: value too large for column "MOTORGM2"."CLASS_REC"(actual: 1017, maximum: 255)
Column1....
Column2....

-- db unicode charset
SQL> create table z_test_unicode (c varchar2(5));
Table created.
SQL> insert into z_test_unicode values('éèîàö');
insert into z_test_unicode values('éèîàö')
ERROR at line 1:
ORA-01401: inserted value too large for column
SQL> insert into z_test_unicode values('é');
1 row created.
SQL> select vsize(c) from z_test_unicode;
VSIZE(C)
3
SQL> insert into z_test_unicode values('éà');
insert into z_test_unicode values('éà')
ERROR at line 1:
ORA-01401: inserted value too large for column
SQL> drop table z_test_unicode
2 /
Table dropped.
-- db without unicode charset
Connected.
SQL> create table z_test_unicode (c varchar2(5));
Table created.
SQL> insert into z_test_unicode values('éèîàö');
1 row created.
SQL> commit;
Commit complete.
SQL> select vsize(c) from z_test_unicode;
VSIZE(C)
5
On possible solution to investigate for this kink of issue :
try to take a look at the init param : nls_lenght_semantics (by default set to Byte) --> to be changed to CHAR
SQL> show parameter semanti
NAME TYPE VALUE
nls_length_semantics string BYTE

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;

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;

Error " conversion error between two character sets" in PI MONI

Hi Experts
I am doing file to Idoc scenario. I am getting the following error in PI MONI "conversion error between two character sets".
please suggest me how to solve the issue.
thanx in advance.

Hi Mickael
Below is the complete error message found in PI MONI.
SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">SYSTEM_DUMP</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>PI Server : XBTO80__0000 : Conversion error between two character sets.</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Importing from a different character set

Oracle 8.1.7 / Windows NT
I'm trying to import a dump file which was created with character set WE8ISO8859P9. My database uses character set UTF8. Some of the records can't be inserted because of error "ORA-1401: Value too large for column". Is this because of the different character sets? If I switch my session to WE8ISO8859P9, imp says "character set conversion from x to y not supported."
How can I get these last records inserted? Here's an excerpt from the log:
Verbunden mit: Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
<
Export-Datei wurde von EXPORT:V08.00.05 |ber konventionellen Pfad erstellt
Warnung: Die Objekte wurden von NOC_ADMIN exportiert, nicht von Ihnen.
Importvorgang mit Zeichensatz WE8ISO8859P9 und Zeichensatz UTF8 NCHAR durchgef|hrt
Import-Server verwendet Zeichensatz UTF8 (mvgliche Zeichensatzkonvertierung)
Export-Server verwendet Zeichensatz WE8ISO8859P9 NCHAR (mvgliche Zeichensatzkonvertierung)
. Import NOC_ADMIN's Objekte in NOC_ADMIN
. . Import der Tabelle "ACCESSROUTERIFS_" 782 Zeilen importiert
. . Import der Tabelle "ITEM_"
IMP-00019: Zeile zur|ckgewiesen aufgrund von Oracle-Fehler 1401
IMP-00003: Oracle-Fehler 1401 gefunden
ORA-01401: Eingef|gter Wert zu gro_ f|r Spalte
Spalte 1 33886
Spalte 2
Spalte 3
Spalte 4 1323
Spalte 5
Spalte 6 11
Spalte 7 18600
Spalte 8 18600
Spalte 9 20-NOV-2000:00:00:00
Spalte 10 processing
Spalte 11 inactive
Spalte 12
Spalte 13
Spalte 14 35682.0
Spalte 15
Spalte 16
Spalte 17
Spalte 18 05.12.00: KD weiss noch nix neues, er wird uns inf...
Spalte 19
Spalte 20 kschmid
Spalte 21 09-FEB-2001:15:50:21
Spalte 22
Spalte 23 12
Spalte 24
Spalte 25 06-NOV-2000:00:00:00
null

Please try ORacle RDBMS support. this issues is to do with Oracle Import.

Getting ORA-01429 error while changing character set

When I am changing character set from WE8DEC to AL32UTF8, I am getting ORA-01429 error
SQL> ALTER DATABASE CHARACTER SET INTERNAL_USE AL32UTF8 ;
ALTER DATABASE CHARACTER SET INTERNAL_USE AL32UTF8
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-01429: Index-Organized Table: no data segment to store overflow row-pieces

Chockalingam wrote:
I am using above steps as per oracle doc only.
http://docs.oracle.com/cd/B10500_01/server.920/a96529/ch10.htm
No, you are not.
- You are not using the correct version doc vs. Oracle server version. Try to find the same suggestion in the relevant doc.
- The doc you reference specifically says "... it can be used only under special circumstances. The ALTER DATABASE CHARACTER SET statement does not perform any data conversion, so it can be used +if and only if the new character set is a strict superset of the current character set+." (emphasis is mine)
You do not have a strict superset.
- Also the special clauses you have used are not documented - for a reason.
Please edit your posts above to remove the ill-advice (steps with internal use only clauses) that does not belong on a forum.
Edited by: orafad on Mar 16, 2012 9:47 PM

Oracle.sql.ARRAY error "Non supported character set: oracle-character-set-"

Hi Folks,
I am getting error :
java.sql.SQLException: Non supported character set: oracle-character-set-178
at oracle.gss.util.NLSError.throwSQLException(NLSError.java:46)
in the following code :
Object[] arrayToPassToDB=new Object[7];
ArrayDescriptor arraydesc = ArrayDescriptor.createDescriptor(arrayDesc,con);
ARRAY array = null;
array = new ARRAY(arraydesc, con, arrayToPassToDB);
i am using jdk1.6 and oracle 10g.
I have copied the orai18n.jar and ojdbc6.jar in WEB-INF\lib directory of my project and also in the Tomcat\lib directory.
can you please help me?
Thanks in advance.

java.sql.SQLException: Non supported character set:oracle-character-set-178

Import error converting character set

Hi there, the first time i ever post something, so i hope i give enough information so my question can be answered.
I have an oracle 8.1.6 database on Windows NT4. On the same machine i have installed Designer 6.
Everything is working just fine i just can't import a dump file made from repository 6. It's not a full dump, so i first created a whole new repository.
Now, when i want to import the dump file in command prompt, using the imp.exe (present in C:\<oracle_home>\bin), the next error occurs:
IMP-00069: Could not convert to environment national character set's handle
IMP-00000: Import terminated unsuccessfully.
As the import is due to start, it gives the following message:
import done in WE8iSO8859P1 character set and WE8IS08859P1 NCHAR character set.
Then the error occurs.
Now i wonder if this can be solved. I cannot see in the dump file what character set was used there. I did not make the export myself. Is there a way that i can convert the character set in the dumpfile or something? Or should i solve this problem by making changes in the database?
Thx for your help, i am trying to solve this problem myself for over a week now and i'm getting tired of it.

Hi friend,
Same Problem i have faced, and i found that this is due to only the Version mismatch, u attempting to import data from higher version to lower one.
Just check at ur end also.
Bye
Tehzeeb Ahmed

Import error character set conversion

import done in US7ASCII character set and AL16UTF16 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
export client uses WE8ISO8859P1 character set (possible charset conversion)
Import terminated successfully without warnings.
how to resolve this
importinng into linux machine

import done in US7ASCII character set and AL16UTF16 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
export client uses WE8ISO8859P1 character set (possible charset conversion)
Import terminated successfully without warnings.Your import was successful. However, there are a few things you need to note from the top of the import log. It is advisable to use correct NLS settings when doing export/import to avoid data corruption/loss. That idea is to ensure you set the correct NLS setting (NLS_LANG) at the client before running exp or imp. In some cases, the setting does not matter because the different character sets can go together.
In this case, I would not worry about it.

Import시 character set 문제, OORA-01435, IMP-00008 에러에 의해 중단되었습니다. 조언을 부탁합니다.

안녕하세요,
아래와 같이 import를 하려고 하는데 에러가 나면서 중단되었습니다.
C:\temp>imp userid=system/1234 file=c:\temp\usr_lms2-TS_LMS_DEV_D1.dmp FULL=y
에러메시지는 아래와 같습니다.
참고로, export 했던 어떤 database에는 usr_lms2 계정이 있었고,
import하려는 이 database에는 그 계정이 없어서 usr_lms2 계정을 생성하고 import를 실행했습니다.
질문1: 아래의 character set과 관련된 메시지는 정상적인것인지 궁금합니다.
질문2: ORA-01435: user does not exist라는 에러는 왜 발생할까요?
질문3: IMP-00008: unrecognized statement in the export file 에러는 dump 화일 자체에 문제가 있다는 말인가요?
해결방법을 알려주시면 좋겠습니다.
Import: Release 11.2.0.2.0 - Production on 목 3월 28 10:00:38 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production
Export file created by EXPORT:V10.02.01 via conventional path
import done in KO16MSWIN949 character set and AL16UTF16 NCHAR character set <-------- ?
import server uses AL32UTF8 character set (possible charset conversion) <-------- ?
export server uses UTF8 NCHAR character set (possible ncharset conversion) <-------- ?
. importing SYSTEM's objects into SYSTEM
. importing USR_LMS2's objects into USR_LMS2
IMP-00003: ORACLE error 1435 encountered <-------------------- 에러
ORA-01435: user does not exist <--------------------- 에러
IMP-00008: unrecognized statement in the export file: <-------------------- 에러
Import terminated successfully with warnings.
감사합니다.

Character Set Error in PL/SQL

Hi,
While connecting to PL/SQL Developer I am getting this following error.
Database character set (AL32UTF8) and client character set (WE8MSWIN1252) are different.
Character set conversion may cause unexpected results.
Note: you can set the client character set through the NLS_LANG registry key in
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_XE.
Please help me avoid this error.
Thanks.

That is presumably a PL/SQL Developer error. You may want to contact the vendor of that particular product to understand that warning because it makes no sense to me.
It is perfectly appropriate, and quite normal, for the client character set to be a subset of the database character set. Setting the client character set to match the database character set can create a host of problems that lead to invalid data being stored in the database. This appears designed to increase the odds that this particular tool will work correctly while decreasing the odds that everything else in your environment will work correctly. That seems like a relatively poor trade-off to me.
Justin

Character set error comming in stored procedure

i am writing these SQL lines when execute these giving me error
SQL Lines
SELECT DocDate,
NVL(SMTransType.Description, '<Not Provided>') DESCRIPTION,
CASE
WHEN DocType = 'GRN' THEN ( SELECT GrnNo
FROM IVGrnMst
WHERE ID = DocID )
END "ReceiptNo",
CASE
WHEN DocType = 'PUR' THEN ( SELECT PrNo ---- its data type VARCHAR2(50)
FROM IVPurReturnMst
WHERE ID = DocID )
WHEN DocType = 'SCP' THEN ( SELECT ConsumptionCode --its data type NVARCHAR2(50)*
FROM IvStoreConsumptionMst
WHERE ConsumptionId = DocID )
END "IssueNo"
FROM IVStockRegister Stock INNER JOIN
SMTransType
ON Stock.DocType = SMTransType.Code;
SQL SQL Error: ORA-12704: character set mismatch
12704. 00000 - "character set mismatch"

are you sure your SELECTs on in the case after when return single value?
try this, please
SELECT DocDate,
NVL(SMTransType.Description, '<Not Provided>') DESCRIPTION,
CASE
    WHEN DocType = 'GRN'
    THEN
      ( SELECT MIN(GrnNo) FROM IVGrnMst WHERE ID = DocID
END "ReceiptNo",
CASE
    WHEN DocType = 'PUR'
    THEN
      (SELECT MIN(PrNo) ---- its data type VARCHAR2(50)
      FROM IVPurReturnMst
      WHERE ID = DocID
    WHEN DocType = 'SCP'
    THEN
      (SELECT MIN(ConsumptionCode) --its data type NVARCHAR2(50)
      FROM IvStoreConsumptionMst
      WHERE ConsumptionId = DocID
END "IssueNo"
FROM IVStockRegister Stock
INNER JOIN SMTransType
ON Stock.DocType = SMTransType.Code;

Conversion error, from character set 4102 to character set 4103

Hi,
We've developed a JCO server(in Java) with an ABAP report the function provided by the JCO server.
MetaData:
     static {
          repository = new Repository("SMSRepository");
          fmeta = new JCO.MetaData("ZSMSSEND");
          fmeta.addInfo("TO", JCO.TYPE_CHAR, 255,   0, 0, JCO.IMPORT_PARAMETER, null);
          fmeta.addInfo("CONTENT", JCO.TYPE_CHAR, 255,   0, 0, JCO.IMPORT_PARAMETER, null);
          fmeta.addInfo("RETN", JCO.TYPE_CHAR, 255,   0, 0, JCO.EXPORT_PARAMETER, null);
          repository.addFunctionInterfaceToCache(fmeta);
Server parameters:
       Properties prop = new Properties();
       prop.put("jco.server.gwhost","shaw2k07");
       prop.put("jco.server.gwserv","sapgw01");
       prop.put("jco.server.progid","JCOSERVER01");
       prop.put("jco.server.unicode","1");
       srv = new SMSServer(prop,repository);
If we run JCO server in both my client machine(from developer studio) and in the WAS machine(stand alone Java program), everything is ok. In the Abap side, the SM59 unicode test return the destination is an unicode system, and the ABAP report call the function can run smoothly.
But we package this JCO server to a web application and deploy to WAS, problem occured. The SM59 unicode test still say the destination is an unicode system. But the ABAP report runs with an ABAP DUMP:
Conversion error between two character set
RFC_CONVERSION_FIELD
Conversion error "RETN" from character set 4102 to character set 4103
A conversion error occurred during the execution of a Remote Function
Call. This happened either when the data was received or when it was
sent. The latter case can only occur if the data is sent from a Unicode
system to a non-Unicode system.
I read the jrfc.trc log, it shows it receives data in unicode 4103(that's ok), but send data in unicode 4102(that's the problem).4102 is UTF-16 Big Endian and 4103 UTF-16 Little Endian. Our system is windows on intel 32 aritechture, so based on Note 552464, it should be 4103.
Why it sends data (Java JCO server send output parameter to ABAP) in 4102?????
What's the problem??? Thank you very much!!
Best Regards,
Xiaoming Yang
Message was edited by:
        Xiaoming Yang

Hello Experts,
Any replies on this?
I am also getting a similar kind of error.
Do you have any idea on this?
Thanks and Best Regards,
Suresh

Import Character set differs

I am running my Oracle8.1.5 Server on windows NT4.0
Dump is taken from Oracle8.1.7 on Unix.
While importing the dump to my database (oracle8.1.5) I am getting the following message.
import done in WE8ISO8859P1 character set and WE8ISO8859P1 NCHAR character set
IMP-00069: Could not convert to environment national character set's handle
IMP-00000: Import terminated unsuccessfully
I tried to change the Character set by following command.
Set nls_lang=American_America.US7ASCII
But Still I couldn't able to import the dump file
TIA
null

I am running my Oracle8.1.5 Server on windows NT4.0
Dump is taken from Oracle8.1.7 on Unix.
While importing the dump to my database (oracle8.1.5) I am getting the following message.
import done in WE8ISO8859P1 character set and WE8ISO8859P1 NCHAR character set
IMP-00069: Could not convert to environment national character set's handle
IMP-00000: Import terminated unsuccessfully
I tried to change the Character set by following command.
Set nls_lang=American_America.US7ASCII
But Still I couldn't able to import the dump file
TIA
null

Import error due to character set difference?

Similar Messages

Maybe you are looking for