X hits on this document

423 views

0 shares

1 downloads

0 comments

46 / 131

Integrate

Integrate

Restrictions:

When working with journalized data, if the "Synchronize deletions from journal" is executed, the deleted rows on the target are committed.

Compatible only with Oracle 9i database and above.

Comparison of data is made using the Update Key defined in the interface. It has to be set.

The TRUNCATE option cannot work if the target table is referenced by another table (foreign key).

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.

Deletes are commited regardless of the COMMIT option.

The option ANALYZE_TARGET will evaluate correct statictics only if COMMIT is set to Yes. Otherwise, the IKM will gather statistics based upon the old data.

To use this IKM, the staging area must be on the same data server as the target.

IKM Oracle Incremental Update (MERGE)

Integrates data in an Oracle target table in incremental update mode. This IKM creates a temporary staging table to stage the data flow. It then uses the Oracle MERGE native SQL command to compares its content to the target table to load the records accordingly. It also allows performing data integrity check by invoking the CKM.

Inserts and updates are done by the bulk set-based MERGE operator to maximize performance. Therefore, this IKM is optimized for very large volumes of data.

Consider using this IKM if you plan to load your Oracle target table to insert missing records and to update existing ones.

To use this IKM, the staging area must be on the same data server as the target.

IKM Oracle Incremental Update (PL Integrates data in an Oracle target table in incremental

SQL)

update mode. This IKM creates a temporary staging table to

stage the data flow. It then compares its content to the target table to guess which records should be inserted and which others should be updated. It also allows performing data integrity check by invoking the CKM.

Inserts and updates are done in row-by-row PL/SQL processing. Therefore, this IKM is not recommended for large volumes of data.

Consider using this IKM if you plan to load your Oracle target table to insert missing records and to update existing ones and if your records contain long or binary long object (BLOB) data types.

Knowledge Modules Reference Guide

46/131

Document info
Document views423
Page views426
Page last viewedSat Dec 10 23:01:44 UTC 2016
Pages131
Paragraphs3942
Words42855

Comments