One of the most common maintenance activities performed on a Db2 LUW database is running Runstats on tables and indexes. Accurate database statistics are vital for the Db2 Optimizer to produce the most optimal plans.
Starting in Db2 Version 18.104.22.168, a new feature called 'DB2_AVOID_LOCK_ESCALATION' provides control over lock escalation behaviour. The feature is configured through a dynamic (no instance recycling needed) registry variable:
It's inevitable that you see a couple of DB2 fix packs every year and place the readme document in a drawer somewhere for perusal later when you are not busy. While the fix packs may contain fixes there are sometimes a few enhancements buried in the fine print.
This presentation from the IDUG EMEA 2016 will provide an overview of DB2 LUW statistics and the options to collect them, to help you achieve optimal query performance, with minimal administration effort.
Investigating performance problems doesn’t have to be hard. There are some basic steps you can take to find common bottlenecks in your system – ‘performance first aid’ if you will. We’re going to look at some of these basic problems and how to find them, using monreport.dbsummary & friends.