Tuning the DB2 CE/PE database server

The DB2 workload type must be configured, and DB2 parallel I/O must be enabled.

Set the DB2 workload type

Since DB2 version 9.7 (and DB2 version 9.5 fix pack 5) FILENET_CM is introduced as a possible value for the DB2_WORKLOAD registry parameter. When setting the DB2_WORKLOAD variable to FILENET_CM it implicitly sets DB2_EVALUNCOMMITTED and DB2_SKIPINSERTED on its behalf.

Sample command: db2set setting DB2_WORKLOAD to FILENET_CM

# db2set DB2_WORKLOAD=FILENET_CM

For more information, refer the FileNet® P8 Version 5.1 Information Center:

https://www.ibm.com/docs/en/filenet-p8-platform/5.5.x?topic=system-overview

Administering IBM FileNet P8 > Performance tuning IBM FileNet P8 components > Tuning IBM > FileNet P8 databases > Tuning an IBM DB2 database for IBM FileNet P8 components

Enable DB2 parallel I/O

DB2 parallel I/O was enabled for all CE/PE data tablespaces. The tablespaces for the object store database and the global configuration database (GCD) are located on a Linux Logical Volume (LV).

Sample command: db2set enabling DB2 parallel I/O for tablespaces

# db2set DB2_PARALLEL_IO=*:4

The above command enables DB2 parallel I/O for all tablespaces. The underlying Logical Volumes (LV) for the database data and log had 4 physical DASDs each. DB2 uses this registry variable to change the way it calculates the I/O parallelism for tablespaces.

Sample command: db2set displaying the registry variable settings

# db2set 
DB2_WORKLOAD=FILENET_CM 
DB2_SKIPINSERTED=YES [DB2_WORKLOAD] 
DB2_EVALUNCOMMITTED=YES [DB2_WORKLOAD] 
DB2COMM=tcpip 
DB2_PARALLEL_IO=*:4

For more information, refer the FileNet P8 Version 5.1 Information Center:

https://www.ibm.com/docs/en/filenet-p8-platform/5.5.x?topic=system-overview

Administering IBM FileNet P8 > Performance tuning IBM FileNet P8 components > Tuning IBM FileNet P8 Content Engine > Tuning IBM FileNet P8 Content Engine databases