Bug 32497 - Updating Database Structure fails with table "specified twice"
Summary: Updating Database Structure fails with table "specified twice"
Status: RESOLVED DUPLICATE of bug 32470
Alias: None
Product: Koha
Classification: Unclassified
Component: Installation and upgrade (web-based installer) (show other bugs)
Version: 22.11
Hardware: All All
: P1 - high blocker (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-19 19:35 UTC by Hannah Co
Modified: 2022-12-19 19:41 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hannah Co 2022-12-19 19:35:47 UTC
Upgrading from 22.05 to 22.11, the web installer is failing at "Updating database structure" with the following error:

Upgrade to 22.06.00.064 [11:24:08]: Bug 14783 - Allow patrons to change pickup location for non-waiting holds
ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Table 'systempreferences' is specified twice, both as a target for 'UPDATE' and as a separate source for data at /usr/share/koha/lib/C4/Installer.pm line 739
Added new system preference 'OPACAllowUserToChangeBranch'
ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Table 'systempreferences' is specified twice, both as a target for 'UPDATE' and as a separate source for data at /usr/share/koha/lib/C4/Installer.pm line 739

I am looking for a solution to this one, and not finding much that's helpful. Does installer.pm need modification, or does the database need some changes. Prior to the error I followed steps to resolve errors related to bug 32399, with errors on the issues table and a couple foreign keys. I don't see how the systempreferences table is related, though.
Comment 1 Katrin Fischer 2022-12-19 19:41:53 UTC
Hi Hanna, a fix for this will be in 22.11.01, see bug 32470.

*** This bug has been marked as a duplicate of bug 32470 ***