Replication: Q-Replication & Availability

Showing 80 of 15640

Implement more granularity processing on "CORRELID" to force more parallelism at Q Apply

We have an application with a high criticality and high workload running Q Replication in a bidirectional mode.This application uses CICS transactions, TSO Batch, Java Batch, local zWAS and distributed transactions as well.And because batch jobs c...

7 months ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Under review

22 VOTE

Ability to create ASNMON Oracle Control Tables via GUI without Federated Server

We have QREP Data Replication established between DB2 Z/OS and Oracle on Linux. We are using Oracle Native Apply on the target DBMS. As per discussions and conclusions in the referenced PMR, 85301,442,000, we have 2 issues:1) We can not directly c...

almost 7 years ago in Replication: Q-Replication & Availability / Q Replication for Z 2 Not under consideration

21 VOTE

Provide Replication Center and Replication Dashboard functionality within DSM

We would like to see the Replication Center tool functionality for IIDR Queue Replication added under the Data Server Manager(DSM) Umbrella. Today we are using Replication Center to administer and monitor our IIDR Queue Replication environment. Th...

almost 7 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release

9 VOTE

Add an ability to start a q subscription via MODIFY on the Capture started task

Currently Q Capture subscriptions can be interacted with either via MODIFY command invoked on a Q Capture started task, or SQL insert statements executed on table IBMQREP_SIGNAL. For many customers, executing a MODIFY command to perform an action ...

over 3 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Future consideration

20 VOTE

ALTER table DATA CAPTURE NONE not detected by IIDR QREP or CDC

If 'ALTER table DATA CAPTURE NONE' is executed against a table that is actively replicating, any changes made to the source data will not be captured or replicated until â€˜ALTER table DATA CAPTURE CHANGES' is executed. This would cause the target...

over 7 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release

3 VOTE

Feed Q Replication with your own LOAD keywords for automatic load

Recently we had opened a case TS013850174, which could not be addressed correctly b/c it requires an enhancement. Problem was as follows. Due to an error in our change management process, target table had a unique index, which was not present at t...

over 1 year ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

13 VOTE

Display of replication throughput per subscription

Today Q Apply stores detailed performance statistics on queue level. This idea raises the request to store certain Q Apply throuput statistics (like rows_processed) on subscription level. Background: Today it is very difficult / sometime impossibl...

over 5 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

6 VOTE

Request for supporting MQ automatic client reconnect

As we know, IBM MQ supports multi-instance configuration and automatic client reconnect since version 7.0.1. Recently we found the latest Q-Relication (11.4.0) even not support such a basic function( automatic client reconnect with multi-instance ...

almost 3 years ago in Replication: Q-Replication & Availability / Replication for Availability (LUW, Db2 Warehouse) 1 Future consideration

1 VOTE

In SQL replication, do not re-execute signals that have already been executed.

In SQL replication, as in Q Capture, add a reprocess_signals to the parameters of the capture and set the default to N. Do not re-execute a signal that has already been executed if the minimum LSN is less than the last signal LSN at the start of t...

6 months ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Submitted

3 VOTE

Q-Capture (on LUW) supports to use a dedicated MQ publish thread to perform all IBM MQ operations...

Currently, there is "parallel_mqthread" && "mqthread_bufsz" parameters, but it only used on z/OS. Cx hopes these features can support on LUW as well, which can specify whether the Q Capture program should use a separate thread to publish m...

over 1 year ago in Replication: Q-Replication & Availability / Replication for Availability (LUW, Db2 Warehouse) 0 Not under consideration

Please enter your email address

FILTER BY CATEGORY