IBM Data and AI Ideas Portal for Customers


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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


ADD A NEW IDEA

FILTER BY CATEGORY

Q Replication for Z

Showing 60

Automate restart of IIDR tasks when RRS terminates

We had issues with RRS recently which were solved via a maintenance cycle. During those issues, our IIDR Capture and Apply tasks failed and required manual restart. We have the option TERM=N enabled yet the Capture/Apply tasks were not restarted w...
about 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Is a defect

Replicating clone tables from a source data store and tables which have a clone table defined

As per IDR 11.4, support is not provided either for replicating source clone tables or for replicating tables which have a clone table defined. We need to be able to replicate source tables involved in clone relationships.
about 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Delivered

Leverage "FOR EACH ROW ON UPDATE" functionality to maintain Peer to Peer Version Columns, instead of triggers

Current implementation of Peer to Peer Version Columns (IBMQREPVERTIME and IBMQREPVERNODE) depend on BEFORE INSERT and BEFORE UPDATE triggers to maintain transaction information for conflict_action of V (last transaction wins). The use of these tr...
over 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Future consideration

Heartbeat messages are not available in EP if using delimited format

1. As far as including schema changes in EP messages – at this time they don't have a pressing need so I would say you don't have to worry about that. However, they do want/need to see heartbeat messages. The manual says heartbeat messages are n...
over 4 years ago in 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.c...
over 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Delivered

QREP Commit by Row Count

For configuration of COMMIT_COUNT, the original suggestion is to have different value for online and batch procession. Since it is not easy to define the period for online and batch (there are online and batch processes during day time), it would ...
over 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Delivered

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 targe...
over 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release

QREP DDL replication, add UNICODE factor for column length

When replicating from non-unicode to unicode, the legth of char/varchar target columns needs to be extended. Example: create all CHAR/VARCHAR columns at the target with source_length*2 and implemented an additional life belt with OKSQLSTATES = 220...
over 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release

zIIP Eligible Q-APPLY

QREP is increasingly become to a key infrastructure component for customers z Systems platform resilience. However, the QREP did need quite a lot MIPS to support. This requirement is for QREP to change some part to be zIIP eligible, specifically f...
over 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

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 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration