Upgrading from 3.1

From EPrints Documentation
Revision as of 13:08, 26 April 2012 by Tmb (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

The following is advice from the EPrints Services team, after carrying out many upgrades to 3.2. Please note that you follow this advice at your own risk.

Avoiding subject__index_grep key length error

When converting subject__index_grep and subject__rindex to utf8, bin/epadmin upgrade will generate an error:

DBD::mysql::db do failed: Specified key was too long; max key length is 1000 bytes at /opt/eprints3/perl_lib/EPrints/Database.pm line 3213, <STDIN> line 1.

To avoid this error drop the tables before running bin/epadmin upgrade:

drop table subject__index_grep
drop table subject__rindex

Then reindex when bin/epadmin upgrade has completed:

bin/epadmin reindex ARCHIVEID subject

Minimising downtime

Whilst bin/epadmin upgrade is running, your repository will be offline.

bin/epadmin upgrade converts all database tables to the utf8 charset. If you have a large repository this process can take a long time. However some of the tables are volatile (ie. the data can be generated) so you can reduce downtime by clearing these tables beforehand, and then regenerating the content afterwards (whilst your repository is back online).

We have found that the following tables are good candidates:


Clear these tables before running bin/epadmin upgrade:

DELETE FROM eprint__rindex;
DELETE FROM eprint__ordervalues_en;

After running bin/epadmin upgrade and getting your repository back online:

bin/epadmin reindex ARCHIVEID eprint
bin/epadmin reorder ARCHIVEID eprint

Your search won't be at full capacity until the indexes are fully regenerated, but we have found that getting the repository back online is more desirable so worth the trade off.