December 12, 2012 at 5:10 am
Hi, our dba is on holiday and I've been asked to look at a job that is failing. The job runs a ssas package, which I have opened up in bis 2005.
When trying to process the cube I get this error:
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_SURVEY_RESULT, Column: TUTOR_ID, Value: . Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: TUTORS of Dimension: TUTORS from Database: IPRSheetAnalysisServices, Cube: IPR Sheets, Measure Group: SURVEY RESULT, Partition: SURVEY RESULT, Record: 1.
If I run the dimension individually then they all process fine. i read that processing the measures individually can resolve this issue - but how do you do that.
The error msg looks like it isnt happy with a null value, but the source database has always had null values and has run fine for months.
Any ideas? I'm a noob with analysis services
December 12, 2012 at 6:31 am
Sounds to me like you are processing a cube and have fact records that have no corresponding dimension data (for example you have a sales record for a client that does exist). The error message should give you more than that and will tell you which fact is in error
You may may want to investigate why this is happening....
If you are desperate and just need the cube updating with what you have you could process the cube so that it skips these records by right clicking on database and click process
When the screen pops up the click on Change Settings and then click on the Dimension Key Errors. Click Use Custom error config and then set Ighnore error count on and then set all the errors to Ignore error
Mack
December 12, 2012 at 7:04 am
Thanks for your response,
yes one of my dimensions has a null value which I dont think is in the 'fact' table...how do I navigate to the fact table to check this
I suspect this because the source database which contains the same tables does not have this null value in the table.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply