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
See this idea on ideas.ibm.com
As documented in PMR TS016588496, a QRep configuration may fail to apply a transaction to a target system due to exceeding the MQ Log configuration. At the DB layer, the configuration setting MAX_LOG manages how large a transaction may be in terms of bytes for the log (update/rollback) for a single transaction.
This idea is to allow for a toggle so Replication doesn't replicate system activities, like Reorg/Index Builds/etc, but the MAX_LOG setting limits the size of the reorg/index build when it doesn't need to, since there is no user data to replicate from these activities. Thus having to adjust MAX_LOG for reorgs/index builds/etc opens a window where the target system may not be syncable, and there is no recovery and/or easy to determine what wasn't replicated.
Since the replication error may be unrecoverable, the only remediation is to rebuild the target system which may take weeks/months - is this really a reasonable outcome due to the behavior of how MAX_LOG is implemented? Or there being no toggle to address how logging is manager for user vs system activities?
Please consider providing a toggle that allows for management of User vs System transactions regarding log allocation that is configurable online and doesn't require a recycle of the DB.
Share if additional details are needed.
Needed By | Week |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.