# DBRepair development

**URL:** <https://forums.plex.tv/t/dbrepair-development/822684>\
**Category:** Apps & Creations\
**Created:** [December 14, 2022, 3:57am UTC](https://forums.plex.tv/t/dbrepair-development/822684 "2022-12-14T03:57:23Z")\
**Posts on this page:** 1\
**Showing post:** 441

<div class="post-metadata">

**Author:** ![exuberantShadow](https://avatars.discourse-cdn.com/v4/letter/e/bbce88/32.png) [@exuberantShadow](https://forums.plex.tv/u/exuberantShadow)\
**Post date:** [March 29, 2024, 10:41pm UTC](https://forums.plex.tv/t/dbrepair-development/822684/441 "2024-03-29T22:41:20Z")

</div>

It’s not an error but an expected behaviour when the DB is running migrations.

It’s been mentioned in the release notes too:

> [@Plex Media Server](https://forums.plex.tv/t/plex-media-server/30447/620):
>
> (PLEASE NOTE) Please also be patient when updating to this version if you have a very large database and allow the upgrade process to finish.

---

_[View the full topic](https://forums.plex.tv/t/dbrepair-development/822684)._