Q Replication and Event Publishing Q Replication and Event PublishingQ Replication and Event Publishing support capture of data from DB2® source tables that are spread across multiple database partitions.
When you create Q Capture control tables in a multiple partitioned database, all of the table spaces used by those control tables must be on the catalog partition. If you use an existing table space, the table space must be non-partitioned and on the catalog partition.
The Q Capture program keeps a list of database partitions within the restart message. Whenever the Q Capture program is started in warm mode, it reads the list of database partitions from the restart message. Q Capture compares the number of database partitions that are known to DB2 with the number of database partitions that are listed in the restart message. If the numbers do not match, the Q Capture program stops.
If you added one or more database partitions since the last time you ran the Q Capture program, you must tell the Q Capture program about the new partitions. You can do this by starting Q Capture with the add_partition parameter.
For example, the following command specifies that the Q Capture program on server SAMPLE should start reading the log file for newly added partitions:
asnqcap capture_server=sample capture_schema=asn1 add_partition=y