namens Michael Kuhn
Verzonden: donderdag 25 augustus 2022 11:03
Aan: Koha
Onderwerp: [Koha] DBMS auto increment fix not working
Hi
In our library we are using Debian 11 with MariaDB 10.5.15 and Koha
21.05.14.
When deleting bibliographic records in the staff client, some deletions
produce the message: &
n the maximum id values in the deleted tables. If they would not be,
you may bump into the issue again one day.
Marcel
Van: Koha namens Michael Kuhn
Verzonden: donderdag 25 augustus 2022 11:03
Aan: Koha
Onderwerp: [Koha] DBMS auto increment fix not working
H
Hi Marcel
On 30 August you wrote:
> 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.
> The wiki promises a script but it never made it probably.
>
> But the easiest 'solution' is deleting the records in
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.
Marcel
Van: Koha namens Michael Kuhn
Verzonden: donderdag 25 augustus 2022 11:03
Hi Michael,
not sure then :(
Maybe someone else has an idea?
Katrin
On 25.08.22 18:39, Michael Kuhn wrote:
Hi Katrin
You wrote:
> the fix did prevent the problem from occurring on older versions, but
> it doesn't fix the data.
>
> Could it be the bad data was there before, maybe from using
Hi Katrin
You wrote:
> the fix did prevent the problem from occurring on older versions, but
> it doesn't fix the data.
>
> Could it be the bad data was there before, maybe from using an older
> DBMS version?
>
> The simplest fix is to delete the entries in the old_ and deleted_
> tables with th
Hi Michael,
the fix did prevent the problem from occurring on older versions, but it
doesn't fix the data.
Could it be the bad data was there before, maybe from using an older
DBMS version?
The simplest fix is to delete the entries in the old_ and deleted_
tables with the doubled up IDs and the
Hi
In our library we are using Debian 11 with MariaDB 10.5.15 and Koha
21.05.14.
When deleting bibliographic records in the staff client, some deletions
produce the message: "An error has occurred! Error 500 / This message
may have been caused by any of the following reasons: etc." In such
"This situation comes up quite often in the list."
-- so sorry, Google got me going in the correct direction, but was missing
that last little "how to" . I guess I should pay more attention to the
list.
Thank you again,
-S
On Thu, Nov 16, 2017 at 2:12 PM, Pedro Amorim wrote:
> You're wel
You're welcome!
I hope this helps others in the future. This situation comes up quite often
in the list.
Have a good one,
Pedro Amorim
On Nov 16, 2017 18:04, "Scott Owen" wrote:
> You Sir,
>
> ARE AWESOME !
>
> thank you so much.
>
> -S
>
>
> On Thu, Nov 16, 2017 at 1:05 PM, Pedro Amorim
You Sir,
ARE AWESOME !
thank you so much.
-S
On Thu, Nov 16, 2017 at 1:05 PM, Pedro Amorim wrote:
> 1) Copy the ID's from About Koha -> System Information
>
> 2) *Select * from old_issues where issue_id IN () * Confirm
> the listed rows are the ones you want to delete;
>
> 3) *Delete fro
1) Copy the ID's from About Koha -> System Information
2) *Select * from old_issues where issue_id IN () * Confirm
the listed rows are the ones you want to delete;
3) *Delete from old_issues where issue_id IN ();*
4) Check in items and be happy.
This should work.
Have a good one,
Pedro Amorim
thank you so much for the fast response.
Is there a report / SQL query to find the duplicate ids that exist on both
issues and old_issues tables ?
On Thu, Nov 16, 2017 at 12:54 PM, Pedro Amorim wrote:
> Scott,
>
> The documented fix only prevents the problem from happening in the future
> for
Scott,
The documented fix only prevents the problem from happening in the future
for new IDs, it will not fix the IDs already compromised.
This is the conversation I had with Marcel a couple weeks ago regarding
this issue:
http://koha.1045719.n5.nabble.com/Salvaging-data-before-using-DBMS-auto-inc
Hi all,
I have the following errors when my staff try and check in items:
"The item has not been checked in due to a configuration issue in your
system. You must ask an administrator to take a look at the about page and
search for the "data problems" section"
I have followed the solution as desc
Thanks very much. The method proposed by Chris Brown works like a charm. I
have no errors up to this point.
On 26 September 2017 at 16:22, Chrispin Simasiku Sitali wrote:
> Greetings all,
>
> I am trying to fix errors related to DBMS auto increment fix using:
> https://wiki.koha-community.org/wi
Dear All,
I had tried the fix given on page:
https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix
with steps as given below:
- Edit /etc/mysql/my.cnf
- Locate the [mysqld] section and add:
init-file=/var/lib/mysql/init-file_kohadev.sql
- Create a file /var/lib/mysql/init-
Hi,
Koha updated from 16.11.09 to 16.11.11.000 / Package Installation/ Ubuntu
14.04 Desktop
and using Mysql Version 14.14 Distrib 5.5.57
I have faced problems regarding check-in earlier. Therefore, Is it relevant
/ necessary for the said version of Koha to follow instructions given in
the URL on
Message-
From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Chrispin
Simasiku Sitali
Sent: Tuesday, September 26, 2017 8:23 AM
To: koha-user ; jonathan.dru...@bugs.koha-community.org
Subject: [Koha] DBMS auto increment fix
Greetings all,
I am trying to fix errors related to
Greetings all,
I am trying to fix errors related to DBMS auto increment fix using:
https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix
but when I come to
#Edit /etc/mysql/my.cnf
#Locate the [mysqld] section and add:
There is no [mysqld] section in this file
I am running Koha 17.05.04.
20 matches
Mail list logo
