<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 7604 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 202, Issue 6<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Re: [Koha] DBMS auto increment fix not working (Michael Kuhn)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 6 Sep 2022 09:25:41 +0200<br>From: Michael Kuhn <mik@adminkuhn.ch><br>To: koha@lists.katipo.co.nz<br>Cc: Koha-devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] [Koha] DBMS auto increment fix not working<br>Message-ID: <393e75a8-fac7-5321-81b1-3a553d05513f@adminkuhn.ch><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>Hi Marcel<br><br>Unfortunately it seems like the mailing list is not accepting my <br>original answer to your e-mail (I tried twice). Instead after some days <br>I received an e-mail with the subject "Undelivered Mail Returned to <br>Sender", telling me<br><br>The mail system<br><br><koha@lists.katipo.co.nz>: connect to lists.katipo.co.nz[202.70.130.220]:25:<br> Connection refused<br><br>I don't even know if this e-mail is getting through. There's probably <br>something wrong with the mailing list when not accepting answers.<br><br>Best wishes: Michael<br>-- <br>Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis<br>Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz<br>T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch<br><br><br><br>Am 30.08.22 um 13:17 schrieb Marcel de Rooy:<br>> Hi,<br>> <br>> The fact that it will no longer happen under MariaDB 10.5.15 does not guarantee that you still suffer the consequences of older occurrences.<br>> The wiki promises a script but it never made it probably. But the easiest 'solution' is deleting the records in the deleted_* tables that have a corresponding id in the normal tables.<br>> After that verify that your autoincrement pointers on the normal tables are higher than the maximum id values in the deleted tables. If they would not be, you may bump into the issue again one day.<br>> <br>> Marcel<br>> <br>> ________________________________<br>> Van: Koha <koha-bounces@lists.katipo.co.nz> namens Michael Kuhn <mik@adminkuhn.ch><br>> Verzonden: donderdag 25 augustus 2022 11:03<br>> Aan: Koha <koha@lists.katipo.co.nz><br>> Onderwerp: [Koha] DBMS auto increment fix not working<br>> <br>> Hi<br>> <br>> In our library we are using Debian 11 with MariaDB 10.5.15 and Koha<br>> 21.05.14.<br>> <br>> When deleting bibliographic records in the staff client, some deletions<br>> produce the message: "An error has occurred! Error 500 / This message<br>> may have been caused by any of the following reasons: etc." In such<br>> cases Koha menu "About Koha > System information" shows the message<br>> aubout data problems, saying<br>> <br>> Some of your tables have problems with their auto_increment values<br>> which may lead to data loss.<br>> <br>> You should not ignore this warning.<br>> <br>> The problem is that InnoDB does not keep auto_increment across SQL<br>> server restarts (it is only set in memory). So on server startup the<br>> auto_increment values are set to max(table.id)+1.<br>> <br>> To know how to avoid this problem see the related wiki page: DBMS auto<br>> increment fix<br>> <br>> <br>> According to<br>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.koha-community.org%2Fwiki%2FDBMS_auto_increment_fix&data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C5c1a779522df4601c58808da8678d0b4%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637970150719835805%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5BkXPF4yrrhvuLP1nFx66eQITkFCQPhoGPDtsdCDWso%3D&reserved=0 the problem<br>> shouldn't appear with MariaDB 10.5.15 but as a trial we have implemented<br>> the solution described there and have restarted everything - still the<br>> problem persists.<br>> <br>> In such cases file "plack-error.log" shows the following:<br>> <br>> {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry<br>> '6187-marcxml-MARC21' for key 'deletedbiblio_metadata_uniq_key' [for<br>> Statement "<br>> INSERT INTO deletedbiblio_metadata (biblionumber,<br>> format, `schema`, metadata)<br>> SELECT biblionumber, format, `schema`, metadata FROM<br>> biblio_metadata WHERE biblionumber=?<br>> "] at /usr/share/koha/lib/C4/Biblio.pm line 2907<br>> <br>> I suspect this behavior indeed looks like the original auto_increment<br>> problem described in bugs 18242, 18651, 18966, 19106 and 20271 but the<br>> reason may in fact not be the same since the described problem shouldn't<br>> appear at all in MariaDB 10.5.15.<br>> <br>> Does anyone have an idea what is happening and how we can solve it?<br>> <br>> Best wishes: Michael<br>> --<br>> Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis<br>> Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz<br>> T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.adminkuhn.ch%2F&data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C5c1a779522df4601c58808da8678d0b4%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637970150719835805%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fS0wgTtECweT98NfdwYV%2FV82IYhpm82iqLYuWP8war4%3D&reserved=0<br>> _______________________________________________<br>> <br>> Koha mailing list https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkoha-community.org%2F&data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C5c1a779522df4601c58808da8678d0b4%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637970150719835805%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8d%2BiOpLG4oo49VF%2BwC9Y9hA7ZDJ6nUxcb2v7K1qdaxs%3D&reserved=0<br>> Koha@lists.katipo.co.nz<br>> Unsubscribe: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.katipo.co.nz%2Fmailman%2Flistinfo%2Fkoha&data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C5c1a779522df4601c58808da8678d0b4%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637970150719835805%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jNLi6yPA%2FG5CLqcpf1nVBI4tnedT4a7zHdM4wWMpcXI%3D&reserved=0<br>> _______________________________________________<br>> <br>> Koha mailing list http://koha-community.org<br>> Koha@lists.katipo.co.nz<br>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha<br><br><br><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 202, Issue 6<br>******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>