Failed validation as a non-ragged hierarchy

After I define a TIME dimension and try to Maintain Dimension (Loading data at first time), it encounters error as below:
An error has occurred on the server
Error class: Express Failure
Server error descriptions:
INI: Error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>
INI: XOQ-01714: "TIME_TEST_HA.TIME_TEST_HA" failed validation as a non-ragged hierarchy, Generic at TxsOqStdFormCommand::execute
at oracle.olapi.data.source.DataProvider.callGeneric(Unknown Source)
at oracle.olapi.data.source.DataProvider.callGeneric(Unknown Source)
at oracle.olapi.data.source.DataProvider.executeBuild(Unknown Source)
at oracle.olap.awm.wizard.awbuild.UBuildWizardHelper$1.construct(Unknown Source)
at oracle.olap.awm.ui.SwingWorker$2.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Here is the data from related table TIME_TEST:
SELECT * FROM TIME_TEST;
YEAR QUARTER MONTH DAY
2008 4 11 5
2008 1 2 6
2008 4 10 7
2009 1 1 1
2009 1 1 5
Any help will be appreciate!
Thanks,
Satine

Hi Stuart,
My OLAP version is 11.1.0.7, upgrading from 11.1.0.6.
Here is the XML file for the dimension.
<!DOCTYPE Metadata [
<!ENTITY % BIND_VALUES PUBLIC "OLAP BIND VALUES" "OLAP METADATA">
%BIND_VALUES;
]>
<Metadata
Version="1.1">
<TimeDimension
Name="DAD"
ETViewName="DAD_VIEW"
ETKeyColumnName="DIM_KEY"
ETLevelColumnName="LEVEL_NAME"
ETDimensionOrderColumnName="DIM_ORDER"
ETHierarchyOrderColumnName="HIER_ORDER">
<Hierarchy>
<LevelHierarchy
IsSkipLevel="False"
IsRagged="False"
Name="SAD"
ETParentColumnName="PARENT"
ETDepthColumnName="DEPTH"
ETViewName="DAD_SAD_VIEW">
<HierarchyLevel
DimensionLevel="YEAR">
<HierarchyLevelMap
KeyExpression="TEST_TEST."YEAR""
Query="TEST_TEST">
<AttributeMap
Name="DAD_YEAR_ID"
Expression="TEST_TEST."YEAR"">
<Attribute
Name="DAD_YEAR_ID"/>
</AttributeMap>
<AttributeMap
Name="END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="END_DATE"/>
</AttributeMap>
<AttributeMap
Name="TIME_SPAN"
Expression="200">
<Attribute
Name="TIME_SPAN"/>
</AttributeMap>
<AttributeMap
Name="YEAR_END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="YEAR_END_DATE"/>
</AttributeMap>
<AttributeMap
Name="YEAR_TIME_SPAN"
Expression="200">
<Attribute
Name="YEAR_TIME_SPAN"/>
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="QUARTER">
<HierarchyLevelMap
KeyExpression="TEST_TEST."QUARTER""
Query="TEST_TEST">
<AttributeMap
Name="DAD_QUARTER_ID"
Expression="TEST_TEST."QUARTER"">
<Attribute
Name="DAD_QUARTER_ID"/>
</AttributeMap>
<AttributeMap
Name="END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="END_DATE"/>
</AttributeMap>
<AttributeMap
Name="QUARTER_END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="QUARTER_END_DATE"/>
</AttributeMap>
<AttributeMap
Name="QUARTER_TIME_SPAN"
Expression="200">
<Attribute
Name="QUARTER_TIME_SPAN"/>
</AttributeMap>
<AttributeMap
Name="TIME_SPAN"
Expression="200">
<Attribute
Name="TIME_SPAN"/>
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="MONTH">
<HierarchyLevelMap
KeyExpression="TEST_TEST."MONTH""
Query="TEST_TEST">
<AttributeMap
Name="DAD_MONTH_ID"
Expression="TEST_TEST."MONTH"">
<Attribute
Name="DAD_MONTH_ID"/>
</AttributeMap>
<AttributeMap
Name="END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="END_DATE"/>
</AttributeMap>
<AttributeMap
Name="MONTH_END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="MONTH_END_DATE"/>
</AttributeMap>
<AttributeMap
Name="MONTH_TIME_SPAN"
Expression="200">
<Attribute
Name="MONTH_TIME_SPAN"/>
</AttributeMap>
<AttributeMap
Name="TIME_SPAN"
Expression="200">
<Attribute
Name="TIME_SPAN"/>
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<Description
Type="Description"
Language="ENGLISH"
Value="Sad">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Sad">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Sad">
</Description>
</LevelHierarchy>
</Hierarchy>
<DimensionLevel
Name="YEAR"
ETKeyColumnName="YEAR">
<Description
Type="Description"
Language="ENGLISH"
Value="Year">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Year">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Year">
</Description>
<UniqueKeyAttribute
Name="DAD_YEAR_ID"/>
<VisibleAttribute
Name="YEAR_END_DATE"/>
<VisibleAttribute
Name="YEAR_TIME_SPAN"/>
<VisibleAttribute
Name="YEAR_LONG_DESCRIPTION"/>
<VisibleAttribute
Name="YEAR_SHORT_DESCRIPTION"/>
</DimensionLevel>
<DimensionLevel
Name="QUARTER"
ETKeyColumnName="QUARTER">
<Description
Type="Description"
Language="ENGLISH"
Value="Quarter">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Quarter">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Quarter">
</Description>
<UniqueKeyAttribute
Name="DAD_QUARTER_ID"/>
<VisibleAttribute
Name="QUARTER_END_DATE"/>
<VisibleAttribute
Name="QUARTER_TIME_SPAN"/>
<VisibleAttribute
Name="QUARTER_LONG_DESCRIPTION"/>
<VisibleAttribute
Name="QUARTER_SHORT_DESCRIPTION"/>
</DimensionLevel>
<DimensionLevel
Name="MONTH"
ETKeyColumnName="MONTH">
<Description
Type="Description"
Language="ENGLISH"
Value="Month">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Month">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Month">
</Description>
<UniqueKeyAttribute
Name="DAD_MONTH_ID"/>
<VisibleAttribute
Name="MONTH_END_DATE"/>
<VisibleAttribute
Name="MONTH_TIME_SPAN"/>
<VisibleAttribute
Name="MONTH_LONG_DESCRIPTION"/>
<VisibleAttribute
Name="MONTH_SHORT_DESCRIPTION"/>
</DimensionLevel>
<Attribute>
<BaseAttribute
SQLDataType="DATE"
ETAttributeColumnName="END_DATE"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="True"
Name="END_DATE">
<Classification
Value="STAR"/>
<Description
Type="Description"
Language="ENGLISH"
Value="End Date">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="End Date">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="End Date">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="NUMBER"
ETAttributeColumnName="TIME_SPAN"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="True"
Name="TIME_SPAN">
<Classification
Value="STAR"/>
<Description
Type="Description"
Language="ENGLISH"
Value="Time Span">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Time Span">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Time Span">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="LONG_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="True"
Name="LONG_DESCRIPTION">
<Classification
Value="STAR"/>
<Description
Type="Description"
Language="ENGLISH"
Value="Long Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Long Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Long Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="SHORT_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="True"
Name="SHORT_DESCRIPTION">
<Classification
Value="STAR"/>
<Description
Type="Description"
Language="ENGLISH"
Value="Short Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Short Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Short Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="DATE"
ETAttributeColumnName="YEAR_END_DATE"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="END_DATE"
IsVisibleForAll="False"
Name="YEAR_END_DATE">
<Description
Type="Description"
Language="ENGLISH"
Value="Year End Date">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Year End Date">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Year End Date">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="NUMBER"
ETAttributeColumnName="YEAR_TIME_SPAN"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="TIME_SPAN"
IsVisibleForAll="False"
Name="YEAR_TIME_SPAN">
<Description
Type="Description"
Language="ENGLISH"
Value="Year Time Span">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Year Time Span">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Year Time Span">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="YEAR_LONG_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="LONG_DESCRIPTION"
IsVisibleForAll="False"
Name="YEAR_LONG_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Year Long Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Year Long Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Year Long Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="YEAR_SHORT_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="SHORT_DESCRIPTION"
IsVisibleForAll="False"
Name="YEAR_SHORT_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Year Short Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Year Short Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Year Short Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="DATE"
ETAttributeColumnName="QUARTER_END_DATE"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="END_DATE"
IsVisibleForAll="False"
Name="QUARTER_END_DATE">
<Description
Type="Description"
Language="ENGLISH"
Value="Quarter End Date">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Quarter End Date">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Quarter End Date">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="NUMBER"
ETAttributeColumnName="QUARTER_TIME_SPAN"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="TIME_SPAN"
IsVisibleForAll="False"
Name="QUARTER_TIME_SPAN">
<Description
Type="Description"
Language="ENGLISH"
Value="Quarter Time Span">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Quarter Time Span">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Quarter Time Span">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="QUARTER_LONG_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="LONG_DESCRIPTION"
IsVisibleForAll="False"
Name="QUARTER_LONG_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Quarter Long Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Quarter Long Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Quarter Long Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="QUARTER_SHORT_DESCRIPTIO"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="SHORT_DESCRIPTION"
IsVisibleForAll="False"
Name="QUARTER_SHORT_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Quarter Short Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Quarter Short Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Quarter Short Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="DATE"
ETAttributeColumnName="MONTH_END_DATE"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="END_DATE"
IsVisibleForAll="False"
Name="MONTH_END_DATE">
<Description
Type="Description"
Language="ENGLISH"
Value="Month End Date">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Month End Date">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Month End Date">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="NUMBER"
ETAttributeColumnName="MONTH_TIME_SPAN"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="TIME_SPAN"
IsVisibleForAll="False"
Name="MONTH_TIME_SPAN">
<Description
Type="Description"
Language="ENGLISH"
Value="Month Time Span">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Month Time Span">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Month Time Span">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="MONTH_LONG_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="LONG_DESCRIPTION"
IsVisibleForAll="False"
Name="MONTH_LONG_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Month Long Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Month Long Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Month Long Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="MONTH_SHORT_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="SHORT_DESCRIPTION"
IsVisibleForAll="False"
Name="MONTH_SHORT_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Month Short Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Month Short Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Month Short Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(8)"
ETAttributeColumnName="DAD_YEAR_ID"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="False"
Name="DAD_YEAR_ID">
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(8)"
ETAttributeColumnName="DAD_QUARTER_ID"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="False"
Name="DAD_QUARTER_ID">
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(6)"
ETAttributeColumnName="DAD_MONTH_ID"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="False"
Name="DAD_MONTH_ID">
</BaseAttribute>
</Attribute>
<Organization>
<AWPrimaryDimensionOrganization
MVOption="NONE"
HierarchyConsistencyRule="STAR_CONSISTENT"
AddUniqueKeyPrefix="True">
<MVCreationOptions
RefreshOn="DEMAND"
RefreshType="COMPLETE"
EnableRewriteMV="False"
UsingConstraintsClause="ENFORCED">
</MVCreationOptions>
<AttributeOrganization
CreateIndex="False"
Attribute="END_DATE">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="TIME_SPAN">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="LONG_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="SHORT_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="YEAR_END_DATE">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="YEAR_TIME_SPAN">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="YEAR_LONG_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="YEAR_SHORT_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="QUARTER_END_DATE">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="QUARTER_TIME_SPAN">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="QUARTER_LONG_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="QUARTER_SHORT_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="MONTH_END_DATE">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="MONTH_TIME_SPAN">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="MONTH_LONG_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="MONTH_SHORT_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="DAD_YEAR_ID">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="DAD_QUARTER_ID">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="DAD_MONTH_ID">
</AttributeOrganization>
<AW
Name="&AW_NAME;"/>
<DefaultBuild>
<![CDATA[BUILD SPEC SYS_DEFAULT
LOAD,
COMPILE
)]]>
</DefaultBuild>
</AWPrimaryDimensionOrganization>
</Organization>
<Description
Type="Description"
Language="ENGLISH"
Value="Dad">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Dad">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Dad">
</Description>
<TimeSpanAttribute
Name="TIME_SPAN"/>
<EndDateAttribute
Name="END_DATE"/>
<DefaultHierarchy
Name="SAD"/>
<ValueDescriptionAttribute
Name="LONG_DESCRIPTION"/>
<ShortValueDescriptionAttribute
Name="SHORT_DESCRIPTION"/>
</TimeDimension>
</Metadata>
You may want to have a test to change IsRagged="False" to IsRagged="True", then it woks well but the result is very stange.
And I find if the hierarchy is only with levels: YEAR and Quarter, then you can maintain it, but, for sure, the YEAR2009,QUARTER1 will overwrite YEAR2008,QUARTER1. If defining the hierarchy with levels:YEAR,QUARTER,MONTH, then you can't maintain it. On my opinion, it may because the data in third level MONTH can't identified the right routine to the higher level QUARTER.
Thanks,
Satine

