Thank you Kathy,
Those changes seemed to work great. What seemed to never end completed in about
a minute, and I was able to start up Evergreen and search/renew and otherwise
interact with the test system as expected (in my limited IT testing role not
being a library staff member that fully utilizes the system). Is this to be
expected to complete that fast or should I be wondering if something didn't go
as needed? I'll have a staff member able to test more in depth next week when
she returns from vacation. The only thing I didn't let complete from the
various update scripts (that started at 2.10.3) was the UPDATE
biblio.record_entry SET id = id WHERE source IS NOT NULL; line that was
updating the 901 fields (none of our libraries use these apparently) and the
consensus from the list here was that if the field isn't used there was no
issue not completing this particular field update (one that took more than
overnight to run).
Thanks again for all the information and help, looks like our upgrade time is
very manageable now with this fix.
City of Burlington
Information Systems Technician
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Kathy
Sent: Thursday, March 29, 2018 3:20 PM
Subject: Re: [OPEN-ILS-GENERAL] 3.0.2-3.0.3 Upgrade DB script takes over a week
After I responded to your e-mail, I submitted a bug with some code to make this
change to the 3.0.2-3.0.3 upgrade script. If you look at the submitted code,
you'll see exactly how you would add the lines to that particular script. You
could copy and paste the code the additions that were made to the script. If
you use git, you could also cherry-pick this patch to apply the changes.
Please note: this patch has not been reviewed by anyone yet, so it might not be
a bad idea for somebody to take a look at it and verify that it looks okay.
If you make those changes as is, there is a section at the end that reenables
the triggers before it finishes up.
On 03/29/2018 06:10 PM, Jesse McCarty wrote:
> Thanks again for the info. We are on 2.10.3 now and upgrading to 3.0.3. How
> would I go about re-enabling the triggers mentioned and is disabling them as
> simple as copy/paste the code snipped Kathy sent into the upgrade script? For
> combing the scripts, would it just be copy/paste the contents of each one
> sequentially into a single file? Do you have a workable single file upgrade
> script that you can share? Modifying these files is new to me.
> Thanks again.
> Jesse McCarty
> City of Burlington
> Information Systems Technician
> -----Original Message-----
> From: Open-ils-general
> [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf
> Of Jason Stephenson
> Sent: Wednesday, March 28, 2018 4:34 PM
> To: email@example.com
> Subject: Re: [OPEN-ILS-GENERAL] 3.0.2-3.0.3 Upgrade DB script takes
> over a week to finish
> On 03/28/2018 06:52 PM, Jesse McCarty wrote:
>> Not sure how to proceed to test getting the upgrade more manageable
>> prior to upgrading production. Obviously cannot have production down
>> or having issues for several business days.
> If you add the code to disable triggers, etc., from the 2.12.6 to 3.0 upgrade
> script, then it runs it much less time. It ran in about half an hour on my
> test system.
> BTW, are you upgrading from 2.10 to 3.0? If so, it sometimes helps to make a
> single upgrade script because some steps are occasionally repeated. In this
> particular case, the 2.12.6 to 3.0.0 upgrade script does this calculation. It
> would be wise to bundle everything up and put that update at the end so you
> only have to do it once, rather than twice.
> There's an authority ingest in that 2.12.6 to 3.0 upgrade that takes a lot
> longer on my test system.
Massachusetts Library Network Cooperative