reinstalling a patch question

[James Ellis_1]

Soon I'll be installing the Sept 2001 patch bundle for HPUX 11.0. I ran the patch check utility program, and got numerous patch errors, all having to do with the kernel (All were PHKL patches). The utility recommended I should re-install the patch using swinstall option '-x reinstall=true'. I have a question, I believe I downloaded all of these patches in the binary format, but maybe I did not. I went to HP and checked and could not find the PHKL_18543, apparently its been superseded? I found this patch in my depot. I am thinking I should download again in binary format, and unshar it and get a fresh patch just to rule out any errors. Should I reinstall using swinstall with the '-x reinstall=true' option? Do I need to do this with a PHKL_18543.depot? I don't see where this patch is that has the .depot ending. I've ran the cleanup command and maybe its gone? If I need to download it again, where do I find it and would this slightly different version be compatible with what is already on my system? Thanks, Jim

[Frederic Sevestre]

Hi,

If you have your patch on a depot it is no use downloading it again. You can install it using :
swinstall -x reinstal=true -s PHKL_18543.

You should install the superseding patch. In that case the reinstall option is not use.

Fr??d??ric

[Sebastian Galeski_1 · Accepted solution]

PHKL_18543 is not supersided patch. Important Details about installation of this patch are in Speciall installation instructions ie.:
Special Installation Instructions:
If PHKL_18543 is installed on a system that does not have
Advanced VxFS, then the Advanced VxFS driver 'vxadv' will be
commented out of the /usr/conf/master.d/vxfs file as follows:

* Disabling AdvJournalFS: vxadv vxadvc 10 100 ...

The following note will be logged in the swagent.log file:

NOTE: "AdvJournalFS" product is now disabled. Any vxadv driver in
the system file will be ignored. If you install the 11.00
version of "AdvJournalFS", you must again install this patch,
PHKL_18543.
(The reinstall* options must be set to false - the default.)

If the Advanced VxFS product is subsequently installed, PHKL_18543
must be reinstalled as specified in the note above, otherwise the
following warning will occur when creating a kernel and the Advanced
VxFS features will not be available:

WARNING: No such device, tunable, or cdio vxadv.
Ignoring the following line.
vxadv

Please apply this patch along with command patch PHCO_13411.
Failure to do so, ie. applying one without the other, will
result in fsck failure, or even fsck corrupting the
filesystem.

The new features in PHKL_13552 are only supported for
V-Class 64-bit systems. Non-V-Class systems can install
this patch with no impact to those systems. The following
patches rely on PHKL_13552 to enable certain features:

PHCO_13606: SAM recognition of new tunables
PHCO_13571: insf, mksf, lssf recognize new devices
PHCO_13494: fbackup/frecover recognize new devices

To enable large record support on V-Class systems, you will
need to set the following tunables:
scsi_maxphys 16777215
st_large_recs 1

To enable failed data overruns where stape reads are shorter
than the actual record size, use:
st_fail_overruns 1

Installing PHKL_17040 on PCI based systems will add diag1 to
the /stand/system file and create the /dev/diag/diag1 device
file. Removing PHKL_17040 will delete diag1 from
/stand/system file and remove the /dev/diag/diag1 device
file from the system. Installing/Removing any patch
superseding PHKL_17040 will leave the system in the state
it was prior to installing the patch.

It may be necessary to boot on a backup kernel to recover
from the boot hang before installing this fix.


hope it help You

[Luc Bussieres_1]

The PHKL_18543 is a "Line in the sand" patch and not a superceded patch this means that some other patches will change part of it only.

If you reinstall the 18543 on a system you will have to reinstall also all other patches that "remodify" what the 18543 have modify. Otherwise your system will be in a "corrupted" state which will prevent you to rebuild a kernel.

The only good reason I know to reinstall the PHKL_18543, is after installing advance JFS version 3.1 (You don't reinstall 18543 with Online JFS 3.3) because there is a fileset in 18543 that is not install on yur system until advance JFS 3.1 is install. So to install that missing fileset you have to install 18543 again but when you do this you verify your swinstall options to make sure taht the 2 reinstall options are set to false. so swinstall will then install only the fileset that was missing.

Luc

[James Ellis_1]

Ok, this seem to be a little confusing to me. From what everyone said, I think if I went ahead and reinstalled PHKL_18543 I would have to reinstall all of the other patches that depend on this patch. I can't remember all of the patches that depend on PHKL_18543. Right now, my server has the HP_UX General Release Patch, June 2000. I recall reading somewhere in another post where it says reinstalling PHKL_18543 is never a good idea because it reverts many filesets back a few revisions? Someone said if you need to re-install the PHKL_18543 patch, you might as well as grab the latest patch bundle from HP and install that over the top immediately. So should I look for a superseding patch of PHKL_18543 and just install this? If I was going to go ahead and install the Sept 2001 patch bundle, would this fix all of the problems? (I have the June 2000 patch bundle on my system now). Thanks,Jim
PS: trying to see if I can save alot of headaches from installing multiple dependant patches of PHKL_18543.

Also, see the attachkemt of the errors I got of PHKL_18543 and other patches.