Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

why are named constraints missing after data only refresh?

FBP_FLUORDec 30 2020

i have refreshed our dev database (PEMS) from production using a script that has always worked (12c and earlier) in our new 19c database (first time i have run it on 19c). the procedure is to disable constraints and import across the network link, then re-enable the constraints. However i have found that after the refresh, the only constraints that still exist on the target dev db are the type "C" or check constraints that have names that start with SYS_. I can use Toad to recreate the constraints of non type C in dev but i am wondering:
why are the constraints missing after import?
Is there a way to avoid this circumstance when refreshing data only? Here is my data only refresh shell script:

sqlplus -L / as sysdba @disable_pems_const.sql
sqlplus -L / as sysdba @disable_pems_triggers.sql
impdp / parfile=refresh_data_pems.par
sqlplus -L / as sysdba @enable_pems_const.sql
sqlplus -L / as sysdba @enable_pems_triggers.sql
sqlplus -L / as sysdba @drop_pems_seq.sql
impdp / parfile=dp_pems_sequences.par

Comments
Post Details