Table of Contents

Search

  1. Preface
  2. Data integration tasks
  3. Mapping tasks
  4. Dynamic mapping tasks
  5. Synchronization tasks
  6. Data transfer tasks
  7. Replication tasks
  8. Masking tasks
  9. Masking rules
  10. PowerCenter tasks

Tasks

Tasks

Schema change handling

Schema change handling

You can choose how
Data Integration
handles changes that you make to the schema of some data object types.
By default, if you make changes to the schema,
Data Integration
does not pick up the changes automatically. If you want
Data Integration
to refresh the data object schema every time the
mapping
task runs, you can enable dynamic schema handling.
A schema change includes one or more of the following changes to the data object:
  • Fields are added.
  • Fields are deleted.
  • Fields are renamed.
  • Field data type, precision, or scale is updated.
Data Integration
automatically refreshes the schema for relational objects every time the task runs. If you want to dynamically refresh the schema for other object types, enable dynamic schema change handling on the
Schedule
page
or in the
Advanced
area of the
Runtime Options
page when you configure the task.
The following table describes the schema change handling options:
Option
Description
Asynchronous
Default.
Data Integration
refreshes the schema when you edit the mapping or mapping task, and when
Informatica Intelligent Cloud Services
is upgraded.
Dynamic
Data Integration
refreshes the schema every time the task runs.
Applicable for source, target, and lookup objects of certain connector types. For some connector types,
Data Integration
can only refresh the schema if the data object is a flat file.
If you select this option, the file object format must be delimited.
Not applicable to hierarchical data.
To see if a connector supports dynamic schema change handling, see the help for the appropriate connector.
If you update fields in the source object and you enable dynamic schema handling, be sure to update the Target transformation field mapping.
Data Integration
writes Null to the target fields that were previously mapped to the renamed or deleted source fields. If you use a target created at run time, update the target object name so that
Data Integration
creates a new target when the task runs. The task fails if
Data Integration
tries to alter a target created in a previous task run.

0 COMMENTS

We’d like to hear from you!