Performance Tuning for Content Manager

398 Performance Tuning for Content Manager

14.1 Maintenance tasks overview

After a Content Manager system has been designed, installed, and configured, it

still requires regular maintenance.

By maintaining a Content Manager system properly and in a timely manner, you

get the best possible performance from it over time, as well as potentially avoid

problems that can manifest themselves as system-endangering situations.

Much of this chapter is extracted from IBM Content Manager System

Administration Guide V8.2, SC27-1335; the publication can be used in

conjunction with this redbook to provide further details.

Regular maintenance tasks include the following activities:

 Optimizing server databases

 Monitoring LBOSDATA directory size

 Managing staging directory space

 Removing entries from the events table

 Removing log files

 Managing Resource Manager utilities and services

 Replacing or repartitioning a hard disk

 Backing up

14.2 Optimizing server databases

Database statistics should be updated periodically, daily, or weekly depending on

the ingest load, and the Library Server and Resource Manager databases in

order to maintain good performance. This should also be the first step whenever

it appears that there are problems associated with Library Server performance,

such as slower logons, searches, or indexing.

runstats and rebind database tables

Keeping DB2 statistics up to date on the tables and data helps the optimizer to

choose the best execution access plans for SQL statements to maximize

performance. We recommend that you run the runstats and rebind commands

on a regular basis as part of ongoing database maintenance. Recalculating table

statistics is

critical to improving database performance and should be done

regularly. If table statistics have not been recalculated recently, then this should

be the first step in diagnosing DB2 performance issues.

Find instructions for running these commands in the DB2 Command Reference

(Start → Programs → IBM DB2 → Information → DB2 Information Center

Chapter 14. Maintenance 399

and type runstats or rebinds in the search field). Use the DB2 Command

Reference, SC09-4828, and the following instructions to run these commands:

1. Open a DB2 Command Window by clicking Start → Programs → IBM

DB2 → Command Line Tools → Command Window. If you are using a

UNIX machine to perform these tasks, after the db2profile script has been run

(if it is not in root’s .profile), the commands can be typed directly onto the

UNIX command line. If you are not already connected to the database,

connect to the database by entering:

db2 connect to <db name> user <user ID> using <password>

– <db name> is the name of the database.

– <user ID> is user ID with administration rights on the database.

– <password> is the valid password of the user ID.

2. Run runstats as follows:

db2 runstats on table <table_name> with distribution and detailed

indexes all

This should be done for each table in the database, for both the Library

Server and Resource Manager databases. For example, for SYSINDEXES

table, use:

db2 runstats on table sysibm.sysindexes

3. The DB2 system db2rbind command should be run after calculating table

statistics to rebind all of the packages in the database. This is a system

command and not a command line statement. This means that it does not

have to be prefixed with db2 as the runstats command does.

Run db2rbind as follows:

db2rbind <database_name> -l <logfile name> all /u <userid> /p

<password>

For example:

db2rbind icmnlsdb –l bind.log all /u icmadmin /p password

db2rbind rmdb –l bind.log all /u rmadmin /p password

4. Check your log file to see the results. Another way that you can check the

success of a rebind is by using the DB2 Control Center:

a. Open the Control Center by clicking Start → Programs → IBM DB2 →

General Administration Tools → Control Center.

b. Go to the database against which you ran db2rbind.

c. In the database, go to Application objects → Packages.

Check the Last bind date and Last bind time columns. The date and time

indicate when you last had DB2 rebind all of the packages.