DB2 8.1 FP10 on AIX 5.3

Our client is having lock problems when executing SQL against their database. They have much more data than we have and we are not having the same problem. Is there a way to trick DB2 to make it look like the database has larger volume of data in its tables than there actually is ?

If there is, how ?

Thanks for any help.

Ask them to increase the database config. parameters LOCKLIST=5000 and MAXLOCKS=80; If their data is 5 times yours, LOCKLIST must be 5 times yours; also their SQLs containing update, delete must have frequent COMMITs.

Any way to make that change I was asking ?

You can reduce your LOCKLIST proportionately if you want to reproduce their problem at your site;that is making the db look bigger from a lock standpoint

You can update the CARD column in SYSCAT.TABLES to indicate the number of rows you want DB2 to think exists. There are other columns in this and other tables that can also be updated.

However, I would suggest that if executing runstats does not help (runstats on table table-name with distribution on key columns and indexes all), then I would try to alter the tables to volatile. Doing a reorg before running runstats would be preferable.