Unable to select OLAP API metadata

Question

I am using oracle rdbms 9.2.0.5
Initially I was able to view BIBDEMO schema cubes using cubeviewer. I also created my own cubes using CWM2 API and was able to view through the bibeans. All of sudden it stopped working and I am currently unable to even view the demo cubes in BIBDEMO schema using cube viewer, it throws a "red bell with no error message" dialog.
I validated the entire OLAP catalog using the CWM2 API, all the objects are valid.
I do not have a time dimension and any AW cubes.
The bi_checkconfig utility returned the following results.
<?xml version="1.0" encoding="UTF-8" ?>
<BICheckConfig version="1.0.0.0">
<Check key="JDEV_ORACLE_HOME" value="d:\Program Files\JDev_903"/>
<Check key="JAVA_HOME" value="D:\JDK\1.3.1_11"/>
<Check key="JDeveloper version" value="9.0.3.4.1247"/>
<Check key="BI Beans version" value="9.0.3.6.0A"/>
<Check key="BI Beans internal version" value="2.7.0.14"/>
<Check key="host" value="199.254.233.44"/>
<Check key="port" value="1521"/>
<Check key="sid" value="config3"/>
<Check key="user" value="kaisernw"/>
<Check key="Connecting to the database" value="Successful"/>
<Check key="JDBC driver version" value="9.2.0.3.0"/>
<Check key="JDBC JAR file location" value="d:\Program Files\JDev_903\jdbc\lib"/>
<Check key="Database version" value="9.2.0.5.0"/>
<Check key="OLAP Catalog version" value="9.2.0.5.0"/>
<Check key="OLAP AW Engine version" value="9.2.0.5.0"/>
<Check key="OLAP API Server version" value="9.2.0.5.0"/>
<Check key="BI Beans Catalog version" value="N/A; not installed in kaisernw"/>
<Check key="OLAP API JAR file version" value="9.2"/>
<Check key="OLAP API JAR file location" value="d:\Program Files\JDev_903\jdev\lib\ext"/>
<Check key="OLAP API Metadata Load" value="Unsuccessful"/>
<Check key="Failure Point" value="MDMLoadFailed"/>
<Check key="StackTrace">
<![CDATA[
============================================================================
1) An error occurred during olap API metadata retrieval. This is probably caused by inconsistent metadata.
1) An error occurred during olap API metadata retrieval. This is probably caused by inconsistent metadata.
============================================================================
oracle.express.ExpressServerExceptionError class: Unknown Error
Server error descriptions:
INI: System failure, Generic at TxsOqConnection::getDefaultDatabase
     void oracle.olapi.metadata.BaseMetadataProvider.<init>(oracle.olapi.data.source.DataProvider)
          BaseMetadataProvider.java:68
     void oracle.olapi.metadata.mdm.MdmMetadataProvider.<init>(oracle.olapi.data.source.DataProvider)
          MdmMetadataProvider.java:127
     oracle.olapi.metadata.MetadataProvider oracle.express.olapi.data.full.ExpressDataProvider.getDefaultMetadataProvider()
          ExpressDataProvider.java:912
     oracle.express.mdm.MdmMetadataProvider oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverImpl_92.getMdmMetadataProvider()
          MDMMetadataDriverImpl_92.java:1134
     oracle.dss.metadataUtil.PropertyBag oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverImpl_92.attach(oracle.dss.metadataUtil.PropertyBag)
          MDMMetadataDriverImpl_92.java:811
     oracle.dss.metadataUtil.PropertyBag oracle.dss.metadataManager.server.drivers.mdm.MDMMetadataDriverImpl.attach(oracle.dss.metadataUtil.PropertyBag)
          MDMMetadataDriverImpl.java:133
     void oracle.dss.metadataManager.server.MetadataManagerImpl.buildObjectModel()
          MetadataManagerImpl.java:1085
     oracle.dss.metadataManager.common.MDRoot oracle.dss.metadataManager.server.MetadataManagerImpl.attach(oracle.dss.metadataManager.common.MDRoot, oracle.dss.metadataUtil.PropertyBag)
          MetadataManagerImpl.java:962
     int oracle.dss.metadataManager.client.MetadataManager.attach(oracle.dss.metadataUtil.PropertyBag)
          MetadataManager.java:866
     int oracle.dss.metadataManager.client.MetadataManager.attach()
          MetadataManager.java:792
     oracle.dss.metadataUtil.OrderedHashtable BICheckConfig.checkConnection(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.io.OutputStream, boolean)
          BICheckConfig.java:250
     void BICheckConfig.main(java.lang.String[])
          BICheckConfig.java:1172
]]>
</Check>
</BICheckConfig>
How can I debug this issue.
Thank you,
Senthil

Answer 1

I figured what the problem is, I missed one of the invalid objects in my OLAP validation log file when I scanned before.
As part of another issue (Issue #1), I dropped and recreated some dimensions. But did not reattach those dimensions to the cube. So in the log, that particular cube was marked as invalid with the error "no dimensions".
FYI - (Issue #1)
When creating dimensions, by mistake I mapped some of the fields using CWM2 map table API to a VIEW. The CWM2 validation API, validated these dimensions and marked them as valid.
But from the query builder I was not able to progress forward from the layout panel to the dimension panel, it will just sit there without throwing any errors. Once I changed the view to the base table in the dimension definition, the querybuilder started working.
Thank you,
Senthil