For example, you can create a source definition, a target definition, or a Lookup transformation in PowerCenter that connects to an Oracle database. When you import these objects in the Developer tool, use the

Connection Assignment

dialog box to specify the connection type for each object.

When you select a connection type for PowerCenter repository objects, use one of the following methods to assign connections:

Assign a single connection to multiple PowerCenter objects at the same time.

You can assign a single connection to all sources, all targets, all Lookup transformations, or all objects that do not have an assigned connection. Or, you can assign a single connection to all objects with names that match a specified name pattern. Select an option from the

Select

list and click

Assign Connection

.

Assign a single connection to multiple PowerCenter objects of different object types.

Choose the

Custom

option in the

Select

list, select multiple PowerCenter objects, and then click

Assign Connection

.

Assign a connection to a PowerCenter object.

Select a PowerCenter object and click the

Open

button in the

Connection Name

column.

You can assign a connection to an object that is different from the original connection type. You might do this if Developer tool does not support the original connection type. If you assign a different connection type than the original one, the Developer tool warns you that the connection types do not match.

If you choose to ignore the warning and proceed, the import succeeds and assigns the new connection to imported data sources. The source or target are valid when the metadata for the chosen connection matches the schema of the imported data sources.

If you import a PowerCenter mapping that contains a Source Qualifier with multiple downstream sources, the import process does not assign connections. You must manually assign connections to the objects.

When you edit the reusable Lookup transformation properties in the mapping level before importing it into the Model repository, the Developer tool imports a non-reusable Lookup transformation without assigning a connection. To resolve this issue, you can assign a connection manually to the Lookup relational data object or instance after import.