This
IKM integrates data into an Oracle target table, aggregating data by time
periods. New records are inserted, and changes to existing periods will be
handled by deleting the old data for the period and then inserting the new
data. Data for old periods may be purged. Data can be controlled by isolating
invalid data in the error table and recycling when fixed.
Prerequisites
for using this IKM are the following:
·
The
Delete Period Type option must specify which period type the target table is
based on.
·
For
Calendar Periods, the target table must contain a column for the period end
date key:
- Must be a
date wid type (YYYYMMDD).
- Must be
named PERIOD_END_DT_WID or otherwise identified in the mapping using the UD1
check box.
·
For
MCAL calendar periods the target table must contain:
- Period
key, usually MCAL_PERIOD_WID or MCAL_DAY_WID, otherwise identified in the
mapping using UD1 check box.
- Calendar
key, usually MCAL_CAL_WID, otherwise identified in the mapping using UD2 check
box.
·
Bitmap
indexes on the above mentioned key columns.
Calendar
periods of day, week, month, quarter and year are supported. For these period
types, the incremental load assumes the interface is loading data for the
current period only. The incremental update works by deleting any existing data
for the current period. Then, the fresh set of data for the current period is
inserted. Optionally, data older than a specified age can be automatically
purged with the Periods to Keep option. The option Periods To Delete does not
apply for calendar periods.
MCAL
calendar periods of MCAL Day and MCAL Period are supported. For these period
types, the incremental load assumes the interface is loading data for the
current period and a given number of previous periods. The incremental update
works by deleting any existing data for these periods. Then, the fresh set of
data is inserted.The option Periods To Delete controls how many previous
periods (as well as the current one) are being incrementally loaded by the
interface. For example, a value of 1 would indicate reprocessing the current
and previous period every load. The Periods to Keep option does not apply for
MCAL calendar periods.
·
Delete Period
Type - The type of calendar periods the target table is based on.
It is used for deleting current periods to reprocess or obsolete periods to
purge. Valid values are the following:
Calendar periods: CAL_DAY, CAL_WEEK, CAL_MONTH, CAL_QTR,
CAL_YEAR.
MCAL
calendar periods: MCAL_DAY, MCAL_PERIOD.
Prerequisites
for using this option are the following:
o
For
calendar periods, the target table must contain a column for the period end
date key
- Must be
named PERIOD_END_DT_WID or otherwise identified in the mapping using the UD1 check
box.
- Must be a
date wid type (YYYYMMDD).
o
For
MCAL calendar periods the target table must contain:
- Period
key, usually MCAL_PERIOD_WID or MCAL_DAY_WID, otherwise identified in the
mapping using UD1 check box.
- Calendar
key, usually MCAL_CAL_WID, otherwise identified in the mapping using UD2 check
box.
·
Periods to Delete - This option is for configuring additional
functionality for the MCAL calendar periods only. It must be left at the
default value (0 - delete current period only) for calendar periods. Setting
this option to a value N > 0 will delete exactly N Julian periods of data
based on the delete period type. For example, setting to 1 will mean the
current and previous periods are deleted.
·
Periods to Keep - This option is for configuring additional functionality
for the calendar periods only. It must be left at the default value (0 - keep
all periods) for calendar periods. Setting this option to a value N > 0 will
delete data in periods which are exactly N julian periods older than the current
julian period
·
Hints - This IKM allows the passing of hints
into the generated SQL. For more information, see the article titled
"Oracle Business Intelligence Applications Version 11.1.1.7.1 Performance
Recommendations (Doc ID 1539322.1)" on My Oracle Support.
·
Alter
Session List -
Applies a list of alter session commands to the session used by the KM.
Commands should be separated by a semi-colon and without the "ALTER
SESSION" prefix. Each command should be prefixed SRC or TGT depending on
whether it should be executed on the source connection (relevant if using an
LKM) or the target connection. For example:
· SRC set TRACEFILE_IDENTIFIER='ODI_TRACE'; SRC set events '10046 TRACE NAME CONTEXT FOREVER, LEVEL 8'; TGT set TRACEFILE_IDENTIFIER='ODI_TRACE_TGT';
No comments:
Post a Comment