See "Customizing Intra-ETL for Oracle Communications Data Model" for more information on the intra-ETL.ĮTL Architecture for Oracle Communications Data Model Source-ETLĮTL (or EL-T, that is, Extract, Load and Transform) first extracts data from the original sources, assures the quality of the data, cleans the data, and makes the data consistent across the original sources. ![]() You can modify the default intra-ETL to populate a customized access layer from a customized foundation layer. Oracle Communications Data Model does include intra-ETL. ETL that populates the access layer (that is, the derived tables, aggregate tables, materialized views, OLAP cubes, and data mining models) using the data in the foundation layer is known as intra-ETL. See "ETL for the Foundation Layer of an Oracle Communications Data Model Warehouse" for more information on creating source-ETL. Unless you are using an application adapter for Oracle Communications Data Model, you must create source-ETL yourself using your understanding of your operational and other source systems and your customized Oracle Communications Data Model. Oracle Communications Data Model does not include source-ETL scripts. ETL that populates the staging layer (if any) and the foundation layer (that is, the base, reference, and lookup tables) with data from the operational system is known as source ETL. As illustrated by Figure 4-1, you use two types of ETL (extraction, transformation and loading) to populate these layers: ![]() ![]() The Role of ETL in the Oracle Communications Data Modelįigure 2-1, "Layers of an Oracle Communications Data Model Warehouse" illustrated the three layers in Oracle Communications Data Model warehouse environment: the optional staging layer, the foundation layer, and the access layer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |