'Essbase Error: Repeated dimension [Accounts] in MDX query'

Dear Essbase Gurus,
I have an error in a query passed to my Essbase cube from an OBI front end, but the errors states quite clearly that it is an essbase error:
'Essbase Error: Repeated dimension Accounts in MDX query'
This is the query it generated:
With
set Accounts3 as 'Accounts.Generations(3).members'
set Attribute Calculations2 as '[Attribute Calculations].Generations(2).members'
set Events5 as 'Events.Generations(5).members'
set Month3 as 'Month.Generations(3).members'
set Scenario2 as 'Scenario.Generations(2).members'
set Year2 as 'Year.Generations(2).members'
set Axis1Set as 'crossjoin ({Accounts3},crossjoin ({Attribute Calculations2},crossjoin ({Events5},crossjoin ({Month3},crossjoin ({Scenario2},{Year2})))))'
select
{Measures.Total e-revenue} on columns,
NON EMPTY {Axis1Set} properties ANCESTOR_NAMES, GEN_NUMBER on rows
from Richmond.RichPOC
As an Essbase newbie I'm unfamiliar with mdx and have no idea what this means, any help would be appreciated.
Thanks
Ed
Edited by: Ed Higgins, AltiusConsulting.com on Oct 15, 2008 9:26 AM

Hi garycris,
Thanks for taking a look, I fear you may have hit the nail on the head, as I mention we are reporting on this using OBIEE, so we have imported the cube (BSO) into our OBI repository, OBI flattens the cube to make it look like a star schema it doesn't recognise the Accounts dimension correctly so we have to set it to be of type 'Other' after we have imported it, otherwise none of the figures in the Accounts dimension are actually reported (you can see the members but when included in a query no data is returned).
Another issue we found was that OBIEE appeared to substitute the name 'Measures' for Accounts when building the query, so we made 'Measures' the default alias for the Accounts dimension, to add to the issue I probably should have mentioned that the aggregation rule in OBIEE for this fact column has been set to SUM rather than External_Agg, but Oracle support have previously indicated that this is OK to do. The issue originally arose because we wanted to extend on of our dimensions with additional attributes stored in a SQL database table.
Sorry it is all a bit messy, the whole OBI with Essbase as a source is still relatively new, and it looks like there may be a few things for the mighty O to iron out, I posted this in here because the OBIEE forum has no posts with similar issues, so thanks for your help so far and anything else you can add.
Ed

Similar Messages

OBIEE Evaluate - "Essbase error : Repeated dimension in MDX query"

Hi,
I'm using OBIEE 11.1.1.6.2 BP1 on top of Essbase.
I have a project dimension in Essbase with three levels - Total Project -> Project Class -> Project. I have created a new logical column in OBIEE to query two levels from project dimension, using evaluate function as below:
Evaluate('%1.Members, %2.Members', "Oracle Hyperion Planning"."ASOCUBE".""."Planning"."Gen2,Project" , "Oracle Hyperion Planning"."ASOCUBE".""."Planning"."Gen4,Project" ).
The above column when used in analysis, works fine, returning "Total Project" and all the projects. It breaks however when any filter is applied on project dimension with the following error:
"[nQSError: 96002] Essbase Error: Repeated dimension [Project] in MDX query".
I donot have any MDX skills and would appreciate if anyone can explain this error and provide any workaround for this. Here's the MDX that fails:
With
set [_Project0] as '{[Project].Generations(2).Members, [Project].Generations(4).Members }'
select
{} on columns,
{{[_Project0]}} properties GEN_NUMBER on rows
from [ASOCUBE.Planning]
where ([Project].[1000000-Treatment Plant])
Many Thanks

This issue regarding BIEE
because MDX is wrong
With
set [_Project0] as '{[Project].Generations(2).Members, [Project].Generations(4).Members }'
select
{} on columns,
{{[_Project0]}} properties GEN_NUMBER on rows
from [ASOCUBE.Planning]
where ([Project].[1000000-Treatment Plant])

