DB2 pureScale instance creation hangs after GPFS

DB2 pureScale instance creation hangs after GPFS

Hang Issue due to SMAP While creating DB2 pureScale instance, it appears that the node becomes unresponsive under RHEL 7.2. If you reboot the node and look at the /var/log/messages, you may notice these several messages: kernel:BUG: soft lockup - CPU#1 stuck for 23s!...
DB2 pureScale Health Check

DB2 pureScale Health Check

More and more customers are now asking for some way to check the health of the DB2 pureScale system. Let’s just focus on few early diagnostics before we jump to the deep exploration at the SQL statement level. This is just akin going to primary health care...
How to detect log full condition

How to detect log full condition

I have seen working with hundreds of customers a chronic LOG FULL condition and the shortcut people use is to increase the LOGPRIMARY and LOGSECOND. This solution works well for a single unit of work that can not fit into the total log space available. So, first...
Kernel upgrade and impact on pureScale

Kernel upgrade and impact on pureScale

In Linux environment, it is a common practice to upgrade the kernel for security patches, vulnerability fixes etc. And if you are running a DB2 pureScale environment, it is likely that you are going to break the GPFS GPL as soon as you upgrade the kernel and this will...
GPFS Disk Cleanup

GPFS Disk Cleanup

During pureScale instance creation, you might run into instance creation failed condition. Under some circumstances, it is possible that db2icrt does not perform a proper clean-up for GPFS and it may fail next time complaining that the disk is already a GPFS disk....

SQL fishing using WLM

The SQLs while DB2 is up and running can be captured in different ways such as: Query column STMT_TEXT from table functions such as MON_GET_ACTIVITY or WLM_GET_WORKLOAD_OCCURRENCE_ACTIVITIES, and MON_GET_ACTIVITY_DETAILS –> SQLs that have been submitted but...