IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com



ADD A NEW IDEA

Search results: Data Replication: Q-Replication & Availability

Showing 46 of 77

Q Replication to allow add/remove member in P2P replication mesh

As we are migrating our DB workload to the cloud we need to have the ability to add/remove members to redefine our P2P multi-master QReplication topology to accommodate for workload growth and making data available closer to customers (application...
about 7 years ago in Data Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

Qrep support Removing a column from the replication key

Currently, adding a column to the replication key is supported today by Q Replication, even for Oracle targets. But, Removing a column from the replication key is not supported today. From customer operation, they think should be allowed to change...
almost 8 years ago in Data Replication: Q-Replication & Availability / Q Replication for Z 0 Delivered

Q Replication to support MRI on DB2 for LUW

Currently MRI (Multiple Row Insert) function is said to be supported on DB2 for LUW after 10.5.0.7, but actually NOT. Without this function, QREP may not meet the performance requirements of some applications , such as PBoC TIPS2. https://www.ibm....
over 8 years ago in Data Replication: Q-Replication & Availability / Q Replication for Z 0 Delivered

For ASNMON update ASNMAIL EXIT with certain industry standard capabilities

Due to new internal infrastructure requirements, and the loss of the Q-REP dashboard, we need to be able to send email alerts via ASNMON. In order to do this, the ASNMAIL Exit must be enhanced to accommodate certain features which are considered s...
almost 5 years ago in Data Replication: Q-Replication & Availability / Q Replication for Z 1 Delivered

Enhancement to add bidirectional Q subscription in one Db2 Server

We have the need to replicate data between two applications which are hosted in the same Db2. The challange was to exchange the data asynchron. The applications do not want to be disturbed if there is a downtime or problem at the other application...
over 5 years ago in Data Replication: Q-Replication & Availability 0 Not under consideration

Document process for publication as opposed to subscription migration

The manuals document the process to migrate ALL *subscriptions* to a new Q capture task. Our scenario involved migrating single publications one-by-one (by sendq) to an existing actively used Q capture task. Please update the replication guide for...
over 6 years ago in Data Replication: Q-Replication & Availability / Q Replication for Z 0 Functionality already exists

Replication condiction

System : InfoSphere Replication Server(Q replication) is real-time database replication solution for better control of DB2 replication. Description : Customer want to check or before image and after image condition each row processing to control s...
over 7 years ago in Data Replication: Q-Replication & Availability / Q Replication for Z 1 Planned for future release

To enable capture log buffer flush periodically (Infosphere Replication Server)

Sometimes, there are too small data to replicate but busy logging which are not interested in. Q Capture log read should be quick enough even busy logging. Customer request the periodical flush of log buffer(logrdbufsz) with optional new parameter.
almost 8 years ago in Data Replication: Q-Replication & Availability / Q Replication for Z 1 Not under consideration

QRep Delete/Insert Record in CCD table for Updates of Replication Key

ICBC use CCD table to update its application DB. There is only one record of Update in CCD table for updates of replication key in Qrep. ICBC cannot remove the origin record with the information in the updated record. Data consistency cannot be gu...
about 8 years ago in Data Replication: Q-Replication & Availability / Q Replication for Z 0 Delivered

Enhance QREP peer-to-peer configuration

Currently most of the customer implementation of QREP is using 'unidirectional replication configuration' even the customer has need of bi-directional replication requirements. Normally applications occur on the source site only, the target tables...
over 8 years ago in Data Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.