Test script logic file - Errror "Invalid Dimension Account"

Hi BPC Experts,
I am a new bee in BPC and have developed HCM applicaton in BPC 5.1. The Appset contains Finance, Rate & HCM applications.
I am working on HCM and wants to write a script logic file for HCM and it is giving an ERROR "Invalid Dimensin Account".
I have following dimensions in HCM Application:
account_hc --> type A
category_hc --> type C
company_hc --> type E
time_hc       --> time t
costcenter_hc --> type u
datasrc_hc      --> type d
employerole_hc --> type u
geography_hc --> type u
rptcurrency_hc --> type r.
I had defined Dimensions in system_cnstants file as mentioned below.
// application constants
*FUNCTION CATEGORYDIM         =CATEGORY_HC
*FUNCTION TIMEDIM =TIME_HC
*FUNCTION CURRENCYDIM =RPTCURRENCY_HC
*FUNCTION ENTITYDIM =COMPANY_HC
*FUNCTION ACCOUNTDIM =ACCOUNT_HC
*FUNCTION INTCODIM =INTCO
*FUNCTION CATEGORYDIM         =CATEGORY
*FUNCTION TIMEDIM =TIME
*FUNCTION CURRENCYDIM =RPTCURRENCY
*FUNCTION ENTITYDIM =ENTITY
*FUNCTION ACCOUNTDIM =ACCOUNT
// This part is needed when a RATE cube
// is associated to the application
// (FX = single or multi currency)
*FUNCTION THISAPP =HCM
*FUNCTION RATEAPP =RATE
*FUNCTION RATEENTITYDIM =RATESRC
*FUNCTION RATEACCOUNTDIM =RATE
*FUNCTION INPUTCURRENCYDIM =INPUTCURRENCY
*FUNCTION RATEENTITYMBR =RATEINPUT
*FUNCTION RATESRCCALCMBR =RATECALC
*FUNCTION AVGRATEID=AVG
*FUNCTION ENDRATEID=END
I tried to validate and save standard default script logic. But it gives me an error " NO match defined for lookup dimension Category"
So I could not use default logic file to write my script logic. Hence I have created HCM logic file. and Given the following script logic.
*XDIM_MEMBERSET ACCOUNT = XYZ_INC_RetPlan
*WHEN ACCOUNT
*IS XYZ_INC_RetPlan
*REC(FACTOR = 1.1, ACCOUNT)
*ENDWHEN
*COMMIT
While validat & save, I get an error "Invalid Dimension Account".
I do not understand why these errors occuring.
I have checked Category & Account dimensions checked. Every thing is ok. I have created Input schedules and they are working ok. It means the dimensions are fine.
Then why the error ?
Can you guys please guide me.
Appreciate your kind help.

Eswara,
try to close down BPC for ExCEl in case your IS/Reports are trying to access the APPlication.And also any other BPC ADmin screens accessing the same Application/Dimension.
1)try to only do a "process " on the account dimension without including the processing for Applications...
2)then try to do a process on the application.
Now your script should be able to recognize Account dimension and validate fine..
hope this helps...

OBIEE - ESSBASE ERROR - 1200467 - Error executing formula for [MDX query]

