IMP-00037: Character set marker unknown ?

Hi,
I try to import some .dat files in oracle 10g database.
These files have been generated by OMWB from a Sybase 12.5 database. The following error occures :
$ imp FILE=Dat/COUNTER.dat
Import: Release 10.1.0.2.0 - Production on Fri Jun 18 14:38:25 2004
Copyright (c) 1982, 2004, Oracle. All rights reserved.
Username: qos_user
Password:
Connected to: Oracle Database 10g Release 10.1.0.2.0 - Production
IMP-00037: Character set marker unknown
IMP-00000: Import terminated unsuccessfully
I suppose there is an argument for the 'imp' command but I tried to read 'imp -help' and I didn't find it.
Could you explain me this error?
Thanks,
Grégory.

I Cannot say that because I have no access to the machine.
Could you tell me why this information is important? Does the generated .dat files depend on this vairiable?
For information, OMWB doesn't generate the files. It generates UNIX commands in a file that you execute manually (offline). In Sybase the command to export values is 'bcp', maybe this command hasn't the good parameters.
For example I post you a line that generates the file from Sybase :
bcp <DB_NAME>.dbo.counter out COUNTER.dat -c -t "<ec>" -r "<er>" -Usa -P -S<SERVER NAME>
What I can note in this command is that it seems to set '<er>' as the rows delimiter and '<ec>' as the cols delimiter. It is a possibility that Oracle does not support this format.

Similar Messages

Imp fails with character set marker unknown

Hi All,
I'm trying to import a dump that was done in WE8ISO8859P1 with Oracle 9i 9.2.0.5.0 into the Western European XE version on Windows XP Professional SP2.
I get an IMP-00037 Character set marker unknown error
I've tried setting NLS_LANG to American_UNITED KINGDOM.WE8ISO8859P1 but the same result. Obviously I'm just a novice but you've to start somewhere right, any help appreciated

