Replication Guide and Reference

What's new

This section introduces the major features of DB2 DataPropagator for the two most recent versions, 6 and 7. For Version 7 (V7), see What's new for Version 7; for Version 6 (V6), see What's new for Version 6.


Compatibility

All releases of DB2 DataPropagator Relational Version 1 (DPropR V1) are not compatible with this product. If you currently use DPropR V1, see Planning for migration for instructions on upgrading.


What's new for Version 7

This section introduces the major features of DB2 DataPropagator Version 7 (V7), which are described in more detail in this book.

DATALINK replication

DB2 Universal Database provides a DATALINK data type that allows the database to control access, integrity, and recovery for external files. DB2 DataPropagator V7 replicates DATALINK columns, but does not replicate the external files to which the DATALINK columns point. To replicate the files, the Apply program uses a user exit routine. See Replicating DATALINK values for more information about DATALINK support.

Replication for AS/400

DB2 Universal Database for AS/400 now supports:

The following features were added to improve the performance of your AS/400 replication environment:

Replication for UNIX, Windows, and OS/2

DB2 DataPropagator Version 7 is available for Linux and NUMA-Q operating systems.

On Windows 32-bit operating systems, you can start the Capture and Apply programs on demand using the ASNSAT command. For information about this command, see Replicating on demand (Windows 32-bit operating systems only).

You can start both the Capture and Apply programs from within an application by using the new asnCapture and asnApply application programming interfaces. For information about these interfaces, see Appendix A, Starting the Capture and Apply programs from within an application.


What's new for Version 6

This section introduces the major features of DB2 DataPropagator Version 6 (V6), most of which are described in more detail in this book.

DB2 Satellite Edition

DB2 Universal Database Satellite Edition (DB2 Satellite Edition) brings the power of DB2 Universal Database to environments containing occasionally connected clients. It is supported on Windows 32-bit operating systems.

With DB2 Satellite Edition, you can replicate data between DB2 servers and some non-IBM source servers (Oracle, Sybase, Informix, Microsoft), and you gain the following benefits:

Two new options let you run the Capture and Apply programs in batch mode:

Capture program AUTOSTOP option
You can run the Capture program in batch mode by using the new AUTOSTOP invocation parameter. The Capture program will run until it captures all of the changes from the log and then it terminates. 5

Apply program COPYONCE option
You can run the Apply program in batch mode by using the new COPYONCE invocation parameter. The Apply program will try to run all eligible subscription sets one time and then it will terminate. 6

Database currency

DB2 replication now provides:

LOB support
You can use DB2 DataPropagator to replicate columns with large-object (LOB) data. The Capture program flags information about changed LOB data, but does not copy the LOB data to staging tables. The Apply program copies changed LOB data directly from the source table to the target table. You can replicate LOB data between DB2 for OS/390 servers or between DB2 Universal Database servers for UNIX, Windows, and OS/2 operating systems. If you have DB2 Connect Version 6, you can also copy LOB data between DB2 for OS/390 and DB2 Universal Database servers for UNIX, Windows, and OS/2 operating systems.

ROWID support
DB2 for OS/390 V6 allows you to generate a unique identifier for each row in a table and store that identifier in a ROWID column. Using the ROWID, you can access a particular row without needing to access an index or scan the table space. Usually a ROWID identifies a row in the table that has the ROWID defined. However, by copying ROWID values from the source table to set the target rows with the same ROWID values, you can use the same ROWID value to identify both the source and target row.

Version-independent capture
The Capture program can read the log for DB2 for MVS/ESA V4, DB2 for OS/390 V5, or DB2 for OS/390 V6. Therefore you can run different versions of DB2 in a data-sharing environment, for example during version-to-version migration, and have one Capture program continue to capture transaction-consistent data.

ODBC support
This feature was added in DB2 for OS/390 V5 and updated in V6 to support a new catalog table (SQLProcedureColumns).

Unicode support
DB2 DataPropagator for UNIX, Windows, and OS/2 operating systems supports unicode.

Port to Linux
DB2 DataPropagator V6 runs on the Linux operating system.

Performance features

The following features were added to improve the performance of your replication environment:

Option to capture only columns that are available for replication
You can start the Capture program using the CHGONLY parameter if you want to capture changes only for those columns that you marked available for replication. By default, the Capture program captures changes that are made to the source table data for all columns.

Capture program sleeptime option
You can use the SLEEP=N invocation parameter to indicate how long you want the Capture program to sleep before it reads the log again, after it reaches the end of the log. To save on CPU, the Capture program will sleep if no data is returned on the log. This parameter is supported for DB2 for MVS 4.1 and later with data sharing. If you use the SLEEP=N parameter with data sharing, and only a small amount of data is returned, then the Capture will sleep for N seconds.

Continuous block fetch by the Apply program
The Apply program uses DB2 continuous block fetch to improve data-transfer rates and overall performance for replicating data from DB2 for OS/390 to other operating systems.

Automated use of RUNSTATS utility
For DB2 DataPropagator on UNIX, Windows, and OS/2 operating systems, the RUNSTATS utility is run automatically after the Apply program completes a full-refresh copy to the target tables. This utility collects new statistics on the target tables and their indexes.

Integration with DB2

The replication components are integrated with DB2 Universal Database more closely than before.

DB2 DataPropagator for OS/390 feature
When you order DB2 for OS/390 V6, you also receive a free trial version of DB2 DataPropagator for OS/390. This trial version has all the features and functions of the standard product. You can use the trial version for 90 days without paying a licensing charge. After the trial period ends, you must order a license for the DB2 DataPropagator priced feature to continue using the product.

Integrated installation for OS/390
You can install DB2 DataPropagator for OS/390 V6 using the DB2 Installer interface. The DB2 Installer is a workstation-based tool that provides an easy-to-read map for the entire installation process. The status of a task is denoted by the changed icons on the windows. Help text is provided for each field, and "Guide Me" help text is provided for each window.

Control Center
A Java version of the DB2 Control Center is available that you can use to perform administration tasks from a Web browser. It includes improved support for administering replication environments for DB2 for OS/390. For more information about this new interface, see the DB2 Universal Database documentation.

DataJoiner Replication Administration tool
The DataJoiner Replication Administration (DJRA) tool comes with DB2 Universal Database and it runs on Windows 95, Windows 98, and Windows NT operating systems. With DJRA, you can perform administration tasks for replication configurations involving DB2 databases, non-IBM databases, or both. Using DJRA, you can easily promote (copy) your replication criteria from one environment to another. You can also start a replication monitor to help you monitor replication activity and produce periodic reports about that activity. If your files are stored on the AS/400 platform, you can use DJRA to automatically generate relative record numbers (RRN) for replication sources so that you can replicate data without user-defined unique keys. The details about these and other benefits of DJRA are documented in this book.

Footnotes:

5
The Capture program AUTOSTOP option is not available on the Capture program for AS/400.

6
The Apply program COPYONCE option is not available on the Apply program for AS/400.


[ Top of Page | Previous Page | Next Page ]