Purging Iterations
Only earlier iterations can be purged. A purge job fails if some of the object iterations have been purged by a purge job that was running previously.
PTC recommends that you avoid
creating queries and purge jobs that target the same objects with two concurrent purge jobs. If two purge jobs attempt to purge the same objects at the same time, one of the jobs fails. If this happens, you can remove and recreate the failed job.
The system does not allow you to purge any of the following:
• Objects you are not authorized to delete
• Objects that are included in a baseline
• Objects that are published to ERP (ESI)
• Objects that are checked out to a project
• Objects that are included in an end item configuration
• Objects that are included in a family table
• Objects that are associated to a promotion notice
• Objects that are a branch point for a new version
• Objects with certain reference relationships, such as CAD parametric dependencies
• An object that is a Checkin iteration in PDM for a sandbox version
• The latest iteration of an object
• Iterations that are referenced from a change object
For more information on conflicts you can override, along with the conflict messages associated with these situations, see
Purge Conflicts.
In addition, the following situations apply to purging iterations:
• If you have specified a number of iterations (higher than 1, which is the default) not to be purged in the collection criteria, you cannot purge that number of iterations. For example, if you specified 2 iterations, then the latest 2 iterations of all revisions are not deleted.
• If another object has a link to the specific version that is being deleted, you cannot purge that version.
Example
An object has the following iterations:
• A1
• A2 (added to baseline)
• A3
• A4 (branch point iteration, from which a new version B is started)
• A5 (latest)
• B1
• B2
• B3
• B4
• B5 (latest)
In this example, only iterations A1, A3, B1, B2, B3, and B4 would be purged.