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: Q-Replication & Availability

Showing 65

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

Q-Replication Apply program shall be able to recognize if a column-organized table contains already a dictionary

Hello, the current implementation of the Q-Replication apply program for an automatic LOAD operation on column-organized target tables does not recognize if a dictionary already exist. A column compression dictionary is used to compress data ...
over 2 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release

Adding of a new apply parameter DBLOAD_OPTIONS in order to influence an automatic load performed by the Q-Replication apply program on column-organized tables.

A column compression dictionary is used to compress data in a column of a column-organized table. When you load data into a column-organized table, the first phase is the analyze phase, which is unique to column-organized tables.The analyze phase ...
over 2 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Delivered

ASNMON improvements on z/OS

In a customer that has installed Q Replication, I've been working in deploy ASNMON task on z/OS side as replacement of IBM Infosphere Data Replication Dashboard tool that was deprecated. The ASN.IBMSNAP_CONDITIONS tables is used to configure the ...
over 3 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release

Prompt customer need to reduce prune interval

In a busy Q Rep env with many bi-di Q subs, there may lots of P2PNORECAPTURE signal insert into IBMQREP_SIGNAL control table by Q Apply program.As per design, Q Capture delete up to 10000 rows at a time for one prune interval.When the average P2P...
over 1 year ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Is a defect

Ignore log records for a dedicated subscription in IGNORETRANS

In very rare cases Db2 cannot provide log records for Q Capture, e.g. in case of a version mismatch, a compression dictionary error, etc. Removing the subscription and reloading the target is a practical approach. But in some situations (e.g., no...
about 1 year ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Future consideration

Db2 LUW - SQL replication should optionally use TRUNCATE when performing a Full Refresh of large tables

Db2 LUW SQL Replication (10.2.1) When you run a Full Refresh of a subscription set, the asnapply utility issues a DELETE FROM <target table> prior to the refresh of the data. For large tables this has a significant and unnecessary overhead...
over 2 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release

LOAD should not be restarted when Apply fails during SET INTEGRITY

When setting up Replication for a DB2 Table for the first time Apply will use a LOAD FROM Cursor to do an initial copy of the tables data. If there are constraints or generated columns defined for that table Apply will issue a SET INTEGRITY comma...
about 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release

DR4A V1.2 Sequence not replicated

After insert on capture side on table with autonumber column, data is inserted, but sequence is not replicated on apply side. You can follow the following steps to recreate the scenario. CREATE LARGE TABLESPACE "TSD_DBA_TEST" IN DATABASE PARTITION...

MS SQL SERVER 2017/2019 Replication target/source support

Now is mid of 2019, but the latest MS SQL Server support is version 2016. Customer is upgrading their MS SQL Server to 2017 and above. And found the Queue Replication does not support the new 2017 server. Failed to create control table.
over 2 years ago in Replication: Q-Replication & Availability 0 Not under consideration