To create cube materialized views in different schemas: To create cube materialized views in the user's own schema: To create dimensional objects in different schemas: To create dimensional objects in the user's own schema: The following roles and system privileges are required to use this package: The BUILD procedure loads data into the cubes and dimensions from their data sources and performs whatever processing steps are needed to prepare the data for querying. The IMPORT_XML procedure creates an analytic workspace with its cubes and cube dimensions from an XML template.
Several other DBMS_CUBE subprograms provide a SQL alternative to Analytic Workspace Manager for creating an analytic workspace from an XML template and for refreshing the data stored in cubes and dimensions. Using a graphical tool named Analytic Workspace Manager, you can enhance the cube with analytic content or create the metadata for new cubes and cube dimensions from scratch. The metadata for cubes and dimensions is defined in XML documents, called templates, which you can derive from relational materialized views using the CREATE_CUBE or DERIVE_FROM_MVIEW functions. These subprograms are discussed in "Using SQL Aggregation Management". Several DBMS_CUBE subprograms support the creation and maintenance of cube materialized views as a replacement for relational materialized views. Multidimensional objects and analytics are available with the OLAP option to Oracle Database.Ĭubes can be enabled as cube materialized views for automatic refresh of the cubes and dimensions, and for query rewrite. They are stored in a container called an analytic workspace. Cubes and cube dimensions are first class data objects that support multidimensional analytics.
0 kommentar(er)
