Hi importing a DB into a new USER space and get
. . importing table "ACTION_HARVEST_DETAIL" 10039 rows imported
IMP-00015: following statement failed because the object already exists:
"ALTER TABLE "ACTION_HARVEST_DETAIL" ADD CONSTRAINT "PK_ACTION_HARVEST_DETA"
"IL" PRIMARY KEY ("ACTION_HARVEST_DETAIL_ID") USING INDEX PCTFREE 10 INITRAN"
"S 2 MAXTRANS 255 STORAGE(INITIAL 393216 NEXT 131072 MINEXTENTS 1 MAXEXTENTS"
" 4096 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABL"
"ESPACE "USERS" ENABLE "
About to enable constraints...
IMP-00017: following statement failed with ORACLE error 2430:
"ALTER TABLE "ACTION_HARVEST_DETAIL" ENABLE CONSTRAINT "PK_ACTION_HARVEST_DETAIL""
When 2430 is
ORA-02430 cannot enable constraint (string) - no such constraint
Cause: The named constraint does not exist for this table.
Action: Check that a constraint exists before trying to enable it.
Why? is it there or not there?
(this happens for about 45% of the constraints)
You'll always learn something if you take your time to ask.
I think that since the table existed as listed in the first error the constraint was not imported, therfore it can not be enabled.
Maybe this would work, i'm not sure.
In situations where multiple refreshes from a single export file are done with IGNORE=Y, certain objects can be created multiple times (although they will have unique system-defined names). You can prevent this for certain objects (for example, constraints) by doing an import with the value of the parameter CONSTRAINTS set to N. If you do a full import with the CONSTRAINTS parameter set to N, no constraints for any tables are imported.
I remember when this place was cool.
Click Here to Expand Forum to Full Width