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. Logo inLibro <https://inLibro.com> Philippe Blouin Directeur de la technologie T 833-INLIBRO (465-4276) <tel:833-465-4276>, poste 230 C philippe.blouin@inLibro.com www.inLibro.com <https://inLibro.com> 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