Current File : //proc/3/cwd/usr/share/mysql/korean/errmsg.sys
�� �, \ e � � U � v � � . u � � B � � 1 � � 8 � � � U � � B � � � G � � !
�
) � � 5 l � � �
6
\
�
�
: d � � � : X � � � L � � 4 z � Z � � � � / W � 4 � E � � % � � b � � � & g � E � � � � � > | � � V � � � q � 0 � � � � L x � ! D! �! 1" �" 2# y# �# X$ �$ �$ % '% �% �% d& �& V' �' �' g( �( �( ) @) �) �) * V* �* �* �* =+ �+ �+ �+ 2, m, �, �, - S- �- �- 1. W. ~. �. / O/ `/ �/ �/ �/ 0 !0 @0 �0 �0 �0 ,1 H1 f1 �1 �1 2 52 q2 �2 �2 }3 �3 4 j4 �4 5 P5 5 �5 �5 26 u6 �6 �6 7 S7 �7 �7 �7 .8 s8 �8 �8 �8 9 B9 �9 �9 �9 *: �: �: ; B; {; �; �; �; %< q< �< �< = <= `= �= �= �= > &> L> x> �> �> H? v? �? �? �? P@ h@ �@ �@ A 2A ~A �A �A $B KB �B �B �B EC rC �C �C �D E aE �E aF �F �F �F G PG lG �G �G GH {H �H I SI I �I &J kJ �J �J �J K 3K wK �K �K �K L L .L LL `L {L �L �L M *M �M N $N aN yN �N �N �N �N O (O ;O SO wO �O �O �O �O P P :P jP �P �P �P 'Q TQ �Q �Q R OR �R �R �R �R S MS �S �S T XT �T U HU _U vU �U �U �U "V 0V qV �V �V �V BW dW �W �W �W X $X AX kX �X �X �X Y 2Y dY �Y �Y Z #Z 9Z kZ �Z �Z �Z =[ m[ �[ �[ �[ 5\ p\ �\ �\ V] �] �] �] �] ?^ {^ �^ �^ _ E_ �_ �_ ` �` �a /b �b �b c ic �c �c !d qd �d �d Qe �e f ^f �f �f ?g fg �g �g �g h �h �h �i �i �i oj �j k >k �k �k l �l m wm �m
n ^n �n �n o ?o so �o �o p p p Wp �p �p q q �q �q 6r r �r s Ws �s �s t Ut �t �t )u Zu �u �u v av �v �v w Sw �w �w 0x Wx �x �x �x >y �y �y �y z sz �z { V{ {{ �{ �{ �{ 2| z| �| .} h} �} �} �} ~ ;~ O~ a~ �~ �~ < P � � 8� W� �� �� ̀ ހ � 1� n� �� �� � >� j� �� �� ͂
� b� �� ƃ 4� �� !� m� �� � $� K� \� �� �� �� `� |� �� � � 8� Y� �� �� "� U� �� #� f� �� � � L� �� � �� �� � N� ^� y� �� �� ƍ � � T� �� Î � @� w� �� ݏ � `� �� �� ڐ � c� �� �� � � #� V� �� � )� �� ғ � :� m� ��
� � � &� 3� =� E� m� �� Õ � � 9� d� �� �� � � <� U� �� � +� c� �� �� Ԙ � g� �� � r� � ě r� � �� #� �� %� ɟ g� à '� �� � #� �� �� �� � [� �� �� � h� �� � � Z� {� �� �� o� �� � � C� �� ʧ � ^� �� 4� ԩ W� ê � W� �� ϫ � � 5� � � �� �� [� � w� ر � � :� d� �� � ;� ~� � "� \� �� ж �� � M� ӷ 4� z� �� ո � n� � G� t� �� ƺ � E� �� ͻ Q� � � I� b� �� �� :� �� � D� �� � L� �� � =� �� �� �� �� �� � j� �� � w� �� � n� �� �� �� �� �� l� �� � H� �� F� �� �� �� :� �� �� �� v� �� [� �� �� 3� H� m� �� �� �� �� � ,� o� �� �� �� ?� �� � K� t� �� � �� �� 9� �� � ]� �� "� B� \� >� }� �� � t� �� �� y� �� �� �� 1� d� �� �� � X� �� �� ��
� �� � p� �� � <� �� � 4� �� �� � �� �� � q� �� (� �� #� A� �� �� -� �� �� R� �� � )� e� #� U� �� �� 2� s� �� 8� j� �� � 7� z� �� �� ;� q� �� �� � � �� �� (� C� �� �� V� �� �� �� ^� �� � �� !� J� �� � -� �� �� � � '� W� �� �� � �� $� K� v� �� �� '� �� �� 1� Y� y� �� � b� � :� N� |� � � C� �� �� � J� � R � � ` � � O � i O � � U � � � � �
L
�
�
+ k � � . ] � � >
�
v � E � � � ! C _ ~ � � , K � ! P � � 7 � 1 � � + v � � 5 � � � � > y � � : { � � 3 � � �
. e � � � � 3 c � G � � � 5 m � � 9 T � � -! �! p" �" �" ,# }# $ �$ 7% �% �% T& f& �& �& �& ' '' D' ( P( �( �( 0) ]) �) �) �) �) #* N* Q* n* �* �* �* + (+ �+ x, hashchk isamchk 아니오 예 화일 '%-.200s'를 만들지 못했습니다. (에러번호: %d - %s) 테이블 '%-.200s'를 만들지 못했습니다. (에러번호: %d) 데이타베이스 '%-.192s'를 만들지 못했습니다.. (에러번호: %d) 데이타베이스 '%-.192s'를 만들지 못했습니다.. 데이타베이스가 존재함 데이타베이스 '%-.192s'를 제거하지 못했습니다. 데이타베이스가 존재하지 않음 데이타베이스 제거 에러('%-.192s'를 삭제할 수 없읍니다, 에러번호: %d) 데이타베이스 제거 에러(rmdir '%-.192s'를 할 수 없읍니다, 에러번호: %d) '%-.192s' 삭제 중 에러 (에러번호: %d - %s) system 테이블에서 레코드를 읽을 수 없습니다. '%-.200s'의 상태를 얻지 못했습니다. (에러번호: %d - %s) 수행 디렉토리를 찾지 못했습니다. (에러번호: %d - %s) 화일을 잠그지(lock) 못했습니다. (에러번호: %d - %s) 화일을 열지 못했습니다.: '%-.200s' (에러번호: %d - %s) 화일을 찾지 못했습니다.: '%-.200s' (에러번호: %d - %s) '%-.192s'디렉토리를 읽지 못했습니다. (에러번호: %d - %s) '%-.192s'디렉토리로 이동할 수 없었습니다. (에러번호: %d - %s) 테이블 '%-.192s'에서 마지막으로 읽은 후 Record가 변경되었습니다. Disk full (%s). 다른 사람이 지울때까지 기다립니다... (에러번호: %d - %s) 기록할 수 없읍니다., 테이블 '%-.192s'에서 중복 키 '%-.192s'닫는 중 에러 (에러번호: %d - %s) '%-.200s'화일 읽기 에러 (에러번호: %d - %s) '%-.210s'를 '%-.210s'로 이름 변경중 에러 (에러번호: %d - %s) '%-.200s'화일 기록 중 에러 (에러번호: %d - %s) '%-.192s'가 변경할 수 없도록 잠겨있읍니다. 소트가 중단되었습니다. 뷰 '%-.192s'가 '%-.192s'에서는 존재하지 않읍니다. 테이블 handler에서 %d 에러가 발생 하였습니다. '%-.192s'의 테이블 handler는 이러한 옵션을 제공하지 않읍니다. '%-.192s'에서 레코드를 찾을 수 없읍니다. 화일의 부정확한 정보: '%-.200s' '%-.200s' 테이블의 부정확한 키 존재. 수정하시오! '%-.192s' 테이블의 이전버젼의 키 존재. 수정하시오! 테이블 '%-.192s'는 읽기전용 입니다. Out of memory. 데몬을 재 실행 후 다시 시작하시오 (needed %d bytes) Out of sort memory. daemon sort buffer의 크기를 증가시키세요 '%-.192s' 화일을 읽는 도중 잘못된 eof을 발견 (에러번호: %d - %s) 너무 많은 연결... max_connection을 증가 시키시오... Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space 당신의 컴퓨터의 호스트이름을 얻을 수 없읍니다. Bad handshake '%-.48s'@'%-.64s' 사용자는 '%-.192s' 데이타베이스에 접근이 거부 되었습니다. '%-.48s'@'%-.64s' 사용자는 접근이 거부 되었습니다. (using password: %s) 선택된 데이타베이스가 없습니다. 명령어가 뭔지 모르겠어요... 칼럼 '%-.192s'는 널(Null)이 되면 안됩니다. 데이타베이스 '%-.192s'는 알수 없음 테이블 '%-.192s'는 이미 존재함 테이블 '%-.100s'는 알수 없음 칼럼: '%-.192s' in '%-.192s' 이 모호함 Server가 셧다운 중입니다. Unknown 칼럼 '%-.192s' in '%-.192s' '%-.192s'은 GROUP BY속에 없음 '%-.192s'를 그룹할 수 없음 Statement 가 sum기능을 동작중이고 칼럼도 동일한 statement입니다. 칼럼의 카운트가 값의 카운트와 일치하지 않습니다. Identifier '%-.100s'는 너무 길군요. 중복된 칼럼 이름: '%-.192s' 중복된 키 이름 : '%-.192s' 중복된 입력 값 '%-.192s': key %d 칼럼 '%-.192s'의 부정확한 칼럼 정의자 '%s' 에러 같읍니다. ('%-.80s' 명령어 라인 %d) 쿼리결과가 없습니다. Unique 하지 않은 테이블/alias: '%-.192s' '%-.192s'의 유효하지 못한 디폴트 값을 사용하셨습니다. Multiple primary key가 정의되어 있슴 너무 많은 키가 정의되어 있읍니다.. 최대 %d의 키가 가능함 너무 많은 키 부분(parts)들이 정의되어 있읍니다.. 최대 %d 부분이 가능함 정의된 키가 너무 깁니다. 최대 키의 길이는 %d입니다. Key 칼럼 '%-.192s'는 테이블에 존재하지 않습니다. BLOB 칼럼 '%-.192s'는 키 정의에서 사용될 수 없습니다. 칼럼 '%-.192s'의 칼럼 길이가 너무 깁니다 (최대 = %lu). 대신에 BLOB를 사용하세요. 부정확한 테이블 정의; 테이블은 하나의 auto 칼럼이 존재하고 키로 정의되어져야 합니다. %s: 연결 준비중입니다
Version: '%s' socket: '%s' port: %d" %s: 정상적인 shutdown
%s: %d 신호가 들어왔음. 중지!
%s: Shutdown 이 완료됨!
%s: thread %ld의 강제 종료 user: '%-.48s'
IP 소켓을 만들지 못했습니다. 테이블 '%-.192s'는 인덱스를 만들지 않았습니다. alter 테이블명령을 이용하여 테이블을 수정하세요... 필드 구분자 인수들이 완전하지 않습니다. 메뉴얼을 찾아 보세요. BLOB로는 고정길이의 lowlength를 사용할 수 없습니다. 'fields terminated by'를 사용하세요. '%-.128s' 화일는 데이타베이스 디렉토리에 존재하거나 모두에게 읽기 가능하여야 합니다. '%-.200s' 화일은 이미 존재합니다. 레코드: %ld개 삭제: %ld개 스킵: %ld개 경고: %ld개 레코드: %ld개 중복: %ld개 부정확한 서버 파트 키. 사용된 키 파트가 스트링이 아니거나 키 파트의 길이가 너무 깁니다. ALTER TABLE 명령으로는 모든 칼럼을 지울 수 없습니다. DROP TABLE 명령을 이용하세요. '%-.192s'를 DROP할 수 없습니다. 칼럼이나 키가 존재하는지 채크하세요. 레코드: %ld개 중복: %ld개 경고: %ld개 You can't specify target table '%-.192s' for update in FROM clause 알수 없는 쓰레드 id: %lu 쓰레드(Thread) %lu의 소유자가 아닙니다. 어떤 테이블도 사용되지 않았습니다. 칼럼 %-.192s와 SET에서 스트링이 너무 많습니다. Unique 로그화일 '%-.200s'를 만들수 없습니다.(1-999)
테이블 '%-.192s'는 READ 락이 잠겨있어서 갱신할 수 없습니다. 테이블 '%-.192s'는 LOCK TABLES 명령으로 잠기지 않았습니다. BLOB 칼럼 '%-.192s' 는 디폴트 값을 가질 수 없습니다. '%-.100s' 데이타베이스의 이름이 부정확합니다. '%-.100s' 테이블 이름이 부정확합니다. SELECT 명령에서 너무 많은 레코드를 찾기 때문에 많은 시간이 소요됩니다. 따라서 WHERE 문을 점검하거나, 만약 SELECT가 ok되면 SET SQL_BIG_SELECTS=1 옵션을 사용하세요. 알수 없는 에러입니다. 알수 없는 수행문 : '%-.192s' '%-.192s' 수행문에 대한 부정확한 파라메터 '%-.192s' 수행문에 대한 부정확한 파라메터 알수 없는 테이블 '%-.192s' (데이타베이스 %-.32s) 칼럼 '%-.192s'는 두번 정의되어 있읍니다. 잘못된 그룹 함수를 사용하였습니다. 테이블 '%-.192s'는 확장명령을 이용하지만 현재의 MySQL 버젼에서는 존재하지 않습니다. 하나의 테이블에서는 적어도 하나의 칼럼이 존재하여야 합니다. 테이블 '%-.192s'가 full났습니다. 알수없는 언어 Set: '%-.64s' 너무 많은 테이블이 Join되었습니다. MySQL에서는 JOIN시 %d개의 테이블만 사용할 수 있습니다. 칼럼이 너무 많습니다. 너무 큰 row 사이즈입니다. BLOB를 계산하지 않고 최대 row 사이즈는 %ld입니다. 얼마간의 필드들을 BLOB로 바꾸셔야 겠군요.. 쓰레드 스택이 넘쳤습니다. 사용: %ld개 스택: %ld개. 만약 필요시 더큰 스택을 원할때에는 'mysqld --thread_stack=#' 를 정의하세요 Cross dependency found in OUTER JOIN; examine your ON conditions 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서버에 접속할 허가를 받지 못했습니다. 당신은 MySQL서버에 익명의 사용자로 접속을 하셨습니다.익명의 사용자는 암호를 변경할 수 없습니다. 당신은 다른사용자들의 암호를 변경할 수 있도록 데이타베이스 변경권한을 가져야 합니다. 사용자 테이블에서 일치하는 것을 찾을 수 없읍니다. 일치하는 Rows : %ld개 변경됨: %ld개 경고: %ld개 새로운 쓰레드를 만들 수 없습니다.(에러번호 %d). 만약 여유메모리가 있다면 OS-dependent버그 의 메뉴얼 부분을 찾아보시오. Row %ld에서 칼럼 카운트와 value 카운터와 일치하지 않습니다. 테이블을 다시 열수 없군요: '%-.192s NULL 값을 잘못 사용하셨군요... regexp에서 '%-.64s'가 났습니다. Mixing of GROUP 칼럼s (MIN(),MAX(),COUNT(),...) with no GROUP 칼럼s is illegal if there is no GROUP BY clause 사용자 '%-.48s' (호스트 '%-.64s')를 위하여 정의된 그런 승인은 없습니다. '%-.128s' 명령은 다음 사용자에게 거부되었습니다. : '%-.48s'@'%-.64s' for 테이블 '%-.64s' '%-.16s' 명령은 다음 사용자에게 거부되었습니다. : '%-.48s'@'%-.64s' for 칼럼 '%-.192s' in 테이블 '%-.192s' 잘못된 GRANT/REVOKE 명령. 어떤 권리와 승인이 사용되어 질 수 있는지 메뉴얼을 보시오. 승인(GRANT)을 위하여 사용한 사용자나 호스트의 값들이 너무 깁니다. 테이블 '%-.192s.%-.192s' 는 존재하지 않습니다. 사용자 '%-.48s'(호스트 '%-.64s')는 테이블 '%-.192s'를 사용하기 위하여 정의된 승인은 없습니다. 사용된 명령은 현재의 MySQL 버젼에서는 이용되지 않습니다. SQL 구문에 오류가 있습니다. Delayed insert thread couldn't get requested lock for table %-.192s Too many delayed threads in use 데이타베이스 접속을 위한 연결 %ld가 중단됨 : '%-.192s' 사용자: '%-.48s' (%-.64s) 'max_allowed_packet'보다 더큰 패킷을 받았습니다. 연결 파이프로부터 에러가 발생하였습니다. fcntl() 함수로부터 에러가 발생하였습니다. 순서가 맞지않는 패킷을 받았습니다. 통신 패킷의 압축해제를 할 수 없었습니다. 통신 패킷을 읽는 중 오류가 발생하였습니다. 통신 패킷을 읽는 중 timeout이 발생하였습니다. 통신 패킷을 기록하는 중 오류가 발생하였습니다. 통신 패팃을 기록하는 중 timeout이 발생하였습니다. Result string is longer than 'max_allowed_packet' bytes The used table type doesn't support BLOB/TEXT columns The used table type doesn't support AUTO_INCREMENT columns INSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLES Incorrect column name '%-.100s' The used table handler can't index column '%-.192s' All tables in the MERGE table are not defined identically Can't write, because of unique constraint, to table '%-.192s' BLOB column '%-.192s' used in key specification without a key length All parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE instead Result consisted of more than one row This table type requires a primary key This version of MySQL is not compiled with RAID support You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column. %s Key '%-.192s' doesn't exist in table '%-.192s' Can't open table The handler for the table doesn't support %s You are not allowed to execute this command in a transaction Got error %d during COMMIT Got error %d during ROLLBACK Got error %d during FLUSH_LOGS Got error %d during CHECKPOINT Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.64s' (%-.64s) The storage engine for the table does not support binary table dump Binlog closed, cannot RESET MASTER Failed rebuilding the index of dumped table '%-.192s' Error from master: '%-.64s' Net error reading from master Net error writing to master Can't find FULLTEXT index matching the column list Can't execute the given command because you have active locked tables or an active transaction Unknown system variable '%-.64s' Table '%-.192s' is marked as crashed and should be repaired Table '%-.192s' is marked as crashed and last (automatic?) repair failed Some non-transactional changed tables couldn't be rolled back Multi-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try again This operation cannot be performed with a running slave; run STOP SLAVE first This operation requires a running slave; configure slave and do START SLAVE The server is not configured as slave; fix in config file or with CHANGE MASTER TO Could not initialize master info structure; more error messages can be found in the MySQL error log Could not create slave thread; check system resources User %-.64s already has more than 'max_user_connections' active connections You may only use constant expressions with SET Lock wait timeout exceeded; try restarting transaction The total number of locks exceeds the lock table size Update locks cannot be acquired during a READ UNCOMMITTED transaction DROP DATABASE not allowed while thread is holding global read lock CREATE DATABASE not allowed while thread is holding global read lock Incorrect arguments to %s '%-.48s'@'%-.64s' is not allowed to create new users Incorrect table definition; all MERGE tables must be in the same database Deadlock found when trying to get lock; try restarting transaction The used table type doesn't support FULLTEXT indexes Cannot add foreign key constraint Cannot add or update a child row: a foreign key constraint fails Cannot delete or update a parent row: a foreign key constraint fails Error connecting to master: %-.128s Error running query on master: %-.128s Error when executing command %s: %-.128s Incorrect usage of %s and %s The used SELECT statements have a different number of columns Can't execute the query because you have a conflicting read lock Mixing of transactional and non-transactional tables is disabled Option '%s' used twice in statement User '%-.64s' has exceeded the '%s' resource (current value: %ld) Access denied; you need (at least one of) the %-.128s privilege(s) for this operation Variable '%-.64s' is a SESSION variable and can't be used with SET GLOBAL Variable '%-.64s' is a GLOBAL variable and should be set with SET GLOBAL Variable '%-.64s' doesn't have a default value Variable '%-.64s' can't be set to the value of '%-.200s' Incorrect argument type to variable '%-.64s' Variable '%-.64s' can only be set, not read Incorrect usage/placement of '%s' This version of MySQL doesn't yet support '%s' Got fatal error %d from master when reading data from binary log: '%-.320s' Slave SQL thread ignored the query because of replicate-*-table rules Variable '%-.192s' is a %s variable Incorrect foreign key definition for '%-.192s': %s Key reference and table reference don't match Operand should contain %d column(s) Subquery returns more than 1 row Unknown prepared statement handler (%.*s) given to %s Help database is corrupt or does not exist Cyclic reference on subqueries Converting column '%s' from %s to %s Reference '%-.64s' not supported (%s) Every derived table must have its own alias Select %u was reduced during optimization Table '%-.192s' from one of the SELECTs cannot be used in %-.32s Client does not support authentication protocol requested by server; consider upgrading MySQL client All parts of a SPATIAL index must be NOT NULL COLLATION '%s' is not valid for CHARACTER SET '%s' Slave is already running Slave already has been stopped Uncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted) ZLIB: Not enough memory ZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted) ZLIB: Input data corrupted Row %u was cut by GROUP_CONCAT() Row %ld doesn't contain data for all columns Row %ld was truncated; it contained more data than there were input columns Column set to default value; NULL supplied to NOT NULL column '%s' at row %ld Out of range value for column '%s' at row %ld Data truncated for column '%s' at row %ld Using storage engine %s for table '%s' Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s' Cannot drop one or more of the requested users Can't revoke all privileges for one or more of the requested users Illegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s' Illegal mix of collations for operation '%s' Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name) Unknown collation: '%-.64s' SSL parameters in CHANGE MASTER are ignored because this MySQL slave was compiled without SSL support; they can be used later if MySQL slave with SSL is started Server is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new format Field or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%d Incorrect parameter or combination of parameters for START SLAVE UNTIL It is recommended to use --skip-slave-start when doing step-by-step replication with START SLAVE UNTIL; otherwise, you will get problems if you get an unexpected slave's mysqld restart SQL thread is not to be started so UNTIL options are ignored Incorrect index name '%-.100s' Incorrect catalog name '%-.100s' Query cache failed to set size %lu; new query cache size is %lu Column '%-.192s' cannot be part of FULLTEXT index Unknown key cache '%-.100s' MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to work Unknown storage engine '%s' '%s' is deprecated and will be removed in a future release. Please use %s instead The target table %-.100s of the %s is not updatable The '%s' feature is disabled; you need MySQL built with '%s' to have it working The MySQL server is running with the %s option so it cannot execute this statement Column '%-.100s' has duplicated value '%-.64s' in %s Truncated incorrect %-.32s value: '%-.128s' Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause Invalid ON UPDATE clause for '%-.192s' column This command is not supported in the prepared statement protocol yet Got error %d '%-.100s' from %s Got temporary error %d '%-.100s' from %s Unknown or incorrect time zone: '%-.64s' Invalid TIMESTAMP value in column '%s' at row %ld Invalid %s character string: '%.64s' Result of %s() was larger than max_allowed_packet (%ld) - truncated Conflicting declarations: '%s%s' and '%s%s' Can't create a %s from within another stored routine %s %s already exists %s %s does not exist Failed to DROP %s %s Failed to CREATE %s %s %s with no matching label: %s Redefining label %s End-label %s without match Referring to uninitialized variable %s PROCEDURE %s can't return a result set in the given context RETURN is only allowed in a FUNCTION %s is not allowed in stored procedures The 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 interrupted Incorrect number of arguments for %s %s; expected %u, got %u Undefined CONDITION: %s No RETURN found in FUNCTION %s FUNCTION %s ended without RETURN Cursor statement must be a SELECT Cursor SELECT must not have INTO Undefined CURSOR: %s Cursor is already open Cursor is not open Undeclared variable: %s Incorrect number of FETCH variables No data - zero rows fetched, selected, or processed Duplicate parameter: %s Duplicate variable: %s Duplicate condition: %s Duplicate cursor: %s Failed to ALTER %s %s Subquery value not supported %s is not allowed in stored function or trigger Variable or condition declaration after cursor or handler declaration Cursor declaration after handler declaration Case not found for CASE statement Configuration file '%-.192s' is too big Malformed 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 table File '%-.192s' has unknown type '%-.64s' in its header '%-.192s.%-.192s' is not %s Column '%-.192s' is not updatable View's SELECT contains a subquery in the FROM clause View's SELECT contains a '%s' clause View's SELECT contains a variable or parameter View's SELECT refers to a temporary table '%-.192s' View's SELECT and view's field list have different column counts View merge algorithm can't be used here for now (assumed undefined algorithm) View being updated does not have complete key of underlying table in it View '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them Can't drop or alter a %s from within another stored routine GOTO is not allowed in a stored procedure handler Trigger already exists Trigger does not exist Trigger's '%-.192s' is view or temporary table Updating of %s row is not allowed in %strigger There is no %s row in %s trigger Field '%-.192s' doesn't have a default value Division by 0 Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ld Illegal %s '%-.192s' value found during parsing CHECK 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: %s Password hash should be a %d-digit hexadecimal number Target log not found in binlog index I/O error reading log index file Server configuration does not permit binlog purge Failed on fseek() Fatal error during log purge A purgeable log is in use, will not purge Unknown error during log purge Failed initializing relay log position: %s You are not using binary logging The '%-.64s' syntax is reserved for purposes internal to the MySQL server WSAStartup Failed Can't handle procedures with different groups yet Select must have a group with this procedure Can't use ORDER clause with this procedure Binary logging and replication forbid changing the global server %s Can't map file: %-.200s, errno: %d Wrong magic in %-.64s Prepared statement contains too many placeholders Key part '%-.192s' length cannot be 0 View text checksum failed Can not modify more than one base table through a join view '%-.192s.%-.192s' Can not insert into join view '%-.192s.%-.192s' without fields list Can not delete from join view '%-.192s.%-.192s' Operation %s failed for %.256s XAER_NOTA: Unknown XID XAER_INVAL: Invalid arguments (or unsupported command) XAER_RMFAIL: The command cannot be executed when global transaction is in the %.64s state XAER_OUTSIDE: Some work is done outside global transaction XAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistency XA_RBROLLBACK: Transaction branch was rolled back There is no such grant defined for user '%-.48s' on host '%-.64s' on routine '%-.192s' Failed to grant EXECUTE and ALTER ROUTINE privileges Failed to revoke all privileges to dropped routine Data too long for column '%s' at row %ld Bad SQLSTATE: '%s' %s: ready for connections.
Version: '%s' socket: '%s' port: %d %s Can't load value from file with fixed size rows to variable You are not allowed to create a user with GRANT Incorrect %-.32s value: '%-.128s' for function %-.32s Table definition has changed, please retry transaction Duplicate handler declared in the same block OUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE trigger Not allowed to return a result set from a %s Cannot get geometry object from data you send to the GEOMETRY field A 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 changes This 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 value Recursive 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 types Unable to connect to foreign data source: %.64s There was a problem processing the query on the foreign data source. Data source error: %-.64s The foreign data source you are trying to reference does not exist. Data source error: %-.64s Can't create federated table. The data source connection string '%-.64s' is not in the correct format The data source connection string '%-.64s' is not in the correct format Can't create federated table. Foreign data src error: %-.64s Trigger in wrong schema Thread stack overrun: %ld bytes used of a %ld byte stack, and %ld bytes needed. Use 'mysqld --thread_stack=#' to specify a bigger stack. Routine body for '%-.100s' is too long Cannot drop default keycache Display width out of range for column '%-.192s' (max = %lu) XAER_DUPID: The XID already exists Datetime function: %-.32s field overflow Can'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 manner Not allowed to set autocommit from a stored function or trigger Definer is not fully qualified View '%-.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' definer The user specified as a definer ('%-.64s'@'%-.64s') does not exist Changing 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 renamed No 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 %.192s Failed 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 functions Can't create more than max_prepared_stmt_count statements (current value: %lu) `%-.192s`.`%-.192s` contains view recursion Non-grouping field '%-.192s' is used in %-.64s clause The used table type doesn't support SPATIAL indexes Triggers can not be created on system tables Leading spaces are removed from name '%s' Failed to read auto-increment value from storage engine user name host name String '%-.70s' is too long for %s (should be no longer than %d) The target table %-.100s of the %s is not insertable-into Table '%-.64s' is differently defined or of non-MyISAM type or doesn't exist Too high level of nesting for select Name '%-.64s' has become '' First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BY The 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: %-.64s Table storage engine '%-.64s' does not support the create option '%.64s' Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partition Only %-.64s PARTITIONING can use VALUES %-.64s in partition definition MAXVALUE can only be used in last partition definition Subpartitions can only be hash partitions and by key Must define subpartitions on all partitions if on one partition Wrong number of partitions defined, mismatch with previous setting Wrong number of subpartitions defined, mismatch with previous setting Constant, random or timezone-dependent expressions in (sub)partitioning function are not allowed Expression in RANGE/LIST VALUES must be constant Field in list of fields for partition function not found in table List of fields is only allowed in KEY partitions The partition info in the frm file is not consistent with what can be written into the frm file The %-.192s function returns the wrong type For %-.64s partitions each partition must be defined VALUES LESS THAN value must be strictly increasing for each partition VALUES value must be of same type as partition function Multiple definition of same constant in list partitioning Partitioning can not be used stand-alone in query The mix of handlers in the partitions is not allowed in this version of MySQL For the partitioned engine it is necessary to define all %-.64s Too many partitions (including subpartitions) were defined It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioning Failed to create specific handler file A BLOB field is not allowed in partition function A %-.192s must include all columns in the table's partitioning function Number of %-.64s = 0 is not an allowed value Partition management on a not partitioned table is not possible Foreign keys are not yet supported in conjunction with partitioning Error in list of partitions to %-.64s Cannot remove all partitions, use DROP TABLE instead COALESCE PARTITION can only be used on HASH/KEY partitions REORGANIZE PARTITION can only be used to reorganize partitions not to change their numbers REORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs %-.64s PARTITION can only be used on RANGE/LIST partitions Trying to Add partition(s) with wrong number of subpartitions At least one partition must be added At least one partition must be coalesced More partitions to reorganize than there are partitions Duplicate partition name %-.192s It is not allowed to shut off binlog on this command When reorganizing a set of partitions they must be in consecutive order Reorganize of range partitions cannot change total ranges except for last partition where it can extend the range Partition function not supported in this version for this handler Partition state cannot be defined from CREATE/ALTER TABLE The %-.64s handler only supports 32 bit integers in VALUES Plugin '%-.192s' is not loaded Incorrect %-.32s value: '%-.128s' Table has no partition for value %-.64s It is not allowed to specify %s more than once Failed to create %s Failed to drop %s The handler doesn't support autoextend of tablespaces A size parameter was incorrectly specified, either number or on the form 10M The size number was correct but we don't allow the digit part to be more than 2 billion Failed to alter: %s Writing one row to the row-based binary log failed Table definition on master and slave does not match: %s Slave running with --log-slave-updates must use row-based binary logging to be able to replicate row-based binary log events Event '%-.192s' already exists Failed to store event %s. Error code %d from storage engine. Unknown event '%-.192s' Failed to alter event '%-.192s' Failed to drop %s INTERVAL is either not positive or too big ENDS is either invalid or before STARTS Event execution time is in the past. Event has been disabled Failed to open mysql.event No datetime expression provided Column count of mysql.%s is wrong. Expected %d, found %d. The table is probably corrupted Cannot load from mysql.%s. The table is probably corrupted Failed to delete the event from mysql.event Error during compilation of event's body Same old and new event name Data for column '%s' too long Cannot drop index '%-.192s': needed in a foreign key constraint The syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s instead You can't write-lock a log table. Only read access is possible You can't use locks with log tables. Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entry Column 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 tables Cannot change the binary logging format inside a stored function or trigger The NDB cluster engine does not support changing the binlog format on the fly yet Cannot create temporary table with partitions Partition constant is out of partition function domain This partition function is not allowed Error in DDL log Not allowed to use NULL value in VALUES LESS THAN Incorrect partition name Transaction characteristics can't be changed while a transaction is in progress ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s' Internal scheduler error %d Error during starting/stopping of the scheduler. Error code %u Engine cannot be used in partitioned tables Cannot activate '%-.64s' log The server was not built with row-based replication Decoding of base64 string failed Recursion of EVENT DDL statements is forbidden when body is present Cannot proceed because system tables used by Event Scheduler were found damaged at server start Only integers allowed as number here This storage engine cannot be used for log tables" You cannot '%s' a log table if logging is enabled Cannot 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': key '%-.192s' Too many files opened, please execute the command again Event 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: %s Table has no partition for some existing values Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %s Fatal error: %s Relay log read failure: %s Relay log write failure: %s Failed to create %s Master command %s failed: %s Binary logging not possible. Message: %s View `%-.64s`.`%-.64s` has no creation context Creation context of view `%-.64s`.`%-.64s' is invalid Creation context of stored routine `%-.64s`.`%-.64s` is invalid Corrupted TRG file for table `%-.64s`.`%-.64s` Triggers for table `%-.64s`.`%-.64s` have no creation context Trigger creation context of table `%-.64s`.`%-.64s` is invalid Creation context of event `%-.64s`.`%-.64s` is invalid Cannot open table for trigger `%-.64s`.`%-.64s` Cannot create stored routine `%-.64s`. Check warnings Ambiguous slave modes combination. %s The BINLOG statement of type `%s` was not preceded by a format description BINLOG statement. Corrupted replication event was detected Invalid column reference (%-.64s) in LOAD DATA Being purged log %s was not found XA_RBTIMEOUT: Transaction branch was rolled back: took too long XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected Prepared statement needs to be re-prepared DELAYED option not supported for table '%-.192s' The master info structure does not exist <%-.64s> option ignored Built-in plugins cannot be deleted Plugin is busy and will be uninstalled on shutdown %s variable '%s' is read-only. Use SET %s to assign the value Storage engine %s does not support rollback for this statement. Transaction rolled back and must be restarted Unexpected master's heartbeat data: %s The requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds). Bad schema for mysql.ndb_replication table. Message: %-.64s Error in parsing conflict function. Message: %-.64s Write 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 Manual Database Table Partition Subpartition Temporary Renamed Too many active concurrent transactions Non-ASCII separator arguments are not fully supported debug sync point wait timed out debug sync point hit limit reached Duplicate condition information item '%s' Unhandled user-defined warning condition Unhandled user-defined not found condition Unhandled user-defined exception condition RESIGNAL when handler not active SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE Data 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-id Query cache is disabled; restart the server with query_cache_type=1 to enable it Duplicate partition field name '%-.192s' Inconsistency in usage of column lists for partitioning Partition column values of incorrect type Too many fields in '%-.192s' Cannot use MAXVALUE as value in VALUES IN Cannot have more than one value for this type of %-.64s partitioning Row expressions in VALUES IN only allowed for multi-field column partitioning Field '%-.192s' is of a not allowed type for this type of partitioning The total length of the partitioning fields is too large Cannot 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. %s Cannot 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.%s Cannot 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: %s Column %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 transaction The 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 structure Invalid performance_schema usage. Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statement Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction Cannot change the binlog direct flag inside a stored function or trigger A SPATIAL index may only contain a geometrical type column Comment 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 clause Mixing 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 transaction Cannot change the sql_log_bin inside a stored function or trigger Failed to read from the .par file VALUES value for partition '%-.64s' must have type INT '%-.48s'@'%-.64s' 사용자는 접근이 거부 되었습니다. SET PASSWORD has no significance for users authenticating via plugins GRANT with IDENTIFIED WITH is illegal because the user %-.*s already exists Cannot truncate a table referenced in a foreign key constraint (%.192s) Plugin '%s' is force_plus_permanent and can not be unloaded The 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 again Primary 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 corrupted Undo 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 unsafe Table 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 corrupted The requested value %s for the master delay exceeds the maximum %u Only Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided) Non matching attribute '%-.64s' between partition and table Table to exchange with partition is partitioned: '%-.64s' Table to exchange with partition is temporary: '%-.64s' Subpartitioned table, use subpartition instead of partition Unknown partition '%-.64s' in table '%-.64s' Tables have different definitions Found a row that does not match the partition Option 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 long Replication 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 table Found a row not matching the given partition set partition '%-.64s' doesn't exist 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. %s The 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. %s FULLTEXT index is not supported for partitioned tables. Invalid condition number Sending 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 table Setting authentication options is not possible when only the Slave SQL Thread is being started. The table does not have FULLTEXT index to support this query The 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 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. @@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 time Cannot create FULLTEXT index on temporary InnoDB table Column '%-.192s' is of wrong type for an InnoDB FULLTEXT index Index '%-.192s' is of wrong type for an InnoDB FULLTEXT index Creating 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 corrupted Slave must silently retry current transaction There is a foreign key check running on table '%-.192s'. Cannot discard the table. Schema mismatch (%s) Table '%-.192s' in system tablespace IO Read error: (%lu, %s) %s IO Write error: (%lu, %s) %s Tablespace is missing for table %s. Tablespace '%-.192s' exists. Tablespace has been discarded for table '%-.192s' Internal error: %s ALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s' Index corrupt: %s Supports only YEAR or YEAR(4) column. Your password does not satisfy the current policy requirements You 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 tables Failed 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 NULL Duplicate 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 mode When @@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 lock Partition specific operations do not yet support LOCK/ALGORITHM Columns participating in a foreign key are renamed Cannot change column type INPLACE Adding foreign keys needs foreign_key_checks=OFF Creating unique indexes with IGNORE requires COPY algorithm to remove duplicate rows Dropping a primary key is not allowed without also adding a new primary key Adding an auto-increment column requires a lock Cannot replace hidden FTS_DOC_ID with a user-visible one Cannot drop or rename FTS_DOC_ID Fulltext index creation requires a lock sql_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 중복된 입력 값: key '%-.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_MODE Your password has expired. To log in you must change it using a client that supports expired passwords. Found a row in wrong partition %s Cannot 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 table The binary log file '%s' is logically corrupted: %s file %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 values Row 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 repository Slave failed to initialize relay log info structure from the repository Access 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 long Plugin '%s' cannot be uninstalled now. %s Cannot 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. File %s is corrupted Query 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 table Foreign 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/REPLACE Invalid size for column '%-.192s'. Table storage engine '%-.64s' found required create option missing Out 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 first Cannot create FULLTEXT index on materialized subquery Undo Log error: %s Invalid argument for logarithm This 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 exceeded Select is not a read only statement, disabling timer Duplicate 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 UNION Expression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated query Slave 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 mode Binary 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 characters Incorrect 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 view Do not support online operation on table with GIS index User variable name '%-.100s' is illegal Cannot %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 %s Expression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %s Supplied filter list contains a value which is not in the required format 'db_pattern.table_pattern' OK packet too large Invalid JSON data provided to function %s: %s Invalid 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 %s Unsupported number of coordinate dimensions in function %s: Found %u, expected %u Slave 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' first This 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_by In aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_by Updating '%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 actions Cannot 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 error Unsupported MAX_EXECUTION_TIME MAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements only Hint %s is ignored as conflicting/duplicated Query block name %s is not found for %s hint Unresolved name %s for %s hint Please 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 protocols Incorrect 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 %.*s Version 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.%-.0s The JSON binary value contains invalid data. Invalid JSON path expression. The error is around character position %u.%-.200s Cannot 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 %ld Invalid JSON value for CAST to %s%-.0s from column %s at row %ld The 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 available Session was killed Memory capacity of %llu bytes for '%s' exceeded. %s Range optimization was not done for this query. Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONING The 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: %s Write 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; %s Can not perform keyring migration : %s Access denied; you need %-.128s privileges for this operation Keyring 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 operation SUPER privilege required for '%s'@'%s' user. Could not reinitialize audit log filters. Invalid argument type Invalid argument count audit_log plugin has not been installed using INSTALL PLUGIN syntax. Invalid "max_array_length" argument type. Invalid "max_array_length" argument value. %s Filter 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%s
Mini Shell