SD-UX patch removal

[Duncan Galbraith]

Hi,
Can anyone explain why sometimes SD-UX will allow me to remove
patches and sometimes it won't. I have created the patches and
installed them. I (sometimes) get a message in the logs when removing like:
The fileset "" is a "sparse" or "patch" fileset which may only be removed if its base fileset "" is also being removed or if rollback data is available. Since neither of these conditions is true, fileset "" will be excluded.

This seems to say 2 things:
1. I'm not removing my base fileset which is OK because I'm not.
2. That rollback data is not available.
If I look in /var/adm/sw/save/ then all the filesets are there so I would assume that rollback data is there. Can I get any more info out of SD-UX as to why it thinks I have no rollback data ?

Thanks,

Duncan

[James R. Ferguson]

Hi Duncan:

"Spare" filesets are those that have parts (already loaded) in an "ancestor" fileset. Hence, since you would not want to remove a partial fileset, 'swremove' denies this operation.

To see the ancestoral relations do:

# swlist -l fileset -a ancestor PHxx_nnnn

...JRF...

[Duncan Galbraith]

I agree I don't want to remove part of my patch product but I don't understand why I can't (sometimes) remove all of it when, as far as I can see, I do have rollback data stored in /var/adm/sw/save.

Any more thoughts ?

[James R. Ferguson]

Hi Duncan:

My guess whould be that the ancestoral relationships are several layers deep and/or there are patch inter-dependencies. I presume that you haven't committed any patches. Of course, this would include having run some level of 'cleanup'.

The patch management documentation takes care to point out that 'swremove'al of patches should be approached with caution.

...JRF...