Upgrading DB2 databases

For DB2, initialize new databases and upgrade your existing schemas and data so that your databases work with the new version of IBM® Business Process Manager.

Figure 1. Sample environment after existing schemas and data are updated. The source environment is not running and the databases are not in use. The databases contain updated schemas and data. The target is not running but contains a deployment environment.

Run the DBUpgrade command to modify some of your existing data for use with IBM BPM V8.6.0.

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

1. Copy the whole folder target_deployment_manager_profile\dbscripts\Upgrade\ to your database computer.
2. If you did not create a new messaging engine database and instead you plan to reuse your previous messaging engine database and schema, you must manually drop the existing messaging engine tables for each one.
   Tip: The messaging engine table names use the SIB prefix.
   If you see any of the following error messages, follow the instructions in the message to increase the default log file size.

   CWMCB0350E: Database CMN172DB does not have defined a sufficient logfile size. Use UPDATE DB CFG FOR CMN172DB USING LOGFILSIZ 16384 DEFERRED to change. Actual size = 4096, minimum size = 16384.
   CWMCB0350E: Database PS172DB does not have defined a sufficient logfile size. Use UPDATE DB CFG FOR PS172DB USING LOGFILSIZ 16384 DEFERRED to change. Actual size = 4096, minimum size = 16384.
   CWMCB0350E: Database PDW172DB does not have defined a sufficient logfile size. Use UPDATE DB CFG FOR PDW172DB USING LOGFILSIZ 16384 DEFERRED to change. Actual size = 4096, minimum size = 16384.
   CWMCB0350E: Database BPC172DB does not have defined a sufficient logfile size. Use UPDATE DB CFG FOR BPC172DB USING LOGFILSIZ 16384 DEFERRED to change. Actual size = 4096, minimum size = 16384.

3. On the database computer, upgrade all schemas. To see which schemas are upgraded, go to the directory where you copied the Upgrade folder and see the upgradeSchemaScriptsHelp_de_name.txt file.

   Go to the directory where you copied the Upgrade folder and run the upgradeSchemaAll command. There is a different upgradeSchemaAll command for each deployment environment in the source.

   upgradeSchemaAll_de_name.bat

   You are prompted to enter the user name and password for each database connection. The command initializes the new database components and upgrades the schemas of all the existing databases. When you are asked if shared work items are enabled for Business Process Choreographer, refer to the note in the next step to see whether shared work items are enabled.

   Alternatively, if you want to run the SQL scripts manually, use an SQL session and run the scripts in the sequence listed in the Upgrade_folder\upgradeSchemaScriptsHelp_de_name.txt file and use the following parameters and commands.

   db2 -s -t -v -z log name  -f  script_name

   where:
   • -s specifies that the script is to exit as soon as the first error occurs
   • -t specifies that the statement is to be printed on the command line so that it can be logged in a log file
   • -v specifies that the output from the command is to be sent to a log file that can be used for error checking
   • -z specifies that the semicolon (;) is to be treated as a delimiter for the commands in the file
   • -f specifies the input file name
   If you see an error while upgrading the Business Process Choreographer Archive database, see the reference topic for instructions.
   Note: If your source environment is V7.0.0.3 or V7.0.0.4 or later minor versions, two versions of upgrade schema scripts are generated for the BPC database. If you create a new Business Process Choreographer configuration with a newly created database, shared work items are enabled and used automatically. If you migrated your Business Process Choreographer configuration, using shared work items is optional. If you have enabled the "Shared Work Items" feature that was introduced in V7.0.0.3, you must remove those generated scripts with "700" in the file name before you run upgradeSchema.bat. If that is not the case, you must remove the script with "7003" in the file name.

   For detailed information about shared work items, refer to Shared work items.

   You might see warning messages when you run the scripts to upgrade the Business Space database telling you that the result of a query is an empty table or that no row was found for FETCH, UPDATE, or DELETE. These messages can safely be ignored.

   The result.log files are found in Upgrade_folder\cell_name or cell_name.de_name\database_type\database_name.schema_name.

4. 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:

   • source.application.cluster.name
   • source.messaging.cluster.name
   • source.support.cluster.name
   • source.web.cluster.name
5. To upgrade the topology data in the database to V8.6.0, run the DBUpgrade utility:
   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.bat -propertiesFile target_migration_properties_file -backupFolder snapshot_folder

   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.
   • snapshot_folder is the directory that contains the information that was extracted from the source environment
   For example:

   install_root\bin\DBUpgrade.bat -propertiesFile "C:\BPM V8.6.0\util\migration\resources\target_migration.properties" -backupFolder C:\snapshot

   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.

   For troubleshooting, the DBUpgrade command has new parameters in V8.5.7 CF2016.09. If necessary, 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. If you did not increase the default log file size, increase it by using the following SQL statement, where @DB_NAME@ is the name of your Process Server database.

   UPDATE DB CFG FOR @DB_NAME@ USING LOGFILSIZ 16384 DEFERRED;