[Koha] Data problems

2018-02-05 Thread Ashok Francis
Dear All,

I am using Koha 17.11.02 version. When I visit the page About Koha ---
system information---, I am getting the information like data problem. Can
anyone please help me how to solve this problem?

Data problems

Some of your tables have problems with their auto_increment values which
may lead to data loss.

*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 
Problems foundPatrons

The following ids exist in both tables *borrowers* and *deletedborrowers*:

1322
Items

The following ids exist in both tables *items* and *deleteditems*:

15979, 15980, 20761, 21245
Holds

The following ids exist in both tables *holds* and *old_reserves*:

2, 3, 1

I will be thankful to you.

Ashok.
New Delhi.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Data problems

2018-02-05 Thread Alvaro Cornejo
Hi

You should follow apply the fix mentioned on the link.

About the duplicated entries, you should access tables "deletedborrowers",
"deleteditems" and "old_reserves" and delete entries that have the
mentioned indexes. Note that you will loose the info of those records.

Regards,

Alvaro

|-|
Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS
y GPRS online
  Visitenos en www.perusms.com

2018-02-05 6:36 GMT-05:00 Ashok Francis :

> Dear All,
>
> I am using Koha 17.11.02 version. When I visit the page About Koha ---
> system information---, I am getting the information like data problem. Can
> anyone please help me how to solve this problem?
>
> Data problems
>
> Some of your tables have problems with their auto_increment values which
> may lead to data loss.
>
> *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  fix>
> Problems foundPatrons
>
> The following ids exist in both tables *borrowers* and *deletedborrowers*:
>
> 1322
> Items
>
> The following ids exist in both tables *items* and *deleteditems*:
>
> 15979, 15980, 20761, 21245
> Holds
>
> The following ids exist in both tables *holds* and *old_reserves*:
>
> 2, 3, 1
>
> I will be thankful to you.
>
> Ashok.
> New Delhi.
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Data problems

2018-02-05 Thread Indranil Das Gupta
Hi,

On 05-Feb-2018 8:03 PM, "Alvaro Cornejo"  wrote:

Hi

You should follow apply the fix mentioned on the link.

About the duplicated entries, you should access tables "deletedborrowers",
"deleteditems" and "old_reserves" and delete entries that have the
mentioned indexes. Note that you will loose the info of those records.


Deleting those records is only half of the fix. The real part of the task
is to set up my.cnf correctly for the future, as mentioned in the section -
'The solution' on the wiki page.

Cheers
Indranil
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Data problems

2018-02-07 Thread Johan Seyfferdt
Hi. Have you fixed your problem yet? I had a similar situation a few weeks
ago and I am willing to help if you still need it.

Johan

On Feb 5, 2018 14:37, "Ashok Francis"  wrote:

Dear All,

I am using Koha 17.11.02 version. When I visit the page About Koha ---
system information---, I am getting the information like data problem. Can
anyone please help me how to solve this problem?

Data problems

Some of your tables have problems with their auto_increment values which
may lead to data loss.

*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 
Problems foundPatrons

The following ids exist in both tables *borrowers* and *deletedborrowers*:

1322
Items

The following ids exist in both tables *items* and *deleteditems*:

15979, 15980, 20761, 21245
Holds

The following ids exist in both tables *holds* and *old_reserves*:

2, 3, 1

I will be thankful to you.

Ashok.
New Delhi.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Data problems

2018-02-08 Thread Rubeno Fernández
Hello, 
I had this problem and I did apply the solution on this page:


However, even after rebooting the server I see the same warning on the About 
Koha: System information page. Why? Is this the expected behaviour?

Rubeno

El dilluns, 5 de febrer de 2018, a les 15:33:39 CET, Alvaro Cornejo va 
escriure:
> Hi
> 
> You should follow apply the fix mentioned on the link.
> 
> About the duplicated entries, you should access tables "deletedborrowers",
> "deleteditems" and "old_reserves" and delete entries that have the
> mentioned indexes. Note that you will loose the info of those records.
> 
> Regards,
> 
> Alvaro
> 
> |---
> |--|
> Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
> celular y Nextel
> en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS
> y GPRS online
>   Visitenos en www.perusms.com
> 
> 2018-02-05 6:36 GMT-05:00 Ashok Francis :
> > Dear All,
> > 
> > I am using Koha 17.11.02 version. When I visit the page About Koha ---
> > system information---, I am getting the information like data problem. Can
> > anyone please help me how to solve this problem?
> > 
> > Data problems
> > 
> > Some of your tables have problems with their auto_increment values which
> > may lead to data loss.
> > 
> > *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  > fix>
> > Problems foundPatrons
> > 
> > The following ids exist in both tables *borrowers* and *deletedborrowers*:
> > 
> > 1322
> > Items
> > 
> > The following ids exist in both tables *items* and *deleteditems*:
> > 
> > 15979, 15980, 20761, 21245
> > Holds
> > 
> > The following ids exist in both tables *holds* and *old_reserves*:
> > 
> > 2, 3, 1
> > 
> > I will be thankful to you.
> > 
> > Ashok.
> > New Delhi.
> > ___
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > https://lists.katipo.co.nz/mailman/listinfo/koha
> 
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Data problems

