It is important to run the DB2 utility RUNSTATS on all of the databases after a significant number of objects are stored and volumes are defined. Running this utility is likely to decrease the length of the DB2 instruction path and to improve performance.

Performance is generally improved when DB2 uses an index to locate an object or object directory entry in a DB2 table. The index scan access path provides more direct access to the data than the table scan access path.

For example, if the DB2 utility RUNSTATS is run on a storage group with only one collection-name and object-name or only one collection-name and pending-action-date, DB2 can choose the table scan access path for operations such as OSREQ DELETE of an object and OSMC object processing. On the other hand, if the DB2 utility RUNSTATS is run after there are a significant number of objects in the Object storage group, the index scan access path can be chosen by DB2.

After running DB2 utility RUNSTATS, rebind the OAM application plans.

DB2 performance can be significantly affected by providing channel separation and DASD device separation when allocating DB2 logs, the directory, and object databases for each Object storage group.

Table spaces are created with primary and secondary space. The secondary space is used when there is no more primary space. The secondary space is allocated from the DB2 storage group containing the primary space.

You must monitor the extension of table spaces into the secondary allocation to determine when to reorganize the individual database table spaces. It might be necessary to add volumes to the DB2 storage group so that additional extensions of the table spaces can occur.

For more information about tuning DB2 databases, see the "DB2 administration" topic in the IBM Information Management Software for z/OS Solutions Information Center.