As
of DB2 version 9.7,
FILENET_CM is
a valid setting for the
DB2_WORKLOAD registry
parameter. The
FILENET_CM parameter setting
bundles the
DB2_EVALUNCOMMITTED registry parameter
and the
DB2_SKIPINSERTED registry parameter,
which help to improve concurrent query and ingestion workloads.
Consider
enabling the DB2_WORKLOAD parameter. When the
these parameters are enabled, unnecessary locking is avoided, which
can improve performance and in some cases, prevent deadlock or query
timeout errors.
- Enable the DB2_WORKLOAD registry parameter
by entering the following command in the DB2 command-line processor:
db2set DB2_WORKLOAD=FILENET_CM
Important: If you have upgraded to DB2
9.7, you must enable the CUR_COMMIT parameter.
The CUR_COMMIT parameter controls the behavior
of cursor stability (CS) scans and works in conjunction with the FILENET_CM setting
of the DB2_WORKLOAD registry parameter. No action
is required if you are running a fresh installation of DB2 9.7. By
default, the CUR_COMMIT parameter is enabled
in fresh installations of DB2 9.7.
- Enable the CUR_COMMIT registry parameter by entering the following
command in the DB2 9.7 command-line processor:
db2 update db cfg using cur_commit ON
- Set the initial buffer pool size for a Content Platform Engine tablespace to 1GB at
a minimum
- A larger size might provide substantial performance benefits.
Typically, 40% of available physical RAM on the database server is
recommended to be dedicated to buffer pools. The database administrator
can adjust this value as necessary
After making these changes, stop and
restart the database using db2stop and db2start.