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 -- 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 Am 10.07.24 um 15:20 schrieb Michael Kuhn via Koha-devel:
Hi Philippe
Many thanks! You wrote:
Ok, let's cheat. You have very few rules, and most of the info has been moved already. So just comment the lines 20734 to 20746 and run updatedatabase.pl again.
OR modify the version to move ahead.
update systempreferences set value = '19.1200018' where variable = 'version';
Then you can drop the issuingrules table later, when you're satisfied with everything. Note that you'll need to update the rules manually in the staff interface to add back the issue length and renewal count/period...
I have modified the version and then moved ahead... unfortunately there is another duplicate entry in another table and the script aborted again:
Upgrade to 19.12.00.029 [15:13:32]: Bug 17702 - Add column account_credit_types.archived {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry '0' for key 'PRIMARY' at /usr/share/perl5/DBIx/Class/Schema.pm line 1118. DBIx::Class::Schema::throw_exception(Koha::Schema=HASH(0x5598ef055ba8), "DBI Exception: DBD::mysql::db do failed: Duplicate entry '0' "...) called at /usr/share/perl5/DBIx/Class/Storage.pm line 113 DBIx::Class::Storage::throw_exception(DBIx::Class::Storage::DBI::mysql=HASH(0x5598f4639198), "DBI Exception: DBD::mysql::db do failed: Duplicate entry '0' "...) called at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1623 DBIx::Class::Storage::DBI::__ANON__("DBD::mysql::db do failed: Duplicate entry '0' for key 'PRIMARY'", DBI::db=HASH(0x5598f4e19490), undef) called at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 20966
How should I proceed?
Is there a way how I can check the original database for duplicate entries so the update process won't abort?
Best wishes: Michael