HP-UX 11i v3 Installation and Update Guide, September 2010
Table A-2 Known install and update problems (continued)
Description/actionProblem
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:
* 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 IT Resource Center (http://itrc.hp.com),
click Search knowledge base, then select Search by document ID for your
search mode. Enter "ttr_na-SSB_1000902981” in the box.
Install or update of an older OE
with certain patches in a
combined depot might result in
errors
The HP-UX 11i v3 September 2008 release includes the option to tune the system
base page size to values larger than its 4 KB default. Integrity Virtual Machines
always uses this feature to tune the system base page size in the host to 64 KB.
HFS file systems will fail to mount when the file system block size is less than
the system base page size.
What to do
If you are performing an update, and plan to use a non-default base page size,
replace each HFS file system with a VxFS file system. For each existing HFS file
system, create a new VxFS file system and copy the contents of the HFS file system
to the VxFS file system. HP does not recommend using HFS file systems on
systems where the base page size will be tuned to a non-default value. While
HFS file systems can be configured to work in this environment, VxFS
administration is much simpler than HFS administration with non-default base
page sizes.
During a cold-install, configure all physical file systems as VxFS file systems.
For information about the new tunable that controls the size of a system base
page, see “Tunable Base Page Size” in the HP-UX 11i Version 3 September 2008
Release Notes (http://hp.com/go/hpux-core-docs).
HFS file system block size must
be greater than or equal to
system base page size
84 Harmless messages and known problems