Re: Import error between versions

What version and patch level of "exp" did you use to do the export?

What version and patch level of "imp" did you use to do the import in each case you mentioned?

Regards,
Dave

"Tom" <tomNOSPAM_at_teameazyriders.com> wrote in message news:gaPtb.1729$__.16461848_at_news-text.cableinet.net...
> Hi,
>
> I'm testing my upgrade to 9i from 8.1.x between OS's
>
> My production system is moving from 8.1.5 on Solaris7 to 9.2.0.4 on Linux.
I
> exported my users into dump files of 1GIG each. I can import these fine
> either into new users on the same system or into a new system running the
> same OS and DB version so i know the dumps are not corrupt.
>
> The issue arises when i try and import these into a new system running a
> different OS and DB version. The import goes OK until the point it would
> appear to move onto the second file in the dump sequence. The dump fails
and
> the error reported just says segmention fault. There is nothing logged
into
> the alert log or any other log. It behaves like this if i import into
8.1.7
> on Solaris or Windows or also 9.2.0.4 on Linux. The even 'odder' thing is
> that if i allow the export to run into a single file, so avoid the
FILESIZE
> parameter, it imports fine into all DB versions...
>
> Has anyone seen anything like this before or have any idea what might
cause
> it?
>
> My exports are scripted each night and have the following syntax...
>
> exp xxxx/password_at_INST FILESIZE=1G
> FILE=$BACKUPDEST/xxxx0.dmp,$BACKUPDEST/xxxx1.dmp,$BACKUPDES
>

T/xxxx2.dmp,$BACKUPDEST/xxxx3.dmp,$BACKUPDEST/xxxx4.dmp,$BACKUPDEST/xxxx5.dm
> p,$BACKUPDEST/xxxx6.dmp,$BACKUPDEST/xxxx7.dmp,$BACKUPDES
> T/xxxx8.dmp,$BACKUPDEST/xxxx9.dmp log=$BACKUPDEST/xxxx.log
>
> thanks for any imput
>
> Tom
>
>
Received on Sun Nov 16 2003 - 17:58:22 CST