We have a cube that exists on a Dev, Test, and Prod environment. For all three environments, they are refreshed nightly using the "Process Full" option. We have the same code base on all three environments and our DW that is used to populate the cubes is in sync across all three environments.
In the past couple of weeks, we have started to get the following error on our Dev and Test environments. The clinician that is referenced is always either this clinician or one or 2 other clinicians.
Errors in the OLAP storage engine: The attribute key cannot be found when processing:
Table: 'DW_dimClinician', Column: 'LastNameFirst_Version', Value: 'Duck, Daffy - 1669788907 - 1';
Table: 'DW_dimClinician', Column: 'NPI', Value: '1669788907'; Table: 'DW_dimClinician', Column: 'ETLEffectiveTo', Value: '6/1/2013 2:22:55 AM'.
The attribute is 'Last Name First Version'.
We have confirmed that the attribute does exist in the warehouse and it does not contain any null values. The attribute in question has not changed in the warehouse in a couple of years.
When the error occurs, we will process just the dimension and once it completes successfully, we will re-process the cube using the Process Full option and it will process successfully.
Yesterday, if failed again. We did not reprocess anything. Last night during the normal refresh, the load did the Process Full on the cube and it successfully processed the cube.
My understanding of the Process Full option was that the cube would automatically process the dimensions first, then process the measures. Due to the inconsistently, It feels like it is trying to process some of the measures prior to the dimensions. Luckily it has not hit our production environment yet. But, I am trying to understand the issue so that I can ensure it doesn't hit that environment.
Are we interpreting the error message correctly?