Skip Headers

Oracle® Communications Data Model Reference 11g Release 2 (11.2) Part Number E15886-05 |
Home | Book List | Contents | Index | Contact Us

Previous | Next
| PDF · Mobi · ePub

# A Control Tables

Some tables are defined in the ocdm_sys schema and use a DWC_ prefix, but are not part of Oracle Communications Data Model. You use the DWC_ control tables when processing the model. For example when loading data or when monitoring errors.

This appendix includes the following sections:

- Intra-ETL Load Parameters Control Table

- Intra-ETL OLAP Mapping Control Table

- Intra-ETL Monitoring Process Control Tables

## Intra-ETL Load Parameters Control Table

Use the ocdm_execute_wf.sh program to manually execute the Intra-ETL. Before you run the Intra-ETL, for an incremental load, you must update the Oracle Communications Data Model Relational ETL parameters in DWC_ETL_PARAMETER table so that this information can be used when loading the relational data. This program prompts for several environment parameter values. And reads ETL parameters from DWC_ETL_PARAMETER table, as shown in Table A-1, and DWC_OLAP_ETL_PARAMETER table, as shown in Table A-2.

The PKG_DWD_*_MAP loads data from Oracle Communications Data Model base tables into the Oracle Communications Data Model derived tables. These packages read relational ETL parameters from the DWC_ETL_PARAMETER table.

You update the parameters in `DWC_ETL_PARAMETER` control table in the `ocdm_sys` schema so that this information can be used when loading the derived and aggregate tables and views.

Table A-1 describes the valid values for the DWC_ETL_PARAMETER table.

Table A-1 DWC_ETL_PARAMETER Table

Column | Description
--- | ---
Process_name | OCDM-INTRA-ETL
from_date_etl | The start date of ETL period.
to_date_etl | The end date of ETL period.
load_dt | The date when this record are populated.
last_updt_dt | The date when this record are last updated
last_updt_by | The user who last updated this record

## Intra-ETL OLAP Mapping Control Table

The OLAP MAP mapping that loads OLAP cube data invokes the analytic workspace build function from the PKG_OCDM_OLAP_ETL_AW_LOAD package. This package loads data from Oracle Communications Data Model aggregate materialized views into the Oracle Communications Data Model analytical workspace and calculates the forecast data. The PKG_OCDM_OLAP_ETL_AW_LOAD reads OLAP ETL parameters from the DWC_OLAP_ETL_PARAMETER table.

You update the Oracle Communications Data Model OLAP ETL parameters in `DWC_OLAP_ETL_PARAMETER` control table in the `ocdm_sys` schema so that this information can be used when loading the OLAP cube data.

Table A-2 describes the valid values for the DWC_OLAP_ETL_PARAMETER table. For more information on the values to specify when performing an initial load of OLAP cube data or when refreshing the OLAP cubes after an initial load, see Oracle Communications Data Model Implementation and Operations Guide.

Table A-2 ETL Parameters in the DWC_OLAP_ETL_PARAMETER Table

Column Name | Description
--- | ---
PROCESS_NAME | OCDM_OLAP_ETL
BUILD_METHOD | Cube build/refresh method specified by one of the following values: `C` specifies a complete refresh which clears all dimension values before loading. `?` specifies a fast refresh if possible; otherwise, a complete refresh. (Default) `P` specifies recomputation of rows in a cube materialized view that are affected by changed partitions in the detail tables. `S` specifies a fast solve of a compressed cube. A fast solve reloads all the detail data and re-aggregates only the changed values.
CUBENAME | Specifies the cubes you want to build: `ALL` builds all of the cubes in the Oracle Communications Data Model analytic workspace. `cubename`[[`|``cubename`]...] specifies one or more cubes, as specified with `cubename`, to build.
MAXJOBQUEUES | A decimal value that specifies the number of parallel processes to allocate to this job. (Default value is `4`.) The number of parallel processes actually allocated by a build is controlled by the smallest of these factors: Number of cubes in the build and the number of partitions in each cube. Setting of the MAXJOBQUEUES argument. Setting of the JOB_QUEUE_PROCESSES database initialization parameter.
CALC_FCST | Whether or not to calculate forecast cubes: `Y` specifies calculate forecast cubes. `N` specifies do not calculate forecast cubes.
NO_FCST_YRS | A decimal value that specifies how many years forecast data you want to calculate. (This parameter takes effect only if you set CALC_FCST to `'Y'`)
FCST_MTHD | `AUTO` which invokes the Geneva forecasting expert system which tests all of possible forecasting methods and options for these methods and chooses and uses the method that best fits the data.
FCST_ST_YR | A value specified as `yyyy` which is the "start business year" of a historical period. Forecast program will calculate the forecast data based on the historical data in this period.
FCST_END_YR | A value specified as `yyyy` which is the "end business year" of a historical period. Forecast program will calculate the forecast data based on the historical data in this period.
OTHER1 | Reserved for future use. (Default value is `NULL`.)
OTHER2 | Reserved for future use. (Default value is `NULL`.)

## Intra-ETL Monitoring Process Control Tables

The two control table in the `ocdm_sys` schema, `DWC_INTRA_ETL_PROCESS` and `DWC_INTRA_ETL_ACTIVITY`, monitor the execution of the Intra-ETL process.

Table A-3 contains column name information for DWC_INTRA_ETL_PROCESS. Table A-4 contains column name information for `DWC_INTRA_ETL_ACTIVITY`.

Table A-3 DWC_INTRA_ETL_PROCESS Columns

Columns Name | Data Type | Not Null | Remarks
--- | --- | --- | ---
PROCESS_KEY | NUMBER(30) | Yes | Primary Key, System Generated Unique Identifier
PROCESS_START_TIME | DATE | Yes | ETL Process Start Date and Time
PROCESS_END_TIME | DATE | ETL Process End Date and Time |
PROCESS_STATUS | VARCHAR2(30) | Yes | Current status of the process
FROM_DATE_ETL | DATE | Start Date (ETL) - From Date of the ETL date range |
TO_DATE_ETL | DATE | End Date (ETL) - To Date of the ETL date range |
LOAD_DT | DATE | Record Load Date - Audit Field |
LAST_UPDT_DT | NUMBER(30) | Last Update Date and Time - Audit Field |
LAST_ UPDT_BY | VARCHAR(30) | Last Update By - Audit Field |

Table A-4 DWC_INTRA_ETL_ACTIVITY Columns

Columns Name | Data Type | Not Null | Remarks
--- | --- | --- | ---
ACTIVITY_KEY | NUMBER(30) | Yes | Primary Key, System Generated Unique Identifier
PROCESS_KEY | NUMBER(30) | Yes | Process Key. FK to DWC_INTRA_ETL_ PROCESS table
ACTIVITY_NAME | VARCHAR2(50) | Yes | Activity Name or Intra ETL Program Name
ACTIVITY_DESC | VARCHAR2(500) | Activity description |
ACTIVITY_START_TIME | DATE | Yes | Intra ETL Program Start Date and Time
ACTIVITY_END_TIME | DATE | Intra ETL Program End Date and Time |
ACTIVITY_STATUS | VARCHAR2(30) | Yes | Current status of the process
ERROR_DTL | VARCHAR2(2000) | Error details if any |
LOAD_DT | DATE | Record Load Date - Audit Field |
LAST_UPDT_DT | NUMBER(30) | Last Update Date and Time - Audit Field |
LAST_ PDT_BY | VARCHAR(30) | Last Update By - Audit Field |