Database Software

Hi,
we are migrating/upgrading to a new/better server for our prod environment.

impdp is generating a lot of errors for 1 user, ( 5 other instances have gone through fine) --
does not seem to be creating the primary key constraints & that is why foreign keys are failing.

Below is an excerpt from the impdp log:
******************************************
ALTER TABLE "PHYS"."MD_INDEX_DETAILS"
ADD CONSTRAINT "MD_INDEX_DETAILS_MD_COLUM_FK1" FOREIGN KEY ("COLUMN_ID_FK")
REFERENCES "PHYS"."MD_COLUMNS" ("ID") ON DELETE CASCADE ENABLE

ORA-39083: Object type REF_CONSTRAINT failed to create with error:
ORA-02270: no matching unique or primary key for this column-list

******************************************

We are using .par file for export parameters:
DIRECTORY=expdir
DUMPFILE = instance1.dmp
LOGFILE = instance.log
ENCRYPTION=ALL
COMPRESSION=ALL
SCHEMAS=USER1,USER2,PHYS,USER3,USER4


Below is my import command:

impdp system/******* schemas=PHYS DIRECTORY=DATA_PUMP_DIR dumpfile= Apr20.dmp logfile=importPhys.log


I checked if the # of constraints are same in current prod env & the new env -- there is a difference of ~70 of which 30+ are Primary keys.

Any input/feedback is appreciated.

Thanks,
NK