Performing an initial load of an Oracle Communications Data Model is a multistep process.
PKG_INTRA_ETL_PROCESS
. This package has a public procedure, Run
, and also has private procedures for executing derived intra-ETL programs, refreshing aggregate materialized views, refreshing data mining models, and refreshing OLAP cubes. The public procedure, Run
, invokes all the private procedures.Describes how the manner in which you perform an initial load of the foundation layer of Oracle Communications Data Model tables, (that is, the reference, lookup, and base tables) varies depending on whether you are using an application adapter.
You perform an initial load of the foundation layer as follows:
If you are using an application adapter for Oracle Communications Data Model, then you use that adapter to load the foundation layer.
If you are not using an application adapter, then you perform the initial load of the foundation layer using source-ETL that you create.
To perform an initial load of access layer of the Oracle Communications Data Model warehouse (that is, the derived and aggregate tables, materialized views, OLAP cubes, and data mining models) perform the following steps:
The intra-ETL workflow is implemented using PL/SQL package, PKG_INTRA_ETL_PROCESS
. This package has a public procedure, Run
, and also has private procedures for executing derived intra-ETL programs, refreshing aggregate materialized views, refreshing data mining models, and refreshing OLAP cubes. The public procedure, Run
, invokes all the private procedures.
Before executing intra-ETL workflow, update ETL parameters in DWC_ETL_PARAMETER
and DWC_OLAP_ETL_PARAMETER
tables. It is suggested to not use ocdm_sys
user to update ETL parameter tables and executing intra-ETL workflow. Ask your DBA to unlock ocdm_user for performing these tasks using the following commands:
ALTER USER ocdm_user account unlock;
Use ocdm_user
user to update ETL parameter tables and execute intra-ETL workflow. In a SQLPLUS session, connect to ocdm_user
user:
sqlplus ocdm_user/ocdm_user@SID
Update ETL parameter tables:
SQL> UPDATE OCDM_SYS.DWC_ETL_PARAMETER SET from_date_etl = < The beginning date of the ETL period >, to_date_etl = < The ending date of the ETL period > WHERE process_name = 'OCDM-INTRA-ETL' ; / SQL> commit; SQL> UPDATE OCDM_SYS.DWC_ETL_PARAMETER SET from_date_etl = < The beginning date of the ETL period >, to_date_etl = < The ending date of the ETL period > WHERE process_name = 'DWD_CUST_DNA' ; / SQL> commit; SQL> UPDATE OCDM_SYS.DWC_ETL_PARAMETER SET from_date_etl = < The beginning date of the ETL period >, to_date_etl = < The ending date of the ETL period > WHERE process_name = 'DWD_CNT_DAY' ; / SQL> commit; SQL> UPDATE OCDM_SYS.DWC_ETL_PARAMETER SET from_date_etl = < The beginning date of the ETL period >, to_date_etl = < The ending date of the ETL period > WHERE process_name = 'OCDM-DWA-MV-DATE' ; / SQL> commit; SQL> UPDATE OCDM_SYS.DWC_ETL_PARAMETER SET from_date_etl = < The beginning date of the ETL period >, to_date_etl = < The ending date of the ETL period > WHERE process_name = 'BUILD-MINING-MODELS' ; / SQL> commit; SQL> UPDATE OCDM_SYS.DWC_ETL_PARAMETER SET build_method = <>, cubename = <>, . . . . fcst_st_yr = <>, fcst_end_yr = <> ; / SQL> commit;
Run the following command to execute intra-ETL workflow:
SQL> BEGIN OCDM_SYS.PKG_INTRA_ETL_PROCESS.Run; END; /
The status of each activity is tracked using DWC_INTRA_ETL_ACTIVITY
table. The status of each cube data loading is tracked using DWC_OLAP_ACTIVITY
table. The status of the entire intra-ETL workflow process is tracked using DWC_INTRA_ETL_PROCESS
table.