IBM Tivoli Software IBM Tivoli Software

[ Bottom of Page | Previous Page | Next Page | Contents ]


Updating the inventory schema

When you install a new fix pack, you must update the Inventory schema.

A fix pack does not necessarily contain fixes on SQL scripts and, if present, these fixes do not necessarily apply to all database vendors.

Table 13 lists the SQL scripts to run for updating the Inventory schema:

Table 13. SQL scripts for updating the Inventory schema
Oracle DB2 MSSQL Sybase Informix DB2 MVS DB2 MVS custom

inv_db_431_FP01.sql

X X X X X X X

Table 14 lists the SQL scripts to run for updating the Historical Inventory schema:

Table 14. SQL scripts for updating the Historical Inventory schema
Oracle DB2 MSSQL Sybase Informix DB2 MVS DB2 MVS custom

h_inv_db_431_FP01.sql

X X X X X X X

Copy the appropriate schema scripts to any system where SQL access is available, such as the database server or the database client workstation if the client allows SQL connectivity, to run the schema scripts.

Notes:
  1. Error or information messages might be displayed when running the database scripts. Each database has unique behavior, so some messages can be expected.
  2. The inv_db2_mvs_custom_*.sql script might contain some customizable variables such as: Descriptions for these variables can be found inside the inv_db2_mvs_admin.sql script.

For example, if you use DB2 and install this fix pack to update the Inventory schema, refer to the DB2 column of Table 13 and run the scripts identified in the table rows by X in the order specified:

  1. inv_db2_431_FP01.sql
  2. h_inv_db2_431_FP01.sql
Note:
SQL scripts delivered with fix packs might alter the existing tables or columns, if you created materialized queries or views. Depending on the tables modified by the fix pack SQL scripts, the following error might occur for DB2 (and a similar error for other RDBMS vendors):
SQL0270N  Function not supported (Reason code = "21").  SQLSTATE=42997
The error indicates dependency on MQT as explained below:
21 A column cannot be dropped or have its length, data type, or
 nullability altered on a table which is a base table for a
 materialized query table.                                      
To fix this problem, perform the following actions:
  1. Drop the dependent materialized query table or tables.
  2. Drop the column of the base table, or alter the length, data type, or nullability of this column.
  3. Recreate the materialized query table or tables.

[ Top of Page | Previous Page | Next Page | Contents ]