cancel
Showing results for 
Search instead for 
Did you mean: 

Installation of PHNE_25626

SOLVED
Go to solution
Konrath
Occasional Advisor

Installation of PHNE_25626

I got a problem when I wanted to install PHNE_25626 on one of my 11.00 systems. The error occurred after the new kernel was loaded:
Loading the kernel...
ld: Unsatisfied symbol "mi_timer_alloc" in file /usr/conf/lib/librpc.a[rpcmod.o]
ld: Unsatisfied symbol "mi_timer_free" in file /usr/conf/lib/librpc.a[rpcmod.o]
ld: Unsatisfied symbol "mi_timer" in file /usr/conf/lib/librpc.a[rpcmod.o]
ld: Unsatisfied symbol "mi_timer_valid" in file /usr/conf/lib/librpc.a[rpcmod.o]
4 errors.
*** Error exit code 1


Can anybody help me?
3 REPLIES
Clemens van Everdingen
Honored Contributor

Re: Installation of PHNE_25626

Hi,

did you install all the dependencies ?

PHCO_23117 bdf(1M) cumulative patch
PHCO_23436 cumulative SAM/ObAM patch
PHCO_23651 fsck_vxfs(1M) cumulative patch
PHCO_23963 libc cumulative header file patch
PHCO_25707 libc cumulative patch
PHKL_18543 PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_20016 2nd CPU not recognized in G70/H70/I70
PHKL_22677 fix of getdirentries, MVFS, rcp, mmap & IDS
PHKL_24027 VxFS 3.1 cumulative patch
PHKL_25613 IDS/9000; file/socket syscalls; eventports
PHKL_25906 Probe,IDDS,PM,VM,PA-8700,asyncio,T600,FS
PHKL_26059 syscall, signal, umask cumulative patch
PHNE_22566 Cumulative STREAMS Patch
PHNE_25626 ONC/NFS General Release/Performance Patch
PHNE_26771 cumulative ARPA Transport patch

If yes: Have you changed any install option like reinstall=true ?

If yes you will probably have a problem with PHKL_18543 which never may be reinstalled as this patch is dependency for almost all patches.

C.

The computer is a great invention, there are as many mistakes as ever, but they are nobody's fault !
Clemens van Everdingen
Honored Contributor
Solution

Re: Installation of PHNE_25626

Hi,

See also this thread:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xf4cc99f08a51d61190040090279cd0f9,00.html

Similar problem.

C.
The computer is a great invention, there are as many mistakes as ever, but they are nobody's fault !
Victor_5
Trusted Contributor

Re: Installation of PHNE_25626

Generally, it happened when
1. patch shares filesets with many superseding patches.
2. install with the reinstall options

the resolution is to reinstall the patches whose filesets were overlayed.

Some thoughts of mine:
1. make backup first
2. install those dependencies patches first, then reinstall this patches. You have got the list from the above post, you also can use swlist
swlist -l fileset -a prerequistie PHNE_\* |grep 25626
3. you can identify superseded patches with
swlist -l patch \*\.*,c=patch |grep superseded
4. when reinstall, make both reinstall options, deselect the "autoselect dependencies when marking software" to prevent other patches from being installed.