I'm running mondrian as a standalone on mysql. I'm getting the exception mondrian.olap.MondrianException: Mondrian Error:Cannot find MDX member '[Measures]'. Make sure it is indeed a member and not a level or a hierarchy. when i run any MDX query
the catalog xml which is creating issue is
<HierarchyGrant hierarchy="[Measures]" rollupPolicy="partial" access="custom">
<MemberGrant member="[Measures]" access="none"/>
<MemberGrant member="[Measures].[X]" access="all"/>
</HierarchyGrant>
Here the hierarchy name and member name are same. This is cause for the issue.
But the same XML works fine on Saiku over mondrian + mysql.
I used mondrian 3.3 in both the cases.
help me resolve this issue.
Perhaps, edit file mondrian.properties:
mondrian.rolap.ignoreInvalidMembers=true
mondrian.rolap.ignoreInvalidMembersDuringQuery=true
Related
I am using ignite native and using atomicity as TRANSACTIONAL_SNAPSHOT when I am trying the load the old storage which was configured with amoticity TRNASACTIONAL it is giving the Unknown page type issue after deleting the .dat file but if I am using new storage it is working fine. Can anybody help me?
org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalStateException: Unknown page type: 10009 pageId: 0002ffff00000006"; SQL statement:
CREATE TABLE "DFM"."ANSWER_TYPE_ENUM" (_KEY VARCHAR INVISIBLE NOT NULL,_VAL OTHER INVISIBLE,"ID" VARCHAR,"ENUM_VALUE" VARCHAR) engine "org.apache.ignite.internal.processors.query.h2.H2TableEngine" [50000-197]
I've never seen errors like these, but I would say that TRANSACTIONAL_SNAPSHOT is experimental and should be avoided for now.
We just switched from oracle jdk 10 to openJDK 13.
When we now try to start our tomee with
set JAVA_OPTS=-Dconfigfilepath="path/to/config.xml"
we get the following exception:
javax.enterprise.inject.UnsatisfiedResolutionException: Api type [java.lang.String] is not found with the qualifiers
Qualifiers: [#org.eclipse.microprofile.config.inject.ConfigProperty(name="configfilepath", defaultValue="org.eclipse.microprofile.config.configproperty.unconfigureddvalue")]
for injection into Field Injection Point, field name : configPath, Bean Owner : [Configuration, WebBeansType:MANAGED, Name:null, API Types:[de.test.Configuration,java.lang.Object], Qualifiers:[javax.enterprise.inject.Default,javax.enterprise.inject.Any]]
It works if we use the ConfigProvider directly. I hope someone can help with this problem.
if there anyone who already get this type of error:
OlapException: XMLA provider gave exception: <SOAP-ENV:Fault> <faultcode> SOAP-ENV:Client.00HSBD01 </faultcode> <faultstring> XMLA MDX parse failed </faultstring> <faultactor> Mondrian </faultactor> <detail> <XA:error xmlns:XA="http://mondrian.sourceforge.net"> <code> 00HSBD01 </code> <desc> The Mondrian XML: Mondrian Error:No function matches signature 'Exists(<Member>, <Set>)' </desc> </XA:error> </detail> </SOAP-ENV:Fault>`.
My architecture: I used tomcat-server and I deploy saiku as OLAP client and mondrian as olap server on the server because I need to access to the result in XMLA format.
Actually, this work but it depends on the query. When I do some Filter this error appears.
For example:
I want to analyse the number of production during all year and all month for each year it works but if I want to analyse only one year with all month of that year then It's not work.
If anyone have an idea, I would be nice.
According to https://learn.microsoft.com/en-us/sql/mdx/exists-mdx?view=sql-server-2017, arguments are: Set, Set.
Try encapsulating your first argument in curly braces.
I have a crystal report which is having a data source from sql server .I am always getting this error when we want to show the report.I have seen the connection too.No Problem with that connection.
error :
Unknown Query Engine Error
Failed to open a rowset.
Error in File C:\Users\ADMINI~1\AppData\Local\Temp\student{ED5C2412-C7A1-4E1D-8093-1EFDA02340ABD}.rpt:
Unknown Query Engine Error
Can any one help me ?
In extension to this Question I found a problem was caused by one column of the table in the report when i remove that fields it is working fine.When the report is migrated from access to sql server source it is converted using cross join.Does this raised from table linking only ?
I'm sure if this is relevant but try the solution given in this link . The solution suggests you add this line to your config file :
<startup useLegacyV2RuntimeActivationPolicy="true"><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/></startup>
Our product leverages Analysis Services combined with Reporting Services, we recently made some changed to add compatability for SQL2008. Everything works great except with certain dimensions, drillthroughs or measures added to a report we suddenly get this following error:
Server: The operation has been
cancelled. Errors in the high-level
relational engine. A connection could
not be made to the data source with
the DataSourceID of 'Adventure Works
DW', Name of 'Adventure Works DW'. OLE
DB error: OLE DB or ODBC error: Class
not registered.
Any ideas?
Found the issue.
SQL2008 doesn't come with the SQL Native Client provider which my cube was using to retreive data from the datawarehouse.
Solution:
Change the provider to SQL OLE DB Provider instead.
You can use XMLA if you so wish:
<Object>
<DatabaseID>Adventure Works DW</DatabaseID>
<DataSourceID>Adventure Works DW</DataSourceID>
</Object>
<ObjectDefinition>
<DataSource xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="RelationalDataSource">
<ID>Adventure Works DW</ID>
<Name>Adventure Works DW</Name>
<ConnectionString>Provider=SQLOLEDB.1;Data Source=s;Persist Security Info=False;Integrated Security=SSPI;Initial Catalog=AdventureWorksDWDW</ConnectionString>
<ImpersonationInfo>
<ImpersonationMode>ImpersonateServiceAccount</ImpersonationMode>
</ImpersonationInfo>
<Timeout>PT0S</Timeout>
</DataSource>
</ObjectDefinition>
</Alter>