Similar Messages

Failed validation as a level hierarchy

Hi,
I have dimension called SKU in my analytic workspace with a hierarchy PRODUCTS defined as ALLPRODUCTS<--MD<--MG<--PG<--STYLE<--PRODUCT. I have used composite keys as Members to maintain uniqueness. For example the member expression for PG is CUBE_DEV.DIMSKU.MDID || CUBE_DEV.DIMSKU.MGID || CUBE_DEV.DIMSKU.PGID. I'm not using Surrogate keys. When I hit the maintain Dimension SKU, LOAD NO SYNCH succeeds but the compile step fails with error
"INI: error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>INI: XOQ-01712: "SKU.PRODUCTS" failed validation as a level hierarchy., Generic at TxsOqStdFormCommand::execute"
I looked at the rejected records and every record has the error "(XSRWLD13) Cannot change the level of a dimension member within a single load." Can anyone help me resolving this issue ?
I'm using AWM 11.2.0.1.0 on Oracle 11g R2 server.
Thanks,
RK

David,
I looked at the data and found out that there were NULLs in many key columns. I updated all of them to the value 'Unknown'. Also I re-implemented Composite keys because I thought Type 2 dimension would pose problem in determining uniqueness. Now there are no errors and I could successfully load data into the dimension.
Below is the latest definition
<!DOCTYPE Metadata [
<!ENTITY % BIND_VALUES PUBLIC "OLAP BIND VALUES" "OLAP METADATA">
%BIND_VALUES;
]>
<Metadata
Version="1.2"
MinimumDatabaseVersion="11.2">
<StandardDimension
Name="SKU"
ETViewName="SKU_VIEW"
ETKeyColumnName="DIM_KEY"
ETLevelColumnName="LEVEL_NAME"
ETMemberTypeColumnName="MEMBER_TYPE"
ETDimensionOrderColumnName="DIM_ORDER"
DefaultHierarchy="PRODUCTS"
ETHierarchyOrderColumnName="HIER_ORDER"
ShortValueDescriptionAttribute="SHORT_DESCRIPTION">
<Organization>
<AWPrimaryDimensionOrganization
AW="&AW_NAME;"
AddUniqueKeyPrefix="True"
MVOption="NONE"
HierarchyConsistencyRule="CONSISTENT">
<MVCreationOptions
RefreshType="COMPLETE"
RefreshOn="DEMAND"
UsingConstraintsClause="TRUSTED">
</MVCreationOptions>
<DefaultBuild>
<![CDATA[BUILD SPEC SYS_DEFAULT
LOAD,
COMPILE
)]]>
</DefaultBuild>
<AttributeOrganization
Attribute="SHORT_DESCRIPTION">
</AttributeOrganization>
</AWPrimaryDimensionOrganization>
</Organization>
<DimensionLevel
Name="MERCHDIVISION"
ETKeyColumnName="MERCHDIVISION">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="MERCHDIVISION">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="MERCHDIVISION">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="MERCHDIVISION">
</Description>
</DimensionLevel>
<DimensionLevel
Name="MERCHGROUP"
ETKeyColumnName="MERCHGROUP">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="MERCHGROUP">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="MERCHGROUP">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="MERCHGROUP">
</Description>
</DimensionLevel>
<DimensionLevel
Name="PRODUCTGROUP"
ETKeyColumnName="PRODUCTGROUP">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="PRODUCTGROUP">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="PRODUCTGROUP">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="PRODUCTGROUP">
</Description>
</DimensionLevel>
<DimensionLevel
Name="STYLE"
ETKeyColumnName="STYLE">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="STYLE">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="STYLE">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="STYLE">
</Description>
</DimensionLevel>
<DimensionLevel
Name="PRODUCT"
ETKeyColumnName="PRODUCT">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="PRODUCT">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="PRODUCT">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="PRODUCT">
</Description>
</DimensionLevel>
<Description
Type="LongDescription"
Language="AMERICAN"
Value="sku">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="sku">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="sku">
</Description>
<Hierarchy>
<LevelHierarchy
Name="PRODUCTS"
IsSkipLevel="True"
IsRagged="True"
ETParentColumnName="PARENT"
ETDepthColumnName="DEPTH"
ETViewName="SKU_PRODUCTS_VIEW">
<HierarchyLevel
DimensionLevel="MERCHDIVISION">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="MERCHGROUP">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID || DIMSKU.MGID"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID || ':' || DIMSKU.MGID">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="PRODUCTGROUP">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID || DIMSKU.MGID || DIMSKU.PGID"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID || ':' || DIMSKU.MGID || ':' || DIMSKU.PGID">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="STYLE">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID || DIMSKU.MGID || DIMSKU.PGID || DIMSKU.STYLE"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID || ':' || DIMSKU.MGID || ':' || DIMSKU.PGID || ':' || DIMSKU.STYLE">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="PRODUCT">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID || DIMSKU.MGID || DIMSKU.PGID || DIMSKU.STYLE || DIMSKU.SKU"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID || ':' || DIMSKU.MGID || ':' || DIMSKU.PGID || ':' || DIMSKU.STYLE || ':' || DIMSKU.SKU">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<Description
Type="LongDescription"
Language="AMERICAN"
Value="PRODUCTS">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="PRODUCTS">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="PRODUCTS">
</Description>
</LevelHierarchy>
</Hierarchy>
<Attribute>
<BaseAttribute
Name="SHORT_DESCRIPTION"
IsVisibleForAll="True"
SQLDataType="NVARCHAR2(100)"
ETAttributeColumnName="SHORT_DESCRIPTION">
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="Short Description">
</Description>
<Description
Type="LongDescription"
Language="AMERICAN"
Value="Short Description">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="Short Description">
</Description>
<Classification
Value="STAR"/>
</BaseAttribute>
</Attribute>
</StandardDimension>
</Metadata>
But I'm facing problem if I put Names in Short Description attribute. I have fields MerchGroupName, MerchDivisionName, ProductGroupName, StyleName in the database table which I would love to use for short description. When I use them, the error is
INI: error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>INI: XOQ-01600: OLAP DML error "ORA-34034: 1 is already a value of DEMANTRADW!SKU_MERCHDIVISION_SURROGATE." while executing DML "SYS.AWXML!R11_LOAD_DIM('SKU.DIMENSION' SYS.AWXML!___R11_LONG_ARG_VALUE(SYS.AWXML!___R11_LONG_ARG_DIM 1) 'MATCH' 'YES' 'YES' 'SKU.MERCHDIVISION.LEVEL' 'SKU.MERCHGROUP.LEVEL' 'SKU.PRODUCTGROUP.LEVEL' 'SKU.STYLE.LEVEL' 'SKU.PRODUCT.LEVEL' 'SKU.SHORT_DESCRIPTION.ATTRIBUTE' 'SKU.PRODUCTS.HIERARCHY')", Generic at TxsOqStdFormCommand::executeINI: XOQ-01601: error while loading data for Cube Dimension "CUBE_DEV.SKU" into the analytic workspace, Generic at TxsOqStdFormCommand::execute

