Sunday, 30 November 2014

Oops, DB2 and the Insufficient Disk Space

So I was trying to create a second Deployment Environment to host a Process Server for IBM BPM Advanced 8.5.5, when I saw this: -

CWMCB0313E: An error occurred while attempting to connect to database PDWDB2: DB2 SQL Error: SQLCODE=-1762, SQLSTATE=08004, SQLERRMC=null, DRIVER=4.11.69. Error code = -1,762, SQLState = 08004, URL = null.

from the DE Wizard.

I immediately went to check DB2: -

db2 connect to pdwdb2

and saw this: -

SQL1762N  Unable to connect to database because there is not enough space to allocate active log files.  SQLSTATE=08004

When I checked the disk: -

df -kmh

Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_rhel65-lv_root
                       18G   16G  453M  98% /
tmpfs                 931M   40K  931M   1% /dev/shm
/dev/sda1             477M   62M  391M  14% /boot
.host:/               1.1T  135G  904G  13% /mnt/hgfs

which isn't a good look.

Having allocated more space using VMware, it was a quick job to extend the file-system: -

fdisk /dev/sda
reboot 
pvcreate /dev/sda3
vgextend vg_rhel65 /dev/sda3
lvextend /dev/mapper/vg_rhel65-lv_root /dev/sda3 
resize2fs -p /dev/mapper/vg_rhel65-lv_root 

and now we're peachy: -

Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_rhel65-lv_root
                       37G   16G   20G  46% /
tmpfs                 931M     0  931M   0% /dev/shm
/dev/sda1             477M   62M  391M  14% /boot
.host:/               1.1T  133G  906G  13% /mnt/hgfs


No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...