I have an issue on essbase with a query with 50 member filters.
The environment is OBIEE 11g over ESSBASE 11.1.2 with an ASO cube.
The user for essbase are with database access filters.
I have the following issue, OBIEE returns a query that filter 30 members and the query runs ok, but the same query with a 50 member filter returns the following error when i execute it on MAXL :
MAXL Error
ERROR - 1200467 - Error executing formula for [MDX query]: status code [1130203] in function [].
ERROR - 1241101 - Unexpected Essbase error 1200467.
i paste an example of the query that returns OBIEE
With
set [_Account2] as '{Distinct({[Account].[Allocated FTE - Budget]})}'
set [_Employee0] as '[Employee].members'
set [_Fund4] as 'Generate([Fund].Generations(2).members, Descendants([Fund].currentmember, [Fund].Generations(4), leaves))'
set [_Position4] as '{Distinct({[Position].[POS111165], [Position].[POS111166], [Position].[POS111167], [Position].[POS111540], [Position].[POS112331], [Position].[POS113201], [Position].[POS113247], [Position].[POS113248], [Position].[POS113540], [Position].[POS113618], [Position].[POS113954], [Position].[POS114109], [Position].[POS114194], [Position].[POS115224], [Position].[POS115912], [Position].[POS115913], [Position].[POS116727], [Position].[POS117229], [Position].[POS117491], [Position].[POS117587], [Position].[POS117610], [Position].[POS117979], [Position].[POS119456], [Position].[POS121262], [Position].[POS121458], [Position].[POS121698], [Position].[POS123368], [Position].[POS124027], [Position].[POS124028], [Position].[POS124110], [Position].[POS124396], [Position].[POS125623], [Position].[POS125624], [Position].[POS126476], [Position].[POS127960], [Position].[POS129352], [Position].[POS129468], [Position].[POS129494], [Position].[POS129535], [Position].[POS129608], [Position].[POS129679], [Position].[POS129730], [Position].[POS129905], [Position].[POS130010], [Position].[POS130144], [Position].[POS133456], [Position].[POS134943], [Position].[POS135231], [Position].[POS135404], [Position].[POS135734]})}'
set [_Program3] as 'Generate([Program].Generations(2).members, Descendants([Program].currentmember, [Program].Generations(3), leaves))'
select
{ [Budget Item]
} on columns,
NON EMPTY {crossjoin({[_Account2]},crossjoin({[_Employee0]},crossjoin({[_Fund4]},crossjoin({[_Position4]},{[_Program3]}))))} properties GEN_NUMBER, [Account].[MEMBER_UNIQUE_NAME], [Account].[Memnor], [Program].[MEMBER_UNIQUE_NAME], [Program].[Memnor], [Employee].[MEMBER_UNIQUE_NAME], [Employee].[Memnor], [Fund].[MEMBER_UNIQUE_NAME], [Fund].[Memnor], [Position].[MEMBER_UNIQUE_NAME], [Position].[Memnor] on rows
from [BCPSASO2.BCPS_ASO]
any suggestions ?
Thanks
Niko
Edited by: user8367101 on Mar 1, 2011 10:31 AM

Here it is:
It is a Windows Server 2003 R2
Processor 8393 SE
31.9 GB of RAM
32-Bit
How does "memscaling" works?
I also think that are high but it is the way it was configured before I managed the application. For my DB
Index Cache setting: 205800
Index cache current value: 205800
Data file cache setting: 33768
Data file cache current: 0
Data Cache setting: 877273
Cata cache current: 71540
Block Size: 65408

MDX Query Syntax error

I have a simple MDX query is shown in below:
SELECT [Accounts].[pv] ON ROWS,
[Reporting].Members ON COLUMNS
FROM RoggeBSO.Db
(please note that Accounts, pv and Reporting words are in square brackets)
When I execute this query on the MDX Script Editor (in EAS), I get the following syntax error:
Statement Executed with warnings.
Syntax error in input MDX Query on line 1 at token 'ON'
Unexpected Essbase error 1260052
I tried this on both ASO & BSO cubes but didn't work. Could anyone help please?
Regards
Chandra
Edited by: user2695091 on 22-Apr-2009 03:27

SELECT {[Accounts].[pv]} ON ROWS,
{[Reporting].Members} ON COLUMNS
FROM RoggeBSO.Db

How to union results from 3 different dimensions in where clause with or - Mdx query

Hi
I have a MDX Query and i need to pass the variable values to it by dynamically.
Each time it will get any one attribute from three dimensions.
Select
{} ON Columns,
{} ON Rows
From
Cube
Where
[Dimension1].[Attribut].&[Value]
or
[Dimension2].[Attribut2].&[Value]
or
[Dimension3].[Attribut3].&[Value]
So It is working for two different values by using union and cross join.
Can you please provide the solution ..
Thanks in advance

