Your IP : 172.28.240.42

Current Path : /usr/share/mysql/korean/
Upload File :
Current File : //usr/share/mysql/korean/errmsg.sys

A`PqacH.c9*n5			z


,<d!
C


)Jq*sNA\~E)K3$X	X%W-LpTNx2x1c m   ~!!Z""#X##J$y$$$;%%&&&S''	(X(~((!))))7*i***+a+++,N,,,,5-s--.9.`...-/>/k/////0m0001'1E1a1112P222\333I444/5^5556T666627u777
8R8v8888!9b999	:_:::!;Z;;;;<P<<<<=?=`====>+>W>>>'?U????/@G@@@@A]AAAB*BkBBB$CQCCCbDD@EE@F}FFFF/GKGGG&HZHHH2I^IIJJJiJJJJKVKKKKKK
L+L?LZLLLL	MM7NWNNNNNO/ODO[OnOOOOO
P%P:PPPmPPPQ2QZQQQQ:RRRRR,SQSSSSCTT
UIU{UUUUV(VUVcVVV	W/WuWWWWXEXWXtXXXX	YSYeYYYY3ZVZlZZZZ,[p[[[[
\h\\]2]]]]^-^r^^^_K_x__`L`
aabbbcNcccd[ddd,eeePffffygggghEhh!iij&jjj<kxkklHl	mNmm#nDnnnoCoyooop<pFpPpppq=qYqqrprrsZssstIttt!ucuuu vUvvv
w?wwwxjxxxy8yxyyyzWzz{W{{{{|<|q||+}m}}}~#~K~z~~~~#{wӀHpȁB}҂Ls`,c͆6&Cw܈<aƉb!`ŋB&Ӎ-\Ҏ?~AǐX̑&>aҒ@gԓDxޔKTZdq{$Nw͖-Tz@i˘W%WY՝aޞceˡPa3]УQ*];(J§TبrZث
AWsD)ƯP$"x޴hashchkisamchk아니오예화일 '%-.200s'를 만들지 못했습니다. (에러번호: %d)테이블 '%-.200s'를 만들지 못했습니다. (에러번호: %d)데이타베이스 '%-.192s'를 만들지 못했습니다.. (에러번호: %d)데이타베이스 '%-.192s'를 만들지 못했습니다.. 데이타베이스가 존재함데이타베이스 '%-.192s'를 제거하지 못했습니다. 데이타베이스가 존재하지 않음 데이타베이스 제거 에러('%-.192s'를 삭제할 수 없읍니다, 에러번호: %d)데이타베이스 제거 에러(rmdir '%-.192s'를 할 수 없읍니다, 에러번호: %d)'%-.192s' 삭제 중 에러 (에러번호: %d)system 테이블에서 레코드를 읽을 수 없습니다.'%-.200s'의 상태를 얻지 못했습니다. (에러번호: %d)수행 디렉토리를 찾지 못했습니다. (에러번호: %d)화일을 잠그지(lock) 못했습니다. (에러번호: %d)화일을 열지 못했습니다.: '%-.200s' (에러번호: %d)화일을 찾지 못했습니다.: '%-.200s' (에러번호: %d)'%-.192s'디렉토리를 읽지 못했습니다. (에러번호: %d)'%-.192s'디렉토리로 이동할 수 없었습니다. (에러번호: %d)테이블 '%-.192s'에서 마지막으로 읽은 후 Record가 변경되었습니다.Disk full (%s). 다른 사람이 지울때까지 기다립니다...기록할 수 없읍니다., 테이블 '%-.192s'에서 중복 키'%-.192s'닫는 중 에러 (에러번호: %d)'%-.200s'화일 읽기 에러 (에러번호: %d)'%-.210s'를 '%-.210s'로 이름 변경중 에러 (에러번호: %d)'%-.200s'화일 기록 중 에러 (에러번호: %d)'%-.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)너무 많은 연결... 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 conditionsTable 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 카운터와 일치하지 않습니다.테이블을 다시 열수 없군요: '%-.192sNULL 값을 잘못 사용하셨군요...regexp에서 '%-.64s'가 났습니다.Mixing of GROUP 칼럼s (MIN(),MAX(),COUNT(),...) with no GROUP 칼럼s is illegal if there is no GROUP BY clause사용자 '%-.48s' (호스트 '%-.64s')를 위하여 정의된 그런 승인은 없습니다.'%-.16s' 명령은 다음 사용자에게 거부되었습니다. : '%-.48s'@'%-.64s' for 테이블 '%-.192s''%-.16s' 명령은 다음 사용자에게 거부되었습니다. : '%-.48s'@'%-.64s' for 칼럼 '%-.192s' in 테이블 '%-.192s'잘못된 GRANT/REVOKE 명령. 어떤 권리와 승인이 사용되어 질 수 있는지 메뉴얼을 보시오.승인(GRANT)을 위하여 사용한 사용자나 호스트의 값들이 너무 깁니다.테이블 '%-.192s.%-.192s' 는 존재하지 않습니다.사용자 '%-.48s'(호스트 '%-.64s')는 테이블 '%-.192s'를 사용하기 위하여 정의된 승인은 없습니다. 사용된 명령은 현재의 MySQL 버젼에서는 이용되지 않습니다.SQL 구문에 오류가 있습니다.지연된 insert 쓰레드가 테이블 %-.192s의 요구된 락킹을 처리할 수 없었습니다.너무 많은 지연 쓰레드를 사용하고 있습니다.데이타베이스 접속을 위한 연결 %ld가 중단됨 : '%-.192s' 사용자: '%-.48s' (%-.64s)'max_allowed_packet'보다 더큰 패킷을 받았습니다.연결 파이프로부터 에러가 발생하였습니다.fcntl() 함수로부터 에러가 발생하였습니다.순서가 맞지않는 패킷을 받았습니다.통신 패킷의 압축해제를 할 수 없었습니다.통신 패킷을 읽는 중 오류가 발생하였습니다.통신 패킷을 읽는 중 timeout이 발생하였습니다.통신 패킷을 기록하는 중 오류가 발생하였습니다.통신 패팃을 기록하는 중 timeout이 발생하였습니다.Result string is longer than 'max_allowed_packet' bytesThe used table type doesn't support BLOB/TEXT columnsThe used table type doesn't support AUTO_INCREMENT columnsINSERT DELAYED can't be used with table '%-.192s', because it is locked with LOCK TABLESIncorrect column name '%-.100s'The used table handler can't index column '%-.192s'All tables in the MERGE table are not defined identicallyCan't write, because of unique constraint, to table '%-.192s'BLOB column '%-.192s' used in key specification without a key lengthAll parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE insteadResult consisted of more than one rowThis table type requires a primary keyThis version of MySQL is not compiled with RAID supportYou are using safe update mode and you tried to update a table without a WHERE that uses a KEY columnKey '%-.192s' doesn't exist in table '%-.192s'Can't open tableThe handler for the table doesn't support %sYou are not allowed to execute this command in a transactionGot error %d during COMMITGot error %d during ROLLBACKGot error %d during FLUSH_LOGSGot error %d during CHECKPOINTAborted connection %ld to db: '%-.192s' user: '%-.48s' host: '%-.64s' (%-.64s)The storage engine for the table does not support binary table dumpBinlog closed, cannot RESET MASTERFailed rebuilding the index of  dumped table '%-.192s'Error from master: '%-.64s'Net error reading from masterNet error writing to masterCan't find FULLTEXT index matching the column listCan't execute the given command because you have active locked tables or an active transactionUnknown system variable '%-.64s'Table '%-.192s' is marked as crashed and should be repairedTable '%-.192s' is marked as crashed and last (automatic?) repair failedSome non-transactional changed tables couldn't be rolled backMulti-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try againThis operation cannot be performed with a running slave; run STOP SLAVE firstThis operation requires a running slave; configure slave and do START SLAVEThe server is not configured as slave; fix in config file or with CHANGE MASTER TOCould not initialize master info structure; more error messages can be found in the MySQL error logCould not create slave thread; check system resourcesUser %-.64s already has more than 'max_user_connections' active connectionsYou may only use constant expressions with SETLock wait timeout exceeded; try restarting transactionThe total number of locks exceeds the lock table sizeUpdate locks cannot be acquired during a READ UNCOMMITTED transactionDROP DATABASE not allowed while thread is holding global read lockCREATE DATABASE not allowed while thread is holding global read lockIncorrect arguments to %s'%-.48s'@'%-.64s' is not allowed to create new usersIncorrect table definition; all MERGE tables must be in the same databaseDeadlock found when trying to get lock; try restarting transactionThe used table type doesn't support FULLTEXT indexesCannot add foreign key constraintCannot add or update a child row: a foreign key constraint failsCannot delete or update a parent row: a foreign key constraint failsError connecting to master: %-.128sError running query on master: %-.128sError when executing command %s: %-.128sIncorrect usage of %s and %sThe used SELECT statements have a different number of columnsCan't execute the query because you have a conflicting read lockMixing of transactional and non-transactional tables is disabledOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need (at least one of) the %-.128s privilege(s) for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect 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 rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Slave is already runningSlave already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing 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 usersCan't revoke all privileges for one or more of the requested usersIllegal 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 startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START SLAVE UNTILIt 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 restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.32s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown 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. This option will be removed in MySQL 5.6.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN. This option will be removed in MySQL 5.6.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 schemaThread 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 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)The target table %-.100s of the %s is not insertable-intoTable '%-.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 isolation level 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': key '%-.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 dropped immediately after creation.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.