Check out the TSSA cleanup documentation: https://docs.bmc.com/docs/tssa89/cleaning-up-truesight-server-automation-data-808908211.html
Also, take a look at the "removing irrelevant patches from an existing catalog" documentation as well: https://docs.bmc.com/docs/tssa89/removing-irrelevant-patches-from-an-existing-catalog-808906657.html
Hopefully these will help get you an answer!
Thanks for you reply with but this is not the solution for our issue.
We already performed "Remove Irrelevant Patches" and perform online/offline cleanup actions.
The patches we are talking about are obsolete patches that are superseded by new ones (and not irrelevant).
Microsoft release every month cumulative rollup updates that replace previous month rollup so use only the latest ones.
The Windows 2016 patch is 1.4 GB in size every month.
Also Windows 2003 patches are still in the catalog and on the file server and TSA is not able to patch / analyze this OS version so why are they don't removed from the catalog?
there's two different asks here:
1: remove files on the file system that are no longer associated w/ a catalog
2: find 'old' patches, that are not irrelevant, etc but will probably not be deployed anytime soon and delete them from the file system and then also reset their status in the bsa database to 'not downloaded' so if they are needed again, they get re-downloaded.
Where can I find the database table corresponding to the patches that are downloaded?
If for somehow irrelevant patches are needed to be downloaded again to solve any kinds of issues I would like to know how i reset that status in the database.
those commands delete patches flagged as irrelevant out of the catalog, not off the file system. which are patches no longer provided by the patch vendor, patches that don't match any filters in the catalog (eg, you removed a filter), and i believe obsoleted patches (not sure about the last one).