[Archivesspace_Users_Group] database integrity constraint conflict

[brian]

Hi Noah,

Would it be possible to email me directly a copy of your database? Ideally, a copy of your database from before the migration would be helpful too.

Brian


Sent from my T-Mobile 4G LTE Device

<div>-------- Original message --------</div><div>From: Noah Huffman <noah.huffman at duke.edu> </div><div>Date:09/14/2015  4:43 PM  (GMT-05:00) </div><div>To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org> </div><div>Cc:  </div><div>Subject: Re: [Archivesspace_Users_Group] database integrity constraint conflict </div><div>
</div>Hi all,
 
I’m still running into this database integrity constraint conflict error when I try to save archival objects that have been transferred from other resource records.  I’m currently running v1.3.0.
 
translation missing: en.no key - translation missing: en.validation_errors.database_integrity_constraint_conflict__java__commysqljdbcexceptionsjdbc4__mysqlintegrityconstraintviolationexception__duplicate_entry__722199 at archival_object-8__for_key__uniq_ao_pos_
 
Maureen reported this issue back in July, but I’m wondering if there are any other fixes outside of stopping ASpace and resequencing on startup?
 
I have a few hundred sibling archival objects and when I try to edit any of them the “duplicate entry” cited in the error message is always the same number (722199 in this case).  That number refers to the parent archival object of all the affected child objects.
 
-Noah
 
================
Noah Huffman
Archivist for Metadata and Encoding
David M. Rubenstein Rare Book & Manuscript Library
Duke University
 
 
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Galligan, Patrick
Sent: Monday, July 20, 2015 9:17 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] database integrity constraint conflict
 
Maureen,
 
We essentially found out that there were only two ways to fix the record save error caused by transferring components in 1.1.2:
 
·         Export the EAD finding aid and re-import (not ideal because you’d have to recreate some links/connections)
·         Stop the AS instance and then restart it with the resequence on startup option enabled
 
The first option wasn’t viable to us, so anytime someone transfers components, we have to resequence over the weekend. It’s a big hassle and not a long-term solution.
 
We haven’t run into this problem with our updated versions that we’re running on the dev though.
 
Patrick Galligan
Rockefeller Archive Center
Assistant Digital Archivist
914-366-6386
 
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Callahan, Maureen
Sent: Friday, July 17, 2015 4:46 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] database integrity constraint conflict
 
Hi Chris and Patrick,
 
We’re on a special branched version of 1.1.2 that HM modified for us while we wait for the container management plug-in to be integrated into the core code. The record was transferred two days ago.
 
Patrick, what do you mean when you say that you resequence every time you transfer components?
 
Thank you both for your insights!
 
Maureen
 
Maureen Callahan
Archivist, Metadata Specialist
Manuscripts & Archives
Yale University Library
maureen.callahan at yale.edu
203.432.3627
 
Webpage: web.library.yale.edu/mssa
Collections: drs.library.yale.edu
 
From: archivesspace_users_group-bounces at lyralists.lyrasis.org  [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick
Sent: Friday, July 17, 2015 4:23 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] database integrity constraint conflict
 
Hi Maureen,
 
Which version are you all using? Was this record transferred recently?
 
b,chris.
 
Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048
http://archivesspace.org/
 

From: archivesspace_users_group-bounces at lyralists.lyrasis.org  <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Galligan, Patrick <PGalligan at rockarch.org>
Sent: Friday, July 17, 2015 9:33 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] database integrity constraint conflict
 
Maureen,
 
I’m just chiming in to say this has also been happening at the RAC. The only fix we’ve found is to resequence each time we transfer components, which is obviously not ideal.
 
We are not on the newest version of AS though.
 
Patrick Galligan
Rockefeller Archive Center
Assistant Digital Archivist
914-366-6386
 
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Callahan, Maureen
Sent: Friday, July 17, 2015 1:45 PM
To: 'archivesspace_users_group at lyralists.lyrasis.org'
Cc: Connolly, Christine; Caldera, Mary
Subject: [Archivesspace_Users_Group] database integrity constraint conflict
 
Hey folks,
 
I’m getting this error:
en.validation_errors.database_integrity_constraint_conflict__java__commysqljdbcexceptionsjdbc4__mysqlintegrityconstraintviolationexception__duplicate_entry__2101963 at archival_object-4__for_key__uniq_ao_pos_
 
when I try to save archival objects that had been transferred from another resource record. For instance, this archival object is number 2102081 but it looks like it’s telling me that it conflicts with archival object 2101963. I’m happy to do something to change one of the sets of records, but it would be helpful to know what that change needs to look like and how I can avoid this constraint in the future.
 
Thanks,
Maureen
 
Maureen Callahan
Archivist, Metadata Specialist
Manuscripts & Archives
Yale University Library
maureen.callahan at yale.edu
203.432.3627
 
Webpage: web.library.yale.edu/mssa
Collections: drs.library.yale.edu
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150914/b92c9287/attachment.html>