Bug #61522 Advice for 'No Value Set For myisam-recover' is not correct
Submitted: 15 Jun 2011 10:15 Modified: 1 Aug 2011 18:40
Reporter: Daniël van Eeden Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Advisors/Rules Severity:S3 (Non-critical)
Version:2.3.4 OS:Any
Assigned to: CPU Architecture:Any

[15 Jun 2011 10:15] Daniël van Eeden
Description:
The "No Value Set For myisam-recover (v1.8)" rule has some issues:

1. myisam-recover was renamed to myisam-recover-options as of MySQL 5.5.3

The recommended action is:
Set myisam-recover=FORCE,BACKUP

This looks like a SET GLOBAL action, but it isn't.

How to repeat:
See Description

Suggested fix:
Set the recommended action to

before 5.5.3:
Set myisam-recover='FORCE,BACKUP' in your my.cnf/my.ini and restart MySQL.

5.5.3 and newer:
Set myisam-recover-options='FORCE,BACKUP' in your my.cnf/my.ini and restart MySQL.
[15 Jun 2011 10:16] Daniël van Eeden
Please consider Bug #36577 to be added as documentation for this rule.
[15 Jun 2011 10:30] Valeriy Kravchuk
Thank you for the problem report.
[1 Aug 2011 18:40] John Russell
Added to 2.3.6 change log:

The advice for the No Value Set For myisam-recover rule was changed
to reflect the new name myisam-recover-options, which applies to
MySQL 5.5.3 and higher.