[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[EP-tech] Re: [solved] advanced search without subject list (3.3.13)



> It's possible those errors occurred due to tables being missing.  What
> happens if you run epadmin update again?  What errors do you get?
The output shortens (but keeps its length for additional executions) to

Starting EPrints Repository.
Connecting to DB ... Database execute debug: SET NAMES 'utf8'
done.
Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
Database execute debug: 
Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
Database execute debug: 
Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
Database execute debug: 
Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
Database execute debug: 
Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
Database execute debug: 
Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
Database execute debug: 
Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
Database execute debug: 
Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
Database execute debug: 
Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
Database execute debug: 
Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
Database execute debug: 
Use of uninitialized value $sql in concatenation (.) or string at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3208, <DATA> line 960.
Database execute debug: 
Database execute debug: ALTER TABLE `subject__rindex` CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin
DBD::mysql::db do failed: Specified key was too long; max key length is 1000 bytes at /opt/eprints3/eprints-3.3.13/bin/../perl_lib/EPrints/Database.pm line 3052, <DATA> line 960.
SQL ERROR (do): ALTER TABLE `subject__rindex` CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin
SQL ERROR (do): Specified key was too long; max key length is 1000 bytes (#1071)
Fixed subject__rindex.field collation
0 datasets added
0 fields added
Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='savedsearchid'
Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='documentid'
Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='fileid'
Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='userid'
Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='eprintid'
Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='requestid'
Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='historyid'
Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='accessid'
Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='messageid'
Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='importid'
Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='cachemapid'
Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='tripleid'
Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='bookmarkid'
Database execute debug: SELECT 1 FROM `counters` WHERE `countername`='metafieldid'
0 counters were added

> Are there any customisations in your code-base?
we added some fields in the scheme, but didn't get into trouble up to 13.3.12 ...

> Which version were you upgrading from?
But obviously due to some missing (and silently failing) perl modules after incomplete update of all of them,
we get a corrupt data base :(

How to fix the SQL ERRORs?

Many thanks
Thomas