September 3, 2008 at 11:31 am
Hi
I am trying to process a cube which has been migrated from Sql server 2000 to Sql Server 2005.
All dimensions has been processed successfully but when I am trying to process cube, I am getting error
"Errors in the OLAP storage engine: The attribute key cannot be found: Table: FactTable, Column: DimKey, Value: 4. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Attibute1 of Dimension: Dim1 from Database: CubeFinance, Cube: Finance, Measure Group: MG1, Partition: Finance_2000, Record: 256."
I have checked dimesion table where I can find a record for Column DimKey having value 4. Also, there are multiple values in FactTable where DimKey = 4.
After going through some of the similar forum issue's, I did set up "Custom Error Configurations" to "Ignore Error" and I was able to process the cube successfully but there is no data in the cube.
Let me know how to resolve this.
Thanks
/**A strong positive mental attitude will create more miracles than any wonder drug**/
September 8, 2008 at 11:26 am
I am getting the same error........can someone plz guide us...............
My dimensions are processed succussfully, but i m getting this error while processing the cube.
One thing that i figured out is the error column has alot of null values in it. But i dont know whether that makes any difference or not, or how to solve that...
any help will be highly appreciated.
Thanks,
Usman
September 25, 2008 at 8:42 am
Sorry for the late response. Hopefully you have't been too held up.
In general, you need to carefully check your referential integrity in your data model. Run SQL scripts to generate any missing records (i.e. Key = value, Description = value). If you grab / pull up the SQL statement used to populate your dimension, you'll notice that it uses inner joins to pull the data. Data missing for an unrelated joined attribute, can cause the records to be missed/skipped entirely.
In general, I'd recommend using the following definition strategy:
a) for any attribute key, always point it to the local value on the dimension table (i.e. the foriegn key).
b) for the attribute description, if you're using off board tables you'll obviously point it to the description on the off board table.
c) for the attribute key, set the NBullProcessing option to UnknownMember.
Again, to check where the gap is, pull up the SQL statement for the "Key Attribute", run it in Management Studio, and carefully check that everything is there. Create RI check procedures, even when you're 100% sure that the data will be ok. (I've been 100% sure, and been caught!)
Good Luck.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply