Consider the following rules and guidelines when you enable dynamic schema change handling:
Do not include an override for the target or source from the advanced properties. If the mapping is enabled for dynamic schema handling and contains a source or target override, the mapping fails with the following error:
Exception: class java.lang.NullPointerException occurred in writeMetadata
However, you can specify an SQL override in mappings enabled for dynamic schema handling.
When you set the
keep_column_case=on
parameter in the connection properties to fix dynamic schema changes for column names that are not in upper case letters, ensure to use this connection only for mappings in advanced mode. Data Integration uses this connection to run the mapping on an
advanced cluster
. If you use the same connection in mappings that are not in advanced mode, it results in an error.
In advanced mode, do not specify the
Truncate Target Table
option in the Target transformation properties. If a column is renamed or added in the source schema and if you configure the
Truncate Target Table
and also set the
Additional Write Runtime Parameters
for the Target transformation, the mapping fails with the following error: