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 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.
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.
While system failures seldom happen, most customers expect crash recovery to complete quickly. Our development team decided upon a solution which promised increased availability, without risking the distinguished resilience that Db2 has achieved over the decades.
With the many new features introduced in 188.8.131.52, not to be overlooked are some of the enhancements made in the area of Recovery and Availability.