Hi Scott, yes, the wiki page has all the current information and suggestions on how to solve this issue. It also notes the DBMS versions where the problem will be fixed.
The easiest way to resolve the problem is deleting the doubled up entries from the old* and deleted* tables. Then you can implement the fix and restart your DBMS server to reset the primary keys to the correct values. This will prevent the creation of more doubled up IDs between the tables. Hope this helps, Katrin On 22.09.21 21:37, Scott Owen wrote:
Hi All, https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix Is this still the best procedure when getting the following error ? ************************************************ You should not ignore this warning. The problem is that InnoDB does not keep auto_increment across SQL server restarts (it is only set in memory). So on server startup the auto_increment values are set to max(table.id)+1. To know how to avoid this problem see the related wiki page: DBMS auto increment fix<https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix> Problems foundCheckouts The following ids exist in both tables issues and old_issues: 4782, 4781 ************************************************ Any sql to clean things up in the two tables ? _______________________________________________ Koha mailing listhttp://koha-community.org [email protected] Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org [email protected] Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
