Error when joining Dimensions

I get a strange error when I try to join my dimensions in order to map the cube - as I do not want to use key lookups (I do not neet outer join!):
First error message box:
"Trying to access invalid Object"
Trying to access invalid Object
Trying to access invalid Object
     at oracle.wh.repos.impl.foundation.CMPElement.checkStatus(CMPElement.java:248)
     at oracle.wh.repos.impl.foundation.CMPElement.getSubject(CMPElement.java:102)
     at oracle.wh.repos.impl.foundation.CMPElement.getPhysicalName(CMPElement.java:859)
     at oracle.wh.repos.impl.mapping.WBMappingIdentityImpl.getPhysicalName(WBMappingIdentityImpl.java:148)
     at oracle.wh.repos.impl.mapping.WBMappingIdentityImpl.getName(WBMappingIdentityImpl.java:132)
     at oracle.wh.ui.mapping.MappingGraphNew.refreshParameterGroup(MappingGraphNew.java:3149)
     at oracle.wh.ui.mapping.MappingGraphNew.refreshComponent(MappingGraphNew.java:2927)
     at oracle.wh.ui.mapping.MappingGraphNew.refreshMappable(MappingGraphNew.java:2868)
     at oracle.wh.ui.mapping.MappingGraphNew.processCreatedEdge(MappingGraphNew.java:2646)
     at oracle.wh.ui.mapping.MappingGraphNew.createEdge(MappingGraphNew.java:2466)
     at oracle.wh.ui.mapping.MappingGraphNew.handleEdgeGesture(MappingGraphNew.java:2443)
     at oracle.wh.ui.mapping.MappingGraphNew.change_PROPERTY_EDGE_COUNT(MappingGraphNew.java:2158)
     at oracle.wh.ui.mapping.MappingGraphNew.propertyChange(MappingGraphNew.java:1985)
     at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:252)
     at oracle.bali.dbUI.graph.jle.GraphCanvas.firePropertyChange(Unknown Source)
     at oracle.bali.dbUI.graph.jle.GraphCanvas.__addEdge(Unknown Source)
     at oracle.bali.dbUI.graph.jle.NodeLinkTool.processLink(Unknown Source)
     at oracle.bali.jle.tool.LinkTool.processMouseReleased(Unknown Source)
     at oracle.bali.dbUI.graph.jle.NodeLinkTool.processMouseReleased(Unknown Source)
     at oracle.bali.jle.tool.BaseTool.mouseReleased(Unknown Source)
     at oracle.bali.jle.tool.CompoundTool._processJLEEvent(Unknown Source)
     at oracle.bali.jle.tool.CompoundTool.mouseReleased(Unknown Source)
     at oracle.bali.jle.JLECanvas.processJLEEvent(Unknown Source)
     at oracle.bali.jle.GlassPane._redispatchToTool(Unknown Source)
     at oracle.bali.jle.GlassPane.processEventImpl(Unknown Source)
     at oracle.ewt.lwAWT.LWComponent.redispatchEvent(Unknown Source)
     at oracle.ewt.event.tracking.GlassMouseGrabProvider$Disp._redispatchEvent(Unknown Source)
     at oracle.ewt.event.tracking.GlassMouseGrabProvider$Disp._redispatchEvent(Unknown Source)
     at oracle.ewt.event.tracking.GlassMouseGrabProvider$Disp.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Component.java:5100)
     at oracle.ewt.lwAWT.LWComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Component.java:4897)
     at java.awt.Container.processEvent(Container.java:1569)
     at oracle.ewt.lwAWT.LWComponent.processEventImpl(Unknown Source)
     at oracle.ewt.lwAWT.LWComponent.redispatchEvent(Unknown Source)
     at oracle.ewt.lwAWT.LWComponent.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Component.java:3615)
     at java.awt.Container.dispatchEventImpl(Container.java:1627)
     at java.awt.Component.dispatchEvent(Component.java:3477)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
     at java.awt.Container.dispatchEventImpl(Container.java:1613)
     at java.awt.Component.dispatchEvent(Component.java:3477)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
