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.
Simple way to check consistency between DB2 and IDAA
When implementing data replication we found a number of tables showing different number of rows in DB2 and on IDAA (2 IDAAs installed with replication).
To verify this we did as follows: - Disable table for acceleration in IDAA1 - Run SPUFI with SELECT COUNT(*) against DB2 (query acceleration = NONE) - Run SPUFI with SELECT COUNT(*) against IDAA2 (query acceleration = ELIGIBLE) - Enable table for acceleration in IDAA1 - Disable table for acceleration in IDAA2 - Run SPUFI with SELECT COUNT(*) against IDAA1 (query acceleration = ELIGIBLE)
Comparing results we found differences between all instances. These differences were not due to replication delay time.
It's ok to do this for one ore two tables but it becomes a mess for hundreds of tables. Hence we ask for a simple solution to get an overview of n of rows of a set of tables as desired.
Do not place IBM confidential, company confidential, or personal information into any field.