2018-02-08 Thread Jonathan Druart
You need to:
1. Read the wiki page entirely and carefully
2. Re-read it to make sure you understood everything
3. Make sure you are using an up-to-date version of Koha
4. Fix the existing corrupted data
5. Apply the fix at DBMS config level
6. Restart and test
7. Tell us if something is not clear in the wiki page

On Thu, 8 Feb 2018 at 11:14 Rubeno Fernández  wrote:

> Hello,
> I had this problem and I did apply the solution on this page:
> 
>
> However, even after rebooting the server I see the same warning on the
> About
> Koha: System information page. Why? Is this the expected behaviour?
>
> Rubeno
>
> El dilluns, 5 de febrer de 2018, a les 15:33:39 CET, Alvaro Cornejo va
> escriure:
> > Hi
> >
> > You should follow apply the fix mentioned on the link.
> >
> > About the duplicated entries, you should access tables
> "deletedborrowers",
> > "deleteditems" and "old_reserves" and delete entries that have the
> > mentioned indexes. Note that you will loose the info of those records.
> >
> > Regards,
> >
> > Alvaro
> >
> >
> |---
> > |--|
> > Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
> > celular y Nextel
> > en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
> SMS
> > y GPRS online
> >   Visitenos en www.perusms.com
> >
> > 2018-02-05 6:36 GMT-05:00 Ashok Francis :
> > > Dear All,
> > >
> > > I am using Koha 17.11.02 version. When I visit the page About Koha ---
> > > system information---, I am getting the information like data problem.
> Can
> > > anyone please help me how to solve this problem?
> > >
> > > Data problems
> > >
> > > Some of your tables have problems with their auto_increment values
> which
> > > may lead to data loss.
> > >
> > > *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 foundPatrons
> > >
> > > The following ids exist in both tables *borrowers* and
> *deletedborrowers*:
> > >
> > > 1322
> > > Items
> > >
> > > The following ids exist in both tables *items* and *deleteditems*:
> > >
> > > 15979, 15980, 20761, 21245
> > > Holds
> > >
> > > The following ids exist in both tables *holds* and *old_reserves*:
> > >
> > > 2, 3, 1
> > >
> > > I will be thankful to you.
> > >
> > > Ashok.
> > > New Delhi.
> > > ___
> > > Koha mailing list  http://koha-community.org
> > > Koha@lists.katipo.co.nz
> > > https://lists.katipo.co.nz/mailman/listinfo/koha
> >
> > ___
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > https://lists.katipo.co.nz/mailman/listinfo/koha
>
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Data problems

2018-02-08 Thread Indranil Das Gupta
Joubu +


cheers
indra

--
Indranil Das Gupta
L2C2 Technologies

Phone : +91-98300-20971
WWW  : http://www.l2c2.co.in
Blog: http://blog.l2c2.co.in
IRC : indradg on irc://irc.freenode.net
Twitter : indradg

