Conversion errors

You must resolve any conversion errors in your root job before you optimize it.

Type conversion errors

When you compile and run your job, check for implicit conversion warnings in the job log. Resolve the reported issues in the job design by using a Transformer stage with explicit type conversion functions. You must use explicit, rather than implicit, conversions to ensure that the conversions are correctly mapped to their SQL equivalents.

Nullable to non-nullable column conversion errors

Use the Transformer stage functions NullToZero, NullToEmpty, and NullToValue in your job designs to ensure correct non-null values. This process is especially important for database sources that feed a Join stage with an outer join, which will output NULL values for columns of unmatched rows unless the columns are explicitly not nullable.

Character set conversion errors

Ensure that Client Character Set property of a connector is compatible with the CHARACTER SET specifications in all source and target table columns. For example, if a source database table column is defined with CHARACTER SET UNICODE, then the Client Character Set on the source connector must specify a multi-byte character set such as UTF8 to ensure enough space in internal string buffers.