[OPEN-ILS-DEV] Errors Upgrading Evergreen 2.4.4 to 2.5.4

[Dan Wells]

Hello Jesse,

You want to comment everything from the failing "SELECT evergreen.upgrade_deps_block_check..." up to (but not including) the next " SELECT evergreen.upgrade_deps_block_check...".  You may need to do this several times before you find them all.

Those checks exist precisely to cause the upgrade to fail if a piece of the script has already been applied.  Commenting out only these check lines *might* work (depending on the content of that section), but is certainly not recommended.

Also, the root of this problem is that there is no supported way to upgrade from 2.4.4+ to 2.5.0.  This is a known issue with no simple fix, other than to say the 2.x maintainer needs to make a new upgrade script for every 2.(x-1) release.  I am not outright opposed to that, but up to this point nobody has argued that the benefits would justify the cost.

Thanks,
Dan


Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

-----Original Message-----
From: open-ils-dev-bounces at list.georgialibraries.org [mailto:open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of Jesse McCarty
Sent: Tuesday, May 20, 2014 11:19 AM
To: 'Evergreen Development Discussion List'
Subject: Re: [OPEN-ILS-DEV] Errors Upgrading Evergreen 2.4.4 to 2.5.4

Thanks Martha,

How much is there to comment out? Is it just the single line(s) that reads:

SELECT evergreen.upgrade_deps_block_check('0841', :eg_version); SELECT evergreen.upgrade_deps_block_check('0842', :eg_version);

Thanks again,

Jesse McCarty
City of Burlington
IT Technical Assistant

-----Original Message-----
From: open-ils-dev-bounces at list.georgialibraries.org [mailto:open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of Martha Driscoll
Sent: Monday, May 19, 2014 2:30 PM
To: open-ils-dev at list.georgialibraries.org
Subject: Re: [OPEN-ILS-DEV] Errors Upgrading Evergreen 2.4.4 to 2.5.4

Jesse,
I found that upgrade scripts 0841 and 0842 which are contained in the
2.4.3-2.5.0 upgrade script were already applied in the upgrade to 2.4.4. 
  I commented out those two parts of the upgrade script.

Martha Driscoll
Systems Manager
North of Boston Library Exchange
Danvers, Massachusetts
www.noblenet.org

On 5/19/2014 1:31 PM, Jesse McCarty wrote:
> Hi,
>
>
> I am going through the process of upgrading our 2.4.4 installation of 
> Evergreen to 2.5.4. Currently running through the install on a test 
> server (which is an exact copy of our production server as it sat 
> several weeks ago, albeit with a different IP Address).
>
> After upgrading OpenSRF to 2.2.2 and the Evergreen code, I started 
> getting errors when running the update DB scripts. I started by 
> running the 2.4.3-2.5.0-upgrade-db.sql (There was no
> 2.4.4-2.5.0-upgrade-db.sql) with more errors that could fit on a 
> screen shot, then ran into additional errors on different update scripts:
>
> For 2.4.3-2.5.0-upgrade-db.sql errors see attached 243-250Error.JPG 
> (this also shows the reingest records script information, which I ran 
> after running all the DB upgrade scripts).
>
> For 2.5.0-2.5.1-upgrade-db.sql errors see attached 250-251Error.JPG
>
> No errors where reported when running the 2.5.1-2.5.2-upgrade-db.sql script.
>
> For 2.5.2-2.5.3-upgrade-db.sql errors see attached 252-253Error.JPG
>
> For 2.5.3-2.5.4-upgrade-db.sql errors see attached 253-254Error.JPG
>
>
> After starting Evergreen, I can connect via the web browser and login 
> to my account with no issues, searching the catalog produces and 
> internal server error. I can also connect to the staff client and 
> register the workstation and test/add SSL exemption with no issues.
> Once the work station is registered I get a Network error (can ping 
> the server from the workstation connecting) show in the attached 
> StaffClientError.JPG file. If I close that error the Staff Client 
> loads and then I can browse patrons and interact with the Server OK.
>
> I have a snapshot of the VM I can revert to that was taken prior to 
> any update scripts running against the DB to work through the process 
> again for further testing if needed.
>
> Thanks,
>
>
> Jesse McCarty
>
> City of Burlington
>
> IT Technical Assistant
>