Errors in the OLAP Storage Engine for a large dimension

March 3, 2014

no comments

A colleague of mine was working on a cube. The cube had a fact table that was also a dimension. It had 18 million rows of data. When my colleague tried to process the cube with that fact and dimension, he couldn’t. Both the full and the incremental process didn’t work. He got an error on processing the large dimension with a message of:

 

Exception calling “Process” with “1” argument(s): “File system error: A FileStore error from WriteFile occurred. Physical file: . Logical file: . .

Errors in the OLAP storage engine: An error occurred while the ‘RN’ attribute of the ‘YYYYY’ dimension from the ‘XXXXX’ database was being processed.

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.

Internal error: The operation terminated unsuccessfully.

Errors in the back-end database access module. The read operation was cancelled due to an earlier error.

Errors in the OLAP storage engine: An error occurred while the ‘RN’ attribute of the ‘YYYYY’ dimension from the ‘XXXXX’ database was being processed.

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.

Server: The operation has been cancelled

 

The RN attribute was a running number that was the identifier for the fact – dimension. My colleague asked me if I had a thought what to do. My first offer was to set the AttributeHierarchyEnabled property to false, though I told him I wasn’t sure if you could do that for an attribute that is the key for the dimension:

Errors in the OLAP Storage Engine

 

Apparently you can’t. he tried to change that property and got a red squiggly line under the attribute and a notification stating that:

 

Attribute hierarchy must be enabled if attribute relationships are used. The key attribute requires attribute hierarchy enabled.

 

Errors in the OLAP Storage Engine

 

So I offered him to define in the DSV that the Logical Primary Key for the fact – dimension will be a combination of attributes that will identify each row:

Errors in the OLAP Storage Engine

 

 

He did that and apparently the key for the dimension hadn’t changed and stayed the RN attribute. The fact – dimension was still connected to itself through the RN attribute.

 

He tried the process again and this time it worked. Still, I would add that in a later look into the DSV I also saw that the table in question was a named query with calculations in it for RN. I would also suggest turning it into a pre – defined table.

So, in short, if you’re having a problem processing a large dimension, consider changing the combination of attributes defining its keys. For additional data, please refer to the Analysis Services Performance Guide chapter 4 Tuning Processing Performance.

Add comment
facebook linkedin twitter email

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

*