For Oracle, 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. 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 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.
For
a list of supported database versions, refer to the system requirements.
Procedure
- 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 Configuring new Oracle
database components for the list of scripts that you generated.
Run the SQL scripts.
- Run the SQL scripts.
Note: The Process and Performance Data Warehouse
database upgrade scripts do not need to be run manually, because they
will be invoked by the DBUpgrade command.
Use one of these methods to run the scripts:- Run the SQL scripts using the upgradeSchema.bat 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.
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.
- 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.bat -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
For example:
BPM_home\bin\DBUpgrade.bat -propertiesFile "C:\bpm 85\util\migration\resources\migration.properties" -backupFolder C:\snapshot
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
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.