Re: Import Question

On Sep 27, 3:40 am, Frank van Bortel <frank.van.bor..._at_gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> hjr.pyth..._at_gmail.com wrote:
> > On Sep 26, 4:35 am, Frank van Bortel <frank.van.bor..._at_gmail.com>
> > wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
>
> >> not produce errors != constraint violations
> >> but more generic than that
> >> - --
> >> Regards,
> >> Frank van Bortel
>
> > Bearing in mind that the original question was, "is Oracle smart
> > enough to import things in an order that will not produce errors?",
> > give me an error, Frank, that will be caused by changing the order of
> > import of tables which ISN'T a constraint violation.
>
> > Creating indexes before the tables on which they're supposed to be
> > built doesn't count, because import has never been that stupid.
>
> You miss the point.

Er, I don't think so.

> It's not just about constraints or the order of tables.

Actually, that's exactly what it's all about. Indeed, I was careful to quote the OP when making the point that the original question was, "is Oracle smart enough to import things in an order that will not produce errors?"

In an **ORDER** that won't produce **ERRORS**.

Order affecting Errors. Errors dependent on Order. It's pretty bloody black and white, Frank!

Now, name me errors which can occur which are a function of the order of import.

Actually, don't bother, because there aren't any, as your failure or refusal to answer the first time I asked testifies.

> The original question was more generic,

Only if you are prepared to completely re-write it!

>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.

Such errors are not a function of the order of import. They are a function of having invalid objects in the original export. Or of not having everything the imported objects depend on already extant in the database (about which, after all, the poor import cannot do anything!) Or, for example: I do imports all the time where I get lots of errors because the views, packages or whatever refer to objects in remote databases and I often forget to get the tnsnames.ora right before importing. Therefore, the objects get created with stacks of compilation errors. But that's not a function of the order of import, but of my bad memory and poor tns network configuration before starting the import at all.

> Is Oracle smart enough to import things in an order
> that will not produce errors? Usually, yes.

Always and forever, yes. Received on Wed Sep 26 2007 - 20:45:25 CDT