��

��v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,�,�,&-q-�-�-.<.v.�.�.6/}/�/>0�0�0&1�1�1A2�2�2*3�3�3;4`4�4�4*5^5�5�5B6�67J7v7�7�7L8�8�889�9�9�:I;�;�<=�=�=>�>�>�>I?�?�?@�@
AAAoA�A�ABQB|B�B�BCC�C�C<D�DElE�E�EFiF�F�FZG�G�GHTH�H�H.ItI�I�IJ/JjJ�JqK�K�K%LVL�LM�M�M�M6N�NOHO�O�O$PSP�PQUQ�Q�Q�R�S:T�T�U�UVJV�V�V/W�W
XqX�X/Y�Y
ZEZ�Z�ZC[}[�[�[\=\�\�\�\�\]!]8]V]j]�]�]�]
^4^�^_._k_�_�_�_�_``2`E`]`�`�`�`�`�`a'aData�a�a	b1b^b�b�bcYc�c�c�cd(dWd�d�debe�e fRfif�f�f�f�f,g:g{g�g�ghLhnh�h�h�hi.iKiui�i�i�i*j<jnj�j�j
k-kCkuk�k�klGlwl�l�l�l?mzm�m	n`n�n�n�noIo�o�o�o"pOp�p�p#q�q�r9s�s�s%tst�t�t2u�u�uvbv�v'wow�w�wjx�x�x�x
y6y�yz�z�z{�{�{-|i|�|
}9}�}?~�~5���4�j���ˀ��-�7�A���с�C�_�ւ�v����`���̄�O�����'�i�����&�[���ه�E���ӈ�p���ɉ�>�~�NJ�"�]���"�]������!�B�w���1�s�����)�Q�������܏)�����Ȑ�}���ّ��#�N�v���Β�H�����ؓ���R�����y��f����2�i�����ӗ�<������,�I�}����B�g���̚h����'�f���לT�؝�?�����О���F�u�����X���Π��4�Z�����1�q�����?�W�z����Y�����)�]���ĥ��d�m�s�}�������Ħ���=�g�������F�m������Y������
�+�p����>�ɫp��ɭr��z���|� ����~��i�z�׳�L�v�����j����C�v���Ҷ	�T�Ʒ��A�c����*�v�������4���#�|�����/�c�y���f�K������r���8�F�D������c�����F�������0�]����3������5�����h������=�|����D����������� �5����~����T����K���
�,�I�p������J����\����U�?�������k����G���E�������9�������u���Z�����2�G�l�������#�U�h������D�z���G������C����t���M�����]�}���y�����F����������
�,�l�������G��������E��M�����a����G�{����a����Z�����o��j�����=�t�������hashchkisamchkNOYESファイル '%-.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'スレッドが表 '%-.192s' のロックを取得できませんでした。'Delayed insert'スレッドが多すぎます。接続 %ld が中断されました。データベース: '%-.192s' ユーザー: '%-.48s' (%-.64s)'max_allowed_packet'よりも大きなパケットを受信しました。接続パイプの読み込みエラーです。fcntl()がエラーを返しました。不正な順序のパケットを受信しました。圧縮パケットの展開ができませんでした。パケットの受信でエラーが発生しました。パケットの受信でタイムアウトが発生しました。パケットの送信でエラーが発生しました。パケットの送信でタイムアウトが発生しました。結果の文字列が 'max_allowed_packet' よりも大きいです。指定されたストレージエンジンでは、BLOB/TEXT型の列を使用できません。指定されたストレージエンジンでは、AUTO_INCREMENT列を使用できません。表 '%-.192s' はLOCK TABLESでロックされているため、INSERT DELAYEDを使用できません。列名 '%-.100s' は不正です。使用のストレージエンジンは列 '%-.192s' の索引を作成できません。MERGE表の構成表がオープンできません。列定義が異なるか、MyISAM表ではないか、存在しません。一意性制約違反のため、表 '%-.192s' に書き込めません。BLOB列 '%-.192s' をキーに使用するには長さ指定が必要です。PRIMARY KEYの列は全てNOT NULLでなければいけません。UNIQUE索引であればNULLを含むことが可能です。結果が2行以上です。使用のストレージエンジンでは、PRIMARY KEYが必要です。このバージョンのMySQLはRAIDサポートを含めてコンパイルされていません。'safe update mode'で、索引を利用するWHERE句の無い更新処理を実行しようとしました。索引 '%-.192s' は表 '%-.192s' には存在しません。表をオープンできません。この表のストレージエンジンは '%s' を利用できません。このコマンドはトランザクション内で実行できません。COMMIT中にエラー %d が発生しました。ROLLBACK中にエラー %d が発生しました。FLUSH_LOGS中にエラー %d が発生しました。CHECKPOINT中にエラー %d が発生しました。接続 %ld が中断されました。データベース: '%-.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: '%-.320s' がマスターでバイナリログ読み込み中に発生しました。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 column '%-.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 `%-.32s`" 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 key clause is 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 '%-.192s'This 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: %-.64sTable 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 `%-.32s` 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 Global Transaction Identifier: the integer component reached the maximal 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 can only be executed when @@GLOBAL.GTID_MODE = ON.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT != AUTOMATIC.@@GLOBAL.GTID_MODE = ON or UPGRADE_STEP_2 requires @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1.@@GLOBAL.GTID_MODE = ON or UPGRADE_STEP_1 or UPGRADE_STEP_2 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 or Previous_gtids_log_event when @@GLOBAL.GTID_MODE = OFF.When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, 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.CREATE TABLE ... SELECT is forbidden when @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1.When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, the statements CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can be executed in a non-transactional context only, and require that AUTOCOMMIT = 1. 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 change one step at a time: OFF <-> UPGRADE_STEP_1 <-> UPGRADE_STEP_2 <-> 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.@@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 '%-.192s'Tablespace for table '%-.192s' exists. Please DISCARD the tablespace before IMPORT.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE '%-.192s' IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sYEAR(%lu) column type is deprecated. Creating YEAR(4) column instead.Your password does not satisfy the current policy requirementsYou must SET PASSWORD before executing this statementFailed 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.