# Problem when updating from 8.5.12 to 9.2.1

**URL:** <https://forums.concretecms.org/t/problem-when-updating-from-8-5-12-to-9-2-1/5977>\
**Category:** Installation\
**Created:** [August 1, 2023, 12:08pm UTC](https://forums.concretecms.org/t/problem-when-updating-from-8-5-12-to-9-2-1/5977 "2023-08-01T12:08:22Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![EvanCooper](https://forums.concretecms.org/user_avatar/forums.concretecms.org/evancooper/32/4597_2.png) [@EvanCooper](https://forums.concretecms.org/u/EvanCooper)\
**Post date:** [August 30, 2023, 9:19pm UTC](https://forums.concretecms.org/t/problem-when-updating-from-8-5-12-to-9-2-1/5977/7 "2023-08-30T21:19:28Z")

</div>

All right I think I have a solution:

This comes from the database creating one table with one collation and the other with another. In some sites there’s a difference between the databases created during install and when Concrete adds tables during an upgrade later.

The fix is to make the `OAuth2ClientScopes` and `OAuth2Client` databases tables have the same collation. If they don’t you can use a command like

`ALTER TABLE OAuth2ClientScopes CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;`

to fix one or both of them.

Let me know if that does the trick.

---

_[View the full topic](https://forums.concretecms.org/t/problem-when-updating-from-8-5-12-to-9-2-1/5977)._