Commit a model in the new version of Connect - Connect_CDC - connect_cdc_mimix_share - 5.8

Connect CDC Installation Guide

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (MIMIX Share)
Version
5.8
Language
English
Product name
Connect CDC
Title
Connect CDC Installation Guide
Copyright
2023
First publish date
2003
ft:lastEdition
2023-09-11
ft:lastPublication
2023-09-11T16:55:56.594134

You must open the current model in the new version of Connect CDC Director and commit the model before it can be used.

  1. Ensure that you save a backup copy of the model (.rsm file).

    Note: Once you open and save a model with the new version of Connect CDC, it cannot be opened by a previous version of Connect CDC.
  2. Perform the following steps to open the model in the new version of Connect CDC Director:

  3. Import the data enhancement method .rsl file as required. See the “Upgrade Information” section in the Connect CDC Release Notes for more information.

  4. Change the listener port numbers to those that you specified when you installed the new Connect CDC software.

  5. Run a Test Connection for each host, to validate that the Listener version is connected.

  6. Upgrade the Metabase versions as required. See the “Upgrade Information” section in the Connect CDC Release Notes for the current Metabase version list by DBMS platform.

    The dialog shown below is an example of an upgrade of a metabase version. In Connect CDC Director, navigate to  Install Source Metabase or Install Target Only Metabase and the following dialog displays.

  7. Click Yes to upgrade the metabase version.

    The following dialog displays. It shows the steps that comprise the upgrade process.

    Note: The replication queues must be empty before you can continue with the upgrade process.To determine if you can continue with tables that are still enabled for capture, please review the Connect CDC Release Notes .
  8. Click Yes.

    The following dialog displays. It checks if the replication queue table is empty and if there are tables enabled for capture.

  9. Either Refresh All Tables in Cache in the model, or run a Catalog Synchronization Report for each server in the model.

  10. Incorporate any new features or functionality for the new release (optional).

  11. Validate the Model. Correct any errors, incompletes or warnings.

  12. Incrementally, commit the model.