WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Upgrading the Common database manually

After migrating the server from a previous version, you must upgrade to a new database schema for the "Common" database before you start the server. You must upgrade manually if the database user that is defined for the data source does not have sufficient authorization to modify the database schema.

Before you begin

Note: Upgrading the Common database manually applies only when migrating from version 6.1.x to version 6.2.x. For information on creating the common database when migrating from version 6.0.2 to version 6.2.x see Creating the common database and configuring the recovery subsystem when migrating from version 6.0.2 to version 6.2.x.

About this task

Any database that is accessed by a migrated server needs to have its schema updated before you start the server. In the case of a cluster, any database that is accessed by any of the migrated cluster members needs to have its schema updated before you start any of the cluster members. You must upgrade manually if the database user that is defined for the data source does not have sufficient authorization to modify the database schema. For the Common database, the database user that is configured for the data source must be authorized to perform all of the following operations: create and alter tables and create and drop indexes and views.
Procedure
  1. Make sure that you are using a user ID with sufficient authority to update the database schema.
  2. Back up the database.
  3. Locate the directory where the database scripts are located: install_root/dbscripts/component_name\database_type.

    Where:

    install_root
    is the root directory of the WebSphere® ESB version 6.2 installation file system.
    component_name
    is CommonDB.
    database_type
    is a name corresponding to the database product you are using. Applicable database types and their directory names are as follows:
    Database type Directory name
    DB2® for z/OS® Version 8.x DB2zOSV8 - Use scripts in this directory if your initial database configuration used DB2 z/OS v8 (uses long table names) or if you upgraded from DB2 z/OS v7 to DB2 z/OS v8
    DB2 for z/OS Version 9.x DB2zOSV9 - Use scripts in this directory if your initial database configuration used DB2 z/OS v9 or later (uses long table names) or if you upgraded from DB2 z/OS v7 to DB2 z/OS v9.
    Derby Derby
    Note: If you have an existing Cloudscape database for a previous (6.0.2) installation of WebSphere ESB, the database must first be upgraded from a Cloudscape database to a Derby database. See . When you have a Derby database that corresponds to that same (6.0.2) WebSphere ESB version, you must upgrade the database to correspond to WebSphere ESB version 6.2 with the scripts in this directory.
    For specific database product names and versions see Database configurations.
  4. Locate the migration scripts for the database that starts with word upgradeSchema. Based on your database(s), you will find upgradeSchema.bat, upgradeSchema.sh, or both, as well as component-specific SQL scripts like upgradeSchema<Migrated WBI version>_<component>.sql. For example, to upgrade the common database schema from WebSphere ESB version 6.0.2.x to version 6.2 and dbType is DB2_UNIVERSAL, you need the following migration scripts:
    • install_root/dbscripts/CommonDB/DB2/upgradeSchema.bat
    • install_root/dbscripts/CommonDB/DB2/upgradeSchema.sh
    • install_root/dbscripts/CommonDB/DB2/upgradeSchemaTables.bat
    • install_root/dbscripts/CommonDB/DB2/upgradeSchema602_Recovery.sql
    • install_root/dbscripts/CommonDB/DB2/upgradeSchema602_relationshipService.sql
    • install_root/dbscripts/CommonDB/DB2/upgradeSchema602_governancerepository.sql
    • install_root/dbscripts/CommonDB/DB2/upgradeSchema602_DirectDeploy.sql
    • install_root/dbscripts/CommonDB/DB2/upgradeSchema602_CommonDB.sql
    • install_root/dbscripts/CommonDB/DB2/upgradeSchema602_customization.sql
    Note: Other scripts that exist in the same CommonDB/DB2 directory may be used, depending on what version of WebSphere ESB you migrated from.
  5. Copy the appropriate script or scripts from the directory in which you found it to the system on which the database is hosted.
  6. Check the SQL scripts, and modify them, if necessary, to meet your requirements. This includes any scripts in the directory that are named according to the following syntax: upgradeSchemannn_<component>xql where nnn corresponds to a product version number and "component" corresponds to any one of the following:
    • CommonDB
    • relationshipService
    • governancerepository
    • DirectDeploy
    • customization
    For example, you might need to change a user name, password, or file path.
  7. Using your database client, connect to the database. This is to ensure that it can connect.
  8. Run your version of the upgrade SQL scripts. For information on how to execute a .sql script with your database, refer to the documentation for your database product.

    If there are any errors, or failure is indicated in your database client output, fix the reported errors and try this step again.

Results

The database schema has been updated. When the server is started for the first time after the upgrade, the data is migrated according to the new schema. After the data has been migrated,version 6.1.x or version 6.0.2.x servers cannot run against the database.

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.zseries.doc/doc/tmig_vtv_upg_cdb.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).