Table of Contents

Search

  1. Preface
  2. Understanding the Repository
  3. Using the Repository Manager
  4. Folders
  5. Managing Object Permissions
  6. Local and Global Shortcuts
  7. Team-Based Development with Versioned Objects
  8. Labels
  9. Object Queries
  10. Team-Based Development with Deployment Groups
  11. Copying Folders and Deployment Groups
  12. Exporting and Importing Objects
  13. Exchanging Metadata
  14. Copying Objects
  15. Metadata Extensions
  16. Appendix A: MX Views Reference
  17. Appendix B: PowerCenter Reports Reference

Repository Guide

Repository Guide

Updating Imported Objects

Updating Imported Objects

After you import objects from the Developer tool, ensure that PowerCenter sessions run.
Complete the following steps to ensure that PowerCenter sessions that use imported objects run:
  1. Re-establish key relationships.
    The Developer tool export process does not retain key relationships between source and target tables if the primary key and foreign key tables are in different mappings. After you import mappings in which the primary key and foreign key tables are in different mappings, you must reestablish the key relationships.
  2. If the mapping uses an SQL query override, verify that the columns in the query are connected.
    The Developer tool allows you to run a mapping with an SQL query override if the columns in the query are not connected. In PowerCenter, the columns you use in the query must be connected.
  3. Create sessions, workflows, and connection objects.
    The Developer tool does not have sessions or workflows. When you import mappings from the Developer tool, you must create PowerCenter sessions and workflows. You must also specify connection information for sources and targets.
  4. Verify that mapping sources use the same connection.
    A Developer tool mapping source can join relational data objects that use different connections. A PowerCenter mapping source can join data from related tables when the tables use the same connection. If a Developer tool mapping source joins relational data objects that use different connections, the exported mapping contains a single Source Qualifier transformation. Verify that the tables joined in the Source Qualifier transformation originate from the same relational database and that they use the same connection. If they do not, replace the Source Qualifier transformation with multiple source qualifiers, and join the sources with a Joiner transformation.
  5. Verify the precision mode.
    By default, the Developer tool runs mappings with high precision enabled, while PowerCenter runs sessions without high precision. If you want PowerCenter sessions to produce the same results as the corresponding Developer tool mappings, run them in the same precision mode.
  6. Verify that reference tables exist.
    PowerCenter requires that reference tables exist in the directory defined in the INFA_CONTENT environment variable. If INFA_CONTENT is not set, the reference tables must exist in the following PowerCenter services directory:
    $INFA_HOME\services\<Developer Tool Project Name>\<Developer Tool Folder Name>
    The PowerCenter administrator can set the INFA_CONTENT environment variable on the machine that hosts PowerCenter services. If INFA_CONTENT is set, copy the reference tables to the INFA_CONTENT directory. If INFA_CONTENT is not set, copy the reference tables to the PowerCenter services directory.

0 COMMENTS

We’d like to hear from you!