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>")
글 수정:
민천사 (민연홍)

Similar Messages

  • Schema Import failed :IMP-00008: unrecognized statement in the export file:

    Hi ,
    I was running a database schema import from a database DMP file.
    I encountered the following error in the log file that was getting generated :
    IMP-00008: unrecognized statement in the export file:
    All the tables got copied except for one. Now what I have thought of is to import that one table again after taking an export from the prod schema.
    But what about the functions,triggers,procedures ?? How do i bring all of them in the schema ?
    If reimporting the schema again the only option ?
    Thanks
    Kk

    Hello,
    In this order:
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14215/exp_imp.htm#i1023988
    Table Objects: Order of Import
    Table objects are imported as they are read from the export file. The export file contains objects in the following order:
    1. Type definitions
    2. Table definitions
    3.Table data
    4.Table indexes
    5. Integrity constraints, views, procedures, and triggers
    6. Bitmap, function-based, and domain indexes
    The order of import is as follows: new tables are created, data is imported and indexes are built, triggers are imported, integrity constraints are enabled on the new tables, and any bitmap, function-based, and/or domain indexes are built. This sequence prevents data from being rejected due to the order in which tables are imported. This sequence also prevents redundant triggers from firing twice on the same data (once when it is originally inserted and again during the import).
    For example, if the emp table has a referential integrity constraint on the dept table and the emp table is imported first, all emp rows that reference departments that have not yet been imported into dept would be rejected if the constraints were enabled.
    When data is imported into existing tables, however, the order of import can still produce referential integrity failures. In the situation just given, if the emp table already existed and referential integrity constraints were in force, many rows could be rejected.
    A similar situation occurs when a referential integrity constraint on a table references itself. For example, if scott's manager in the emp table is drake, and drake's row has not yet been loaded, scott's row will fail, even though it would be valid at the end of the import.

  • 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

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

  • 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

  • Imp-00008: unrecognized statement in the export file

    Hi All,
    I am trying to import an export from Oracle 8.1.7 source system to Oracle 11.2 using imp . I am getting the following errors may times during the import process.
    imp-00008: unrecognized statement in the export file
    The character set of Source data base is WE8DEC and the character set of target data base is WE8MSWIN1252 and i get the below statement during the start of the import
    import done in US7ASCII character set and AL16UTF16 NCHAR character set
    import server uses WE8MSWIN1252 character set (possible charset conversion)
    export client uses WE8DEC character set (possible charset conversion)
    export server uses WE8DEC NCHAR character set (possible ncharset conversion)
    The error imp-00008: unrecognized statement in the export file is it due to the Oracle version compatibility or due to Character set compatibility issue.
    I tried to create a new Database on same Oracle sever and i cant find WE8DEC in the list of character set to choose. Please help me on how to proceed.
    Regards,
    alen.

    934571 wrote:
    Hi Srini,
    Data is getting loaded correctly, but i get several of these error imp-00008: unrecognized statement in the export file messages during the import process, so i am not sure what is missing.
    Pl post the complete error message from the import log file.
    1) Is it possible to import the dump exported form oracle 8 into oracle 11?? Do we need to take any special care during the import ??
    Yes - no special requirements are needed.
    2) The Oracale Database character set it WE8DEC, but when i try to create a new database in 11 , i dont find that character set , is the character set obsolete now , if so what character set is super set of WE8DEC ??
    Pl post exact OS and database versions. Ideally you should be using AL32UTF8 for all new databases. WE8DEC is a deprecated characterset.
    See section 4.2.1 here - http://docs.oracle.com/cd/E11882_01/install.112/e24186/install.htm#BABFDDEA
    Thanks,
    Alen.HTH
    Srini

  • IMP-00008: unrecognized statement in the export file, oracle 11gr2 on redhat 5

    I am using Oracle 11g R2 on Radhat 5 linux to import(imp) a dmp file with a table with blob data type. I got the following errors with binary non-ascii on the screen and failed imp at that table:
    IMP-00008: unrecognized statement in the export file: (a lot of non-ascii characters followed)
    How do that happen and how do we handle it?
    -Henry

    Hello,
    IMP-00008 may due to several reasons.
    The Dump may be corrupted, you may also hit a Bug and so on, ...
    Is it the only error you got or do you have other error message (for instance IMP-00032) ?
    Else, I don't know why you use EXP/IMP in 11.2, the Original Export/Import is not recommended. You should use DATAPUMP which is much more powerful.
    Please, find enclosed a link about DATAPUMP:
    http://www.oracle-base.com/articles/10g/oracle-data-pump-10g.php
    Hope this help.
    Best Regards,
    Jean-Valentin Lubiez

  • Issue with triggers while importing (imp) to another user

    hi all,
    we have two oracle databases (oracle 10g R2)
    1. production
    2. test (clone of production)
    whenever we need to update the test database for the developers we take a full export dump of the production (hardly 20GB) and import the same into test after dropping the tables in the required schema
    export system/***@production file=exp.dmp log=log.log full=y statistics=nonewe have a schema named user1, in production.
    same is the case in test
    I got a request to refresh the user1 schema in test, but with a different schema user2 (new schema created), as there was some critical dev. work going on with user1 schema.
    hence i didnt want to touch the user1 schema in test environment & after taking an export dump of the production i didnt import it into the same schema.
    i imported the dump data to user 2 schema
    imp system/***@test file=exp.dmp log=implog.log fromuser=user1 touser=user2 statistics=nonethe moment i did this developers working with user1 schema started facing issues when their code hit triggers on user1 schema. all insert/update triggers in the user1 schema started pointing to corresponding tables in user2.
    any clues why something like this happened? what was the mistake in he imp command i used?
    thanks for your time

    Hi,
    Check for the trigger source in your original schema. If it has schema name mentioned before the tables on which the trigger is created, it would create problem during import. While importing, it will reference the previous schema , though you are importing it in new schema.
    If this is the case, remove the schema name from the source and then export and re import.
    Regards
    Vinitaa

  • Import (imp) failing with IMP-00010 error

    Hi Experts,
    I am doing import to Windows from an export dump that was taken on Solaris 10. But the import is failing with the following error.
    IMP-00010: not a valid export file, header failed verification
    IMP-00000: Import terminated unsuccessfully
    I checked the source and target oracle versions and NLS_LANG parameter.
    In both the databases NLS_LANG parameter is set to AMERICAN only. But the oracle versions are different
    Source
    OS : Solaris 10
    Oracle version : *11.2.0.2*
    Export dump : exp_CAAU2.dmp.gz (Export taken by zipping)
    Target
    OS : Windows server 2003
    Oracle Version : *10.2.0.2.0*
    While importing into windows env, it is failing..
    Please let me know the reason why the import is failing?
    Can i upgrade the target oracle version to 11.2.0.2 to succeed the import?

    Hi,
    The IMP indicates this this error is coming from the old imp. This dump file could be from the expdp utility, which would require you to use the impdp utility.
    Source
    OS : Solaris 10
    Oracle version : 11.2.0.2
    Export dump : exp_CAAU2.dmp.gz (Export taken by zipping)
    Target
    OS : Windows server 2003
    Oracle Version : 10.2.0.2.0
    While importing into windows env, it is failing..
    What really matters here is the compatibility level. If your source and target compatibility levels are the same, then with Data Pump, the dumpfile created on the source, would work on the target. If the compatibility levels are different, then use expdp with the version parameter set to the compatibility level of the target.
    Please let me know the reason why the import is failing?Check the suggestions above first.
    Can i upgrade the target oracle version to 11.2.0.2 to succeed the import?It could help, but first check to see if you are using the right utility and then check the compatibility versions.
    Dean

  • Problem during import IMP-00003

    Dear all,
    DB: 10.2.0.4
    Solaris 10
    IMP-00003: ORACLE error 1659 encountered
    ORA-01659: unable to allocate MINEXTENTS beyond 9 in tablespace MEDTC^C
    I have 64Gb free in the tablespace MEDTC. sysaux and systems tablespaces are free.
    tablespace creation script
    CREATE TABLESPACE MEDTC DATAFILE
    '/u04/data/medt02_02.dbf' SIZE 32760M AUTOEXTEND ON NEXT 8K MAXSIZE UNLIMITED
    LOGGING
    ONLINE
    PERMANENT
    EXTENT MANAGEMENT LOCAL AUTOALLOCATE
    BLOCKSIZE 8K
    SEGMENT SPACE MANAGEMENT AUTO
    FLASHBACK ON;
    Any idea ?
    kai

    Thanks Maran,
    ABLESPACE_NAME     BLOCK_ID     BLOCKS     BYTES
    medt          17          507904     4160749568
    medt          507921          507904     4160749568
    medt          1015825          507904     4160749568
    medt          1523729          507904     4160749568
    medt          2031633          507904     4160749568
    medt          2539537          507904     4160749568
    medt          3047441          507904     4160749568
    medt          3555345          507904     4160749568
    medt          4063249          131048     1073545216

  • Importing (imp) a dump (exp) from a schema into another schema

    Hello
    -I know I should read the manual-
    -I also know that there are some experts here who only need two lines to explain it- :)
    I have a dump file from a complete schema (lets call it xx).
    I habe another schema (yy) in the same database and:
    I would like to put that dump file into the schema yy.
    How does the imp command looks like?
    Thank you in advance!

    How does the imp command looks like? To get help say at OS prompt.
    imp help=y
    -aijaz

  • Importing 9.2 to 10.2

    Hi All,
    I'm trying to import a full dump from 9.2 to 10.2 for days now and cannot figure out what the problem is. 10.2 is on a different server but also windows 2003 SP2.
    NLS_LANG of both machines are the same for client and server:
    AMERICAN_AMERICA.WE8ISO8859P1
    UFAT is also same on the server.
    Every time i try to import it fail after a while, tried to export again with diffeent files and splitting up files but getting the same error over and over.:
    This is the error:
    . . importing table "HOLDSUBLEDGER"
    illegal lob length marker 49664
    bytesread = 00000000000
    TABLE = HOLDSUBLEDGER
    IMP-00098: INTERNAL ERROR: impgst2
    IMP-00018: partial import of previous table completed: 181470 rows imported
    IMP-00008: unrecognized statement in the export file:
    IMP-00008: unrecognized statement in the export file:
    IMP-00008: unrecognized statement in the export file:
    f
    IMP-00008: unrecognized statement in the export file:
    f
    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:
    S+_5
    IMP-00008: unrecognized statement in the export file:
    I get a lot of IMP-00008:
    When it goes trough it goes fine for a while and tha again the import stops and end
    IMP-00009: abnormal end of export file
    IMP-00018: partial import of previous table completed: 5084344 rows imported
    Thanx for answering

    IMP-00098: INTERNAL ERROR: impgst2
    IMP-00018: partial import of previous table completed: 181470 rows imported
    IMP-00008: unrecognized statement in the export file: You may need to file a SR for this in metalink.
    Also check if Metalink Doc 278980.1 helps.

  • Mapviewer demo Import error ( imp-00980 )

    I'm encountering an import problem when attempting to import the mvdemo.dmp sample data that is included with the Mapviewer demo into Oracle 9i PEdition. Is there a problem with the the EXP coming from Oracle v8? Here is a sample of the error log output:
    Export file created by EXPORT:V08.01.07 via conventional path
    import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
    export client uses US7ASCII character set (possible charset conversion)
    export server uses US7ASCII NCHAR character set (possible ncharset conversion)
    . importing SCOTT's objects into SCOTT
    . . importing table "STYLES" 250 rows imported
    . . importing table "THEMES" 7 rows imported
    . . importing table "MAPS" 2 rows imported
    . . importing table "CITIES" 195 rows imported
    . . importing table "COUNTIES" 3230 rows imported
    . . importing table "INTERSTATES" 239 rows imported
    . . importing table "STATES" 56 rows imported
    IMP-00017: following statement failed with ORACLE error 980:
    "BEGIN "
    "execute immediate 'INSERT INTO USER_SDO_GEOM_METADATA values (''CITIES'','"
    "'LOCATION'',mdsys.SDO_dim_array(MDSYS.SDO_DIM_ELEMENT(''X'',-180,180,.00000"
    "005),MDSYS.SDO_DIM_ELEMENT(''Y'',-90,90,.00000005)),NULL) ' ; "
    "COMMIT; END;"
    IMP-00003: ORACLE error 980 encountered
    ORA-00980: synonym translation is no longer valid
    ORA-06512: at line 2
    IMP-00088: Problem importing metadata for index CITIES. Index creation will be skipped
    I have discovered that the following view does not exist in the db:
    USER_SDO_GEOM_METADATA
    Help would be appreciated.
    -Peter

    Try connecting to the database as mdsys.
    Look for a table called sdo_geom_metadata_table, and if it is there see if there
    is anything in it. If there isn't anything in it, or it isn't there, try executing:
    prvtgmd.plb from ORACLE_HOME/md/admin. It looks like the
    views might not have been created correctly.
    Dan

  • Speedup the import process using imp tool

    hi,
    how many ways to speedup the import process using imp tool in oracle 9.2.0.8

    Hi,
    Follow below guidelines also:
    IMPORT(imp):
    Create an indexfile so that you can create indexes AFTER you have imported data. Do this by setting INDEXFILE to a filename and then import. No data will be imported but a file containing index definitions will be created. You must edit this file afterwards and supply the passwords for the schemas on all CONNECT statements.
    Place the file to be imported on a separate physical disk from the oracle data files.
    Increase DB_CACHE_SIZE (DB_BLOCK_BUFFERS prior to 9i) considerably in the init$SID.ora file
    Set the LOG_BUFFER to a big value and restart oracle.
    Stop redo log archiving if it is running (ALTER DATABASE NOARCHIVELOG;)
    Create a BIG tablespace with a BIG rollback segment inside. Set all other rollback segments offline (except the SYSTEM rollback segment of course). The rollback segment must be as big as your biggest table (I think?)
    Use COMMIT=N in the import parameter file if you can afford it
    Use STATISTICS=NONE in the import parameter file to avoid time consuming to import the statistics
    Remember to run the indexfile previously created.
    Note: Before following the above guideliness check your requirement aso.
    Best regards,
    Rafi.
    http://rafioracledba.blogspot.com/

Maybe you are looking for