Hi Philip
Thanks for replying me.
I tried on that way, In my mdx query i am using one slice attribute (i.e [Customer].[Gender].allmembers) in rows so getting error "The Hierarchy already appears in Axis1".
SELECT
{[Measures].[Internet Sales Amount] } ON 0,
NON EMPTY
{[Customer].[Gender].allmembers } ON 1 -- Used
FROM
[Adventure Works]
WHERE
[Customer].[Gender].&[M]
,[Product].[Size Range].[(All)]
,[Customer].[Country].[All Customers]
[Customer].[Gender].[All Customers]
,[Product].[Size Range].&[XL]
,[Customer].[Country].[All Customers]
[Customer].[Gender].[All Customers]
,[Product].[Size Range].[(All)]
,[Customer].[Country].&[Australia]
Can you provide alternate ways to get resolved.
Thanks in advance

MDX query error in web intellegence

HI,
I have to create the reports in webi from olap universe which is underlying cube ssas 2008, when i run the report i got the following error.
A database error occured.The database error text is: Failed to execute MDX query.Reason:The component Microsoft
OLEDB Proivder for Analysis Services 2008 returned server error (The expression contains a function that cannot operate on a
set with more than 4,294,967,296 tuples.)
When I exclude some objects from the webi report, it run successfully. I am using BOE 3.1 SP3 .
Do have some idea, what is I am doing wrong.
Regards,
Tayyab
Edited by: Tayyab Muhammad on Nov 19, 2010 2:46 AM

Hi Tayyab,
>> if we do , then how can i build my webi report, As you
     know, one universe can be created from one cube and
     there is only one data source (universe) for webi reports.
      have any one good idea to resolve this issue
AK: 1) You can create two OLAP Universes from the underlying two Cubes. And then perform "ADD LINK" to merge the data. Then create one single Webi Report.
OR
2) Create 2 WebI reports each from different sourcing OLAP Universes. Then use "Merge Dimensions" option in Webi to merge the data into single WebI report from both the existing webi reports.
Note: For Merging Webi reports, you need a common dimension betweeen these two parent WebI reports.
AK.
Edited by: Anil Kumar2981 on Nov 22, 2010 5:32 PM
Edited by: Anil Kumar2981 on Nov 22, 2010 5:34 PM

Formatting MDX report,Error=One or more axes in MDX query have been skipped

Hi All
Need to show the measures on row-ways instead of Column-ways in MDX report. Able to generate report with measures Column-ways.
Getting error when tried the following:
#) when used "{} On Rows" instead of "{} On COlumns".
ERROR - 1200545 - One or more axes in MDX query have been skipped.
ERROR - 1241101 - Unexpected Essbase error 1200545.
If anyone faced something like this before, please share some work-around.
Thanks & Regards
sharma

Hi,
Take a look at this SAP Note: 1580524 - Xcelsius Dashboard does not display variable popup
Also go through the below discussion, it may help you.
Bex Variable PopUp does not come up launching Xcelsius dashboard
One or more mandatory variables of query XXX no... | SCN
Bex Variable PopUp does not come up launching Xcelsius dashboard
BICS - Passing Mandatory Filter Variable value to a BEx Query
Passing parameters between XCelsius dashboards using BI direct connection
Hope this helps brother.
Regards,
Suman T

Custom Calculation in ASO - Error in MDX query

