[Archivesspace_Users_Group] re-indexing errors for a 1.3.0 instance

[Brian Hoffman]

Hi,

Yes, you should definitely restore from your backup and then look into doing this through the UI or the API. Transferring top-level records via SQL is very likely going to result in corrupted data that you will have a difficult time remediating down the road.

Brian


> On Feb 18, 2016, at 2:36 PM, Douglas James Simmons <dsimmons at siu.edu> wrote:
> 
> I was asked to move all accessions data from one repository to another one. It seemed from looking at the tables like a simple sql update. 
> 
> In each accessions record in mysql, I replaced the old repo_id with the new one.
> I stopped the archivesspace server, deleted /data/solr_index/index and restarted it. The solr console reported :
> 
> [collection1] Solr index directory '/home/ambika/Documents/Feb130/archivesspace/data/solr_index/index' doesn't exist. Creating new index...
> 
> As expected. However, it now shows multiple entries like:
> 
> 13:28:36 SEVERE SolrCore java.lang.NullPointerException
> 13:28:36 SEVERE SolrDispatchFilter null:java.lang.NullPointerException
> 
> Should I restore the db from backup and try doing this a different way? Would this process involve the resequencing flag to be set at startup?
> 
> Thanks,
> 
> DOUG SIMMONS
> Assistant Manager
> 
> MORRIS LIBRARY - SYSTEMS
> MAIL CODE 6632
> SOUTHERN ILLINOIS UNIVERSITY
> 605 AGRICULTURE DRIVE
> CARBONDALE, ILLINOIS  62901
> 
> dsimmons at siu.edu
> P: 618/453-1026
> F: 618/453-3440
> LIB.SIU.EDU
> 
> 
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group