Use a different object path for the migrated mapping
Use a different object path for the migrated mapping
After you migrate the mapping, you can use a different object path to run the mapping from the
new environment.
Before you migrate the mapping, you can change the object metadata or the runtime attributes to
reflect the object path in the migrated environment. You don't have to edit or update
the mapping in the new environment.
As a rule, when you specify the schema and table in the advanced properties or object
properties,
Data Integration
honors the attributes in the following order of
precedence:
SQL override
. The SQL statement
to override the default query generated from the specified source type in the
Source or Lookup transformation in a mapping.
Custom query
. The SQL statement
to reduce the number of columns to query in the Source or Lookup transformation
in a mapping.
Runtime advanced attributes
. The
advanced properties such as schema name and table name in the Source, Target, or
Lookup transformation in a mapping.
Connection attributes
. The
schema attribute in the connection properties.
Object metadata
. The object type
selected in the Source, Target, or Lookup transformation in a mapping.