Description :
- Integration Knowledge Module
- Integrates data into a SQL compliant database target table in truncate / insert (append) mode.
- Data can be controlled. Invalid data is isolated in the Error Table and can be recycled.
Restrictions:
- When working with journalized data, if the "Synchronize deletions from journal" is executed, the deleted rows on the target are committed regardless of the COMMIT option
- The OBI_TRUNCATE_TABLE and OBI_COLLECT_STATS options are not implemented on all RDBMs
- The OBI_TRUNCATE_TABLE option cannot work if the target table is referenced by another table (foreign key)
- When using the RECYCLE_ERRORS option, you have to set an Update Key for your interface.
- When using this module with a journalized source table, data are automatically filtered to not include source deletions.
- The FLOW_CONTROL and STATIC_CONTROL options call the Check Knowledge Module to isolate invalid data (if no CKM is set, an error occurs). Both options must be set to NO in the case when an Integration Interface populates a TEMPORARY target datastore.
- Integration Knowledge Module
- Integrates data into a SQL compliant database target table in truncate / insert (append) mode.
- Data can be controlled. Invalid data is isolated in the Error Table and can be recycled.
Restrictions:
- When working with journalized data, if the "Synchronize deletions from journal" is executed, the deleted rows on the target are committed regardless of the COMMIT option
- The OBI_TRUNCATE_TABLE and OBI_COLLECT_STATS options are not implemented on all RDBMs
- The OBI_TRUNCATE_TABLE option cannot work if the target table is referenced by another table (foreign key)
- When using the RECYCLE_ERRORS option, you have to set an Update Key for your interface.
- When using this module with a journalized source table, data are automatically filtered to not include source deletions.
- The FLOW_CONTROL and STATIC_CONTROL options call the Check Knowledge Module to isolate invalid data (if no CKM is set, an error occurs). Both options must be set to NO in the case when an Integration Interface populates a TEMPORARY target datastore.
No comments:
Post a Comment