This chapter describes the steps required to administer the ETL process using the Oracle Data Integrator Studio (ODI Studio).
The AM.zip file contains pre-configured ETL scheduling in Inactive mode.
The Incremental ETL is used to load the delta data. You can execute an Incremental ETL either by executing Load Plan LP_INC_AM, or scheduling an ETL to run at the configured time interval.
To schedule a Load Plan, execute the following steps:
In the Designer tab, navigate to Load Plans and Scenarios section and expand LP_INC_AM (Load Plan for Incremental ETL).
Right-click Scheduling and select New Scheduling.
The Load Plan Scheduling dialog box appears.
You can set options given in the Status and Execution sections, according to the requirements to schedule the Load Plan.
The process of monitoring the Incremental ETL using the Oracle Database Integrator Studio is same as the process of monitoring the Initial ETL.
For step-by-step information related to monitoring the Incremental ETL process using the ODI Studio, see Section 7.2, "Monitoring Initial ETL Process: ODI Studio."
This section describes the steps required to manage the Incremental ETL process using the Oracle Database Integrator Studio.
Open the Oracle Data Integrator Studio, and click Connect to Repository.
The Oracle Data Integrator Login dialog box appears.
In the Oracle Data Integrator Login window:
From the Login Name drop-down list, select the ODI Work Repository name.
In the User field, enter the name of the ODI user.
In the Password field, enter the password for the ODI user.
Click OK.
The Oracle Data Integrator screen.
From the left pane, select the Operator tab.
Expand the Load Plans and Scenarios section.
The LP_INC_AM option represents the load plan for the Incremental ETL process for Argus Mart.
Right-click the LP_INC_AM option.
The drop-down menu appears.
Click Run.
The Start Load Plan dialog box appears.
In the Start Load Plan screen:
From the Context drop-down list., select CTX_ARGUSMART.
From the Logical Agent drop-down list, select LA_AM.
From the Log Level drop-down list, select a level.
Click OK.
The Information dialog box with the Load Plan Started confirmation message appears.
Click OK.
You can verify the status of the ETL process by navigating to the Load Plan Executions section and expanding the Load Plan folder. You can view the status of the Load Plan in Green color with tilted s, which signifies that the ETL session is in progress.
Right-click the Load Plan, which you want to stop, in the Load Plan folder of the Load Plan Executions section. This displays a menu, as shown in the following figure:
Select Stop Normal. This displays the Stop Load Plan dialog box.
Select PA_AM from the Physical Agent drop-down list.
Click OK. This stops the execution of the Load Plan.
You can verify the status of the ETL process by navigating to the Load Plan Executions section and expanding the Load Plan folder. You can view the status of the Load Plan in Red color with the X symbol, which signifies that the ETL session is not in progress, as highlighted in the following figure:
Note:
You must verify in Argus Mart database if the ETL session has been successfully ended after this step.Restarting the Incremental ETL process enables you to start the ETL process from the last execution step where it was stopped or failed.
Right-click the Load Plan, which you want to restart, in the Load Plan folder of the Load Plan Executions section. This displays a menu, as shown in the following figure:
Click Restart. This displays the Restart Load Plan dialog box.
Select PA_AM from the Physical Agent drop-down list.
Select the required log level from the Log Level drop-down list.
Click OK. This displays the Information dialog box with the Load Plan restarted message.
Click OK.
This adds another Load Plan, with the same name as that of the stopped ETL, in the Load Plan folder of the Load Plan Executions section. However, this instance of the ETL Process is in Green color, which signifies that the ETL is in progress, as highlighted in the following figure:
Once the ETL process is complete, the Load Plan is displayed in Green color with a completed symbol, as highlighted in the following figure:
The complete ETL process is divided into two major phases: Staging and Mart. The Mart phase starts only when the Staging phase is complete.
If an ETL process fails, you have the option of continuing the process from the failed step or executing it again from the beginning of ETL.
This section explains the steps to resume a failed ETL from the failed step and to execute it again from the beginning of ETL.
This section comprises the following sub-sections:
If the last execution step of the failed or stopped ETL belongs to the Staging phase, the ETL resumes from the failed or stopped point, as shown in the following figure:
If the last execution step of the failed or stopped ETL belongs to the Mart phase, the ETL resumes from the first step of the Mart phase and not from the failed or stopped point.
The process to continue the failed Incremental ETL from the failed step is exactly the same as that of the process of restarting the Incremental ETL after stopping it.
See the Restarting the Incremental ETL section for the step-by-step procedure to continue the failed Incremental ETL from the failed step.
The process to restart the failed Incremental ETL from the beginning is exactly the same as that of the process of running the Incremental ETL.
However, before restarting the ETL, you must log on to the Oracle SQL Developer or SQLPlus (or SQL Prompt) using the Argus ETL User credentials and execute the following statements:
EXEC pkg_sm_stage_util.p_set_cmn_profile_value ('DATABASE', 'ODI_ETL_STATUS', '0');EXEC pkg_sm_stage_util.p_set_cmn_profile_value ('DATABASE', 'ETL_SM_ITERATION_NUMBER', NULL);
COMMIT;
To verify the successful execution of these statements, you can execute the following Select statements:
SELECT * FROM rm_cmn_profile_global WHERE KEY = 'ODI_ETL_STATUS';
The entry for the Value column must be 0 after executing this statement.
SELECT * FROM rm_cmn_profile_global WHERE KEY = 'ETL_SM_ITERATION_NUMBER';
The entry for the Value column must be blank after executing this statement.
See the Running the Incremental ETL section for the step-by-step procedure to restart the failed Incremental ETL from the beginning of ETL.