Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.
Not Found
English

Page Not Found

The page or file you are looking for has been moved or no longer exists.

The following links might help you find the content you need:


You can also search the Documentation Portal or visit the home page.

English
  • Data Integration Connectors
  • All Products

Table of Contents

Search

  1. Part 1: Introduction to Amazon Redshift connectors
  2. Part 2: Data Integration with Amazon Redshift V2 Connector
  3. Part 3: Data Integration with Amazon Redshift Connector

Amazon Redshift Connectors

Amazon Redshift Connectors

Back Next

Rules and guidelines for migrating a mapping

Rules and guidelines for migrating a mapping

Consider the following rules and guidelines when you use the same or a different object path for the migrated mapping :
  • The following table lists the transformation, object type, and the fields in the advanced properties of a mapping that you can retain when you migrate to the new environment:
    Transformations
    Object Type
    Advanced Fields
    Source
    Single object, multiple objects
    Schema and table name
    Lookup
    Single object
    Applicable for unconnected, and connected cached and uncached.
    Target
    Single object
  • Before you migrate a mapping to Org2, map the connection1 of Org1 to Org2 that can access the schema and table name configured in the advanced properties in Org1.
  • After you migrate the mapping to Org2, you must not edit the mapping.
  • When you override the schema and table name in a mapping, the mapping fails with an error if the schema used in the connection in Org2 is not valid. The mapping fails with the following error:
    An unexpected exception occured while fetching metadata:[The following schema is not found - invalidschema]
  • You cannot dynamically refresh the data object schema at runtime. You must maintain the same metadata for the table selected in the source, target, or lookup transformations and the corresponding advanced field overrides as schema change handling is not applicable.
  • Consider the following guidelines for multiple sources:
    • If the mapping contains multiple sources, you can override the schema in the advanced properties only if the source objects have the same schema, as in the following example:
      object1:
      <schema1.object1>
      object2:
      <schema1.object2>
      If the schema is different, for example, if the schema for object1 is
      <schema1.object1>
       and object2 is
      <schema2.object2>
      , migration does not work.
    • Do not override the table from the advanced properties if the mapping contains multiple objects.
0 COMMENTS
We’d like to hear from you!