IBM Tivoli Monitoring, Version 6.3

DB2 warehouse database procedure

  1. Stop all running Warehouse Proxy agent instances and the Summarization and Pruning agent.
  2. Back up your warehouse database.
  3. Copy the scripts from the Tivoli Enterprise Portal Server in one of the following directories to a temporary directory on the system where the warehouse database is located:
    • Windows:
      install dir\CNPS\SQLLIB\WAREHOUSE\DB2
    • UNIX and Linux:
      install dir/arch/cq/sqllib/WAREHOUSE/DB2
  4. On the system where the warehouse database is located, change to the directory where you placed the script files in Step 3. Then, connect to the warehouse database through the DB2® command line with a user ID that has the authorization to alter and load tables and drop views. Run commands based on the following example to connect, set the schema, and save the script to an output file:
    db2 connect to WAREHOUS user ITMUSER using ITMPASS
    db2 set current schema="ITMUSER"
    db2 -tv -z log/script.sql.log -f script.sql
    These parameters are used in the example:
    • WAREHOUS is the database name.
    • ITMUSER is the user name used by the Warehouse Proxy agent.
    • ITMPASS is the password used by the Warehouse Proxy agent.
    • script.sql is the name of the script file. See Table 1 for the script file names.
    • script.sql.log is the name of the output file.
    Notes: You might receive error messages such the following from DB2:
    • SQL0204N "schema name.table name" is an undefined name. SQLSTATE=42704

      This message indicates that the table named table name does not exist and cannot be altered or dropped. This happens if you do not have warehousing or summarization enabled for the given table. For example if you only have hourly and daily summarization enabled, you see this message for the weekly, monthly, quarterly, and yearly summarization tables because these tables do not exist.

    • SQL3304N The table does not exist.

      This message indicates that the table does not exist and cannot be loaded. This happens if you do not have warehousing or summarization enabled for the given table. For example if you only have hourly and daily summarization enabled, you see this message for the weekly, monthly, quarterly, and yearly summarization tables because these tables do not exist.



Feedback