Path: news.cambrium.nl!textnews.cambrium.nl!feeder2.cambriumusenet.nl!feed.tweaknews.nl!209.197.12.242.MISMATCH!nx01.iad01.newshosting.com!newshosting.com!69.16.185.11.MISMATCH!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!postnews.google.com!j8g2000yqd.googlegroups.com!not-for-mail From: "Vladimir M. Zakharychev" Newsgroups: comp.databases.oracle.server Subject: Re: Internal imp errors importing 8.1.7 dump file on 10.2 Date: Wed, 7 Jul 2010 02:50:06 -0700 (PDT) Organization: http://groups.google.com Lines: 82 Message-ID: References: <752559eb-655f-4c0c-b6cf-c4bb94f2bda5@z8g2000yqz.googlegroups.com> NNTP-Posting-Host: 91.196.34.22 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1278496206 18228 127.0.0.1 (7 Jul 2010 09:50:06 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Wed, 7 Jul 2010 09:50:06 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: j8g2000yqd.googlegroups.com; posting-host=91.196.34.22; posting-account=PAnILQoAAAD84SMI2vqfU32t6U_KSuGX User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 ( .NET CLR 3.5.30729; .NET4.0E),gzip(gfe) Xref: news.cambrium.nl On Jul 6, 7:51=A0pm, Mark D Powell wrote: > On Jul 5, 9:31=A0am, Wolfram R=F6sler 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=3Dexport.dmp fromuser=3Dname touser=3Dname show=3Dy > > > It runs fine for a while but then prints the following errors: > > > =A0illegal lob length marker 49408 > > =A0bytesread =3D 00000000000 > > =A0TABLE =3D 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=3D2000000") 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=3Dexport.dmp owner=3Dname consistent=3Dy > > > 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=F6sler > > According to my reading of Vlad's reference: > Compatibility Matrix for Export And Import Between Different Oracle > Versions [Video] #132904.1 > > An 8.1.7.4 export can be read by 10.2 imp. > My bad indeed, I read the matrix incorrectly. Direct import from 8.1.7 to 10.2 seems to be officially supported. > I would think the fact you are running this with show=3Dy indicates the > dmp file is corrupted. =A0At least that is what the error means per > note: > > IMP-00098: INTERNAL ERROR: impgst2Segmentation Fault - core dumped > #578616.1 > > zero length lobs are also a possible issue > Bug 3890213 - IMP-98 possible importing zero length Lobs with > CHUNKSIZE > 32767 #3890213.8 > > So you could have a zero length LOB to fix before exporting or perhaps > as mentioned the copy of the export dmp file was not done using a > binary FTP but there is a very good chance the export is corrupted. > > HTH -- Mark D Powell -- Strange thing is that according to the OP this same export dump is processed without errors on 8.1.7, so this must be either a bug, an incompatibility or a corruption. Since 8.1.7 to 10.2 import is supported and mentioned zero length LOB bug is fixed in 10.2.0.1 base release, we are left with corruption, but the OP says file checksums match. I don't know how the file was checksummed, but I'd recommend to zip it on source host and transfer compressed dump in binary mode to the target - if unzip will not throw any errors, you can be sure the file is not corrupted. Regards, Vladimir M. Zakharychev