Running the generated Oracle database scripts

If you run the BPMConfig command with the property bpm.de.deferSchemaCreation set to true, or if you used the Deployment Environment wizard and cleared the Create Tables option, you must run the generated database scripts manually to create the database tables.

Before you begin

Before you begin this task, you must have run the BPMConfig command or the Deployment Environment wizard to generate the correct SQL scripts. You also need to have created the required database users using the generated createUser.sql scripts.

If the bpm.de.deferSchemaCreation property is set to false, or if you used the Deployment Environment wizard and did not clear the Create Tables option, the SQL scripts used to create the database tables are automatically run when you create the deployment environment.

About this task

The database SQL scripts are generated in the dmgr_profile_name/dbscripts folder by default. This folder includes the following sub-folder:

cell_name.deployment_environment_name - For each deployment environment, this folder will contain the SQL files that need to be run.

Procedure

Locate the generated SQL scripts.
A default configuration for a Standard deployment environment with Oracle databases contains the following sub-folders and SQL scripts:
- cell_name.deployment_environment_name
  - Oracle
    - orcl
      cmnuser
      createSchema_Standard.sql
      
      createSchema_Messaging.sql
      
      psuser
      createSchema_Standard.sql
      
      createProcedure_Standard.sql
      
      pdwuser
      createSchema_Standard.sql
In the above example, orcl is the Oracle instance, cmnuser is the deployment environment-level user, psuser is the Process Server user, and pdwuser is the Performance Data Warehouse user.

Run the scripts to apply the schema to the CMNDB.

For example, use the following commands to run the scripts manually for a deployment environment-level Common database configuration:

sqlplus cmnuser/cmnpassword@orcl @BPM_HOME/profiles/DmgrProfile/dbscripts/cell_name.deployment_environment_name/Oracle/orcl/cmnuser/createSchema_Standard.sql

sqlplus cmnuser/cmnpassword@orcl @BPM_HOME/profiles/DmgrProfile/dbscripts/cell_name.deployment_environment_name/Oracle/orcl/cmnuser/createSchema_Messaging.sql

Run the scripts to apply the schema to the BPMDB.

For example, use the following commands to run the scripts manually for the Process database configuration:

sqlplus psuser/pspassword@orcl @BPM_HOME/profiles/DmgrProfile/dbscripts/cell_name.deployment_environment_name/Oracle/orcl/psuser/createSchema_Standard.sql

sqlplus psuser/pspassword@orcl @BPM_HOME/profiles/DmgrProfile/dbscripts/cell_name.deployment_environment_name/Oracle/orcl/psuser/createProcedure_Standard.sql

Run the scripts to apply the schema to the PDWDB.
For example, use the following commands to run the scripts manually for the Performance Data Warehouse database configuration:
```
sqlplus pdwuser/pdwpassword@orcl @BPM_HOME/profiles/DmgrProfile/dbscripts/cell_name.deployment_environment_name/Oracle/orcl/pdwuser/createSchema_Standard.sql
```

What to do next

You must now run the bootstrap utility to load configuration data for the IBM® Business Process Manager applications into the Process database. This data is required for the applications to run correctly.