Hi David, the fix will only prevent new cases from happening. Before you implement it, you need to clean up your data. Deleting all duplicate entries from the deleted* tables is the easiest way to achieve this. Then when you restart your DBMS the primary keys will be set correctly to avoid the issue in the future, if all has been set up correctly. Also note that this is only necessary for specific DBMS versions as listed on the wiki page. If you have a newer version already, cleaning the data might be enough. There is nothing you can do from the GUI side to avoid these issues or to clean it up, it needs to be done with SQL. Hope this helps, Katrin On 07.07.23 11:41, David Liddle wrote:
Hi, Jonathan, we've both read through that entry in the wiki. You have an advantage over us in being someone well acquainted with the source of the problem and the ongoing history of resolving it. Naturally, it makes perfect sense to you—and we're grateful to you and all the other knowledgeable developers and bug-killers out here.
For us, the wiki page isn't so clear. When we take the steps that seem to be indicated, we do so with uncertainty. Here's what I've done so far on our development server, and I'd love to hear back that I've done the right thing:
SHOW databases; USE koha_library; SELECT b.biblionumber FROM biblioitems b JOIN deletedbiblioitems db ON b.biblionumber=db.biblionumber; SHOW columns FROM deletedbiblioitems; SELECT biblioitemnumber,biblionumber,timestamp FROM deletedbiblioitems WHERE biblionumber=11857; DELETE from deletedbiblioitems WHERE biblioitemnumber=11857; SELECT b.biblionumber FROM biblioitems b JOIN deletedbiblioitems db ON b.biblionumber=db.biblionumber; quit
1. I've removed the troublesome biblio from the table "deletedbiblioitems"; some of these steps are just me verifying information: # mysql 2. I've implemented the fix listed in the section "Current Solution" on the wiki page: -- Added a "[mysqld]" section to the file /etc/mysql/my.cnf. -- Added an "init-file" entry to that section that points to /var/lib/koha/library/mysql/init-file_koha_fix.sql. (I created the file here to ensure that it would be backed up.) -- Created and edited the file /var/lib/koha/library/mysql/init-file_koha_fix.sql as indicated. -- Restarted the DB server without errors.
There are still five entries that appear with the following query:
SELECT b.biblionumber FROM biblioitems b JOIN deletedbiblioitems db ON b.biblionumber=db.biblionumber; Each of the other queries given on the wiki page results in an empty set, which I assume to be a good thing. That leaves me with the following questions: -- Do I need to remove the remaining five entries from the table "deletedbiblioitems" in order to put the data in a clean state? -- Is there anything that the cataloging team needs to do or verify before (and after) these entries are removed?
Thank you very much for your help and patience!
David Liddle System Administrator
On Thu, Jul 6, 2023 at 2:43 PM Jonathan Druart <jonathan.druart@bugs.koha-community.org> wrote:
Hi Lauren, did you have a look at the wiki page? https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix
Le mer. 5 juil. 2023 à 20:50, Lauren Denny <lauren_denny@sil.org> a écrit :
Hi Jonathan,
Thanks for the SQL. We ran the report and got 6 biblionumbers including the one we tried to delete. I'm not sure what is wrong or how to fix these. Could you elaborate on what needs to be corrected.
Thanks, Lauren
On Tue, Jul 4, 2023 at 5:37 AM Jonathan Druart <jonathan.druart@bugs.koha-community.org> wrote:
Apparently the about page is not displaying the warning if the problem is on the [deleted]biblioitems table. You can catch the incorrect entries with the following SQL query: select b.biblionumber from biblioitems b join deletedbiblioitems db on b.biblionumber=db.biblionumber;
Le sam. 1 juil. 2023 à 10:49, David Liddle <david@liddles.net> a écrit :
Hi Katrin, and thank you for the input and suggestion. Our system shows no warnings, however. Not being on the cataloging side of things, I can’t provide much more detail about the context of the items to be deleted.
Regards from the Siegerland,
David
On Fri, Jun 30, 2023 at 8:13 PM Katrin Fischer <katrin.fischer.83@web.de> wrote:
Hi David,
please check the About Koha > System information tab for any errors.
I suspect you might see a warning about duplicated IDs. If that is the case, you can find some more information in the wiki:
https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix
Hope this helps,
Katrin
On 28.06.23 15:39, David Liddle wrote: > Greetings all! To add a little more detail to this issue, I'll include > that the server logs contain several instances of the following error: > > /var/log/koha/library/worker-output.log.1:C4::Biblio::_koha_delete_biblioitems(): > DBI Exception: DBD::mysql::st execute failed: Duplicate entry '11857' > for key 'PRIMARY' at /usr/share/koha/lib/C4/Biblio.pm line 535 > > Surely that biblio entry is the blocking element, but we're uncertain > about how it should be handled so that the deletion proceeds > smoothly—and without harming related entries. Thank you for giving it > your attention! > > David Liddle > System Administrator > david.liddle@wycliff.de (just not for this list) > > Wycliff e.V., https://wycliff.de > Seminar für Sprache und Kultur, https://spracheundkultur.org > Internationales Tagungszentrum Karimu, https://karimu.de > > > > On Fri, Jun 23, 2023 at 11:26 PM Lauren Denny <lauren_denny@sil.org> wrote: >> Hi everyone, >> >> I have a record that will not delete. When I try to delete the record or >> merge it with another record I get this message: >> An error has occurred!*Error 500*This message may have been caused by any >> of the following reasons: >> >> - You made use of an external link to an item that is no longer available >> - You followed an outdated link e.g. from a search engine or a bookmark >> - You tried to access a page that needs authentication >> - An internal link in the client is broken and the page does not exist >> What's next? >> >> - Use top menu bar to navigate to another part of Koha. >> - To report a broken link or any other issue, please contact the Koha >> administrator. Send email <library%40teamwork-global.net> >> >> Does anyone have an idea of what is happening? >> >> Lauren >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha@lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha@lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha