Upgrading Oracle databases

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.

The details of the diagram are provided in the figure caption.

Run the DBUpgrade command to modify your existing database schemas and data for use with IBM Business Process Manager V8.5.6. The DBUpgrade utility updates the following items to V8.5.6:

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.6, it does not automatically update existing dependencies. The dependencies must be updated after migration.

The DBUpgrade utility also converts encrypted passwords to work with the encryption algorithm used by IBM Business Process Manager V8.5.6. Encrypted passwords can be stored in the database for secure web service integrations users.

Note: Encrypted passwords can be stored in the database for Microsoft SharePoint integrations users.

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.6.

The CONNECT, RESOURCE, DBA_TABLES, and SELECT privileges are required on the database level.
The upgrade process accesses system views. Grant the SELECT privilege to the user who performs the upgrade. These privileges are already granted to the public group by default; it is not necessary to grant them again unless they were revoked.
```
all_indexes
all_tables
USER_TAB_COLUMNS
all_objects
all_constraints
all_tab_columns
```

Tip: If you use tablespaces with a UNIFORM SIZE less than 120K, create new tablespaces with the AUTOALLOCATE option and make it the default tablespace for IBM BPM database schema users. Otherwise, you will see an error similar to the following error when you upgrade the schema:

Executing upgrade step: Upgrade 8.5.0 schema to 8.5.5 for database ProcessServerDatabase.
Error executing SQL statement: ORA-60019: Creating initial extent of size 14 in tablespace of extent size 8

On Oracle, IBM Business Process Manager stores large objects (LOBs) with the SECUREFILE option. For SECUREFILE, it is recommended to use a tablespace with the AUTOALLOCATE option. If you use UNIFORM SIZE extents, ensure that the UNIFORM SIZE is big enough. Given the default block size of 8K, specify a UNIFORM SIZE of at least 120K. IBM BPM does not explicitly prescribe the tablespace options; it relies on the default Oracle settings (such as AUTOALLOCATE) to automatically manage extents.

For a list of supported database versions, refer to the system requirements.

Procedure

Based on your source environment and the location of the target environment, perform the following step:

Current® version of IBM Business Process Manager Standard or WebSphere® Lombardi Edition	File system where IBM BPM V8.5.6 is to be installed	Steps to take
WebSphere Lombardi Edition 7.1.0 that is previously upgraded from Teamworks® 7.0.0 or 7.0.1 WebSphere Lombardi Edition 7.2.0 that is previously upgraded from Teamworks 7.0.0 or 7.0.1 to WebSphere Lombardi Edition 7.1.0 and then upgraded to WebSphere Lombardi Edition 7.2.0	Same file system as the existing WebSphere Lombardi Edition installation	In the `installation_root`/util/DBUpgrade directory, modify the `upgrade.properties` file to set the value of the `previous.lombardi.install.dir` property to be your source environment installation directory. Note: If this property is missing or not valid, the upgrade script is unable to migrate encrypted passwords, but can still perform other upgrade processing.
WebSphere Lombardi Edition 7.1.0 that is previously upgraded from Teamworks 7.0.0 or 7.0.1. WebSphere Lombardi Edition 7.2.0 that is previously upgraded from Teamworks 7.0.0 or 7.0.1 to WebSphere Lombardi Edition 7.1.0 and then upgraded to WebSphere Lombardi Edition 7.2.0	Different file system from the existing WebSphere Lombardi Edition installation	If `[Lombardi_home_710]/AppServer/lib/ext/jcrypt.jar` or `[Lombardi_home_720]/AppServer/lib/ext/jcrypt.jar` is present in your installation, copy it to `installation_root/AppServer/lib/ext`

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.bat
```
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.

The result.log files are found in Upgrade_folder\cell_name or cell_name.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 install_root\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.6, 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.
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.
```
install_root\bin\DBUpgrade.bat -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.bat -propertiesFile "C:\bpm 85\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.

V8.5.6 no longer supports the Lombardi database user registry. Users that were maintained by the Lombardi database user registry are moved to the WebSphere Application Server file-based user registry. After migration, you can maintain these users in the WebSphere Application Server administrative console.

The utility updates existing schemas and migrates data. If you previously upgraded to WebSphere Lombardi Edition 7.1.0 or WebSphere Lombardi Edition 7.2.0 from Teamworks 7.0.0 or 7.0.1, the script also converts encrypted passwords to work with IBM Business Process Manager V8.5.6.

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.