The following identifies some of the major changes from prior releases.
Analytic Workspace Manager in Release 10.2.0.3 provides a Sparsity Advisor, which examines the source data and makes recommendations for defining OLAP cubes that provide the best performance. The functionality of calculation plans has been enhanced to provide post-load forecasting, allocation, and aggregation. Analytic Workspace Manager also supports Java add-ins, so that any Java developer can extend and customize the tools in Analytic Workspace Manager.
Oracle OLAP in Oracle Database 10g Release 2 (10.2) provides numerous performance enhancements and extensions to the dimensional data model.
Analytic Workspace Manager 10.2 supports Calculation Plans and multiple languages. Compressed composites provide support for partial computation and non-additive operators.
Analytic workspaces are included with other database objects in transportable tablespaces.
See Also:Chapter 12 for information about backing up analytic workspaces
Oracle OLAP 10.1.0.4 provides a simpler approach to building and enabling analytic workspaces while introducing the more powerful analytic tools of the OLAP engine into the build process.
Analytic workspaces are still stored in LOB tables in Oracle Database 10g, but in a different format that supports partitioning and multiple writers.
The Model View in Analytic Workspace Manager 10g enables you to define the logical model of your analytic workspace directly in database standard form. You no longer create logical models in the OLAP Catalog for building analytic workspaces. Analytic Workspace Manager supports a wider range of schema designs than the OLAP Catalog.
See Also:Chapter 3 for instructions on using the Model View
Analytic Workspace Manager and the PL/SQL
DBMS_AWM package generate a new version of standard form metadata that supports the new features of Oracle Database 10g.
SELECT statements for the views of an analytic workspace are stored in the analytic workspace itself. Enablement no longer requires the creation of database objects.
The OLAP API and OracleBI Beans query the Active Catalog views, which display the database standard form metadata stored in analytic workspaces. Enablement no longer requires the creation of OLAP Catalog