Upgrading DB2 for z/OS databases

Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15

For DB2® for z/OS® databases, increase the buffer size for table spaces, initialize new databases, and upgrade your existing schemas and data.

Run the DBUpgrade command to modify your existing database schemas and data for use with IBM® Business Automation Workflow 26.x. The DBUpgrade utility updates the following items to 26.x:

• System Data toolkit
• Heritage Process Portal process application
• Hiring Sample tutorial process application

Important: Although the DBUpgrade utility installs the System Data toolkit 26.x, the utility does not automatically update existing dependencies. Therefore, test your applications after migration. If they are not compatible with the new version of Business Automation Workflow, you can update the dependencies so that your applications continue to use the previous version.

For each deployment environment that you are creating, complete the following steps:

1. To initialize your new database components, run the create*.sql files that were generated when you ran the BPMConfig -create command.
   1. Copy the create*.sql scripts for the new database components from target_deployment_manager_profile/dbscripts/Upgrade/ to your database computer.
   2. Connect to each database and run the customized SQL files against the database.
      You can use the BPMConfig properties file to help you determine the databases against which to run the SQL.
   3. To create the messaging engine tables, complete the following steps:
      1. If you are reusing your previous messaging engine database and schema, manually drop the existing messaging engine tables.
         Tip: The messaging engine table names use the SIB prefix.
      2. Run the createSchema_Messaging.sql file to re-create the tables manually on the database where you want to configure Messaging. This file is in deployment_manager_profile/dbscripts/Upgrade/cell_name.de_name/database_type/Messaging_engine_database_name.Messaging_engine_schema_name.
2. For Process and Performance Data Warehouse databases, complete the following steps for your DB2 for z/OS database:
   1. To ensure that you can successfully run the SQL scripts for the DB2 for z/OS schema upgrade, alter the following table spaces to increase the buffer pool size to 8K:
      • WLPT33
      • WLPT34
      • WLPT52
      • WLPT53
      • WLPT134
      • WLPT145

      To do so, drop the table spaces and create them again with 8k buffer pools.

      Note: You should move the data to a temporary table space before dropping it. Then, copy it back when you re-create the table space.

      Example SQL to re-create table spaces:

      SET CURRENT SQLID = 'ZASIPS';
      
      DROP TABLESPACE ZACELLDB.WLPT33;
      DROP TABLESPACE ZACELLDB.WLPT52;
      
      CREATE TABLESPACE WLPT33
      IN ZACELLDB
      USING STOGROUP ZADBSTO
      SEGSIZE 32
      LOCKMAX SYSTEM
      LOCKSIZE ROW
      DEFINE YES
      CCSID UNICODE
      BUFFERPOOL BP8K1;
      
      CREATE TABLESPACE WLPT52
      IN ZACELLDB
      USING STOGROUP ZADBSTO
      SEGSIZE 32
      LOCKMAX SYSTEM
      LOCKSIZE ROW
      DEFINE YES
      CCSID UNICODE
      BUFFERPOOL BP8K1;

   2. From the target_deployment_manager_profile/dbscripts/Upgrade/cell_name.de_name/database_type/ProcessServer_database_name directory, obtain the upgradeSchema_ProcessServer.sql script that corresponds to the product version that you are migrating from.
      For example, if you are migrating from IBM Business Process Manager V7.5.x, copy the script named upgradeSchema751_ProcessServer.sql to your working directory.

      Connect to the DB2 for z/OS database, and run the upgradeSchema75x_ProcessServer.sql or upgradeSchema8xx_ProcessServer.sql script against the database by using your preferred tool. Then, run the newly created createProcedure_ProcessServer.sql script to create the stored procedures.

      You can safely ignore SQL errors about creating duplicate indexes.

      You can safely ignore SQL errors with text similar to the following text: ROW NOT FOUND FOR FETCH, UPDATE, OR DELETE, OR THE RESULT OF A QUERY IS AN EMPTY TABLE. SQLCODE=100, SQLSTATE=02000, DRIVER=3.61.96 for the following SQL statement:

      UPDATE LSW_BPD_INSTANCE SET ATTACHMENT_STORE = 3  WHERE BPD_INSTANCE_ID IN (SELECT DISTINCT  BPD_INSTANCE_ID FROM LSW_BPD_INSTANCE_DOCUMENTS)
      UPDATE LSW_BPD_INSTANCE SET  CASE_FOLDER_SERVER_NAME='IBM_BPM_ContentStore'  WHERE NOT CASE_FOLDER_ID IS NULL
      UPDATE LSW_BPD_ACTIVITY_INSTANCE SET ENABLDOC_SERVER_NAME='IBM_BPM_ContentStore'  WHERE NOT ENABLING_DOCUMENT_ID IS NULL
      UPDATE LSW_BPD_INSTANCE SET  STARTING_DOCUMENT_SERVER_NAME='IBM_BPM_ContentStore'  WHERE NOT STARTING_DOCUMENT_ID IS NULL

      The script is generated in deployment_manager_profile/dbscripts/Upgrade/deployment_environment_name/database_type/database_name.schema_name.

   3. From the target_deployment_manager_profile/dbscripts/Upgrade/cell_name.de_name/database_type/PDW_database_name directory, obtain the upgradeSchema_PerformanceDW.sql script that corresponds to the product version that you are migrating from.
      For example, if you are migrating from Business Automation Workflow V7.5.x, copy the script named upgradeSchema751_PerformanceDW.sql to your working directory.

      Connect to the DB2 for z/OS database, and run the upgradeSchemaPerformancexxx_PerformanceDW.sql script against the database by using your preferred tool.

      You can safely ignore SQL errors about creating duplicate indexes.

   4. Check the status of the table spaces.
      When you run the upgradeSchemaxxx_ProcessServer.sql script, you might see the warning message SQL CODE -162, indicating that the table space is under Check Pending status. Use the following command to identify table spaces that are under Check Pending status:

       -DISPLAY DATABASE(PS_DB_NAME) SPACENAM(*) RESTRICT

      Tip: For improved performance, list the table spaces in AREO* status and use REORG to fix them.

      After each table space is identified, the database administrator can use the CHECK DATA utility to fix it.

      If you are using DB2 on a z/OS system, run the following command:

       Command Prefix DISPLAY DATABASE(PS_DB_NAME) SPACENAM(*) RESTRICT

