![]() In addition, you can use the OEM Cube Viewer facility to carry out ad-hoc querying of the data in the cube. Creating the cube using OEM again runs a number of PL/SQL CWM_* packages to register the cube's CWMLITE metadata, and you can then browse the cube's measures by double-clicking on the cube icon and drilling down into the cube. In addition to creating dimensions, OEM allows you to create Cubes, which bring together a fact table and a number of dimensions into a logical 'cube'. The dimensions that OEM creates are different to the dimensions created by using the CREATE DIMENSION statement, or by using Oracle Warehouse Builder - whilst the CREATE DIMENSION statement is used in their intial creation, a number of PL/SQL CWM_* procedures are run afterwards to register CWMLITE metadata. These dimensions are made up of columnns from relational tables, with the relationship between columns (and their hierarchies) being explicitly specified so that this can be later used by the query rewrite mechanism. You can right-click on the 'dimensions' node and create CWMLITE metadata to construct dimensions for your warehouse or data mart. This area is effectively a CWMLITE metadata browser, allowing you to create, view and amend ROLAP data structures such as cubes, dimensions, measures and summaries. OEM 9.2 has a new node in the navigator view called 'Warehouse', with areas for Measures Folders, Cubes and Dimensions. Option 1 - Using Enterprise Manager and Analytic Workspace Manager.īefore you can use any of the new GUI tools for building an analytic workspace, you first have to build a ROLAP version of the cube, and this ROLAP version is used as the template for building the analytic workspace. A guide to this process can be found elsewhere on the weblog. ![]() Prior to all this, and before you install either the AWM or OWB, you'll need to download a list of patches from metalink to enable all the analytic workspace PL/SQL API packages. Option 2 requires you to license 9iDS, and then separately download the updated version of OWB, known as 9.2. Option 1 can be used using tools that you get 'out of the box' with Oracle 9i Release 2, although you'll need to download the Analytic Workspace Manager application separately from OTN. Build the dimensions and cubes using Oracle Warehouse Builder, then use the 9i OLAP Metadata Transfer Bridge to transfer the structures and data into an Analytic Workspace.Build the dimensions and cubes using Oracle Enterprise Manager, then use Analytic Workspace Manager to transfer the structures and data into an Analytic Workspace.The two approaches I took to building the analytic workspace were as follows They work in broadly similar ways, using the same underlying AWM_ PL/SQL packages supplied as part of the 9.2.0.4.1 patchset, but there are a few subtle differences that are worth bearing in mind. ![]() Rather than manually building and populating analytic workspaces using the OLAP Worksheet and OLAP DML, you can now build and populate them using extensions to Oracle Warehouse Builder, or using the Analytic Workspace Manager add-in to Enterprise Manager. ![]() Now that the 9.2.0.4.1 Oracle Database patchset is available, together with the Analytic Workspace Manager and OWB9.2, I thought I'd take a look at the different options available for populating an Analytic Workspace and making the data available for querying using SQL.
0 Comments
Leave a Reply. |