Known Issues for Data Integration

There are some known issues with workarounds in Data Integration.

Symptom Area Affected Problem Solution
.mdo file corrupt Replication .mdo file corrupt issue is due to having the same table mapping with different column mappings in two pipelines. If there are two distributions with the same table mapping and you change the column mapping of table mapping present in first distribution, the column mapping of the same table mapping in second distribution also gets updated.
Non-supported data types Replication Map Column screen will show non-supported data types, but you can still provide customized column mapping for the same. These data types will be ignored during commit operation. Non-supported data types will be greyed out.
java.lang.NullPointerException Replication Exception occurs when we have same source tables. Same source tables can be in the following two scenarios:
  • Duplicate table mapping across two different pipelines (without touching Column Mapping).
  • One to many case for example same source table and two different target topics across two different pipelines.
  • Do a force deploy which creates a new mdo file. The kernel starts successfully.

    OR

  • Delete mdo file and start the Kernel to create a new mdo file. The kernel starts successfully.
Distribution key exceeds data type Distribution Key Distribution Key cannot have a Character dataype with a length that exceeds (254 for DB2 and 255 for MS SQL Server).