Re: Internal imp errors importing 8.1.7 dump file on 10.2

From: Vladimir M. Zakharychev <vladimir.zakharychev_at_gmail.com>
Date: Mon, 5 Jul 2010 11:44:48 -0700 (PDT)
Message-ID: <577d547e-751b-4acb-b7b3-f71ecc747c99_at_c10g2000yqi.googlegroups.com>



On Jul 5, 5:31 pm, Wolfram Rösler <wolfram.roes..._at_gmail.com> wrote:
> Hello,
>
> I have a 24 GB dump file that was created with Oracle 8.1.7 on AIX,
> which I want to proof-read with 10.2 on Windows, so I did:
>
> imp system/xxx file=export.dmp fromuser=name touser=name show=y
>
> It runs fine for a while but then prints the following errors:
>
>  illegal lob length marker 49408
>  bytesread = 00000000000
>  TABLE = MYTABLENAME
> IMP-00098: INTERNAL ERROR: impgst2
> IMP-00008: unrecognized statement in the export file:
> <07><1e>
> ...
> IMP-00032: SQL statement exceeded buffer length
>
> These occur several times until IMP-00008 repeats forever (until I
> aborted the import 16 hours later). Importing with a larger buffer
> ("buffer=2000000") made no difference.
>
> The dump file can be imported without errors and warnings on the
> source machine (8.1.7 on AIX). The original dump file and my copy of
> it have identical CRCs so it's not a corruption issue. I'm running imp
> directly on the DB server so it's not a client/server compatibility
> issue either.
>
> The export parameters are nothing special:
>
> exp system/xxx file=export.dmp owner=name consistent=y
>
> Any idea what's going wrong? Is the dump file ok, and if so, how can I
> import it?
>
> Thanks for any help
> W. Rösler

Most probably 10.2 is not fully backwards-compatible with 8.1.7 (clients surely aren't.) Metalink note #132904.1 says that direct export from 8.1.7 and import into 10.2 is not supported. One way to import I can think of is to import the dump into an intermediate 9.2.0.8 database, export from there with 9.2 exp utility and then import this new dump into 10.2. 9.2 is compatible with 8.1.7 and 10.2 is compatible with 9.2 as far as imp/exp are concerned.

Also, make sure both source and target databases (and tools) are at the latest respective patchset levels (8.1.7.4 and 10.2.0.5 or 10.2.0.4, whichever is available for your platform.)

Hth,

   Vladimir M. Zakharychev Received on Mon Jul 05 2010 - 13:44:48 CDT

Original text of this message