Import Restrictions

• •Source and target
• •Transformation
• •Mapping
• •Functions
• •Mapping variables
• •Session properties
• •Workflows and Worklets
• •Tasks

Source and Target Restrictions

• •When you import a source or target from PowerCenter release 9.1.0 or earlier, the import process cannot verify if a connection type associated with the object is valid.
• •If the version of the PowerCenter repository is earlier than 9.5.0, an IBM DB2 source database name or an IBM DB2 target name must start with "DB2" to set the DB2 type.
• •When the row delimiter for a flat file source is not valid, the import process changes it to the default value.
• •You cannot import Salesforce sources or targets from PowerCenter.
• • When you import Teradata sources from PowerCenter, the import process ignores the following properties:
• - Not Null property of a column
• - Output is Deterministic
• - Output is Repeatable
• - Number of Sorted Ports
• - Foreign Key
• • When you import Teradata targets from PowerCenter, the import process ignores the following properties:
• - Not Null property of a column
• - Update Override
• - Target Table Prefix
• - Foreign Key
• • When you import Netezza sources from PowerCenter, the import process ignores the following properties:
• - Foreign Key
• - Output is Deterministic
• - Output is Repeatable
• - Number of Sorted Ports
• •When you import Netezza targets from PowerCenter, the import process ignores the following properties:
• - Foreign Key
• - Update Override
• •When you import a Netezza source from PowerCenter, the import process imports the Netezza source with the same name under a newly created Netezza data object. However, when you create a read operation, the Source transformation within the read operation has a unique name appended with a number that is different from the imported source name.
• •When you import a mapping with a Source Qualifier having an overridden SQL query, which selects a subset of the columns of the Source Qualifier, the Integration Service cannot run the mapping. To resolve this issue, remove the extra port and ensure that you match the SQL query to include all the columns in the source in the physical data object in the Developer tool.

Transformation Restrictions

• •An expression in a transformation must contain 4,000 characters or fewer.
• •The database type for an SQL transformation converts to ODBC during the import process.
• •When you set the data cache size or the index cache size for a transformation to a value that is not valid, the import process changes the value to Auto.
• •When you import a mapping with an empty Lookup cache directory name into the Model repository, the imported mapping is not valid. To resolve this issue, enter a valid value for the Lookup cache directory name under the run-time properties for the Lookup transformation in the Developer tool.

Mapping Restrictions

• •When you import a mapping with supported objects or transformations, the import process creates a separate Model repository mapping for each pipeline in the PowerCenter mapping, preserving the target load order.
The import process behavior remains the same for a workflow that contains a session that runs a mapping with multiple pipelines. Each mapping name is appended with a number that indicates the order in which mapping needs to run as mentioned in the target load order.
• •If the mapping contains objects that are not supported in the Model repository, the pipelines are imported as a single mapping into the Model repository.
The pipelines with the unsupported transformation or object are imported with broken links in the Model repository. In this case, the number of imported mappings can be less than the total number of pipelines in a PowerCenter mapping based on the target load order. If any pipeline in PowerCenter contains transformations or objects that are not supported in the Model repository, the pipeline is broken with the unconnected objects and it appears within a single mapping in the Model repository.

Functions Restrictions

Mapping Variables Restrictions

Session Properties Restrictions

Workflow Restrictions

• •In PowerCenter, when you right-click a workflow link, you can set a link condition in the Workflow Manager. After you import the workflow in the Model repository, you can see the condition only as a comment, and you must manually convert the mapping based on the condition required.
• •Workflow parameter, workflow variables, and session parameters are not supported for import from PowerCenter in the Model repository.
• •You cannot import nested worklets from PowerCenter.

Task Restrictions