Full vs. incremental model update - 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

Model Update may be one of these modes:

  • Full, updating all tables

During a full Model Update, the kernel disables and re-enables capture on all tables, typically the longest step in the entire Model Update process.

  • Incremental, updating only those tables that meet both the following conditions:

  • The tables are listed in the delta XML files.

  • The tables had capture enabled prior to Model Update.

For these tables, the kernel disables capture on all tables that are currently enabled for capture, loads the new model, and then re-enables capture on these tables using the new model.  

By default, Model Update automatically tries to do an incremental update. Model Update reverts to a full update under the following conditions:

  • Delta files are missing because:

  • The user specifies a full commit.

  • The user deletes one or more delta XML files.

  • The model location is changed from LOCAL to HTTP server or vice versa. In this case, some delta XML files are in one location while others are in another, and the kernel cannot find them all.

  • A server is dropped from the model.

  • A mapping or distribution changes, which affects all requests in a model.

Model Update converts to a full update, disabling capture on all the tables that had capture enabled before on only this specific server without affecting the other servers.

Note: If either of the above conditions is present, a full Model Update takes place. Check the kernel log for a message that indicates which Model Update mode is in use. This log is typically in: C:\PreciselyConnect\ConnectCDC58\kernel\<model name>_<host name>.log