On Sep 28, 3:58 am, Frank van Bortel <frank.van.bor..._at_gmail.com>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hasta wrote:
>
> >> It's not just about constraints or the order of tables.
> >> The original question was more generic, and yes, sometimes
> >> you'll get errors because dependent objects do not
> >> (yet) exist: procedures, functions, packages and views to name
> >> a few, can either be invalid and need to be recompiled, or are
> >> not created at all, which can happen with views.
>
> > Woaw ! When is a view not created at all, Frank ?
>
> Whenever you have a 'Synonym translation no longer valid'
> (ORA-00940?) error. Howard will probably argue this is not
> an import error, but a user error.
> It is not - it is simply the sequence in which import
> handles objects. Rerun the import with ignore=y
> and rows=n, and it should be OK.
>
> - --
> Regards,
> Frank van Bortel
Howard will argue that you won't get 'synonym translation no longer
valid' errors **as a result of** the import. Those errors must have
been there in the original database. Import does not CAUSE them as a
result of its ORDER of imports.
Received on Thu Sep 27 2007 - 17:45:03 CDT