3. Copy the sample migration.properties file and rename it to target_migration.properties. Update the file with the configuration information for the target environment.
   Check all the target properties and edit them if required, following the instructions in the sample file. The sample file is in install_root/util/migration/resources/migration.properties.
   Specify target environment values for the following properties:

   • admin.username and admin.password: Use the cellAdmin user or the WebSphere® primary administrative user name.
   • bpm.home: The installation root of your target product. Make sure that the file separators are forward slashes (/). Use the full path. Do not use the tilde character (Ëœ) to stand for the home directory. For example:

     bpm.home=/opt/IBM/BPM
     bpm.home=C:/IBM/BPM

   • profile.name: The target deployment manager profile.
   • target.config.property.file: The full path of the configuration properties file that you used to create your target environment.

   You must specify the source cluster names, not target cluster names, for the following properties:

   Note: Because IBM BPM Express is a stand-alone server and not a cluster, you must not use the following properties for the source cluster name.

   • source.application.cluster.name
   • source.messaging.cluster.name
   • source.support.cluster.name
   • source.web.cluster.name
4. Go to the target_install_root/util/dbUpgrade directory and set the database.is.db2zos property to true in the upgrade.properties file.
   For example:

   database.is.db2zos=true

5. To upgrade the databases to 26.x, run the DBUpgrade utility on the server in the target environment.
   Important: Ensure that your deployment manager and all the managed nodes in the source environment have been stopped before running this utility.

   install_root/bin/DBUpgrade.sh -propertiesFile target_migration_properties_file

   where:

   • target_migration_properties_file is the full path to the migration properties file in which you specified the configuration information for the target environment.
   For example:

   install_root/bin/DBUpgrade.sh -propertiesFile /opt/BPM26.x/util/migration/resources/target_migration.properties

   The command displays each database upgrade action as it runs. After all the upgrades are finished, you see a message similar to the following message:

   All upgrade steps have been completed successfully.

   The log location is listed in the output. If there are errors or exceptions, they appear in the log.

   If you are migrating from IBM Business Process Manager V7.5.x and you get an out-of-memory error indicating too many or too large data records, you can try to increase the heap size of the JVM for the DBUpgrade command. Open the DBUpgrade.sh file in install_root/bin and find -Xmx2048m in this file. It indicates that the maximum JVM heap size is 2048 megabytes. You can increase this value to update the heap size.

   If necessary for troubleshooting, you can run DBUpgrade -generateSQLOnly to generate the SQL files without running them. You can then edit the generated SQL files manually and run DBUpgrade -omitSQLGeneration to upgrade the database using the modified files.

6. Run the BPMUpdateSystemApp command on all .twx files except those files that have the word sample in its name from the folder install_root/BPM/Lombardi/imports/. If, for example, the file was named procurement-sample.twx, it would be excluded. If, for example, the file was named system-toolkit.twx, the command would look like this:

   wsadmin -lang jython -conntype none -javaoption -Xms256m -javaoption -Xmx1024m
   wsadmin>AdminTask.BPMUpdateSystemApp( [ '-twxFile', 'install_root/BPM/Lombardi/imports/system-toolkit.twx', '-clusterName', 'PC_clusterName' ] )

   See BPMUpdateSystemApp command for more information about the command.