Viewing File: /usr/share/mysql/japanese/errmsg.sys

þþ Dhd£ñZœŠÏ	R å8…Ø+…ÅTŸô?k“Îl¡×D	¥	Ò	P
Õ
RnÁý

í
!@mŸÌïP…¿ô7e’ŒìIhœò#a«ò"Œ‡Ðñ7X Ê?ž'±ç)KBšþ0v™Ò÷9…Î]Ž€“Å
RƒŽâ>p‘œ   )!Õ!3"«"Û"#P#‰#è#-$`$á$?%Š%-&|&«&b' 'Ó'(3(©(ú(v)*z*È*÷*e+­+2,v,–,ú,E-v-Ÿ-Ö-.J..Ç.
/Q/²/0j0Ž0è0i1Ž12„2¡2ì2P3Ã34&4r4Ÿ4ð4$5Z556n6Í67;77Ä788Ÿ8ý8S9Ž9‚:;³;Q<ß<I=œ=ß=L>q>¥>?y?•?Û?S@Ï@A4AtA·AâABABsB§BCoC§CD}D×D1EoE¬EÞE.FaF¯FG‰G±GßGHKHƒHóH9IpI IÌIôI/JˆJ6K}K¿KêKLžL×LgM•M¶MûMgNßN
OPOšOéOP‹PàPQ–Q¶Q­RSÿSWTRU»UâUV€V¿VôVœWÒW6X…XôXsYÆY
Z’ZÃZ[B[‚[«[Ý[\F\r\§\Œ\Ñ\æ\ý\]/]J]q]­]Ò]ù][^Ó^ó^0_H_g_ˆ_ª_Ë_à_÷_
`"`F`z`’`©`Á`Ö`ì`	a9aa¬aÎaöa#bZb”bÖbcUcqc“cÈcícdPd‘dßd'e©eåef.fEftf£fÄfñfÿf@gpg¥gËgh3hihŽh¯háhóhi:iYi„i¥iïij3j`j‹jÏjòjk:k`kzkÈkl<l[lrl©lm?mœmÎm%nZnn¶nÉnoJozo°oçopwp€pèpŠqkrþrxs sês8tqt²tðt@u‘uÁu vvåv-wkwƒw(xOxlxšxËxôx€yÐyvz¶zÕzX{š{ë{'|u|¿|÷|ž}ý}`~Ò~ó~GwÆò(€\€‰€³€ë€õ€ÿ€@Ü‚‚”‚Õ‚4ƒ}ƒ×ƒ„U„Š„Ê„
…S…Ž…å…'†X†ž†ä†‡_‡—‡Ñ‡ˆQˆ‘ˆÌˆ.‰U‰‡‰Ï‰ü‰<Š€ŠŠŠÛŠ‹q‹Û‹ŒTŒyŒ¢ŒÚŒûŒ0xê,ŽfŽ¡ŽÀŽâŽ
9M_•â:N¹6‘U‘’‘ª‘Ê‘Ü‘’/’l’‡’§’“<“h“‘“­“Ë“”`”Ÿ”Ä”2•¿•–k–œ–ë–"—I—Z—Œ—¥—õ—^˜z˜¹˜å˜™6™W™›™û™ šSš…š!›d›¢›Þ›œVœŽœÂòXžhžƒžŸž³žÐžùž(Ÿ^ŸžŸÍŸ J  ± ç 
¡j¡“¡Â¡ä¡$¢m¢˜¢É¢ò¢
£-£`£ž£€3€ €Ü€¥D¥w¥ª¥Š Š&Š0Š=ŠGŠOŠwŠ­ŠÍŠðŠ§C§n§™§º§ù§ šFš_š»š©5©m©—©Ž©Þ©#ªqªžªñª|«#¬Î¬|­%®¡®-¯ª¯/°Ó°q±Í±1²—²³-³Š³Ä³ÿ³)ŽeŽœŽŸŽµrµ»µöµ)¶d¶…¶Œ¶·y·²·ô·žMž—žÝž)¹q¹­¹Gºçºj»Ö»/ŒjŒ­ŒâŒœ,œHœŸþŸÊ¿›ÀnÁ%ŠÂëÂùÃ÷ÄMÅwųÅÆNƑÆùÆ5ÇoǧÇãÇÈ2È`ÈæÈGɍÉÊÉèÉ3ʁÊËZˇ˾ËðË/ÌoÌÂÌ÷Ì{Í8Î;ÎsΌÎÓÎèÏdÐÑÐ1ÑnÑžÑÒvÒÂÒþÒgÓŽÓßÓüÓ#ԜÔÕ{ÕêÕ!ֈÖØÖ%×׵טØÖØöÙäÚܞÜÀÜõÜ2ÝóÝ3ÞjÞ©ÞçÞcßzߑß#à¥àá_ááàáõáâ6âSâwâ”âÆâÙâã.ãTã“ãìãQä¹äøä!åŠåµå=æˆæææAç¿ç
èhèÏèïè	éëé*êmêžê!ëUë‹ë&ìVììžìÞìí3ídí¹íî5înîî·îï¿ï)ðkðÓðõð€ñ¹ñíñOò‰òÓò?ó„óÌó*ôGôáôyõÜõúõ[ö¯öæö<÷f÷øFúÍú7û°üÅüþ¿þñþ!ÿ_ÿÎÿJÔW°Ó@s×
 ?³¢DÄß9‡ò/`ˆú<	f	“	œ	æ	-
z
É
FwÃóMr›Àç
>
™
Ã
D•Íõ@oþqÖêc²ß1T¡æiœî'’ü9uë1Ÿë9€ñ@’Hº!h±è*nÇS€Êù6 š Ú P!®!"r"á"#\#€#£#œ#ß#û#$n$›$È$ç$%œ%ì%Y&}&Ó&{'¯'Í'O((Ç()?))Ñ)*…* *"+k+€+Ú+,M,,Ö,-D-v-Ï-8.v.Ž.Š.Ê./4/q/ˆ/›/Ï/ÿ/w0ã0(1x1|2š2Ñ2	3:33±3Õ3ð3o4‘4É4‡5696‹6È67¯7;8Ó879V9ð9:):g:}:¢:Ã:à:š;ì;[<‡<Ì<ù<#=9=P=•=¿=ê=í=
> >E>|> >Ä>‘?@C@ž@í@¢AB`B¯BøB§CRDhashchkisamchkNOYESファむル '%-.200s' を䜜成できたせん。(゚ラヌ番号: %d - %s)è¡š '%-.200s' を䜜成できたせん。(゚ラヌ番号: %d)デヌタベヌス '%-.192s' を䜜成できたせん。(゚ラヌ番号: %d)デヌタベヌス '%-.192s' を䜜成できたせん。デヌタベヌスはすでに存圚したす。デヌタベヌス '%-.192s' を削陀できたせん。デヌタベヌスは存圚したせん。デヌタベヌス削陀゚ラヌ ('%-.192s' を削陀できたせん。゚ラヌ番号: %d)デヌタベヌス削陀゚ラヌ (ディレクトリ '%-.192s' を削陀できたせん。゚ラヌ番号: %d)ファむル '%-.192s' の削陀゚ラヌ (゚ラヌ番号: %d - %s)システム衚のレコヌドを読み蟌めたせん。'%-.200s' の状態を取埗できたせん。(゚ラヌ番号: %d - %s)䜜業ディレクトリを取埗できたせん。(゚ラヌ番号: %d - %s)ファむルをロックできたせん。(゚ラヌ番号: %d - %s)ファむル '%-.200s' をオヌプンできたせん。(゚ラヌ番号: %d - %s)ファむル '%-.200s' が芋぀かりたせん。(゚ラヌ番号: %d - %s)ディレクトリ '%-.192s' を読み蟌めたせん。(゚ラヌ番号: %d - %s)ディレクトリ '%-.192s' に移動できたせん。(゚ラヌ番号: %d - %s)è¡š '%-.192s' の最埌の読み蟌み時点から、レコヌドが倉化したした。ディスク領域䞍足です(%s)。(゚ラヌ番号: %d - %s)曞き蟌めたせん。衚 '%-.192s' に重耇するキヌがありたす。'%-.192s' のクロヌズ時゚ラヌ (゚ラヌ番号: %d - %s)ファむル '%-.200s' の読み蟌み゚ラヌ (゚ラヌ番号: %d - %s)'%-.210s' の名前を '%-.210s' に倉曎できたせん (゚ラヌ番号: %d - %s)ファむル '%-.200s' の曞き蟌み゚ラヌ (゚ラヌ番号: %d - %s)'%-.192s' はロックされおいたす。゜ヌト凊理を䞭断したした。ビュヌ '%-.192s' は '%-.192s' に存圚したせん。ストレヌゞ゚ンゞンが゚ラヌ %d を返したした。衚 '%-.192s' のストレヌゞ゚ンゞンでは提䟛されないオプションです。'%-.192s' にレコヌドが芋぀かりたせん。ファむル '%-.200s' 内の情報が䞍正です。衚 '%-.200s' の玢匕ファむル(key file)の内容が䞍正です。修埩を詊行しおください。衚 '%-.192s' の玢匕ファむル(key file)は叀い圢匏です。修埩しおください。衚 '%-.192s' は読み蟌み専甚です。メモリが䞍足しおいたす。サヌバヌを再起動しおみおください。(%d バむトの割り圓おに倱敗)゜ヌトメモリが䞍足しおいたす。゜ヌトバッファサむズ(sort buffer size)の増加を怜蚎しおください。ファむル '%-.192s' を読み蟌み䞭に予期せずファむルの終端に達したした。(゚ラヌ番号: %d - %s)接続が倚すぎたす。メモリが䞍足しおいたす。mysqld やその他のプロセスがメモリヌを䜿い切っおいないか確認しお䞋さい。メモリヌを䜿い切っおいない堎合、'ulimit'の蚭定等で mysqld のメモリヌ䜿甚最倧量を倚くするか、スワップ領域を増やす必芁があるかもしれたせん。IPアドレスからホスト名を解決できたせん。ハンドシェむク゚ラヌナヌザヌ '%-.48s'@'%-.64s' によるデヌタベヌス '%-.192s' ぞのアクセスは拒吊されたした。ナヌザヌ '%-.48s'@'%-.64s' のアクセスは拒吊されたした。(using password: %s)デヌタベヌスが遞択されおいたせん。䞍明なコマンドです。列 '%-.192s' は null にできたせん。'%-.192s' は䞍明なデヌタベヌスです。衚 '%-.192s' はすでに存圚したす。'%-.100s' は䞍明な衚です。列 '%-.192s' は %-.192s 内で曖昧です。サヌバヌをシャットダりン䞭です。列 '%-.192s' は '%-.192s' にはありたせん。'%-.192s' はGROUP BY句で指定されおいたせん。'%-.192s' でのグルヌプ化はできたせん。集蚈関数ず通垞の列が同時に指定されおいたす。列数が倀の個数ず䞀臎したせん。識別子名 '%-.100s' は長すぎたす。列名 '%-.192s' は重耇しおたす。玢匕名 '%-.192s' は重耇しおいたす。'%-.192s' は玢匕 %d で重耇しおいたす。列 '%-.192s' の定矩が䞍正です。%s : '%-.80s' 付近 %d 行目ク゚リが空です。衚名別名 '%-.192s' は䞀意ではありたせん。'%-.192s' ぞのデフォルト倀が無効です。PRIMARY KEY が耇数定矩されおいたす。玢匕の数が倚すぎたす。最倧 %d 個たでです。玢匕のキヌ列指定が倚すぎたす。最倧 %d 個たでです。玢匕のキヌが長すぎたす。最倧 %d バむトたでです。キヌ列 '%-.192s' は衚にありたせん。指定されたストレヌゞ゚ンゞンでは、BLOB列 '%-.192s' は玢匕キヌにできたせん。列 '%-.192s' のサむズ定矩が倧きすぎたす (最倧 %lu たで)。代わりに BLOB たたは TEXT を䜿甚しおください。䞍正な衚定矩です。AUTO_INCREMENT列は個たでで、玢匕を定矩する必芁がありたす。%s: 接続準備完了。
バヌゞョン: '%s'  socket: '%s'  port: %d"%s: 通垞シャットダりン
%s: シグナル %d を受信したした。匷制終了したす
%s: シャットダりン完了
%s: スレッド %ld を匷制終了したす (ナヌザヌ: '%-.48s')
IP゜ケットを䜜成できたせん。衚 '%-.192s' に以前CREATE INDEXで䜜成された玢匕がありたせん。衚を䜜り盎しおください。フィヌルド区切り文字が予期せぬ䜿われ方をしおいたす。マニュアルを確認しお䞋さい。BLOBには固定長レコヌドが䜿甚できたせん。'FIELDS TERMINATED BY'句を䜿甚しお䞋さい。ファむル '%-.128s' はデヌタベヌスディレクトリにあるか、党おのナヌザヌから読める必芁がありたす。ファむル '%-.200s' はすでに存圚したす。レコヌド数: %ld  削陀: %ld  スキップ: %ld  è­Šå‘Š: %ldレコヌド数: %ld  重耇: %ldキヌのプレフィックスが䞍正です。キヌが文字列ではないか、プレフィックス長がキヌよりも長いか、ストレヌゞ゚ンゞンが䞀意玢匕のプレフィックス指定をサポヌトしおいたせん。ALTER TABLE では党おの列の削陀はできたせん。DROP TABLE を䜿甚しおください。'%-.192s' を削陀できたせん。列玢匕の存圚を確認しお䞋さい。レコヌド数: %ld  重耇数: %ld  è­Šå‘Š: %ldFROM句にある衚 '%-.192s' はUPDATEの察象にできたせん。䞍明なスレッドIDです: %luスレッド %lu のオヌナヌではありたせん。衚が指定されおいたせん。SET型の列 '%-.192s' のメンバヌの数が倚すぎたす。䞀意なログファむル名 %-.200s.(1-999) を生成できたせん。
è¡š '%-.192s' はREADロックされおいお、曎新できたせん。衚 '%-.192s' は LOCK TABLES でロックされおいたせん。BLOB/TEXT 列 '%-.192s' にはデフォルト倀を指定できたせん。デヌタベヌス名 '%-.100s' は䞍正です。衚名 '%-.100s' は䞍正です。SELECTがMAX_JOIN_SIZEを超える行数を凊理したした。WHERE句を確認し、SELECT文に問題がなければ、 SET SQL_BIG_SELECTS=1 たたは SET MAX_JOIN_SIZE=# を䜿甚しお䞋さい。䞍明な゚ラヌ'%-.192s' は䞍明なプロシヌゞャです。プロシヌゞャ '%-.192s' ぞのパラメヌタ数が䞍正です。プロシヌゞャ '%-.192s' ぞのパラメヌタが䞍正です。'%-.192s' は %-.32s では䞍明な衚です。列 '%-.192s' は2回指定されおいたす。集蚈関数の䜿甚方法が䞍正です。衚 '%-.192s' は、このMySQLバヌゞョンには無い機胜を䜿甚しおいたす。衚には最䜎でも1個の列が必芁です。衚 '%-.192s' は満杯です。䞍明な文字コヌドセット: '%-.64s'衚が倚すぎたす。MySQLがJOINできる衚は %d 個たでです。列が倚すぎたす。行サむズが倧きすぎたす。この衚の最倧行サむズは BLOB を含たずに %ld です。栌玍時のオヌバヌヘッドも含たれたす(マニュアルを確認しおください)。列をTEXTたたはBLOBに倉曎する必芁がありたす。スレッドスタック䞍足です(䜿甚: %ld ; サむズ: %ld)。必芁に応じお、より倧きい倀で 'mysqld --thread_stack=#' の指定をしおください。OUTER JOINに盞互䟝存が芋぀かりたした。ON句の条件を確認しお䞋さい。Table handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handler関数 '%-.192s' をロヌドできたせん。関数 '%-.192s' を初期化できたせん。; %-.80s共有ラむブラリにはパスを指定できたせん。関数 '%-.192s' はすでに定矩されおいたす。共有ラむブラリ '%-.192s' を開く事ができたせん。(゚ラヌ番号: %d %-.128s)関数 '%-.128s' は共有ラむブラリヌ䞭にありたせん。関数 '%-.192s' は定矩されおいたせん。接続゚ラヌが倚いため、ホスト '%-.64s' は拒吊されたした。'mysqladmin flush-hosts' で解陀できたす。ホスト '%-.64s' からのこの MySQL server ぞの接続は蚱可されおいたせん。MySQL を匿名ナヌザヌで䜿甚しおいるので、パスワヌドの倉曎はできたせん。他のナヌザヌのパスワヌドを倉曎するためには、mysqlデヌタベヌスの衚を曎新する暩限が必芁です。ナヌザヌテヌブルに該圓するレコヌドが芋぀かりたせん。該圓した行: %ld  倉曎: %ld  è­Šå‘Š: %ld新芏にスレッドを䜜成できたせん。(゚ラヌ番号 %d) もしも䜿甚可胜メモリヌの䞍足でなければ、OS䟝存のバグである可胜性がありたす。%ld 行目で、列の数が倀の数ず䞀臎したせん。衚を再オヌプンできたせん。: '%-.192s'NULL 倀の䜿甚方法が䞍適切です。regexp が゚ラヌ '%-.64s' を返したした。GROUP BY句が無い堎合、集蚈関数(MIN(),MAX(),COUNT(),...)ず通垞の列を同時に䜿甚できたせん。ナヌザヌ '%-.48s' (ホスト '%-.64s' 侊) は蚱可されおいたせん。コマンド %-.128s は ナヌザヌ '%-.48s'@'%-.64s' の衚 '%-.64s' の䜿甚に関しお蚱可されおいたせん。コマンド %-.16s は ナヌザヌ '%-.48s'@'%-.64s'
 の列 '%-.192s'(è¡š '%-.192s') の利甚に関しお蚱可されおいたせん。䞍正な GRANT/REVOKE コマンドです。どの暩限で利甚可胜かはマニュアルを参照しお䞋さい。GRANTコマンドぞの、ホスト名やナヌザヌ名が長すぎたす。衚 '%-.192s.%-.192s' は存圚したせん。ナヌザヌ '%-.48s' (ホスト '%-.64s' 侊) の衚 '%-.192s' ぞの暩限は定矩されおいたせん。このMySQLバヌゞョンでは利甚できないコマンドです。SQL構文゚ラヌです。バヌゞョンに察応するマニュアルを参照しお正しい構文を確認しおください。Delayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in use接続 %ld が䞭断されたした。デヌタベヌス: '%-.192s' ナヌザヌ: '%-.48s' (%-.64s)'max_allowed_packet'よりも倧きなパケットを受信したした。接続パむプの読み蟌み゚ラヌです。fcntl()が゚ラヌを返したした。䞍正な順序のパケットを受信したした。圧瞮パケットの展開ができたせんでした。パケットの受信で゚ラヌが発生したした。パケットの受信でタむムアりトが発生したした。パケットの送信で゚ラヌが発生したした。パケットの送信でタむムアりトが発生したした。結果の文字列が 'max_allowed_packet' よりも倧きいです。指定されたストレヌゞ゚ンゞンでは、BLOB/TEXT型の列を䜿甚できたせん。指定されたストレヌゞ゚ンゞンでは、AUTO_INCREMENT列を䜿甚できたせん。INSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLES列名 '%-.100s' は䞍正です。䜿甚のストレヌゞ゚ンゞンは列 '%-.192s' の玢匕を䜜成できたせん。MERGE衚の構成衚がオヌプンできたせん。列定矩が異なるか、MyISAM衚ではないか、存圚したせん。䞀意性制玄違反のため、衚 '%-.192s' に曞き蟌めたせん。BLOB列 '%-.192s' をキヌに䜿甚するには長さ指定が必芁です。PRIMARY KEYの列は党おNOT NULLでなければいけたせん。UNIQUE玢匕であればNULLを含むこずが可胜です。結果が2行以䞊です。䜿甚のストレヌゞ゚ンゞンでは、PRIMARY KEYが必芁です。このバヌゞョンのMySQLはRAIDサポヌトを含めおコンパむルされおいたせん。'safe update mode'で、玢匕を利甚するWHERE句の無い曎新凊理を実行しようずしたした。. %s玢匕 '%-.192s' は衚 '%-.192s' には存圚したせん。衚をオヌプンできたせん。この衚のストレヌゞ゚ンゞンは '%s' を利甚できたせん。このコマンドはトランザクション内で実行できたせん。COMMIT䞭に゚ラヌ %d が発生したした。ROLLBACK䞭に゚ラヌ %d が発生したした。FLUSH_LOGS䞭に゚ラヌ %d が発生したした。CHECKPOINT䞭に゚ラヌ %d が発生したした。接続 %u が䞭断されたした。デヌタベヌス: '%-.192s' ナヌザヌ: '%-.48s' ホスト: '%-.64s' (%-.64s)この衚のストレヌゞ゚ンゞンはバむナリ圢匏の衚ダンプを利甚できたせん。バむナリログがクロヌズされおいたす。RESET MASTER を実行できたせん。ダンプ衚 '%-.192s' の玢匕再構築に倱敗したした。マスタヌで゚ラヌが発生: '%-.64s'マスタヌからのデヌタ受信䞭のネットワヌク゚ラヌマスタヌぞのデヌタ送信䞭のネットワヌク゚ラヌ列リストに察応する党文玢匕(FULLTEXT)が芋぀かりたせん。すでにアクティブな衚ロックやトランザクションがあるため、コマンドを実行できたせん。'%-.64s' は䞍明なシステム倉数です。衚 '%-.192s' は壊れおいたす。修埩が必芁です。衚 '%-.192s' は壊れおいたす。修埩(自動)にも倱敗しおいたす。トランザクション察応ではない衚ぞの倉曎はロヌルバックされたせん。耇数ステヌトメントから成るトランザクションが 'max_binlog_cache_size' 以䞊の容量を必芁ずしたした。このシステム倉数を増加しお、再詊行しおください。この凊理は、皌働䞭のスレヌブでは実行できたせん。あらかじめSTOP SLAVEコマンドを実行しおください。この凊理は、皌働䞭のスレヌブでなければ実行できたせん。スレヌブの蚭定をしおSTART SLAVEコマンドを実行しおください。このサヌバヌはスレヌブずしお蚭定されおいたせん。コンフィグファむルかCHANGE MASTER TOコマンドで蚭定しお䞋さい。'master info'構造䜓の初期化ができたせんでした。MySQL゚ラヌログで゚ラヌメッセヌゞを確認しおください。スレヌブスレッドを䜜成できたせん。システムリ゜ヌスを確認しおください。ナヌザヌ '%-.64s' はすでに 'max_user_connections' 以䞊のアクティブな接続を行っおいたす。SET凊理が倱敗したした。ロック埅ちがタむムアりトしたした。トランザクションを再詊行しおください。ロックの数が倚すぎたす。読み蟌み専甚トランザクションです。グロヌバルリヌドロックを保持しおいる間は、DROP DATABASE を実行できたせん。グロヌバルリヌドロックを保持しおいる間は、CREATE DATABASE を実行できたせん。%s の匕数が䞍正です'%-.48s'@'%-.64s' は新しいナヌザヌを䜜成できたせん。䞍正な衚定矩です。MERGE衚の構成衚はすべお同じデヌタベヌス内になければなりたせん。ロック取埗䞭にデッドロックが怜出されたした。トランザクションを再詊行しおください。䜿甚の衚は党文玢匕を利甚できたせん。倖郚キヌ制玄を远加できたせん。芪キヌがありたせん。倖郚キヌ制玄違反です。子レコヌドがありたす。倖郚キヌ制玄違反です。マスタヌぞの接続゚ラヌ: %-.128sマスタヌでのク゚リ実行゚ラヌ: %-.128s%s コマンドの実行゚ラヌ: %-.128s%s の %s に関する䞍正な䜿甚法です。䜿甚のSELECT文が返す列数が違いたす。競合するリヌドロックを保持しおいるので、ク゚リを実行できたせん。トランザクション察応の衚ず非察応の衚の同時䜿甚は無効化されおいたす。オプション '%s' が2床䜿甚されおいたす。ナヌザヌ '%-.64s' はリ゜ヌスの䞊限 '%s' に達したした。(珟圚倀: %ld)アクセスは拒吊されたした。この操䜜には %-.128s 暩限が(耇数の堎合はどれか1぀)必芁です。倉数 '%-.64s' はセッション倉数です。SET GLOBALでは䜿甚できたせん。倉数 '%-.64s' はグロヌバル倉数です。SET GLOBALを䜿甚しおください。倉数 '%-.64s' にはデフォルト倀がありたせん。倉数 '%-.64s' に倀 '%-.200s' を蚭定できたせん。倉数 '%-.64s' ぞの倀の型が䞍正です。倉数 '%-.64s' は曞き蟌み専甚です。読み蟌みはできたせん。'%s' の䜿甚法たたは堎所が䞍正です。このバヌゞョンのMySQLでは、ただ '%s' を利甚できたせん。臎呜的な゚ラヌ %d: '%-.512s' がマスタヌでバむナリログ読み蟌み䞭に発生したした。replicate-*-table ルヌルに埓っお、スレヌブSQLスレッドはク゚リを無芖したした。倉数 '%-.192s' は %s 倉数です。倖郚キヌ '%-.192s' の定矩の䞍正: %s倖郚キヌの参照衚ず定矩が䞀臎したせん。オペランドに %d 個の列が必芁です。サブク゚リが2行以䞊の結果を返したす。'%.*s' はプリペアヌドステヌトメントの䞍明なハンドルです。(%s で指定されたした)ヘルプデヌタベヌスは壊れおいるか存圚したせん。サブク゚リの参照がルヌプしおいたす。列 '%s' を %s から %s ぞ倉換したす。'%-.64s' の参照はできたせん。(%s)導出衚には別名が必須です。Select %u は最適化によっお枛らされたした。特定のSELECTのみで䜿甚の衚 '%-.192s' は %-.32s では䜿甚できたせん。クラむアントはサヌバヌが芁求する認蚌プロトコルに察応できたせん。MySQLクラむアントのアップグレヌドを怜蚎しおください。空間玢匕のキヌ列は NOT NULL でなければいけたせん。COLLATION '%s' は CHARACTER SET '%s' に適甚できたせん。スレヌブはすでに皌働䞭です。スレヌブはすでに停止しおいたす。展開埌のデヌタが倧きすぎたす。最倧サむズは %d です。(展開埌デヌタの長さ情報が壊れおいる可胜性もありたす。)ZLIB: メモリ䞍足です。ZLIB: 出力バッファに十分な空きがありたせん。(展開埌デヌタの長さ情報が壊れおいる可胜性もありたす。)ZLIB: 入力デヌタが壊れおいたす。Row %u was cut by GROUP_CONCAT()行 %ld はすべおの列ぞのデヌタを含んでいたせん。行 %ld はデヌタを切り捚おられたした。列よりも倚いデヌタを含んでいたした。列にデフォルト倀が蚭定されたした。NOT NULLの列 '%s' に 行 %ld で NULL が䞎えられたした。Out of range value for column '%s' at row %ld列 '%s' の 行 %ld でデヌタが切り捚おられたした。ストレヌゞ゚ンゞン %s が衚 '%s' に利甚されおいたす。照合順序 (%s,%s) ず (%s,%s) の混圚は操䜜 '%s' では䞍正です。Cannot drop one or more of the requested users指定されたナヌザヌから指定された党おの暩限を剥奪するこずができたせんでした。照合順序 (%s,%s), (%s,%s), (%s,%s) の混圚は操䜜 '%s' では䞍正です。操䜜 '%s' では䞍正な照合順序の混圚です。倉数 '%-.64s' は構造倉数の構成芁玠ではありたせん。(XXXX.倉数名 ずいう指定はできたせん。)䞍明な照合順序: '%-.64s'このMySQLスレヌブはSSLサポヌトを含めおコンパむルされおいないので、CHANGE MASTER のSSLパラメヌタは無芖されたした。今埌SSLサポヌトを持぀MySQLスレヌブを起動する際に利甚されたす。サヌバヌは --secure-auth モヌドで皌働しおいたす。しかし '%s'@'%s' は叀い圢匏のパスワヌドを䜿甚しおいたす。新しい圢匏のパスワヌドに倉曎しおください。フィヌルドたたは参照 '%-.192s%s%-.192s%s%-.192s' は SELECT #%d ではなく、SELECT #%d で解決されたした。START SLAVE UNTIL ぞのパラメヌタたたはその組み合わせが䞍正です。START SLAVE UNTIL で段階的にレプリケヌションを行う際には、--skip-slave-start オプションを䜿うこずを掚奚したす。䜿わない堎合、スレヌブのmysqldが䞍慮の再起動をするず問題が発生したす。スレヌブSQLスレッドが開始されないため、UNTILオプションは無芖されたした。玢匕名 '%-.100s' は䞍正です。カタログ名 '%-.100s' は䞍正です。ク゚リキャッシュのサむズを %lu にできたせんでした。サむズは %lu になりたした。列 '%-.192s' は党文玢匕のキヌにはできたせん。'%-.100s' は䞍明なキヌキャッシュです。MySQLは --skip-name-resolve モヌドで起動しおいたす。このオプションを倖しお再起動しなければ、この暩限操䜜は機胜したせん。'%s' は䞍明なストレヌゞ゚ンゞンです。'%s' は将来のリリヌスで廃止予定です。代わりに %s を䜿甚しおください。察象衚 %-.100s は曎新可胜ではないので、%s を行えたせん。機胜 '%s' は無効です。利甚するためには '%s' を含めおビルドしたMySQLが必芁です。MySQLサヌバヌが %s オプションで実行されおいるので、このステヌトメントは実行できたせん。列 '%-.100s' で、重耇する倀 '%-.64s' が %s に指定されおいたす。䞍正な %-.32s の倀が切り捚おられたした。: '%-.128s'䞍正な衚定矩です。DEFAULT句たたはON UPDATE句に CURRENT_TIMESTAMP をずもなうTIMESTAMP型の列は1぀たでです。列 '%-.192s' に ON UPDATE句は無効です。This command is not supported in the prepared statement protocol yet゚ラヌ %d '%-.100s' が %s から返されたした。䞀時゚ラヌ %d '%-.100s' が %s から返されたした。Unknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'View's SELECT and view's field list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.64s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections.
Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaスレッドスタック䞍足です(䜿甚: %ld ; サむズ: %ld ; 芁求: %ld)。より倧きい倀で 'mysqld --thread_stack=#' の指定をしおください。Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. The trigger will be activated under the authorization of the invoker, which may have insufficient privileges. Please recreate the trigger.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The table mysql.proc is missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)察象衚 %-.100s は挿入可胜ではないので、%s を行えたせん。Table '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning functionNumber of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on master and slave does not match: %sSlave running with --log-slave-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryColumn count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please use mysql_upgrade to fix this error.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tables"You cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native function'%-.64s' は玢匕 '%-.192s' で重耇しおいたす。Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occured on the master. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sMaster command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous slave modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The master info structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected master's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128s"Comment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the slave startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the slave.Statement is unsafe because it uses a system variable that may have a different value on the slave.Statement is unsafe because it uses a system function that may return a different value on the slave.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTナヌザヌ '%-.48s'@'%-.64s' のアクセスは拒吊されたした。SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `slave_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on master and the slave.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on master and the slave.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the master delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setパヌティション '%-.64s' は存圚したせん。Failure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded slave mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Slave SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters MASTER_LOG_FILE, MASTER_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when MASTER_AUTO_POSITION is active.CHANGE MASTER TO MASTER_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-slave-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires. Replicate the missing transactions from elsewhere, or provision a new slave from backup. Consider increasing the master's binary log expiration period. %s.@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Slave is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a slave. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE MASTER cannot be executed when the slave was stopped with an error or killed in MTS mode. Consider using RESET SLAVE or START SLAVE UNTIL.Cannot recover after SLAVE errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedSlave must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sSupports only YEAR or YEAR(4) column.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constaint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constaint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format. Check if the correct password algorithm is being used with the PASSWORD() function.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_slave_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionは玢匕 '%-.192s' で重耇しおいたす。Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of slave_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Slave failed to initialize master info structure from the repositorySlave failed to initialize relay log info structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP SLAVE command execution is incomplete: Slave SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP SLAVE command execution is incomplete: Slave IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_forced_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been committed on master but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.File %s is corruptedQuery partially completed on the master (error on master: %d) and was aborted. There is a chance that your master is inconsistent at this point. If you are sure that your master is ok, run this query manually on the slave and then restart the slave with SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVE;. Query:'%s'Query caused different errors on master and slave. Error on master: message (format)='%s' error code=%d; Error on slave:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the slave.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.Column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please use mysql_upgrade to fix this error.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running slave sql thread; run STOP SLAVE SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running slave io thread; run STOP SLAVE IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the slave has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until slave_open_temp_tables = 0.CHANGE MASTER TO with a MASTER_LOG_FILE clause but no MASTER_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNIONExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated querySlave worker has stopped after at least one previous worker encountered an error when slave-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the slave after fixing any failed threads, you should fix this worker as well.slave_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occured in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replication slave thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uSlave channel '%s' does not exist.A slave channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete slave info objects for channel '%s'.Multiple channels exist on the slave. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP SLAVE FOR CHANNEL '%s' firstThis operation requires running replication threads; configure slave and run START SLAVE FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running slave sql thread; run STOP SLAVE SQL_THREAD FOR CHANNEL '%s' first.When sql_slave_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START SLAVE [SQL_THREAD]'. Value of sql_slave_skip_counter can only be used by one SQL thread at a time. Please use 'START SLAVE [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_slave_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' cannot be used in key specification.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).User %s does not exist.User %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if neccessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring plugin is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring plugin is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please run mysql_upgrade.RESET MASTER is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on slaves when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER_ACL needed to perform operationSUPER privilege required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replication slave.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULL
Back to Directory File Manager