Wednesday, July 05, 2006 10:19 AM
I am getting the error:
Warning 2 Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: B@ - key@ of Dimension: Brcledger from Database: Misys, Cube: Misys 1, Measure Group: Brcledger, Partition: Brcledger, Record: 24163. 0 0
I have read that this is caused by a referential integrity problem however, the fact table is the dimension table, and the joint primary key is definitely unique. There doesn't seem to be anything special about record number 24163 So why can i not process my cube?
Wednesday, July 05, 2006 10:26 AM
Just incase it is any help.. the other error message which comes up I have pasted here:
Warning 1 Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_brcledger, Column: B_x0040_, Value: 0; Table: dbo_brcledger, Column: key_x0040_, Value: 474142463032485130310000000C. 0 0
WHERE (key@ = '474142463032485130310000000C')
Returns 1 result
Wednesday, July 05, 2006 3:15 PMOwner
You have a situation when Analysis Server cannot find a key in the dimension while processing partition.
I would guess you might have problems with dimension process that lead to partition processing errors.
Try re-process your Brcledger dimension change processing options to report and stop on every error.
After you fix dimension problems you should be able to process your partitions without a problem.
This posting is provided "AS IS" with no warranties, and confers no rights.
Tuesday, July 18, 2006 2:59 PM
I have the same problem but it only occurs when i define my dimension as a time dimension. ]
Also my fact table is a view which gets it's surrgate keys by joining to the dimension tables in its definiton. This might be connected but the cube processes fine with the same data source, fact table, dimensions etc as long as i dont define the dimension as a time dimension.
Also the value of the attribute keys it cant find is always zero '0'. There are the same number of errors in the processing as there are nulls in the key column of the fact table. So i assume the nulls are being converted to 0 and then the referential integrity goes.....