Db2 Datapropagator - New With 7.1 - IBM i series Handbook

IBM Licensed Programs: Database Accessories
– Staging tables : Can be used as a source for further copies without recapturing
changes, supporting a consistent data environment, and providing flexibility in data
distribution across the network
• Updatable copies
– Replica tables : Updates to a replica table are automatically applied to the original
source table of the replica, provided no conflicts are detected.
The Apply component running at the replica site, detects update conflicts after they
occur during the subscription cycle. When transactions are rejected, the Apply
compensates the transactions at the replica site. During this process, the Apply
inserts rejection codes for every rejected transaction in the control table. Conflict
detection is provided at three levels: no detection, standard detection, and enhanced
detection, specified while defining the replication source.
DB2 DataPropagator – New with 7.1
Replicating Large Objects
DB2 Universal Database supports large object (LOB) data types, which includes binary LOB
(BLOB), character LOB (CLOB), and double-byte character LOB (DBCLOB). This section
refers to all of these types as LOB data.
BIGINT Data Type
Big integer (BIGINT) data type allows replication of big eight-byte integer data types. This
permits the storage and replication of integers larger than 2.1 GB for specialized application
needs.
Replicating DATALINK Values
Accessing large files (such as multimedia data) over a remote network can be inefficient and
costly. If these files do not change, or change infrequently, faster access to the files and
reduced network traffic can be provided by replicating these files to remote sites.
DB2 Universal Database provides a DATALINK data type to allow the database to control
access, integrity, and recovery for this type of files. DB2 Universal Database supports
DATALINK values on all platforms except OS/390.
Performance Improvements
• The STRDPRCAP command has a new parameter, GENCDROW to specify that only
changed columns are replicated.
• For replication scenarios where the target tables reside on the same system as the
Change Data tables, the Version 7.1 Apply/400 code no longer resorts to the use of
528
iSeries Handbook