RC/Migrator for DB2 for Z/OS : Which option in a Migration Strategy do I use to include the Referential Integrity?

Products

• RC Compare for DB2 for z/OS
• RC/Migrator for DB2 for z/OS

Issue/Introduction

When tables are migrated, referential integrity can be migrated as well. Instead of automatically including all referential integrity definitions with tables, you can specify an option which will 1) Not include referential integrity definitions, 2) Include only local referential integrity for the tables defined in the migration structure or 3) Include all referential integrity including foreign key definitions and all tables in the referential structure.

 

 

Environment

Release: R20
Component: RCM

Resolution

On the Strategy Analysis Options screen, there is a RI (Referential Integrity) option that can be used to indicate whether to include referential integrity definitions.

The values for this option are N, L, or G.

N - Exclude referential integrity definitions. This is the default. Table definitions will still include unique constraint definitions. You do not have to include a referential integrity option
to include unique constraint definitions.

L - Include only local referential integrity. Local referential integrity includes foreign key definitions for any tables involved in the migration. It does not automatically include tables in the referential structure but the specified migration structure.

G - Include all (global) referential integrity. Use this option to include foreign key definitions and all tables in the referential structure.

Additional Information

Control Options