On Thu, Feb 8, 2018 at 8:15 PM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> You need to:
> 1. Read the wiki page entirely and carefully
> 2. Re-read it to make sure you understood everything
> 3. Make sure you are using an up-to-date version of Koha
> 4. Fix the existing corrupted data
> 5. Apply the fix at DBMS config level
> 6. Restart and test
> 7. Tell us if something is not clear in the wiki page
>
> On Thu, 8 Feb 2018 at 11:14 Rubeno Fernández  wrote:
>
> > Hello,
> > I had this problem and I did apply the solution on this page:
> > 
> >
> > However, even after rebooting the server I see the same warning on the
> > About
> > Koha: System information page. Why? Is this the expected behaviour?
> >
> > Rubeno
> >
> > El dilluns, 5 de febrer de 2018, a les 15:33:39 CET, Alvaro Cornejo va
> > escriure:
> > > Hi
> > >
> > > You should follow apply the fix mentioned on the link.
> > >
> > > About the duplicated entries, you should access tables
> > "deletedborrowers",
> > > "deleteditems" and "old_reserves" and delete entries that have the
> > > mentioned indexes. Note that you will loose the info of those records.
> > >
> > > Regards,
> > >
> > > Alvaro
> > >
> > >
> > |---
> 
> > > |--|
> > > Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
> > > celular y Nextel
> > > en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
> > SMS
> > > y GPRS online
> > >   Visitenos en www.perusms.com
> > >
> > > 2018-02-05 6:36 GMT-05:00 Ashok Francis :
> > > > Dear All,
> > > >
> > > > I am using Koha 17.11.02 version. When I visit the page About Koha
> ---
> > > > system information---, I am getting the information like data
> problem.
> > Can
> > > > anyone please help me how to solve this problem?
> > > >
> > > > Data problems
> > > >
> > > > Some of your tables have problems with their auto_increment values
> > which
> > > > may lead to data loss.
> > > >
> > > > *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 foundPatrons
> > > >
> > > > The following ids exist in both tables *borrowers* and
> > *deletedborrowers*:
> > > >
> > > > 1322
> > > > Items
> > > >
> > > > The following ids exist in both tables *items* and *deleteditems*:
> > > >
> > > > 15979, 15980, 20761, 21245
> > > > Holds
> > > >
> > > > The following ids exist in both tables *holds* and *old_reserves*:
> > > >
> > > > 2, 3, 1
> > > >
> > > > I will be thankful to you.
> > > >
> > > > Ashok.
> > > > New Delhi.
> > > > ___
> > > > Koha mailing list  http://koha-community.org
> > > > Koha@lists.katipo.co.nz
> > > > https://lists.katipo.co.nz/mailman/listinfo/koha
> > >
> > > ___
> > > Koha mailing list  http://koha-community.org
> > > Koha@lists.katipo.co.nz
> > > https://lists.katipo.co.nz/mailman/listinfo/koha
> >
> > ___
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > https://lists.katipo.co.nz/mailman/listinfo/koha
> >
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Data problems

2018-02-08 Thread Rubeno Fernández
I followed the wiki to the letter and it actually misled me. The file I had to 
modify wasn't /etc/mysql/my.cnf but /etc/mysql/mysql.conf.d/mysqld.cnf, at 
least on this Ubuntu 16 installation. Until I did so, MySQL would give an 
error message on restart.

El dijous, 8 de febrer de 2018, a les 15:45:28 CET, Jonathan Druart va 
escriure:
> You need to:
> 1. Read the wiki page entirely and carefully
> 2. Re-read it to make sure you understood everything
> 3. Make sure you are using an up-to-date version of Koha
> 4. Fix the existing corrupted data
> 5. Apply the fix at DBMS config level
> 6. Restart and test
> 7. Tell us if something is not clear in the wiki page
> 
> On Thu, 8 Feb 2018 at 11:14 Rubeno Fernández  wrote:
> > Hello,
> > I had this problem and I did apply the solution on this page:
> > 
> > 
> > However, even after rebooting the server I see the same warning on the
> > About
> > Koha: System information page. Why? Is this the expected behaviour?
> > 
> > Rubeno
> > 
> > El dilluns, 5 de febrer de 2018, a les 15:33:39 CET, Alvaro Cornejo va
> > 
> > escriure:
> > > Hi
> > > 
> > > You should follow apply the fix mentioned on the link.
> > > 
> > > About the duplicated entries, you should access tables
> > 
> > "deletedborrowers",
> > 
> > > "deleteditems" and "old_reserves" and delete entries that have the
> > > mentioned indexes. Note that you will loose the info of those records.
> > > 
> > > Regards,
> > > 
> > > Alvaro
> > |
> > |-
> > |--
> > |
> > > |--|
> > > 
> > > Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
> > > celular y Nextel
> > > en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
> > 
> > SMS
> > 
> > > y GPRS online
> > > 
> > >   Visitenos en www.perusms.com
> > > 
> > > 2018-02-05 6:36 GMT-05:00 Ashok Francis :
> > > > Dear All,
> > > > 
> > > > I am using Koha 17.11.02 version. When I visit the page About Koha ---
> > > > system information---, I am getting the information like data problem.
> > 
> > Can
> > 
> > > > anyone please help me how to solve this problem?
> > > > 
> > > > Data problems
> > > > 
> > > > Some of your tables have problems with their auto_increment values
> > 
> > which
> > 
> > > > may lead to data loss.
> > > > 
> > > > *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 foundPatrons
> > > > 
> > > > The following ids exist in both tables *borrowers* and
> > 
> > *deletedborrowers*:
> > > > 1322
> > > > Items
> > > > 
> > > > The following ids exist in both tables *items* and *deleteditems*:
> > > > 
> > > > 15979, 15980, 20761, 21245
> > > > Holds
> > > > 
> > > > The following ids exist in both tables *holds* and *old_reserves*:
> > > > 
> > > > 2, 3, 1
> > > > 
> > > > I will be thankful to you.
> > > > 
> > > > Ashok.
> > > > New Delhi.
> > > > ___
> > > > Koha mailing list  http://koha-community.org
> > > > Koha@lists.katipo.co.nz
> > > > https://lists.katipo.co.nz/mailman/listinfo/koha
> > > 
> > > ___
> > > Koha mailing list  http://koha-community.org
> > > Koha@lists.katipo.co.nz
> > > https://lists.katipo.co.nz/mailman/listinfo/koha
> > 
> > ___
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > https://lists.katipo.co.nz/mailman/listinfo/koha

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Data problems

