OLE DB or ODBC error: Operation canceled; HY008 | Not allowed...columns...one side...many-to-one relationship

  • Hello,

    I just added a new dimension to a copy/imported tabular model, by way of Table Properties, and when to the diagram and added it into a hierarchy. All is well, and I can see data in the newly added columns. I saved, and when to deploy this test model to fully validate, and I get this error (which I dummied up a bit):

    "Column 'device_key' in Table 'Device' contains a duplicate value '1234567879' and this is not allowed for columns on the one side of a many-to-one relationship or for columns that are used as the primary key of a table.

    OLE DB or ODBC error: Operation canceled; HY008.

    An error occurred while processing the partition 'Acct_a34546b9-ebcc-4368-9d6e-f65ecbf41aa7' in table 'Acct_a34546b9-ebcc-4368-9d6e-f65ecbf41aa7'.

    OLE DB or ODBC error: Operation canceled; HY008.

    An error occurred while processing the partition 'Sub_201410' in table 'Subscriber_47f73a22-37f4-41f9-a1f9-c31fb3431f1b'.

    The current operation was cancelled because another operation in the transaction failed.

    OLE DB or ODBC error: Operation canceled; HY008.

    An error occurred while processing the partition 'RevB_201410' in table 'Revenue_a681f8c5-c2a7-4e7f-acc1-9dc2ed38728f'.

    OLE DB or ODBC error: Operation canceled; HY008.

    An error occurred while processing the partition 'P_201410' in table 'Ports_d4a1f101-0847-4169-8e63-2152048446a6'.

    OLE DB or ODBC error: Operation canceled; HY008.

    An error occurred while processing the partition 'SH_aec694ec-39bd-4c5f-b69c-38dc198ca7b2' in table 'SH_aec694ec-39bd-4c5f-b69c-38dc198ca7b2'."

    * I've deleted the test cube and deployed again same error.

    * I've redone the dimension in the cube and deployed again same error.

    * I've up'd the ExternalCommandTimeout from 3600 to 7200, and deployed again same error.

    * I looked around in the relationships but nothing really stood out, and I didn't change anything there.

    How can I fix this error?

    Thanks, JPQ

  • Your problem data:

    "Column 'device_key' in Table 'Device' contains a duplicate value '1234567879' "

    A key that you are using as the "one" in a "many to one" relationship has duplicate values in the table.

    If it's a genuine Many to Many relationship then Tabular doesn't support these natively until version 2016 (with Bi-Directional Cross Filters: https://msdn.microsoft.com/en-us/library/mt591991.aspx).

    There are plenty of ways around it in earlier versions though: http://social.technet.microsoft.com/wiki/contents/articles/22202.a-practical-example-of-how-to-handle-simple-many-to-many-relationships-in-power-pivotssas-tabular-models.aspx

    If it's not meant to be this way then dedupe the data and reprocess.


    I'm on LinkedIn

  • PB_BI (11/15/2016)


    Your problem data:

    "Column 'device_key' in Table 'Device' contains a duplicate value '1234567879' "

    If it's not meant to be this way then dedupe the data and reprocess.

    The problem was that I had tested a SSIS package that I made a mod too, and left the table with data, where I should have truncated it, so when I deployed, it moved new data in, dup'd the rows, and that was the error. I had thought it was something wrong in the cube itself, it was not. Truncated the data with the SSIS Package, problem fixed.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply