Description:
The scenario LOAD_PARTITION_METADATA must be run prior to executing the interface
Restrictions:
For many key columns exclude from I$ index by marking with UD1
1. Integration Knowledge Module
2. Integrates data into a partitioned Oracle
fact or aggregate table in incremental update mode.
3. Inexistent rows are inserted; already
existing rows are updated.
4. Data can be controlled. Invalid data is
isolated in the Error Table and can be recycled.
5. When using this module with a journalized
source table, it is possible to synchronize deletions.
Pre-requisites:The scenario LOAD_PARTITION_METADATA must be run prior to executing the interface
Restrictions:
1. When working with journalized data, if
the "Synchronize deletions from journal" is executed, the deleted
rows on the target are committed
2. Comparison of data is made using the
Update Key defined in the interface. It must be set.
3. The TRUNCATE option cannot work if the
target table is referenced by another table (foreign key)
4. 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.
5. Deletes are commited regardless of the
COMMIT option
6. The ANALYZE_TARGET option will
evaluate correct statistics only if COMMIT is set to Yes. Otherwise, the IKM
will gather statistics based on old data.
ExtraFor many key columns exclude from I$ index by marking with UD1
No comments:
Post a Comment