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 updateson 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
The standby inherits the db parms upon restore. If enabling ROS and running various reports (and other "stuff") on the standby - the memory parms (bufferpools, various heaps, etc) may not be optimal for that workload, but STMM is not altering the "values". One can get around it using the DB2_OVERRIDE_BPF - but that (in my view) - kinda defeats the purpose. And in case of a failover, one would have to remember to "take it off" and re-activate, etc. Kind of clunky. So - I would rather have that the STMM actually was active on the standby, and does its magic like on the primary. In case of a takeover - it would fairly quickly re-tune itself to the current workload.
Do not place IBM confidential, company confidential, or personal information into any field.