The following replication and publishing enhancements
are available in IBM® WebSphere® Replication Server
Version 9.5 Fix Pack 2 and IBM WebSphere Data
Event Publisher Version 9.5 Fix Pack 2.
- Unlimited number of partitions
- The 16-partition limit for multiple-partitioned databases is now
lifted in Q Replication, Event Publishing, and SQL Replication. All
replication and publishing functions now support capture of data from DB2® source
tables that are spread across multiple database partitions with no
limit on the number of partitions.
- New option for improving performance of bidirectional replication
- The Q Capture program can ignore specified transactions to improve
performance in a two-server bidirectional configuration. When there
are many bidirectional Q subscriptions, the signal inserts that are
used by default to avoid recapture of transactions can affect performance.
To avoid this situation, you can specify that the programs use the
IBMQREP_IGNTRAN table. This method tells the Q Capture program to
automatically ignore any changes that come from the Q Apply program.
This method can improve performance because Q Capture does not need
to build the Q Apply transactions in memory, and Q Apply does not
need to perform signal inserts.
- Replication of a subset of source table columns and rows in multidirectional
replication
- Q Replication now supports subsetting of columns and filtering
of rows in bidirectional and peer-to-peer replication. Until Fix Pack
2, all columns of the source table had to be part of a Q subscription
for multidirectional replication, and no search conditions were allowed
for row filtering. You can use the ASNCLP command-line program to
specify the columns that you want to replicate, and a WHERE clause
for row selection. The Replication Center also has been enhanced so
that you can view the source columns that have been chosen for multidirectional
replication, the mapping between source columns and target columns,
and any unmapped columns.
- Interoperability between the latest replication server version
and older DB2 releases
- You need not migrate or change existing DB2 databases
(down to Version 8.2) to use the latest replication server and its
features with them. You also can run replication server on an entirely
separate system from the systems that host source or target databases.
Both configurations require cataloging the databases and nodes at
the system that is running the replication server, and creating control
tables that match the replication server version.
- ASNCLP can generate SQL scripts even when validation checks result
in errors
- The ASNCLP command-line program now can continue generating SQL
scripts for defining or changing Q Replication or Event Publishing
objects even when validation checks result in errors. The ASNCLP can
generate SQL even when it encounters errors because of duplicate or
existing objects when it is processing CREATE commands.
- Improved encryption for password files used by Q and SQL Replication
- The asnpwd command can now create encrypted
password files for remote connections by using the Advanced Encryption
Standard (AES) method that DB2 uses. This new encryption method
meets stricter U.S. government standards for encryption under FIPS
140-2 and provides better password file support for 64-bit Windows operating systems.
- Easier and more flexible promotion of configurations with ASNCLP
- A new CONFIG SERVER option to the SET SERVER command for Q Replication
helps you specify the promotion target more easily. Also, individual
ASNCLP SESSION SET commands are now automatically created in the generated
script for each PROMOTE statement in the input script. A SET RUN LATER
statement also is automatically added to the generated script to let
you confirm or modify its contents before running it.