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
Memory constraints for IBM CDC on Db2 for z/OS were one of the reasons why IBM released the remote capture engine which moves the processing outside of z/OS and allows very large transactions to be processed:
https://www.ibm.com/support/knowledgecenter/SSTRGZ_11.4.0/com.ibm.cdcdoc.cdcdb2zremote.doc/concepts/overview.html
Remote capture offloads the processing to a Linux system which can be configured with very large memory (tens of Gigabytes) with spill to disk for transaction staging:
https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcfordb2luw.doc/concepts/assessingdiskspaceandmemoryrequirements.html
https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcfordb2luw.doc/concepts/ramrequirements.html
Quote : "You are performing large batch transactions in your source database rather than online transaction processing (OLTP)."
https://www.ibm.com/support/knowledgecenter/SSTRGZ_11.4.0/com.ibm.cdcdoc.cdcfordb2luw.doc/concepts/diskspacerequirements.html
Quote : "The txnstore directory stores uncommitted transaction data when the log parser stops normally or immediately. This design enables the log parser, on restart, to resume reading the log from where it left off. The uncommitted log entries are stored in a Pointbase database called txqueue. If a large quantity of uncommitted transaction data exists when the log parser stops, the size of this database could be large, but it is deleted when it is no longer needed. The txnstore directory also contains a Pointbase database that is used to store transaction queue snapshots. A transaction queue snapshot stores uncommitted transaction data that is more than x hours old, where x=2 by default. Transaction queue snapshots are used to minimize how far back in the log the log reader needs to start reading if the log parser stops, because in this case the uncommitted transaction data was not stored in the txqueue database. The amount of data that a transaction queue can hold is limited, so these databases never grow very large."