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 Common database
Use this procedure to upgrade the Common database schema.
The Common database is cell-scoped. Therefore, when a deployment target such as a server, cluster, or non-clustered managed node in the cell is migrated to IBM BPM V8.0.1, the database must also be migrated. In a mixed-version cell environment, this might result in pre-V8.0.1 servers, clusters, and non-clustered managed nodes using the same instance of the database as V8.0.1 servers, clusters, and non-clustered managed nodes.
If the database user configured for the Common database has the required permissions, the Common database is automatically updated as part of starting the server. Otherwise, you must upgrade the Common database schema manually.
For the Common database upgrade scripts, the following permissions are required:
- CREATE TABLE
- ALTER TABLE
- DROP INDEX
- CREATE INDEX
- CREATE VIEW
- DROP VIEW
- CREATE SEQUENCE
Procedure
The Common database is automatically updated as part of starting the server if the database user configured for the Common database has the required permissions. To upgrade the Common database schema manually, follow the instructions in Manually upgrading the product databases.
You can choose to upgrade the Common database schema manually even if the database user configured for the Common database has the required permissions.
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