# Schema errors (info) when completing a DB Optimisation

**URL:** <https://forums.plex.tv/t/schema-errors-info-when-completing-a-db-optimisation/920604>\
**Category:** Plex Pass Betas\
**Tags:** server-mac\
**Created:** [May 29, 2025, 8:29pm UTC](https://forums.plex.tv/t/schema-errors-info-when-completing-a-db-optimisation/920604 "2025-05-29T20:29:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![LupoLoopy\_1](https://avatars.discourse-cdn.com/v4/letter/l/a9adbd/32.png) [@LupoLoopy\_1](https://forums.plex.tv/u/LupoLoopy_1)\
**Post date:** [May 29, 2025, 8:29pm UTC](https://forums.plex.tv/t/schema-errors-info-when-completing-a-db-optimisation/920604/1 "2025-05-29T20:29:45Z")

</div>

Server Version#: 1.41.8.9834  
Player Version#: N/A  
These errors present in the log when I attempt a database optimisation

21 instances of:

[Req#1444a6/Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x14b633b08, 17, statement aborts at 60: [select \* from metadata\_items limit 1] database schema has changed.

1 instance of

SQLITE3:0x14b633b08, 17, statement aborts at 21: [UPDATE activities SET `finished_at`=:U1 WHERE `id`=:C1] database schema has changed

This appears to be the angry query, as pulled from the verbose log:  
May 29, 2025 21:08:28.542 [0x16c72b000] INFO - [Req#13fa3d] SQLITE3:0x14b633b08, 17, statement aborts at 59: [SELECT mt.`id`,mt.`library_section_id`,mt.`parent_id`,mt.`metadata_type`,mt.`guid`,mt.`edition_title`,mt.`slug`,mt.`hash`,mt.`media_item_count`,mt.`title`,mt.`title_sort`,mt.`original_title`,mt.`studio`,mt.`rating`,mt.`audience_rating`,mt.`rating_count`,mt.`tagline`,mt.`summary`,mt.`content_rating`,mt.`content_rating_age`,mt.`index`,mt.`absolute_index`,mt.`duration`,mt.`user_thumb_url`,mt.`user_art_url`,mt.`user_banner_url`,mt.`user_clear_logo_url`,mt.`user_music_url`,mt.`user_fields`,mt.`originally_available_at`,mt.`available_at`,mt.`expires_at`,mt.`refreshed_at`,mt.`year`,mt.`added_at`,mt.`created_at`,mt.`updated_at`,mt.`changed_at`,mt.`resources_changed_at`,mt.`tags_genre`,mt.`tags_collection`,mt.`tags_director`,mt.`tags_writer`,

Is this anything I should worry about? Should I rollback to the old database backup? Unfortunately it predates this PMS version - but it’s only the version prior so I presume PMS will pick it up and attempt a schema upgrade if necessary?

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [August 27, 2025, 8:30pm UTC](https://forums.plex.tv/t/schema-errors-info-when-completing-a-db-optimisation/920604/2 "2025-08-27T20:30:14Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.