Removing a corrupt superseded patch

[Damien Lass]

Looking for any help on this one...

I removed a corrupt patch (PHCO_22526) from my HP-UX 11.0 server in an attempt to clean up the machine. I did not think this to be a problem as I already have the superseding patch (PHCO_23966) configured successfully on the box.

As a result of uninstalling the corrupt patch, many active files failed to be removed and placed in the /var/adm/sw/cleanupfile. These files include:
/usr/sbin/swverify, /usr/sbin/swagentd, /usr/lbin/swconfig.

Now when I attempt to run a swlist command I receive the following error: WARNING: Ignoring unknown keyword "is_volatile" at line 14279.

Does anyone have any ideas of how I can fix this mess I have created? Thanks in advance!

[Helen French]

Hi Damien,

If the OS is HP-UX 11.0, then install the SD cumulative patch PHCO_25875. That may fix your problem.

HTH,
Shiju

[Damien Lass]

If I were to reboot my box, would those files that are in the /var/adm/sw/cleanupfile be removed once inactive? I definately don't want to lose the swagentd or any of the other files mentioned above...

[Helen French]

Hi,

The patch mentioned doesn't require a reboot ! Check the patch description.

HTH,
Shiju

[Damien Lass]

Shiju-
I understand that the new patch does not require a reboot. I would like to avoid installing PHCO_25875 if at all possible. If I patch this box with PHCO_25875, I have to patch 8 other boxes which might open another can of worms in itself. I can do that, but I am looking for an alternative solution that does not require installing anything higher than PHCO_23966 on environment.

I do appreciate the idea though. If need be, I will do this.

[Mateja Bezjak · Accepted solution]

Hi Damien,

Did you force the PHCO_22526 removal? Checkremove scripts prevent removing the patch if a superseeding patch is applied.

Have you tried removing PHCO_23966 and then applying it again? What is the output of /var/adm/sw/swremove.log and /var/adm/swagent.log files?

Regards,
Mateja

[Damien Lass]

Mateja -
Thanks for the note. Removing PHCO_23966, reinstalling PHCO_22526, and then again installing PHCO_23966 fixed the errors I was receiving. Thanks again!