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

ASNCLP to support a VALIDATE(NO) option

When creating new replication configurations ASNCLP checks the existence of MQ Queues, qmaps, tables, etc. When deploying to production, we need to have pre-prepared and tested the implementation scripts. However, because ASNCLP validates that the...
about 2 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release

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

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 2 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Functionality already exists

Display of replication throughput per subscription

Today Q Apply stores detailed performance statistics on queue level. This idea raises the request to store certain Q Apply throuput statistics (like rows_processed) on subscription level. Background: Today it is very difficult / sometime impossibl...
over 2 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

The Q-Replication apply programm shall be able to call the Db2 High Performance Unload (HPU) utility by the HPU stored procedure

Hello, in enterprise warehouse and OLTP areas of DB2 installations exist often very big databases with several tera bytes (often 100 of TBs) of data. For example we have several OLTP databases with more than 20TB and tables with billion of recor...
over 2 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Future consideration

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

QCapture should recognize column with FIELDPROC at CAPSTART time

QCapture should check if the source table has FIELDPROC in any of its column when it process the CAPSTARTsignal. Today QCapture checks if the source tables have any FIELDPROC at start or reinit time and keeps this information in memory. If a new t...
almost 3 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Delivered

Mutiple thread Spill Agent for Queue Replication

Customer met poor performance of spill agent issue recently. And would like to request this enhancement.The idea can be either below :1) The spill agent runs on multiple threads2) Multiple spill agents serve for one spill queue
almost 3 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

Qrep distributed apply support log split

Qrep is used to replicate data from z to distributed environment, ICBC found the Qrep apply log keep to increase and cause the difficult in operation management, so they request Qrep to enable the log split function on the apply site. they expect...
about 3 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration