Model update does not upgrade the model - Connect_CDC - connect_cdc_mimix_share - Latest

Connect CDC Advanced User Guide

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (MIMIX Share)
Version
Latest
Language
English
Product name
Connect CDC
Title
Connect CDC Advanced User Guide
Copyright
2024
First publish date
2003
Last edition
2024-07-19
Last publish date
2024-07-19T23:30:25.334335

In some situations, Model Update does not upgrade the model:

  • If a new host is added to the model. When the new host is added, the model update process is started only on the hosts present in the existing version of the model. Connect CDC will recognize the added hosts only after the model is updated on the new host and the model is reloaded in MonCon.

  • When you change or add a new user procedure, you cannot call one user procedure from another. This will cause a model upgrade to fail. A user procedure can only be called by a result expression defined in a target mapping or from a gate condition.

  • If you change the port number on the host (the port number that Connect CDC Listener uses), Model Update does not upgrade the model because Connect CDC MonCon tries to connect to the Connect CDC Listener on the previously defined port.

  • If you change the replication user password, Model Update can not upgrade the model. This is because the model update process will first attempt to access the model with the old password.

  • If a host goes down and you change the host name (for example, dropping the host and adding a new one), Model Update does not upgrade the model because it tries to contact the old host.

  • If you use scheduled replication and have data in the queues, model update fails under these conditions:

  • If you use full commit when the scheduled request is not active at the time of Model Update.

When the request is not running, the queues do not drain, and Model Update quits without any modifications to the model version.

  • If you use incremental commit, only when there are changes to the scheduled request.

When the request is not running, the queues do not drain, and Model Update quits without any modifications to the model version.

  • If the queues cannot be drained within a certain timeout.

If a scheduled request is active at the time of Model Update, then Model Updates waits for a certain amount of time to drain the queues because the request is running. When the queues fail to drain, Model Update quits without any modifications to the model version.