Locking is one of the most common causes of application slowness in a production database environment. From the application side, the symptom may simply appear as: "The application is hanging." or: "The transaction is taking too long." But from a Db2 DBA perspective, the real question is: Who is waiting, who is holding the lock, and why? In this article, I will walk through a practical DB2 LUW locking investigation using db2pd and Db2 monitoring table functions. The examples

You can copy and keep below SQL oneliners to get packages and tables details from DB2 database. 1. SQL to get the Package details select...

Sometimes we face an error where one (or more) of our db2 tablespaces goes offline caused by loads, DB crashes, abnormal db2 services/or...