This object is marked with an XPSTombstone. This XPSNumber was tied to an object with OID (24-e80ec43b-afee-4dda-a1ba-9bbfcf8226aa). The Siteminder Policy Store is really somewhat like two parallel DB’s. The traditional policy store has been used since R6 and earlier. The XPSExtensions are essentially a set of pointers which relate to the data in the policy store. This works a bit like an Index, or a Virtual List, or a Virtual table (in OBC). When the object is deleted using a non-XPS Tools (e.g. FSSAdminUI, Policy Store API, smobjimport) the object is created in the traditional policy store, but the XPS extensions do not get updated automatically.
XPSSweeper will essentially update the XPSExtensions by adding the data that points back to the newly created data, or deleting the data. In additional any data which is deleted using an XPSTool (e.g. XPSExplorer, SMAdminUI, etc) these objects are asynchronously deleted in XPS directly. However they aren’t deleted immediately. They are marked with an XPSTombstone. Above we see the XPSNumber which is referencing the GUID of the object. That GUID no longer exists in the policy store. The housekeeping thread is run to delete the objects marked with an XPSTombstone.
housekeeping thread are executed by Policy Server at 5 minutes interval as default, and XPSSweeper include this function.