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
Hi Michael,
good that we have increased the upper limit to 4096 now. this should help!
But, I still see a need, for this.. specially for LOGFILSZ.
Most of dbs out there are deployed using standard values.. New APP, new DB, nobody know what will be the transaction volume.. You need to tune that , later..
So, just allowing us to increase LOGSECOND to a big value (more than 255 now) , helps, but its not enough to fully and best tune them...
Keeping logfile sizes smaller can bring issues, like too much archive logs being generated, etc.. so increasing the logfile size is needed..
Or vice-versa..
shared db hosting several different applications, but few of them changed or has been decommissioned, and the workload has decreased.. no need to keep huge, big transaction logs anymore.. so a need to reduce the logfilesize is again required..
Although we have not made LOGPRIAMRY nor LOGFILSIZ online configurable in 11.5.0.0 we have increased LOGPRIMARY and LOGSECOND to 4096 each. So a dynamic LOGSECOND update can be done to address this immediate concern.
Also, a tech preview in 11.5.0.0 and pending support coming soon, Advanced Log Space Management (https://www.ibm.com/support/pages/db2-version-115-advanced-log-space-management-tech-preview) will address transaction log full problems for OLTP type workloads.
We would like customers to try these two new features and then provide feedback if there is still a need for both LOGPRIMARY and LOGFILSIZ to become online configurable.