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

In today’s digital world, data is the new oil and Database Administrators (DBAs) are the guardians who keep it secure, available, and...

In SQL Server, an orphaned user is a database user that is not mapped to a valid SQL Server login at the instance level. It is a user...

A Database Administrator (DBA) is responsible for designing, implementing, and maintaining the database system, as well as establishing...

Sometime you've encountered with below error/issue during version upgrade check in DB2. Well, while executing db2ckupgrade sometime gives...