Replication Extract does not support historical definitions of DB2 tables. It uses the current definition of a table as recorded in the DB2 catalog when extracted log data is formatted. Therefore, use caution when you alter the definition of a DB2 table to be replicated.
If the alteration requires dropping and re-creating the table (for example, if you are moving a table from a simple tablespace to a partitioned tablespace), you must ensure that all data changes are replicated and passed to the Replication Server before dropping and re-creating the table. This ensures that Replication Extract does not need to reread the portion of the log that contains data changes made to the original version of the table.
Before you drop the table, turn off replication for the primary table. This prevents Replication Extract from extracting any more changes made to a table having this DBID.OBID combination. (DBID and OBID are the database ID and the object ID, respectively, that uniquely define the database to DB2.)
After you re-create the table, start replication by using the Replication Agent interface dialog panels to enable replication for the primary table.
See “Working with Replication Agent system tables” for more information.
