Update your DB2 database configuration

Review this tuning information prior to migrating your DB2 database.

I5/OS|This step is not necessary.

In this step you will update your DB2 database configuration to the minimum requirements for WebSphere Commerce v6.

1. Navigate to the following directory:

   • WC_installdir/bin

2. Review the database tuning parameters in the updateDB2Configuration script. Consider these values as the minimum required. Check the values of this script and evaluate your specific database needs, for example, you might already be using higher values. In such a case, you should not run this script.

   A list of the DB2 database parameters that are updated and the values to which the script sets them are contained in the following table:
   

   DB2 parameter	Value
   applheapsz 1000	1000
   stmtheap	60000
   app_ctl_heap_sz	8192
   locklist	2400
   indexrec	RESTART
   logfilsiz	1000
   logprimary	12
   logsecond	10
   pckcachesz	4096
   catalogcache_sz	4096

If any of the configuration parameters for your current database already exceed these minimum parameters, update the script to remove the line for that particular parameter before you run it.

Depending on the actual size of your database, you can increase or decrease the logfilsiz from the default setting of 1000 blocks. Otherwise, if there is not enough space, the transaction log file will probably get full when you run the database migration script. In this case, increase your disk space size or relocate the database log to another disk. During the database migration pre-checking step the premigration checker will estimate the required disk space needed for the database log.

For more information on these DB2 parameters, and to determine the appropriate values for your database, see the DB2 Administration Guide.

db2 attach to remote_node user db_admin_user using password