HP-UX 11i v2 Installation and Update Guide, December 2007

Known Problems and Troubleshooting
Known Install and Update Problems
Appendix A144
Core file Generated During
Update from HP-UX 11i v1 to
HP-UX 11i v2
If you are updating your HP-UX 11i v1 December 2006 OE to a
later OE like HP-UX 11i v2 June 2007 or later, you may see a core
file generated during the update process.
The core file is generated because of a call to the /usr/bin/pwd
command by the /usr/sam/bin/samreg script. The pwd from the
HP-UX 11i v2 OE gets invoked by an OE which is still under
update; thus the Kernel and libraries are still at the HP-UX 11i v1
level. This causes pwd to dump core.
What To Do
You can safely ignore this core file as it does not cause any data
loss or loss of functionality.
Core File Generated while
Removing Some Products
from HP-UX 11i v2
If you are removing products like iSCSI-00 or HyprFabrc-00 from
a HP-UX 11i v2 June 2007 or higher OE, you may find a core file
generated by the cimprovagt process.
What To Do
You can safely ignore this core file as it does not cause any data
loss or loss of functionality.
Application Discovery Agent
Does Not Correctly Trap and
Format Messages
The Application Discovery agent does not correctly trap and
format messages when an unconfigure action is taken. This
results in messages that display inappropriately within columns
designated for Software Distributor (SD) within the swagent.log
file.
What To Do
When analyzing Software Distributor messages in the
swagent.log file, you can safely ignore the following lines because
they apply to Application Discovery agent and not to Sof:ware
Distributor:
* Running "unconfigure" script for product "AppDiscMN"
* Stopping the agent daemon
* Removing WBEM provider
removing the AmgrAgentProvider
* Removing ssl directories
Table A-1 Known Install and Update Problems (Continued)
Problem Description/Action