DB2

Automic recommends keeping the following notes in mind when installing and operating DB2 in order to achieve top performance.

It is important to reorganize the AE database including all clients on a regular basis. An extensive database affects performance negatively (prolonged access times etc.).

Notes

General
Do not limit resource consumption. Aborting transactions due to limitations specified in the database hamper processing in the AE system. Additionally, inconsistent database contents can occur which cause subsequent errors or endless loops.
Statistics in DB2: We recommend to turn off automatic runstats in DB2 (every version) and run runstats manually at a point in time where a typical load and a typical mix of activities are in the system. Never run runstats when no or only a few activities are present. This would lead to wrong/not optimal access plans and therefore to less throughput or in the worst case to deadlocks. If you encounter deadlocks, run runstats exactly on those tables where the deadlocks occurring, and at a point in time when you have deadlocks. In most cases this will solve the deadlocks.
Make sure to have the tables dimensioned big enough when creating the database. As the sizes depend on the actual use of AE, the following overview shows the right span of sizes in percent.

Table	Approximate size in percent
RT	40% - 60%
AH	20% - 30%
ABLOB	~ 19%
MELD	10% - 20%
AJPP	5%
RH	5%
Other tables	< 1%

Indices should regularly be reorganized.

DB2 on UNIX/Windows
Default settings are optional for the supported DB2 versions. Changing these values does not improve performance. Automic strongly recommends storing the database's LOG areas on a high-performance disk.