mysql刪除用戶錯(cuò)誤怎么辦

本文主要給大家簡(jiǎn)單講講mysql刪除用戶錯(cuò)誤怎么辦，相關(guān)專業(yè)術(shù)語(yǔ)大家可以上網(wǎng)查查或者找一些相關(guān)書(shū)籍補(bǔ)充一下，這里就不涉獵了，我們就直奔主題吧，希望mysql刪除用戶錯(cuò)誤怎么辦這篇文章可以給大家?guī)?lái)一些實(shí)際幫助。

1、錯(cuò)誤提示

ERROR 1558 (HY000): Column count of mysql.user is wrong. Expected 43, found 42. Created with MySQL 50560, now running 50645. Please use mysql_upgrade to fix this error.

意思是數(shù)據(jù)庫(kù)以前做過(guò)升級(jí)但是數(shù)據(jù)庫(kù)里的mysql庫(kù)沒(méi)有升級(jí)導(dǎo)致的權(quán)限混亂
2、解決辦法
升級(jí)數(shù)據(jù)庫(kù)使用命令
mysql_upgrade -uroot -p ‘密碼’

Enter password:
Looking for 'mysql' as: mysql
Looking for 'mysqlcheck' as: mysqlcheck
Running 'mysqlcheck with default connection arguments
Warning: Using a password on the command line interface can be insecure.
Running 'mysqlcheck with default connection arguments
Warning: Using a password on the command line interface can be insecure.
mysql.columns_priv                                 OK
mysql.db                                           OK
mysql.event                                        OK
mysql.func                                         OK
mysql.general_log                                  OK
mysql.help_category                                OK
mysql.help_keyword                                 OK
mysql.help_relation                                OK
mysql.help_topic                                   OK
mysql.host                                         OK
mysql.ndb_binlog_index                             OK
mysql.plugin                                       OK
mysql.proc                                         OK
mysql.procs_priv                                   OK
mysql.proxies_priv                                 OK
mysql.servers                                      OK
mysql.slow_log                                     OK
mysql.tables_priv                                  OK
mysql.time_zone                                    OK
mysql.time_zone_leap_second                        OK
mysql.time_zone_name                               OK
mysql.time_zone_transition                         OK
mysql.time_zone_transition_type                    OK
mysql.user                                         OK
Running 'mysql_fix_privilege_tables'...
Warning: Using a password on the command line interface can be insecure.
Running 'mysqlcheck with default connection arguments
Warning: Using a password on the command line interface can be insecure.
Running 'mysqlcheck with default connection arguments
Warning: Using a password on the command line interface can be insecure.
mysqlcheck: Got error: 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '.2_b_cloud_provider  FOR UPGRADE' at line 1 when executing 'CHECK TABLE ...  FOR UPGRADE'
cb-fetch-data-pre.cron_task                        OK
cb-fetch-data-pre.cron_task_result                 OK
cb-fetch-data-pre.xxl_job_qrtz_blob_triggers       OK
cb-fetch-data-pre.xxl_job_qrtz_calendars           OK
cb-fetch-data-pre.xxl_job_qrtz_cron_triggers       OK
cb-fetch-data-pre.xxl_job_qrtz_fired_triggers      OK
cb-fetch-data-pre.xxl_job_qrtz_job_details         OK
cb-fetch-data-pre.xxl_job_qrtz_locks               OK
cb-fetch-data-pre.xxl_job_qrtz_paused_trigger_grps OK
cb-fetch-data-pre.xxl_job_qrtz_scheduler_state     OK
cb-fetch-data-pre.xxl_job_qrtz_simple_triggers     OK
cb-fetch-data-pre.xxl_job_qrtz_simprop_triggers    OK
cb-fetch-data-pre.xxl_job_qrtz_trigger_group       OK
cb-fetch-data-pre.xxl_job_qrtz_trigger_info        OK
cb-fetch-data-pre.xxl_job_qrtz_trigger_log         OK
cb-fetch-data-pre.xxl_job_qrtz_trigger_logglue     OK
cb-fetch-data-pre.xxl_job_qrtz_trigger_registry    OK
cb-fetch-data-pre.xxl_job_qrtz_triggers            OK
cloudbest-index-point-pre.b_cloud_provider         OK
cloudbest-index-point-pre.cron_task                OK
cloudbest-index-point-pre.cron_task_result_2019_09 OK
cloudbest-index-point-pre.cron_task_result_2019_10 OK
cloudbest-index-point-pre.cron_task_result_2019_11 OK
cloudbest-index-point-pre.cron_task_result_2019_12 OK
cloudbest-index-point-pre.cron_task_result_2020_01 OK
cloudbest-index-point-pre.cron_task_result_2020_02 OK
cloudbest-index-point-pre.cron_task_result_2020_03 OK
cloudbest-index-point-pre.cron_task_result_2020_04 OK
cloudbest-index-point-pre.cron_task_result_2020_05 OK
cloudbest-index-point-pre.cron_task_result_2020_06 OK
cloudbest-index-point-pre.cron_task_result_2020_07 OK
cloudbest-index-point-pre.cron_task_result_2020_08 OK
cloudbest-index-point-pre.cron_task_result_2020_09 OK
cloudbest-index-point-pre.i_index_rank             OK
cloudbest-index-point-pre.i_instances              OK
cloudbest-index-point-pre.i_model                  OK
cloudbest-index-point-pre.i_model_price            OK
cloudbest-index-point-pre.i_performance_reportes   OK
cloudbest-index-point-pre.i_region                 OK
cloudbest-index-point-pre.statistic_index          OK
cloudbest-market.ddos_accounts                     OK
cloudbest-market.ddos_custom                       OK
cloudbest-market.ddos_shield_info                  OK
cloudbest-market.ddos_task_queue                   OK
cloudbest-order.cb_order                           OK
FATAL ERROR: Error during call to mysql_check for upgrading the tables names on all db(s) except mysql

最后一個(gè)錯(cuò)誤是因?yàn)槠渌臄?shù)據(jù)庫(kù)表沒(méi)法更改，這個(gè)不會(huì)影響。 到這算是解決上面的錯(cuò)誤。權(quán)限可以正常使用了

mysql刪除用戶錯(cuò)誤怎么辦就先給大家講到這里，對(duì)于其它相關(guān)問(wèn)題大家想要了解的可以持續(xù)關(guān)注我們的行業(yè)資訊。我們的板塊內(nèi)容每天都會(huì)捕捉一些行業(yè)新聞及專業(yè)知識(shí)分享給大家的。