SolvedPrivate

OLAP CUBE Problem

Posted on 2013-06-05
2
35 Views
Last Modified: 2016-02-18
Hello, I get the following error

Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'MYTABLE', Column: 'ID', Value: '57101553'. The attribute is 'ID'. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: ID of Dimension: MYTABLE from Database: OlapRepPortal, Cube: MYCUBE, Measure Group: MYTABLE, Partition: MYTABLE, Record: 216231. 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 'MYTABLE' partition of the 'MYTABLE' measure group for the 'MYCUBE' cube from the OlapRepPortal database.

Open in new window

0
Comment
Question by:snnege
2 Comments
 

Author Comment

by:snnege
ID: 39223040
Last error


Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'MY_TABLE', Column: 'SERVER_ID', Value: '538'; Table: 'MY_TABLE', Column: 'REZ_NO', Value: '62367'. The attribute is 'SERVER ID'. Errors in the OLAP storage engine: The attribute key was converted to an unknown member because the attribute key was not found. Attribute SERVER ID of Dimension: MY TABLE from Database: OlapRepPortal, Cube: MY_CUBE, Measure Group: MY TABLE, Partition: MY TABLE, Record: 380531. 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 'MY TABLE' partition of the 'MY TABLE' measure group for the 'MY_CUBE' cube from the OlapRepPortal database.

Open in new window

0
 
LVL 37

Accepted Solution

by:
ValentinoV earned 500 total points
ID: 39224644
That error means you've got values in your fact table (measure group) for foreign keys to dimensions which don't actually exist in the dimension, in other words incorrect foreign keys.

The error message clearly states what tables, columns and even values you need to look into.

There can be many causes for this to happen. Have a read through the following articles, they should contain useful info to help you out:
SSAS Quick Reference: Attribute Key Cannot Be Found
Idiot’s Guide to SSAS Attribute Relationships
0

Featured Post

3 Use Cases for Connected Systems

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Naughty Me. While I was changing the database name from DB1 to DB_PROD1 (yep it's not real database name ^v^), I changed the database name and notified my application fellows that I did it. They turn on the application, and everything is working. A …
SQL Server engine let you use a Windows account or a SQL Server account to connect to a SQL Server instance. This can be configured immediatly during the SQL Server installation or after in the Server Authentication section in the Server properties …
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Along with being a a promotional video for my three-day Annielytics Dashboard Seminor, this Micro Tutorial is an intro to Google Analytics API data.

776 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question