Following the update to Messaging Gateway (SMG) 10.7, the database error logs show a number of errors indicating that database tables have been marked as crashed and should be repaired but the SMG control center and scanning appear to be working as expected.

190417 19:27:02 [ERROR] mysqld: Table './brightmail/report_smtp_connection' is marked as crashed and should be repaired
190417 19:27:02 [Warning] Checking table:  './brightmail/report_smtp_connection'
190417 19:27:02 [ERROR] mysqld: Table './brightmail/settings_domain' is marked as crashed and should be repaired
190417 19:27:02 [Warning] Checking table:   './brightmail/settings_domain'
190417 19:27:03 [ERROR] mysqld: Table './brightmail/settings_container' is marked as crashed and should be repaired
...
190418  1:00:50 [Warning] Checking table: './brightmail/status_user_pref'
190418  1:00:50 [ERROR] mysqld: Table './brightmail/settings_alert_notification' is marked as crashed and should be repaired
190418  1:00:50 [Warning] Checking table: './brightmail/settings_alert_notification'
190418  1:00:50 [ERROR] mysqld: Table './brightmail/status' is marked as crashed and should be repaired
190418  1:00:50 [Warning] Checking table: './brightmail/status'

These are spurious error messages and can be safely ignored.

If there is concern that these may represent an actual database issue, the database integrity can be confirmed by running the cc-config database --repair command from the admin command line.

Please see How to check and repair the database in Messaging Gateway for more details