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,
Post an idea
Upvote ideas that matter most to you
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.
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...
Q-Replication Apply program shall be able to recognize if a column-organized table contains already a dictionary
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 ...
Requesting Q-Replication capability from Non-Temporal to Temporal Table
This RFE/Idea is to request Q-Replication capability from Non-Temporal source to Temporal Table target. The existing Q-Replication only supports from Temporal to Temporal tables. For reporting within FTM (Financial Transaction Manager), there is...
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...
Sequence Number management in a replicated DB2 system
Today sequence numbering in a DB2 subsystem that is being replicated to a secondary site needs to be managed outside of the replication support manually by the customer. Guidance has been given to use odd/even numbering on one side and the other....
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.
V12-CERT-2017 - Support for replication of REORG DISCARD events
When a REORG discard is run on the source side in a replication relationship / event relationship we want to be able to replay this event on the target side somehow.We do not want to do this by logging the discards in the REORG, of course.One sug...
support for CHG_UPD_TO_DEL_INS=Y in Q-replication z/OS
we are on DB2 z/OS V12R1M509 and are migrating our applications from SQL-replication to Q-replication. we have multiple applications which use Non-Condensed, Non-complete CCD targets and are built around using IBMSNAP_REGISTER CHG_UPD_TO_DEL_INS=Y...
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...
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.
Do not place IBM confidential, company confidential, or personal information into any field.