Unable to create OLAP Metadata catalog in EIS

We are planning on creating new Essbase apps using EIS to create and load from our relational data warehouse databases. Have worked with Essbase for many years, but never EIS. We are currently on 9.3.3 for all Hyperion apps. I successfully installed the Integration Services Server on our test environment (Windows) and verified that the service is running. Also installed the Integration Services Console on my PC. We created the Metadata catalog database/tablespace on our MS SQL Server (2008). Using the ODBC Data Source Administrator on the EIS server, I created a new ODBC data source for this database following the instructions in the EIS install guide and used the “SQL Server” driver as specified. I was able to get a successful test connection within the Data Source Administrator and successfully saved the Data Source. However, when I first use the Integration Services console and first try to create the Metadata catalog, I get the following error: ODBC Error [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified. I enter the correct EIS server name, but have to manually type in the Catalog ODBC DSN name as the one I created doesn’t show up in the drop down. I also verified that the correct administrator userid and password are used. What could I be missing or doing wrong? Thanks. Mike

Yes, I am using the Essbase server name. The only other thing I can think of is the driver version. I just used the one called "SQL Server" which is what the install guide said. However, this is the 9.3.1 guide, so may be outdated info for 9.3.3. I did not use the DataDirect 6.0 drivers that were installed when I installed the Integration Services software on the server. Is it possible I need to download Microsoft SQL Server 2008 Native Client 10.0 and install that on the server? That is the other thing. There currently is no SQL client software installed on the EIS server. Could that be the problem? Thanks

Similar Messages

  • Using OEM to create olap metadata (cubes)

    To anyone who can help:
    I'm able to use the cube viewer with the bibdemo schema and view view my cubes. But when I create a new cube pulling from a new schema I'm not able to see my cubes with the cube viewer. I get the infamous red bell when.
    I'm using 9.2.0.4.1 version of the database.
    Please help.
    Jeff

    Hi,
    I have the same problem.
    Any news?
    Greets
    Even Langer

  • Jco connection metadata unable to create

    hi,
    single server.
    j2ee engine and abap installed on same server, both engines registered under SLD.
    created model data jco destination but unable to create a metadata jco destination.
    error: message server not entered, signon group not entered.
    but both are disable while creating meta data destinations.
    please solve this prob

    You must set up the message server in your SLD environment.
    Look at this blog.
    /people/sugree.phatanapherom/blog/2005/08/14/configuring-sld-in-sneak-preview-sap-netweaver-04-sneak
    /people/thomas.jung/blog/2006/02/08/as-abap-sneak-preview-lessons-logon-groups

  • AIS freezes when trying to create a new metadata catalog

    Hi,
    I'm really new in EIS/AIS. We are using EIS and Essbase version 9.3.1. I just created a new odbc connection to our data warehouse (Oracle in OraHome92). I tried to create a new catalog but EIS freezes. When I tried to "end task" the console, it closes and would get a message "olapbldr error". Need to know how to fix this. Any help would be greatly appreciated.

    Hi,
    I'm really new in EIS/AIS. We are using EIS and Essbase version 9.3.1. I just created a new odbc connection to our data warehouse (Oracle in OraHome92). I tried to create a new catalog but EIS freezes. When I tried to "end task" the console, it closes and would get a message "olapbldr error". Need to know how to fix this. Any help would be greatly appreciated.

  • Role and Privileges for OLAP metadata

    Hi,
    Is there any document which specifies what all roles and privileges are required for creating any OLAP meta data ( Dimension, Cube, Measure and Catalog etc)?
    I think these are impt roles:-
    SELECT_CATALOG_ROLE
    EXECUTE_CATALOG_ROLE
    DELETE_CATALOG_ROLE
    RECOVERY_CATALOG_OWNER
    OLAP_DBA
    OLAP_USER
    Through system/manager I created one user TEST_BI_OLAP and granted CONNECT.
    After login as TEST_BI_OLAP I am able to create dimension. Why it is possible whereas doc says user should have OLAP_USER or OLAP_DBA role associated with it.
    OR only CONNECT is sufficient for creating OLAP metadata!!!!!
    regds
    P

    The difference is in what the end user sees. Say you want to deploy an analytical workspace based off of a ROLAP dimensional cube. Here is how I've been approaching the problem:
    1. Create a new user with the OLAP_USER role to hold the AW (say "AW_USER")
    2. Now log in with a userid that has OLAP_DBA role, and create the AW utilizing the ROLAP cube - but direct the AW to be stored in the AW_USER schema. Note that because it is in a separate schema from the ROLAP cube, you will not need to append characters to the dimension or measure names.
    3. Have end users log in using the AW_USER name. Then they will see the AW information, but they will not have access to the ROLAP cube data.
    Hope this helps,
    Scott

  • Urgent help please: error at bi_checkconfig when validate OLAP metadata....

    dear friends,
    i used oracle database 10g Release 1 which i've patched it with Oracle 10.1.04 patchset, Oracle JDeveloper 10g (Version 10.1.2.1.0, build 1913) and bibeans 10.1.2.1 to build Business Intelligence based Application.
    first, i create OLAP metadata ( like: dimensions, level, cube, measures ) with Oracle Enterprise Manager Database Control, i design my cube in star schema format and store my OLAP metadata in COBA_OLAP schema that i've created before.
    After all my job with OLAP metadata finished, then i go to command prompt and validate my OLAP metadata with utility that brought by Oracle BIBeans 10.1.2.1 called bi_checkconfig
    i validate my OLAP metadata by executing this command from command prompt:
    C:\jdev1012\bibeans\bi_checkconfig>bi_checkconfig -h localhost -po 1521 -sid kuliah -u COBA_OLAP -p wysiwyg -q
    BI Beans Diagnostics(v1.0.2.0) 10/18/05
    ==============================================================================================================
    JDEV_ORACLE_HOME.......................................................................................................     = C:\jdev1012
    JAVA_HOME......................................................................................................................     = C:\jdev1012\jdk\jre
    JDeveloper version................................................................................................................     = 10.1.2.1.0.1913
    BI Beans release description.................................................................................................     = BI Beans 10.1.2 Production Release
    BI Beans component number................................................................................................     = 10.1.2.67.0
    BI Beans internal version.......................................................................................................     = 3.2.2.0.24.2
    Connect to database.............................................................................................................     = Successful
    JDBC driver version...............................................................................................................     = 10.1.0.42
    JDBC JAR file location..........................................................................................................     = C:\jdev1012\jdbc\lib
    Database version..................................................................................................................     = 10.1.0.4.0
    OLAP Catalog version............................................................................................................     = 10.1.0.4.0
    OLAP AW Engine version......................................................................................................     = 10.1.0.4.0
    OLAP API Server version.......................................................................................................     = 10.1.0.4.0
    BI Beans Catalog version.......................................................................................................     = N/A; not installed in COBA_OLAP
    OLAP API JAR file version.....................................................................................................     = "10.1.0.5.0"
    OLAP API JAR file location....................................................................................................     = C:\jdev1012\jdev\lib\ext
    Load OLAP API metadata .....................................................................................................     = unsuccessful
    Error: An error occurred during olap API metadata retrieval. This is probably caused by inconsistent metadata.
    my log file at C:\jdev1012\bibeans\bi_checkconfig\bi_error.log looks like this :
    ============================================================================
    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: A system failure occurred., Generic at TxsOqConnection::getDefaultDatabase
         at BICheckConfig.checkConnection(BICheckConfig.java:277)
         at BICheckConfig.main(BICheckConfig.java:1367)
    i really need help to fix this problem, any kind of solutions will be very appreciated...
    best regards,
    amiril

    Hi
    i was using AWM since 9i just because it creates OLAP metadata with a new API called CWM2, and Oracle Enterprise Manager was using a propietary API .
    With AWM 10.1.0.4 building your OLAP metadata is very simple, you can define your Dimensions, cubes, measures and even you can load your data from your source system.
    You can refer to the Oracle® OLAP Application Developer's Guide where you can find more information on this tool.
    And relative to your error i will recommend that you build on a dimension-by-dimension basis and try to validate your OLAP Metadata.
    Regards

  • How to create OLAP Catalog Metadata from Analytic Workspace

    Hi,
    How to create OLAP Catalog Metadata objects automatically from Analytic Workspace, not using CWM2_OLAP_AW_OBJECT package.
    Is there tool for it?

    Analytic Workspace Manager is the supported tool from Oracle for creating OLAP catalog metadata (plus the SQL views required for BI Beans). Hopefully this should be out in June as an additional download following the 9.2.0.3x patch.
    However you might want to look at IAF Software's "Coaster" product (http://www.iafsoft.com/products/coaster.htm) which also contains functionality to create the OLAP Catalog. We've had a play around with it and have been impressed.
    regards
    Mark Rittman

  • Unable to Create Fact and Dimension tables from the Tools menu in EIS conso

    Hi All,
    In the EIS console, I am unable to create the fact table and the dimension tables to produce my OLAP model from the TOOLS menu whereas I am able to create them by dragging from the left panel where the tables are displayed. I am geeting the below error message:
    "An exception occured while retrieving OLAP model metadata. Please verify you are connected to the catalog and try again"
    Any help appreciated.
    Thanks,
    Raja

    I have fact and dimension tables in one server and i moved those stuff to another server.If I do that what happen to essbase and about totale EPM System.I want to know how to do this and what I can expect?
    Please reply

  • Unable to select OLAP API metadata

    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

    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

  • Unable to change Date Created in Metadata

    Please help with my first post...
    Unable to change Date Created field in Metadata.
    I am a newspaper photographer sending .jpg pics with captions to my office from my iMac. They are viewed at the office on Windows PCs using SCC MediaGrid.
    When changing Date Created in Metadata Invalid Format warning appears "Format should be ISO 8601 XML compliant, that is YYYY-MM-DDThh:mm[:ss][tz] (eg 2006-07-11T13:14:30-07:00)"
    If 2009-09-26, for example, is entered then exported pictures opened up in Photoshop or shown on SCC MediaGrid do not display the date.
    To get dates to show up I first have to open a pic in Photoshop, go to File Info, enter 26/9/09 in Date Created and Save As.
    Next I have to Import this into Aperture where the Date Created shows as "20090926".
    Using Lift Metadata and Stamp Metadata the date can be transferred to other pics.
    Now when I export these pics the date does show up in Photoshop and SCC MediaGrid.
    Can Date Created be typed straight into field in Aperture?...Very important when pics go into archive on a server.
    Also if I hit Return key in a Metadata Caption, to type on the next line, both lines will appear as one with a small square in-between them when viewed on SCC MediaGrid on a Windows PC.
    Thanks in anticipation.

    Nick I don't generallt use the IPTC metadata, so I'm not sure I will be too much help.
    What version of Aperture are you using? I tried both things and I didn't have any problems with the latest version of Aperture on my Mac.
    I was able to enter a date into "Date Created" both with and without the time-zone adjustment. Can you tell us the exact string you tried to enter into the "Date Created" and exactly when you get the error? I tried to enter my time zone (eastern US) as "-5:00", but Aperture wouldn't let me enter the 5 and popped up the error message when I typed that key. I had to use "-05:00".
    As for the caption, when I hit return, Aperture ends my edit. I cannot reproduce your described behavior of actually getting a new-line into the field. I suspect your problem (although I don't know how you get to your problem) is one of the following:
    1) The IPTC standard doesn't tell if the software should use a Unix-style end-of-line (which is a line-feed), or a DOS/Windows style end-of-line (which is carriage-return followed by line-feed). Aperture may put in the Unix-style and your Windows programs don't know what to do with it.
    2) The IPTC standard does indicate the end-of-line style, but either Aperture or your other programs don't follow it.
    or
    3) IPTC Metadata doesn't actually support end-of-line, so Aperture should not allow you to enter multiple lines, but it has a bug so it does allow you to do that.
    Can you tell us where exactly you are editing the caption? I tried it in the inspector pane (on the left) in the "Metadata" tab, and then I hit the "IPTC" button at the bottom of the tab.
    nathan

  • Unable to create Metadata connection for Dictionary Provider

    Hi,
    I am getting the following error while I try to run a Web Dynpro Application;
    The initial exception that caused the request to fail, was:
       com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
        at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:191)
        at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
        at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
        at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
        at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
        ... 37 more
    The JCo Connections are tested and pinged, they work fine.
    Can anyone please tell what the error could be?

    The details exception list is as below:
    com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.dow.dc.model.types.Syuname could not be loaded: com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
         at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:191)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         ... 34 more

  • RFC Error: Unable to create Metadata connection for Dictionary Provider

    I configured two RFC ('WD_XXX__MODELDATA_DEST and WD_XXX_RFC_METADATA_DEST). I tested it and it shown green light.
    When I run my application that coonnect to CRM using RFC, I got the following errors:
    <i>com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.xxx.types.Syuname could not be loaded: com.sap.dictionary.runtime.DdException: 'WD_ICEBERG_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_XXX_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
         at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:670)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:233)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:443)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:381)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:410)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:79)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:121)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:117)
         at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:207)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:690)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:560)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:311)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:204)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:347)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:668)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:268)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:40)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.dictionary.runtime.DdException: 'WD_XXX_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_XXX_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:225)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         ... 49 more</i>
    I understand that I need to configured the Metadata Dictionary type for the RFC. For this, I need to configure the Message Server properties (for load balancing).
    But my Basis guy told me that CRM is an application server, so we only can configured with application server properties. Is this true? (I really doubt it) That is no Message Server connection to CRM system now.
    If it is true, how can I create a RFC connection to CRM system?
    Thanks for help.
    Kent

    Hi KC,
    Try the following links, they may help you.
    http://help.sap.com/saphelp_nw04s/helpdata/en/3a/3b1b40fcdd8f5ce10000000a155106/content.htm
    JCO connection
    Using the SAP Enterprise Connector for generating BAPI Proxy Classes
    points if useful
    Thanks
    Suresh

  • Unable to create SC from internal catalog (MDM)

    Hi All,
    We have issue were user is unable to create SC from internal catalog. User can access the catalog, however when trying to checkout he gets BLANK screen. This issue is with all the items for that catalog.
    Please advise.
    Thanks,
    Sunil

    Hi Sunil,
    What is your IE version ? If its IE 8.0 please check SAP note 1511147. This contains settings that are needed.
    Please also check the following note:
    1264879 - Transferred Catalog items get stuck at Inbound Handler
    Please maintain the ISO code of page on the webservice details as UTF-8 and retest. Also try, if you are using BYPASS_INBOUND_HANDLR parameter on the call structure with value = X delete this line and retest.
    Another issue is that if the user does not have access to the product category their items will not be added to the SC.
    I hope this helps,
    Lisa

  • Access to OLAP Metadata from BI Beans 903

    Hi,
    we have a problem accessing OLAP objects via BI Beans.
    Having created OLAP dimensions and facts via OWB or EIM, we were not able to see them in the BI Beans Query Builder.
    We then ran the "cwm2_olap_metadata_refresh.mr_refresh" routine on the OLAPSYS schema, which is supposed to update the CWM OLAP objects into CWM2 format.
    In BI Beans we now try to connect to our schema which contains the OLAP objects; the connection is fine; when doing "New (matrix, table, graph)", we get a Query Builder error message : "Unable to initialize Query Builder"
    On the detail screen (see java error below), it seems that dimensions cannot be retrieved from the OLAP catalog.
    However, we see entries for our dimensions when looking in union views, such as all$olap2udimensions or in tables such as the CWM2$MRALL_HIERDIMS table.
    Thanks,
    Klaus
    oracle.dss.dataSource.common.QueryRuntimeException
    java.lang.NullPointerException
    java.util.Vector oracle.dss.dataSource.common.QueryQueryAccess.getDimensions(java.lang.String)
    QueryQueryAccess.java:413
    java.util.Vector oracle.dss.queryBuilder.QueryBuilderQueryAccessUtils.getVisibleDimensions(java.lang.String)
    QueryBuilderQueryAccessUtils.java:130
    java.util.Vector oracle.dss.queryBuilder.QueryBuilderUtils.getVisibleDimensions(oracle.dss.queryBuilder.QueryBuilder)
    QueryBuilderUtils.java:495
    void oracle.dss.queryBuilder.QueryBuilderUI.createDefaultPanels()
    QueryBuilderUI.java:405
    void oracle.dss.queryBuilder.QueryBuilderUI.init()
    QueryBuilderUI.java:351
    boolean oracle.dss.queryBuilder.QueryBuilder.initialize()
    QueryBuilder.java:2337
    void oracle.dss.addins.wizard.presentation.PresentationWizardContext.initQueryBuilder()
    PresentationWizardContext.java:102
    void oracle.dss.addins.wizard.presentation.PresentationWizardContext.setDesigner(oracle.dss.addins.designer.BIDesigner)
    PresentationWizardContext.java:149
    boolean oracle.dss.addins.wizard.presentation.PresentationWizardAddin.invokeFromMenu(oracle.ide.addin.Context, java.lang.String[], oracle.dss.addins.designer.BIFolder, oracle.dss.addins.designer.BIDesigner, boolean)
    PresentationWizardAddin.java:64
    void oracle.dss.addins.designer.BIDesignerAddin.actionPerformed(java.awt.event.ActionEvent)
    BIDesignerAddin.java:572
    void javax.swing.AbstractButton.fireActionPerformed(java.awt.event.ActionEvent)
    AbstractButton.java:1450
    void javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(java.awt.event.ActionEvent)
    AbstractButton.java:1504
    void javax.swing.DefaultButtonModel.fireActionPerformed(java.awt.event.ActionEvent)
    DefaultButtonModel.java:378
    void javax.swing.DefaultButtonModel.setPressed(boolean)
    DefaultButtonModel.java:250
    void javax.swing.AbstractButton.doClick(int)
    AbstractButton.java:279
    void javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mouseReleased(java.awt.event.MouseEvent)
    BasicMenuItemUI.java:886
    void java.awt.Component.processMouseEvent(java.awt.event.MouseEvent)
    Component.java:3715
    void java.awt.Component.processEvent(java.awt.AWTEvent)
    Component.java:3544
    void java.awt.Container.processEvent(java.awt.AWTEvent)
    Container.java:1164
    void java.awt.Component.dispatchEventImpl(java.awt.AWTEvent)
    Component.java:2593
    void java.awt.Container.dispatchEventImpl(java.awt.AWTEvent)
    Container.java:1213
    void java.awt.Component.dispatchEvent(java.awt.AWTEvent)
    Component.java:2497
    void java.awt.LightweightDispatcher.retargetMouseEvent(java.awt.Component, int, java.awt.event.MouseEvent)
    Container.java:2451
    boolean java.awt.LightweightDispatcher.processMouseEvent(java.awt.event.MouseEvent)
    Container.java:2216
    boolean java.awt.LightweightDispatcher.dispatchEvent(java.awt.AWTEvent)
    Container.java:2125
    void java.awt.Container.dispatchEventImpl(java.awt.AWTEvent)
    Container.java:1200
    void java.awt.Window.dispatchEventImpl(java.awt.AWTEvent)
    Window.java:922
    void java.awt.Component.dispatchEvent(java.awt.AWTEvent)
    Component.java:2497
    void java.awt.EventQueue.dispatchEvent(java.awt.AWTEvent)
    EventQueue.java:339
    boolean java.awt.EventDispatchThread.pumpOneEventForHierarchy(java.awt.Component)
    EventDispatchThread.java:131
    void java.awt.EventDispatchThread.pumpEventsForHierarchy(java.awt.Conditional, java.awt.Component)
    EventDispatchThread.java:98
    void java.awt.EventDispatchThread.pumpEvents(java.awt.Conditional)
    EventDispatchThread.java:93
    void java.awt.EventDispatchThread.run()
    EventDispatchThread.java:85
    java.lang.NullPointerException
    java.lang.Object java.util.Hashtable.put(java.lang.Object, java.lang.Object)
    Hashtable.java:380
    oracle.dss.metadataManager.common.MDDimension oracle.dss.dataSource.common.Query.getMeasureDim()
    Query.java:3015
    oracle.dss.metadataManager.common.MDDimension oracle.dss.dataSource.common.QueryQueryAccess._getMeasureDimension()
    QueryQueryAccess.java:679
    java.lang.String oracle.dss.dataSource.common.QueryQueryAccess.getMeasureDimension(java.lang.String)
    QueryQueryAccess.java:456
    void oracle.dss.dataSource.common.QueryQueryAccess._initializeDimensionality()
    QueryQueryAccess.java:792
    java.util.Vector oracle.dss.dataSource.common.QueryQueryAccess.getDimensions(java.lang.String)
    QueryQueryAccess.java:409
    java.util.Vector oracle.dss.queryBuilder.QueryBuilderQueryAccessUtils.getVisibleDimensions(java.lang.String)
    QueryBuilderQueryAccessUtils.java:130
    java.util.Vector oracle.dss.queryBuilder.QueryBuilderUtils.getVisibleDimensions(oracle.dss.queryBuilder.QueryBuilder)
    QueryBuilderUtils.java:495
    void oracle.dss.queryBuilder.QueryBuilderUI.createDefaultPanels()
    QueryBuilderUI.java:405
    void oracle.dss.queryBuilder.QueryBuilderUI.init()
    QueryBuilderUI.java:351
    boolean oracle.dss.queryBuilder.QueryBuilder.initialize()
    QueryBuilder.java:2337
    void oracle.dss.addins.wizard.presentation.PresentationWizardContext.initQueryBuilder()
    PresentationWizardContext.java:102
    void oracle.dss.addins.wizard.presentation.PresentationWizardContext.setDesigner(oracle.dss.addins.designer.BIDesigner)
    PresentationWizardContext.java:149
    boolean oracle.dss.addins.wizard.presentation.PresentationWizardAddin.invokeFromMenu(oracle.ide.addin.Context, java.lang.String[], oracle.dss.addins.designer.BIFolder, oracle.dss.addins.designer.BIDesigner, boolean)
    PresentationWizardAddin.java:64
    void oracle.dss.addins.designer.BIDesignerAddin.actionPerformed(java.awt.event.ActionEvent)
    BIDesignerAddin.java:572
    void javax.swing.AbstractButton.fireActionPerformed(java.awt.event.ActionEvent)
    AbstractButton.java:1450
    void javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(java.awt.event.ActionEvent)
    AbstractButton.java:1504
    void javax.swing.DefaultButtonModel.fireActionPerformed(java.awt.event.ActionEvent)
    DefaultButtonModel.java:378
    void javax.swing.DefaultButtonModel.setPressed(boolean)
    DefaultButtonModel.java:250
    void javax.swing.AbstractButton.doClick(int)
    AbstractButton.java:279
    void javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mouseReleased(java.awt.event.MouseEvent)
    BasicMenuItemUI.java:886
    void java.awt.Component.processMouseEvent(java.awt.event.MouseEvent)
    Component.java:3715
    void java.awt.Component.processEvent(java.awt.AWTEvent)
    Component.java:3544
    void java.awt.Container.processEvent(java.awt.AWTEvent)
    Container.java:1164
    void java.awt.Component.dispatchEventImpl(java.awt.AWTEvent)
    Component.java:2593
    void java.awt.Container.dispatchEventImpl(java.awt.AWTEvent)
    Container.java:1213
    void java.awt.Component.dispatchEvent(java.awt.AWTEvent)
    Component.java:2497
    void java.awt.LightweightDispatcher.retargetMouseEvent(java.awt.Component, int, java.awt.event.MouseEvent)
    Container.java:2451
    boolean java.awt.LightweightDispatcher.processMouseEvent(java.awt.event.MouseEvent)
    Container.java:2216
    boolean java.awt.LightweightDispatcher.dispatchEvent(java.awt.AWTEvent)
    Container.java:2125
    void java.awt.Container.dispatchEventImpl(java.awt.AWTEvent)
    Container.java:1200
    void java.awt.Window.dispatchEventImpl(java.awt.AWTEvent)
    Window.java:922
    void java.awt.Component.dispatchEvent(java.awt.AWTEvent)
    Component.java:2497
    void java.awt.EventQueue.dispatchEvent(java.awt.AWTEvent)
    EventQueue.java:339
    boolean java.awt.EventDispatchThread.pumpOneEventForHierarchy(java.awt.Component)
    EventDispatchThread.java:131
    void java.awt.EventDispatchThread.pumpEventsForHierarchy(java.awt.Conditional, java.awt.Component)
    EventDispatchThread.java:98
    void java.awt.EventDispatchThread.pumpEvents(java.awt.Conditional)
    EventDispatchThread.java:93
    void java.awt.EventDispatchThread.run()
    EventDispatchThread.java:85

    Hi,
    Can you confirm the version number of the various products you are using please:
    - Database
    - JDeveloper
    - BIBeans
    - Oracle Warehouse Builder (OWB)
    - EIM (can you explain what this is please)
    I presume you have created a database using the data warehouse option of the Database Configuration Assistant. This should install a demo schema owned by the user SH. Can you create a crosstab using this schema. This will help determine the status of the metadata layer.
    Keith Laker
    BIBeans Product Manager
    Oracle Corporation

  • Error during Olap metadata retrieval

    Hi all,
    We are getting the following error while trying to establish connection to the olap catalog to retrive olap metadata information for BI Beans
    "Successfully connected to the Oracle database but failed to retrieve metadata.
    Although the database connection succeeded,metadata in the OLAP Catalog is not
    valid and could not be retrieved.In order to create OLAP queries against the
    database,you must ensure that the OLAP Catalog metadata is valid."
    On running the BI Beans configuration diagnostic utility we get the following error
    <?xml version="1.0" encoding="UTF-8" ?>
    <BICheckConfig version="1.0.0.0">
    <Check key="JDEV_ORACLE_HOME" value="D:\JDev_57_Oct14Class"/>
    <Check key="JAVA_HOME" value="D:\jdk1.3.1_04"/>
    <Check key="JDeveloper version" value="9.0.3.998"/>
    <Check key="BI Beans version" value="9.0.3.4.0"/>
    <Check key="BI Beans internal version" value="2.7.0.11.3"/>
    <Check key="host" value="ap950sun.us.oracle.com"/>
    <Check key="port" value="1521"/>
    <Check key="sid" value="HCXD2BI"/>
    <Check key="user" value="hbi"/>
    <Check key="Connecting to the database" value="Successful"/>
    <Check key="JDBC driver version" value="9.2.0.1.0"/>
    <Check key="JDBC JAR file location" value="D:\JDev_57_Oct14Class\jdbc\lib"/>
    <Check key="Database version" value="9.2.0.2.0"/>
    <Check key="OLAP Catalog version" value=""/>
    <Check key="OLAP AW Engine version" value=""/>
    <Check key="OLAP API Server version" value=""/>
    <Check key="BI Beans Catalog version" value="N/A; not installed in hbi"/>
    <Check key="OLAP API JAR file version" value="9.2"/>
    <Check key="OLAP API JAR file location" value="D:\JDev_57_Oct14Class\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.idl.util.OlapiException
         at oracle.express.idl.ExpressConnectionModule.ConnectionInterfaceStub.getDefaultDatabase(ConnectionInterfaceStub.java:1465)
         at oracle.express.mdm.MdmMetadataProvider.<init>(MdmMetadataProvider.java:200)
         at oracle.express.mdm.MdmMetadataProvider.<init>(MdmMetadataProvider.java:187)
         at oracle.express.olapi.data.full.ExpressDataProvider.getDefaultMetadataProvider(ExpressDataProvider.java:549)
         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 BICheckConfig.checkConnection(BICheckConfig.java:250)
         at BICheckConfig.main(BICheckConfig.java:1172)
    ]]>
    </Check>
    </BICheckConfig>
    We are getting the same error for 2 different users.
    We are using Jdeveloper 9.0.3 with BI Beans 9.0.3 and 9.2.0.2 database
    Could someone help us with this.
    Thanks in advance.
    Nigel

    Hi,
    The issue here is if the whole catalog is corrupt or just one schema. So to try and determine the status of the catalog I would try:
    1) Using OEM remove all the objects you created
    2) I presume you created your database using the Database Configuration Assistant? You should have used the warehouse template
    3) Make sure the following accounts are unlocked and also not expired : SH, OLAPSYS
    4) Make sure the password for the SH schema is SH
    5) Make sure the password for the OLAPSYS account is manager
    6) Install the BIBDEMO schema that is shipped with BI Beans. This in the jdev_home/bibeans/bibdemo_schema
    The installation process will remove SH schema from the OLAP catalog.
    7)Once this is installed use JDeveloper to see if you can create a crosstab or graph.
    8) If the BIBDEMO schema works try creating your new schemas one at a time.
    9) Make sure the if you define the a dimension as type time it has END_DATE (column type DATE) and TIME_SPAN (column type number) defined. Otherwise don't define the dimension as type time.
    Hope this helps
    Keith Laker
    Product Manager
    Oracle Business Intelligence Beans

Maybe you are looking for