For DB2 for z/OS databases, increase the buffer size for table
spaces and upgrade your existing schemas and data.
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 your existing database
schemas and data for use with
IBM® Business Process Manager
V8.5. The
DBUpgrade
utility updates the following items to
V8.5:
- System Data toolkit
- Process Portal process application
- Hiring Sample tutorial process application
Note: Although the DBUpgrade utility updates the System Data toolkit to
IBM Business Process Manager
V8.5, it does not automatically update
existing dependencies. The dependencies must be updated after migration.
Before you begin
Ensure that you have shut down the source environment
before you proceed with the migration.
Important: You
must upgrade your DB2 for z/OS database to a supported version. If
your DB2 for z/OS database is at V7 or V8, upgrade it to DB2 for z/OS
V9 or V10 before migration.
Verify that the users that are configured
to access your DB2 for z/OS databases have the necessary privileges
to upgrade the databases. The following minimum database privileges
are needed to modify existing DB2 for z/OS database schemas and data
for use with
IBM Business Process Manager V8.5.
For
a list of supported database versions, refer to the system requirements.
Procedure
- For Process and Performance Data Warehouse
databases, complete the following steps for your DB2 for z/OS database:
- 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:
For information about altering table spaces, see
- From the target_deployment_manager_profile/dbscripts/Upgrade/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.
Note: If you are migrating from IBM Business Process Manager V7.5.x
or IBM Business Process Manager 8.x,
locate the two CREATE PROCEDURE statements in the upgradeSchema75x_ProcessServer.sql or upgradeSchema80x_ProcessServer.sql script,
and cut and paste these statements into a new text file with a .sql extension.
In this new file, also include the DB2 --#SET TERMINATOR @ control
statement to set the SQL terminator to the @ character, as required
for stored procedures. Save your amendments to the .sql scripts.
Connect
to the DB2 for z/OS database, and run the upgradeSchema75x_ProcessServer.sql or upgradeSchema80x_ProcessServer.sql script
against the database by using your preferred tool. Then, run the newly
created .sql script to create the stored procedures.
- From the target_deployment_manager_profile/dbscripts/Upgrade/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 IBM Business Process Manager 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 upgradeSchemaPerformanceDW.sql script
against the database by using your preferred tool.
- 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 migrating from IBM BPM
Standard V8.x,
complete the following steps for the Business Space database:
- Copy the upgrade SQL scripts
that you generated by running the BPMGenerateUpgradeSchemaScripts utility
from target_deployment_manager_profile/dbscripts/Upgrade to
your database computer. See Generating SQL scripts
for DB2 for z/OS and configuring new database components for
the list of scripts that you generated. Run the SQL scripts.
- Ensure that the copied scripts
have write permissions. If the tool that you want to use to view,
edit, and run the scripts requires the scripts to be in EBCDIC format,
rather than ASCII format, convert the files to EBCDIC.
Important: After you convert the files from ASCII to EBCDIC,
check that no SQL statements exceed 72 characters in length, and fix
if necessary. Longer lines can lead to line truncation and invalid
statements when you run the scripts.
- Connect to the database and run
the customized scripts against the database by using your preferred
tool; for example, the DB2 command line processor, SPUFI, or in a
batch job.
You can also use one of these methods to
run the scripts:
- Run the SQL scripts using the upgradeSchema.sh file
that was generated along with the SQL scripts.
- Run the SQL scripts directly using an SQL session.
To run the SQL scripts directly, run
the scripts in the following sequence:
- Run all upgradeTablespac* scripts before
you run any upgradeSchema* scripts.
- Run the upgradSchema_SchemaStatus.sql script
before you run any other "upgradeSchema*" SQL scripts.
The options are embedded
in the SQL scripts. Additional options are not required.
Note: If you
had the Business Process Choreographer Reporting function configured,
it was removed during runtime migration. However, the associated data
was not automatically removed from the database. If you determine
that you no longer need this data, run the dropSchema_Observer.sql script
and then the dropTablespace_Observer.sql script using
an SQL session with special configuration.
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.
- Go to the target_BPM_home/util/dbUpgrade directory and set the database.is.db2zos property
to true in the upgrade.properties file. For example:
database.is.db2zos=true
- To upgrade the databases to V8.5, 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.
BPM_home/bin/DBUpgrade.sh -propertiesFile migration_properties_file -backupFolder snapshot_folder
where:- migration_properties_file is
the full path to the migration properties file in which you specified
the configuration information for the target environment. Ensure that
the value of the target.config.property.file property
is set to the full path of the configuration properties file that
you used to create your target environment. You must also set the
value of profile.name.
- snapshot_folder is the directory that contains
the information that was extracted from the source environment
If you are migrating from 7.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,
or decrease the value of database.batch.size (the
size of the records to be updated as a batch) in the following file: BPM_home/util/dbUpgrade/upgrade.properties.
This example shows how to change the heap size of the JVM for the DBUpgrade command:JVM_HEAPSIZE_OPTIONS="-Xms512m -Xmx768m"
$JAVA_EXE $JVM_HEAPSIZE_OPTIONS -cp $CLASSPATH
For example:
BPM_home/bin/DBUpgrade.sh -propertiesFile /opt/BPM85/util/migration/resources/migration.properties -backupFolder /tmp/snapshot
What to do next
You might see warning messages
similar to the following in the upgrade log: Couldn't load
Resource META-INF*****. These messages can safely be ignored.