Executing the ETL Load Plans in ODI

To load data from the source to their target tables in the data mart, run the Load Plan packaged with Oracle Argus Analytics ODI.

Perform the following tasks in ODI Studio:

  1. Navigate to the Operator tab.
  2. In the Load Plans and Scenarios sections, right-click Load Plan: LP_FL_AN for full loads or LP_IL_AN for Incremental Loads option and select Execute/Run.
  3. Provide the values for the Load Plan variables, as mentioned in the table below.

    Table 4-1 ODI Parameters

    Parameters Load Type Description Allowed Values

    VAR_ALN_PERIOD_FROM_DATE

    Full Load

    The start date of the days to populate from in the W_DAY_D/PVA_DAY table. It should be in the format: MM/DD/RRRR

    Date values such as:

    01/01/1980

    Recommended value:

    01/01/1980

    VAR_ALN_PERIOD_TO_DATE

    Full Load

    The end date of the days to populate till in the W_DAY_D/PVA_DAY table. It should be in the format: MM/DD/RRRR

    Date values such as: 12/31/2019

    Recommended Value: 12/31/2019

    VAR_INT_TRUNCATE_STAGE

    Both

    This variable is used to decide whether to truncate the stage table or not and is useful in multiple Argus Safety DB support

    Valid values:0: Does not truncate Stage table1: Truncate Stage table Should be specified as 1 always in case of Single Argus Safety Instance as source information

    Recommended Value: 1

    VAR_INT_COLLECT_STATISTICS

    Both

    This variable is used to decide whether the statistics of the target tables need to be collected or not.

    Default Value: 1

    Values Accepted: 0,1

    0: Load Plans will not collect statistics

    1: Load Plans will collect statistics after loading data

    VAR_ALN_ENTERPRISE

    Both

    The specific Enterprise ID to run the ETL for.

    -1: Runs the ETL for the entire Warehouse0: Runs the ETL for all the enterprises the user ($$p_user_name) has access toInteger Value [1,2,3, etc]: Runs the Incremental ETL for the specified Enterprise only.

    Note: For Full Load, this value has to be -1.

    VAR_ALN_ERROR_REJECT_LIMIT

    Both

    This variable is used to set the number of rows that will be tracked in the respective error tables prior to aborting the ETL in case of errors.

    Valid Values:Positive Integer numbers: (E.g. 0, 100, 1000, etc.)UNLIMITED: All the error records are logged

    Recommended Value: UNLIMITED

    VAR_ALN_USER_NAME

    Both

    The user name for which the ETL shall use to set the VPD Context for the specified enterprise in the parameter: VAR_ALN_ENTERPRISE. This value should be passed inside single quotes: such as 'username'.

    Default value: 'admin'

    VAR_INT_RAISE_ERROR

    Both

    Setting this variable to 0 or 1 will appropriately either stop a Load Plan/Interfaces/Mappings or continue the same when data errors are encountered during the load.

    0: Do not raise data error when encountered during ETLs1: Raise data error when encountered during ETLs

    Recommended Value: 1

    VAR_INT_CONFIG_DAYS

    Incremental Load

    Reduces the incremental extract window by the specified number of days. Example: Extract all changed rows between LAST_EXTRACT_DATE and (SYSDATE - $$p_config_days)

    Integers

    Recommended Value: 0

    VAR_INT_REKEY_FACT

    Incremental Load

    To rekey fact tables in case data in the W_HS_MAPPING_S defined for match and merge has changed

    0: Will not rekey the Fact tables 1: Will rekey the Fact tables

    Recommended Value: 0

    VAR_INT_OVERRIDE_LAST_EXTRACT_DATE

    Incremental Load

    Specify a Date value in the format MM/DD/RRRR if you want to override the last extract date for the Incremental Data for the specific ETL run. This will cause reload of data in the warehouse that are present in the given incremental extract window.

    Date values such as:01/01/1900 or 12/23/2012

    Recommended Value: NULL (Change this with discretion)

    VAR_INT_INCLUDE_PSEUDO_ST_CODE_FLG

    Both

    The parameter defines whether to include the workflow states present between the Locking record and the Unlocking record of a case in the Case Workflow State Fact table.

    Date values is 1.1: Include the Workflow States between Locking and Unlocking records of the case.0: Exclude the Workflow States between Locking and Unlocking records of the case.

  4. Click OK to run the Load Plan.