IBM FileNet P8, Version 5.2.1            

Tuning an IBM DB2 database for Content Platform Engine

When Content Platform Engine is used with an IBM® DB2® database, consider tuning the DB2 database to improve performance.

Ensuring good performance of new (empty) object stores

After you create an object store, it is important that you monitor the database. As new content is added to the object store, the DB2 optimizer continually requires current table and index statistics to select the most efficient access plan. Ensuring that the DB2 optimizer has current statistics is especially important during large ingestions at a high rate, such as migration. It is also important for proof-of-concept testing, stress testing, and testing custom applications.

Monitoring databases by using the FileNet System Dashboard for Enterprise Content Management

For each object store, Content Platform Engine provides counts and durations for the various database operations and server operations. This information can provide valuable insight into database performance.

You can find these counts and durations by using the FileNet® System Dashboard for Enterprise Content Management.

Enabling automatic statistics

For instructions about enabling automatic statistics from the command line, see Enabling automatic statistics collection.

Improvements are possible when manually gathering statistics by using the DB2 Task Center within the first 1,000,000 documents or the first 100,000 folders.

Using DB2 Administration Tools to gather statistics manually

Use the DB2 Administration Tools to update statistics at regular intervals and send notifications. Scheduling information is stored in the DB2 tools catalog database.

For example, a script similar to the following script example might be on the Command Script tab of the Task properties and scheduled to run every 20 minutes during a migration.

CONNECT TO OS1DB;
RUNSTATS ON TABLE CEUSER.CONTAINER ON ALL COLUMNS AND INDEXES ALL ALLOW WRITE ACCESS ;
COMMIT WORK;
RUNSTATS ON TABLE CEUSER.CONTENT ON ALL COLUMNS AND INDEXES ALL ALLOW WRITE ACCESS ;
COMMIT WORK;
RUNSTATS ON TABLE CEUSER.DOCVERSION ON ALL COLUMNS AND INDEXES ALL ALLOW WRITE ACCESS ;
COMMIT WORK;
RUNSTATS ON TABLE CEUSER.GENERIC ON ALL COLUMNS AND INDEXES ALL ALLOW WRITE ACCESS ;
COMMIT WORK;
RUNSTATS ON TABLE CEUSER.HIERARCHYINDEX ON ALL COLUMNS AND INDEXES ALL ALLOW WRITE ACCESS ;
COMMIT WORK;
RUNSTATS ON TABLE CEUSER.RELATIONSHIP ON ALL COLUMNS AND INDEXES ALL ALLOW WRITE ACCESS ;
COMMIT WORK;
RUNSTATS ON TABLE CEUSER.SECURITYDESC ON ALL COLUMNS AND INDEXES ALL ALLOW WRITE ACCESS ;
COMMIT WORK;
CONNECT RESET;

For more information about using the Task Center to schedule tasks, see Task Center overview.

Start of change

Upgrading DB2 from an earlier version

For a Content Platform Engine upgrade that involves upgrading a DB2 database from a version of DB2 earlier than V9.1, ensure that the DB2 SELF_TUNING_MEM parameter is set to ON and the LOCKLIST parameter is set to AUTOMATIC. Otherwise, the upgrade operation of the object store might fail. In versions of DB2 earlier than V9.1, the SELF_TUNING_MEM parameter is set to OFF by default.

End of change

DB2 tuning considerations

The following table lists DB2 configuration and tuning parameters and includes possible starting values.

Consider applying these settings to increase Content Platform Engine performance when Content Platform Engine is running on a DB2 database.

Refer to the IBM DB2 documentation for information about the starting values that are appropriate for your environment.
Table 1. DB2 configuration and tuning parameters
Parameter name Possible starting value Description
DB2_PARALLEL_IO Ensure that the value matches your table space and disk configuration. The value of this registry parameter specifies how DB2 calculates the I/O parallelism of a table space, which can have a significant impact disk I/O performance.
LOCKTIMEOUT 30 Specifies the number of seconds that an application waits to obtain a lock before it times out. Setting this value helps avoid global deadlocks and lock escalations.
LOGFILSIZ 6000 Specifies the size of both primary and secondary log files.
Note:
Specify the size of the log files to be in balance with the number of primary log files.
PCTFREE 20% - 35% Set the value in the following tables:
  • CONTENT
  • CONTAINER
  • DOCVERSION
  • PROPERTYDEFINITION
  • RELATIONSHIP
  • GENERIC
  • LINK
  • SECURITYDESC


Last updated: March 2016
p8ppt127.htm

© Copyright IBM Corporation 2016.