Re: "Import succeded with warnings" and ERRORS!?

"Rick Denoire" <100.17706_at_germanynet.de> wrote in message news:9ci2tto1g0lm9cbqrkt4t7mb5v192tmkc4_at_4ax.com...
> "Howard J. Rogers" <howardjr_at_www.com> wrote:
>
> >I think you've made rather hard for yourself by misunderstanding what
Import
> >does when the paths to the data files are different between different
> >databases. Import couldn't give a monkeys: Table A from source
tablespace
> >DATA01 will quite happily be created in target tablespace DATA01,
regardless
> >of where the datafiles for the target tablespace are physically located.
> >
> >So, no, Import will not "fail if the paths of the DB Files differ".
>
> Are you saying that the import will succeed even if the needed
> tablespaces are missing before doing the import? If tables go to the
> system tablespace, that wouldn't not be a "success" for us; the
> resulting DB would be plain wrong.
>
> I have read that if the paths differ, the tablespaces will have to
> exist prior to importing the dump. Let me know if you think this is
> true, because it would mean that there is no sure way to import a dump
> if some additional information about the exporting DB is missing.
>

[rest snipped]
> Thanks
>
> Rick

The assertion about pre-existing tablespaces should be read as follows

'If you want to/need to change the location of the files you have to precreate the tablespaces (because otherwise the tablespaces will either be created in the wrong location or the create tablespace command will simply fail.)'
That said you can quite easily extract the commands from your export, by issuing
imp .. show=y full=y log=<any file>
and edit <any file>

I'm not sure what's not easy about that.

Hth

Sybrand Bakker
Senior Oracle DBA Received on Sat Oct 20 2001 - 05:34:18 CDT