In general, a change to the database cfg parm LOGFILSIZ requires the database to be bounced (DEACTIVATE/ACTIVATE) cleanly, meaning no inflight/open transactions (e.g. no indoubt transactions or async undo through DB2_ONLINERECOVERY).
In knowing that when there is any form of database recovery, such
Db2 for Linux, UNIX, and Windows Version 11.5 GA comes with the tech preview of a new feature called “Advanced Log Space Management” (ALSM). Although this new feature still has some limitations and isn’t ready yet for productive use, I’d like to show you how it works and its benefits.
Db2 11.5 is here and with it comes a bunch of new features and changed behaviors in the area of Availability & Recovery that should make your every day tasks easier. Check out the list that includes items like Advanced Log Space Management, Reduced Logging and better HADR Reads on Standby.
With Db2 Version 11.5 the journey has begun to make log space management more autonomic. Reduce your likelihood of hitting transaction log full conditions with Advanced Log Space Management (ALSM), which is a technology preview and not supported for production environments until further notice.
Thinking about your availability and recovery strategy shouldn't give you sleepless nights. Db2 understands the importance of keeping your database online 24x7 and with Db2 11.1 / 11.5 and its continuous delivery of new features and enhancements, you are on the right path of achieving such goals.