Creating the warehouse database on Oracle

This section provides guidelines for creating the Tivoli® Data Warehouse database on Oracle.

For specific instructions on how to create an Oracle database, see the Oracle documentation or have a database administrator create the database for you.

When you create the warehouse database using Oracle, follow these guidelines:

• Use the Unicode character set (AL32UTF8) when creating the database.
• Create a database user login name and password that the warehousing components (portal server, Warehouse Proxy Agent, and Summarization and Pruning Agent) can use to access the data warehouse. In these instructions, this user account is referred to as the warehouse user.
• Use the default values shown in the following table for the warehouse name and warehouse user. The default values are used in the configuration procedures for connecting the warehousing components to the warehouse database.

  Table 1. Default values for Tivoli Data Warehouse parameters

  Parameter	Default value
  Tivoli Data Warehouse database name	WAREHOUS
  User name	ITMUser
  User password	itmpswd1

• Create an ITM_DW role, and give this role the following permissions:

  GRANT CREATE CONNECT TO ITM_DW;
  GRANT CREATE PROCEDURE TO ITM_DW;
  GRANT CREATE TABLE TO ITM_DW;
  GRANT CREATE VIEW TO ITM_DW;

  After you create the warehouse user ID that will be used by the Warehouse Proxy and the Summarization and Pruning Agents to connect to the Tivoli Data Warehouse database, give this user ID the role you just created:

  CREATE USER itmuser PROFILE DEFAULT IDENTIFIED by itmuser_password 
  			ACCOUNT UNLOCK;
  GRANT role TO itmuser;

  As all the Tivoli Data Warehouse tables are created in the user's default tablespace, you need to allocate enough space quota on the default tablespace to this user to create all the tables, or you can simplify it by allowing unlimited tablespace to this user.
  Note: The ITM_DW role needs the connect privilege only if the database objects are created using the schema publication tool. If the historical configuration is changed and the warehouse user has limited privileges, the schema tool must be used to create any additional database objects (using the schema tool's updated mode; see Schema Publication Tool).
• Activate the Oracle listener using the Oracle Listener Service on Windows or the lsnrctl start command on Linux and UNIX.