Creating Q subscriptions
Q subscriptions specify your sources and targets, the queues that are used to transport data, and other replication options. Q subscriptions differ depending on whether you are using unidirectional replication, replication to federated targets and stored procedure targets, replication from Oracle sources, and multidirectional replication.
- Grouping replication queue maps and Q subscriptions
Before you define Q subscriptions and replication queue maps, you should first plan how you want to group Q subscriptions and replication queue maps. - Creating replication queue maps
When you create Q subscriptions, you specify which IBM® MQ queues to send the data over by associating each Q subscription with a replication queue map. You can create a replication queue map before you begin creating Q subscriptions or as one of the steps of creating Q subscriptions. - Using parallel send queues
You can specify that the Q Capture program use multiple send queues, each with its own transmission queue, to send transactions to a single receive queue on the Q Apply server or to publish XML or delimited messages. This configuration is referred to as using parallel send queues. - Setting up unidirectional Q Replication
With unidirectional replication, you can replicate data in one direction from a source table to a target table or manipulate the data at the target using stored procedures. The target for the Q subscription can be either a DB2® server or a non-DB2 server. - Replicating Data Definition Language (DDL) operations
You can speed up and simplify the configuration and maintenance of DB2 continuous availability and disaster recovery solutions by taking advantage of the Data Definition Language (DDL) replication features in InfoSphere® Data Replication Version 10.1.3 and later. - Synchronizing Q Apply across multiple receive queues for disaster recovery
When you use multiple receive queues to replicate a workload, you can synchronize the apply process across receive queues to ensure that a time-consistent point can be restored, even if data is lost for one of the queues, before switching the workload to a standby site for unplanned outages. - Q Replication to federated targets
Q Replication to targets such as Oracle or Microsoft SQL Server works much like a scenario where both source and target are DB2 servers. - Q Replication to native Oracle targets
You can use Q Replication to replicate data to an Oracle target without the need for federation. The program that applies data to the native Oracle target is called Q Apply for Oracle. - Manipulating data by using stored procedures as a target
When you create a Q subscription for unidirectional replication, you can specify that the changes be replicated from the source table to a stored procedure instead of directly to a target table. You can use the stored procedure to manipulate data that is captured from the source before the data is applied to the target table. - Setting up multidirectional Q Replication
With Q Replication, you can replicate data back and forth between tables on two or more servers while applications update the identical copies of a table at all servers while keeping all copies of the table synchronized. This type of replication is known as multidirectional replication. - Loading target tables for Q Replication
When you create a Q subscription, you can choose among several options for loading target tables with data from the source. - Replicating load operations at the source table
You can specify that load operations at the source table that use the DB2 LOAD utility are replicated to the target table. - Search conditions and log record variables to filter rows
To filter which rows are replicated or published, you can use a search condition that includes an SQL WHERE clause, a predicate with variables that are found in the log record, or combine both for powerful filtering capability. - Using expressions in Q Replication
You can use expressions to change data while it is being replicated from the source to the target. Q Replication supports both SQL expressions and XML expressions. - Q Replication and Event Publishing for multiple database partitions (DPF)
Q Replication and Event Publishing support capture of data from DB2 source tables that are spread across multiple database partitions, also known as DPF (Database Partitioning Feature). - Replication of DB2 partitioned tables: Version 9.7 Fix Pack 1 or earlier (Linux, UNIX, Windows)
Q Replication supports DB2 tables that are partitioned by range (using the PARTITION BY clause of the CREATE TABLE statement). These tables are sometimes known as range-partitioned tables. - Replication of DB2 partitioned tables: Version 9.7 Fix Pack 2 and later (Linux, UNIX, Windows)
Q Replication supports DB2 tables that are partitioned by range (using the PARTITION BY clause of the CREATE TABLE statement). These tables are sometimes known as range-partitioned tables. - CCD tables in Q Replication
Consistent-change-data (CCD) tables provide committed transactional data that can be read and used by other applications, for example InfoSphere DataStage® or the Apply program for SQL replication. - Creating point-in-time tables for Q Replication
You can create point-in-time target tables or nicknames that contain a copy of the source data and an additional column that holds the timestamp of approximately when the source row was changed. - Replicating temporal tables
You can replicate changes to temporal tables and their associated history tables in both unidirectional and bidirectional configurations.