IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from previous versions > Migrating your IBM BPM Advanced V7.5.x or WebSphere Process Server V7.x or V6.2.x runtime > Runtime migration subprocedures > Migrating databases
Migrating the Business Process Choreographer database
Use this procedure to upgrade the Business Process Choreographer database schema.
The Business Process Choreographer database is deployment-target scoped. This database can be configured at a server or cluster scope.
If this database is configured in a mixed-version cell environment, each server, cluster, or non-clustered managed node has a unique instance of the database, and each instance has schema and data that are unique to that version of the product. When each server, cluster, or non-clustered managed node is migrated, its unique instance of the database is migrated as part of the runtime migration procedure.
The database user that is configured for the BPEDB data source is not authorized to perform all of the following operations:
- Create and alter tables
- Create and drop indexes and views
- Query, update, delete, and insert (for the table SCHEMA_VERSION)
For the Business Process Choreographer database upgrade scripts, the following permissions are required:
- To run the upgradeTablespaces SQL script for DB2 for Linux, UNIX, or Windows:
- CREATE BUFFERPOOL
- CREATE TABLESPACE
- To run the upgradeTablespaces SQL script for DB2 for z/OS:
- CREATE TABLESPACE
- To run the upgradeSchema SQL script for all databases:
- CREATE TABLE
- ALTER TABLE
- DROP INDEX
- CREATE INDEX
- CREATE VIEW
- DROP VIEW
Procedure
Automatic upgrade is not supported. To upgrade the Business Process Choreographer database schema manually, follow the instructions in Manually upgrading the product databases.
Related tasks:
Migrating a stand-alone environment
Migrating an ND environment with full downtime
Migrating an ND environment with minimal downtime
Manually upgrading the product databases