IBM Data and AI Ideas Portal for Customers
This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
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
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
The lack of memory was in structures beloow the 2G bar. Probaly will be better if those APPLY structures will be moved above the 2G bar. The important think is that all wich pass through CAPTURE can be applied at APPLY side.
Q Apply memory usage for reading transaction messages for apply at target is controlled by MEMORY_LIMIT parameter in IBMQREP_RECVQUEUES.
If Q Apply MEMORY_LIMIT is exceeded due to a very long transaction, Q Apply is still able to apply the transaction at the destination target by running in MONSTER mode.
In MONSTER mode, Q Apply reads each message of a long transaction serially and applies it piecemeal on the target database, instead of trying to read the entire transaction into memory first.
In this way it does provide guaranteed delivery for long transactions that cannot fit in Q Apply memory, even if it may not be very performant in Monster mode due to serial read from receive queue.
The only way it will not be apply a long transaction at target is if DB2 gives an error when applying rows to target table(s).
We therefore need clarification on what exactly is meant by “memory lack at destination” ?
Is the memory lack in Q Apply program memory?
Or is it lack of memory / resources on DB2 side?
What exact failure did Q Apply and/or DB2 report when the issue with long transaction was encountered (such as sample of Q Apply / DB2 diagnostic logs)?