处理时出现OLAP错误 [英] OLAP Error while Processing

问题描述

我是OLAP的新手，并想出了如何制作多维数据集和对其进行处理的方法.但是，当我玩的太多时，最终会遇到以下错误:

I am new to OLAP, and figured out how to make a cube and process it. However, when i play with it too much, i eventually come up against this error:

OLAP存储引擎中的错误: 找不到属性键:表: dbo_v_MYEntities，列:uniqueId， 值:2548.OLAP中的错误 存储引擎:记录已跳过 因为属性键不是 成立.属性:的唯一ID 维度:v个来自的MY实体 数据库:Test Cube New，多维数据集:MYdm MyApp-视图，度量值组:v MY 实体，分区:v MY实体， 记录:2526.

Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_v_MYEntities, Column: uniqueId, Value: 2548. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Unique Id of Dimension: v MY Entities from Database: Test Cube New, Cube: MYdm MyApp - Views, Measure Group: v MY Entities, Partition: v MY Entities, Record: 2526.

似乎有些值卡住了，并且多维数据集希望该值在那里，我知道我可以编辑错误属性并阻止它引发异常，但是我希望能够对其进行修复.

It seems that some values get stuck, and the cube expect the value to be there, I know i can edit error properties and stop it from throwing exceptions, but i would like to be able to fix it.

我不介意清除多维数据集，以便它从头开始重新生成，但是我似乎无法做到这一点.

I wouldn't mind clearing the cube, so that it re-generates itself from scratch, but i can't seem to be able to do that.

一旦出现此错误，即使我删除了多维数据集并从头开始再次创建它，该错误仍然存​​在.

Once i get this error, even if i delete the cube, and create it again from scratch, the error is still there.

到目前为止(在我的测试环境中)，唯一的解决方案是更改项目部署目标属性中的数据库名称.显然，这不会在生产中达到成功.

The only solution so far (in my test environment) was to change database name in project deployment target properties. Obviously this will not do the trick in production.

推荐答案

基本上是

表:dbo_v_MYEntities，列: uniqueId，值:2548

Table: dbo_v_MYEntities, Column: uniqueId, Value: 2548

意味着您的表/视图"dbo.v_MYEntities"具有一列"uniqueid"，其中包含值"2548"，该值不在BIDS维度使用选项卡中与dbo.v_MYEntities相关的表中.当dbo.v_MYEntities是事实表，并且相关的维表不包含键时，通常会发生这种情况.我将检查模式的参照完整性，以尝试确定为什么会发生这种情况，并在ETL或视图定义中对其进行更正.

Means that your table/view "dbo.v_MYEntities" has a column "uniqueid", which contains a value "2548" which is not in a table which is related to dbo.v_MYEntities in the dimension usage tab in BIDS. This usually happens when dbo.v_MYEntities is a fact table, and the related dimension table does not contain a key. I would check the referential integrity of the schema trying to determine why this is happening and correct it in the ETL or in the view definition.

这篇关于处理时出现OLAP错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！