PowerCenter Repository Maintenance

PowerCenter Repository Maintenance

Rules and Guidelines for Purging Versions of Objects

Rules and Guidelines for Purging Versions of Objects

Use the following rules and guidelines when you purge versions of objects:
  • If you purge the latest version of an object and the preceding version has a different name, the preceding version takes the name of purged version. For example, you have the source src_Records. The latest version is named src_Records, but the name of the preceding version in the history is src_RecordsWeekly. If you purge the latest version, the name of the preceding version becomes src_Records.
  • When you purge an individual version of a dependent object, you render composite objects invalid if they use the dependent object version. Verify object dependencies before purging individual object versions.
  • In an advanced purge of an active object, you cannot purge a version of a dependent object if it is used in an unpurged version of a composite object.
  • In an advanced purge of an active object, if you specify a number of versions to keep, you keep the latest checked-in version, even if it was checked in after the purge cutoff time. If the number of versions to keep is greater than the number of object versions, you keep all object versions.