HP-UX 11i v3 Installation and Update Guide, March 2012

Table 15 Known install and update problems (continued)
Description/actionProblem
when the base page size is not 4K
or 8K
page size (BPS) is set to greater than the 8K value. The update failures were seen
on systems with the HP Integrity Virtual Machines (Integrity VM or HPVM) product
(VMKernelSW bundle versions B.04.00 and later) that automatically sets BPS to
64K. The failures might also occur on HP Integrity systems that have BPS set to 16K
or 64K values. The Tunable Base Page Size feature (introduced in September 2008
OE Update) enables these changes (see the base_pagesize(5) manpage). The
update from OE media might fail in one of two ways on systems with BPS > 8K:
1. A read error while reading filesets from the OE media, with a “Bad Address
(14)” wording in the error message. Installing PHKL_39114 will fix the read
error.
2. The update might hang while installing the filesets from the March 2009 OE
(or later) media. Installing PHKL_39114 will not fix this critical problem.
What to do
Before performing an update using the March 2009 OE (or later) media, install
patches PHKL_39509 and PHKL_39594 on HP Integrity systems (which fixes the
defect with the FS buffer cache on systems with the 64K base page size). The
patches can be installed from the HP-UX 11i v3 September 2009 (or later) media.
The system will reboot after installing these patches. After the system boots, you
can proceed with the update.
OR
If your kernel base page size (BPS) is set to larger than 8K, then set the BPS to 4K
before performing the update. After you have updated your system, return the BPS
to its former value.
For detailed notes on work-arounds and recovery steps, see QXCR1000907205
and QXCR1000868519 at the HP Support Center (http://hp.com/go/hpsc). Click
Search support knowledge, then select Search by document ID for your search
mode. Enter "ttr_na-SSB_1000907205” and "ttr_na-SSB_1000868519” in the
box.
If you ignite or update a system to an Operating Environment (OE) older than
March 2009 using a combined depot that also contains certain patches, the session
might result in the following error messages in swagent.log:
Install or update of an older OE
with certain patches in a combined
depot might result in errors
* Installing fileset "PHKL_nnnnn.C-INC,r=1.0"
(nnn of nnn).
ERROR: Cannot read from the file
"/var/adm/sw/products/ProgSupport/C-INC/INFO":
No such file or directory (2).
ERROR: Rebuilding the Installed Products Database
has failed.
You may need to retry this operation.
The problem is due to tools in pre-March 2009 OEs incorrectly handling certain
patch dependency and ancestor relationships. Patches PHKL_38623, PHKL_38733,
PHKL_38715, PHKL_38762, and possibly other patches can trigger this problem.
These patches are contained in the March 2009 (or later) FEATURE11i bundle,
and possibly other March 2009 (or later) patch bundles.
Due to header files missing from the ProgSupport.C-INC fileset, a compile of
C source code will fail. Many of the header files in the /usr/include directory
tree or in /usr/old/usr/include will be missing. A swverify check will not
detect the missing files.
What to do
To avoid this problem, Ignite or update to the older OE first. Then install the desired
patches from the March 2009 (or later) FEATURE11i bundle. Do not install or
update an older OE with the FEATURE11i bundle (or referenced patches) in a
combined depot.
To repair damage that might have resulted from this problem, follow the steps
described in QXCR1000902981. Go to the HP Support Center (http://hp.com/
go/hpsc). Click Search support knowledge, then select Search by document ID for
your search mode. Enter "ttr_na-SSB_1000902981” in the box.
Known install and update problems 79