"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 <pjamori...@gmail.com> wrote: > 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" <so...@edzone.net> wrote: > >> You Sir, >> >> ARE AWESOME !!!!! >> >> thank you so much. >> >> -S >> >> >> On Thu, Nov 16, 2017 at 1:05 PM, Pedro Amorim <pjamori...@gmail.com> >> wrote: >> >>> 1) Copy the ID's from About Koha -> System Information >>> >>> 2) *Select * from old_issues where issue_id IN (<paste ID's here>) * Confirm >>> the listed rows are the ones you want to delete; >>> >>> 3) *Delete from old_issues where issue_id IN (<paste ID's here>);* >>> >>> 4) Check in items and be happy. >>> >>> This should work. >>> >>> Have a good one, >>> >>> Pedro Amorim >>> >>> On 16 November 2017 at 17:02, Scott Owen <so...@edzone.net> wrote: >>> >>>> 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 <pjamori...@gmail.com> >>>> wrote: >>>> >>>>> 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-usin >>>>> g-DBMS-auto-increment-fix-td5951803.html >>>>> >>>>> I ended up manually deleting said IDs from the old_issues table. >>>>> >>>>> Have a good one, >>>>> >>>>> Pedro Amorim >>>>> >>>>> On 16 November 2017 at 16:50, Scott Owen <so...@edzone.net> wrote: >>>>> >>>>>> 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 described >>>>>> >>>>>> https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix >>>>>> #The_solution >>>>>> >>>>>> and I continue to get the error, and staff are unable to check in >>>>>> items. >>>>>> >>>>>> Is there a fix / workaround that my staff can do ?? >>>>>> >>>>>> -S >>>>>> _______________________________________________ >>>>>> 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
