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.
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...
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...
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...
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.
Do not place IBM confidential, company confidential, or personal information into any field.