Reloading patches

[David R Gallup]

I tried to reinstall some patches but several were skipped with the massage "To reinstall this patch, deinstall it first before attempting to reinstall it"
Why does swinstall do this for some patches but not others? I have an old system that has been patched and patched. Certain patches won't configure with swconfig saying that they need other filesets but the filesets are already there.

Is there any way to force an installation of a given configuration of the OS short of starting from scratch?

[Andreas Voss]

Hi,

from command line you could add to swinstall the option

-x reinstall=true -x reinstall_files=true

Regards

[Alex Glennie]

I suspect the answer is because the patch was in a transient or unconfigured state and the /var/adm/sw/patch/PATCH_NOSAVE option was not set or has now been removed ... in which case this could be tricky if it's possible at all ....

How many patches are we talking ?
whats the output from swlist -l fileset -a state and the patches we are talking ?

My advise at the moment is have a backup made first and be very careful

[David R Gallup]

Here is the full senario. I had HP-UX 10.2 loaded with workstation ACE and Quality Pack June 99 CD's loaded as well. I had several bugs in my application Pro/ENGINEER Release 2000i2. PTC said I needed to load workstation ACE and quality pack Dec 99. I did that, Pro/ENGINEER bugs fixed but many problems with HP VUE. I could not get that fixed despite several days of tracing error logs etc.

Last night I reloaded workstation ACE Dec 99 including core OS with rienstall existing filesets set on (through swinstall config GUI). At that point it could not make kernal due to unreferenced variables. So I continued on with swinstall using the Quality Pack CD, also with reinstall existing filesets set true. Kernal build OK, HP VUE OK. Pro/ENGINEER core dumps!

Swinstall refused to reinstall over 100 of the patches on the quality pack CD with the message "To reinstall this patch, deinstall it first before attempting to reinstall it".

I did not have the override errors config turned on. I am bold but not that bold.

The attached file has the output from swlist -l fileset -a state. It shows all the patches configured. Obviously, some of the newer patchs were overwritten even though I did not set swinstall to overwrite newer files. HELP!

[Darrel Louis]

Hi,

If you read the patch descriptin of some patches it says that you need de-install the patch before reinstalling it.

Read the patch description first.
A Advise don't reinstall patch PHKL_16751 for 10.20 or PHKL_18543 for 11.X, this will cause more problems.

You have some products in a installed state, run "swconfig \*"

Good Luck

Darrel

[David R Gallup]

I have already run "swconfig \*" before I did the "swlist -l fileset -a" listing. Swconfig says the unconfigured filesets depend on additional filesets but they are already on the system. How can I get rid of a fileset that won't configure? Swremove won't take them off.

[Darrel Louis]

Hi,

swmodify -u should do the trick.

read the man page for swmodify.

Darrel

[David R Gallup]

I managed to get back to where I had a "good" OS by using swremove and selecting every patch on the system. This gave an error for every patch that had been installed prior to the last time the cleanup command was run. Since "enforce errors" was set, only the new patches were removed.

At some point I will have to try installing the Dec 99 ACE and Quality Pack again but I will be much more careful about selecting the patches to apply. No more Match What System Has!!!

I have just one problem remaining:

This machine has 2 ethernet interfaces, the built in 10 mbs interface and a 100 mbs add in card. When the system boots, it makes a special file /dev/lan0. It is creating it with major number 76 which corresponds to the btlan3 driver. I need this file to have a major number of 52 which corresponds to driver lan2. I have several license managers which look at /dev/lan0 to get the machine ID. They are getting the wrong ID and refusing to let my software run.

I can restore the correct /dev/lan0 file from tape or I can create a new one with mksf -d lan2 -H 8.16.6 -I 0 -v -i /dev/lan0. Everything seems to work OK until the machine reboots, then it makes a new /dev/lan0 file.

What is creating this file and how do I make it stop???

[Jitendra_1]

You might want to add a startup script which basically does the same thing you are n doing manually . That is remove the /dev/lan0 and recreate it using mksf .
Also you can try removing btlan driver from the kernel if that helps.