HP Tru64 UNIX Version 5.1B-2 and Higher Patch Kit Installation Instructions (March 2009)

Phase 3 – Identifying Manually Installed Patches
Phase 3 reports patches that exactly match existing files on your system that are not marked as
installed by the system inventory. For example, in earlier kits, TruCluster software Release patches
were installed manually. This phase will report any manually installed Release patch files that
exactly match a patch contained in the current dupatch-based TruCluster software patch kit.
You can optionally enable dupatch to mark these patches as installed, which involves copying
valid setld database information to your system. The dupatch utility will copy the appropriate
patch_subset.inv, patch_subset.scp, and patch_subset.ctrl files into place for
these patches.
If you do not want to enable dupatch to mark these patches as installed, you must manually
remove the patched system files so the normal dupatch installation can install the affected
patches.
Phase 4 – Handling Missing or Unknown Files on Your System
Phase 4 reports information about any unknown and missing system files. These files should be
considered as intentional customizations which are important to correct system operation. As
such, care should be taken to understand why system files have been customized.
Before enabling any patch installations in Phase 5, review the information reported in Phase 4
against your log of manual system changes to ensure you understand why the system was
intentionally customized and to determine how to proceed. In some cases you may need to
remove customizations to ensure proper system operation.
To assist you in identifying the origin of changed system files, baselining now reports all missing
or unknown system files.
The following sections provide general guidance for some of the normal situations where system
files are intentionally customized manually.
Manually Installed CSPs
In response to a problem report, you may receive a manually installable CSP from your service
provider. CSPs are a set of compatible files that deliver fixes to the problems you reported.
Additionally, the patch may include instrumentation necessary for debugging purposes.
If your system was customized through a manual installation of CSPs, you must ensure that the
fixes delivered by the CSPs are included in the current Release Patch Kit before enabling dupatch
to overwrite any unknown or missing system files.
Warning!
If you are unsure if the CSP is included in the Release Patch Kit, do not enable dupatch to
overwrite the manually installed CSP. If you must install the Release patch being blocked by a
CSP, contact your service provider for assistance.
If the unknown or missing files are attributable to manually installed CSPs that are included in
a Release Patch Kit, perform one of the following steps:
• If all CSP files are overwritten by the patches noted in Phase 5, you can safely enable dupatch
to overwrite applicable missing or unknown system files.
• If some of the CSP files are not overwritten by the patches noted in Phase 5, contact your
service provider for assistance.
To determine if your CSP is included in the Release Patch Kit, refer to the Patch Summary and
Release Notes for the Release Patch Kit. See “Patch Process Resources” and “Related
Documentation” for information about viewing patch documentation on the Web.
Creating a Baseline 27