Updating your DB2 database configuration

Review this tuning information before you migrate your DB2 database.

About this task

For IBM i OS operating system This step is not necessary.

In this step, you update your DB2 database configuration to the minimum requirements for WebSphere Commerce Version 7.0.

Procedure

Navigate to the following directory:
- WC_installdir/bin

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
`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 probably becomes full when you run the database migration script. In this case, you must increase your disk space size or relocate the database log to another disk. During the database migration pre-checking step, the premigration checker estimates the required disk space that is needed for the database log.

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

Open a DB2 command window.
Switch to directory WC_installdir/bin.
Connect to the database with command:
- db2 connect to dbname user userID using password
Note: If your database is remote, you must attach to the remote node before you run the script as follows:
```
db2 attach to remote_node_name user db_admin_user using password
```
Run the updateDB2Configuration script:
- ./updateDB2Configuration.sh dbname userID password remoteDB [log]
- updateDB2Configuration.bat dbname remoteDB [log]
  Where:
  
  dbname
  
  The name of the database to be populated.
  
  userID
  
  The user ID of the user who owns the database.
  
  password
  
  The password of the user that owns the database.
  
  remoteDB
  
  Set to true if the database is remote, false if not.
  
  log
  
  The name of the log file that captures the results of the update.
  
  The script updates your database configuration to the recommended minimum values.
Stop and then restart DB2.