Hello, So the upgrade scripts are intended to be done sequentially as written due to certain limitations in the build process of Evergreen currently (this is still under community discussion). So unfortunately, if you're already on 2.6.4, then you may have some small edits necessary to perform the upgrade from 2.6 series to 2.7 series. If I recall correctly, you should be able to the run the 2.6.3-2.7 script without problems, but when you try to do the 2.7.0-2.7.1 script, it might cause conflicts because some of the changes in the 2.7.0-2.7.1 might already have been done during the 2.6.3-2.6.4 script.
In situations like these, most system administrators will manually compare the differences between the conflicting upgrade scripts and make edits to the files as necessary to "skip" anything that's already been done and doesn't need to be re-done. Long-term, the developer community needs to complete discussions about how to make the database upgrade process cleaner between major version shifts, but this is the present reality. -- Ben On Sat, Mar 7, 2015 at 9:23 AM, Jayaraj JR <[email protected]> wrote: > Hello, > > We are currently working on Evergreen version 2.6.4. We would like to > upgrade to 2.7 series. But the sql script found for upgrade is from 2.6.3 to > 2.7 series. What script is to be done for upgrading from 2.6.4 or higher > version to 2.7 series. > > Thanking You > > -- > Jayaraj J R > Library Information Assistant > IISER Thiruvananthapuram -- Benjamin Shum Evergreen Systems Manager Bibliomation, Inc. 24 Wooster Ave. Waterbury, CT 06708 203-577-4070, ext. 113
