Unable to run cleanup due to patch being in corrupt state

[Adam Noble]

All,

I have a patch which has been superseded which is in a corrupt state. When I run cleanup I am unable to commit my existing patches due to this patch. I am also unable to remove the patch using swremove. Can I change the state of the patch so it is ignored or something as I desperately need to clear down some space. There is no actual error in any of the sw logs it just says unable to remove patch.

Cheers

[Robert-Jan Goossens]

Hi Adam,

I don't think you can. how did this patch get corrupted ?

Could you check the dirextory permissions in /var/adm/save/PHNE_xxxx.

Please post patch-number.

Regards,
Robert-Jan

[Adam Noble]

drwxr-xr-x 3 root sys 1024 Oct 10 2000 PHCO_19047

[Steven E. Protter]

corrupt patches must be removed.

swremove PHXX_19XXX

swverify \*

Does it confirm the corrupt analysis:

Is this 11.00?

Is PHKL_18543 installed but only ONE time?

SEP

[Adam Noble]

# swremove PHCO_19047

======= 10/27/05 15:04:12 BST BEGIN swremove SESSION
(non-interactive)

* Session started for user "root@orafin2".

* Beginning Selection
* Target connection succeeded for "orafin2:/".
NOTE: One or more patch filesets were automatically selected or
deselected to maintain patch integrity. Please refer to the
swremove.log logfile for details.
ERROR: Cannot continue the "swremove" task.
* Selection had errors.



======= 10/27/05 15:04:20 BST END swremove SESSION (non-interactive)

#

As you can see it can't be removed. When I do a verify it comes up with errors regarding mtime etc on files. Can't I somehow get it to ignore this particular patch

[Robert-Jan Goossens]

the only think I can think of is to reinstall the patch (reinstall=true) and then remove it from your server.

Robert-Jan

[Adam Noble]

Thanks I was thinking of doing the same however I am unsure if this would have a detrimental effect on the system as there would be a patch on the system which had superseded this one

[Robert-Jan Goossens]

patch PHCO_19047 has no dependencies ,and normally in (my experiences) sam patches give no trouble if you reinstall them.

Do be shure download the reccomended PHCO_21187 or the latest PHCO_31879 also, just in case you need to reinstall one after you have removed 19047.

Regards,
Robert-Jan

[Geoff Wild]

Wait!

Try this:

If you ever get an error like this:

cleanup -c 1


Would you still like to commit these patches? y
Committing patches superseded at least 1 time(s) ...
ERROR: swmodify(1M) encountered problems committing the
superseded patches:

ERROR: Could not select the software "PHCO_25723.*". This software
is in a corrupt state and is not available for selection.
Corrupt software can be removed with the swremove command, or
replaced with the swcopy command.
ERROR: Could not select the software "PHSS_26577.*". This software
is in a corrupt state and is not available for selection.
Corrupt software can be removed with the swremove command, or
replaced with the swcopy command.
All information has been logged to /var/adm/cleanup.log.


Then do this:

swmodify -a state=configured -a patch_state=superseded PHCO_25723.*


swmodify -a state=configured -a patch_state=superseded PHSS_26577.*




Rgds...geoff

[Adam Noble]

well I'm afraid that didn't work either the patch is still in a corrupt state so nothing changed.

[Geoff Wild · Accepted solution]

So, you tried this:

swmodify -a state=configured -a patch_state=superseded PHCO_19047.*

and that failed?

Rgds...Geoff

[Adam Noble]

sorry missed off the .* at the end. Superb Geoff has done the trick many thanks!!!!