March 12, 2025 at 6:43 pm
Hi , Im Facing the Below Issue in Ananlytics.
We have a Inventory Partition which is connected to WareHouse Dimension.
Error Message:
Errors in the OLAP storage engine: The attribute key cannot be found when processing:
Table: 'T2_PieceInventory', Column: 'StorageID', Value: 'ERETURNS'; Table: 'T2_PieceInventory',
Column: 'WarehouseLocation', Value: '3PL'. The attribute is 'Storage Location'. Errors in the OLAP storage engine:
The attribute key was converted to an unknown member because the attribute key was not found.
Attribute Storage Location of Dimension: Warehouse from Database: ArhausAnalytics,
Cube: Arhaus Analytics, Measure Group: Product Inventory, Partition: Product Inventory 2021, Record: 19685997.
Details :
I've Verified the data in the Dimension and this was missing the in the Dimension then i went back and added to the View behind the dimension and now i see the data when i query the View. Processed the Dimension (Process Update ) multiple Times , Once done then Processed the Fact/Partition but I'm still facing the same issue and same error.
I've also tried emptying the table behind the Fact/Partition and re-loaded the Data.
Any Help would be Appreciated , Not able to figure it out what I'm I missing.
March 13, 2025 at 7:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
March 14, 2025 at 10:01 pm
First question, did you process full on the dimension containing the error? I don't remember if you can process updaate a partition, but I did read something about process updates only adding data and not removing data that nolonger exist.
The error message in your post refers to a different partition (2021) than the error message in the attached image (2024). I know SSAS does it's best to trick you by raising hundreds of messages saying "an error was found while processing x" and then you have to look for the preceding warning to find that actual error, but is it possible you fixed one error and found another?
You said you can see the missing dimension member in the view, after processing update can you browse the dimension and see the missing member? Does the dimension read all the data from the view or is there a query that might suppress some rows? e.g. SELECT * FROM dim.vwCustomers WHERE CurrentStatus = 1. Are you any good at MDX? (I am not), but sometimes the easiest way to check the presence of a dimension member is to run an mdx query where you can include the surrogate key that may not be visible in the cube.
Is your goal to get zero errors or get the cube processed and then solve the errors? The message says the missing key way converted to the unknown member. You should have the option of allowing this to continue without causing failure. Some people prefer to allow the unknown member to be used and not fail the cube, we usually assign a default dimension key to early arriving facts, but both are valid options and if the cube fails at night we set it to ignore unknown members and fix it the next day. If you have to, can you do a full process of the dimensions and then start by processing the problematic partitions? I realise this is a nightmare if the full cube takes many hours to process, but sometimes the cube demands a full process, or so it seems.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply