DB2 DPF with two nodes

Install Binaries


  • DB2 InfoSphere Warehouse Edition,
  • DB2 Spatial Extender,
  • DB2 Universal Fixpack.

DB2 Spatial extender has to be the same edition as DB2 InfoSphere, e.g., 9.7.0. Suppose binaries are unzipped as follows:

e.g.: DB2 download folder: /data2/fwang/db2dpf

/server: infosphere warehouse edition

/gse: db2 spatial

/universal: universal fixpack (9.7.6)

/license2: license

To setup license, just copy license file to the install folder: cp /data2/fwang/db2dpf/license2/*.lic /data2/fwang/db2dpf/server/isw/Ese/db2/license


Two nodes: node40 and node41


node40: /shared: local, also exported as /shared on node41

node41: /db: local, has access to shared folder /shared

DB2 accounts (excluding db2admin user) and db2 binary will be installed in a shared folder:

e.g.,: /shared/database/db2inst

DB2 databases will be installed locally:

node40: /shared/database (or soft link: /db/shared/database)

node41: /db/shared/database

/data will be for data

/log will be for log

Create DB2 Users

Create db2 users on both master and slave nodes, with same login information. The users should be local users and not NIS or NIS+ users. db2admin user(dasuser1) should have local home, and db2inst1 and db2fenc1 should have shared home folders.

sudo /usr/sbin/groupadd -g 999 db2iadm1
sudo /usr/sbin/groupadd -g 998 db2fadm1
sudo /usr/sbin/groupadd -g 997 dasadm1
sudo /usr/sbin/useradd -u 1104 -g db2iadm1 -m -d /shared/database/db2inst1 db2inst1
sudo /usr/sbin/useradd -u 1103 -g db2fadm1 -m -d /shared/database/db2fenc1 db2fenc1
sudo /usr/sbin/useradd -u 1102 -g dasadm1 -m -d /home/dasusr1 dasusr1

Then sudo passwd to change passwds for all users.

Setup DB2

sudo /data2/fwang/db2dpf/server/isw/Ese/db2setup

Save response files: /data2/fwang/rsp/db2ese.rsp, db2ese_slave.rsp

(Check if license is right if needed. Ignore this if license file was copied before.)

Add license:

sudo ./db2licm -l

If license file not copied:

sudo /shared/database/db2inst1/sqllib/adm/db2licm -a /data2/fwang/db2dpf/license2/iwebe.lic

Setup Public Key Authentication (Avoid Login between Nodes)

Run as db2instance user:

su -l db2inst1

Do this on both master/slave nodes:

ssh-keygen -t rsa
cd ~/.ssh
mv id_rsa identity
chmod 600 identity
cat id_rsa.pub>> authorized_keys
chmod 644 authorized_keys
rm id_rsa.pub

ssh-keyscan -t rsa node40 node40.clus.cci.emory.edu,>> ~/.ssh/known_hosts
ssh-keyscan -t rsa node41 node41.clus.cci.emory.edu,>> ~/.ssh/known_hosts

Do this on master node:

sudo nano /etc/ssh/sshd_config (adding entry and update entry):

# HostbasedAuthentication no
HostbasedAuthentication yes

Do this on both master/slave nodes:

sudo nano /etc/ssh/shosts.equiv:

Add following:


Go to: /etc/ssh:

sudo ssh-keyscan -t rsa node40 node40.clus.cci.emory.edu,>> /tmp/ssh_known_hosts
sudo ssh-keyscan -t rsa node41 node41.clus.cci.emory.edu,>> /tmp/ssh_known_hosts
sudo cp /tmp/ssh_known_hosts .

On slave nodes (node41):

sudo nano /etc/ssh/ssh_config
#HostbasedAuthentication no
HostbasedAuthentication yes
EnableSSHKeysign yes

Restart ssh on both nodes:

sudo /sbin/service sshd restart

Enable ssh for DB2 on both nodes:

db2set DB2RSHCMD=/usr/bin/ssh

Fix if wrong:

Clean all db2 processes:


Stop fault monitor daemon (db2fmcd):

sudo ./db2fmcu -d

sudo /shared/database/ibm/db2/V9.7/bin/db2val
or db2val -o
(missing lib)

Install DB2 from cmd with response file:

Master node:

sudo ./db2setup -u /data2/fwang/db2dpf/rsp/db2ese.rsp

Find error, fix it:

db2set DB2COMM = TCPIP
db2set DB2_ENABLE_LDAP=no
db2set -all DB2COMM

Setup DB2 slave:

sudo ./db2setup -u /data2/fwang/db2dpf/rsp/db2ese_addpart.rsp

Install DB2 Spatial Extender on Master Node

db2stop first.

Setup DB2 Spatial Extender on master node

Install DB2 spatial extender on master node, by running db2setup from DB2GSE

installation file path:

sudo ./db2setup

Choose to generate response files only, and reuse existing instance.

Response file generated: db2gse.rsp

sudo ./db2setup -u ../rsp/db2gse.rsp

Apply Fixpack (Master Node)


db2admin stop

Under universal:

sudo ./installFixPack -b /shared/database/ibm/db2/V9.7

db2 instance update (master node):

cd /shared/database/ibm/db2/V9.7/instance/
sudo ./db2iupdt db2inst1

Setup Physical Partitioning Information on both Master and Slave Nodes:

Shut down db2 first: db2stop

16 cores, 15 partition per core

Create a file db2nodes.cfg in /home/db2inst1/sqllib, with following entries:

0 node40 0
1 node40 1
2 node40 2
3 node40 3
4 node40 4
5 node40 5
6 node40 6
7 node40 7
8 node40 8
9 node40 9
10 node40 10
11 node40 11
12 node40 12
13 node40 13
14 node40 14
15 node41 0
16 node41 1
17 node41 2
18 node41 3
19 node41 4
20 node41 5
21 node41 6
22 node41 7
23 node41 8
24 node41 9
25 node41 10
26 node41 11
27 node41 12
28 node41 13
29 node41 14

Manually add a partition:

db2start DBPARTITIONNUM 1 ADD DBPARTITIONNUM HOSTNAME node40.clus.cci.emory.edu PORT 1

Look at system resources:

numactl –hardware

I/O Consideration

DB2 doc: “Optimizing table space performance when data is on RAID devices”

Linux article: “A Comparison of Chunk Size for Software RAID-5”

RAID strip size = chunk size * disks in an array (e.g., 64K x 5 = 320K for our case.)

Chunk size is also “segment size of disk”.

  • RAID5 chunk size: 64K
  • Disk segment size: 64K
  • RAID5 Strip size: 320K

The DB2 extent size for a tablespace is the amount of data that the database manager writes to a container before writing to the next container.

The extent size should be a multiple of the underlying segment size of the disks. Also a multiply of the page size.

  • Page size (large table): 32KB
  • Extent size = 320K x N
  • Prefetch size = 320K x N

Check raid level:


md0 : active raid5 sdd1[4] sdc1[3] sdb1[2] sda1[1] hdb1[0] 11721065472 blocks super 1.0 level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]

See Chunk size

Create and Configure a Partitioned Database

After DB2 is created, a PAIS database needs to be created. This includes enabling spatial database, generating tables, creating user-defined functions, and assign users with proper privileges, which are shown below. A set of SQL scripts are created to facilitate this.

Create table spaces by run the SQL script createdb_dpf.sql (download here: createdb_dpf.sql)

  • This script is used to create the database, alter configurations for the database, create buffer pools, and create tables spaces to be used by the database.
  • The following information needs to be specified to your real server environment:
    • Set database name: replace TESTDB as the real database name;
    • Set database storage path;
    • Set database DBPATH;
    • Set database newlogpath;
  • Database parameters may also need to be adjusted based on server resources.
  • The script needs to be executed by DB2 instance user (e.g., db2inst1).
  • Run the script as db2 -tf createdb_dpf.sql.
  • Note:
    • Set the proper permission to this current DB2 instance user and make all paths you specified accessible to him.
    • Be patient and wait for a long time to build up the database.

Enable the Spatial Extender to the database.

Use the command db2se enable_db TESTDB (TESTDB is your database's name).

Create Schema

Create tables

Create Tables by running these SQL scripts below (notice: change to your own database name in those SQL scripts):

Create Keys and Indexes

Create keys and Indexes by running these SQL scripts below:

  • db2 -tf keys.sql
  • db2 -tf index.sql Scripts can be downloaded here: keys.sql, index.sql

Materialize (Replicate) SRS table

The performance of spatial queries in a partitioning environment may be improved by replicate Spatial Reference System table across all nodes.

Script can be downloaded here: create_srs_mqt.sql