![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
You should update the schema whether or not you are interested in the fixes for the defects which are affected by the schema changes. Read the following section to determine whether to update the inventory schema.
The fix pack install will place files named inv_<db>_schema.sql, inv_<db>_upgrade_42.sql, inv_<db>_patch1.sql, inv_<db>_FP01.sql and inv_<db>_FP02.sql on the managed nodes where the patch is installed, in the following directory:
$BINDIR/../generic/inv/SCRIPTS/RDBMS
where <db> is the shortname for the database. For each of these scripts, there is also a history equivalent script for updating the history tables, and these scripts have the same names with a "h_" prefix.
All of these scripts allow you to either update or reinstall your database schema.
If you have already run the full schema scripts (inv_<db>_schema.sql or inv_<db>_upgrade_42.sql) and you wish to preserve your existing data, then you will just need to run the inv_<db>_FP01.sql and inv_<db>_FP02.sql scripts to update your database without losing any data. See APARs IY46226 and IY40716 for additional information regarding the fix pack scripts. If you previously installed 4.2-INV-FP01 and applied the associated FP01 scripts, then you will just need to run the FP02 scripts.
You will need to copy the appropriate schema scripts to any system where SQL access is available (such as the database server or the database client machine if the client allows for SQL connectivity) to install the schema scripts.
DB2 only: Create the temporary tablespace "usertemp1" by running the inv_db2_admin_patch.sql script as a DB2 administrator. If you are installing a new DB2 database and using the inv_db2_admin.sql script, you do not need to run the patch script as it is now contained in the latest version of the admin script.
DB2 and Informix only: Run the inv_<db>_FP01.sql, inv_<db>_FP02.sql, and inv_<db>_FP04.sql scripts as a DB2 inventory user.
Notes for all Database Scripts: You may notice error or information messages displayed when running the database scripts. Each database has unique behavior, so some messages may be expected.
You should run a "Replace with Current Results" scan when scanning a new endpoint and after installing a new schema.
This section contains additional information from APAR IY40716.
The following differences were noted in the SQL scripts used to upgrade Inventory, Version 4.0 to 4.2 compared to the SQL scripts used for a version 4.2 fresh install:
The fresh install and patch1 scripts were changed in order to remove the differences.
The following paragraphs describe how to update your schema.
If you ran the version 4.2 fresh install scripts when creating the Inventory, Version 4.2 schema, you need to run the (h_)inv_xxx_FP02.sql scripts.
If you migrated your schema from version 4.0 to 4.2 with the patch1 and upgrade scripts, you need to run the updated (h_)inv_xxx_patch1.sql scripts.
If you migrated your schema from version 4.0 to 4.2 with just the upgrade scripts (that is, you did not run the patch1 scripts because your version 4.0 environment was already at the 4.0-INV-FP01 or later schema level), you do not need to run any schema scripts for this APAR.
[ Top of Page | Previous Page | Next Page | Contents ]