Enabling use of foreign keys (referential integrity)

Universal Cache User Guide : Setting up caching : Universal-Cache-specific settings and tasks for IBM InfoSphere CDC : Enabling use of foreign keys (referential integrity)

If you have set up subscriptions with Management Console and the subscriptions include tables with foreign keys, you need to set the IBM InfoSphere CDC for solidDB^® system parameter refresh_with_referential_integrity to true. Additionally, if your backend data server is Oracle or DB2 for Linux, UNIX, and Windows, you need to disable the fast loader.

About this task:

You can set system parameters

▪with the dmset -I <INSTANCE_NAME> <parameter_name>=<parameter_value> command, or

▪using the Management Console:

In the Configuration perspective of the Management Console, select the datastore.

Right-click on the datastore and select Properties > System Parameters.

If you make changes to a system parameter during active replication, you must stop and restart replication for the changes to take effect.

Procedure

1 Set the IBM InfoSphere CDC for solidDB^® system parameter refresh_with_referential_integrity to true.

For example:

dmset -I soldidB_1 refresh_with_referential_integrity=true

2 If your backend data server is DB2 for Linux, UNIX, and Windows, set the refresh_allow_fast_loader system parameter in IBM InfoSphere CDC for DB2 to false.

For example:

dmset -I DB2_1 refresh_allow_fast_loader=false

3 If your backend data server is Oracle, set the refresh_allow_fast_loader and ts_fast_loader_disable_constraint system parameters in IBM InfoSphere CDC for Oracle to false.

For example:

dmset -I Oracle_1 refresh_allow_fast_loader=false

dmset -I Oracle_1 ts_fast_loader_disable_constraint=false