Db2 Batch processing has long been considered a mainframe only domain. Many enterprise domain applications require bulk processing of large volumes of data for critical environments. But,what if we could offload some of the batch process handling of mainframe jobs to Linux servers using Java?
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 220.127.116.11, 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 18.104.22.168, not to be overlooked are some of the enhancements made in the area of Recovery and Availability.