IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI 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

Replication: Change Data Capture

Showing 188

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
almost 7 years ago in Replication: Change Data Capture 1 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 data...
about 7 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...
about 7 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 algorit...
about 7 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 7 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 7 years ago in Replication: Change Data Capture 1 Not under consideration

qjoretrievejournalentries - do not format journal entry timestamps according to the system timezone

In order to have a consistent view of journal entries between systems it is necessary to always normalize the journal entry timestamps to UTC from the system time with the timezone offset. This adjustment must be done for every journal entry read ...
over 2 years ago in Replication: Change Data Capture 0 Not under consideration

Add support for newly added functionality in Oracle 12.2: collations for columns

Case-Insensitive DatabaseOracle Database supports case-insensitive collations. By applying such collations to SQL operations, an application can perform string comparisons and matching in a case-insensitive way, independent of the language of the ...
over 6 years ago in Replication: Change Data Capture 1 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.