If a user creates a dimension with N levels and M attributes where N * M >
31, and if the user selects "Create level attribute columns in views" in AWM
for each of those attributes, then the server will incorrectly calculate
attribute GROUPING IDs for those levels. This can lead in some cases to the
following type of error during dimension build.
31, and if the user selects "Create level attribute columns in views" in AWM
for each of those attributes, then the server will incorrectly calculate
attribute GROUPING IDs for those levels. This can lead in some cases to the
following type of error during dimension build.
XOQ-00703: Error executing OLAP DML command "(GROUPINGID PRODUCT_PARENTREL
INTO
PRODUCT_ATTR_CGID USING PRODUCT_LEVELREL GID : ORA-36979: Property ***GID
dimension status mismatches level dimension status*** can only be set by the
GROUPINGID command.
A partial workaround for this issue is to uncheck "Create level attribute
columns in views" for each attribute until the number N * M (above) goes
below 31.
本文详细阐述了在AWM中创建维度属性时遇到的错误,特别是当维度水平乘以属性数量超过31时,可能出现的‘GROUPINGID’执行错误。提供了一个临时解决方案,即在每个属性中取消选择‘创建视图中的层级属性列’选项,直至维度属性的数量减少到31以下。
858

被折叠的 条评论
为什么被折叠?



