OLAP - OWB - BIBEANS

Hi All, (92028OWB - 9205DB - 10GBIBEANS)
We're getting a wierd error from bibeans-olap in our time dimension.
Dimension (in a nutshell)
Year num
Year_des varchar
Quart num
Quart_des varchar
Cal_key num (unique key - sk) at month level.
Month_des varchar
The dimension works fine if we build it manually in OEM, but when we use the bridge or add another attribute to the lowest level. We start getting ORA-932 and BIB -9509
errors: expected CHAR got DATE or expected CHAR got NUM.
[We get these errors when we try and build a crosstab in
JDev.  They pop right up after we define our elements for the crosstab report.]
Does anyone know where this error is comming from - like OLAP in the database? Somewhere is the CWM did we map it incorrectly -the CWM code came from the bridge - is there a bug? every other dim seems to work very well.
We dont want to use the Time dim that came with OWB - we'd like to use our own. Is there a way to trace this
to find out which Column is giving us the problem?
Any help would be greatly appriciated.
Thanks, -Gus

Hi Gus,
Hmmm, not sure, but it may have something to do with how the bridge generates the time dimension attributes. In this case it may be the case that we generate an incorrect indicator and so have a date where Beans expect a string...
This is getting slightly complex so I suggest that you log a tar on this one, support can dig deeper into the issue than we on the forum.
Jean-Pierre

