X hits on this document

370 views

0 shares

1 downloads

0 comments

9 / 131

Integrate

Integrate

Load

the processing activities.

IKM SQL to File Append

The following options are used for the logging mechanism:

LOG_LEVEL: This option is used to set the granularity of the data logged.

The following log levels can be set:

  • o

    0: nothing to log

    • o

      1: any JDBC action will be indicated such as ‘select action’, ‘delete action’, ‘insert action’…

    • o

      2: in addition to level 1, all records that generate an error will be logged

    • o

      3: in addition to level 2, all processed records will be logged

LOG_FILE_NAME: Full path to the log file used.

MAX_ERRORS:Specify the maximum number of errors. The IKM process stops when the maximum number of errors specified in this option is reached.

Important Note: This Knowledge Module is NOT RECOMMENDED when using LARGE VOLUMES. Other specific modules using Bulk utilities (SQL*LOADER, BULK INSERT...) or direct links (DBLINKS, Linked Servers...) are usually more efficient.

Integrates data in a target file from any SQL compliant staging area in replace mode.

Consider using this IKM if you plan to transform and export data to a target file. If your source datastores are located on the same data server, we recommend using this data server as staging area to avoid extra loading phases (LKMs)

To use this IKM, the staging area must be different from the target.

IKM SQL to SQL Append

Integrates data in a target SQL compliant table from any SQL compliant staging area in replace mode.

Consider using this IKM if you plan to use a staging area different from the target. If most of your source datastores are located on the same data server, we recommend using this data server as staging area to avoid extra loading phases (LKMs)

To use this IKM, the staging area must be different from the target.

LKM File to SQL

Loads data from an ASCII or EBCDIC File to any SQL compliant database used as a staging area. This LKM uses the Agent to read selected data from the source file and write the result in the staging temporary table created dynamically.

Consider using this LKM if one of your source datastores is an ASCII or EBCDIC file. Use specific LKMs for your target staging area whenever possible as they are more optimized for performance. For example, if you are loading to an Oracle database, use “LKM File to Oracle (SQLLDR)” or “LKM File to Oracle (EXTERNAL TABLE)” instead.

Knowledge Modules Reference Guide

9/131

Document info
Document views370
Page views373
Page last viewedTue Dec 06 14:43:05 UTC 2016
Pages131
Paragraphs3942
Words42855

Comments