Jump to: navigation, search

ETL_AUDIT System

The ETL_AUDIT table records information about every iWD Data Mart ETL job that has been executed. Various ETL jobs use the information stored in this table to determine when task processing ended from the last run of the job and thus, where to resume processing.

The ETL_AUDIT System Table
Field Data Type Description
ETL_AUDIT_KEY int Primary key of this table.

PARENT_ETL_AUDIT_KEY
Introduced: 9.0.013
int Points to the first ETL_AUDIT_KEY in the job run.
ETL_AUDIT_START_TIME
Introduced: 9.0.011
datetime Date and time when the job started.
ETL_AUDIT_FINISH_TIME
Renamed: 9.0.011 (previously ETL_AUDIT_TIME)
datetime Date and time when the job finished.

DURATION
Introduced: 9.0.011
int Calculated value, in seconds, that counts the time that has elapsed from the time at which the job was started to the time at which it was finished.
STATUS
Introduced: 9.0.011
Describe the job status, one of the following:
  • FINISHED
  • IN PROGRESS
  • FAILED
BATCH_ID int Batch number, for jobs that process data in batches (such as GTL_DM_load_intraday). Each batch job has its own ETL audit record.
DATA_SOURCE_TYPE varchar(16) Primary source of the job data; either config, task, or datamart. (Data from the Interaction Server Events Log database is classified as task data source type.)
DATA_SOURCE_NAME varchar(1000) Database ID (equals database JDBC URL).
PROCESS_NAME varchar(255) The name of the job that is processing the records (such as, load_config).
FIRST_EXTRACTED_EVENT_ID bigint ID that starts the range of event IDs that are processed.
LAST_EXTRACTED_EVENT_ID bigint ID that ends the range of event IDs that are processed.
BATCH_LAST_EVENT_ID bigint ID of the last event in the batch. Used to set the starting point for the next batch.
LAST_INTERVAL_DATE_KEY int Last date interval that is processed by the aggregate ETL scripts.
LAST_INTERVAL_TIME_KEY int Last time interval that is processed by the aggregate ETL scripts.
This page was last edited on June 30, 2020, at 16:16.
Comments or questions about this documentation? Contact us for support!