5 Replies Latest reply: Nov 12, 2009 8:30 PM by 716495 RSS

    Discoverer Catalog Error in D4OLAP

    410079
      Following was a posting I done in discoverer forum; but did not get any response so far. I am hoping that BI Beans experts here could have some insights to this as DISCOVERER for OLAP uses BIBEANS.

      Thanks
      Suresh.
      ________________________________________________________


      Hi,

      I have an application server BI installation (10.1.2) that has Discoverer installed on RedHat Linux AS 3.0. My AW/OLAP Cubes are on on 9.2.0.6 and so is D4OSYS catalog schema.

      When I install the catalog and add a user to the catalog. I am able to logon with that user in Discoverer Plus for OLAP with that user, create workbooks/worksheets, save, retrieve etc. But on next day, when I logon with the same user, I can't open any of workbooks created by that user in the folder. It gives no permission error. The user has Full control over the folder and workbook. When I create a new workbook, it allows that, but while saving it gives Java lang null exception, neverthless it saves the workbook. The D4OSYS user is able to open all these workbooks. Following is the type of error I am getting:

      oracle.dss.d4o.common.D4OException: D4O-1011 An error occurred while loading user preferences.
      oracle.dss.bicontext.BINoPermissionException: BIB-10307 User lacked sufficient privileges to perform the operation.
      oracle.dss.metadataManager.common.InsufficientPrivilegeException: BIB-10307 User lacked sufficient privileges to perform the operation.
      at oracle.dss.d4o.common.UserPreferencesLoader.loadPreferences(Unknown Source)
      at oracle.dss.d4o.gui.MainPanel.connected(Unknown Source)
      at oracle.dss.d4o.gui.MainPanel.access$1700(Unknown Source)
      at oracle.dss.d4o.gui.MainPanel$ConnectTask.finished(Unknown Source)
      at oracle.dss.d4o.gui.common.SwingWorker$3.run(Unknown Source)
      at java.awt.event.InvocationEvent.dispatch(Unknown Source)
      at java.awt.EventQueue.dispatchEvent(Unknown Source)
      at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
      at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
      at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
      at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
      at java.awt.EventDispatchThread.run(Unknown Source)
      oracle.dss.bicontext.BINoPermissionException: BIB-10307 User lacked sufficient privileges to perform the operation.
      oracle.dss.metadataManager.common.InsufficientPrivilegeException: BIB-10307 User lacked sufficient privileges to perform the operation.
      at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:389)
      at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:258)
      at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:253)
      at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:219)
      at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:518)
      at oracle.dss.d4o.common.UserPreferencesLoader.loadPreferences(Unknown Source)
      at oracle.dss.d4o.gui.MainPanel.connected(Unknown Source)
      at oracle.dss.d4o.gui.MainPanel.access$1700(Unknown Source)
      at oracle.dss.d4o.gui.MainPanel$ConnectTask.finished(Unknown Source)
      at oracle.dss.d4o.gui.common.SwingWorker$3.run(Unknown Source)
      at java.awt.event.InvocationEvent.dispatch(Unknown Source)
      at java.awt.EventQueue.dispatchEvent(Unknown Source)
      at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
      at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
      at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
      at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
      at java.awt.EventDispatchThread.run(Unknown Source)
      oracle.dss.metadataManager.common.InsufficientPrivilegeException: BIB-10307 User lacked sufficient privileges to perform the operation.
      at oracle.dss.metadataManager.server.drivers.persistence.PersistenceMetadataDriverImpl.lookup(PersistenceMetadataDriverImpl.java:2517)
      at oracle.dss.metadataManager.server.MetadataManagerImpl.lookup(MetadataManagerImpl.java:5900)
      at oracle.dss.metadataManager.client.MetadataManager.lookup(MetadataManager.java:5936)
      at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:378)
      at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:258)
      at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:253)
      at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:219)
      at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:518)
      at oracle.dss.d4o.common.UserPreferencesLoader.loadPreferences(Unknown Source)
      at oracle.dss.d4o.gui.MainPanel.connected(Unknown Source)
      at oracle.dss.d4o.gui.MainPanel.access$1700(Unknown Source)
      at oracle.dss.d4o.gui.MainPanel$ConnectTask.finished(Unknown Source)
      at oracle.dss.d4o.gui.common.SwingWorker$3.run(Unknown Source)
      at java.awt.event.InvocationEvent.dispatch(Unknown Source)
      at java.awt.EventQueue.dispatchEvent(Unknown Source)
      at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
      at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
      at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
      at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
      at java.awt.EventDispatchThread.run(Unknown Source)
      oracle.dss.bicontext.BINoPermissionException: BIB-14695 Insufficient privileges for folder.
      at oracle.dss.persistence.storagemanager.bi.mapping.JdbcAdapterExceptionHandler.getBINoPermissionException(JdbcAdapterExceptionHandler.java:383)
      at oracle.dss.persistence.storagemanager.bi.mapping.JdbcAdapterExceptionHandler.throwException(JdbcAdapterExceptionHandler.java:338)
      at oracle.dss.persistence.storagemanager.bi.mapping.JdbcLookupHelper.resolvePath(JdbcLookupHelper.java:307)
      at oracle.dss.persistence.storagemanager.bi.mapping.JdbcAdapter.resolvePath(JdbcAdapter.java:1287)
      at oracle.dss.persistence.storagemanager.bi.BIStorageManagerImpl.lookupHelper(BIStorageManagerImpl.java:773)
      at oracle.dss.persistence.storagemanager.bi.BIStorageManagerImpl.lookup(BIStorageManagerImpl.java:839)
      at oracle.dss.persistence.persistencemanager.server.PersistenceManagerImpl.lookup(PersistenceManagerImpl.java:1587)
      at oracle.dss.persistence.persistencemanager.server.InitialPersistenceManager.lookup(InitialPersistenceManager.java:955)
      at oracle.dss.metadataManager.server.drivers.persistence.PersistenceMetadataDriverImpl.lookup(PersistenceMetadataDriverImpl.java:2483)
      at oracle.dss.metadataManager.server.MetadataManagerImpl.lookup(MetadataManagerImpl.java:5900)
      at oracle.dss.metadataManager.client.MetadataManager.lookup(MetadataManager.java:5936)
      at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:378)
      at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:258)
      at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:253)
      at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:219)
      at oracle.dss.metadataManager.common.MDFolder.lookup(MDFolder.java:518)
      at oracle.dss.d4o.common.UserPreferencesLoader.loadPreferences(Unknown Source)
      at oracle.dss.d4o.gui.MainPanel.connected(Unknown Source)
      at oracle.dss.d4o.gui.MainPanel.access$1700(Unknown Source)
      at oracle.dss.d4o.gui.MainPanel$ConnectTask.finished(Unknown Source)
      at oracle.dss.d4o.gui.common.SwingWorker$3.run(Unknown Source)
      at java.awt.event.InvocationEvent.dispatch(Unknown Source)
      at java.awt.EventQueue.dispatchEvent(Unknown Source)
      at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
      at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
      at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
      at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
      at java.awt.EventDispatchThread.run(Unknown Source)

      Similar problem I had faced in BIBeans catalog prior to the 10g version of Beans. It went away in 10g Beans. Any help is appreciated.

      Thanks
      Suresh.
        • 1. Re: Discoverer Catalog Error in D4OLAP
          Klaker-Oracle
          I presume, if you check the status of the user via Application Server Enterprise Manager using the Catalog maintenance feature the user is still correctly registered. Please also check using the SQLPlus or OEM your new user has the correct user roles. Your user should have OLAP_USER and D4O_PUB roles assigned.

          I would recommend logging a TAR with Oracle Support to try and debug this problem. I have not seen this issue before, even with the BI Beans catalog.

          Hope this helps

          Business Intelligence Beans Product Management Team
          Oracle Corporation
          • 2. Re: Discoverer Catalog Error in D4OLAP
            Kirill.Boyko
            Same for me...

            Are there any resolution for that?

            Disco 10.1.2.07.59
            BI Beans 3.2.1.0.13

            platform: Windows 2003
            • 3. Re: Discoverer Catalog Error in D4OLAP
              Klaker-Oracle
              There is a technote on Metalink 435577.1 that seems to show a similar problem to the one you have both described.

              Cause
              The issue is caused by an older catalog version being used with a newer Discoverer for OLAP version.

              The basic diagnostic run from within D4O shows the following relevant information:

              Discoverer Plus OLAP version 10.1.2.2.0.0010
              Discoverer version 10.1.2.54.25
              BI Beans Catalog version 3.2.1.0.13
              Discoverer Catalog version 10.1.2.07.59
              Authorized for Discoverer Plus OLAP catalog "Yes"

              There is an incompatible version of D4O (phase 1), 10.1.2.07.59 and catalog, version 10.1.2.07.59,
              with a 10.2.0.1 database and 10.2.0.1 OLAP catalog


              Solution
              Upgrading the Discoverer Catalog to the version included with Discoverer for OLAP 10.1.2.2 fixes the problem. The following steps will backup the existing catalog entries, re-create the catalog using the correct version and import the previous data into the new catalog to preserve information:

              1. Make sure that D4OSYS users are not connected to the instance.
              Use either Enterprise Manager (current processes) or SQLPlus (connected as sysdba)

              SQL>select username, sid, serial# from v$session where username='D4OSYS';


              If required, terminate the relevant session with the proper sid and serial# values, execute the following command to kill a session:

              (The example uses 19 as the sid, and 65 as the serial# value)

              SQL>alter system kill session '19, 65';

              2. In Application Server Control, navigate to the Administration / Discoverer tab and export the existing discoverer catalog.

              3. Take a note of which users are authorized in the catalog.
              This information will be required to authorize these users once the new catalog is in
              place.

              4. Create a backup of their existing D4OSYS schema by using the exp tool.
              This is a precaution in case this process has to be repeated or discontinued.

              5. Drop the entire D4OSYS schema:

              sqlplus / as sysdba
              SQL>drop user d4osys cascade;

              6. In Application Server Control (ASC), go to Administration / Discoverer and
              install a new catalog.

              (This is now the new version catalog).

              7. Ensure that no users are authorized to use the catalog.
              If any users are authorized, de-authorize them, so that no users remain in the
              list of authorized users. Do not de-authorize the D4OPUB role.

              8. Select all the users that had previously been authorized and authorize them in the new catalog.

              Steps 7 and 8 are required to synchronize RDBMS roles with the Discoverer catalog privileges.

              Checkout the note on Metalink as it contains links to other related notes that you might also want to review.

              Hope this helps


              Keith Laker
              Oracle EMEA Consulting

              BI Blog: http://oraclebi.blogspot.com/
              DM Blog: http://oracledmt.blogspot.com/
              BI on Oracle: http://www.oracle.com/bi/
              BI on OTN: http://www.oracle.com/technology/products/bi/
              BI Samples: http://www.oracle.com/technology/products/bi/samples/
              • 4. Re: Discoverer Catalog Error in D4OLAP
                Kirill.Boyko
                OK,

                Thank you Keith!

                It is working correctly now.
                • 5. Re: Discoverer Catalog Error in D4OLAP
                  716495
                  hye Keith Laker

                  i try the steps that u mention..
                  but i get the error D4O-1009 An error occurred while loading the worksheet..
                  even i uninstall the catalog and install the catalog..
                  when i create the worksheet and saved..of i exit..and try to open back...it show this error..

                  this is the diagnosis for the connection...

                  <D4OCheckConfig version="1.0.0.0">
                  <Check key="JDK version" value="1.6.0_16"/>
                  <Check key="BI Beans internal version" value="3.2.2.0.24"/>
                  <Check key="Discoverer Plus OLAP version" value="10.1.2.07.75"/>
                  <Check key="Discoverer version" value="10.1.2.48.18"/>
                  <Check key="port" value="-1"/>
                  <Check key="Connect to database" value="Successful"/>
                  <Check key="JDBC driver version" value="10.1.0.3.0"/>
                  <Check key="JDBC JAR file location" value="\TOSHIBA\disco\plus_files\d4o_double.jarjar"/>
                  <Check key="Database version" value="10.2.0.1.0"/>
                  <Check key="OLAP API Server version" value="10.2.0.1.0"/>
                  <Check key="OLAP AW Engine version" value="10.2.0.1.0"/>
                  <Check key="OLAP Catalog version" value="10.2.0.1.0"/>
                  <Check key="BI Beans Catalog version" value="3.2.2.0.24"/>
                  <Check key="Discoverer Catalog version" value="10.1.2.07.75"/>
                  <Check key="Authorized for Discoverer Plus OLAP catalog" value="Yes"/>
                  <Check key="OLAP API JAR file version" value="9.2"/>
                  <Check key="OLAP API JAR file location" value="\TOSHIBA\disco\plus_files\d4o_double.jarjar"/>
                  <Check key="Load OLAP API metadata" value="Successful"/>
                  <Check key="Number of metadata folders" value="3"/>
                  <Check key="Number of metadata measures" value="19"/>
                  <Check key="Number of metadata dimensions" value="17"/>

                  this is the error when i save the error...


                  oracle.dss.d4o.common.D4ORuntimeException: D4O-1009 An error occurred while loading the worksheet.
                  oracle.dss.bicontext.BINamingException: BIB-14099 Unknown naming exception.
                  oracle.dss.bicontext.BINamingException: BIB-14067 Persistable object threw exception during lookup on method setXMLAsString; component class oracle.dss.dataSource.QueryServer; exception null.
                  ......
                  .....
                  ....

                  i not have any clue...why this thing occur..
                  any idea why this thing occur...
                  thanks in advance....

                  regards,
                  rao..