These instructions assume that you are using DB2 Universal Database and guide you through the following tasks:
Note. When you create and access the DATAWAREHOUSE table, be aware of the following issues:
Complete the following steps:
On Windows:
You must replace install_dir with the path to your DB2 product installation directory, such as C:\PROGRA~1\IBM\SQLLIB. You can find this location by using the db2level command:CREATE DB USERDB CONNECT TO USERDB BIND 'install_dir\bnd\@db2cli.lst' blocking all grant public TERMINATE
On Linux:
You must replace install_dir with the path to your DB2 product installation directory. You can find this location by using the db2level command:CREATE DB USERDB CONNECT TO USERDB BIND install_dir/bnd/@db2cli.lst grant public CLIPKG 5 TERMINATE
db2start
db2 -vf datawarehouse1.sql
CONNECT TO USERDB DROP TABLE DATAWAREHOUSE CREATE TABLE DATAWAREHOUSE ( MESSAGEDATA BLOB (1 M ) NOT NULL , PUTTIMESTAMP TIMESTAMP NOT NULL , DBINSERTTIMESTAMP TIMESTAMP NOT NULL WITH DEFAULT CURRENT_TIMESTAMP ) TERMINATE
db2 -vf datawarehouse2.sql
Wait for the script to finish running. If you are running the script for the first time, the following message is displayed, where DB2ADMIN is your user name:
DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0204N "DB2ADMIN.DATAWAREHOUSE" is an undefined name. SQLSTATE=42704Ignore this message. The message is displayed because the script attempts to remove an existing table called DATAWAREHOUSE before it creates a new table, but if you have not run the script before, the script cannot find the existing table.
For instructions, see Enabling ODBC connections to the databases in the WebSphere Message Broker documentation.