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 need to update the Inventory schema.

This fix pack installation places files named inv_dbvendor_schema_423_FP03.sql and h_inv_dbvendor_schema_423_FP03.sql on the managed nodes where the patch is installed, in the following directory:

$BINDIR/../generic/inv/SCRIPTS/RDBMS 

where dbvendor is the shortname for the database.

If you have already installed and configured the previous fix packs, you do not need to run the

scripts again.

For instance, if you use DB2(R) and install this fix pack over a 4.2.3 GA Version you need to run the following scripts:

If you have already run one of these scripts because you have already installed the related fix pack, you do not need to run it again.

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 for SQL connectivity) to run the schema scripts.

During the running of the scripts, temporary copies are made of information held in MATCHED_SWARE, SIG_PACKAGE, and SIGS_MAP tables. If the tables, particularly MATCHED_SWARE, the inventory temporary table space might not be sufficient. During testing on a database with 20000 endpoints and 400000 entries in the MATCHED_SWARE table, the inventory temporary tablespace variable inv_temp_ts was increased from the default value of 10 MB to 100 MB. In addition, the size of the transaction log for INV_DB was increased to 50 MB. Take this into consideration when preparing to run the scripts.

Notes:
  1. With DB2 7.2: if an error occurs when running the inv_db2_schema_423_FP02.sql script, increase the application heap size with the following command:

    db2 update db cfg for <inv_db_name> using applheapsz 256

    Then rerun the first instruction in the inv_db2_schema_423_FP02.sql file:

    alter table COMPUTER alter column OS_NAME set data type varchar(128);

  2. If you are running a customizable script in an MVS(TM) environment (inv_db2_mvs_<cm version>_<fix pack level>.sql), some variables can be customized. For information about the variables, refer to the header information in the inv_db2_mvs_admin.sql script.
  3. Error or information messages might be displayed when running the database scripts. Each database has unique behavior, so some messages can be expected .
  4. When you run the inv_db2_mvs_custom_423_FP02.sql script the alter table NATIV_SWARE alter column PACKAGE_NAME set data type varchar(128) instruction might not alter the NATIV_SWARE table. To avoid this problem you must perform the following steps:
    1. Backup the table and the related views
    2. Delete the table and all related views
    3. Recreate table and related views

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