Forum Stats

  • 3,875,939 Users
  • 2,266,998 Discussions
  • 7,912,379 Comments

Discussions

Designing cubes. OWB vs AWM

Alex.UA
Alex.UA Member Posts: 67 Blue Ribbon
edited Mar 29, 2016 10:41AM in OLAP

Hi all,

There are two UI tools provided by Oracle to create cubes based on cube organized MVs.

AWM allows to create cubes in analytic workspace in particular schema and then deploy them.

"Enable Materialized View Refresh pf the Cube" should be checked to generate MVs.

(more details - Oracle Database 11g: The Top Features for DBAs and Developers | Data Warehousing and OLAP)

105029.gif

On the other hand OWB also allows to do the same.

But in this case there is no need to create Analytic workspace and all the metadata will be stored in owbsys schema.

"ROLAP: with Cube MVs" should be checked to generate MVs.

(more details - https://blogs.oracle.com/warehousebuilder/entry/owb_11gr2_cube_organized_materialized_views)

owb_olap5_2.jpg

Both approaches allow export/import metadata and promote changes to production. As well as automation of this process.

So the question is which tool is preferable to use for designing cubes and why?

Thanks

953225Izik Warn

Answers

  • Alex.UA
    Alex.UA Member Posts: 67 Blue Ribbon
    edited Mar 29, 2016 10:41AM

    I investigated a bit further so the answer is: preferable tool is AWM because OWB will be deprecated.

    Oracle recommends using ODI instead of OWB but ODI can be used only to process data for existing cubes but not designing cubes from scratch.

    953225Izik Warn
This discussion has been closed.