Tatua onyo: hitilafu ya hifadhidata Hesabu ya safu wima ya mysql.proc si sahihi.

Kwa kweli, ikiwa unatumiaphpMyAdmin, huwezi kupata kosa tatizo liko wapi?

• Shida ni kwa sababu umeboresha MariaDB auHifadhidata ya MySQLtoleo.
• Boresha MariaDB auMySQLBaada ya toleo la hifadhidata, miundo ya data haitumikimysql_upgradeamri ya kukamilisha sasisho la kuboresha.
• Baadaye, wakati wa uendeshaji wa hifadhidata ya MySQL, ujumbe wa makosa unaweza kuonyeshwa.

Plugin ya WordPressWakati wa mchakato wa kuhifadhi nakala kiotomatiki, hitilafu ifuatayo ilitokea ▼

Onyo: Hitilafu ya hifadhidata Hesabu ya safu wima ya mysql.proc si sahihi. Inatarajiwa 21, ilipatikana 20. Iliundwa na MariaDB 50560, sasa inaendesha 100406. Tafadhali tumia mysql_upgrade kurekebisha hitilafu hii Hoja SHOW FUNCTION STATUS

• mysql.proc Hili ni jedwali la mfumo katika 5.1 ambalo hurekodi taarifa kuhusu taratibu au vitendakazi vilivyohifadhiwa.

Jinsi ya kurekebisha onyo: Hitilafu ya Hifadhidata Hesabu ya safu wima ya mysql.proc si sahihi?

Ifuatayo niChen Weiliangsuluhisho la kumbukumbu.

Sura ya 1:Mazoezi salama ni kutupa au kuhifadhi nakala rudufu kwanza:

mysqldump -uroot -p123456 --quick --master-data=1 --all-databases --flush-logs --lock-tables >

• Tafadhali badilisha "123456" iliyo hapo juu kuwa nenosiri lako la msingi la MySQL.

Sura ya 2:tumia zifuatazomysql_upgrade amri ya kutatua

mysql_upgrade -u root --datadir=/var/lib/mysql/ --basedir=/ --password=123456

Ifuatayo ni mchakato wa operesheni ya onyesho la SSH▼

[root@db lib]# mysql_upgrade -u root -p123456 -hdb --datadir=/var/lib/mysql/ --basedir=/
mysql_upgrade: the '--datadir' option is always ignored
mysql_upgrade: the '--basedir' option is always ignored
Looking for 'mysql' as: mysql
Looking for 'mysqlcheck' as: mysqlcheck
Running 'mysqlcheck' with connection arguments: '--host=db'
Running 'mysqlcheck' with connection arguments: '--host=db'
mysql.columns_priv                                OK
mysql.db                                          OK
mysql.event                                       OK
mysql.func                                        OK
mysql.general_log
Error   : You can't use locks with log tables.
status  : 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.servers                                     OK
mysql.slow_log
Error   : You can't use locks with log tables.
status  : OK
mysql.student                                     OK
mysql.t1                                          OK
mysql.t2                                          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
................................................
test.newuser                                      OK
test.usertag                                      OK
Running 'mysql_fix_privilege_tables'...
WARNING: NULL values of the 'character_set_client' column ('mysql.proc' table) have been updated with a default value (latin1). Please verify if necessary.
WARNING: NULL values of the 'collation_connection' column ('mysql.proc' table) have been updated with a default value (latin1_swedish_ci). Please verify if necessary.
WARNING: NULL values of the 'db_collation' column ('mysql.proc' table) have been updated with default values. Please verify if necessary.
OK
[root@db lib]#

Kuna suluhisho zaidi kwa shida za hifadhidata ya MySQL hapa chini▼

Jinsi ya kusasisha/kusasisha hadi MariaDB7 kwa VestaCP/CWP/CentOS 10.10.2?

Mafunzo haya yatakuongoza jinsi ya kusasisha/kusakinisha MariaDB hadi toleo jipya zaidi la Mariadb 7 kwenye Centos 10.10.2.Mafunzo haya pia yanafanya kazi na CWP na VestaCP au paneli nyingine yoyote inayolingana ya udhibiti wa seva ya VPS. MariaDB 10.10.2 ni thabiti sana sasa...

Jinsi ya kurekebisha mandhari ya WordPress {{haijulikani}} suala la oembed_cache?

Je, mada inayoanza hutatua vipi {{haijulikani}} akiba_ya_embed?Kuna watu wapya wa media ambao wamejifunza kuunda tovuti ya WordPress na kutumia mada ya kuanza kwa robin.Imepatikana {{haijulikani}}, makosa ya oembed_cache Wakati phpMyAdmin ilipokagua hifadhidata ya MySQL, ilibainika kuwa...

kosa la jedwali la data la mysqld limetiwa alama kama suluhu ya kuharibika na ya mwisho (otomatiki?) ya ukarabati

Hitilafu ya jedwali la data ya mysqld imealamishwa kama suluhu la kuharibika na la mwisho (otomatiki?) la kukarabati Makala haya yatakujulisha hitilafu tunaporekebisha jedwali: Jedwali \'./db_name/table_name\' limetiwa alama kuwa limeanguka na la mwisho...

Onyo la MySQL: Imepatikana safu mlalo ambapo safu wima ya_auto_increment

Ikiwa msimamizi wa tovuti ya e-commerce ana ruhusa za kutosha, hifadhidata ya MySQL inaweza kudumishwa kupitia paneli ya udhibiti ya hifadhidata ya phpMyAdmin.Matengenezo ya jedwali "uchambuzi" au "hundi" yanaweza kufanywa kwenye hifadhidata ya WordPress makosa yanapotokea kwenye hifadhidata.Lakini labda basi ...