Cubes Generation error. different between MOLAP, ROLAP

I am using one cubes for my sales analysis.
When I try to redesign storage and Process the cube from MOLAP to ROLAP, it
create error with something related to fail to create index.
I didn't change the cube design.
What information I need to be careful ?
Hi Kam.
This error is usally related to Real-Time OLAP. Are you trying to re-design
the storage mode of your cube as a Real-Time? This feature requires special
settings in the relational database.
You may find more information here
http://msdn.microsoft.com/library/de...eties_0o4z.asp
Hope that helps.
"Kam" wrote:

> I am using one cubes for my sales analysis.
> When I try to redesign storage and Process the cube from MOLAP to ROLAP, it
> create error with something related to fail to create index.
> I didn't change the cube design.
> What information I need to be careful ?

Cubes Generation error. different between MOLAP, ROLAP

I am using one cubes for my sales analysis.
When I try to redesign storage and Process the cube from MOLAP to ROLAP, it
create error with something related to fail to create index.
I didn't change the cube design.
What information I need to be careful ?Hi Kam.
This error is usally related to Real-Time OLAP. Are you trying to re-design
the storage mode of your cube as a Real-Time? This feature requires special
settings in the relational database.
You may find more information here
http://msdn.microsoft.com/library/d...ieties_0o4z.asp
Hope that helps.
"Kam" wrote:

> I am using one cubes for my sales analysis.
> When I try to redesign storage and Process the cube from MOLAP to ROLAP, i
t
> create error with something related to fail to create index.
> I didn't change the cube design.
> What information I need to be careful ?

Cube Processing Error - Urgent - Thanks

First when I processed cube's (Process Data) using SSIS package I got "Memory error"

"Memory error: Allocation failure : Not enough storage is available to process this command."

I changed "OLAP\ Process \ BufferMemoryLimit" to 30% . I have /3GB setup. and I am using AS 2005 - 32 bit.

When I rerun the package I got olap storage engine error

Errors in the OLAP storage engine: An error occurred while processing the 'Scenario Analysis 2006' partition of the 'Scenario Analysis' measure group for the 'Scenario Analysis' cube from the Risk Reports database.

I don't know what's that, so I run cube process (Full) from Management Studio and got error below while reading data process stoped with following popup message

The trace has been stopped
Unexpected end of the file has occurred. The following elements are not closed: root, return, ExecuteResponse, soap:Body soap: Envelope. Line 13180, position 1. (System.Xml)

Thanks for any help - Ashok

Please check if you're running out of disk space...

Cube Processing Error - Urgent - Thanks

First when I processed cube's (Process Data) using SSIS package I got "Memory error"

"Memory error: Allocation failure : Not enough storage is available to process this command."

I changed "OLAP\ Process \ BufferMemoryLimit" to 30% . I have /3GB setup. and I am using AS 2005 - 32 bit.

When I rerun the package I got olap storage engine error

Errors in the OLAP storage engine: An error occurred while processing the 'Scenario Analysis 2006' partition of the 'Scenario Analysis' measure group for the 'Scenario Analysis' cube from the Risk Reports database.

I don't know what's that, so I run cube process (Full) from Management Studio and got error below while reading data process stoped with following popup message

The trace has been stopped
Unexpected end of the file has occurred. The following elements are not closed: root, return, ExecuteResponse, soap:Body soap: Envelope. Line 13180, position 1. (System.Xml)

Thanks for any help - Ashok

Please check if you're running out of disk space...

Cube Deploy Error

Hello, I'm trying to deploy a cube on Analysis Services and I'm getting the next error:

Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: DSAP PRODUCTO of Dimension: DSAP PRODUCTO from Database: SAPIN_BI, Cube: Sapin BI Dllo, Measure Group: DSAP COMBOS, Partition: DSAP COMBOS, Record: 1.

I'm sure the data is consistent and has integrity.... and I verified It ...

Could you please give me a clue ?

What do I have to post or which script do I have to send you ?

Thanks a lot !

jortiz wrote:

