On 04/25/2018 10:57 AM, Josh Stompro wrote:
> Hello, I just noticed that the auditor table trigger is disabled during
> the visibility update, so that answers that question, it is something
> that is done. But it seem like it has a very small performance impact.
> On my test system reingest of
mpro
Sent: Tuesday, April 24, 2018 9:03 AM
To: Evergreen Discussion Group
<open-ils-general@list.georgialibraries.org<mailto:open-ils-general@list.georgialibraries.org>>
Subject: Re: [OPEN-ILS-GENERAL] 3.0.2-3.0.3 Upgrade DB script takes over a week
to finish
This sender failed our
-boun...@list.georgialibraries.org] On Behalf Of Josh
Stompro
Sent: Tuesday, April 24, 2018 9:03 AM
To: Evergreen Discussion Group <open-ils-general@list.georgialibraries.org>
Subject: Re: [OPEN-ILS-GENERAL] 3.0.2-3.0.3 Upgrade DB script takes over a week
to finish
This sender failed our
org] On Behalf Of Jesse
McCarty
Sent: Wednesday, April 04, 2018 2:10 PM
To: 'Evergreen Discussion Group' <open-ils-general@list.georgialibraries.org>
Subject: Re: [OPEN-ILS-GENERAL] 3.0.2-3.0.3 Upgrade DB script takes over a week
to finish
Jason,
If the authority reingest is the one
On 04/04/2018 03:10 PM, Jesse McCarty wrote:
> If the authority reingest is the one that runs in the
> 2.12.0-2.12.1 script, it looks like between an hour/hour and a
> half on our test system this morning. I don't know how many bib
> records we have, but our Database sits about 24GB if that helps
-GENERAL] 3.0.2-3.0.3 Upgrade DB script takes over a week
to finish
On 04/04/2018 02:46 PM, Jesse McCarty wrote:
> 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/rene
On 04/04/2018 02:46 PM, Jesse McCarty wrote:
> 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
-ils-general-boun...@list.georgialibraries.org] On Behalf Of Kathy
Lussier
Sent: Thursday, March 29, 2018 3:20 PM
To: open-ils-general@list.georgialibraries.org
Subject: Re: [OPEN-ILS-GENERAL] 3.0.2-3.0.3 Upgrade DB script takes over a week
to finish
Hi Jesse,
After I responded to your e-mail, I
On 03/29/2018 06:10 PM, Jesse McCarty wrote:
> 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.
Yes, you could just combine
@list.georgialibraries.org
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
-ils-general-boun...@list.georgialibraries.org] On Behalf Of Jason
Stephenson
Sent: Wednesday, March 28, 2018 4:34 PM
To: open-ils-general@list.georgialibraries.org
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
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
Um, yeah. A hundred times, yes. Don't disable triggers that you don't
hard code in re-enabling afterwards. And then make sure you have. Twice.
If you're paranoid like I am, then three times.
Rogan Hamby, MLIS
Data and Project Analyst
Equinox Open Library Initiative
phone: 1-877-OPEN-ILS
Yes, absolutely, and please note that you do need to reenable those
triggers when the recalculation is done. :)
Kathy
On 03/23/2018 04:22 PM, Rogan Hamby wrote:
Just to follow up on this the essence of the triggers Kathy is
pointing to are triggers that mostly are there to maintain the MARC
Just to follow up on this the essence of the triggers Kathy is pointing to
are triggers that mostly are there to maintain the MARC XML or tables
derived from the MARC in various ways so when only altering the visibility
row it's probably safe to disable them but I'd be hesitant to make that as
a
Hi Jesse,
Yes, the recalculation at the end of that upgrade script is necessary.
In 3.0, we made some changes to the way catalog searches determine
record visibility, and this part of the script recalculates visibility
to fix a few search issues that were discovered in the 3.0 release.
Hi Jesse,
Am I correct in understanding that you're saying that particular update
took over a week? That seems a bit extraordinary but I have seen where
some updates like this are better off broken up into chunks or run serially
for best results. The best path will vary based on system level,
Hello Everyone,
During my last test cycle we ran into an issue upgrading from 2.10 to a newer
version with an update script that was setting the 901$sfor bib records. This
took an extended amount of time to complete. Well now, in testing our upgrade
to the 3.0 series part of the 3.0.2-3.0.3
18 matches
Mail list logo
