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

Replication: Change Data Capture

Showing 59

Enable a single CDC instance to connect to multiple Netezza databases

Currently a single CDC instance can connect only to one Netezza database. We would like to have a single CDC instance to connect to multiple Netezza databases on the same appliance
over 4 years ago in Replication: Change Data Capture 1 Not under consideration

Support Differential Refresh on DB2 for i (iSeries/ IBMi)

Currently there is no support to perform differential refresh when source/target databases are DB2 for i (iSeries / IBM i)This requires target tables to be cleared to perform a refresh in case there were any issues in replication.We have productio...
over 4 years ago in Replication: Change Data Capture 0 Not under consideration

CDC should show the hostname which the user is already connect to datastore from.

In CDC management console, when "Mutiuser Configuration" is enabled.if the user A already connect to datastore from management console in some one windows env. when customer want to connect to datastore by user A from another windows env, the dat...
over 4 years ago in Replication: Change Data Capture 1 Not under consideration

Table level row count in MC on the fly in IIDR

CDC Performance Monitor in MC have features about subscriptions level row count increase during mirroring. Our requirement is to have table level counts as well in MC on the fly while its replicating from source to target. Currently we can see num...
over 4 years ago in Replication: Change Data Capture 1 Not under consideration

Add a Feature to Replicate Microseconds Portion of Timestamp

We use IIDR CDC on z/OS for replication using DB2 data on z/OS as the source and a flat file on a non-z/OS platform as the target. We have encountered a situation where the microseconds portion of the timestamp value on a DB2 z/OS table is not re...
over 4 years ago in Replication: Change Data Capture 1 Not under consideration

Replicate the data into HDFS through Kafka

The current Replication to HDFS through HDFSWeb. It is slow and lack of the ingestion standard. Kafka is the new way, which can standardize the ingestion to HDFS. The following are the reasons:a. can use Avro, which is the good compression algori...
over 4 years ago in Replication: Change Data Capture 1 Not under consideration

Change to memory management algorithm

We use Change Data Capture in several project in our company.We identified a serious problem regarding memory management algorithm. Once a week we have a batch of jobs performing many modifications to replicated tables. This workload is characteri...
over 4 years ago in Replication: Change Data Capture 1 Not under consideration

View contents of iSeries source journal position table via a command

The CDC metadata on the source on the iSeries includes information on the journal receivers and sequence numbers being processed by CDC. Although not authoritatively up-to-date as the target is the master in this respect, this information is good ...
over 4 years ago in Replication: Change Data Capture 1 Not under consideration

Make table active on iSeries without data loss

When the user changes the status of a table to active with Mark Table Capture Point in GUI, mark capture point in chcclp or System i command SETMIRSTS (*ACTV), a marker is posted to the journal and all unreplicated transactions between the end poi...
over 4 years ago in Replication: Change Data Capture 1 Not under consideration