Hi, On Mon, May 19, 2014 at 10:31 AM, Jesse McCarty <[email protected]> wrote: > 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).
At this point, one should stop and figure out what the problem is before running any further schema upgrade scripts. This is because each script runs its statements in (at least) one big transaction. If any statement in the big transaction fails, all of the following ones automatically fail as well (and the work done by any prior statements in the transaction will be rolled back). Also, subsequent schema upgrade scripts assume that the previous ones have run successfully. It is impossible to tell from the screenshot what statement had failed initially. Thus, it is also helpful to redirect the output of a schema upgrade script to a file for further study, e.g., psql -U evergreen -f 2.4.3-2.5.0-upgrade-db.sql > log.apply_2.4.3-2.5.0 2>&1 & > 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. You should revert to that snapshot now and try again, this time noting the specific first error in the 2.4.3-2.5.0 step. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: [email protected] direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
