Consistent copying without impacting DB2 availability
When data must come from tables that require 24×7 enterprise availability there is an issue for IT. Users need to query and update the tables without interruption. Stopping the source objects is not a viable option.

Without stopping the source objects, it can be very difficult to copy tables while preserving consistency between tables and indexes and between different tables. BCV5 minimizes the copy time, but it cannot avoid the impact of changes made to objects while they are being copied. The good news is that DB2 stores information about all these table changes in its log. Our latest development BCV6
is an automated solution that uses the information in the log to bring the copied tablespace to a consistent state.
BCV6 enhances BCV5’s rich feature set with the ability to make consistent copies of objects without stopping them or putting them in read-only state. Using information from the source DB2 subsystem log, all changes made to the source tablespace during the copy process are rolled back in the target environment. When the copying finishes, the target tablespace is identical to the source tablespace found at the beginning of the copy process. The quiesce point is a preferred consistency marker in common use.
more»