Second box (behind the first one)
"API: length is not supported for data type NUMBER"
API8015: length is not supported for data type NUMBER.
API8015: length is not supported for data type NUMBER.
     at oracle.wh.repos.impl.mapping.WBMappingParameterImpl.validateDataType(WBMappingParameterImpl.java:226)
     at oracle.wh.repos.impl.mapping.WBMappingParameterImpl.setLength(WBMappingParameterImpl.java:603)
     at oracle.wh.service.impl.mapping.component.Join.mappableAdded(Join.java:812)
     at oracle.wh.repos.impl.mapping.WBStageComponentImpl.mappableAdded(WBStageComponentImpl.java:544)
     at oracle.wh.repos.impl.mapping.WBMappableImpl.mappableAdded(WBMappableImpl.java:232)
     at oracle.wh.repos.impl.mapping.WBMappableImpl.addChild(WBMappableImpl.java:500)
     at oracle.wh.repos.impl.mapping.WBMappingParameterGroupImpl.addChild(WBMappingParameterGroupImpl.java:246)
     at oracle.wh.repos.impl.mapping.WBMappableImpl.constructAddChild(WBMappableImpl.java:123)
     at oracle.wh.repos.impl.mapping.WBMappingParameterImpl.<init>(WBMappingParameterImpl.java:155)
     at oracle.wh.repos.impl.mapping.WBMappingParameterImpl.createNew(WBMappingParameterImpl.java:317)
     at oracle.wh.repos.impl.mapping.WBMappableImpl.cloneMappable(WBMappableImpl.java:198)
     at oracle.wh.repos.impl.mapping.WBMappingParameterImpl.cloneMappable(WBMappingParameterImpl.java:328)
     at oracle.wh.repos.impl.mapping.WBMappableImpl.internalConnectTo(WBMappableImpl.java:469)
     at oracle.wh.repos.impl.mapping.WBMappableImpl.internalConnectTo(WBMappableImpl.java:367)
     at oracle.wh.repos.impl.mapping.WBMappingParameterImpl.connectTo(WBMappingParameterImpl.java:425)
     at oracle.wh.ui.mapping.MappingGraphNew.processCreatedEdge(MappingGraphNew.java:2626)
     at oracle.wh.ui.mapping.MappingGraphNew.createEdge(MappingGraphNew.java:2466)
     at oracle.wh.ui.mapping.MappingGraphNew.handleEdgeGesture(MappingGraphNew.java:2443)
     at oracle.wh.ui.mapping.MappingGraphNew.change_PROPERTY_EDGE_COUNT(MappingGraphNew.java:2158)
     at oracle.wh.ui.mapping.MappingGraphNew.propertyChange(MappingGraphNew.java:1985)
     at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:252)
     at oracle.bali.dbUI.graph.jle.GraphCanvas.firePropertyChange(Unknown Source)
     at oracle.bali.dbUI.graph.jle.GraphCanvas.__addEdge(Unknown Source)
     at oracle.bali.dbUI.graph.jle.NodeLinkTool.processLink(Unknown Source)
     at oracle.bali.jle.tool.LinkTool.processMouseReleased(Unknown Source)
     at oracle.bali.dbUI.graph.jle.NodeLinkTool.processMouseReleased(Unknown Source)
     at oracle.bali.jle.tool.BaseTool.mouseReleased(Unknown Source)
     at oracle.bali.jle.tool.CompoundTool._processJLEEvent(Unknown Source)
     at oracle.bali.jle.tool.CompoundTool.mouseReleased(Unknown Source)
     at oracle.bali.jle.JLECanvas.processJLEEvent(Unknown Source)
     at oracle.bali.jle.GlassPane._redispatchToTool(Unknown Source)
     at oracle.bali.jle.GlassPane.processEventImpl(Unknown Source)
     at oracle.ewt.lwAWT.LWComponent.redispatchEvent(Unknown Source)
     at oracle.ewt.event.tracking.GlassMouseGrabProvider$Disp._redispatchEvent(Unknown Source)
     at oracle.ewt.event.tracking.GlassMouseGrabProvider$Disp._redispatchEvent(Unknown Source)
     at oracle.ewt.event.tracking.GlassMouseGrabProvider$Disp.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Component.java:5100)
     at oracle.ewt.lwAWT.LWComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Component.java:4897)
     at java.awt.Container.processEvent(Container.java:1569)
     at oracle.ewt.lwAWT.LWComponent.processEventImpl(Unknown Source)
     at oracle.ewt.lwAWT.LWComponent.redispatchEvent(Unknown Source)
     at oracle.ewt.lwAWT.LWComponent.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Component.java:3615)
     at java.awt.Container.dispatchEventImpl(Container.java:1627)
     at java.awt.Component.dispatchEvent(Component.java:3477)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
     at java.awt.Container.dispatchEventImpl(Container.java:1613)
     at java.awt.Component.dispatchEvent(Component.java:3477)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
