Re: [OPEN-ILS-GENERAL] Error when upgrading from 2.9.3 to 2.10.0

[Vaclav Jansa]

Hi Bill,
thanks for confirmation. Our testing environment is currently fully updated
from 2.8.2 to 2.10.2. Overall DB update process is without error.

Best regards

Vaclav Jansa

On Sun, May 1, 2016 at 5:17 PM, Bill Erickson  wrote:

> Hi Linda,
>
> On Sat, Apr 30, 2016 at 2:41 PM, Linda Jansova  wrote:
> 
>
>> This time we experienced the same error (but involving a different copy
>> of the same serial):
>>
>> psql:version-upgrade/2.9.3-2.10.0-upgrade-db.sql:4578: ERROR: insert or
>> update on table "usr_circ_history" violates foreign key constraint
>> "usr_circ_history_target_copy_fkey"
>> DETAIL:  Key (target_copy)=(57113) is not present in table "copy".
>>
>> Could it be related to the bug fixed in 2.10.2 as described at
>> https://evergreen-ils.org/documentation/release/RELEASE_NOTES_2_10.html#_evergreen_2_10_2
>> (Fixes a bug where serials checkouts failed for users that track
>> circulation history.)?
>>
>
> That's the one.  See more here:
> https://bugs.launchpad.net/evergreen/+bug/1564079
>
>
>> If so, what should we do to get rid of the error in our case when 2.10.2
>> has not been reached yet (in the upgrade process)?
>>
>
> The 2.10.2 fix includes a patch to the 2.9.3-2.10.0 upgrade script.
> You'll want to get the 2.10.2 code and use it to perform your 2.10.0
> upgrade (and ideally continue on to 2.10.2 to pick up more bug fixes).
>
> Hope this helps,
>
> --bill
>
>

Re: [OPEN-ILS-GENERAL] Error when upgrading from 2.9.3 to 2.10.0

[Bill Erickson]

Hi Linda,

On Sat, Apr 30, 2016 at 2:41 PM, Linda Jansova  wrote:


> This time we experienced the same error (but involving a different copy of
> the same serial):
>
> psql:version-upgrade/2.9.3-2.10.0-upgrade-db.sql:4578: ERROR: insert or
> update on table "usr_circ_history" violates foreign key constraint
> "usr_circ_history_target_copy_fkey"
> DETAIL:  Key (target_copy)=(57113) is not present in table "copy".
>
> Could it be related to the bug fixed in 2.10.2 as described at
> https://evergreen-ils.org/documentation/release/RELEASE_NOTES_2_10.html#_evergreen_2_10_2
> (Fixes a bug where serials checkouts failed for users that track
> circulation history.)?
>

That's the one.  See more here:
https://bugs.launchpad.net/evergreen/+bug/1564079


> If so, what should we do to get rid of the error in our case when 2.10.2
> has not been reached yet (in the upgrade process)?
>

The 2.10.2 fix includes a patch to the 2.9.3-2.10.0 upgrade script.  You'll
want to get the 2.10.2 code and use it to perform your 2.10.0 upgrade (and
ideally continue on to 2.10.2 to pick up more bug fixes).

Hope this helps,

--bill

[OPEN-ILS-GENERAL] Error when upgrading from 2.9.3 to 2.10.0

[Linda Jansova]

Hi,

We have been trying to upgrade Jabok Evergreen database from 2.8.2. We 
have successfully reached 2.9.3. When upgrading from 2.9.3 to 2.10.0, 
the following error has occured:


psql:version-upgrade/2.9.3-2.10.0-upgrade-db.sql:4578: ERROR: insert or 
update on table "usr_circ_history" violates foreign key constraint 
"usr_circ_history_target_copy_fkey"

DETAIL:  Key (target_copy)=(52644) is not present in table "copy".

The copy in question is a copy attached to a bib record representing a 
serial (http://www.jabok.cuni.cz/eg/opac/record/2154?locg=102). We tried 
to check it in and out and then we used the updated 2.8.2 database for 
another upgrade attempt.


This time we experienced the same error (but involving a different copy 
of the same serial):


psql:version-upgrade/2.9.3-2.10.0-upgrade-db.sql:4578: ERROR: insert or 
update on table "usr_circ_history" violates foreign key constraint 
"usr_circ_history_target_copy_fkey"

DETAIL:  Key (target_copy)=(57113) is not present in table "copy".

Could it be related to the bug fixed in 2.10.2 as described at 
https://evergreen-ils.org/documentation/release/RELEASE_NOTES_2_10.html#_evergreen_2_10_2 
(Fixes a bug where serials checkouts failed for users that track 
circulation history.)?


If so, what should we do to get rid of the error in our case when 2.10.2 
has not been reached yet (in the upgrade process)?


If not, any ideas what could have gone wrong?

Thank you in advance for any hints!

Linda