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 <ensei...@gmail.com> wrote: > Hello, > I had this problem and I did apply the solution on this page: > <https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix> > > 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 <ashokfrancis....@gmail.com>: > > > 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
