Title: Weid exp/imp problem
You
may need to use consistent=y on the export to ensure that the view for the
entire export run is from one snapshot in time. If your application is
busy changing data during the export, then as export moves through the list of
tables (alphabetically I think) th
Title: Weid exp/imp problem
Helmut:
This
could be due to the fact that constraints on those tables have not been defined
yet. Since tables are imported in
Alpha order, I would suggest performing a no-data import after this one is
complete.
Thank You
Stephen P. Karniotis
Tec
You can handle this by two ways. The first is running
the imp in two times. And the second imp with rows=n
and ignore=y.
On the other hand, you can create all the objects with
the constraints INITIALLY DEFERRED. With the
precaution that you can not undo the mode of the
constraint with an alter t
Title: Weid exp/imp problem
This
error is coming because at the time of adding foreign key constraint ,
referencing primary key is not available.
You
can avoid this error by creating a similar schema in the user in which you are
taking the import and then import data
with
parameter "ignore
[EMAIL PROTECTED] wrote:
>
> Hi
>
> You are most likely importing a table with foreign key prior to importing
> the primary key that it points to.
> you can do export with constraints N (I think) . Recreate the constraints
> after import.
> Or export your tables in the right order so the primar
Hi
You are most likely importing a table with foreign key prior to importing
the primary key that it points to.
you can do export with constraints N (I think) . Recreate the constraints
after import.
Or export your tables in the right order so the primary keys get imported
first (use a parfile
