Migrate > Migrating WebSphere Commerce > Prepare to migrate WebSphere Commerce



Update the DB2 database configuration

Review this tuning information prior to migrating your DB2 database.

In this step we will update the DB2 database configuration to the minimum requirements for WebSphere Commerce v7.0.


Procedure

  1. Navigate to the following directory:

  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 the 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 AUTOMATIC
    stmtheap AUTOMATIC
    locklist AUTOMATIC
    indexrec RESTART
    logfilsiz 1000
    logprimary 12
    logsecond 10
    pckcachesz AUTOMATIC
    catalogcache_sz 4096

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

    Depending on the actual size of the 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, we will need to increase the disk space size or relocate the database log to another disk. During the database migration pre-checking step the pre-migration checker will estimate the required disk space needed for the database log.

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

  3. Open a DB2 command window.

  4. Switch to directory WC_INSTALL/bin.

  5. Connect to the database with command:

    • db2 connect to dbname user userID using password

    If the database is remote, attach to the remote node before running the script... 

    db2 attach to remote_node_name user db_admin_user using password

  6. Run the updateDB2Configuration script:

    • AIXLinuxSolaris ./updateDB2Configuration.sh dbname userID password remoteDB [log]

    • Windows updateDB2Configuration.bat dbname remoteDB [log]

      Where:

      dbname

      The name of the database to be populated.

      AIXLinuxSolaris userID

      The user ID of the user who owns the database.

      AIXLinuxSolaris 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 will capture the results of the update.

      The script will update the database configuration to the recommended minimum values.

  7. Stop and then restart DB2.


Previous topic:

Prepare the WebSphere Commerce environment


+

Search Tips   |   Advanced Search