2018-02-09 Thread Ashok Francis
Hello,

Thank you so much for your email. I am very scared about the data loss. So
I didn't fix the problem. Can you please help me step by step? Thank you so
much.

On Wed, Feb 7, 2018 at 11:26 PM, Johan Seyfferdt  wrote:

> Hi. Have you fixed your problem yet? I had a similar situation a few weeks
> ago and I am willing to help if you still need it.
>
> Johan
>
> On Feb 5, 2018 14:37, "Ashok Francis"  wrote:
>
> Dear All,
>
> I am using Koha 17.11.02 version. When I visit the page About Koha ---
> system information---, I am getting the information like data problem. Can
> anyone please help me how to solve this problem?
>
> Data problems
>
> Some of your tables have problems with their auto_increment values which
> may lead to data loss.
>
> *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  x>
> Problems foundPatrons
>
> The following ids exist in both tables *borrowers* and *deletedborrowers*:
>
> 1322
> Items
>
> The following ids exist in both tables *items* and *deleteditems*:
>
> 15979, 15980, 20761, 21245
> Holds
>
> The following ids exist in both tables *holds* and *old_reserves*:
>
> 2, 3, 1
>
> I will be thankful to you.
>
> Ashok.
> New Delhi.
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
>
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Data problems

2018-02-10 Thread Jonathan Druart
There is a "Deal with corrupted data" section on the wiki which point to a
bug report, with a proposed patch.
You can try it and see if it works for you.
Good luck

On Sat, 10 Feb 2018 at 02:24 Ashok Francis 
wrote:

> Hello,
>
> Thank you so much for your email. I am very scared about the data loss. So
> I didn't fix the problem. Can you please help me step by step? Thank you so
> much.
>
> On Wed, Feb 7, 2018 at 11:26 PM, Johan Seyfferdt  wrote:
>
> > Hi. Have you fixed your problem yet? I had a similar situation a few
> weeks
> > ago and I am willing to help if you still need it.
> >
> > Johan
> >
> > On Feb 5, 2018 14:37, "Ashok Francis" 
> wrote:
> >
> > Dear All,
> >
> > I am using Koha 17.11.02 version. When I visit the page About Koha ---
> > system information---, I am getting the information like data problem.
> Can
> > anyone please help me how to solve this problem?
> >
> > Data problems
> >
> > Some of your tables have problems with their auto_increment values which
> > may lead to data loss.
> >
> > *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_fi
> > x>
> > Problems foundPatrons
> >
> > The following ids exist in both tables *borrowers* and
> *deletedborrowers*:
> >
> > 1322
> > Items
> >
> > The following ids exist in both tables *items* and *deleteditems*:
> >
> > 15979, 15980, 20761, 21245
> > Holds
> >
> > The following ids exist in both tables *holds* and *old_reserves*:
> >
> > 2, 3, 1
> >
> > I will be thankful to you.
> >
> > Ashok.
> > New Delhi.
> > ___
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > https://lists.katipo.co.nz/mailman/listinfo/koha
> >
> >
> >
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] Data problems "Check In"

2018-12-13 Thread betocalderon
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.

***
Data problems

Some of your tables have problems with their auto_increment values which may
lead to data loss.

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
Problems found
Items

The following ids exist in both tables items and deleteditems:

7, 8, 9, 10
Checkouts

The following ids exist in both tables issues and old_issues:

1, 2, 3



--
Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Data problems "Check In"

2018-12-14 Thread Katrin Fischer
What is your question? Have you checked the wiki page the text mentions? 
It explains all about the problem:


https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix

On 13.12.18 18:12, betocalderon wrote:

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.

***
Data problems

Some of your tables have problems with their auto_increment values which may
lead to data loss.

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
Problems found
Items

The following ids exist in both tables items and deleteditems:

7, 8, 9, 10
Checkouts

The following ids exist in both tables issues and old_issues:

1, 2, 3



--
Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha