error import after full export
DBAsupport.com Forums - Powered by vBulletin
Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: error import after full export

  1. #1
    Join Date
    Jul 2002
    Posts
    228

    error import after full export

    hi,
    I've exported correctly the dmp.
    exp system/manager@oradb full=y file=c:\x.dmp log=error.log

    but when I try import this dmp, I get these errors:

    imp system/manager@oradb fromuser=tom touser=sam file=c:\x.dmp log=error_imp.log

    IMP-00019:row rejected due oracle error 1401
    IMP-00003racle error 1401 encountered
    ORA-1401:inserted value too large for column
    Column1 0000232
    Column2 cat
    ..................
    .................

    How is it possible that I get imp error if export is correct?

    Could you help me??

    Raf

  2. #2
    Join Date
    Jan 2002
    Location
    Up s**t creek
    Posts
    1,525
    Are you importing the table definitions as well? or does the table already exist?

    If so it's possible the defintion of the table your trying to import into does not match the database you exported from.

    Regards
    Jim
    Oracle Certified Professional
    "Build your reputation by helping other people build theirs."

    "Sarcasm may be the lowest form of wit but its still funny"

    Click HERE to vist my website!

  3. #3
    Join Date
    Jul 2002
    Posts
    228
    I truncate table with error and disable all constraints on this table
    after I exported this table:
    exp tom/tom@oradb file=tb.dmp tables=ER

    after I imported this table:
    imp system/manager@oradb file=tb.dmp fromuser=tom touser=sam ignore=y

    but I get same previous error:

    IMP-00019:row rejected due oracle error 1401
    IMP-00003racle error 1401 encountered
    ORA-1401:inserted value too large for column
    ..........
    ..........
    ..........

    Why
    Raf

  4. #4
    Join Date
    Jul 2001
    Location
    Slovenia
    Posts
    422
    Is this the same database for exp and imp?
    Tomaž
    "A common mistake that people make when trying to design something completely
    foolproof is to underestimate the ingenuity of complete fools" - Douglas Adams

  5. #5
    Join Date
    May 2001
    Location
    Maryland, USA
    Posts
    409
    As per metalink Doc ID : 188645.1, This may be due to Character Set UTF8 of your database. For more info, Check that Document in metalink.

    Thanks.
    -- Dilip

  6. #6
    Join Date
    Jul 2002
    Posts
    228
    No, TomazZ
    I exported from oradb and import in a new instance.

    Raf

  7. #7
    Join Date
    Jul 2001
    Location
    Slovenia
    Posts
    422
    patel_dil has an answer for you.
    Tomaž
    "A common mistake that people make when trying to design something completely
    foolproof is to underestimate the ingenuity of complete fools" - Douglas Adams

  8. #8
    Join Date
    Jan 2002
    Location
    Up s**t creek
    Posts
    1,525
    Truncating the table will not change it's definition, and disabling constraints is also not necessary, the error relates to the fact that it is trying to insert data which is outsides the bounds of the coloumn.

    eg.

    If you have userA and userB both with a table CUSTOMER but userA has the NAME column defined as varchar2(20) and userB has the NAME column defined as varchar2(10). If the names contained in userA's table are greater than 10 characters in length if you try to import the table data into userB the import will fail with the error you are getting.

    Either drop the tables in the user you importing into or update the table defintions to match the user you are exporting from.

    HTH
    Jim
    Oracle Certified Professional
    "Build your reputation by helping other people build theirs."

    "Sarcasm may be the lowest form of wit but its still funny"

    Click HERE to vist my website!

  9. #9
    Join Date
    Jul 2002
    Posts
    228
    ok,
    I have resolved my problem ORA-1401 (I have increased the columns with error, after I've export and import again).

    But now I get another error:

    IMP-00017: following statement failed with ORACLE error 2298:
    "ALTER TABLE "ACTS" ENABLE CONSTRAINT "ACTS_SECURITY""
    IMP-00003: ORACLE error 2298 encountered
    ORA-02298: cannot validate (oradb.ACTS_SECURITY) - parent keys not found
    IMP-00017: following statement failed with ORACLE error 2298:
    "ALTER TABLE "CLASS" ENABLE CONSTRAINT "CLASS_SECURITY""
    IMP-00003: ORACLE error 2298 encountered
    ORA-02298: cannot validate (oradb.CLASS_SECURITY) - parent keys not found

    these constraints references table groups of user sam.

    How can I resolve this problem?
    Raf

  10. #10
    Join Date
    Jan 2002
    Location
    Up s**t creek
    Posts
    1,525
    You are going to have to either provide the parent tables with the necessary rows so that the constraints can be validated or use the tables with disabled/removed constraints.
    Jim
    Oracle Certified Professional
    "Build your reputation by helping other people build theirs."

    "Sarcasm may be the lowest form of wit but its still funny"

    Click HERE to vist my website!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width