Similar Messages

  • How can i convert java application of bibeans to java applet?

    Hi Bibeans PMTeam,
    Bibeans provide two type client:java application and web client(JSP/Servlet),because web client's function is weaker than java app,so we want to convert java app to java applet,thus,we can embed java applet into web browser(our system framework is in web browser).
    That is,we want one applet client that commution with a server side service(can by socket,just like oracle 9i form service)that provide the data that applet need,or the applet connect to olap server and bibeans catalog server by socket(this need security authentication if olap server,bibeans catalog,web server is not in one machine).
    so we need you provide whole resolve scheme,thanks a lot,if this answer is not clarity,please connect:[email protected],thanks a lot!

    hi tomsong
    well, in my experience 20mb are quite large for an applet. also take into account that you need a certain jvm that supports this type of application (my guess is that internet explorers native vm isnt an option)
    i personally would tend to deliver the functionality via java webstart (look at the sunsite):so you can centrally manage the software, download it once and opertae an application on your client (i mean an APPLICATION and not an applet)
    regarding 2: well but there is NO bibean service in ias: so you have to open the former mentioned jdbc connection to the olap service from your client
    for the availability: you have to check with the pm team
    in the meantime: what about the following approach: give power users a java application and lightweight or random users a handy html client ?
    regards,
    thomas

  • Error in Running a dimension ( BIB-9509 Oracle OLAP did not create cursor.)

    oracle.dss.dataSource.common.QueryRuntimeException: BIB-9509 Oracle OLAP did not create cursor.
    oracle.express.ExpressServerExceptionError class: OLAPI
    Server error descriptions:
    DPR: Unable to create server cursor, Generic at TxsOqDefinitionManagerSince9202::crtCurMgrs4
    OES: ORA-00938: not enough arguments for function
    , Generic at TxsRdbRandomAccessQuery::TxsRdbRandomAccessQuery
    help is appreciated
    Thanks, Prasad

    This is the patch: 2529822
    "Best Practices for Tabular Cube Aggregation & Query Operations". Thanks very much for your advice.
    I followed the instructions in the document, but it did not seem to make a difference when
    trying to follow the tutorial instructions and using the SALES measure.
    However, I selected the stock price measures and it worked ok.
    Is there a size limit here? I am looking at Oracle OLAP and BIBeans to replace our Cognos installation,
    which is expensive and unreliable on unix. Of course our managers and customers want every dimension
    across a huge fact table to be available for end users...

  • BIBeans error in OWB.

    Hi All
    I created 2 dimensions and one cube and all are deployed sucessfully with Deploy Catlog only Option.
    The problem is when i click on the Data Viewer it gives following error:
    ENT-06965: Creation of BIBeans MetadataManager from OLAP and the Catalog informatation has failed.
    1.I need to install BIBeans in my meachine or it is installed with OWB itself?
    2.Any steps to work with source in one database and target at other database?
    Please help me regarding this

    Change to DEPLOY ALL, redeploy and try again.
    Cheers
    Si

  • ENT-06965: Creation of BIBeans MetadataManager from OLAP .... has failed

    Hi!
    I tried to change a dimension definition in OWB (also changed its corresponding mapping). I deployed the modifications succesfully and executed the mapping.
    However, when I try to see the data from the Design Center I get this error:
    ENT-06965: Creation of BIBeans MetadataManager from OLAP and the Catalog informatation has failed.
    I have never worked with BIBeans or deployed anything to AW (I use a relational implementation).
    There is this post (ENT-06965: Creation of BIBeans MetadataManager from OLAP .... has failed.
    which says that I have to use some PL/SQL packages owned by OLAPSYS, but I don`t know which one.
    Does anybody know how to solve this problem?
    Thank you,
    Yorgos

    Hi Thomas,
    Just look at the above link (ENT-06965: Creation of BIBeans MetadataManager from OLAP .... has failed. you can find there the solution.
    I`m copying here the relevant part:
    "You may have invalid OLAP metadata left over within your CWM catalogs".
    "there are some views owned by OLAPSYS user that show all the dimension and cubes that are "OLAP enabled"
    "You will need to use the following packages:
    CWM2_OLAP_DIMENSION.DROP_DIMENSION(owner, dimension_name)
    CWM2_OLAP_CUBE.DROP_CUBE(owner, cube_name)
    Use this view to find the names of installed dimensions : ALL$OLAP2_DIMENSIONS
    Use this view to find the names of installed cubes : ALL$OLAP2_CUBES"

  • How to connect OLAP in OWB.

    Hi,
    Can any one help me regarding the connection of Measures in OLAP schema.
    Thanks in advance...

    Hi
    You will see that in the view created (ORDER_CHG_VIEW for example in Mark's post) there is an operation column exposed with the op that was done on the source I for example indicating insert, D - delete, U - update. This operation column can be used and in OWB you can have a complex mapping graph with many targets and process the operation in a splitter and have a splitgroup for inserts, updates and deletes for example. The target table has a Loading Type property in mapping, by default it is INSERT, but you can INSERT/UPDATE (MERGE), DELETE, UPDATE, etc.
    For example you can have SourceTable -> Splitter -> Multiple Target Tables, each group in the splitter could process inserts, updates, deletes for example or whatever you desire.
    In OWB 11gR2 you can use the code template framework and get ootb support for CDC using log miner (or a basic trigger based alternative useful for demos or getting started).
    Mark has another post for this release highlighting this:
    http://www.rittmanmead.com/2009/10/10/changed-data-capture-and-owb11gr2/
    Cheers
    David

  • High-level view of steps for 10g OWB-OLAP to Discoverer

    I would greatly appreciate ANY feedback to the following steps. These are not necessarily correct or the best way to do this. I am attempting to take source data, use OWB, create the analytical workspace, and from there have the metadata available and used by Discoverer.
    This is rather high-level, feel free to jump in anywhere.
    We are trying to see if we can get away with NOT using the Analytical workspace manager (AWM) if possible. With that in mind, we are trying to make the most of the process with OWB & OLAP.
    Is this possible to do without ever using the AWM? Can we go end to end (source data--->discoverer final reporting) primarily using OWB to get to the point where we can use the metadata for Discoverer?
    Can anyone relate experiences perhaps that would make me want to consider using the AWM at certain points instead?
    Most importantly, if I do use this methodology, would I be safe after everything has been setup? WOuld I want to consider using AWM at a later point for performance reasons while I am using Discoverer? Or would OWB be helpful as well in some aspects in maintenance of data? Any clue on how often I might need to rebuild, and if so, what to use in that case to minimize time?
    Thanks so much for any insight or opinion on anything I have mentioned!

    Hi Gregory,
    I guess the answer is that this depends. My first question is whether you are looking at a Relational OLAP or Multi Dimensional OLAP solution? This may change the discussion slightly, but just lets look at some thoughts:
    In essence you can use the OWB bridge to generate the AW objects (cubes etc). If you do that (for either ROLAP or MOLAP) you will get the AW objects enabled for querying, using any OLAPI query tool, like BI Beans or the new Discoverer for OLAP. The current OWB release does not run the discoverer enabler (creating views specifically written for EUL support in Disco classic).
    So if you are looking at Disco classic you must use the AWM route...
    The other things that you must be aware off is that the OWB technology is limited to cloning the relational objects for now. This means that you will create a new model based on your existing data. If you want to tweak the objects generated you will probably need to go to the underlying code in either scenario.
    So if you want to create calculated measures for example you could generate a cube with OWB, create a "dummy measure" and add the formula in OLAP DML. The same will go for some other objects you may want to create such as text measures...
    The benefit of creating place holder or dummy measures is that the metadata is completely in order, you simply change the measure's behavior...
    For the future (the beta starts relatively soon) OWB will support much more modeling, like logical cubes and you can then directly deploy to OLAP. Also the mappings are transparent to the storage. So you map to a logical cube and OWB will implement the correct to load either OLAP or relational targets.
    We will also start supporting calculated measures, sparsity definitions, partioning and compression on cubes, as we will support parallel building of cubes.
    Hope this gives you some insight!
    Jean-Pierre

  • Can The New OWB 9.0.4 Actually Populate A 9i OLAP Cube?

    Hi there,
    I guess this is one for Igor Machin or Jean-Pierre Dijcks.
    I've seen today on OTN that OWB 9.0.4 is now available, and had a look through the white paper written by Jean-Pierre, together with the accompanying OWB + 9i paper written by Shauna O'Boyle. What i'm particularly interested in is the 9i OLAP integration.
    Could you confirm for me whether 9.0.4 will actually generate the scripts to populate the 9i OLAP cube, or does it just create the OLAP metadata, as with 9.0.3.? If so, are this OLAP DML scripts, or PL/SQL?
    My guess is that the actual population of the 9i OLAP cube will have to wait for the Analytic Workspace Manager, which is coming with the database 9.2.0.2a patch, due in March. However, it'd be good news if this functionality was present in OWB 9.0.4.
    Many thanks
    Mark Rittman
    [email protected]

    Igor
    I've had a chance to install and look at OWB 904 now, and look through the manuals. I see that OWB can now populate the AW cube by using the inbuild PLSQL transformations, LOAD_OLAP_CUBE and LOAD_OLAP_DIMENSION (not sure on the names, haven't got the guide to hand but they're named something like this).
    Could you just confirm - will these work now, or will they only work when a future patch to Oracle is released? The manual doesn't make any note about needing a further patch, it seems to imply that it would work once OWB has been installed and Oracle 9.2 is used.
    thanks
    Mark

  • OWB 9.0.4 and OLAP

    Hi,
    I have questions regarding the OWB 9.0.4 and his OLAP features. I tried to set up an Analytical Workspace
    and OLAP objects (dimensions and a cube) as it was written in the OWB904UsersGuide. Therefore I created
    an PL/SQL script with the OWB Export Wizard. The script created the OLAP objects but I also got some errors,
    that several Identifiers need to be declared. Well, I thought it worked fine, cause when I checked the OLAP
    directory node in the OEM, I found my cube and dimensions there. But when I tried to load the OLAP objects
    with the WB_OLAP_LOAD_DIMENSION and WB_OLAP_LOAD_CUBE transformations from OWB I got the error that my dimensions are invalid, even if the OEM shows them as valid.
    I read several articles in the OWB and the OLAP forum about this issue and I'm a bit confused now. Does the OWB now support OLAP at all, and when will the post 9.2.0.3 patch be released?
    Is there an other way to convert the relational OWB starschema into an OLAP schema and to load it with data?
    Can I use BI Beans on the relational starschema without an working OLAP schema?
    Thanks in advance,
    Dirk

    Which version of the database is being used? The AW work involves a patch that has not yet been released. The OLAP 9.2.0.3 patch is due to be released in July, the exact
    release date is unknown.
    OWB provides the bridge which will populate the metadata for a relational OLAP cube in the OLAP catalog. BI Beans can be used on this relational cube. The bridge also supports cloning of this relational cube in an OLAP analytic workspace, both the metadata for the AW and the data loading programs are generated from the bridge. The OWB 9.0.4.10 patch has a number of improvements and bug fixes that will help deploying to OLAP. The OLAP 9.2.0.3 patch is due to be released in July, the exact
    release date is unknown.
    The OLAP metadata for ROLAP cubes can either be created using OWB, or through OEM or manually. If by OLAP schema
    you mean an AW, then either use OWB to clone the ROLAP cube in an AW, or use the Analytic Workspace Manager
    (AWM) that will clone the ROLAP cube and provide some more options or manually code up the OLAP DML metadata etc. Manual coding of the AW is a specialized task that involves substantial knowledge of OLAP DML (the Express SPL language) to write both the data object definitions and performant data loader programs, also the enabling of the AW through SQL for BI Beans is a complex task. All of these manual tasks are provided by both the OWB OLAP bridge and the AWM.
    For BI Beans, the ROLAP metadata must be populated in the OLAP catalog, so can be achieved using OWB to deploy the
    relational star schema then the OWB OLAP bridge to populate only the ROLAP metadata. OWB does this using CWM1 apis. BI Beans can be used on top of the ROLAP cube.

  • BiBeans Sample Olap Problem

    Hello ;
    I couldn't run the Bibeans sample.
    what can I do? which patch i must install?
    I Below is the output from running bi_checkconfig:,
    C:\oracle\ora92\bibeans\bi_checkconfig>bi_checkconfig -h oas -po 1521 -sid LOGOB
    IZ -u BIBDEMO -p BIBDEMO -o LOGOBIZ -q
    <?xml version="1.0" encoding="UTF-8" ?>
    - <BICheckConfig version="1.0.2.0">
    <Check key="JDEV_ORACLE_HOME" value="C:\oracle\ora92" />
    <Check key="JAVA_HOME" value="C:\Program Files\Java\j2re1.4.2_04" />
    <Check key="JDeveloper version" value="9.0.4.0.1407" />
    <Check key="BI Beans release description" value="BI Beans 9.0.4 Production Release" />
    <Check key="BI Beans component number" value="9.0.4.23.0" />
    <Check key="BI Beans internal version" value="2.7.5.32" />
    <Check key="host" value="oas" />
    <Check key="port" value="1521" />
    <Check key="sid" value="LOGOBIZ" />
    <Check key="user" value="BIBDEMO" />
    <Check key="olapservice" value="LOGOBIZ" />
    <Check key="Connecting to the database" value="Successful" />
    <Check key="JDBC driver version" value="9.2.0.4.0" />
    <Check key="JDBC JAR file location" value="C:\oracle\ora92\jdev\lib\patches" />
    <Check key="Database version" value="9.2.0.6.0" />
    <Check key="OLAP Catalog version" value="9.2.0.1.0" />
    <Check key="OLAP AW Engine version" value="9.2.0.1.0" />
    <Check key="OLAP API Server version" value="9.2.0.1.0" />
    <Check key="BI Beans Catalog version" value="N/A; not installed in BIBDEMO" />
    <Check key="OLAP API JAR file version" value="9.2" />
    <Check key="OLAP API JAR file location" value="C:\oracle\ora92\jdev\lib\ext" />
    <Check key="OLAP API Metadata Load" value="Unsuccessful" />
    <Check key="Failure Point" value="MDMLoadFailed" />
    - <Check key="StackTrace">
    - <![CDATA[
    ============================================================================
    1) Not supported by server versionORAOLAP9.2.0.1.0
    1) Not supported by server versionORAOLAP9.2.0.1.0
    ============================================================================
    oracle.express.idl.util.OlapiException: Not supported by server versionORAOLAP9.2.0.1.0
         at oracle.express.idl.ExpressMdmModule.MetadataProviderInterfaceStub.getMetadataXML(MetadataProviderInterfaceStub.java:317)
         at oracle.olapi.metadata.XMLFetcher9202.fetchXML(XMLFetcher9202.java:45)
         at oracle.olapi.metadata.MetadataFetcher.fetchBaseMetadataObjects(MetadataFetcher.java:167)
         at oracle.olapi.metadata.BaseMetadataProvider.fetchMetadataObject(BaseMetadataProvider.java:138)
         at oracle.olapi.metadata.BaseMetadataProvider.fetchMetadataObject(BaseMetadataProvider.java:95)
         at oracle.olapi.metadata.mdm.MdmMetadataProvider.getMetadataObject(MdmMetadataProvider.java:150)
         at oracle.olapi.metadata.mdm.MdmMetadataProvider.getRootSchema(MdmMetadataProvider.java:177)
         at oracle.express.mdm.MdmMetadataProvider.getRootSchema(MdmMetadataProvider.java:149)
         at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverImpl_92.getMdmSchema(MDMMetadataDriverImpl_92.java:1284)
         at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverImpl_92.getRoot(MDMMetadataDriverImpl_92.java:973)
         at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverImpl_92.addToObjectModel(MDMMetadataDriverImpl_92.java:2260)
         at oracle.dss.metadataManager.server.drivers.mdm.MDMMetadataDriverImpl.addToObjectModel(MDMMetadataDriverImpl.java:275)
         at oracle.dss.metadataManager.server.MetadataManagerImpl.buildObjectModel(MetadataManagerImpl.java:1099)
         at oracle.dss.metadataManager.server.MetadataManagerImpl.attach(MetadataManagerImpl.java:969)
         at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:876)
         at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:799)
         at BICheckConfig.checkConnection(BICheckConfig.java:277)
         at BICheckConfig.main(BICheckConfig.java:1348)
      ]]>
    </Check>
    </BICheckConfig>

    Hi again;
    I did the patch upgrade.
    here is the checkconfig result
    <?xml version="1.0" encoding="UTF-8" ?>
    - <BICheckConfig version="1.0.2.0">
    <Check key="JDEV_ORACLE_HOME" value="C:\oracle\ora92" />
    <Check key="JAVA_HOME" value="C:\Program Files\Java\j2re1.4.2_04" />
    <Check key="JDeveloper version" value="9.0.4.0.1407" />
    <Check key="BI Beans release description" value="BI Beans 9.0.4 Production Release" />
    <Check key="BI Beans component number" value="9.0.4.23.0" />
    <Check key="BI Beans internal version" value="2.7.5.32" />
    <Check key="host" value="oas" />
    <Check key="port" value="1521" />
    <Check key="sid" value="LOGOBIZ" />
    <Check key="user" value="BIBDEMO" />
    <Check key="olapservice" value="LOGOBIZ" />
    <Check key="Connecting to the database" value="Successful" />
    <Check key="JDBC driver version" value="9.2.0.4.0" />
    <Check key="JDBC JAR file location" value="C:\oracle\ora92\jdev\lib\patches" />
    <Check key="Database version" value="9.2.0.6.0" />
    <Check key="OLAP Catalog version" value="9.2.0.6.0" />
    <Check key="OLAP AW Engine version" value="9.2.0.6.0" />
    <Check key="OLAP API Server version" value="9.2.0.6.0" />
    <Check key="BI Beans Catalog version" value="N/A; not installed in BIBDEMO" />
    <Check key="OLAP API JAR file version" value="9.2" />
    <Check key="OLAP API JAR file location" value="C:\oracle\ora92\jdev\lib\ext" />
    <Check key="OLAP API Metadata Load" value="Successful" />
    <Check key="Number of metadata folders" value="0" />
    <Check key="Number of metadata measures" value="5" />
    <Check key="Number of metadata dimensions" value="2" />
    - <Check key="OLAP API Metadata">
    - <![CDATA[ ==============================================================================
    Type      Name (S=Schema, C=Cube, M=Measure, D=Dimension)         Status   
    ========= ======================================================= ============
    Folder... ROOT
    Measure..    STKPRICE_CLOSE                                       Successful
                 S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_CLOSE
    Measure..    STKPRICE_HIGH                                        Successful
                 S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_HIGH
    Measure..    STKPRICE_LOW                                         Successful
                 S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_LOW
    Measure..    STKPRICE_OPEN                                        Successful
                 S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_OPEN
    Measure..    STKPRICE_VOLUME                                      Successful
                 S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_VOLUME
    Dimension    Day                                                  Successful
                 S=BIBDEMO, D=DAY
    Dimension    Stock                                                Successful
                 S=BIBDEMO, D=STOCK
      ]]>
    </Check>
    </BICheckConfig>
    And I configured the Olap connection and database connection from jdeveloper (common.jpr)
    But when I run Linking_presentations
    i am getting the error message :
    oracle.dss.datautil.client.ManagerFactoryException: BIB-18007 A MetadataManager exception has occurred.
    oracle.dss.metadataManager.common.MetadataManagerException: BIB-10100 Cannot connect to the database. (Reason: See error BIB-16613)
         at oracle.dss.datautil.client.XMLManagerFactory.createQueryManager(XMLManagerFactory.java:191)
         at oracle.dss.datautil.client.ManagerFactoryImpl.lookupQueryManager(ManagerFactoryImpl.java:176)
         at oracle.dss.datautil.client.ManagerFactoryImpl.lookupMetadataManager(ManagerFactoryImpl.java:219)
         at oracle.dss.datautil.client.ManagerFactoryImpl.lookupManager(ManagerFactoryImpl.java:128)
         at samples.javaclient.bootstrap.BIFrame.connect(BIFrame.java:198)
         at samples.javaclient.linkingPresentations.BILinking.connect(BILinking.java:192)
         at samples.javaclient.bootstrap.BIFrame$9.actionPerformed(BIFrame.java:537)
         at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
         at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
         at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
         at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
         at javax.swing.plaf.basic.BasicButtonListener$ReleasedAction.actionPerformed(BasicButtonListener.java:301)
         at javax.swing.SwingUtilities.notifyAction(SwingUtilities.java:1530)
         at javax.swing.JComponent.processKeyBinding(JComponent.java:2438)
         at javax.swing.JComponent.processKeyBindings(JComponent.java:2473)
         at javax.swing.JComponent.processKeyEvent(JComponent.java:2401)
         at java.awt.Component.processEvent(Component.java:4909)
         at java.awt.Container.processEvent(Container.java:1569)
         at java.awt.Component.dispatchEventImpl(Component.java:3615)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1713)
         at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:627)
         at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:831)
         at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:741)
         at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:592)
         at java.awt.Component.dispatchEventImpl(Component.java:3506)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Window.dispatchEventImpl(Window.java:1606)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
    oracle.dss.metadataManager.common.MetadataManagerException: BIB-10100 Cannot connect to the database. (Reason: See error BIB-16613)
         at oracle.dss.metadataManager.client.MetadataManager.setConnectionObjects(MetadataManager.java:4015)
         at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:862)
         at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:799)
         at oracle.dss.datautil.client.XMLManagerFactory.createQueryManager(XMLManagerFactory.java:187)
         at oracle.dss.datautil.client.ManagerFactoryImpl.lookupQueryManager(ManagerFactoryImpl.java:176)
         at oracle.dss.datautil.client.ManagerFactoryImpl.lookupMetadataManager(ManagerFactoryImpl.java:219)
         at oracle.dss.datautil.client.ManagerFactoryImpl.lookupManager(ManagerFactoryImpl.java:128)
         at samples.javaclient.bootstrap.BIFrame.connect(BIFrame.java:198)
         at samples.javaclient.linkingPresentations.BILinking.connect(BILinking.java:192)
         at samples.javaclient.bootstrap.BIFrame$9.actionPerformed(BIFrame.java:537)
         at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
         at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
         at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
         at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
         at javax.swing.plaf.basic.BasicButtonListener$ReleasedAction.actionPerformed(BasicButtonListener.java:301)
         at javax.swing.SwingUtilities.notifyAction(SwingUtilities.java:1530)
         at javax.swing.JComponent.processKeyBinding(JComponent.java:2438)
         at javax.swing.JComponent.processKeyBindings(JComponent.java:2473)
         at javax.swing.JComponent.processKeyEvent(JComponent.java:2401)
         at java.awt.Component.processEvent(Component.java:4909)
         at java.awt.Container.processEvent(Container.java:1569)
         at java.awt.Component.dispatchEventImpl(Component.java:3615)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1713)
         at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:627)
         at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:831)
         at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:741)
         at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:592)
         at java.awt.Component.dispatchEventImpl(Component.java:3506)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Window.dispatchEventImpl(Window.java:1606)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
    oracle.dss.connection.common.ConnectionException: BIB-16601 Cannot connect to the database. (Reason: See error BIB-16613)
         at oracle.dss.connection.server.drivers.mdm.MDMConnectionDriverImpl.connect(MDMConnectionDriverImpl.java:157)
         at oracle.dss.connection.server.ConnectionImpl.connect(ConnectionImpl.java:286)
         at oracle.dss.connection.client.Connection.connect(Connection.java:409)
         at oracle.dss.connection.client.Connection.connect(Connection.java:326)
         at oracle.dss.metadataManager.client.MetadataManager.setConnectionObjects(MetadataManager.java:3997)
         at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:862)
         at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:799)
         at oracle.dss.datautil.client.XMLManagerFactory.createQueryManager(XMLManagerFactory.java:187)
         at oracle.dss.datautil.client.ManagerFactoryImpl.lookupQueryManager(ManagerFactoryImpl.java:176)
         at oracle.dss.datautil.client.ManagerFactoryImpl.lookupMetadataManager(ManagerFactoryImpl.java:219)
         at oracle.dss.datautil.client.ManagerFactoryImpl.lookupManager(ManagerFactoryImpl.java:128)
         at samples.javaclient.bootstrap.BIFrame.connect(BIFrame.java:198)
         at samples.javaclient.linkingPresentations.BILinking.connect(BILinking.java:192)
         at samples.javaclient.bootstrap.BIFrame$9.actionPerformed(BIFrame.java:537)
         at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
         at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
         at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
         at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
         at javax.swing.plaf.basic.BasicButtonListener$ReleasedAction.actionPerformed(BasicButtonListener.java:301)
         at javax.swing.SwingUtilities.notifyAction(SwingUtilities.java:1530)
         at javax.swing.JComponent.processKeyBinding(JComponent.java:2438)
         at javax.swing.JComponent.processKeyBindings(JComponent.java:2473)
         at javax.swing.JComponent.processKeyEvent(JComponent.java:2401)
         at java.awt.Component.processEvent(Component.java:4909)
         at java.awt.Container.processEvent(Container.java:1569)
         at java.awt.Component.dispatchEventImpl(Component.java:3615)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1713)
         at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:627)
         at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:831)
         at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:741)
         at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:592)
         at java.awt.Component.dispatchEventImpl(Component.java:3506)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Window.dispatchEventImpl(Window.java:1606)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
    oracle.dss.security.BISecurityException: BIB-16613 Database access error occurred while connecting to the OLAP instance.
    java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
         at oracle.dss.connection.server.drivers.mdm.MDMPluggableConnectionDriverImpl.connectToDatabase(MDMPluggableConnectionDriverImpl.java:141)
         at oracle.dss.connection.server.drivers.mdm.MDMPluggableConnectionDriverImpl.connect(MDMPluggableConnectionDriverImpl.java:40)
         at oracle.dss.connection.server.drivers.mdm.MDMConnectionDriverImpl.connect(MDMConnectionDriverImpl.java:149)
         at oracle.dss.connection.server.ConnectionImpl.connect(ConnectionImpl.java:286)
         at oracle.dss.connection.client.Connection.connect(Connection.java:409)
         at oracle.dss.connection.client.Connection.connect(Connection.java:326)
         at oracle.dss.metadataManager.client.MetadataManager.setConnectionObjects(MetadataManager.java:3997)
         at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:862)
         at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:799)
         at oracle.dss.datautil.client.XMLManagerFactory.createQueryManager(XMLManagerFactory.java:187)
         at oracle.dss.datautil.client.ManagerFactoryImpl.lookupQueryManager(ManagerFactoryImpl.java:176)
         at oracle.dss.datautil.client.ManagerFactoryImpl.lookupMetadataManager(ManagerFactoryImpl.java:219)
         at oracle.dss.datautil.client.ManagerFactoryImpl.lookupManager(ManagerFactoryImpl.java:128)
         at samples.javaclient.bootstrap.BIFrame.connect(BIFrame.java:198)
         at samples.javaclient.linkingPresentations.BILinking.connect(BILinking.java:192)
         at samples.javaclient.bootstrap.BIFrame$9.actionPerformed(BIFrame.java:537)
         at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
         at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
         at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
         at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
         at javax.swing.plaf.basic.BasicButtonListener$ReleasedAction.actionPerformed(BasicButtonListener.java:301)
         at javax.swing.SwingUtilities.notifyAction(SwingUtilities.java:1530)
         at javax.swing.JComponent.processKeyBinding(JComponent.java:2438)
         at javax.swing.JComponent.processKeyBindings(JComponent.java:2473)
         at javax.swing.JComponent.processKeyEvent(JComponent.java:2401)
         at java.awt.Component.processEvent(Component.java:4909)
         at java.awt.Container.processEvent(Container.java:1569)
         at java.awt.Component.dispatchEventImpl(Component.java:3615)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1713)
         at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:627)
         at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:831)
         at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:741)
         at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:592)
         at java.awt.Component.dispatchEventImpl(Component.java:3506)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Window.dispatchEventImpl(Window.java:1606)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
    java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:334)
         at oracle.jdbc.ttc7.TTC7Protocol.handleIOException(TTC7Protocol.java:3695)
         at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:352)
         at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:362)
         at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:536)
         at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:328)
         at java.sql.DriverManager.getConnection(DriverManager.java:512)
         at java.sql.DriverManager.getConnection(DriverManager.java:171)
         at oracle.dss.connection.server.drivers.mdm.MDMPluggableConnectionDriverImpl.connectToDatabase(MDMPluggableConnectionDriverImpl.java:127)
         at oracle.dss.connection.server.drivers.mdm.MDMPluggableConnectionDriverImpl.connect(MDMPluggableConnectionDriverImpl.java:40)
         at oracle.dss.connection.server.drivers.mdm.MDMConnectionDriverImpl.connect(MDMConnectionDriverImpl.java:149)
         at oracle.dss.connection.server.ConnectionImpl.connect(ConnectionImpl.java:286)
         at oracle.dss.connection.client.Connection.connect(Connection.java:409)
         at oracle.dss.connection.client.Connection.connect(Connection.java:326)
         at oracle.dss.metadataManager.client.MetadataManager.setConnectionObjects(MetadataManager.java:3997)
         at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:862)
         at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:799)
         at oracle.dss.datautil.client.XMLManagerFactory.createQueryManager(XMLManagerFactory.java:187)
         at oracle.dss.datautil.client.ManagerFactoryImpl.lookupQueryManager(ManagerFactoryImpl.java:176)
         at oracle.dss.datautil.client.ManagerFactoryImpl.lookupMetadataManager(ManagerFactoryImpl.java:219)
         at oracle.dss.datautil.client.ManagerFactoryImpl.lookupManager(ManagerFactoryImpl.java:128)
         at samples.javaclient.bootstrap.BIFrame.connect(BIFrame.java:198)
         at samples.javaclient.linkingPresentations.BILinking.connect(BILinking.java:192)
         at samples.javaclient.bootstrap.BIFrame$9.actionPerformed(BIFrame.java:537)
         at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
         at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
         at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
         at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
         at javax.swing.plaf.basic.BasicButtonListener$ReleasedAction.actionPerformed(BasicButtonListener.java:301)
         at javax.swing.SwingUtilities.notifyAction(SwingUtilities.java:1530)
         at javax.swing.JComponent.processKeyBinding(JComponent.java:2438)
         at javax.swing.JComponent.processKeyBindings(JComponent.java:2473)
         at javax.swing.JComponent.processKeyEvent(JComponent.java:2401)
         at java.awt.Component.processEvent(Component.java:4909)
         at java.awt.Container.processEvent(Container.java:1569)
         at java.awt.Component.dispatchEventImpl(Component.java:3615)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1713)
         at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:627)
         at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:831)
         at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:741)
         at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:592)
         at java.awt.Component.dispatchEventImpl(Component.java:3506)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Window.dispatchEventImpl(Window.java:1606)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
    *******************************************************

  • Bibean tutorial olap connection gives ora 942

    Hi,
    I'm working my way through the bibean tutorial.
    I have not made much progress.
    I'm stuck at the point where I create the BI Designer via wizard.
    I'm seeing this error:
    oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
    oracle.express.ExpressServerExceptionError class: OLAPI
    Server error descriptions:
    INI: ORA-00942: table or view does not exist
    in function: TxsRdbSelectStatement:execute(), Generic at TxsOqConnection::getDefaultDatabase
         at oracle.olapi.metadata.BaseMetadataProvider.<init>(BaseMetadataProvider.java:68)
         at oracle.olapi.metadata.mdm.MdmMetadataProvider.<init>(MdmMetadataProvider.java:127)
         at oracle.express.olapi.data.full.ExpressDataProvider.getDefaultMetadataProvider(ExpressDataProvider.java:912)
         at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverImpl_92.getMdmMetadataProvider(MDMMetadataDriverImpl_92.java:1134)
         at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverImpl_92.attach(MDMMetadataDriverImpl_92.java:811)
         at oracle.dss.metadataManager.server.drivers.mdm.MDMMetadataDriverImpl.attach(MDMMetadataDriverImpl.java:133)
         at oracle.dss.metadataManager.server.MetadataManagerImpl.buildObjectModel(MetadataManagerImpl.java:1085)
         at oracle.dss.metadataManager.server.MetadataManagerImpl.attach(MetadataManagerImpl.java:962)
         at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:866)
         at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:792)
         at oracle.dss.addins.designer.OLAPSource.test(OLAPSource.java:280)
         at oracle.dss.addins.wizard.connection.OlapTestPanel.testConnectionImpl(OlapTestPanel.java:49)
         at oracle.dss.addins.wizard.connection.TestConnectionPanel$2.construct(TestConnectionPanel.java:180)
         at oracle.jdeveloper.common.SwingWorker$2.run(SwingWorker.java:168)
         at java.lang.Thread.run(Thread.java:536)
    oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
    I used 'oemapp console' to look at my OLAP install.
    It shows cubes and dimensions owned by BIBDEMO so I see some hope.
    Here is info about my current setup:
    Linux localhost 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386 GNU/Linux
    Oracle9i Enterprise Edition Release 9.2.0.3.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.3.0 - Production
    Jdeveloper 9.0.3.1 build 1107
    java version "1.4.1_03"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_03-b02)
    Java HotSpot(TM) Client VM (build 1.4.1_03-b02, mixed mode)
    Any of you have any clues for me?
    Is it possible for me to connect to OLAP via sqlplus or pl/sql
    so I can eliminate Jdeveloper, JDBC, and Java as suspects?
    -atm

    hiAgain,
    I made progress today by installing 9.2.0.1 general purpose DB and then upgrading it to 9.2.0.3.
    Along the way I bumped into a bug with the DB:
    20:47:04 SQL> alter user bibcat identified by bibcat default tablespace users;
    alter user bibcat identified by bibcat default tablespace users
    ERROR at line 1:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-04045: errors during recompilation/revalidation of LBACSYS.LBAC_EVENTS
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: at line 2
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: at line 2
    google told me this:
    shutdown immediate;
    startup migrate;
    alter view lbacsys.lbac$all_table_policies compile;
    alter package lbacsys.lbac_events compile body;
    shutdown immediate;
    startup;
    Above commands ran okay for me.
    then,
    I ran rdbms/admin/utlrp.sql to recompile everything invalid.
    results of this looked good too:
    SELECT comp_name, status, substr(version,1,10) as version from dba_registry;
    -atm

  • OWB - making cubes / dimensions available for Disco OLAP

    ** Posted on the OWB forum initially but no replies **
    Hi, can someone explain (or tell where I can find documentation on) deploying cubes and dimensions for viewing in Disco Plus OLAP ?
    I have already derived other unrelated tables/views to business areas and have setup the security on those for Disco with no problem.
    The cubes and dims are defined as ROLAP and there is data in the underlying tables. I have granted SELECT access on the underlying tables to the required users. The dims and cubes have been deployed with the "Deploy All" setting
    If I log on as the eul owner into Disco Plus OLAP I can see the dims, cubes, measures and data with no problem, however if I log on with one of the other users I can log on ok (so no issues there) but have no objects to select from.
    I think the issue is to do with access not being granted to the new users to the relevant OLAP objects but do not know which ones.
    Thanks
    Paul

    Sorry folks, I got mixed up with another thread running somewhere else.
    With ROLAP, all you should need to do is grant select on all the dimension and cube tables. The metatdata for these tables is owned by OLAPSYS and stored in various tables starting with CWM_XXXX. Assuming your Disco user has been granted the role OLAP_USER (which should happen by default, and you confirmed this in a previous part of this thread) then everything should work.
    This might be caused by the CWM catalog not being up to date in terms of all the required metadata. Try connecting as the OLAPSYS user and then execute the following command
    exec CWM2_OLAP_METADATA_REFERESH.MR_REFERESH
    Once this has finished you might find that you cannot connect to Discoverer. This will be because the sample ROLAP schema owned by SH gets corrupted during installation and this can cause problems with the OLAP metadata. The only thing to do is to use the OLAP PL/SQL packages to delete the dimensions/cubes owned by SH then re run the command to refresh the metadata catalog - > CWM2_OLAP_METADATA_REFERESH.MR_REFERESH
    Security - You need to use the normal database label security with a ROLAP implementation as the AW PERMIT command is not available with ROLAP.
    Keith

  • BIBeans on WinNT - killer of previously working OLAP samples?

    I installed JDeveloper 9i RC and BiBeans RC. I applied all the latest OLAP patches and started working on BiBeans tutorial. I installed the demo database bibdemo schema and started creating OLAP connection required by Designer wizard. As other people already posted, the connection won't work until upcoming OLAP Patch for WinNT/2000.
    So I tried to go back to my previously working OLAP samples (generated from OLN OLAP API Fundamentals class) and noticed that they didn't work any more.
    Here is the output of the sample program:
    **** Obtained CORBA stub for /etc/OLAPServer/OLAPServer1 ****
    **** OLAP Services connection start ****
    **** OLAP Services connection made ****
    *** Metadata provider created ***
    Exception in thread main
    oracle.express.mdm.MetadataNotFoundException
         java.lang.String oracle.express.mdm.MetadataPropertyBag.getStringPropertyValue(java.lang.String)
         oracle.express.mdm.MdmObject oracle.express.mdm.MdmObjectFactory.createMdmObject(java.lang.String, oracle.express.mdm.MetadataPropertyBag, oracle.express.mdm.MdmMetadataProvider, oracle.olapi.data.source.DataProvider)
         oracle.express.mdm.MdmObject oracle.express.mdm.MdmMetadataProvider.getMetadataObject(java.lang.String)
         oracle.express.mdm.MdmSchema oracle.express.mdm.MdmMetadataProvider.getRootSchema()
         void oracle.practices.OLAPPractices.execute(java.lang.String[])
         void oracle.practices.OLAPPractices.main(java.lang.String[])
    Process exited with exit code 1.
    The line that generates the exception is:
    MdmSchema root = mdp.getRootSchema();
    I noticed that installing BIBDEMO sample schema removed the old SH measures and cubes. I tried changing the user/pwd from SH to BIBDEMO and got the same error.
    What's causing the problem. Can I easily undo the BIBDEMO changes and make the OLAP API samples work again. Or am I stuck waiting for the upcoming OLAP Patch?
    /Stan

    Hi Stan
    Can you tell us exactly what you did?
    What versions of the Beans and Oracle9i OLAP did you have first?
    What version of the OLAP patch did you install?
    What OS are you using? I initially installed Oracle 9i Database for MS Windows NT/2000 from CD-ROM (version 9.0.1). I have also installed JDeveloper 3.2.3 from an accompanying CD-ROM. I don't remember if BI Beans existed in that release, probably not.
    Then I downloaded JDeveloper 9i RC and BIBeans AddIn for JDeveloper. I installed the following patches:
    - Oracle9i Patch Set Version 9.0.1.2.0,
    - Oracle OLAP Release 1 Patch Set Version 9.0.1.1.1,
    - Oracle OLAP Best Practices for Cube Aggregation and Query Operations Release 1 (9.0.1) for Windows and UNIX, Part Number A92122-01,
    - XADEMO.BAT for Oracle OLAP.
    I'm using Windows NT 4 with SP 6a.
    I have also re-installed the SH_CAT schema as you suggested in the other note, but that didn't make the problem go away. I'm still getting MetadataNotFoundException when calling mdp.getRootSchema().
    /Stan

  • Does OWB creates CWM2 for OLAP/BI

    The environment is:
    Personal Oracle9i Release 9.2.0.3.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.3.0 - Production
    JDev 9.0.3.1035
    I managed to run the OLAP/BI Beans tutorials. So, I am now ready to create my own OLAP Metadata.
    I created some Dimensions, Cube and Measures with Oracle Enterprise Manager (OEM) which generates CWM (Common Warehouse Metadata) for 9R1.
    But to use full capabilities I need CWM2 from 9R2 so to generate OLAP Objects in CWM2 it seems that I need to go to OLAP Worksheet or use the PL/SQL packages for CWM2.
    I came across document named "Use Oracle Warehouse Builder To Build Your OLAP-Ready Data Warehouse" dated 2002, authors: Particia Fay, Jean-Pierre Dijcks and Oracle Corp. This documents shows how to create OLAP Objects with OWB in 9i.
    Does OWB generates OLAP Objects of CWM2 type ?
    Thanks for the feedback.
    Pedro Garza

    I just want to be clear on the DB version. I currently have 9.2.0.3.0 and it looks like I need a yet to be released 9.2.0.4. (rather than 9.0.2.4).Correct. Sorry for the typo in 9.2.0.4. The standalone OLAP patch on top of the database 9.2.0.3 exists but is not yet externally released. And you do need it. It is likely that it will be released in the patchset 9.2.0.4 rather than standalone.
    AW Manager is a tool with its own interface, very much like OEM, with a tree showing Measure Folders, Cubes and Dimensions. It appears under "Integrated Management Tools" in the menu when installed. So you would use OEM to create relational implementation of these objects and AWM to create dimensional implementation.
    Or you would use Warehouse Builder to model the objects once and then deploy to either relational or dimensional.
    Nikolai

  • Export metadata from OWB to Oracle OLAP

    Hi,
    I would like to know why the 'OWB export metadata to OLAP' generate an erreur like:
    ORA-06512: at "OLAPSYS.CWM$OLAP$DIMENSION", line 242
    ORA-06510: PL/SQL: unhandled user-defined exception
    ORA-06512: at "OLAPSYS.CWM$UTIL", line 341
    ORA-01403: no data found
    ORA-06512: at "OLAPSYS.CWM$OLAP$DIMENSION", line 67
    ORA-06512: at line 10
    knowing that i have installed the patches to the DB server
    and i whork with th Oracle Wherhouse Bilder 9.0.3.33

    It would appear that your mapping is incorrect. During the conversion to OLAP metadata, the dimension is not properly defined or contains no rows of data. If you check the log it should be possible to determine which dimension has failed. Also make sure your dimension values are unique across all levels in your relational table.
    How many dimensions and cubes are you trying to deploy?
    I would also recommend posting this on the OWB forum as they will be able in a better position to resolve your issue:
    Warehouse Builder
    Business Intelligence Beans Product Management Team
    Oracle Corporation

Maybe you are looking for