For Oracle, 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
your existing database schemas and data for use with
IBM Business Process Manager V8.5.5. The
DBUpgrade utility
updates the following items to
V8.5.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.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 Oracle database to a supported version. If your
Oracle database is at 9i or 10g, upgrade it to 11g before migration.
Verify
that the users that are configured to access your Oracle databases
have the necessary privileges to upgrade the databases. The following
database privileges are needed to modify existing Oracle database
schemas and data for use with
IBM Business Process Manager V8.5.5.
For
a list of supported database versions, refer to the system requirements.
Procedure
For each deployment environment that
you are creating, complete the following steps:
- Copy the whole folder target_deployment_manager_profile/dbscripts/Upgrade/ to
your database computer.
- 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.
- 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.sh
You are prompted to enter the user name and
password for each database connection. This command initializes the
new database components and upgrades the schemas of all the existing
databases except for the Process Server and Performance Data Warehouse
databases. Those two databases are upgraded later by the DBUpgrade command. 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.
The options are embedded in the SQL scripts. Additional options are
not required.
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 de_name/database_type/database_name.schema_name.
- 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 BPM_home_8.5/util/migration/resources/migration.properties.
Ensure that all properties have been changed
to the target (not source) 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 to the name of the new
deployment manager profile.
- To upgrade the databases to V8.5.5, run
the DBUpgrade utility on the deployment manager
computer in the target environment. The DBUpgrade command
automatically upgrades the schema and data for Process Server and
Performance Data Warehouse and updates the topology information in
the Business Process Choreographer database.
Tip: By default, DBUpgrade upgrades
both the schema and data for Process Server and Performance Data Warehouse
databases. For instructions for running the schema update separately,
see the DBUpgrade command-line utility reference
topic.
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 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:
BPM_home/bin/DBUpgrade.sh -propertiesFile /opt/BPM85/util/migration/resources/target_migration.properties -backupFolder /tmp/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.
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.
Open the DBUpgrade.sh file in BPM_home/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.
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.