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 our replication environment ASNMON is running on Z to monitor Q Replication processes on a significant number of Z systems. In case ASNMON records an exception, ASNMON sends emails to admin accounts. The mail server team generally requires encr...
Automate restart of IIDR tasks when RRS terminates
We had issues with RRS recently which were solved via a maintenance cycle. During those issues, our IIDR Capture and Apply tasks failed and required manual restart. We have the option TERM=N enabled yet the Capture/Apply tasks were not restarted w...
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 target...
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 a...
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...
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 a...
When a table fails due to structure or availability changes, the replication set should instead set the failed table to inactive instead of crashing capture. It should also send an email notification to alert of the issue.
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...
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 P2...
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...
Do not place IBM confidential, company confidential, or personal information into any field.