Hi All,
We are trying to use a run a custom calculation on our ASO cube
We are getting the error as below
Syntax error in input MDX query on line 13 at token ' )'
When i checked my POV i did not find any issue. Even when I try to put only one crossjoin, it is still giving me the error saying "error at line 2')' "
I am unable to find the cause of this issue.
Can any one help me on this.
******content of Maxl Script********
execute calculation on database ASOFNPLN.ASOFNPLN with local script_file D:\++++++++Sateesh+++++++\ADWEA\Custom.csc"
POV
"Crossjoin({[FY09]},
Crossjoin({[Actual]},
Crossjoin ({[Jan],[Feb]},
Crossjoin({[Working]},
CrossJoin({[XA]},
CrossJoin({[0000000]},
CrossJoin({[000000000]},
CrossJoin({[00000]},
CrossJoin({[175110]},
CrossJoin({[CC_ADWEA_0000_AED]},
CrossJoin({[Unspecified Product]},
CrossJoin({[HSP_InputValue]},
CrossJoin({[Local]} )))))))))))))"
SourceRegion "{[Opening Balance],[Ending Balance],[Periodic Balance]}";
*************** Content of Custom.csc *********
case when
IsUda([Account].currentMember, "Expense") OR IsUda([Account].currentMember, "Revenue")
AND
Is([Period].CurrentMember, [Jan]) OR Is([Period].CurrentMember, [Feb]) OR Is([Period].CurrentMember, [Mar]) OR Is([Period].CurrentMember, [Apr]) OR Is([Period].CurrentMember, [May]) OR Is([Period].CurrentMember, [Jun]) OR Is([Period].CurrentMember, [Jul]) OR
Is([Period].CurrentMember, [Aug]) OR Is([Period].CurrentMember, [Sep]) OR Is([Period].CurrentMember, [Oct]) OR Is([Period].CurrentMember, [Nov]) OR Is([Period].CurrentMember, [Dec]) OR Is([Period].CurrentMember, [YearTotal])
THEN
([Ending Balance]):=([Opening Balance]+[Periodic Balance]);
([Opening Balance]):=([View].[Ending Balance], [Period].CurrentMember.lag(1));
([Ending Balance]):=([Opening Balance]+[Periodic Balance]);
END

You've got a mismatched " in the first line of the "execute calculation" statement.
However, I think the real problem is in the calc script. I don't believe you can do this in MDX:
CASE WHEN x THEN
a := y;
b := z;
END
You have to do this:
a := CASE WHEN x THEN y END;
b := CASE WHEN x THEN z END;
An alternative is to create a formula member for each of the measures you are trying to set (with the member formula containing the CASE logic) and have the calc script copy the formula member to the permanent member.

Database error: The MDX query

Hello,
I am working on BO 4.0. I have created a BEx query in BI 7.0(allow external access to this query is enabled) and executed in Analyzer it is working fine there. I now created universe by using this BEx query which has 3 dimensions and 2 measures.
Now I wanted to create a WEBI on top of that universe, when I tried to drag the dimensions it is showing the following error.
Database error: The MDX query SELECT { } ON COLUMNS , CROSSJOIN( CROSSJOIN( [ZCOUNTRY].[LEVEL01].MEMBERS, [ZCUSTGRP].[LEVEL01].MEMBERS ), [ZCITY].[LEVEL01].MEMBERS ) DIMENSION PROPERTIES MEMBER_CAPTION ON ROWS FROM [ZDEMO_001/REP_20110829064115] failed to execute with the error Error occurred when starting the parser: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'. (IES 10901) (WIS 10901)
I also tried with Live Office the result is the above error message. I am now clueless of how get out of this. Please help me.
Your response is always appreciated. Many Thanks.
Note: I dont have any filters here.
regards,
Naresh

Who are doing Scheduling operation??
Developer or Admin??
Dev: Check whether he/she has rights to Schedule (Ask your BO Admin).
I'm Back

SSRS report with tabular model – MDX query how to get the sum and count of measure and dimension respectively.

