How Configuration Information Is Propagated
Once you have completed the configuration tasks for the replicated database, you can move the configuration information to your target databases (Full Peer and Protected Read-only databases). The propagation procedure ensures that the replication scheme is defined identically in each database of the scheme.
You can propagate configurations by choosing the Propagate command from the Operations menu. For more information, see the online help topic Propagating Configuration Information.
Note: If you make any changes to the configuration once you have Ingres Replicator set up and running, you must copy the changes to the target databases. In general, you must not change the collision or error mode for a CDDS on just one of the databases that participate in a CDDS.
The propagating configuration procedure completes the following tasks on the databases it is run against:
• Copies the configuration data to the target Replicator catalogs
• Makes local context changes to the target data
• Creates support objects; if support objects already exist in the target database, these older objects are first destroyed
The propagating configuration procedure does not perform any of the following tasks on remote databases:
• Create lookup tables
You must create or copy lookup tables in each database. The propagating configuration procedure copies lookup table assignments. For more information, see
Lookup Tables on page 1.
• Activate the remote databases
You must activate each database by choosing the Activate Replication command from the Operations menu (alternatively, use the Table Activated option in the CDDS Definition dialog) in order for Ingres Replicator to run. (See the online help topics CDDS Definition dialog and Activating Replication for details).
• Define error mail destinations
If you want to create individual error mail destination lists, you must define error mail destinations on every installation by expanding the Replication branch and selecting the Mail Alert Users branch. For more information, see the online help topic Defining Error Mail Destinations.
Last modified date: 01/30/2023