Verifying a fix pack installation

After successfully completing the fix pack installation, you must complete verification activities, which include checking that the postinstallation conditions of your system are properly set.

Before you begin

Note: Due to the console removal as part of fixpack V1.1.0.2, this topic is only valid for fixpack V1.1.0.1 and earlier. For later fixpacks refer to the PureData System for Operational Analytics fix pack readme documents associated with that fixpack.

Successfully complete the entire fix pack installation process. See: Installing a fix pack.

About this task

Resolve any issues by calling IBM Support.

Procedure

Complete the following steps to verify the installation of a fix pack on your system:

In the Fix Packs list, check that the Status column has a value of Committed.
To see the list of committed fix pack components, click the fix pack link in the Fix Packs panel.
Navigate to System > Events and use the following filters to view and assess system events that might require action:
1. Set Severity to Fatal, Critical, Major, Minor, Warning.
2. Set Category to Alert, then click Refresh and view the events.
3. Change Category to Call support, then click Refresh and view the events.
4. Change Category to Customer serviceable, then click Refresh and view the events.
Check that the core warehouse database is up and running by using the database performance monitor in the system console.
Verify that all the IBM® Tivoli® System Automation for Multiplatforms (Tivoli SA MP) resources are online.
1. Log in to the management host as root.
2. Issue the hals command.
3. Verify that all the Tivoli SA MP resources in the core warehouse have an OPSTATE value of Online and an HA STATUS value of Normal.
4. Verify that all the Tivoli SA MP resources on the management host have an OPSTATE value of Online and an HA STATUS value of Normal.

The following step must be run on the administration host as the core warehouse instance owner or another database user that has rebind privileges on the database.

Manually rebind all of the DB2® packages on all of the core warehouse databases. After you install a fix pack, some packages are marked as invalid. Packages marked as invalid are implicitly rebound the first time an application uses them. To eliminate this overhead and to ensure that the rebind is successful, manually rebind all of the packages by running the following command:
```
db2rbind dbname -l logfile_name all
```
where dbname represents the name of a core warehouse database, and where logfile_name represents the name of the log file to be used for recording any errors during the package revalidation procedure. An example of a time stamped log file name that you can specify is db2rbind_$(date +%s).log.
Monitor your system for a reasonable time to verify that your system and your mission-critical applications are running correctly.

What to do next

If you installed the fix pack on your test system and verified that the installation was successful, install the fix pack on the production system by repeating the entire fix pack installation process.

Enable your backup strategy if it was disabled before you began the fix pack installation process.

Back up your core warehouse database again. This database backup ensures that you can restore your core warehouse database to the recently installed fix pack level. You can use the cold data method of local disk storage on the /bkpfs file system. See: Multi-temperature data management guidelines.

Resume normal operations.