Having issue processing a cube with error message such as this. Always seem
to get past this but everytime I build a cube I have to try to figure this
out and can’t pinpoint the cause.

Errors in the OLAP storage engine: The attribute key cannot be found: Table:
xxxx, Column: xxx, Value: 2704. Errors in the OLAP storage engine: The record
was skipped because the attribute key was not found. Attribute: xxxx of
Dimension: xxxx from Database: xxxx, Cube: xxx, Measure Group: xxxx,
Partition:xxx, 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 'xx'
partition of the 'xx' measure group for the 'TECH' cube from the xxx database.

Do you have referential integrity on your schema?

It sounds a bit like one of the records in the fact table has a value in
a column that does not have a matching key in it's respective dimension
table.

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <F33E6E34-F66B-4A37-BB3B-FC787F004622 (AT) microsoft (DOT) com>,
CJ (AT) discussions (DOT) microsoft.com says...

Hi,

This can be said as a referential integrity issue, like having value in fact
and not in dimesion... This occus basically bacause of changing dimesion.

I have faced this type of issue couple of times. Thats just think of a
scenario you have one dimsion value XX in DIM_X table. When you reload data
XX might have deleted or updated from the source OLTP table(rare situation).
In such a scenario when you process cube, initally the dimesion value was
there and now it has changed, so cube processing can throw an error.

Please cross check and Lemme know if its the reason...

Thanks,
Sree

"Darren Gosbell" wrote:

Thanks guys, I appreciate all the help.

"Sreejith G" wrote: