Hi Philippe You wrote:
If you're a bit adventurous (and have some time, which you're probably thinking you've burnt enough already): try to update to 20.05, for example, using 20.05 code.
So you reset your installation (you have saved your DB, right?), then instead of installing a 24.05, you install an older version, like 20.05 and do the update.
The specific lines in updatedatabase.pl probably are the same, but a lot of underlying plumbing could be different and work badly with your system. I'd start by ruling that out.
1. On an different host with Koha 23.11 I loaded the database which then showed the following error: ERROR 1452 (23000) at line 8292833: Cannot add or update a child row: a foreign key constraint fails (`koha_test`.`#sql-alter-368-2a`, CONSTRAINT `borrower_message_transport_preferences_ibfk_1` FOREIGN KEY (`borrower_message_preference_id`) REFERENCES `borrower_message_preferences` (`borrower_) 2. I didn't care for it and then tried to update the database. This time the update process went far far further but it still aborted here: Upgrade to 23.06.00.013 [17:56:51]: Bug 28966 - Holds queue view too slow to load for large numbers of holds ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Can't DROP CONSTRAINT `tmp_holdsqueue_ibfk_1`; check that it exists at /usr/share/koha/lib/C4/Installer.pm line 741 This seems to be a different problem and I'm hoping the solution could lead to the road of success... Do you happen to know how to solve this? 3. Furthermore I saw the database dump file I received for the update ends like this: -- -- Constraints der Tabelle `virtualshelves` -- ALTER TABLE `virtualshelves` ADD CONSTRAINT `virtualshelves_ibfk_1` FOREIGN KEY (`owner`) REFERENCES `borrowers` (`borrowernumber`) ON DELETE SET NULL ON UPDATE SET NULL; COMMIT; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; while the database dump files I usually create myself do not contain constraints at all and end like this: -- Dump completed on 2024-07-10 6:25:22 Does this make sense to you? Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch
On 2024-07-10 09:44, Michael Kuhn via Koha-devel wrote:
Hi
At my own risk I have modified the version to 19.12.00.029 and then moved ahead... (of course table "opac_news" will have to be checked after the update)
Unfortunately then another error popped up:
Upgrade to 19.12.00.075 [15:28:32]: Bug 25086 - Set changed_fields column of borrower_modifications as nullable {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Can't create table `koha_bib`.`serial` (errno: 150 "Foreign key constraint is incorrectly formed") at /usr/share/perl5/DBIx/Class/Schema.pm line 1118. DBIx::Class::Schema::throw_exception(Koha::Schema=HASH(0x5654e142fba8), "DBI Exception: DBD::mysql::db do failed: Can't create table `"...) called at /usr/share/perl5/DBIx/Class/Storage.pm line 113 DBIx::Class::Storage::throw_exception(DBIx::Class::Storage::DBI::mysql=HASH(0x5654e693cdd8), "DBI Exception: DBD::mysql::db do failed: Can't create table `"...) called at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1623 DBIx::Class::Storage::DBI::__ANON__("DBD::mysql::db do failed: Can't create table `koha_bib`.`seri"..., DBI::db=HASH(0x5654e71fe510), undef) called at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 21746
I guess in this case I cannot just modify the version and move ahead. I assume there will be more errors like this since the process hasn't even reached Koha 20.05. To me it seems like this database is corrupt and I cannot proceed to Koha 24.05.
Now my question ist - how can I check the integrity of the Koha 19.11 database so the update process to reach Koha 24.05 will work as expected?
Best wisshes: Michael