Hello everyone,
I am using the following MDX query on one of my SSRS report.
SELECT NON EMPTY { [Measures].[Days Outstanding], [Measures].[Amt] } ON COLUMNS,
NON EMPTY { ([Customer].[Customer].[Customer Key].ALLMEMBERS) }
HAVING [Measures].[ Days Outstanding] > 60
DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME ON ROWS
FROM ( SELECT ( STRTOSET(@Location, CONSTRAINED)) ON COLUMNS
FROM ( SELECT ( {[Date].[Fiscal Period].&[2014-06]}) ON COLUMNS
FROM [Model]))
Over here, the data is being filtered always for current month and for a location that is being selected by user from a report selection parameter.
I would like to get the count of total no. of customers and sum of the amount measure.
When I am using them in calculated members it gives incorrect values. It considers all records (ignores the sub-select statements) instead of only the records of current month and selected location.
I also tried with EXISTING keyword in calculated members but there is not difference in output. Finally, I manage the same at SSRS level.
Can anybody please advise what are the ways to get the required sum of [Measures].[Amt] and count of [Customer].[Customer].[Customer Key].ALLMEMBERS dimension?
Also, does it make any difference if I manage it as SSRS level and not at MDX query level?
Any help would be much appreciated.
Thanks, Ankit Shah
Inkey Solutions, India.
Microsoft Certified Business Management Solutions Professionals
http://www.inkeysolutions.com/MicrosoftDynamicsCRM.html

Can anybody please advise what are the ways to get the required sum of [Measures].[Amt] and count of [Customer].[Customer].[Customer Key].ALLMEMBERS dimension?
Also, does it make any difference if I manage it as SSRS level and not at MDX query level?
Hi Ankit,
We can use SUM function and COUNT function to sum of [Measures].[Amt] and count of [Customer].[Customer].[Customer Key].ALLMEMBERS dimension. Here is a sample query for you reference.
WITH MEMBER [measures].[SumValue] AS
SUM([Customer].[Customer].ALLMEMBERS,[Measures].[Internet Sales Amount])
MEMBER [measures].[CountValue] AS
COUNT([Customer].[Customer].ALLMEMBERS)
MEMBER [Measures].[DimensionName] AS [Customer].NAME
SELECT {[Measures].[DimensionName],[measures].[SumValue],[measures].[CountValue]} ON 0
FROM [Adventure Works]
Besides, you ask that does it make any difference if I manage it as SSRS level and not at MDX query level. I don't thinks it will make much difference. The total time to generate a reporting server report (RDL) can be divided into 3 elements:Time to retrieve
the data (TimeDataRetrieval);Time to process the report (TimeProcessing);Time to render the report (TimeRendering). If you manage it on MDX query level, then the TimeDataRetrieval might a little longer. If you manage it on report level, then the TimeProcessing
or TimeRendering time might a little longer. You can test it on you report with following query:
SELECT Itempath, TimeStart,TimeDataRetrieval + TimeProcessing + TimeRendering as [total time],
TimeDataRetrieval, TimeProcessing, TimeRendering, ByteCount, [RowCount],Source
FROM ExecutionLog3
WHERE itempath like '%reportname'
Regards,
Charlie Liao
TechNet Community Support

Getting the MDX query select error when running a webi report on BI query

Getting the following error when running a webi report on BI query :
A database error occured. The database error text is: The MDX query SELECT { [Measures].[D8JBFK099LLUVNLO7JY49FJKU] } ON COLUMNS , NON EMPTY [ZCOMPCODE].[LEVEL01].MEMBERS ON ROWS FROM [ZTEST_CUB/REP_20100723200521] failed to execute with the error Unknown error. (WIS 10901).
I have gone through many threads related to this error. But not able find the steps to follow for resoultion.
Please help in this regard.
Thanks,
Jeethender

The Fix Pack is also for Client Tools--it is a separate download. Please see the text below for ADAPT01255422
ADAPT01255422
Description:
Web Intelligence generates an incorrect MDX statement when a characteristic and a prompt are used.
The following database error happens: "The MDX query ... failed to execute with the error
Unknown error (WIS 10901)."
New Behavior:
This problem is resolved.
This information is also available in the Fixed Issues document for any Fix Pack greater than 2.2.

Error In MDX query

