Step 1: Creating Decision Warehouse database resources

You can use SQL scripts to create a dedicated schema in the database.

If you set the Rule Execution Server persistence to datasource or jdbc and you intend to use Decision Warehouse to store your test execution results, you must create a dedicated schema in the database that contains these tables and views. To do so, you can use the provided SQL scripts, located in <ODM_InstallDir>/executionserver/databases. A readme file in this directory provides additional information about the scripts.

The script that creates the Decision Warehouse database schema is named trace_<database_name>.sql.

Note:

The Installation Settings wizard in the Rule Execution Server console creates all the necessary tables for Rule Execution Server and for Decision Warehouse. If you are configuring Decision Validation Services and you have already run the Installation Settings wizard to create the tables, you do not have to create database resources manually. However, if you did not use the wizard to create database resources, you must run the script to create the Decision Warehouse database schema.

When you use DB2 (except on z/OS), the scripts that create the Rule Execution Server database tables are written for databases that use automatic storage.

BP32K is the buffer pool that is expected in SYSCAT.BUFFERPOOLS. If BP32K is not there, you can use the existing buffer pool or create a new buffer pool named BP32K. Use the following command to query SYSCAT.BUFFERPOOLS for the existing buffer pool:
```
Select * from SYSCAT.BUFFERPOOLS
```
Otherwise, use the following command to create a buffer pool named BP32K:
```
CREATE BUFFERPOOL BP32K SIZE 2000 PAGESIZE 32K
```
You must update the trace_db2.sql script and select the custom option in the Installation Settings wizard to run it. Modify the following line in the script to specify storage for the table space:
```
CREATE TABLESPACE RESDWTS PAGESIZE 32K BUFFERPOOL BP32K;
```
Here is an example of the table space specification in the script:
```
CREATE TABLESPACE RESDWTS PAGESIZE 32K  MANAGED BY Database 
USING [ FILE 'C:\DB2\Container.file' 640 ] BUFFERPOOL  BP32K;
```
You might have to further modify the script based on your database settings.

Note:

If you completed this task as part of the Rule Execution Server configuration, you do not have to do this a second time. It is included here solely for completeness.

If you use Command Editor to run the scripts, you must log in with the credentials that you use for the data source for Rule Execution Server.

Use any tool that can handle SQL to import and run the SQL scripts. The tools provided for each database include:

Database	Database tool
IBM DB2	DB2 command line processor
Derby	ij command line processor
MySQL	mysql command line processor
Oracle	sqlplus command line processor
Postgre SQL	Postgre SQL command line tool
SQL Server	Query Tool
Sybase	isql command line processor

To access the database, the database user must have the following credentials:

A user ID and a password
Complete privileges on the tables and view of the schema (create, insert, delete)
create index privileges
On Oracle, create trigger and create sequence privileges. If you use an Oracle database, run all the scripts in the SQL Plus client.

Install a database client for the database that you use. Refer to the documentation of the database for more information.

The default CLOB size might not be sufficient for the FULL_EXECUTION_TRACE field in the EXECUTION_TRACES table. You might need a size qualifier if SQL raises exceptions with the <Lob-Value> reason code.