Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Delivered
Workspace Db2
Created by Guest
Created on Jun 19, 2018

Make logprimary and logfilsiz online configurable

If workload increases on system, it might be necessary to adjust (typically increase) the available active log space. System downtime is not acceptable in our days. It is sufficient if the log files get resized before re-use and the amount of log files adjust on next log file reclaim. Nevertheless the available disk space should be checked when the config change request gets performed.
  • Guest
    May 5, 2020

    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..

  • Admin
    Michael Roecken
    May 5, 2020

    Although we have not made LOGPRIAMRY nor LOGFILSIZ online configurable in 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 and pending support coming soon, Advanced Log Space Management ( 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.