Don't know whats all that about, but I cannot join any more!
I'm currently using OWB 10.1.0.2.0
on a Oracle 9i 9.2.0.4 database
(Or should I not comine 9i with 10g??!!!)
Please advise me what to do!
Thanks
Mani

Hi Mani,
Something similar happened to me, when in a mapping I tried to connect a dimension to a joiner. The occurring error: API8015.
This was caused by a changed datatype, in my case I had changed a VARCHAR2 field into NUMBER.
The solution (as also suggested with bug 3116947), is to alter the datatype, it says into number but that's exactly (again: in MY case) where it goes wrong.
Therefore, I changed the datatype into DATE since this never has a length NOR a precision, and then changed it back into the desired datatype with appropriate properties. Now it works fine again.
Hope this helps - as a workaround that is ;-)
Cheers, Patrick
PS my OWB version is 9.2.0.4 (just upgraded from 9.2.0.2.8).

Similar Messages

  • Error when populating dimension

    I encountered the following error when trying to populate a dimension in Analytic Workspace Manager:
    action BUILDDATABASE failed on object <analytic_workspace>
    Does anyone know what that means?

    1) No SKEY_VAL is not a variable.
    2) This is my first attempt at using ODI, I did not create the SQL. All I did was to create a reverse a model against my MSSQL staging database and create and reverse a model against the planning application. Then I created an interface for the Account dimension in planning mapped the account, parent and description columns from my SQL table to the Planning dimension and I get this error. There are no columns called SKEY_VAL in either the source or the target and I have not created any objects with this name in ODI. I can see that ODI is asking for this column when I execute the interface, but I don't know why.

  • Error when maintaining dimension in AWM 10.1.0.4

    Hi,
    I am running AWM 10.1.0.4 on a 10.1.0.4 database. Have set up dimension, levels, hierarchy, and mappings. Everything OK, but when trying to maintain this dimension I get the following error message:
    oracle.AWXML.AWException: Action BUILDDATABASE failed on object OLAP_DBA1.TEST1
    at oracle.AWAction.BuildDatabase.Execute(BuildDatabase.java:414)
    at oracle.olap.awm.wizard.awbuild.BuildWizardHelper$1.construct(BuildWizardHelper.java:175)
    at oracle.olap.awm.ui.SwingWorker$2.run(SwingWorker.java:109)
    at java.lang.Thread.run(Unknown Source)
    Caused by: oracle.AWXML.AWException: oracle.express.ExpressServerException
    java.sql.SQLException: Ikke flere data å lese fra porten (No more data to read from the port)
    at oracle.AWXML.AWConnection.executeCommand(AWConnection.java:248)
    at oracle.AWAction.BuildDatabase.Execute(BuildDatabase.java:397)
    ... 3 more
    Caused by: oracle.express.ExpressServerException
    java.sql.SQLException: Ikke flere data å lese fra porten (No more data to read from the port)
    at oracle.express.spl.SPLExecutor.executeCommand(SPLExecutor.java:155)
    at oracle.AWXML.AWConnection.executeCommand(AWConnection.java:244)
    ... 4 more
    Any clues?
    Sverre

    There are posts on the OLAP forum covering this problem. Anthony Waite from the OLAP Product Management team has provided the following information:
    e new, default Model View in AWM 10.1.0.4.0 is based upon the OLAP Analytic Workspace API (a.k.a. AW/XML). Just to recap and further clarify my earlier post, you must pass the following requirements in order to use it:
    1) Be sure to be using the Enterprise Edition of the Oracle Database 10g.
    SQL> select banner from v$version where banner like 'Oracle%';
    You should see Oracle Database 10g Enterprise Edition.
    2) Be sure to have the Data Warehouse database configuration or the OLAP Option enabled.
    SQL> select parameter, value from v$option where parameter='OLAP';
    You should see OLAP TRUE.
    3) Be sure that the RDBMS 10.1.0.4 patch set has been completely installed. Users often miss the required Post-Installation Steps such as running catpatch.sql.
    SQL> select comp_name, version, status from dba_registry;
    You should see VALID and 10.1.0.4.0 for the OLAP components.
    4) The Oracle Database must have the compatibility mode of 10.1 to use the Model View as it relies on the unique features found in Oracle Database 10g.
    SQL> select name, value, description from v$parameter where name ='compatible';
    You should see 10.1, not 9.2 or earlier.
    5) Please refer to the patchnote.htm that is bundled with 10.1.0.4.0 patch set. Only you are aware of what type of database configuration you have. You will want to pay close attention to "7.2.1.3 Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters" and "7.2.2 Upgrade the Release 10.1 Database".
    Basically, I believe you have missed these required steps after installing the 10.1.0.4.0 patch set from the OUI: (pasted from the patchnote.htm)
    For the full discussion please refer to this link:
    Re: Error trying to Analytic Workspace using latest version AWM 10.1.0.4
    Hope this helps
    Keith
    Oracle Business Intelligence Product Management
    BI on Oracle: http://www.oracle.com/bi/
    BI on OTN: http://www.oracle.com/technology/products/bi/
    BI Beans http://www.oracle.com/technology/products/bib/index.html
    Discoverer: http://www.oracle.com/technology/products/discoverer/
    BI Software: http://www.oracle.com/technology/software/products/ias/devuse.html
    Documentation: http://www.oracle.com/technology/documentation/appserver1012.html
    BI Samples: http://www.oracle.com/technology/products/bi/samples/
    Blog: http://oraclebi.blogspot.com/

  • Error when processing dimension using XMLA script

    I am hopeful that someone has an answer for this...
    I am in the process of deploying SQLServer 2014 and have been running in parallel with my production environment for 2 weeks with no issues.  Yesterday morning, my primary data load job failed while executing a process dimension script.  The script
    does a process update on multiple dimensions, but fails on the product dimension.  This is the script:
    <Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
    <Parallel>
    <Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2">
    <Object>
    <DatabaseID>WestLakeSales</DatabaseID>
    <DimensionID>Dim Product</DimensionID>
    </Object>
    <Type>ProcessUpdate</Type>
    <WriteBackTableCreation>UseExisting</WriteBackTableCreation>
    </Process>
    </Parallel>
    </Batch>
    It processes the attributes and starts processing the associated measure groups, then fails with a return code that I cannot find any information on:
    <return xmlns="urn:schemas-microsoft-com:xml-analysis">
    <results xmlns="http://schemas.microsoft.com/analysisservices/2003/xmla-multipleresults">
    <root xmlns="urn:schemas-microsoft-com:xml-analysis:empty">
    <Exception xmlns="urn:schemas-microsoft-com:xml-analysis:exception" />
    <Messages xmlns="urn:schemas-microsoft-com:xml-analysis:exception">
    <Error ErrorCode="3238133769" Description="" Source="Microsoft SQL Server 2014 Analysis Services" HelpFile="" />
    </Messages>
    </root>
    </results>
    </return>
    At the end of the job log it just shows this:
    Finished processing the 'Inventory Weekly 2009 08' partition.
    Processing of the 'Inventory Weekly 2009 06' partition has started.
    Finished processing the 'Inventory Weekly 2009 06' partition.
    Processing of the 'Inventory Weekly 2010 02' partition has started.
    The job completed with failure.
    The job completed with failure.
    The job completed with failure.
    Execution complete
    When I run process update from Studio it processes all of the attributes and measure group partitions, then throws a single 'error' result with no description or message.  It appears that all partitions process successfully.  See the screen shot:
    This script ran fine up until yesterday.  There were no system changes.  The same script is currently running fine on the production SQLServer 2008 instance.
    Anyone see anything like this happening in SSAS 2014?  Any tips on further trouble shooting?

    Hi Bendare2,
    Thank you for sharing your solution.
    Regards,
    Simon Hou
    TechNet Community Support

  • Error when building dimension or deleting workspace

    I am just starting to work with AW and trying to get past some initial bumps. I initially created 2 AWs but did all of my work in just one of them, using a small, 20 row dataset that I created. But soon I was getting too many errors in that AW and figured something was corrupted so I deleted it.
    But now, when I try to create a simple dimension (with 2 levels) in the remaining AW, I get the error:
    Errors have occurred during xml parse
    <Line 3, Column 15>: <Line 3, Column 15>: XML-20210: (Fatal Error) Unexpected EOF.
    Also the error:
    The transaction is not committable: "An error has occurred on the server
    Error class: Express Failure
    Server error descriptions:
    DPR: Unable to create server cursor, Generic at TxsOqDefinitionManager::generic<CommitRoot>
    INI: Unable to parse XML string sent from the client to the server, Generic at XML Parser Errors:
    Error processing subelement: <StandardDimension><Attribute><BaseAttribute><Classification>
    Error processing tag: Classification:
    Error returned by xsOqXmlParserExecute.
    Error processing subelement: <StandardDimension><Attribute><BaseAttribute><Classification>
    Error processing tag: Classification:
    Error returned by xsOqXmlParserExecute.
    Error processing subelement: <StandardDimension><Attribute><BaseAttribute><Classification>
    Error processing tag: Classification:
    Error returned by xsOqXmlParserExecute.
    Error processing subelement: <StandardDimension><Attribute><BaseAttribute><Classification>
    Error processing tag: Classification:
    Error returned by xsOqXmlParserExecute.
    Then when I try to DELETE this second AW and start completely afresh I get the error:
    An error has occurred on the server
    Error class: Express Failure
    Server error descriptions:
    DPR: Unable to create server cursor, Generic at TxsOqDefinitionManager::generic<CommitRoot>
    INI: Unable to parse XML string sent from the client to the server, Generic at XML Parser Errors:
    Error processing subelement: <StandardDimension><Attribute><BaseAttribute><Classification>
    Error processing tag: Classification:
    Error returned by xsOqXmlParserExecute.
    Error processing subelement: <StandardDimension><Attribute><BaseAttribute><Classification>
    Error processing tag: Classification:
    Error returned by xsOqXmlParserExecute.
    Error processing subelement: <StandardDimension><Attribute><BaseAttribute><Classification>
    Error processing tag: Classification:
    Error returned by xsOqXmlParserExecute.
    Error processing subelement: <StandardDimension><Attribute><BaseAttribute><Classification>
    Error processing tag: Classification:
    Error returned by xsOqXmlParserExecute.
    Does anyone have any ideas what is causing this? Thanks. John

    David. Thanks very much. The patch would not take to the database (just hung) so I was given a brand new box and fully upgraded DB. Works fine so far. A bit of a silver lining I guess. {:>) -John                                                                                                                                                                                                                                                                                                                                                                                                       

  • Getting error when processing dimension

    Hi All,
             I am working on BPC5.1.when iam processing the dimension iam getting the error.
    in OPTIMIZE SCHEMA---Skip optimize schema step,
    in UPDATE OLAP----
    Skip updating OLAP step..
    RESULT---FAIL...
    this are the errors iam getting.can some body help me in solving these issues..
    All the best.
    Regards,
    Naresh.K..

    Hi Sorin!
    Our technical team managed to find the immediate cause for the problem, and a solution.
    According to them there was a corruption on a speciffic OLAP file. By deleting it, they allowed it to be recreated on the next application processing. The file in question was found in \Microsoft SQL Server\MSSQL.2\OLAP\Data\UGF.0.db\<APPLICATION>.38.cub.xml
    Where <APPLICATION> is the name of the problematic cube.
    After that everything is working.
    I still don't know why the file was corrupted, but at least now we have a quick & repeatable solution in case this happens again.

  • 0xc0040396 Error When Joining EMS Array

    I am trying to migrate ISA 2006 Enterprise to TMG 2010 Enterprise.  I built the Windows 2008 R2 EMS server and successfully imported the configuration which I had exported from ISA (single server "array").  I then installed
    TMG 2010 on my intended first array member, which is a Windows 2008 R2 server with the same name and IP address as the original ISA server.  The new server thus has a certificate with the same subject name as the one used by the old ISA server. 
    I also imported a certificate which is used for an OWA publishing rule into the new server.
    When I try to join this server to the array, it can connect to the EMS but it eventually fails with this error:
     "0xc0040396 SSL is enabled for the internal network.  You must specify a certificate to use for SSL authentication."
    I'm not entirely sure what the error means.  I've checked the Web Proxy tab for the Internal Network on the new server and SSL was not enabled.  I've tried enabling it and specifying the certificate with the subject name of the server, but that
    made no difference.  I also tried using the OWA certificate, which of course also failed (no surprise there).  (I don't think the old ISA server has SSL enabled on the Internal Network anyway, but I'll need to confirm this.)
    Does anyone have an idea as to how I resolve this?  I'm guessing that maybe I'm missing the meaning of the error and I'm hoping someone else can help with this.  I'm not finding much about this on Web about this error.
    Thanks in advance for any help.

    I think I may have gotten around the problem. 
    On the original ISA server it turned out that SSL was enabled on the Internal Network, so I disabled that, exported the configuration again and imported that to the EMS.  Now when I try to join the TMG to the array, the EMS can communicate with it,
    which seems to be further than I got before.  That said, I think it may have been a mistake to import the ISA config a second time because I now get a different error that seems to suggest an old version is detected.  If that's the case,
    then I think I can just rebuild the EMS and import the ISA config again, then attempt to join the TMG to the array again.
    Both the EMS and the TMG server were at RTM version, so I also got them both up to Service Pack 2.  I don't think that made any difference with the issue, but it's worth mentioning. 
    Based on what I did, I do have a question:  If an ISA 2006 config is imported to TMG 2010 EMS, will importing the same config a second time to the same EMS cause problems?  My thinking is that once the config is imported, the imported settings
    are upgraded to TMG 2010 and that the second import may break things because of that.  Knowing the answer to that question will tell me whether or not I need to rebuild the EMS.

  • Report - Time out Error when Joining EKPO & MSEG

    Hi All,
    This is my code:
    SELECT    EKKO~EBELN
                EKKO~LIFNR
                EKKO~BUKRS
                EKKO~EKORG
                EKPO~EBELP
                EKPO~TXZ01
                EKPO~MATNR
                EKPO~MENGE
                EKPO~MEINS
                EKPO~UNTTO
                EKPO~PSTYP
             FROM EKKO
            INNER JOIN EKPO ON
            EKKOEBELN = EKPOEBELN
            INTO TABLE T_EKPO
            UP TO P_MAX ROWS
            WHERE  EKKO~EBELN IN S_EBELN
            AND EKKO~BSART IN S_BSART
            AND EKKO~LIFNR IN S_LIFNR
            AND EKKO~EKORG IN S_EKORG
            AND EKKO~EKGRP IN S_EKGRP
            AND EKKO~BEDAT IN S_BEDAT
            AND EKPO~MATNR IN S_MATNR
            AND EKPO~WERKS IN S_WERKS
            AND EKPO~MATKL IN S_MATKL
            AND EKPO~PSTYP IN R_PSTYP
            AND EKPO~KNTTP IN S_KNTTP.
       SELECT MBLNR
               ZEILE
               ERFMG
               EBELN
               EBELP
               FROM MSEG
               INTO TABLE T_MSEG
               FOR ALL ENTRIES IN T_EKPO
               WHERE EBELN = T_EKPO-EBELN
               AND EBELP = T_EKPO-EBELP.
    Now i am getting time out error. Can Any one suggest how can i solve this issue.

    Identical problem by different (?) user:
    Joining tables EKPO & MSEG

  • Error when building dimension using AWM

    Hi Gurus,
    I am trying to build a dimension using AWM 11.1.0.7.0B Standalone. My Database version is _11.1.0.6.0._
    The moment i start to create a New Dimension, i get the below error.
    The transaction is not committable: "An error has occurred on the server
    Error class: Express Failure
    Server error descriptions:
    DPR: Unable to create server cursor, Generic at TxsOqDefinitionManager::g
    The transaction is not committable: "An error has occurred on the server
    Error class: Express Failure
    Server error descriptions:
    DPR: Unable to create server cursor, Generic at TxsOqDefinitionManager::generic<CommitRoot>
    INI: Unable to parse XML string sent from the client to the server, Generic at XML Parser Errors:
    Error processing subelement: <StandardDimension><Attribute><BaseAttribute><Classification>
    Error processing tag: Classification:
    Error returned by xsOqXmlParserExecute.
    +"+
    +at oracle.olap.awm.dataobject.dialog.PropertyViewer.doCreateAction(Unknown Source)+
    +at oracle.olap.awm.dataobject.dialog.CreateDialogHostActionThread.doAction(Unknown Source)+
    +at oracle.olap.awm.ui.dialog.ThreadedDialogActionThread.run(Unknown Source)+
    Please help!!!!!
    +*Regards,*+
    +*Ravi R*+

    The initial release of OLAP in 11.1.0.6 was not stable. Please upgrade to at least database 11.1.0.7, and preferably 11.2.0.3. If you move to 11.1.0.7, then you should apply the "OLAP D Patch", #9147749. See the OLAP certification page for more details.
    http://www.oracle.com/technetwork/database/options/olap/olap-certification-092987.html

  • Classic duplicate key error when processing dimensions

     I have a dimension attribute that has a list of values below
    atlanta
    atlanta
    Atlanta
    Atlanta
    Atlanta
    ATLANTA
    it has caused the duplicate key errors. I've checked the colloation property of AS server and it's set to Latin1_general with case-sensitive UNCHECKED.... I wonder why I still get this type of errors? 
    thanks
    --Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

    You would need to use a case-sensitive collation for these not to be considered duplicates and even then, on closer inspection, I still see duplicates in your data.  There are only three distinct case-sensitive values out of the six examples you've
    provided: atlanta, Atlanta, and ATLANTA.
    Jason

  • Error when processing dimensions

    Hello,
    I'm working with BPC 7.0 NW and I'm trying to process the dimension P_ACC (copied from the APSHELL directly) and I get the following errors:
    "Failed to expand K2 function for dimension P_ACCT's member formulas" and
    "MDX statement error:"You do not have the authorization for component !!"
    Any idea about how to solve this erros?
    Thanks and regards,
    Ana

    Hi Ana
    Its called MDXLib.lgl not MDX.lgl
    find that in the appset apshell and try to copy the same in similar path in your appset.
    I think it must be in logic files folder not sure of exact path.
    But that should not be issue here since you are using direct MDX Query, can you just remove that one formula and process dimension and then remove the cache
    Then add back the formula and then see how it works, then try using some other account for now as divisor (Denominator) and see what happens
    Thanks and Regards
    Harish B K

  • I have an error when join pc's to domain windows server 2012 r2

    Hello everyone
    I have a problem to join computers to the domain.
    I'm doing the procedure is as follows.
    1.'ll properties pc
    2. I click Change to join the domain.
    3. I request the domain administrator credentials
    4. I get the window that has joined the domain correctly and then click accept gives me the following error:}
    This error message me with all computers that attempt to join the domain.
    I have reviewed forums, I have already set the WINS part and for the network adapter. Not if it's a problem with the server version domain is Windows Server 2012 R2.
    I appreciate your help.
    regards
    Miguel Solano

    Hello everyone
    I have a problem to join computers to the domain.
    Well I can not understand Spanish but I guess it is related to RPC. :D
    In that case, you need to make sure your DNS entries are correct in clients NIC. Similar threads here:
    "RPC Server Unavailable" while attempting to Join domain
    Windows
    Server Troubleshooting: "The RPC server is unavailable"
    Mahdi Tehrani   |  
      |  
    www.mahditehrani.ir
    Please click on Propose As Answer or to mark this post as
    and helpful for other people.
    This posting is provided AS-IS with no warranties, and confers no rights.
    How to query members of 'Local Administrators' group in all computers?

  • Error when joining a leopard server to an active directory

    Hi all,
    I'd like to add my mac os x server to an active directory. If I fill the "Active Directory Domain" with ip address, "Unable to add the domain, there was no response from the ip,please check that the address you entered is correct", if I fill with domain name, "Unable to add domain, An unexpected error of type -14987 (eUndefinedError) occurred.
    What's going on there???

    Hi all,
    I'd like to add my mac os x server to an active directory. If I fill the "Active Directory Domain" with ip address, "Unable to add the domain, there was no response from the ip,please check that the address you entered is correct", if I fill with domain name, "Unable to add domain, An unexpected error of type -14987 (eUndefinedError) occurred.
    What's going on there???

  • Processing error when doing a drillthrough agianst a Rolap dimension, working with MOLAP

    Hi,
    I'm having a drillthrough dimension (fact) that i'm using for drillthrough scripts. One thing that I have come a cross is that I get processing errors when I run queries agianst a ROLAP dimension where as it works agianst the same dimension set
    as MOLAP. This is kind of confusing me.
    The error message i get is like this one:
    Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined
    limit of allowable errors for the operation.
    Errors in the OLAP storage engine: An error occurred while the 'Journal NO' attribute of the 'GLFact' dimension from the 'XXX' database was being processed.
    I found a article about this
    http://sqlblog.com/blogs/marco_russo/archive/2009/01/17/issues-executing-a-drillthrough-with-a-rolap-dimension.aspx
    But I have set KeyDuplicate, Keynotfound, Nullkeyconvertedtounknown and NullKeynotallowed to ignoreerror and still it doesn't work.
    So my questions are 2:
    1. Do anyone have a solution for me? Or having any thoughts about this?
    2. When switching over to MOLAP the processingtime takes about 30 min. How can i decrease this to a minimum?
    This is all implemented in SSAS 2005.

    I'm getting the exact same error when attempting to drill down on a rolap dimension associated to the cube.  the cube is molap, but the dimension is rolap to reduce processing time (processing dimension using molap spike my 4 core processing to 100%
    for 4 minutes due to all the select DISTINCT on the attributes (about 10)). 
    I too have seen the article about KeyDuplicate but I think this is a different issue.  Anyone figure out the problem?
    Version: SSAS 2012 SP2
    Example of error:
    Server: The current operation was cancelled because another operation in the transaction failed. Errors in the OLAP storage engine: An error occurred while the 'City' attribute of the 'NameAddress'
    dimension from the 'MyDatabase' database was being processed. Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.

  • Flow accept error when using ANSI join syntax

    Hi
    I had a region populated by a query joining two views (one in-line using connect by). When trying to create the region if the join was coded using ANSI syntax (INNER JOIN .... USING) I got a flow accept error when either trying to proceed using the wizard, or apply changes when editing the region.
    After changing to the old style Oracle join (using predicates), I was able to create the region and everything worked ok. I found the solution after reading this post Error 404 wwv_flow.accept was not found in which the OP says he would raise a bug. Did the bug get raised? I ask since his problem arose whilst he was selecting from a view using ANSI joins and using instead of triggers, and I was joining an in-line view to a view using ANSI joins and instead of triggers, but neither view has been changed, just the join syntax. The view defined in the database is used in other regions and works fine. This could indicate the OP's problem was fixed, but one still exists.
    Incidentally this is the only time I have used non-ANSI joins in the entire apex app - the rest work!. Unfortunately it is impossible for me to demo the app.
    Richard
    using ApEx 3.0.1.00.07 and 10g (10.2.0.1) EE on Wintel

    Tyler,
    Apologies, what I was trying to say was that I couldn't put the application on the Oracle APEX site.
    Yes, I do have a work-around, but that does not mean a bug may still exist. I count myself fortunate I saw that post and, therefore, experimented with the syntax of the join - there is no reason APEX should not accept ANSI join conditions, in fact , it does. The ANSI-joined SQL statement executed perfectly in TOAD and SQL*Plus, but I could not even save it in APEX.
    regards
    Richard

Maybe you are looking for