superseded patches with configure scripts

[sparky_2]

After installing the dec2004 patch bundle, the output generated from the check_patches script reports that there are a number of superseded patch filesets that are in an installed state, but they include a configure script. The swagent.log simply reports that the patches are being excluded because they have been superseded.

I understand that it is normal to have superseded patches installed but not configured, as this can be useful for roll-back purposes.

But does the fact that configure scripts for these superseded patches have been created indicate a potential problem? What is the best course of action to take in this circumstance?

[Simon Hargrave]

The easiest way to see if there are any problematic unconfigured filesets is to execute: -

# swlist â l fileset â a state

This will show you the state of every installed package.

On a happy system, all filesets should be "configured". Any that aren't you may need to run swconfig, however as you talk of superceded patches I'd check the ITRC patch database for conflicts first as you may have potential issues.