IMP-00009: abnormal end of export file
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 8 of 8

Thread: IMP-00009: abnormal end of export file

  1. #1
    Join Date
    Jun 2002
    Location
    Longmont, Colorado
    Posts
    174

    IMP-00009: abnormal end of export file

    I'm trying to import a dump file into my 9205 on Solaris9.
    The export came from an 8163 on NT and was a taken with the following parameters:

    file=rlcproc_exp.dat
    log=rlcproc_exp.log
    buffer=204800
    full=y

    I am importing it into the 9205 with the following parameter:

    file=rlcproc_exp.dat
    log=IMP_LCPROCESS.log
    buffer=512000000
    ignore=y
    fromuser=LCPROCESS
    touser=LCPROCESS
    commit=N

    Here's the log:
    ###############################
    Connected to: Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
    JServer Release 9.2.0.5.0 - Production

    Export file created by EXPORT:V08.01.06 via conventional path
    import done in WE8ISO8859P1 character set and AL16UTF16 NCHAR character set
    export server uses WE8ISO8859P1 NCHAR character set (possible ncharset conversion)

    . importing LCPROCESS's objects into LCPROCESS
    . . importing table "AUDIT_FIXALARMS" 0 rows imported
    . . importing table "FIXALARMS"
    IMP-00009: abnormal end of export file
    IMP-00028: partial import of previous table rolled back: 262136 rows rolled back

    Import terminated successfully with warnings.
    ###################################

    What is causing this? Is there a known bug with importing directly into 9205 from 8163??

    Help.

    Also, subsequent import attempts now show:

    IMP-00009: abnormal end of export fileSegmentation Fault(coredump)


    Any ideas what's causing these?

  2. #2
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    Your dump file is corrupt. Did you FTP in binary mode?
    Jeff Hunter
    marist89@yahoo.com
    http://marist89.blogspot.com/
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

  3. #3
    Join Date
    Jun 2002
    Location
    Longmont, Colorado
    Posts
    174
    I've FTP'd twice and the second time I made sure it wasn't due to a ASCII mistake. And it continues to error.

  4. #4
    Join Date
    Dec 2001
    Posts
    96
    Try taking the export in compress=Y and then import it. I am sure you wont get errors.

  5. #5
    Join Date
    Dec 2001
    Posts
    96
    also, when you ftp it in binary mode,check the file sizes before you start the import . also take compress= Y during export

  6. #6
    Join Date
    Dec 2000
    Location
    Ljubljana, Slovenia
    Posts
    4,439
    Originally posted by aj_usa
    Try taking the export in compress=Y and then import it. I am sure you wont get errors.
    That's an odd suggestion. That's even dangerous suggestion. And its certanly not related the problem discussed here. General suggestion about COMPRESS in export should be: "NEVER USE COMPRESS=Y! (unless you are absolutely sure you understand what are the implkication of COMPRESS=Y)"
    Jurij Modic
    ASCII a stupid question, get a stupid ANSI
    24 hours in a day .... 24 beer in a case .... coincidence?

  7. #7
    Join Date
    Jun 2002
    Location
    Longmont, Colorado
    Posts
    174
    OK...
    It was a bad ftp job. The file sizes weren't even close.
    Sorry. I should have checked before posting.
    THanks for the caution about COMPRESS=y...I'll keep it in mind.

  8. #8
    Join Date
    Apr 2002
    Location
    France
    Posts
    118
    I agree with Jmodic about the compress option.

    I'll add that the export was already taken with compress=Y as this is (sadly) the default.
    If there is no solution, it is because there is no problem - Shadok -

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