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.
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...
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...
Reduce the number of Db2 threads when replicating table with XML column
When a table with a XML column is replicated, we observed a high number of SMF Db2 accounting records, one for each row that a have a XML column.
The records are due to Db2 threads created by the replication process.
As the Db2 SMF records are g...
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...
IBM Data for Availability V1.2 RFE for tablespaces objects replication
IBM Data for Availability V1.2 (IBM Db2 Replication for Continuous Avalability) lacks replication of CREATE, ALTER, DROP and other statements like authorise and revoke for tablespace objects.
When using IIAS console to define table replication w...
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...
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...
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.
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...
The Q-Replication apply programm shall be able to call the Db2 High Performance Unload (HPU) utility by the HPU stored procedure
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...
Do not place IBM confidential, company confidential, or personal information into any field.