June 26, 2009 at 5:58 am
Using SQL Server 2005.
I created a SSIS package to process a cube, deployed the package, and scheduled it to run daily. Approximately 1 in 5 times the process fails with the error given below. This error occurs on different dimensions at different times.
I inspect the fact table and do not discover a missing attribute key. All attribute keys are accounted for. I then successfully manually process the cube in Management Studio. Finally, I successfully manually execute the job step to process the cube.
I'm perplexed as to why the initial daily cube process fails because I don't find a missing attribute key.
Any ideas?
Errors in the OLAP storage engine: The attribute key cannot be found: Table: mun_BookingsSales, Column: Rep, Value: 82.
Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Sales Reps of Dimension: Sales Reps from Database: MuncyTopCust, Cube: MuncyTopCust, Measure Group: Bookings Sales, Partition: Bookings Sales, Record: 4.
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 'Bookings Sales' partition of the 'Bookings Sales' measure group for the 'MuncyTopCust' cube from the MuncyTopCust database.
June 29, 2009 at 1:46 pm
With the missing dimension key it would basically mean that there is no match for the fact record in your dimension table. Are you certain that the dimension tables are being refreshed prior to processing the cube (partitions)?
----------------------------------------------------------------------------------------
Dan English - http://denglishbi.wordpress.com
June 29, 2009 at 5:52 pm
Thanks, Dan.
I am certain the dimension tables are being refreshed. The job step that refreshes the dimension tables preceeds the cube process step. After the cube process step fails I immediately manually process the cubes in Management Studio successfully. I then restart the job at the cube process step and it completes successfully. I also lookup the value of the foreign key in the fact table and verify that it exists in the dimension table.
I'm stumped.
July 14, 2009 at 5:24 am
I believe I've discovered what was occasionally causing the cube processing errors. In my SSIS package to process the cube I selected all objects (database, cube, and dimensions). I unselected cube and the dimensions, leaving just the database to be processed, then republished the package. I haven't had the problem occur in more than a week.
I did not know when I first created the package that having the database option selected will cause the dimensions and cube to process. Probably what was happening was that the objects were being processed out of order?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply