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

Similar Messages

  • 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 시 imp-00008오류 해결 방법 좀 부탁드립니다.

    안녕하세요.
    import 시 imp-00008 오류와 함께 imp.exe 응용프로그램 오류로 import 가 중지되어버림니다.
    imp systm/pwd file=exp.dmp fromuser=scott touser=scott
    이상한건 import 가 중지되어도 데이터 양이 적어서 그런 지는 모르지만 테이블 생성과 함께 데이터는 import 되어있다는 겁니다.
    위와 같은 오류는 왜 나는 건가요?
    그리고 해결방법은 없을까요?
    읽어주셔서 감사하고 답변 주시면 더욱 감사하겠습니다.

    이 메세지를 질문으로 주셨다면 좀 더 빠르게 처리했겠죠.
    그리고 원래 이런 사항은 OS version, OS word size, DB version, DB word size
    가 있어야 합니다. 버젼에 따라서 경우가 다르거든요.
    이 사항을 자세하게 알려주시지 않아서 진행하기가 어렵네요.
    어디서 exp해서 imp하는 건지요?
    글 수정:
    민천사 (민연홍)
    아래에 생락하셨던 create문은 어떻게 되나요?
    그리고 exp/imp 명령까지 올려주세요. direct mode로 exp하셨나요?
    alert log에 어떤 에러가 떨어지지는 않았나요?
    그리고 DB의 language는 어떻게 되나요? exp할 때에 K016MSWIN949
    인데 OS의 NLS_LANG은 UTF8이군요. imp하는 DB가 UTF8인가요?
    KO16MSWIN949에서 한글은 2바이트 영문은 1바이트 이지만..
    UTF8에서는 한글은 3바이트 영문은 2바이트?입니다.
    좀 더 크게 들어가게 됩니다.
    1. How does NLS affect import/export?
    Import and export are client products, in the same way as SQL*Plus or
    Oracle Forms, and will therefore translate characters from the database
    character set to that defined by NLS_LANG. The character set used for
    the export will be stored in the export file and, when the file is imported,
    the import will check the character set that was used. If it is different to
    that defined by NLS_LANG at the import site, the characters will be
    translated to the import character set and then, if necessary, to the
    database character set.
    References:
    Note 15095.1 Export/Import and NLS Considerations
    Note 48644.1 Identifying the Export Character Set
    2. How should NLS_LANG be set when using export?
    Oracle recommendeds to set the character set part of NLS_LANG environment parameter
    to the same character set as the character set of the database you are exporting.
    select value from nls_database_parameters where parameter='NLS_CHARACTERSET';
    That way no conversion will take place and the exportfile will be created
    in the same character set as the orginal database and contain ALL data from
    original database (even incorrectly stored data if that would be the case).
    Even if the plan is to import this into a database with a different character set
    later the conversion can be postponed until the import.
    3. How should NLS_LANG be set when using import?
    If the source and target database have the same character set,
    the character set part of the NLS_LANG should be set to that same character set
    on both the export and the import.
    Even if the character sets of the exporting and importing databases
    are not the same the best (prefered) value to use for
    the character set part of NLS_LANG on both export and import is still
    the character set of the source database.
    select value from nls_database_parameters where parameter='NLS_CHARACTERSET';
    But setting the NLS_LANG to the character set of the target database during import
    is also correct.
    That way conversion only takes place once, either on export or on import.
    However, the preferred place to do the conversion is between the import executable
    and the target database.
    4. Example: you want to go from an WE8MSWIN1252 to an UTF8 db:
    (note that this is only the exp/imp example, if you want to migrate to UTF8
    check Note 260192.1 for the full story )
    1) double check the NLS_CHARACTERSET on the SOURCE database
    select * from nls_database_parameters where parameter = 'NLS_CHARACTERSET';
    and export with the NLS_LANG set to AMERICAN_AMERICA.<NLS_CHARACTERSET>
    In this case we want to create a export file containing WE8MSWIN1252 data.
    (This is also the setting you want to use if you take an
    export as backup)
    on unix this is:
    $ set NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252
    $ export NLS_LANG
    $ exp ....
    on windows this is:
    c:\>set NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252
    c:\>exp ....
    2) import with the NLS_LANG set to American_america.WE8MSWIN1252 (= source NLS_CHARACTERSET)
    into the new UTF8 db.
    on unix this is:
    $ set NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252
    $ export NLS_LANG
    $ imp ....
    on windows this is:
    c:\>set NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252
    c:\>imp ....
    The conversion to UTF8 is done while inserting the data
    in the UTF8 database.
    We recommend to set the NLS_LANG explicit in the current shell for unix
    (-> Note 131207.1 How to Set Unix Environment Variable )
    or in the dos box used for the exp or imp tool on windows.
    (-> "c:\>set NLS_LANG=AMERICAN_AMERICA.<characterset of the source database>")
    글 수정:
    민천사 (민연홍)

  • 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

  • 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

  • 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.

  • Character set err while trying to import a db

    when i am trying to import a DB I have the following problem, i can't read the import instruction because of the character set:
    C:\oracle>imp
    Import: Release 8.1.7.0.0 - Production on ╟ط┼╦غوغ 05 16 19:55:33 2005
    (c) Copyright 2000 Oracle Corporation. All rights reserved.
    ╟╙ف ╟غف╙╩╬╧ف: yaser/yaser
    ف╩╒غ ╚ض: Oracle8i Release 8.1.7.0.0 - Production
    JServer Release 8.1.7.0.0 - Production
    \ n فغط ╟غ╟╙╩م╤╟╧: EXPDAT.DMP > E:\WORLDDOC\dmp\yaser14082003.DMP
    ├╧╬غ ┼╓╟ط╔ ═╠ف ╟غ╨╟ع╤╔ ╟غك╙م╫╔ (╟غ═╧ ╟غ├ظ╒ل قك 8192) 30720>
    ╩ف ╩عكمµ فغط ╟غ╩╒╧م╤ ╚ك╟╙╫╔ EXPORT:V08.01.07 فµ ╬غ╟غ ف╙╟╤ ╩ظغم╧م
    ╩ف ╟غ╟╙╩م╤╟╧ طم AR8MSAWIN ف╠فك┘╔ ═╤كط كAR8MSAWIN NCHAR ف╠فك┘╔ ═╤كط
    ظ╟╞ف╔ ف═╩كم╟╩ فغط╟╩ ╟غ╟╙╩م╤╟╧ طظ╫ (غ┌ع/ط╟): ط╟ >
    ┼قف╟غ ╬╫├ ╩عكمµ ╚╙╚╚ ك╠ك╧ ع╟╞µ (غ┌ع/ط╟): ط╟ >
    فµ═ ╟غ╟╙╩م╤╟╧ (غ┌ع/ط╟): غ┌ع >
    ╟╙╩م╤╟╧ ╚م╟µ╟╩ ╟غ╠╧كغ (غ┌ع/ط╟): غ┌ع >
    ╟╙╩م╤╟╧ فغط ╟غ╩╒╧م╤ ╚╟غع╟فغ (غ┌ع/ط╟): ط╟ >
    ╟╙ف ╟غف╙╩╬╧ف: yaser/yaser
    ├╧╬غ ├╙ف╟┴ ╟غ╠╧كغ (T) ├ك ╟غفظ╫┘ (T:P) . ╩┘µم ╟غظ╟╞ف╔ ╟غ╬╟غم╔ عغ ╟غ╠╧╟كغ غغف╙╩╬╧ف
    ├╧╬غ ╟╙ف ╟غ╠╧كغ (T) ├ك ╟غفظ╫┘ (T:P). ├ك غ╟ ╘م┴:
    . ╟╙╩م╤╟╧ ╟غع╟╞µ╟╩ yaser طم yaser
    IMP-00034: ╩═╨م╤: Fromuser "yaser/yaser" ┌م╤ فك╠ك╧ طم فغط ╟غ╩╒╧م╤
    . ╟µ╩قل ╟غ╟╙╩م╤╟╧ ╚µ╠╟═ ف┘ ك╠ك╧ ╩═╨م╤╟╩
    C:\oracle>

    You will need to update the Language portion of your NLS_LANG on the OS you are running Import from. The Language and and not the chracter set controls the language for messages.
    NLS_LANG = language_territory.charset
    For more information on setting the NLS_LANG and it's effect check the globalization guide or the following Metalink notes:
    [NOTE:179133.1] The correct NLS_LANG in a Windows Environment
    [NOTE:264157.1] How to set correctly NLS_LANG on Unix Environments

  • Character set change? Help!

    Hi,
    I am doing imports and the export client uses ZHS16GBK character set (simplified chinese) and my imports are done in
    US7ASCII which is not a super set of the aforementioned character set. I want to change to ZHS32GB18030 which is a super set
    of US7ASCII and ZHS16GBK. Is it possible to change my character set in sql plus?
    Also could this character conversion cause an IMP-00008 error (unrecognized statement in export file)?
    -Ashley

    This one my logs. It has the error ORA 942, this is an error that I have found in most of my files that I am importing:
    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 file created by EXPORT:V10.01.00 via conventional path
    Warning: the objects were exported by SMARTGPS2006, not by you
    import done in US7ASCII character set and AL16UTF16 NCHAR character set
    import server uses AL32UTF8 character set (possible charset conversion)
    export client uses ZHS16GBK character set (possible charset conversion)
    export server uses UTF8 NCHAR character set (possible ncharset conversion)
    . importing SMARTGPS2006's objects into RPI
    . . importing partition "MCC_ASYN_POS":"MCC_ASYN_POS200706" 0 rows imported
    . . importing partition "MCC_ASYN_POS":"MCC_ASYN_POS200802" 0 rows imported
    . . importing partition "MCC_ASYN_POS":"MCC_ASYN_POS200803" 0 rows imported
    . . importing partition "MCC_ASYN_POS":"MCC_ASYN_POS200804" 0 rows imported
    . . importing partition "MCC_ASYN_POS":"MCC_ASYN_POS200903" 22939070 rows imported
    . . importing partition "MCC_ASYN_POS":"MCC_ASYN_POS200904" 0 rows imported
    . . importing partition "MCC_ASYN_POS":"MCC_ASYN_POS200905" 0 rows imported
    . . importing partition "MCC_ASYN_POS":"MCC_ASYN_POS200906" 0 rows imported
    . . importing partition "MCC_ASYN_POS":"MCC_ASYN_POS200907" 0 rows imported
    IMP-00017: following statement failed with ORACLE error 942:
    "ALTER TABLE "MCC_ASYN_POS" ADD CONSTRAINT "MCC_ASYN_POS_OEMCODE_NEW" FOREIG"
    "N KEY ("OEMCODE") REFERENCES "OEM" ("OEMCODE") ENABLE NOVALIDATE"
    IMP-00003: ORACLE error 942 encountered
    ORA-00942: table or view does not exist
    About to enable constraints...
    Import terminated successfully with warnings.
    From doing research I have found that IMP-00008 is because the file is corrupt. Is this always the case?
    Also, you said there errors would not be because of a character set conversion issue, does that mean I do need to change my character set?
    Ashley

  • MP-00038: Could not convert to environment character set's handle

    I wan't import an Oracle 10g database dump into Oracle Express:
    source DB runs on Linux
    NLS_LANG=AMERICAN_AMERICA.WE8DEC
    destination
    Windows:
    NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252
    X:\>imp system/manager file=edb.dmp full=y
    Import: Release 10.2.0.1.0 - Production on Wed Nov 14 09:25:40 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Productio
    n
    IMP-00038: Could not convert to environment character set's handle
    IMP-00000: Import terminated unsuccessfully
    What can I do ???

    Hi sivaram,
    how exactly did you export from 11g, and how did you try to import? (Commands with parameters would be great, probably also the first lines of each log file)
    And which exact database release did you export from? Which character set does it use?
    -Udo

  • Importing XE export into Enterprise ED DB getting IMP-00008: unrecognized .

    I have 2 WIndows Express editon databases V10.2.0.1 one on each laptop and an Enterprise Ed DB V10.2.0.1.0 on a Window's server. If I export a schema (using exp) from the database on laptop XE 1 and then import it into laptop XE 2 database then there are no problems and it all works fine. If I take the same export file and try to import it into the Enterprise Ed using the same command:
    imp userid=system/XXXXX@dev file=c:\file.dmp log=c:\file.log fromuser=LICHE touser=LICHE SHOW=Y
    then I get the following problem
    Export file created by EXPORT:V10.02.01 via conventional path
    import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
    IMP-00008: unrecognized statement in the export file:
    . importing LICHE's objects into LICHE
    "BEGIN "
    "sys.dbms_logrep_imp.instantiate_schema(schema_name=>SYS_CONTEXT('USERENV','"
    "CURRENT_SCHEMA'), export_db_name=>'XE', inst_scn=>'6682797');"
    "COMMIT; END;"
    "ALTER SESSION SET CURRENT_SCHEMA= "LICHE""
    "CREATE SEQUENCE "SERVICELEVEL_SEQ" MINVALUE 1 MAXVALUE 99999999999999999999"
    "9999999 INCREMENT BY 1 START WITH 8 NOCACHE NOORDER NOCYCLE"
    Why doesn't the import work?
    regards
    Paul Platt

    I found the problem. I was using the wrong version of imp.exe
    I was using the version in the bin directory under 10g Developer\bin rather than the client software product\bin directory.
    thanks
    Paul P

  • IMP-00008 Strange behaviour of IMPORT utility

    I'm importing a dump file which works fine multiple times. Whenever I use the import argument constraints=N the import starts and after a while hammers the output with strange error messages as listed at the end. As soon as I set the argument to constraints=Y it will work again. Any idea what to do?
    Regards
    Joerg
    Import: Release 8.1.7.0.0 - Production on Thu May 8 13:55:49 2003
    (c) Copyright 2000 Oracle Corporation. All rights reserved.
    Connected to: Oracle8i Enterprise Edition Release 8.1.7.4.0 - Production
    With the Partitioning option
    JServer Release 8.1.7.4.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-00008: unrecognized statement in the export file:
    TB
    IMP-00008: unrecognized statement in the export file:
    TB

    what version of import are you using
    If the RDBMS version is 8.1.7.0
    then there seems to be a bug registerd
    This is bug: 1696451
    Fixed-Releases: 8172 9010
    IMP-17, ORA-2430 possible importing with CONSTRAINTS=N.
    Workaround:
    Ignore the errors, they are just due to IMPORT trying to enable
    constraints which have not been imported.
    Please apply the patch set 8.1.7.4
    hope this helps
    thanks
    devi

  • Oracle Import errors  IMP-00098,   IMP-00028 , IMP-00008

    Hi all
    I have successfully exported a schema called ahc from Database 10g Enterprise Edition Release 10.2.0.1.0 on linux.
    but when i imported in test db server running the same OS and Oracle Versions.it returnd errors .
    i took the export three times but got the same error while importing.
    here is out put
    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 WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
    export client uses US7ASCII character set (possible charset conversion)
    . . importing table "ADM_DTL" 0 rows imported
    . . importing table "ADVANCES" 1 rows imported
    . . importing table "BANK" 10 rows imported
    . . importing table "BASIC" 2 rows imported
    . . importing table "DESIGN" 240 rows imported
    . . importing table "DISTRICT" 26 rows imported
    . . importing table "EMPLOYEEMAIN" 3 rows imported
    . . importing table "GRADES" 185 rows imported
    . . importing table "ICD" 15413 rows imported
    . . importing table "MAINCODES" 336 rows imported
    . . importing table "QUALIFICATION" 15 rows imported
    . . importing table "SALARY" 2 rows imported
    . . importing table "SPALLOWANCE" 16 rows imported
    . . importing table "TBL_LAB_GROUP" 470 rows imported
    . . importing table "TBL_LAB_MAIN_DTL" 231992 rows imported
    . . importing table "TBL_LAB_MAIN_MAS" 79552 rows imported
    . . importing table "TBL_LAB_OPINION" 856 rows imported
    . . importing table "TBL_LAB_RESULT"
    illegal lob length marker 32770
    bytesread = 00000000000
    TABLE = TBL_LAB_RESULT
    IMP-00098: INTERNAL ERROR: impgst2
    IMP-00028: partial import of previous table rolled back: 137170 rows rolled back
    IMP-00008: unrecognized statement in the export file:
    IMP-00008: unrecognized statement in the export file:
    IMP-00008: unrecognized statement in the export file:
    *¿4¿¿¿E¿N¿*
    *#¿U="¿1¿¿¿¿;¿~¿O¿¿¿w4H¿¿¿"¿"¿>`N¿¿G¿¿¿¿¿¿¿¿'¿$V¿¿¿¿¿6¿i¿2Xn¿.¿¿_<5H¿¿q¿¿¿¿¿<c¿¿#U07¿¿¿n¿Uh¿*¿¿¿¿¿N¿¿¿v+2db¿9¿¿#jd¿¿¿7¿At¿(*
    *IMP-00008: unrecognized statement in the export file:*
    *¿¿¿V )((*
    *IMP-00008: unrecognized statement in the export file:*
    *¿H¿m¿¿*
    *IMP-00008: unrecognized statement in the export file:*
    *IMP-00008: unrecognized statement in the export file:*
    *IMP-00008: unrecognized statement in the export file:*
    c¿1
    IMP-00008: unrecognized statement in the export file:
    *¿¿¿¿¿PIz¿o/¿¿o¿O¿\¿7¿¿f¿¿¿(¿¿@     @*
    IMP-00008: unrecognized statement in the export file:
    *¿¿¿"¿¿G¿0¿U¿v¿¿1!¿J¿f>¿¿¿44s¿RYD¿j¿¿¿c¿!¿*
    *IMP-00008: unrecognized statement in the export file:*
    *¿¿v)<¿¿i¿:f¿A@*
    *IMP-00008: unrecognized statement in the export file:*
    *IMP-00008: unrecognized statement in the export file:*
    *IMP-00008: unrecognized statement in the export file:*
    *IMP-00008: unrecognized statement in the export file:*
    *IMP-00008: unrecognized statement in the export file:*
    *IMP-00008: unrecognized statement in the export file:*
    *¿%¿1¿¿¿K@*
    *IMP-00008: unrecognized statement in the export file:*
    *IMP-00008: unrecognized statement in the export file:*
    *:BLAN.TERMID:=:GLOBAL.TERMID;*
    *IMP-00008: unrecognized statement in the export file:*
    *:BLAN.SHIFT:=:GLOBAL.SHIFT;*
    *IMP-00008: unrecognized statement in the export file:*
    *IMP-00008: unrecognized statement in the export file:*
    *END;*
    *IMP-00008: unrecognized statement in the export file:*
    *IMP-00008: unrecognized statement in the export file:*
    *r100g0b100¿¿*
    *IMP-00008: unrecognized statement in the export file:*
    *00r25g100b75@*
    *IMP-00008: unrecognized statement in the export file:*
    *00r50g100b75¿*
    *IMP-00008: unrecognized statement in the export file:*
    *00r75g100b75¿*
    *IMP-00008: unrecognized statement in the export file:*
    *00r88g100b75¿*
    *IMP-00008: unrecognized statement in the export file:*
    *IMP-00008: unrecognized statement in the export file:*
    Import terminated successfully with warnings.
    Edited by: farnaw4u on Feb 26, 2010 10:17 AM

    Hello,
    You may experience a bug or a corruption in the "dump". If it's a corruption you may retry your export/import.
    But, anyway, the classical Export/Import is not recommended. Starting with 10.1 you should use Datapump
    (expdp/impdp).
    Please, find enclosed a link about this utility:
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14215/part_dp.htm#i436481
    Hope this help.
    Best regards,
    Jean-Valentin

  • 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

  • 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 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.

Maybe you are looking for