Upgrading to 8.6.x sometimes causes the error An explicit DROP INDEX is not allowed on index umbracoRelationType.IX_umbracoRelationType_alias

[nul800sebastiaan]

Some reports of this on the forum:

https://our.umbraco.com/forum/using-umbraco-and-getting-started/102207-unable-to-upgrade-form-855-to-860

https://our.umbraco.com/forum/using-umbraco-and-getting-started//102231-upgrade-error-855-to-861

We are not sure why but some people have constraints on the umbracoRelationType table, this is not something Umbraco creates.

To fix this, the migration to 8.6.0 should drop those constraints on IX_umbracoRelationType_alias , IX_umbracoRelationType_name and IX_umbracoRelationType_UniqueId , if they exist.

We would appreciate some community help with this!

[bjarnef]

@nul800sebastiaan could the projects have been migrated from v7 to v8?

I did a Google Search where I found this old PR which seems to be merged in v7.6 where e.g. has IX_umbracoRelationType_alias in the additions: https://github.com/umbraco/Umbraco-CMS/pull/1749/files

[nul800sebastiaan]

Not from the reports we've seen so far! All started as v8.

[leekelleher]

FWIW, I've hit this error (today), upgrading from 8.5.5 to 8.6.4, (on my localhost). To note, I didn't manually apply any constraints to the umbracoRelationType table. As far as I'm aware it was a typical/standard Umbraco install, (as in I haven't applied any SQL fine tuning, etc).

I ran the SQL query (from the forum post)...

ALTER TABLE umbracoRelationType
DROP CONSTRAINT IX_umbracoRelationType_alias;

...and that's resolved the issue, and I could upgrade.

[jameswilki]

Hi,
I've seen this error today upgrading from 8.5.5 to 8.11.1 on a local site. The site started as 8.2.0 and had the following upgrades up to 8.5.5:

• 8.2.0 -> 8.2.1
• 8.2.1 -> 8.4.0
• 8.4.0 -> 8.5.3
• 8.5.3 -> 8.5.5
  Running the above SQL query allowed the upgrade to continue - thanks @leekelleher & Chad on the forum.

When I upgraded a different site running on Umbraco Cloud last year, the error did not occur but it went through more steps. That site started as v8.0.0 and it received patch releases to 8.0.3. I had to manually upgrade the site to 8.4.2 as the automated upgrade failed.

• 8.0.0 -> 8.0.1 -> 8.0.2 -> 8.0.3 (cloud)
• 8.0.3 -> 8.4.2 (manual)
• 8.4.2 -> 8.5.5 (manual)
• 8.5.5 -> 8.6.2 (cloud)
• 8.6.2 -> 8.6.3 -> 8.6.4 -> 8.6.5 -> 8.8.0 -> 8.8.2 -> 8.9.1 -> 8.10.1 (cloud)

[umbrabot]

Hiya @nul800sebastiaan,

Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more.

We will close this issue for now but we're happy to open it up again if you think it's still relevant (for example: it's a feature request that's not yet implemented, or it's a bug that's not yet been fixed).

To open it this issue up again, you can write @umbrabot still relevant in a new comment as the first line. It would be super helpful for us if on the next line you could let us know why you think it's still relevant.

For example:

@umbrabot still relevant
This bug can still be reproduced in version x.y.z

This will reopen the issue in the next few hours.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