swlist does not show an installed patch

[Bandar Al-Harbi]

I am trying to install PHNE_25644 on 11.11
but received this message :
NOTE: The patch fileset "PHNE_25644.C-
INC,r=1.0" is superseded by
another patch fileset that is
already installed on the target.
Fileset "PHNE_25644.C-INC,r=1.0"
will be excluded.
NOTE: The patch fileset "PHNE_25644.CORE-
KRN,r=1.0" is superseded by
another patch fileset that is
already installed on the target.
Fileset "PHNE_25644.CORE-KRN,r=1.0"
will be excluded.
NOTE: The patch fileset "PHNE_25644.CORE2-
KRN,r=1.0" is superseded
by another patch fileset that is
already installed on the
target.
Fileset "PHNE_25644.CORE2-KRN,r=1.0"
will be excluded.

NOTE: The patch fileset "PHNE_25644.NET-
KRN,r=1.0" is superseded by
another patch fileset that is
already installed on the target.


Any one can help please.

[Marco Santerre]

Bandar,

what this is telling you is that you have a more recent patch on your system already. You may want to check in the ITRC patch database to find out which patches supersedes this one, and find the one that you currently have on your system.

So, basically, you shouldn't need to install this patch cause it's already on your system.

[Jeff Schussele]

Hi,

If the patch was originally installed in a bundle, then a
swlist | grep PHNE_25644
won't find it - try
swlist -l patch | grep PHNE_25644

But if it's already been committed because it's been superseded, then you'll have to research it supersedes here on the ITRC & then look for those the same way as above.

Rgds,
Jeff

[Pete Randall]

Odd! I checked the patch database and can't find any superceding patches. I have to wonder what patch it thinks supercedes?


Pete

[Zigor Buruaga]

Hi,

I can not find any patch superseding that.
Maybe you could try to run:
#swlist -l patch | grep "cumulative ARPA"

and see what shows.

Kind regards,
Zigor

[Hari Kumar]

very new.....
swlist -l patch PHNE_25644
Does this lists out ?

[Michael Steele_2]

First, lots of places to check for what happened:

a) swlist -l fileset -a state | grep -v \# | grep -i #####

b) Check /var/adm/sw/swagent.log

'swagent.log' explains everything.

Post any errors

[Bandar Al-Harbi]

I tried:
#swlist -l patch | grep "cumulative ARPA"
I had :
# PHNE_28089 1.0 cumulative ARPA Transport patch - which is commented as you can see !!

[Pete Randall]

That's your answer, then. PHNE_28089 reports:

Supersedes:
PHNE_27989 PHNE_27730 PHNE_27382 PHNE_27063 PHNE_26762 *PHNE_25644*
PHNE_25642 PHNE_25134 PHNE_24506 PHNE_24211 PHNE_23645 PHNE_23288


Your PHNE_25644 was superceded by PHNE_28089 so you can't apply it.


Pete

[Bandar Al-Harbi]

You mean I do not need to, or should I find out another way ??

[Umapathy S]

There is no need to apply that one. Superseeded pataches will be superset of the concerned patch.

[Jeff Schussele]

Do not need to.
Supersedes have all the earlier patch data plus whatever new data it offers.

Rgds,
Jeff

[Zigor Buruaga]

Hi,

No, you don't need to apply the patch, since a more recent version is already applied.
Anyway, you can check the status of the new patch with:
#swlist -l patch -a state | grep PHNE_28089

Kind regards,
Zigor

[Michael Steele_2]

Under this HP comment in PHNE_25644 &b PHNE_28909:

"...Warning: 03/08/18 - This Critical Warning has been issued by HP....."

"... - PHNE_27063 introduced an unexpected send(2) system call
failure of EWOULDBLOCK on a TCP socket when the preceding
poll(2) system call on the same socket had returned a POLLOUT
revent. This could result in an application hanging.
- The same behavior is experienced with superseding patches


- The previous patch, PHNE_25644, does not exhibit this same
behavior. To ensure as many known issues as possible are
addressed, HP recommends that PHNE_25644 be installed after
the patches are removed. If PHNE_25644 was installed prior
to the patches, it will automatically be restored when the
patches are removed and it will not need to be reinstalled.


http://www2.itrc.hp.com/service/patch/patchDetail.do?patchid=PHNE_28089&context=hpux:800:11:11

As pointed out above there are some problems which seem to be ongoing. So you might want to call HP about this.