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/

Similar Messages

  • Error in Maintaining Dimension in AWM

    Hi,
    I am building up a workspace with 14 Dimensions. I have mapped the dimensions and Cubes to the source views and am trying to maintain them. When I go to Maintain Dimension, some of the dimensions are giving error:
    oracle.AWXML.AWException: Action BUILDDATABASE failed on object APPS.BULR
    Caused by: oracle.AWXML.AWException: ***Error Occured in BUILD_DRIVER: In __XML_SEQUENTIAL_LOADER: In __XML_LOAD_HIERS: In __XML_SET_GID_FREL: One or more loops have been detected in relationship BULR!BULR_IND_PARENTREL over BULR!BULR_IND. The 1 items involved are 42537.
    Each of these dimensions havs one "Value Based Hierarchy" and one attribute. I have checked the mappings and they are all correct. Any idea what could be causing this error?
    Thanks,
    Anshu

    This is a symptom of a problem in your hierarchy. This is not my area, but I believe it is trying to tell you that you have a loop in your hierarchy (A is the parent of B is the parent of A). This will take us a very long time to solve :-).
    Look carefully at the relationship named, and trace the parentage of the specified value. You should discover that there is a loop there.
    Jim

  • 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

  • AWM - error duirng maintain dimension process

    I get the following error when selecting the maintain option on the product dimension (PROD):
    An error has occurred on the server
    Error class: Express Failure
    Server error descriptions:
    INI: Error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>
    INI: XOQ-01711: Aggregation path for hierarchies on a dimension "PROD" is inconsistent, Generic at TxsOqStdFormCommand::execute
    I am running awm11.1.0.7.0B on db version 11G 11.1.0.7.0.
    Any ideas on what this means?
    Thanks,
    Frank
    Edited by: bmwrider on Sep 18, 2009 11:54 AM
    Edited by: bmwrider on Sep 18, 2009 11:57 AM

    The error indicates that there are some loops in your hierarchy (e.g: circular loop within same hierarchy) or inconsistencies in the definition of a specific member across hierarchies (e.g: each hierarchy is well defined on its own but one or more members of the dimension, present in multiple hierarchies, are defined inconsistently, in terms of its descendants, across hierarchies).
    If you have enabled the create dimension Materialized View option, try disabling it and rebuild/maintain the dimension. The build process for the dimension with "create MV" option enabled enforces stricter data quality checks than if this option is disabled (dimension MV not required/not created/not used for Query Rewrite).
    Also see links:
    [Thread: problem maintaining cube |http://forums.oracle.com/forums/thread.jspa?messageID=3507124&#3507124]
    [Thread: Error while populating Dimension |http://forums.oracle.com/forums/click.jspa?searchID=-1&messageID=3270334]

  • SSTemplate.xlt Error during 'Maintain Dimension Member' in BPC Admin

    Hi,
    While trying to 'maintain dimension member' in BPC administrator (BPC 7.0 Netweaver version) for a dimension,I get error message that 'C:\...Temp\SSTemplate.xlt' file could not be found.
    Due to this I am unable to maintain members for any dimension.
    If anyone has faced this issue and resolved it,could you please me out?
    Thanks in advance,
    Rinal

    Dear Rinal Parmar,
    I think that the dimension file which you mean is lose from the directory(the directory which you installed the SAP BPC). If you've backup the Appset before, please you find the dimensian file (.xlt) which is lose in the backup directory. After that, you copy paste into the exactly directory (the directory which you installed the SAP BPC). Then, You should process dimension and process application again.
    Thanks,
    Wandi

  • 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).

  • 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 output condition records

    Hello experts
    I m getting an error while maintaining output condition records using VV11. The error reads as "862     System error: system cannot read the structure for table B567". Can you pls help in identifying the root cause.
    I checked that the condition table 567 has he correct fields and the field catalogue has the fields.
    Thanks
    Regards
    Srikkanth

    Hello
    Try to regenerate the condition table B567 using the report RV12A001.
    Use TCode SE38, select usage 'B', table '567' and mark the boxes for following indicator
    - dictionary
    - reports and screens.
    Press execute and re-try by maintaining VV11 for the output.
    Regards
    JP

  • Bug when maintaining dimension data i AWM 10g

    Hi,
    I have been playing around with AWM 10g since the release and generally I'm very impressed with it. Easy and logical to work with.
    I have found what I believe is a bug though. The second time I load data to a dimension through the maintenance wizard and if I check the "Delete all attribute values of the selected dimensions" some dimensions start to behave wrong when trying to drill up and down.
    This can be replicated with the global dataset. I create the AW from the "Global Star Mapped" template. The first time I load data to all dimensions and cubes everything works correct. When I run the maintenance wizard again for all dimensions and cubes and check "Delete all attribute values of the selected dimensions" (without actually touching the source data) the result is that the Product and Channel dimensions don't work correct anymore. If I view the data of one of these dimensions it is not possible to drill by clicking the + to the left of the values. When viewing the cube in AWM and trying to drill down in those dimensions the only thing that happens is that the drill arrows disappears.
    The Time and Customer dimension are not affected so something must be different between these and the other dimensions. When I tried with one of my own test datasets all the dimensions malfunctions after the second load.
    The only way I have found to get it to work again is deleting the affected dimensions and starting again.
    Bent

    Yep, I confirmed the behavior on my configuration too. Bizarre... I did notice you can still drill if you use the pull-down menu rather than directly clicking on the + to the left of the values.
    Typically, a user would select this option if they would like the dimensional attributes in the analytic workspace to match the relational source. For example, your relational source has changed and you do not want these previous values to persist within the analytic workspace. In this case with the GLOBAL sample schema, the data source is the same so something funky is going on.
    By the way, if I encounter sudden odd behavior with the View Data feature (random known issue we are working on), I usually disconnect from the database and reconnect. Usually the behavior disappears. However, in this case it does not.
    I'll enter this into the bug system. Thanks for all the details. Much appreciated.

  • 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 maintaining GL Account for Revenue account determination in VKOA

    Hi all,
    I am getting the error "Entry V XXXX doesnot exist check your entry", when I try to maintain account assignment under one condition table in VKOA. This error doesnot come while maintaining account assignment for the same combination under a different condition table.
    (note: - I observe that in F4 help entries the Application/USage link is not displayed when I try for the condition table with issue. For all other condition tables, I am able to see the application/usage combination. I am not sure if this is an issue)
    Could you pl share your inputs to fix this issue.
    Regards
    Sri

    hi,
    Please check your input fields what your entering those entries has to be existed in the master.
    For example if your maintaining for table 002 -  Cust.Grp/Account Key
    Application V - Sales & Distribution COndition type KOFI Chart of acc 1000 Account assignment group for this customer AAG 01
    Account key ECC  G/L Account Number xxxxxxx should exist in the system.
    Please check you entries and try to enter your existing inputs or eles if you need to enter unexisted inputs you have to maintaine those inthere parent table for example if your enter GL 120000, if the GL is not exist in Chart of Acc 1000 you ahve to create GL 120000 in chart of acc 1000.
    I hope it will clear you.
    Regards,
    Rama Mohan Bangaru

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

  • 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

Maybe you are looking for

  • How to make a JPanel with a GridLayout scroll

    I am using a JPanel to hold around 100 buttons. The JPanel is using GridLayout to organise these buttons in rows of 3 buttons per row. i.e. buttonPanel.setLayout(new GridLayout(33,3)); As there are so many buttons they obviously don't all fit in the

  • Automatic variable Change of the Place item on a action

    I'm begining in the scripting area, but I'm lost realy.  I looking in a way to change the place automatic based on the filename/ folder. Today I do like this: I'm aplying a image in the back of a photo with automate batch. My actions goes in resume l

  • Mail logging

    How do I turn on logging for Mail 7.2 on OS X 10.9..2? I need to troubleshoot an issue with autodiscovery failing against an Exchange server. Thanks!

  • Facing problem in JFileChooser setSelectedFile

    Hi All, Am facing problem in JFileChooser's setSelectedFile. While trying to save the file I give a default file name which may contain "/" also.When I pass the File Object with the name(eg AC/B_XYZ_123) to the JFileChooser's setSelectedFile it is di

  • Listener log file

    My database version is 11g Release 11.1.0.6.0. I need my listener to write to a specific log file, I've tried different things including setting the following parameters in listener.ora and restrarting the listener: LOG_DIRECTORY_LISTENER = /mydesire