| Author |
Topic |
|
jodz
Starting Member
2 Posts |
 Posted - 2006-03-31 : 07:23:58
|
| Newbie here and I got a problem processing a cube. I'm using SQL 2005.I have two tables. One fact table, which also contains dimensions (tble A), and a dimension table (tble b).I keep having the error mentioned above referencing the identity column of my tble a. I have not used this column as a dimension. I've tried ignoring the error during process and the processing would be succesful, but whene the cube is viewed in the web page, there are no record.Please help. How do I work around this error?Thanks! |
|
|
jodz
Starting Member
2 Posts |
Posted - 2006-03-31 : 07:37:55
|
| Errors in the OLAP storage engine: The attribute key cannot befound: |
 |
|
|
pmalkan
Starting Member
1 Post |
Posted - 2006-05-09 : 17:36:06
|
| I am having an exact same problem with my cube "Errors in the OLAP storage engine: The attribute key cannot be found:'. Did you ever figure out the solution?The record that it system indicated error on has nothing wrong with it or even with any relational entity. This is big database. Not sure if that's what is causing and if I need to try anything on Partition side.Appreciate any help I can get. |
|
|
|
spdhiva
Starting Member
13 Posts |
Posted - 2006-10-13 : 16:06:14
|
| The key, which you have in the fact table doesn't exist in the Dim table. You can use the Qry analyzer to find which key exists in the fact table and Which doesn't in Dim table. If you find any then add the value in the dim table and Process the Dimension and Cube. |
|
|
|
influent
Constraint Violating Yak Guru
367 Posts |
Posted - 2008-02-05 : 12:47:46
|
| I ran into this issue because I had accidentally messed up my script that was inserting data into my fact table, which made my foreign key no longer valid. |
|
|
|
ChrisBui2008
3 Posts |
Posted - 2009-01-23 : 15:59:00
|
| This usually occur's when you delete an attribute, dimension, etc. and you reprocess the cube before reprocessing the dimension. There are really two ways to fix it. 1) run a sql query to find the missing values and replace the value with the correct one. 2) drop the partition and create a new one. I prefer option #2 because it's quicker.Chris Bui |
|
|
|
TabAlleman
Starting Member
8 Posts |
Posted - 2009-05-07 : 12:33:20
|
| Is there some way that you can set up your dimension so that if the attribute in the fact table is not found in the dimension table, it defaults to some "unknown" member? I tried to do this, but I'm still getting this error.-Tab Alleman |
|
|
|
pratana
Starting Member
1 Post |
Posted - 2011-02-13 : 15:17:37
|
| I had the exact same problem.Reprocessing the dimensions THEN the cube fixed this for me. |
|
|
|
influent
Constraint Violating Yak Guru
367 Posts |
Posted - 2011-06-29 : 14:34:38
|
| I know this is old but it seems like a good place to ask: What do you get from processing a cube that you don't get from processing its measures and dimensions? I'm assuming the answer is the same for all versions of SSAS, but I could be wrong. |
|
|
|
|
Errors in the OLAP storage engine: The attribute k