I just experienced the same error and your posts directed me to repair ALL TABLES with
phpMyAdmin (
mysql), but I wonder WHY those entries got messed up because I just imported the whole
database from my production server to my test server. These are the tables that needed repair and I did also a myisamchk -a -S moodle/*.MYI as proposed in an official moodle doc:
moodle.mdl_backup_files
|
repair
|
info
|
Delete link points outside datafile at 268
|
moodle.mdl_backup_files
|
repair
|
warning
|
Number of rows changed from 7 to 0
|
moodle.mdl_backup_files
|
repair
|
status
|
OK
|
moodle.mdl_backup_ids
|
repair
|
info
|
Delete link points outside datafile at 3096
|
moodle.mdl_backup_ids
|
repair
|
warning
|
Number of rows changed from 71 to 0
|
moodle.mdl_backup_ids
|
repair
|
status
|
OK
|
moodle.mdl_backup_log
|
repair
|
warning
|
Number of rows changed from 5290859 to 5430903
|
moodle.mdl_cache_flags
|
repair
|
warning
|
Duplicate key for record at 68 against record at 0
|
moodle.mdl_cache_flags
|
repair
|
warning
|
Number of rows changed from 32 to 25
|
moodle.mdl_context
|
repair
|
warning
|
Number of rows changed from 94972 to 94973
|
moodle.mdl_grade_categories_history
|
repair
|
warning
|
Number of rows changed from 1775 to 1760
|
moodle.mdl_grade_grades_history
|
repair
|
warning
|
Number of rows changed from 70204 to 69377
|
moodle.mdl_grade_items_history
|
repair
|
warning
|
Number of rows changed from 3435 to 3424
|
moodle.mdl_log
|
repair
|
warning
|
Number of rows changed from 950297 to 950333
|
Rosario