Table of Contents

Search

  1. Preface
  2. Mappings
  3. Mapplets
  4. Mapping Parameters
  5. Mapping Outputs
  6. Generate a Mapping from an SQL Query
  7. Dynamic Mappings
  8. How to Develop and Run a Dynamic Mapping
  9. Dynamic Mapping Use Cases
  10. Mapping Administration
  11. Export to PowerCenter
  12. Import From PowerCenter
  13. Performance Tuning
  14. Pushdown Optimization
  15. Partitioned Mappings
  16. Developer Tool Naming Conventions

Developer Mapping Guide

Developer Mapping Guide

Source and Target Restrictions

Source and Target Restrictions

The following source and target restrictions apply when you import PowerCenter objects:
  • 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.

0 COMMENTS

We’d like to hear from you!