sonalb

Hello, Just a quick note. I got the same error, but the versions of iReport and jasperreports on JasperServer were perfectly compatible. I found that the issue was that the file was stored in ANSI encoding ... but Jasper expected it in UTF-8. I just converted my file to UTF-8 and uploaded again. Worked fine. Just noting this down here, in case somebody else finds this thread and it helps. Thanks, Sonal.

Hi, While trying to create an Analysis View against my schema, I got an error message pointing to a logical error in my schema. I then edited my schema file, and reloaded it against the older "OLAP Schema" object. However, when I tried to re-create the Analysis View, I got the same error. The error went away if I delete the old connection and old schema, and then create a new schema & connection object. From this, it appears that there's some sort of caching of OLAP objects happening in the server, which is ignoring updates. Is this a configuration issue ? Appreciate any pointers. I'm using JS Pro 3.5 (Trial). Thanks & Regards, Sonal.

@Manfred: Do you have an AggLevel tag for "Gender" dimension in the aggregate definition in the schema ? See "Payment Method" degenerate dimension example here http://mondrian.pentaho.org/documentation/aggregate_tables.php#Another_aggregate_table I'm also having a problem with the degenerate dimensions in aggregate tables. Things were fine with the default rules, but as soon as I added an explicit aggregate definition, Mondrian is going directly to the fact table and is ignoring the aggregate table. I checked the logs, and am getting the following WARN message even though the degenerate dimension is mentioned in the aggregate definition: WARN AggTableManager,http-8080-Processor17:43 - Recognizer.checkUnusedColumns: Candidate aggregate table 'agg_lc_orders_fact' for fact table 'orders_fact' has a column 'orderType' with unknown usage. The corresponding definition in the schema file is: <AggName name="agg_lc_orders_fact"> <AggMeasure ... /> <AggLevel name="[Order Type].[actionType]" column="orderType" /> </AggName> One workaround could be to convert the degenerate dimensions to simple dimensions with their own dimension tables. However, I have almost 10-12 such degenerates. Creating and maintaining dimension tables for them would not be an ideal solution. @Manfred: Do post a solution if you found one. Would appreciate any suggestions / pointers from the other experts here. Please find attached my schema. Thanks & Regards, Sonal.

Hi, @Sherman: Thanks for your response. I have attached the SQL when the "NON EMPTY" clause is not used. I am indeed using the automated aggregate discovery process of Mondrian. I have also attached the aggregate table definition, as well as the indexes in the aggregate table. Would appreciate your thoughts. Would an explicit aggregate definition in the schema help ? Thanks & Regards, Sonal.

Hello All, I've created an aggregate table with a collapsed time dimension, and several lost dimensions. I have retained several degenerate dimensions as-is from the fact table. Now, I've created an Analysis View with these degenerate dimensions. I have selected the "Suppress Empty Rows / Columns". It works fine as long as I'm at the "All" Members level ... but the minute I drilldown the system locks-up. I checked the database and found that the underlying database query is trying to run a lookup of the aggregate table vs. the fact table ! I have checked and found the following things: 1.) It works fine if I remove the "NON EMPTY" clause from the MDX or by removing the "Suppress Empty Rows / Columns" option. 2.) I made the degenerate dimension as "NOT NULL" in the database ... still locks up (I did flush the OLAP cache too). 3.) This problem only comes with degenerate dimensions. 4.) I have indexes on all the degenerate dimensions in the aggregate table ... doesn't seem to help. Is there something wrong with my setup ... or could it be a Mondrian issue ? I'm using the MySQL database. I have attached the schema, the MDX, and the bad database SQL. Would appreciate any pointers from the experts. Thanks, Sonal.

Thanks Manfred. Some of the values are being reported incorrectly. Am checking against the data in the system ... will post an update here after that. Thanks again.

Hello, I’m trying to create a second measure in my schema which is a “SUM DISTINCT” of a particular column. Allow me to explain: Fact Table: orgID txnDate vendorName txnAmount vendorMax A1 2008-08-30 Vendor_1 100,000 500 A2 2008-09-15 Vendor_1 24,000 500 A3 2009-01-30 Vendor_2 26,000 200 A2 2009-01-10 Vendor_1 57,000 500 I have defined three dimensions: 1.) Organisation [based on orgID] 2.) Time [based on txnDate] 3.) Vendors [Degenerate dimension on vendorName] I already have one measure to sum the txnAmount. I need another measure that can give me the rolled-up sum of vendorMax for distinct vendorID / vendorName. For example, in the table above, For [All Organizations] & [All Years], the measure should return 700. For [All Organizations] & Year=2008, the measure should return 500. For [All Organizations] & Year=2009, the measure should return 700. I’ve not had any success using MeasureExpression, or CalculatedMember. I’m not too sure if I can use a Join in this case, since I want a measure and not a dimension. Would appreciate any help/pointers you may have. Thanks in advance. Sonal.

Hi, Is it possible to customize the displayed columns / data in the Drillthrough from the Analysis Views ? I've got a fact table with the following structure: id, fact_col_1, fact_col_2... And I also have a detail table: id, detail_col_1... I'd like the drillthrough to show me id, details_col_1 from the detail table instead of showing the default records from the fact table. How can I do this ? Appreciate your help. Thanks in advance. Sonal.