Setting NLS_LANG to either character set should be fine. WE8MSWIN1252 is a superset of WE8ISO8859P1 ( http://aswan.gatech.edu/docs/oracle/10g/server.101/b10749/applocal.htm#636814 ) .
From the docs:
There are two character set conversions when you Import a dump file. The first one is performed by Import executable from the character set of the dump file (which is equal to NLS_LANG of Export session) to the character set of NLS_LANG of the Import session. The second conversion from the Import NLS_LANG to the database character set is performed by SQL*Net.
Here is more information in the docs:
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14215/exp_imp.htm#i1021901
~Dietmar.

Character set marker unknown error while importing data in 10g from 8i

Hi All,
I am trying to import the whole database schema wise (one by one) through oracle 10g database control page (which is browser based)
But when i try to import the objects of a schema i get the error that
"IMP-00037 : Character set marker unknown "
Import terminated unsuccessfully
Would anybody please tell me about the mentioned error ???
Kindly provide the solution.
Mentioned below are the character sets available in both the version.
Character sets in oracle 8.1.7 :-
Database Character Set :: WE8ISO8859P1
National Character Set :: WE8ISO8859P1
Character sets in oracle 10.2.0.1.0 :-
Database Character Set :: WE8ISO8859P1
National Character Set :: AL16UTF16
Regards
Milin...
Message was edited by:
user640001

Hi,
As you have asked, i have mentioned the export command below to get the full database export file.
And I have copied this export file (dump) to another machine(Server) where i have to import that file to upgrade the database to 10g Rel 2.
SET CC=%DATE:~4,2%-%DATE:~7,2%-%DATE:~10,4%
exp username/password@db_name
file=D:\PAY_BKP\EXP_FULL_PAY_%CC%.DMP log=D:\PAY_BKP\EXP_FULL_PAY.log
indexes=yes
full=yes
Kindly provide guidance.
Regards
Milin

IMP 00037 : Unknown character set marker.

I have used Oracle 9i (9.2.0.1) in my machine. Existing O/S in my machine is Win XP with service pack 2. I have created clubtown database user in machine.
Grant connect, resource, dba to clubtown user. Now i import data i.e. clubtown.dmp file which i have received from my client. i placed clubtown.dmp file in C:\. Then I invoke command prompt.(C:\) I put the command below..
imp system/<system-password> file=clubtown.dmp fromuser=clubtown touser=clubtown buffer=80000
log=club.log Unfortunately import done unsuccessfully.
giving message :
IMP 00037 : Unknown character set marker.
Note : When i installed Oracle in my Machine
i chose default character set.

How did you get that file? Was ftp involved? Did you ftp the file in binary mode?
The file needs to be ftp-ed in binary mode, or you will get this or other similar errors.
Sybrand Bakker
Senior Oracle DBA

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.

Character set conversion UTF-8 -- ISO-8859-1 generates question mark (?)

I'm trying to convert an XML-file in UTF-8 format to another file with character set ISO-8859-1.
My problem is that the ISO-8859-1 file generates a question mark (?) and puts it as a prefix in the file.
?<?xml version="1.0" encoding="UTF-8"?>
<ns0:messagetype xmlns:ns0="urn:olof">
<underkat>testv��rde</underkat>
</ns0:messagetype>
Is there a way to do the conversion without getting the question mark?
My code looks as follows:
public class ConvertEncoding {
     public static void main(String[] args) {
          String from = "UTF-8", to = "ISO-8859-1";
          String infile = "C:\\temp\\infile.xml", outfile = "C:\\temp\\outfile.xml";
          try {
               convert(infile, outfile, from, to);
          } catch (Exception e) {
               System.out.println(e.getMessage());
               System.exit(1);
     private static void convert(String infile, String outfile,
                                        String from, String to)
                         throws IOException, UnsupportedEncodingException
          //Set up byte streams
          InputStream in = null;
          OutputStream out = null;
          if(infile != null) {
               in = new FileInputStream(infile);
          if(outfile != null) {
               out = new FileOutputStream(outfile);
          //Set up character streams
          Reader r = new BufferedReader(new InputStreamReader(in, from));
          Writer w = new BufferedWriter(new OutputStreamWriter(out, to));
          /*Copy characters from input to output.
           * The InputSreamreader converts
           * from Unicode to the output encoding.
           * Characters that cannot be represented in
           * the output encoding are output as '?'
          char[] buffer = new char[4096];
          int len;
          while((len = r.read(buffer))!= -1) { //Read a block of output
               w.write(buffer, 0, len);
          r.close();
          w.flush();
          w.close();
}

Yes the next character is the '<'
The file that I read from is generated by an integration platform. I send a plain file to it (supposedly in UTF-8 encoding) and it returns another file (in between I call my java class that converts the characterset from UTF-8 to ISO-8859-1). The file that I get back contains the '��' if the conversion doesn't work and '?' if the conversion worked.
My solution so far is to skip the first "junk-characters" when reading from the inputstream. Something like:
private static final char UTF_BOM = '\uFEFF'; //UTF-BOM = ?
String from = "UTF-8", to = "ISO-8859-1";
if (from != null && from.toLowerCase().startsWith("utf-")) { //Are we reading an UTF encoded file?
/*Read first character of the UTF-Encoded file
It will return '?' in the first position if we are dealing with UTF encoding If ? is returned we skip this character in the read
try {
r.mark(1); //Only allow to read one char for the reset function to work
char c;
int i = r.read();
c = (char) i;
if (String.valueOf(UTF_BOM).equalsIgnoreCase(String.valueOf(c))) {
r.reset(); //reset to start position
r.skip(1); //Skip first character when reading from the stream
else {
r.reset();
} catch (IOException e) {
e.getMessage();
//return null;
}

Conversions between character sets when using exp and imp utilities

I use EE8ISO8859P2 character set on my server,
when exporting database with NLS_LANG not set
then conversion should be done between
EE8ISO8859P2 and US7ASCII charsets, so some
characters not present in US7ASCII should not be
successfully converted.
But when I import such a dump, all characters not
present in US7ASCII charset are imported to the database.
I thought that some characters should be lost when
doing such a conversions, can someone tell me why is it not so?

Not exactly. If the import is done with the same DB character set, then no matter how it has been exported. Conversion (corruption) may happen if the destination DB has a different character set. See this example :
[ora102 work db102]$ echo $NLS_LANG
AMERICAN_AMERICA.WE8ISO8859P15
[ora102 work db102]$ sqlplus test/test
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Jul 25 14:47:01 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
TEST@db102 SQL> create table test(col1 varchar2(1));
Table created.
TEST@db102 SQL> insert into test values(chr(166));
1 row created.
TEST@db102 SQL> select * from test;
C
¦
TEST@db102 SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
[ora102 work db102]$ export NLS_LANG=AMERICAN_AMERICA.EE8ISO8859P2
[ora102 work db102]$ sqlplus test/test
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Jul 25 14:47:55 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
TEST@db102 SQL> select col1, dump(col1) from test;
C
DUMP(COL1)
©
Typ=1 Len=1: 166
TEST@db102 SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
[ora102 work db102]$ echo $NLS_LANG
AMERICAN_AMERICA.EE8ISO8859P2
[ora102 work db102]$ exp test/test file=test.dmp tables=test
Export: Release 10.2.0.1.0 - Production on Tue Jul 25 14:48:47 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Export done in EE8ISO8859P2 character set and AL16UTF16 NCHAR character set
server uses WE8ISO8859P15 character set (possible charset conversion)
About to export specified tables via Conventional Path ...
. . exporting table TEST 1 rows exported
Export terminated successfully without warnings.
[ora102 work db102]$ sqlplus test/test
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Jul 25 14:48:56 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
TEST@db102 SQL> drop table test purge;
Table dropped.
TEST@db102 SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
[ora102 work db102]$ imp test/test file=test.dmp
Import: Release 10.2.0.1.0 - Production on Tue Jul 25 14:49:15 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Export file created by EXPORT:V10.02.01 via conventional path
import done in EE8ISO8859P2 character set and AL16UTF16 NCHAR character set
import server uses WE8ISO8859P15 character set (possible charset conversion)
. importing TEST's objects into TEST
. importing TEST's objects into TEST
. . importing table "TEST" 1 rows imported
Import terminated successfully without warnings.
[ora102 work db102]$ export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P15
[ora102 work db102]$ sqlplus test/test
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Jul 25 14:49:34 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
TEST@db102 SQL> select col1, dump(col1) from test;
C
DUMP(COL1)
¦
Typ=1 Len=1: 166
TEST@db102 SQL>

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.
감사합니다.

MySQL to Oracle Migration Issue - Unknown character set index for field.

Hi,
Looking for help..!!!
Migrating mySQL - version 4 database to Oracle 10g using oracle migration work bench. It went well until the last step. But, during the data migration, OMWB has given the following error:
+++++++++++
Unable to migrate data from source table gets.sales_order_01 to destination table gets_ora.sales_order_oracle10: gets_ora.sales_order_oracle10; Unknown character set index for filed "12596" received from ser.
+++++++++++
Log file shows:
java.sql.SQLException: Unknown character set index for field '12596' received from server.
     at com.mysql.jdbc.Connection.getCharsetNameForIndex(Connection.java:1692)
     at com.mysql.jdbc.Field.<init>(Field.java:161)
     at com.mysql.jdbc.MysqlIO.unpackField(MysqlIO.java:510)
     at com.mysql.jdbc.MysqlIO.getResultSet(MysqlIO.java:285)
     at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1326)
     at com.mysql.jdbc.MysqlIO.sqlQuery(MysqlIO.java:1225)
     at com.mysql.jdbc.Connection.execSQL(Connection.java:2278)
     at com.mysql.jdbc.Connection.execSQL(Connection.java:2225)
     at com.mysql.jdbc.Statement.executeQuery(Statement.java:1163)
     at oracle.mtg.migrationServer.LoadTableData._migrateTableData(LoadTableData.java:563)
     at oracle.mtg.migrationServer.LoadTableData.run(LoadTableData.java:326)
     at oracle.mtg.migration.WorkerThread.run(Worker.java:268)
I appreciate your help in this regards.
Regards,
K

Hi K,
Whats the default character set of you MySQL and Oracle Databases.
What version of JDBC driver are you using?
Is there any unicode characters used in your data?
Have you tried offline data move?
Thanks
Dermot.
Message was edited by:
dooneill

IMP-00069: Could not convert to environment national character set's handle

While importing database objects from dmp we are getting the following Error
C:\>imp chem/chem@chemdb full=y file='E:\eiproject\expdat.dmp' log=y;
Import: Release 8.1.5.0.0 - Production on Thu Sep 13 10:28:54 2001
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Connected to: Oracle8i Enterprise Edition Release 8.1.5.0.0 - Production
With the Partitioning and Java options
PL/SQL Release 8.1.5.0.0 - Production
Export file created by EXPORT:V08.01.07 via conventional path
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
null

Hi James,
IMP-69 can occur if you try to use an EARLIER version of IMPORT against an export (.dmp) file produced by a LATER version of EXPORT.
How about trying this:
Use the 8.1.5 EXPORT utility from Win2K to connect to your Solaris 8.1.7 database; then use the 8.1.5 IMPORT utility to import the file into the 8.1.5 W2K database.
Nat

How to exp/imp both diff character set tables between in DB1 and DB2?

In the Solaris 2.7 ,the oracle 8i DB1 has NLS_CHARACTERSET
ZHS16CGB231280 and NLS_NCHAR_CHARACTERSET ZHS16CGB231280
character set.
In other linux7.2 system ,the oracle 8i DB2 is install into the
NLS_NCHAR_CHARACTERSET US7ASCII and NLS_CHARACTERSET US7ASCII
character set.
The tables contents of DB1 have some chinese. I want to exp/imp
tables of DB1 into DB2 . But the chinese can't correct display
in the SQLWheet tools. How do the Exp/Imp operation ? ples help
me . thanks .

The supported way to store GB231280-encoded characters is using a ZHS16CGB231280 database or a database created using a superset of GB231280 ,such as UTF8 .Can you not upgrade your target database from US7ASCII to ZHS16CGB231280 ?
With US7ASCII and NLS_LANG set to US7ASCII , you are using the garbage in garbage out (GIGO) approach. This may seem to work but there are many hidden problems :-
1. Invalid SQL String Function behaviours - LENGTH ( ) , SUBSTR ( ) , INSTR ( )
2. Data can be corrupted when data is loaded into another database. e.g. EXP / IMP , Dblinks
3. Communication with other clients will generate incorrect results. e.g. other Oracle products - Oracle Text, Forms. , Java , HTML etc.
4. Linguistic sorts not available
5. Query using the standard WHERE clause may return incorrect results ..
6. Extra coding overhead in handling character conversions manually.
I recommend you to check out the FAQ and the DB Character set migration guide on the Globalization Support forum on OTN.
Nat.

Imp-00038 could not convert environment character set's handle

Hi People,
Am I did export a table and am now trying to import the same file that was exported onto a different schema but am getting an IMP-00038 error.
Could you be knowing what the problem is and how to go round it.
Thank you kindly,
Michael.

This is because the two schemas are using different character sets.
We have just had the same problem. It should be a case of changing the offending character set which I beleive is is set in the init ora file. If we sort it, I will post the solution for the next guy who gets this.

IMP-00016: required character set conversion (type 1 to 871) not supported

I am running Oracle DB: 8.1.7.4
Hit a problem when I export from Source DB: US7ASCII
and then, import into Target DB: UTF8.
Is there any workaround if this is the only export dump available?
Many thanks in advance.

Thanks for the prompt reply.
Both source and target are in the same version: 8.1.7.4.
The error gotten:
Import: Release 8.1.7.4.0 - Production on Fri Aug 22 15:37:37 2008
(c) Copyright 2000 Oracle Corporation. All rights reserved.
Connected to: Oracle8i Release 8.1.7.4.0 - Production
JServer Release 8.1.7.4.0 - Production
IMP-00016: required character set conversion (type 1 to 871) not supported
IMP-00000: Import terminated unsuccessfully
Many thanks in advance.

IMP-00016 required character set conversion (type 178 to 871) not supported

Hi, I am importing Portal release 2 handson to our test database whose character set is UTF8,durning importing, the following error message comes out 'IMP-00016: required character set conversion (type 178 to 871) not supported',what should i do? thank u in advance . My mail address is:[email protected] .

Thanks for the prompt reply.
Both source and target are in the same version: 8.1.7.4.
The error gotten:
Import: Release 8.1.7.4.0 - Production on Fri Aug 22 15:37:37 2008
(c) Copyright 2000 Oracle Corporation. All rights reserved.
Connected to: Oracle8i Release 8.1.7.4.0 - Production
JServer Release 8.1.7.4.0 - Production
IMP-00016: required character set conversion (type 1 to 871) not supported
IMP-00000: Import terminated unsuccessfully
Many thanks in advance.

Unknown character set index

i migrate from mysql4.0 to oracle i captured the source model and tranlate it to oracle but some tables didn't populate with data it gave me this error (Unable to migrate data from source table maeva.client_payment_mode to destination table root.CLIENT_PAYMENT_MODE :
Unknown character set index for field "12819" received from server)

Barry,
I'm having the same problem; I included the details you're asking about in this thread:
Re: UNKNOWN CHARACTER SET INDEX FOR FIELD '560' RECEIVED FROM SERVER.
Thanks,
Matt.

IMP-00037: Character set marker unknown ?

Similar Messages

Maybe you are looking for