The queues must be drained for model update because one or more tables may be disabled for capture during the model update process. When a table is disabled for capture, the corresponding cdc mirror table is dropped and any pending data contained in the mirror table will be lost.
The model update process involves the following activities:
-
Determines what tables have changed
-
Places a read-only table lock on the changed tables
-
Drains queues for all changed tables
-
Disables capture
-
Instantiates a new model and metabase
-
Re-enables capture
-
Removes table locks
Note: You can continue inserting, updating, or deleting rows during Model Update for DB2/400, MS SQL Server, Postgres, and UDB. In other databases, you may experience data loss if you continue.