X hits on this document

377 views

0 shares

1 downloads

0 comments

10 / 131

Load

LKM SQL to SQL

Load

LKM SQL to SQL (JYTHON)

Load

LKM SQL to SQL (row by row)

Loads data from a SQL compliant database to a SQL compliant staging area. This LKM uses the Agent to read selected data from the source database and write the result into the staging temporary table created dynamically.

Consider using this LKM if your source datastores are located on a SQL compliant database different from your staging area. Use specific LKMs for your source and target staging area whenever possible as they are more optimized for performance. For example, if you are loading from an Oracle source server to an Oracle staging area, use “LKM Oracle to Oracle (dblink)” instead.

Loads data from a SQL compliant database to a SQL compliant staging area. This LKM uses Jython scripting to read selected data from the source database and write the result into the staging temporary table created dynamically. This LKM allows you to modify the default JDBC data types binding between the source database and the target staging area by editing the underlying Jython code provided.

Consider using this LKM if your source datastores are located on a SQL compliant database different from your staging area and if you plan to specify your own data type binding method.

Use specific LKMs for your source and target staging area whenever possible as they are more optimized for performance. For example, if you are loading from an Oracle source server to an Oracle staging area, use “LKM Oracle to Oracle (dblink)” instead.

Loads data from any ISO-92 database to any ISO-92 compliant target database. This LKM uses a Jython script to read selected data from the database and write the result into the target temporary table, which is created dynamically. It loads data from a staging area to a target and indicates the state of each processed row.

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

Knowledge Modules Reference Guide

10/131

Document info
Document views377
Page views380
Page last viewedTue Dec 06 20:04:19 UTC 2016
Pages131
Paragraphs3942
Words42855

Comments