JAAS between WLS (untrusted) domains - ServerIdentity failed validation

I'm trying to create a proxy/delegate class that can be used by clients to
transparently access a server.
The class should be usable from clients within WLS containers and from
regular java apps.
Using JNDI authentication everything works fine.
Using JAAS I'm having a problem when my client is a EJB app in an untrusted
WLS domain. When the login is requested the following error is occuring:
<ServerIdentity failed validation, downgrading to anonymous.>
I want to be able to do a JAAS login to a non-trusted domain. I'm assuming
that the server is trying to pass the subject who is logged into the current
container, and my call to LoginContext.login()
Any thoughts?
//Example of code
loginContext = new LoginContext("ServiceSecurity", new
FW_SimpleCallbackHandler(pUser, pPassword, pUrl));
loginContext.login();
Subject subject = loginContext.getSubject();
serviceHome = (ServiceHome)weblogic.security.Security.runAs( subject,
new PrivilegedExceptionAction() {
public Object run() throws Exception{
//JNDI lookup
//Create session bean instance
weblogic.security.Security.runAs( subject,
new PrivilegedExceptionAction() {
public Object run() throws Exception{
//do operation on instance

Then I'd start talking to BEA support to see if they even know how to do
this.
Without the trust relationship I'm not sure if you can achieve what you
want.
Dejan
Mark Fine wrote:
This is exactly what I am doing.
Implicitly there is a security context within the session bean (the user
logs in via the web app and context is propagated). I obtain a LoginContext
to the other server and call the method within that context.
It doesn't work because it is implicitly passing the security context of the
session bean and failing due to lack of trust.
//Example of code
loginContext = new LoginContext("ServiceSecurity", new
FW_SimpleCallbackHandler(pUser, pPassword, pUrl));
loginContext.login();
Subject subject = loginContext.getSubject();
serviceHome = (ServiceHome)weblogic.security.Security.runAs( subject,
new PrivilegedExceptionAction() {
public Object run() throws Exception{
//JNDI lookup
//Create session bean instance
weblogic.security.Security.runAs( subject,
new PrivilegedExceptionAction() {
public Object run() throws Exception{
//do operation on instance
"Deyan D. Bektchiev" <[email protected]> wrote in message
news:[email protected]...
In that case you should be able to get the two different Subjects from
the two different domains (return a different url from the URLCallback
when you login with JAAS), and afterwards use
weblogic.security.Security.doAs(...);
with the correct Subject for the appropriate server when you access the
servers.
HTH,
--dejan
Mark Fine wrote:
Thanks, but i think the content was miscommunicated. Everything works
fine
when the domains are "trusted". I want to know how to have "untrusted"
domains talk to each other through explicit logins.
ie. imagine an application on a domain in a finance department. What if
they are trusted against other domains and can't / don't want to
establish
trust with your domain. They just need access to one particular service
you
expose.
Thanks,
m
"Deyan D. Bektchiev" <[email protected]> wrote in message
news:[email protected]...
Hi Mark,
You should first establish a trust relationship between your Weblogic
servers:
http://e-docs.bea.com/wls/docs70/secmanage/domain.html#1171534
Then you can use JAAS to authenticate and get valid Subjects for the two
users.
--dejan
Mark Fine wrote:
I'm trying to create a proxy/delegate class that can be used by clients
to
transparently access a server.
The class should be usable from clients within WLS containers and from
regular java apps.
Using JNDI authentication everything works fine.
Using JAAS I'm having a problem when my client is a EJB app in an
untrusted
WLS domain. When the login is requested the following error is
occuring:
<ServerIdentity failed validation, downgrading to anonymous.>
I want to be able to do a JAAS login to a non-trusted domain. I'm
assuming
that the server is trying to pass the subject who is logged into the
current
container, and my call to LoginContext.login()
Any thoughts?
//Example of code
loginContext = new LoginContext("ServiceSecurity", new
FW_SimpleCallbackHandler(pUser, pPassword, pUrl));
loginContext.login();
Subject subject = loginContext.getSubject();
serviceHome = (ServiceHome)weblogic.security.Security.runAs( subject,
new PrivilegedExceptionAction() {
public Object run() throws Exception{
//JNDI lookup
//Create session bean instance
weblogic.security.Security.runAs( subject,
new PrivilegedExceptionAction() {
public Object run() throws Exception{
//do operation on instance

OSB Validate action failed validation

Hi All,
I'm trying to convert non-xml to xml by using XqueryTransformation source as an HL7 and target as an CCD schema.When validating the against the schema I got the following exception.
Please provide any suggestions.
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-382505</con:errorCode>
<con:reason>OSB Validate action failed validation</con:reason>
<con:details>
<con1:ValidationFailureDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
<con1:message>
string value '' does not match pattern for cs in namespace urn:hl7-org:v3
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
<con1:message>
Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
<con1:message>
Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
<con1:message>
Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
<con1:message>
Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
<con1:message>
Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
<con1:message>
Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
<con1:message>
Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
<con1:message>
Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
</con1:ValidationFailureDetail>
</con:details>
Thanks
Mani

Hi Anuj,
I tried doing that but in Response, it is echoing back the request after the statement:
The invocation resulted in an error: .
And now it shows:
Stage Error Handler
$fault: <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-382505</con:errorCode>
<con:reason>OSB Validate action failed validation</con:reason>
<con:details>
<con1:ValidationFailureDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
<con1:message>
string value '2' is not a valid enumeration value for VersionType in namespace http://www.example.org/abcd_Request_Schema
</con1:message>
<con1:xmlLocation>
<abcd:Version xmlns:abcd="http://www.example.org/abcd_Request_Schema">2</abcd:Version>
</con1:xmlLocation>
</con1:ValidationFailureDetail>
</con:details>
<con:location>
<con:node>PipelinePairNode1</con:node>
<con:pipeline>PipelinePairNode1_request</con:pipeline>
<con:stage>request xml validation</con:stage>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
System Error Handler
$fault: <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>402</con:errorCode>
<con:reason>
Validation Failed. Please enter proper values.
</con:reason>
<con:details>
<con1:ValidationFailureDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
<con1:message>
string value '2' is not a valid enumeration value for VersionType in namespace http://www.example.org/abcd_Request_Schema
</con1:message>
<con1:xmlLocation>
<abcd:Version xmlns:abcd="http://www.example.org/abcd_Request_Schema">2</abcd:Version>
</con1:xmlLocation>
</con1:ValidationFailureDetail>
</con:details>
<con:location>
<con:node>PipelinePairNode1</con:node>
<con:pipeline>PipelinePairNode1_request</con:pipeline>
<con:stage>request xml validation</con:stage>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
Is there any way by which only the customized error can be seen & not the OSB errors?

Ragged Hierarchy Snowflake Displays Dimension Key as Descriptor

Hello All -
I am having an issue with OWB 10gR2 and any help would be appreciated.
I have created a Product Dimension using the "ROLAP" - "Manual" storage method which I've modeled as a snowflake to support our ragged hierarchy.
I can create, validate, and view the data in the dimension and it is correct ... but the only level of my three levels (All Products, Products, Sub Products) to display the descriptor is the Sub Products level. The other two levels display the Surrogate ID - regardless of what settings I change.
I know this might sound trivial but it does make a huge difference when you're working with a large number of product hierarchies or demonstrating to non-technical superiors.
Thanks in advance for any assistance!

I took a look at this thread, but I think you have a different issue than mine. My Snowflake dimension isn't implemented as MANUAL. I use the Snowflake option and it isn't a "ragged" hierarchy.
In reality I do, but I "force" the levels to the maximum number. This lets me attach all facts at the base level and have a single grain. For example if I had a mix of 2 level and 3 level hierarchies, I repeat level 2 into level 3 for the 2 level items.
I rarely use the data viewer, but I did see that if I use it on the table objects, I see my short descriptors. If I use it on the dimension objects it doesn't work - probably because I only implement relational objects.

Dimension 'Years' failed validation

Hi All,
I am getting this error while deploying the application.
Error : Dimension 'Years' failed validation 'YearMembersSequential' for the following reason(s): Year members must be sequential.
I am seeing my Year dimension is sequential only.
I am not able to figure out the reason for this error . Can anyone please help me understand this.

Not to open a new thread as I have an issue with dimension Year as well, I will post my problem here (hope the author won't mind).
I created a simple EPMA application in version 11.1.2.2 with all mandatory and 2 generic dimensions. One of mandatory dimension is, of course, Year (dimension type: Year) with following members: FY11, FY12, FY13. Initial deployment against both, Planning and Essbase went well. After that I wanted to extend dimension Year for member FY14 and to redeploy the application. Validation was successful, but deployment message was "Completed/With Errors" (100%). Deployment was done with selecting "Refresh outline" and "Full deploy". In deployment log file I have the following entry:
"Consolidation operators for years must be set to Ignore for all plan types."
"Rejecting Member FY14."
This message is clear enough, but the problem is that members that belong to dimension type Year don't even have consolidation operators in properties area.
What else comes to my mind is that (maybe) with version 11.1.2.2 it is not allowed to add new members for dimension Year once application is deployed for the very first time. But in that case, the above error message is quite misleading. Under version 11.1.1.3 it is possible to add new members to dimension Year and to redeploy it without errors.
Is this a bug or a feature?
Has anyone had such problem?
Thanks,
Damir

Apple's Audio Units Fail Validation in Yosemite

Why do Apple's audio units fail validation in Yosemite
Anyone else having this problem ?
What's the fix ?
Even Logic Pro X 10.0.7 can't validate Apple's AU plugs.
[Rant: i have never been so disappointed with a Mac OS as i am with YO. Most of my midi/audio/video programs will not work because of the validation of AU/VST plugs. I am this close to trashing Yosemite . It reminds me of my OS 9 days: if you even looked in the wrong direction the system stop working.]

are there any AU plugs here, in the components folder...?

Define the Characteristics of the validity table for non-cumulatives

Hi Friends,
Here I am designing MultiProvider ( ZCA_M01), based on the Two Business content info cubes (0IC_C03 & 0SD_C03 ) & one customized info cube (ZPUR_C01).
I done Identification for char & keyfigures also.
When i trying to activating the Multiprovider, here i am getting the error , error message is : Define the Characteristics of the validity table for non-cumulatives.
Even here I am attaching the error message help also.
Message no. R7846
Diagnosis
The InfoCube contains non-cumulative values. A validity table is created for these non-cumulative values, in which the time interval is stored, for which the non-cumulative values are valid.
The validity table automatically contains the "most detailed" of the selected time characteristics (if such a one does not exist, it must be defined by the user, meaning transfered into the InfoCube).
Besides the most detailed time characteristic, additional characteristics for the InfoCube can be included in the validity table:
Examples of such characteristics are:
A "plan/actual" indicator, if differing time references exist for plan and actual values (actual values for the current fiscal year, plan values already for the next fiscal year),
the characteristic "plant", if the non-cumulative values are reported per plant, and it can occur that a plant already exists for plant A for a particular time period, but not yet for plant B.
Procedure
Define all additional characteristics that should be contained in the validity table by selecting the characteristics.
In the example above, the characteristics "plan/actual" and "plant" must be selected.
The system automatically generates the validity table according to the definition made. This table is automatically updated when data is loaded.
Please take as a high priority.
Thanks & Regards,
Vanarasi Venkat.

Hi Venkat,
If you want to include 0IC_C03 cube in your multi provider the you must make sure that the time characterestics ( 0CALDAY, 0CALMONTH ....) are present in all of the other info providers which you are including in the MP. The Time char to choose depends upon the Inventory cube in which you have mentioned during the definition. As you are using the standard cube 0IC_C03 it has the time char as 0CALDAY. Try to include this in all the other info providers and dont include more tha one Non-cumulative in the MP.
Try this and see if it helps....

File Browse is emptied after failed validation

Why does the file browse text box get emptied after a failed validation? Is there any way to prevent this?
To further explain, create a form on a page with two page items, a text box and a file browse item, then put a not null validation on the text box. When you submit the page with a null text box, but with a file selected for the browse button, then validation catches and throws the error message back to the user when the page refreshes. However, the file browse text box is emptied, and the user has to reselect the file before resubmitting the page.
Is this a bug, or just the way it is supposed to work? Any way around it?
Thanks,
Kris
Edited by: kshenn on Oct 31, 2008 7:06 AM

Hello,
>> Is this a bug, or just the way it is supposed to work?
This is not a bug. Actually, it has nothing to do with APEX. The behavior of the file browse item is controlled by the HTML standard, which clears the field for security reasons.
If you pay close attention to Denes example, you’ll see that even when the validation error page is displayed, the file browse item itself is being cleared. The JavaScript generated file path is the one that retain its value. I don’t have access to Denes code, but I’m assuming that in his uploading procedure he’s using the JavaScript generated path.
>> Any way around it?
Where the file browse item is concern, no workaround.
In your specific case, where the validation you need is “not null”, you can create a JavaScript validation, and fire it before submitting the page (as part of the submit button). That way, the browser will not clear the file browse item, because the page will not be submitted without proper values in your items.
Regards,
Arie.

Validity Table in Non cumulative cube

Hi Friends,
What is the use of validity table in Non cumulative cube?
I have already studied the document 'How to Inventory
Please can any one explain me with example.
Thanks & Regards,
Ramnaresh.P.

Hi,
Validity table is created for non-cumulative key values.
Non cumulative key figures are one which are not possible to cumulate such as head count, inventory amount, these are always in relation to a point in time.
Regards,
Shiva.

Server Crash : ServerIdentity failed validation, downgrading to anonymous

All,
Setup is as follows:
Domain has got an admin server and 2 managed servers.
Managed Server 1 on Machine 1
Managed Server 2 on Machine 2
Following error is continuously thrown in the logs :
<22-Jul-2010 09:54:45 o'clock> <Error> <Security> <managed1> <ExecuteThread: '2' for queue: 'weblogic.
socket.Muxer'> <<WLS Kernel>> <> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
Can this 090513 error on JMS queue lead to a server crash ?
I also get the below error
<ExecuteThread: '2' for queue: 'weblogic.adm
in.RMI' : Executing(weblogic.management.internal.MBeanHomeImpl)> <<WLS Kernel>> <> <BEA-080003> <RuntimeException thrown by r
mi server: weblogic.management.internal.MBeanHomeImpl.getMBean(Ljavax.management.ObjectName;)
java.lang.NullPointerException.
java.lang.NullPointerException
at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.java:109)
Regards,
Rashi

Does this domain have rmi communication with another weblogic domain? If so this error would normally occur if you have not enabled domain trust between the domains. You can enable domain trust by following the steps in the below link :
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/secmanage/domain.html#wp1176064
Not sure is this alone will crash a server. Is there any other errors in the logs ?

40222 Disabled item failed validation.

When I run a Forms app, I receive this error message after I click one of its buttons:
41012 Invalid value for field Renewal_Type
40222 Disabled item RB.Renewal_Type failed validation.
There is a radio group by that name in one of the blocks, although it has not been assigned to a canvas. I think the developer of this app may have intended it for another form that he was going to build, but never got to it; thus it's disabled. Is that what causes this error message or is it something else? How can I fix this? Thanks.
Edited by: Prohan on Sep 10, 2010 9:42 AM

I found the answer here:
FRM - 40212 / FRM - 40222 error on a radio group during query
I can't say I understood the explanation for why it worked, but it did.

Ragged Hierarchy and Skip Level Hierarchy

Hi all,
I am confused with ragged and skip level hierarchy, as i read some documents related to obiee 11g.
Will you please explain with an example the difference between ragged hierarchy and skip level hierarchy and also when to use these hierarchies?
regards
chandra kanth.

Chandra Kanth,
Hope this helps you
http://blogs.simba.com/.a/6a00e3932f172e88340133f4d758b5970b-800wi
Thanks,
Saichand.v

AIP-13978: Error - the input xsd fails validation

Hi,
For an ebXML setup over Generic exchange. I have to perform validation against XSDs which are nested in structure.
So while setting up the Document definition in the Business action, I uploaded the files as zip files and provided the name of the root XSD file.
However on clicking finish the for business action I am getting the IP-13978: Error - the input xsd fails validation: java.lang.NullPointerException
In the log file error message is as given:
2007.03.12 at 14:40:16:093: AJPRequestHandler-ApplicationServerThread-5: BusinessLogicLayer - (ERROR) java.lang.NullPointerException
     at oracle.tip.buslogic.datatypeimport.b2b.XMLSchemaImport.getXSDElement(XMLSchemaImport.java:259)
     at oracle.tip.buslogic.datatypeimport.b2b.XMLSchemaImport.importXSD(XMLSchemaImport.java:609)
     at oracle.tip.buslogic.datatypeimport.b2b.XMLSchemaImport.importZipFile(XMLSchemaImport.java:426)
     at oracle.tip.buslogic.bll.b2b.GenericWizard.createNativeDatatype(GenericWizard.java:452)
     at oracle.tip.buslogic.bll.b2b.DocumentProtocolWizard.createDocumentDefinition(DocumentProtocolWizard.java:1228)
     at oracle.tip.buslogic.bll.b2b.DocumentProtocolWizard.createDocumentDefinition(DocumentProtocolWizard.java:1061)
     at oracle.tip.tools.integration.buslogic.b2b.collaboration.CreateBusinessActionFinishEventHandler.performExtendedActions(CreateBusinessActionFinishEventHandler.java:245)
     at oracle.tip.tools.integration.event.IPBaseUnboundEventHandler.performActions(IPBaseUnboundEventHandler.java:88)
     at oracle.tip.tools.integration.event.IPEventHandler.handleEventIP(IPEventHandler.java:138)
     at oracle.tip.tools.integration.event.IPEventHandler.handleEvent(IPEventHandler.java:104)
     at oracle.cabo.servlet.event.TableEventHandler.handleEvent(Unknown Source)
     at oracle.cabo.servlet.event.TableEventHandler.handleEvent(Unknown Source)
     at oracle.cabo.servlet.event.BasePageFlowEngine.handleRequest(Unknown Source)
     at oracle.cabo.servlet.AbstractPageBroker.handleRequest(Unknown Source)
     at oracle.cabo.servlet.ui.BaseUIPageBroker.handleRequest(Unknown Source)
     at oracle.cabo.servlet.PageBrokerHandler.handleRequest(Unknown Source)
     at oracle.cabo.servlet.UIXServlet.doGet(Unknown Source)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
2007.03.12 at 14:40:16:093: AJPRequestHandler-ApplicationServerThread-5: UI - (ERROR) oracle.tip.tools.integration.buslogic.b2b.collaboration.CreateBusinessActionFinishEventHandler.handleEvent(): Error -: AIP-13978: Error - the input xsd fails validation: java.lang.NullPointerException
Please let me know to resolve this issue.
Thanks,
Gautham

Please check the root xsd and it its dependent XSD are present

OLE DB Destination" failed validation and returned validation status "VS_ISBROKEN.

Hi
I have a package which has 10 sequence containers. Have 10 Flat File Source files and all is working perfect on BI Debug mode. When I deploy this package to server I am getting the following error.
I have changed the property Retain the same connection = True but same problem. I have changed the data flow task to Load Project instead of Load Into Project but in error message it is still showing the old name. I have tried to remove the whole step i.e.
Removed Load into Project Data flow with sequence container but I am getting the same error message.
I am not able to understand the reason. Any Idea why am I getting the same error message even I do not have the Data Flow named Load Into Package. It is in SSIS 2008 and being deployed on SQL 2012 server.
Message
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 15:28:32 Error: 2014-07-22
15:28:36.86 Code: 0xC020201B Source: Load Into Project OLE DB Destination [62] Description: The number of input columns for OLE DB Destination.Inputs[OLE DB Destination Input] cannot be zero. End Error Error:
2014-07-22 15:28:36.86 Code: 0xC004706B Source: Load Into Project SSIS.Pipeline Description: "OLE DB Destination" failed validation and returned validation status "VS_ISBROKEN". End Error
Error: 2014-07-22 15:28:36.86 Code: 0xC004700C Source:
Load Into Project SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2014-07-22 15:28:36.87 Code: 0xC0024107 Source: Load Into Project Description:
There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 15:28:32 Finished: 15:28:36 Elapsed: 4.39 seconds. The package execution failed. The
step failed.
Many Thanks.
MH
this the error log
starttime
endtime
event
source
message
57:26.0
57:26.0
OnError
Load Into Project
The number of input columns for OLE DB Destination.Inputs[OLE DB Destination Input] cannot be zero.
57:26.0
57:26.0
OnError
Load Into Project
OLE DB Destination failed validation and returned validation status "VS_ISBROKEN".
57:26.0
57:26.0
OnError
Load Into Project
One or more component failed validation.
57:26.0
57:26.0
OnError
Load Into Project
There were errors during task validation.
57:19.0
57:19.0
OnPostExecute
Load Into TrialBalance
57:19.0
57:19.0
OnPostExecute
Trial Balance
57:19.0
57:19.0
OnPostExecute
SSIS_LoadCheck_CoreManGroup
57:19.0
57:19.0
PackageEnd
SSIS_LoadCheck_CoreManGroup
End of package execution.
57:18.0
57:18.0
OnPostExecute
Load Into JournalLine
57:18.0
57:18.0
OnPostExecute
JournalLine
57:18.0
57:18.0
OnPreExecute
Trial Balance
57:18.0
57:18.0
OnPreExecute
Truncate TrialBalance
57:18.0
57:18.0
OnPostExecute
Truncate TrialBalance
57:18.0
57:18.0
OnPreExecute
Load Into TrialBalance
57:07.0
57:07.0
OnPostExecute
Load Into Journal Type
57:07.0
57:07.0
OnPostExecute
JournalType
57:07.0
57:07.0
OnPreExecute
JournalLine
57:07.0
57:07.0
OnPreExecute
Truncate Table JournalLine
57:07.0
57:07.0
OnPostExecute
Truncate Table JournalLine
57:07.0
57:07.0
OnPreExecute
Load Into JournalLine
57:05.0
57:05.0
OnPostExecute
Load Into UserName
57:05.0
57:05.0
OnPostExecute
UserName
57:05.0
57:05.0
OnPreExecute
Business Area
57:05.0
57:05.0
OnPreExecute
Truncate Table Business Area
57:05.0
57:05.0
OnPostExecute
Truncate Table Business Area
57:05.0
57:05.0
OnPreExecute
Load Into Business Area
57:05.0
57:05.0
OnPostExecute
Load Into Business Area
57:05.0
57:05.0
OnPostExecute
Business Area
57:05.0
57:05.0
OnPreExecute
Cost Centre
57:05.0
57:05.0
OnPreExecute
Truncate CostCenter
57:05.0
57:05.0
OnPostExecute
Truncate CostCenter
57:05.0
57:05.0
OnPreExecute
Load Into Cost Centre
57:05.0
57:05.0
OnPostExecute
Load Into Cost Centre
57:05.0
57:05.0
OnPostExecute
Cost Centre
57:05.0
57:05.0
OnPreExecute
Project Status
57:05.0
57:05.0
OnPreExecute
Truncate Table Project Status
57:05.0
57:05.0
OnPostExecute
Truncate Table Project Status
57:05.0
57:05.0
OnPreExecute
Load Into Project Status
57:05.0
57:05.0
OnPostExecute
Load Into Project Status
57:05.0
57:05.0
OnPostExecute
Project Status
57:05.0
57:05.0
OnPreExecute
Project
57:05.0
57:05.0
OnPreExecute
Truncate Table Project
57:05.0
57:05.0
OnPostExecute
Truncate Table Project
57:05.0
57:05.0
OnPreExecute
Load Project
57:05.0
57:05.0
OnPostExecute
Load Project
57:05.0
57:05.0
OnPostExecute
Project
57:05.0
57:05.0
OnPreExecute
JournalType
57:05.0
57:05.0
OnPreExecute
Truncate Table Journal Type
57:05.0
57:05.0
OnPostExecute
Truncate Table Journal Type
57:05.0
57:05.0
OnPreExecute
Load Into Journal Type
57:03.0
57:03.0
OnPostExecute
Load Into Entity
57:03.0
57:03.0
OnPostExecute
Entity
57:03.0
57:03.0
OnPreExecute
Account
57:03.0
57:03.0
OnPreExecute
Truncate Table Accounts
57:03.0
57:03.0
OnPostExecute
Truncate Table Accounts
57:03.0
57:03.0
OnPreExecute
Load Into Account
57:03.0
57:03.0
OnPostExecute
Load Into Account
57:03.0
57:03.0
OnPostExecute
Account
57:03.0
57:03.0
OnPreExecute
UserName
57:03.0
57:03.0
OnPreExecute
Truncate Table User Name
57:03.0
57:03.0
OnPostExecute
Truncate Table User Name
57:03.0
57:03.0
OnPreExecute
Load Into UserName
57:02.0
57:02.0
PackageStart
SSIS_LoadCheck_CoreManGroup
Beginning of package execution.
57:02.0
57:02.0
OnPreExecute
SSIS_LoadCheck_CoreManGroup
57:02.0
57:02.0
OnPreExecute
CoA
57:02.0
57:02.0
OnPreExecute
Truncate Table CoA
57:02.0
57:02.0
OnPostExecute
Truncate Table CoA
57:02.0
57:02.0
OnPreExecute
Load Into CoA
57:02.0
57:02.0
OnPostExecute
Load Into CoA
57:02.0
57:02.0
OnPostExecute
CoA
57:02.0
57:02.0
OnPreExecute
Entity
57:02.0
57:02.0
OnPreExecute
Truncate Table Entity
57:02.0
57:02.0
OnPostExecute
Truncate Table Entity
57:02.0
57:02.0
OnPreExecute
Load Into Entity

Message
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 15:28:32 Error: 2014-07-22
15:28:36.86 Code: 0xC020201B Source: Load Into Project OLE DB Destination [62] Description: The number of input columns for OLE DB Destination.Inputs[OLE DB Destination Input] cannot be zero.
22 15:28:36.86 Code: 0xC004700C Source: Load Into Project 22 15:28:36.87 Code: 0xC0024107 Source: Load Into Project Description: There were errors during task validation. End
Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 15:28:32 Finished: 15:28:36 Elapsed: 4.39 seconds. The package execution failed. The step failed.
Hi MustafaH,
According to the error message(hightlight above), it seems it's a mapping issue that Naarasimha point out in the post above. Please check this carefully.
An OLE DB destination includes mappings between input columns and columns in the destination data source. You do not have to map input columns to all destination columns, but depending on the properties of the destination columns, errors can occur if
no input columns are mapped to the destination columns.
Reference form: http://msdn.microsoft.com/en-us/library/ms141237.aspx
In your post, you said that it is in SSIS 2008 and being deployed on SQL 2012 server. Do you mean that you create the package deployment utility by using SSIS 2008, and then implement SSIS deployment in SSIS 2012 environment? If so, you need to
convert the project to package deployment model to generate Manifest file in SSIS 2012. Please see:
Use the SQL Server 2008 version of Business Intelligence Development Studio to develop and maintain packages that are based on SQL Server 2008 Integration Services (SSIS)
Use SQL Server Data Tools - Business Intelligence for Visual Studio 2012 to develop and maintain packages that are based on SQL Server 2012 Integration Services (SSIS).
For more information, please see:
Interoperability and Coexistence (Integration Services):
http://msdn.microsoft.com/en-us/library/bb522577.aspx?ppud=4
If you have any feedback on our support, please click
here.
Elvis Long
TechNet Community Support

Failed validation as a non-ragged hierarchy

Similar Messages

Maybe you are looking for