Hello, I'm trying to deploy a cube on Analysis Services and I'm getting the next error:

Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: DSAP PRODUCTO of Dimension: DSAP PRODUCTO from Database: SAPIN_BI, Cube: Sapin BI Dllo, Measure Group: DSAP COMBOS, Partition: DSAP COMBOS, Record: 1.

I'm sure the data is consistent and has integrity.... and I verified It ...

Could you please give me a clue ?

What do I have to post or which script do I have to send you ?

Thanks a lot !

Hello, Is there any service like a kind of remote desktop via Web, to show you the problem ?

|||

Assuming your cube is built on top of a SQL Server relational database, your best bet might be to use Profiler to capture the SQL queries being generated by SSAS as it processes your cube. Then look at the queries and try to determine what query is returning unexpected data. More than likely the problem lies in the design of the dimension usage within the cube. Perhaps one of the dimensions is related to one of the measure groups based on the wrong attribute or fact table column?

HTH,

Dave Fackler

|||

Dave Fackler wrote:

Assuming your cube is built on top of a SQL Server relational database, your best bet might be to use Profiler to capture the SQL queries being generated by SSAS as it processes your cube. Then look at the queries and try to determine what query is returning unexpected data. More than likely the problem lies in the design of the dimension usage within the cube. Perhaps one of the dimensions is related to one of the measure groups based on the wrong attribute or fact table column?

HTH,

Dave Fackler

Hi Dave, It doesn't matter which dimensions and fact table I use, I get a similar error like this:

Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_HSAP_REDENCIONES, Column: NMPRODUCTO_KEY, Value: 1. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: DSAP PRODUCTO of Dimension: DSAP PRODUCTO from Database: SAPIN_BI, Cube: Sapin BI Dllo, Measure Group: HSAP REDENCIONES, Partition: HSAP REDENCIONES, Record: 1. 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 processing the 'HSAP REDENCIONES' partition of the 'HSAP REDENCIONES' measure group for the 'Sapin BI Dllo' cube from the SAPIN_BI database.

|||

Based on the errror message, it would appear that your fact table has a column named NMPRODUCTO_KEY and a record was read from the fact table that has a value of 1 in that column. In addition, the measure group HSAP REDENCIONES would appear to be related to the DSAP PRODUCTO dimension using the NMPRODUCTO_KEY column to match the DSAP PRODUCTO attribute (which appears to be serving as the key attribute in the dimension). The question is: do any of the members in the DSAP PRODUCTO dimension have a key value of 1 for the DSAP PRODUCTO attribute? What column in the underlying dimension table is the DSAP PRODUCTO attribute based on?

Dave F.

|||

Sorry if I interfere. Have you added a new column to your fact table lately that was not in the processed cube initially?

If you use query binding for the partition(s) this new column will not appear automatically. You will have to add it yourself.

This looks like a problem that I had a few days ago.

Regards

Thomas Ivarsson

|||

Thomas Ivarsson wrote:

Sorry if I interfere. Have you added a new column to your fact table lately that was not in the processed cube initially?

If you use query binding for the partition(s) this new column will not appear automatically. You will have to add it yourself.

This looks like a problem that I had a few days ago.

Regards

Thomas Ivarsson

Thank you so much for your answers !!

|||

What solution did work?

Regards

Thomas Ivarsson

Cube data storage location

Hi -

What level of storage locations we can define in SSAS database e.g. Can we define a separate location for these SSAS ojects.

Instance

Database,

dimensions

Measure Gruop

Measure

Partitons

We do want to store cube database in root data folder.Can some one gide me on this, how to do this. Appreciate your help.

You can set a per instance data folder (indeed each instance will have it's own install folder and the data folder is under that by default). But below that, although you can set the storeage location for cubes and measure groups, these settings pretty much just serve as the default for any new partitions that are created. It is really only at the partition level that you have granular control over where the data is stored. Even then this is really only worth changing if you want to spread your data across mulitple disks. If you are not doing this I would recommend that you just stay with the default folder structure.

I believe that the metadata for databases cubes and measure groups (which are quite small) are all stored in the data folder for the instance along with the dimension data and metadata.

On my laptop I have configured the default folder for my instance to a folder outside of "program files", but I have left everything else at the default settings.