Why cann't i see the cube that i create with owb ??

Question

hello:
owb version:10.1.0.4
db version:10.2.1.0.1
Business Intelligence 10.1.2.0.2
windows 2003
i use owb create 3 dimensions and 1 cube,and deploy on target schema successfully.
and export the metadata to eex file, and import eex file into discoverer administrator ,when create workbook i can see the cube created with owb;
then i selected ORACLE BI DISCOVERER option to connect target_schema,so i can see my cube and dimension;
but when i selected ORACLE BI DISCOVERER FOR OLAP option to connect target_schema, login in successful , but when i create my workbook ,cann't see my cube and demension
why for this,and how to do it,so i can see them?
pls help me!

Answer 1

There are three ways to deploy a multi-dimensional model and the final model selection depends on the database options you have purchased and they tools you have at your displosal:
relational access - You can define relational cubes and dimensions within OWB and deploy these to your target schema. The dimensions are implemented as query re-write objects and can be viewed within the view USER_DIMENSIONS. The data relating to the dimension is stored within a simple relational table, either as a snowflake or star schema format. The cube object does not really exist as such but is implemented as fact table. Typically, access to this type of implementation is via Discoverer and you need to create a Discoverer EUL to view the deployed tables. Within Discoverer you will not see the dimension or cubes listed but you will see tables and/or views relating to your deployed schema.
The Discoverer Bridge will create the eex/EUL file to install the schema within Discoverer Administrator. However, you must use Discoverer Plus/Viewer with the relational connection details.
As an FYI the management of Discoverer EULs is integrated within OWB 10gR2.
OLAP models - OWB also supports the deployment a schema as either a relational OLAP model or within an analytic workspace (this creates a MOLAP model). The OLAP deployment can be viewed only using Discoverer OLAP, however, management of the schema does not require an EUL and the administration is managed by Discoverer Administrator. All the administration is managed by OWB. To access a multi-dimensional model using Discoverer OLAP you must first run the OLAP bridge from within OWB. This will deploy all the required metadata for Discoverer OLAP to connect to your schema.
However, I would recommend you urgently upgrade to OWB10gR2 as this provides additional tuning options for the OLAP data model that are not present in your current version of OWB 10.1.0.4. Unfortunately, with your current OWB version building an OLAP model is a two stage process, a form of data staging. You need to create a relational target schema first and then replicate that target schema within an OLAP model. OWB10gR2 allows you to map data from a source object directly to a multi-dimensional object with no need to stage the data.
If you cannot upgrade at this point my suggestion would be to use OWB to design the target relational schema and then use Analytic Workspace Manager (AWM) to design your OLAP schema for Discoverer OLAP access. AWM will provide you with all the tools for tuning and managing your OLAP model within a 10gR2 database schema.
Once you have upgraded to OWB10gR2 you can stop using AWM as all the tuning features are within OWB.
Hope this makes sense and is helpful.
Keith