”. Overthinking and trying to predict Db2 performance is a slippery slope, and so rather than “thinking” about Db2 performance why not have the database tell you how it will perform. The key to this is the Db2 accounting trace, and subsequent Db2 accounting reports. The accounting reports are useful
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.
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.
Moving to a new version or fix pack of Db2 should not be a scary event for databases using the high availability disaster recovery (HADR) feature. Fear of an outage or re-initialization of your standby is no longer a concern.