This article will help DB2 DBAs and Users to proactively monitor their most critical and live systems on continuous basis without any impact to production and analyze the data on key points to identify any possible DB2 health/hang/performance issues and fix them.
Whenever a performance problem arises, the database takes the blame, but is that really true? This article will provide a hand's on, step by step approach to determine where the problem is. "Guilty Until Proven Innocent"
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.
OVERHEAD and TRANSFERRATE are tablespace parameters that the optimizer uses to help choose an access plan. Are the defaults good enough? (hint: probably not) In this blog post, I describe a simple way to measure values for your system.
As guest blogger, Russ Stocker shares useful tips on DB2 Large Object (LOB) performance. Part 2: a primer on LOB storage management