PowerCenter Repository Maintenance

Back Next

Example of a Rarely Checked-Out Composite Object

You rarely check in and check out the mapping m_PhoneList. Two checked-in versions of the mapping exist. However, you frequently check in and out the reusable transformation in the mapping. The transformation is a Filter transformation named FIL_Tr. It has six versions.

At the repository level, you purge versions based on criteria, and you specify that you want to keep only the latest checked-in version of objects.

The following figure shows the history of the mapping and transformation versions:

FLT_Tr version 1 has a history of m_PhoneList purged version 1. FLT_Tr version 2 has a history of m_PhoneList purged version 2. FLT_Tr version 3 does not use a mapping in this transformation. FLT_Tr version 4 has a history of m_PhoneList purged version 2. FLT_Tr version 5 has a history of m_PhoneList purged version 2. FLT_Tr version 6 has a history of m_PhoneList purged version 2.

The advanced purge produces the following results:

Object	Purged Versions
Mapping m_PhoneList	Version 1, assuming that no Session task or other composite object uses m_PhoneList.
Transformation FIL_Tr	Version 1. You do not purge versions 2, 4, 5, and 6 of the transformation, because version 2 of m_PhoneList uses those transformation object versions. You do not purge version 3 of the transformation, because you retain version 2, which is an older version.

If you cannot purge an older version of an object, the Repository Service retains all newer versions of the object during an advanced purge.

Rename Saved Search

Table of Contents

PowerCenter Repository Maintenance

PowerCenter Repository Maintenance

Example of a Rarely Checked-Out Composite Object

Example of a Rarely Checked-Out Composite Object