Thank you for your recommendations. I've imported the database from our production to dev and changed the schema version as Megan had suggested, fortunately in this case it resolved the issue and allowed archivesspace to run as expected. Our production environment is running on docker, but I doubt that would impact the schema version. I completely understand what you're saying Blake and normally I would not want to mess with the schema version, however in this instance since the schema version seems to be completely off and not match any other version, it may be needed in order to get the DB in sync with the current version it should be on. I'm crossing my fingers that moving forward it won't mess with things. In order to be sure, is there a way to migrate data manually to ensure that schema matches and all the data gets migrated?
On Fri, May 14, 2021 at 10:50 AM Blake Carver <[email protected]> wrote: > I wouldn't recommend changing the schema_info, this can put you in a > really bad place. > > Your error: > ""The schema info version should be 120 for ArchivesSpace version > v2.6.0. However, your schema info version is set at 122" > > Every release of ArchivesSpace has a schema number . All recent releases > have the schema number listed on the release notes. So the latest > version 3.0 is 147, and the previous release 2.8.1 is 138 and so on down > the line. Those numbers are important and are set by the code. That's what > the ArchivesSpace code looks at to know that the MySQL Database lines up > with what it expects. Each version expects certain tables/rows/columns to > be there and in a certain format. As ArchivesSpace starts each time it > checks that shema_info number, and if it's wrong, it fails. So > ArchivesSpace 3.0 starts up and says "Hey MySQL what ya got there?" and > MySQL says "147" and ArchivesSpace says "Groovy, that's what I need to > run" and then they high five and start getting down to business. If > ArchivesSpace starts up and says "Hey MySQL, what ya got there?" and it > says "122" and ArchivesSpace was expecting 120, ArchivesSpace says "That > ain't right, I can't work with that" and starts telling you all about it in > archivesspace.out. > > So your version of ArchivesSpace is expecting schema_info to be 120 but > it's actually 122, which is larger number and therefore a newer release. > > Looking back at the old releases, schema_info on 2.7 is 126 and the > release before that is 120 is 2.6.0, which means 122 is... I don't know > what. > > I'm not sure what to recommend here. From what I can see there is not any > release that should have a schema version of 122, so I don't know how that > got set like that. > > ------------------------------ > *From:* [email protected] < > [email protected]> on behalf of > Schanz, Megan <[email protected]> > *Sent:* Thursday, May 13, 2021 9:35 AM > *To:* Archivesspace Users Group < > [email protected]> > *Subject:* Re: [Archivesspace_Users_Group] Database Migration Error on AS > 2.6.0 > > That *should* only happen when the setup-database script was run for a > later version of ArchivesSpace. But if that isn't the case, you could try > manually reverting the schema number in the database to see if that > resolves your issue. > > update schema_info set version = 120; > > > I've had to do that at one point in the past, but I can't recall what > circumstances led to me having to do that. > > - Megan > > _____________________________________ > > Megan Schanz > Application Developer & Systems Administrator > Michigan State University Libraries > ------------------------------ > *From:* [email protected] < > [email protected]> on behalf of > Ludwig Possie <[email protected]> > *Sent:* Wednesday, May 12, 2021 7:56 PM > *To:* Archivesspace Users Group < > [email protected]> > *Subject:* [Archivesspace_Users_Group] Database Migration Error on AS > 2.6.0 > > I'm in the process of moving our current version of Archivesspace 2.6.0 to > a new server running Ubuntu 20.04. I've installed Java 1.8, MySQL 8.0.25 > and mysql connector 8.0.25 on the new server. > > I successfully got Archivesspace 2.6.0 running on MySQL (New blank > database) on the new server. When I import our current production database > and run the setup-database.sh script I get no error and an 'All Done' > message at the end. However when I attempt to run archivesspace.sh I get a > Database Migration Error, with the following recommendation, "The schema > info version should be 120 for ArchivesSpace version v2.6.0. However, your > schema info version is set at 122 > Please ensure your migrations have been run and completed by using the > setup-database script." > I've ran the script various times but I keep getting the same results. > Has anyone experienced an issue like this? Please advise. Thank you. > > -- > Ludwig Possié > Systems Admin > Stewart Library > Weber State University > 801-626-8093 > _______________________________________________ > Archivesspace_Users_Group mailing list > [email protected] > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Ludwig Possié Systems Admin Stewart Library Weber State University 801-626-8093
_______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
