ENT-06965- view dimension or cube.

It reproduces east problem to me when attempt to see the data of some dimension or cube after deploying them and to execute mappings. (for this I use the option To Deploy All).
how I can solve my problem?
If later derive the dimensions and the cube to the Discoverer I will be able to see it or it will give he himself error me?.
Please to respond.
Thank you very much by the help.
ENT-06965:Failure in the creation of the manager of metadatos of BiBeans from OLAP and the information of catalogue.

if I connect myself instead of with the proprietor of repositorio, with the user of the area in where they are the dimensions and the bucket, it changes of error to the ENT-06952: Failure in the connection to database OLAP.
It can be by the roles of the user?
As I can see whereupon usuary I accede to the BiBeans?
thanks,

Similar Messages

  • How to change column names in dimension and cube views?

    whenever AWM creates a view on a dimension or cube, it creates columns for long and short description with full name
    forexanmpel, it creates like
    CREATE OR REPLACE VIEW OLAPTRAIN.CHANNEL_VIEW
    AS
    SELECT
    "DIM_KEY",
    "LEVEL_NAME",
    "MEMBER_TYPE",
    "DIM_ORDER",
    "LONG_DESCRIPTION",
    "SHORT_DESCRIPTION",
    "ALL_CHANNELS_LONG_DESCRI",
    "ALL_CHANNELS_SHORT_DESCR",
    "CLASS_LONG_DESCRIPTION",
    "CLASS_SHORT_DESCRIPTION",
    "CHANNEL_LONG_DESCRIPTION",
    "CHANNEL_SHORT_DESCRIPTIO",
    "CHANNEL_TYPE",
    "CHANNEL_CHANNEL_TYPE",
    "CHANNEL_ALL_CHANNELS_ID",
    "CHANNEL_CLASS_ID",
    "CHANNEL_CHANNEL_ID"
    FROM TABLE(CUBE_TABLE('"OLAPTRAIN"."CHANNEL"') );
    what is the way to customize the column name? for example for class level, how can we say insterad of long_description and short_description, use LONG and SHORT simply?
    i also see the size of long and short descriptions are set to varchar2(60) and varchar2(20), is there a way to change that for each level in AWM?
    Thanks

    Hi there,
    I don't think there is a way to control the column names within the OLAP product itself, but if this is something you really want to do, have you tried creating your own views?
    As you can see, the syntax is pretty simple
    Thanks,
    Stuart Bunby
    OLAP Blog: http://oracleOLAP.blogspot.com
    OLAP Wiki: http://wiki.oracle.com/page/Oracle+OLAP+Option
    OLAP on OTN: http://www.oracle.com/technology/products/bi/olap/index.html
    DW on OTN : http://www.oracle.com/technology/products/bi/db/11g/index.html

  • Can CWM2 API creating dimensions and cube reference a view

    Can CWM2 API creating dimensions and cube reference a view instead of a table.
    Can the following API reference a view instead of table
    For creating dimensions
    CWM2_OLAP_TABLE_MAP.MAP_DIMTBL_HIERLEVEL
    CWM2_OLAP_TABLE_MAP.MAP_DIMTBL_HIERLEVELATTR
    For creating cubes
    CWM2_OLAP_TABLE_MAP.MAP_FACTTBL_LEVELKEY
    CWM2_OLAP_TABLE_MAP.MAP_FACTTBL_MEASURE

    Hi!
    Yes!
    And I am using views sometimes.
    I am reading at this moment also the following...
    maybe someone can explain me this sentence...
    MULTIPLE FACT TABLES:
    "The CWM2 APIs also support multiple fact tables per cube. In this case, the data
    associated with a given combinations of hierarchies can be stored in a separate fact
    table. All the fact tables associated with a cube must have the same column
    structure."
    I get a fetch error message..'cause of this.
    What does it mean by "the same column
    structure" ???
    ODDS

  • 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"

  • ENT-06965

    Hello,
    I have deployed the tables, external tables, dimensions and sequences successfully.
    I was now going to deploy my cube and then my mappings.
    When deploying my cube I get an error saying:
    French:
    ORA-06510: PL/SQL : exception définie par l'utilisateur non traitée
    ORA-06512: à "OLAPSYS.CWM2_OLAP_UTILITY", ligne 1660
    ORA-01403: aucune donnée trouvée
    ORA-06512: à "OLAPSYS.CWM2_OLAP_CUBE", ligne 33
    ORA-06512: à "OLAPSYS.CWM2_OLAP_CUBE", ligne 55
    ORA-06512: à "OLAPSYS.CWM2_OLAP_CUBE", ligne 386
    ORA-06512: à ligne 4
    English:
    ORA-06510: PL/SQL : exception defined by user not processed
    ORA-06512: "OLAPSYS.CWM2_OLAP_UTILITY", line 1660
    ORA-01403: no data found
    ORA-06512: "OLAPSYS.CWM2_OLAP_CUBE", line 33
    ORA-06512: "OLAPSYS.CWM2_OLAP_CUBE", line 55
    ORA-06512: "OLAPSYS.CWM2_OLAP_CUBE", line 386
    ORA-06512: at line 4
    Any ideas or pointers as to where or what I should do to fix this issue?
    Thank you!
    PS. I am doing the Oracle By Example (OBE) - Oracle Warehouse Builder 10g Release 2 online tutorials found at:
    http://www.oracle.com/technology/obe/10gr2_owb/admin/owb10gr2_gs.htm
    The error comes at the chapter "Deploying the Target Warehouse"
    http://www.oracle.com/technology/obe/10gr2_owb/owb10gr2_gs/owb/lesson5/deployingobjects.htm#t2
    Message was edited by:
    EGil

    Managed to deploy the cube and load data into all objets.
    I'm supposed to be able to see my data in the Dimensions and the Cubes now but I'm getting a new error:
    ENT-06965
    ENT-06965 : La création du gestionnaire de métadonnées BI Beans à partir d'OLAP et des informations du catalogue a échoué.
    ENT-06965 : La création du gestionnaire de métadonnées BI Beans à partir d'OLAP et des informations du catalogue a échoué.
         at oracle.wh.ui.owbcommon.dataviewer.dimensional.DataViewerConnection.connect(DataViewerConnection.java:153)
         at oracle.wh.ui.owbcommon.dataviewer.dimensional.DimDataViewerMain.BIBeansConnect(DimDataViewerMain.java:433)
         at oracle.wh.ui.owbcommon.dataviewer.dimensional.DimDataViewerMain.init(DimDataViewerMain.java:202)
         at oracle.wh.ui.owbcommon.dataviewer.dimensional.DimDataViewerEditor._init(DimDataViewerEditor.java:68)
         at oracle.wh.ui.editor.Editor.init(Editor.java:1115)
         at oracle.wh.ui.editor.Editor.showEditor(Editor.java:1431)
         at oracle.wh.ui.owbcommon.IdeUtils._tryLaunchEditorByClass(IdeUtils.java:1431)
         at oracle.wh.ui.owbcommon.IdeUtils._doLaunchEditor(IdeUtils.java:1344)
         at oracle.wh.ui.owbcommon.IdeUtils._doLaunchEditor(IdeUtils.java:1362)
         at oracle.wh.ui.owbcommon.IdeUtils.showDataViewer(IdeUtils.java:864)
         at oracle.wh.ui.owbcommon.IdeUtils.showDataViewer(IdeUtils.java:851)
         at oracle.wh.ui.console.commands.DataViewerCmd.performAction(DataViewerCmd.java:19)
         at oracle.wh.ui.console.commands.TreeMenuHandler$1.run(TreeMenuHandler.java:188)
         at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
         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)
    Anyone has information in regards to this error?
    Message was edited by:
    EGil

  • Building Dimensions and Cubes in 11.1

    Hi Experts,
    Can anyone provide me a weblink or atleast steps as to how to create a Dimensions and Cubes in OWB 11.1.
    For practice purpose i am accessing HR User. In there i have selected Locations and Countries table and is using it to create the Place_Dim (Place Dimension)
    Issues:
    1. What are Levels and Heirarchiies
    (In ROLAP its asking me to use the surrogate Key i both the levels)
    2. It is asking me to bound it to table or view. I have never seen any help regarding in bounding and out bounding in the tool.
    Please help.
    Regards,
    Ravi Remje

    Many Thanks Dave for your help. The links are very helpfull.
    I have a silly doubt in my mind. Kindly apologize for my dumbness.
    Concerns:
    I went through the OWB tool and came to the conclusion that the DIMENSIONS and CUBES are logical object. However, if i want to use it as a Physical table, is it any way as in how we can use the simple tables as different types of dimensions and facts by changing their loading type. Is it any possible way to implement the same feature for DIMENSION and CUBE objects. I dont want them to be used as views but as a table.
    Please help.
    Regards,
    Ravi Remje

  • Webi report: Issue Cannot retrieve dimensions from Cube

    Hello Experts,  We're facing an issue with a partical set of Webi reports in Quality environment. The reports are BW reports based on OLAP BICS connectivity on top of Bex queries.y  Below is the scenario and the issue:  1. The backed Bex queries have been trasported to Quality BW system and they're running fine when run from RSRT or Bex analyzer. 2.The Webi reports along with the BICS connections have been migrated to the Quality box and the BICS connections have been editied so that they point to the Quality BOX bex queries and they're testing and responding to the connection successfully. 3. The Webi reports pointed to the Dev Box in the Dev BOBJ system are working fine, but when the same reports for which the connections were repointed in Quality as above, are giving the error "Cannot Retrieve Dimensions from Cube".  Steps taken: a. Deleted the reports and the BICS connection from Quality environment and remigrated the reports,connecitons and changed the connecitons but still the issue persists. b.Tried finding the root cause and got the following issue in the Bex query in Quality: There are filters put in the Bex query . All other filters are working fine except 0CALMONTH. We tried putting all sorts of variables on 0CALMONTH, but the moment a variable is put on 0CALMONTH, this issue occurs. But when we tried removing the variable from 0CALMONTH in filters and restricted it to a single value, the Report works fine.  However the same is not an issue in the Dev Box and all queries with similar variables are working fine.  So we're thinking this might be an issue on the BW backend and the cube might have to be transported again to the Quality Box.  ANy quick suggestions or inputs on this would be greatly appreciated.  Thanks and regards, Abhishek

    Hi Abhishek,
    I am facing same issue.Have you resolve this issue?
    Regards,
    Rajesh

  • Universe Designer: Error getting dimensions for cube

    -Using Business Objects Edge 3.1 SP2
    -SAP BW 7.0 (patch level 21)
    This is quite odd behavior that seemed at first an authorization issue, but now I am uncertain.
    -Attempting to create a Universe based on a Infocube.
    -Universe connection is created with no problem using user 'ABC'
    -Using Universe Designer on the BOBJ server, no issues creating the Universe
    -Using Universe Designer on a users desktop, the Universe fails to create with error message:
    A runtime exception has occurred. (Error getting dimensions for cube $0SD_C03 (catalog $INFOCUBE): Unknown error)
    -Change the connection to use user 'DEF', the Universe creates just fine on the desktop
    -Behavior is not exclusive to one BW object, happens no matter what 'ABC' tries to access from this desktop
    So, at first I am thinking authorizations, but then the universe create would fail on the server as well.  If it is environmental, what could possibly affect this behavior.
    Any ideas before I submit to SAP Support?
    Edited by: Kevin Smolkowicz on May 5, 2010 12:40 PM
    Edited by: Kevin Smolkowicz on May 5, 2010 12:41 PM

    Oddly enough it was an authorization issue.
    When authenticating against the SAP source system from Universe Designer on either the workstation or server, both traces show a missing authorization for RFC_NAME = RASB
    This setting is not found in referenced SAPu2019s guides or whitepapers under suggested authorizations for Universe create.  What remains unexplained is why using the same credentials from 2 different computers had a different response.

  • How to import SH Sample Dimensions and Cubes with OWB Client

    Hi, is there a functionality to import the Dimensions and Cubes from the sample to reuse and manipulate them within the OWB Client?
    I can add Dimensions in the Enterprise Manager but mapping should be difficult- right?
    Specs: DB 10g rel2, OWB 10.1.0.4

    dimension - either define a table on your own, or use the data modeler and physically define a new dimension.
    Cube - same as above.
    as for levels and hierarchies, this can also be done in the data modeler. You can specify keys, levels, attributes, measures...all that stuff for dims and facts. There many tabs on the lower half of the dimension modeler screen that control this.
    Check out the oracle by examples for easy tutorials.

  • View dimension mysteriously filled with YTD in Essbase adapter

    Hi,
    I don't understand how my view column is automatically filled with the value YTD during my FDM import.
    I have a source file without a view dimension, i have no view dimension in my import format i have 'YTD_Inp' as the no-data value in the dimension specification.
    But still the view in the export is filled with YTD.
    When i change my datavalue dimension to View and set YTD_INP as the no data value it works fine.
    Has anybody an idea where the YTD comes from and how i can change it to YTD_Inp?
    Thanks in advance,
    Marc

    This is what we do for our HFM adapter to get the View dimension to display Periodic rather than YTD.
    Enable the View dimension in workbench for the adapter (sounds like you did this, we figure this would be enough but it didn't work for us either)
    In your import group, add another import format line; add one for View. I generally say take field 1 of 1 as I am doing CSV. Under the script column just enter the value "YTD_Inp".
    View | 1 | 1 | YTD_Inp
    This should write YTD_Inp as the View to every record that is imported/validated/exported.
    Hope this works!

  • Using dimension and cube operator

    hi
    I am facing problem in using this dimension and cube operator..
    Actually I want to create a sales data with dimensions as time,customer and product
    After creating a dimension in owb I get a table created attached with it same is the case with cube operator
    so where should I store my measures in the cube or the table created and where to store the data about dimensions in the table created.
    and finally how to use them in mapping to retrieve the data stored
    Thanks

    It sounds like you are not getting any matching keys for loading into the cube.
    Do you have a time dimension created by OWB in the cube? The key used by the cube operator for an OWB time dimension is a formatted number. The time dimension keys are stored as follows;
    Day Level - YYYYMMDD
    Month Level - YYYYMM
    Week Level - YYYYWW
    Quarter - YYYYQ
    Year - YYYY
    If you have a source that has a SQL date datatype for example and want to construct the key for a cube's time dimension at the day level something like the following expression can be used to construct the time reference from a SQL date...
    to_number(to_char( time_key, 'YYYYMMDD'))
    It may not be this but just a thought.
    Cheers
    David

  • Error during viewing the OLAP cubes

    Hi ALl,
    Thanks for you time.
    I recently installed a new development environment of BOXI-R2 sp4 and then imported all the contents from another existing BOXI-R1 environment.
    I can now see all my existing UNIVERSES properly.
    However each time I try to view the OLAP cubes on the dashboard, the below error is thrown.
    Was wondering if anyone out there faced the same problem?
    Any help is deeply appreciated.
    Regards,
    Steve
    HTTP Status 500 -
    type Exception report
    message
    description The server encountered an internal error () that prevented it from fulfilling this request.
    exception
    org.apache.jasper.JasperException
         org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:372)
         org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
         org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
    root cause
    com.crystaldecisions.thirdparty.org.omg.CORBA.UNKNOWN  minor code: 0x0  completed: No
         com.crystaldecisions.thirdparty.com.ooc.OB.Util.unmarshalSystemException(Util.java:295)
         com.crystaldecisions.thirdparty.com.ooc.OB.GIOPClientWorker.execute(GIOPClientWorker.java:598)
         com.crystaldecisions.thirdparty.com.ooc.OB.GIOPClientWorkerThreaded.receiverRun(GIOPClientWorkerThreaded.java:595)
         com.crystaldecisions.thirdparty.com.ooc.OB.GIOPClientWorkerThreaded$ReceiverThread.run(GIOPClientWorkerThreaded.java:137)
    note The full stack trace of the root cause is available in the Apache Tomcat/5.0.27 logs.

    The stack trace from Tomcat log attached:
    -06-16 15:39:44 StandardWrapperValve[action]: Servlet.service() for servlet action threw exception
    java.lang.IllegalStateException: Cannot forward after response has been committed
         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:324)
         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
         at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:670)
         at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:637)
         at org.apache.jsp.scripts.tools.err_005fpage_jsp._jspService(err_005fpage_jsp.java:83)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704)
         at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590)
         at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:510)
         at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966)
         at org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:581)
         at org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:787)
         at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:758)
         at org.apache.jsp.jsp.dashboard_jsp._jspService(dashboard_jsp.java:658)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704)
         at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:474)
         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:409)
         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
         at org.apache.struts.action.ActionServlet.processActionForward(ActionServlet.java:1759)
         at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1596)
         at com.crystaldecisions.webapp.struts.framework.CrystalUTF8InputActionServlet.process(CrystalUTF8InputActionServlet.java:29)
         at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
         at java.lang.Thread.run(Thread.java:534)
    2009-06-16 15:45:18 StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception
    com.crystaldecisions.thirdparty.org.omg.CORBA.UNKNOWN  minor code: 0x0  completed: No
         at com.crystaldecisions.thirdparty.com.ooc.OB.Util.unmarshalSystemException(Util.java:295)
         at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPClientWorker.execute(GIOPClientWorker.java:598)
         at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPClientWorkerThreaded.receiverRun(GIOPClientWorkerThreaded.java:595)
         at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPClientWorkerThreaded$ReceiverThread.run(GIOPClientWorkerThreaded.java:137)

  • OWB 11.2.0.1 dimension and cube operators + ODBC target database

    Hi,
    We are considering using OWB to populate a netezza data mart making use of the dimension and cube operators.
    Could we use OWB for this/is it supported in this manner or do we need to use another ETL tool/workaround.
    Understand OWB supports ODBC as target.
    Any advice much appreciated.
    Thanks

    Hi
    You can have ODBC targets but the cube/dim operators use MERGE loading type so its not a tested/supported case using the operators with Netezza. It has been optimized for Oracle.
    Cheers
    David

  • Cannot find object after creating dimension and cube.

    I need to develop a project using olap api to get olap data.
    My db release is 10.1.0.2, owb is 10.1.0.4.
    After i create dimension and cube in owb, I cannot find any object i have created in owb. Except that in OEM, after i click the button dimension, there comes an message as that the dimension does not have complete metadata or was created by old release and OEM will create a metadata for it. After that, I can find the dimension in AWM and get the imformation using olap api.
    However, there is no measure button in OEM, I cannot find the measures in measure folder. So that i cannot get the information of the MdmMeasureDimension using olap api.
    Can somebody help me with this issue? Thanks!

    With OWB 10.1 and prior releases to get OLAP metadata for a dimension or cube you must have used the OWB transfer wizard to deploy the OLAP metadata. This bridge basically creates and executes a script with all of the CWM calls to create the OLAP dimension and cube metadata.
    When you deployed the dimension from OWB in 10.1 it only created the 'create dimension DDL' for the object.
    Cheers
    David

  • [ask] set view dimension

    Dear expert,
    So i am using EPMA for my consolidation app now, when i try to modify my period dimension into structure below
    BEFORE:
    Period
    ---------Quarter1
    -----------------Jan
    -----------------Feb
    -----------------Mar
    ---------Quarter2
    AFTER:
    Period
    ----Halfyear
    ---------Quarter1
    -----------------Jan
    -----------------Feb
    -----------------Mar
    ---------Quarter2
    deploy application failed. the message is to add another "view" dimension , because my period dimension generation has changed from 3 to 4.
    what i do is add another member into view dimension. lets call it "HTD" = half to date
    deply successful . but when i create data form . i can't find "HTD" in View dimension member selection . and i cant input in any intersection.
    how to add correct view dimension ?
    anyone ever experienced this issue ?
    Thanks for the advice

    Try ::::
    Period
    ----Halfyear1
    ---------Quarter1
    -----------------Jan
    -----------------Feb
    -----------------Mar
    ---------Quarter2
    ----Halfyear2
    ---------Quarter3
    ---------Quarter4
    Regards
    Kiran TR
    Edited by: user13706063 on Oct 25, 2012 2:31 AM

Maybe you are looking for