Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I had a similar issue today (same error message), for the sake of anyone else getting here with the same problem I put some notes on my wiki: <a href="http://www.david-halliday.co.uk/wiki/doku.php?id=databases:oracle&amp;#select_dates_for_ssas_include_hierarchy" rel="nofollow">http://www.david-halliday.co.uk/wiki/doku.php?id=databases:oracle&amp;#select_dates_for_ssas_include_hierarchy</a></p> <p>My case was SQL (simplified and reworded to defend the innocent):</p> <pre><code>SELECT dim_id, dim_name, dim_attribute1.name, dim_attribute2.name FROM dim_table INNER JOIN dim_attribute1 ON dim.attribute1_id = dim_attribute1.id INNER JOIN dim_attribute2 ON dim.attribute2_id = dim_attribute2.id </code></pre> <p>The strange thing was the error was happening for some cases of dim_attribute1_name but not dim_attribute2_name. However this particular case the attribute was exactly the same. In the end the solution was to change the SQL to:</p> <pre><code>SELECT dim_id, dim_name, dim_attribute1.id, dim_attribute1.name, dim_attribute2.id, dim_attribute2.name FROM dim_table INNER JOIN dim_attribute1 ON dim.attribute1_id = dim_attribute1.id INNER JOIN dim_attribute2 ON dim.attribute2_id = dim_attribute2.id </code></pre> <p>Then use in the dimension (hiding the IDs in the list) the id value for the key of the attribute and the name for the name of the attribute. I haven't seen this before but for some reason it happened here. This solution I believe is better than setting the cube to process ignoring duplicate key errors.</p> <p>I presume that if one is building a dimension joining tables this will give better performance/reliability. But don't quote me on that.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload