I searched for the manual which would explain how to write proper SQL. I never found it and the more I talked to people on which strategy I should follow, the less useful information I seemed to get. The same was true whenever I asked for general rules to decide which index was needed.
Starting in Db2 Version 184.108.40.206, 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:
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 220.127.116.11, not to be overlooked are some of the enhancements made in the area of Recovery and Availability.
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.