This discussion is archived
2 Replies Latest reply: Sep 25, 2013 12:27 AM by Papai RSS

difference between IKM oracle incremental update and IKM oracle incremental update(PL SQL)

Papai Newbie
Currently Being Moderated

Hi,

    What is the difference between  IKM oracle incremental update and IKM oracle incremental update(PL SQL) and IKM oracle incremental update(row by row).

 

 

Thanks

Papai

  • 1. Re: difference between IKM oracle incremental update and IKM oracle incremental update(PL SQL)
    Bhabani Ranjan Guru
    Currently Being Moderated

    The only difference is that second one uses plsql for incremental update. It also handle the clob issues pretty well.

     

    If you need to know more you can read the description section of each KM.

     

    IKM Oracle Incremental Update (PL SQL)

    -------

    Description:

    - Integration Knowledge Module

    - Integrates data into an Oracle target table in incremental update mode using PL/SQL.

    - Inexistent rows are inserted; already existing rows are updated.

    - Data can be controlled. Invalid data is isolated in the Error Table and can be recycled.

    - This KM uses PL/SQL to perform the inserts and updates so that long and blob columns are supported. Please refer to the restrictions.

    - When using this module with a journalized source table, it is possible to synchronize deletions.

     

     

    Restrictions:

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

    - The data is updated even if not changed (update all)

    - The row count (nb of inserts/updates) is not available as the transactions are performed using PL/SQL

    - 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.

    - The option FLOW_TABLE_OPTION is set by default to NOLOGGING. Set it to whitespace if the interface runs on an Oracle 7 database

    - Deletes are commited regardless of the COMMIT option

     

     

    IKM Oracle Incremental Update

    -------------

    DESCRIPTION:

      - Integrates data into an Oracle target table in incremental update mode.

      - Inexistent rows are inserted; already existing rows are updated.

      - Data can be controlled. Invalid data is isolated in the Error Table and can be recycled.

      - When using this module with a journalized source table, it is possible to synchronize deletions.

     

     

    REQUIREMENTS:

      - The Update Key defined in the interface is mandatory.

     

     

    RESTRICTIONS:

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

      - 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.

      - The option FLOW_TABLE_OPTION is set by default to NOLOGGING. Set it to whitespace if the interface runs on an Oracle 7 database

      - Deletes are commited regardless of the COMMIT option

      - 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.

      - Default UPDATE option is TRUE, which means by default it's assumed that there is at least one non-key column specified in a target datastore.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points