Statement: SELECT{ CROSSJOIN({ [Product].[Product] }, { [Measures].[Shipping Units] })} ON ROWS FROM [Shipment]
com.interlacesystems.iquery.QueryException: COLUMNS axis specification missing
     Statement: SELECT{ CROSSJOIN({ [Product].[Product] }, { [Measures].[Shipping Units] })} ON ROWS FROM [Shipment]
     at com.interlacesystems.iquery.imdx.QueryCommand.resolve(Unknown Source)
     at com.interlacesystems.iquery.imdx.QueryCommand.resolve(Unknown Source)
     at com.interlacesystems.iquery.imdx.IMDXQueryFactory.parseStatement(Unknown Source)
     at com.interlacesystems.iquery.QueryFactory.createStatement(Unknown Source)
     at com.interlacesystems.iquery.DefaultQueryExecutionHandler.<init>(Unknown Source)
     at com.interlacesystems.isclient.admin.query.QueryAction.makePreviewURL(Unknown Source)
     at com.interlacesystems.isclient.admin.query.QueryAction.exportQuery(Unknown Source)
     at com.interlacesystems.isclient.admin.query.QueryAction.preview(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:269)
     at org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:170)
     at com.interlacesystems.isclient.common.ISAction.process(Unknown Source)
     at com.interlacesystems.isclient.common.ISAction.execute(Unknown Source)
     at org.apache.struts.chain.commands.servlet.ExecuteAction.execute(ExecuteAction.java:58)
     at org.apache.struts.chain.commands.AbstractExecuteAction.execute(AbstractExecuteAction.java:67)
     at org.apache.struts.chain.commands.ActionCommandBase.execute(ActionCommandBase.java:51)
     at org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:190)
     at org.apache.commons.chain.generic.LookupCommand.execute(LookupCommand.java:304)
     at org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:190)
     at org.apache.struts.chain.ComposableRequestProcessor.process(ComposableRequestProcessor.java:283)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:462)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at com.interlacesystems.isclient.auth.SessionInitFilter.doFilter(Unknown Source)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at com.interlacesystems.isclient.auth.AuthorizationFilter.doFilter(Unknown Source)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at com.interlacesystems.isclient.auth.AuthenticationFilter.doFilter(Unknown Source)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at com.hyperion.css.wls.CssJpsFilter.doFilter(CssJpsFilter.java:32)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at com.interlacesystems.isclient.auth.RootFilter.doFilter(Unknown Source)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
I am getting following error in While Executing a folllowing MDX Query.....

general mdx format is
SELECT
{ } ON COLUMNS,
{} ON ROWS
FROM [Cube]
I think you are missing { } COLUMNS, in query.
Thanks,
Sumant

Export in Query Ready Mode get Essbase Error 1020047

Through Workspace when in a Financial Reporting Report, when we click on Export in Query Ready Mode, we get the following error in Excel and then Excel closes. 'Essbase Error (1020047): A column item [%] conflicts with a row item[%].'
Any ideas?
We are using 11.1.2
Thanks.

This is bug and fixed in 11.1.2.1.102 Smart View

Parser dimension ACCOUNT's xml file error.

Hi friends,
i manully uploading master data in ACCOUNT dimension.
what i did here, i manually added PARENTH1hierarchy and i changed that column position infront of "ACCTYPE" property. While pasting i might paste on ACCTYPE property & processed ACCOUNT dim.So it gone and disturbed underlying XML file. I checked 3 files XLS,XLT and XML files in UJFS. But XLS & XLT doesn't have ACCTYPE property. So how can i put it back? Any suggestions pls.
Eventhough ACCTYPE dim property defined and existed(under maintain dim property of ACCOUNT dim). when i try to check maintain members data for manually entering data, it not available in columns. when i try to process ACCOUT dim, system saying below error message.
Parser dimension ACCOUNT's xml file error.
How to correct this error.?
Thanks,
Naresh
Edited by: Naresh P on Jan 13, 2011 7:20 AM

Hi,
It will be better to delete the XML file from UJFS and process your dimension once again. However, it might happen that you are still unable to edit the membersheet. In that case, it will be advisable to take a backup of the member sheet and recreate the same member sheet once again.
Hope this helps.

'Essbase Error: Repeated dimension [Accounts] in MDX query'

Similar Messages

Maybe you are looking for