[Koha] 500 errors in staff mode and forcing a database update

[Fairlamb, Christina]

Hello all,

We've had these issues since at least Koha 21.11 but are now on 22.05.

Some links on the koha staff page result in a 500 error. Checking the
plack-error.log, these are the lines linking to the page I was trying to
access:


*EDI accounts*
DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st
execute failed: Unknown column 'me.responses_enabled' in 'field list' at
/usr/share/koha/intranet/cgi-bin/admin/edi_accounts.pl line 110

*Library EANs*

DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st
execute failed: Unknown column 'me.ee_id' in 'field list' at
/usr/share/koha/intranet/cgi-bin/admin/edi_ean_accounts.pl line 93

We also still have the Patron relationship problems issue in this bug:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24263, which
should have been fixed during past upgrades. (values have been used for
guarantee/guarantor relationships, but do not exist in the
'borrowerRelationship')

It seems as though our database schema is not updating fully during our
latest koha upgrades. I've tried to run the Manual schema upgrade which
results in this message only:

DEV atomic update
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/
bug_30899.pl  [07:15:11]: Bug 30899 - Check borrower_attribute_types FK
constraint (30449 follow-up)

Which, according to this bug report:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30899 - is a none
issue and means the schema is up to date.

Is there a way to force a schema update to go through all updates since a
specific koha version?

Christina