NG4R3P

Linux 4gvps.4gvps.com 3.10.0-1127.18.2.vz7.163.46 #1 SMP Fri Nov 20 21:47:55 MSK 2020 x86_64
SOFT : Apache PHP : 7.4.33
/usr/share/mysql/spanish/

38.135.39.45

[ NAME ]	[ SIZE ]	[ PERM ]	[ DATE ]	[ ACT ]
+FILE +DIR
errmsg.sys	61.261 KB	-rwxr-xr-x	2021-01-21 20:22	R E G D
REQUEST EXIT

þþçyHs¦é/vÉû-f–Âõ,f£é<u¦ÚS{¼äKx½ùi» #L‚”â# A U | ¾ Ú ) X æ RxœÉ%;^ˆûH Á n¾=U¦ÿU±0lŒ [›Ê 8`tžÓJ}¦Ç]o‘ÇùFh°Ø÷!`nðzÂ:]»ØJoÜ'”A|St±"k¶{¿áD € £ ë !Q!„!¶!Ó!ò!""V"‰"Ä"û"0#r#¹#$>$$Ã$%`%Ã%í%&T&Ç&÷&'B'…'¦'É'î'(k(¦(É() )@)h)³)*7*v*Ð*+›+ñ+J,,-R-›-Í-ò-8.•.ñ.O/j/§/ 0a0•0Ä0 1U1z1§1¼1×12`2¥2Ð23Z3¨3û3'4m4¡4Þ4505‚5Ñ5÷556l6Ž6³6í67?7g77¼7ê7,88Ö89&9;9Í9ú9‚:²:Ó:;l;º;è;<M<<¿<=e=–=ó=>Á>Q?ª?ó?»@þ@%ALA¡AØAøAyB™BÆBùB_C¸CíCDœDÏDE3E\E…E·EÜE FLFF–F«FÀF×FõF G$GKG‡G¬GÓG5HHÍH I"IAIbI„I¥IºIÑIäIüI JTJlJƒJ›J°JÆJãJKYK†K¨KÐKýK4LnL°LøL/MKMmM¢MÇMöM*NkN¹NOƒO¿OñOPPNP}PžPËPÙPQJQQ¥QëQ RCRhR‰R»RÍRêRS3S^SSÉSÛS T:TeT©TÌTâTU:UTU¢UæUV5VLVƒVÞVWvW¨WÿW4XgXX£XèX$YTYŠYÁYîYQZ~ZÂZ€[E\Ø\R]z]Ä]^K^Œ^Ñ^!_r_¢_```Æ`aLadaïab3bob’b»bGc—c=d}dœdeoe²eîeii¹iïi#jPjzj²j¼jÆjkAkŽk³kÏkFl‡læl/m‰mÐmn|^|¸|ó|}H}d}‚}Â}~V~{~é~vÖ"€t€¢€Ù€C\¬‚1‚p‚œ‚¹‚í‚ƒRƒ²ƒ×ƒ „<„Ø„…Y…—…Ö… †A†¾†B‡y‡©‡ˆˆ:ˆVˆjˆ‡ˆ°ˆßˆ‰U‰„‰Â‰Š8ŠhŠžŠÄŠ!‹J‹y‹›‹Û‹$ŒOŒ€Œ©ŒÁŒäŒUÃêWŽ“ŽÇŽûŽ.aÎ×Ýçôþ.d„§Ñú%‘P‘q‘°‘×‘ý‘’r’Ã’ì’$“N“k“•“Ú“(”o”¨”3•Ú•…–3—Ü—X˜ä˜a™æ™Šš(›„›è›NœÓœäœA{¶àžSžužÔž)ŸrŸŸàŸ < s ¾ 0¡i¡«¡Í¡¢2¢x¢Ä¢£H£â£‚¤¥q¥Ê¥¦H¦}¦±¦Ç¦ã¦´§™¨e©6ª «À«%¬†¬”’®è®¯N¯±¯é¯,°”°Ð° ±B±~±«±Í±û±²â²(³e³ƒ³Î³´¶´õ´"µSµpµ¯µïµB¶w¶û¶¸·»·ó·¸S¸h¹ä¹Qº±ºîº8»‡»ö»B¼~¼ç¼4½_½|½£½5¾µ¾¿}¿×¿?ÀÀÜÀ6ÁˆÁrÂÃÂÄÅ:Æ¿ÆáÆÇSÇÈTÈ‹ÈÊÈÉ„É›É²ÉDÊÆÊ)Ë€Ë®ËÌÌ;ÌWÌtÌžÌòÌ$Í7Í|ÍŽÍÔÍÎIÎ®ÎÏUÏ~ÏçÏÐšÐåÐCÑžÑÒgÒÅÒ,ÓLÓfÓHÔ‡ÔÊÔÕ~Õ²ÕèÕƒÖ³ÖÜÖûÖ;×n××Á×ØbØ’ØËØìØÙìÙÚ€ÚÂÚ*ÛLÛ×ÛÜDÜ¦ÜàÜ*Ý–ÝÛÝ#ÞÞžÞ8ßÐß3àQà²àá=á“á½ábâä$åŽåhashchkisamchkNOSINo puedo crear archivo '%-.200s' (Error: %d - %s)No puedo crear tabla '%-.200s' (Error: %d)No puedo crear base de datos '%-.192s' (Error: %d)No puedo crear base de datos '%-.192s'; la base de datos ya existeNo puedo eliminar base de datos '%-.192s'; la base de datos no existeError eliminando la base de datos(no puedo borrar '%-.192s', error %d)Error eliminando la base de datos (No puedo borrar directorio '%-.192s', error %d)Error en el borrado de '%-.192s' (Error: %d - %s)No puedo leer el registro en la tabla del sistemaNo puedo obtener el estado de '%-.200s' (Error: %d - %s)No puedo acceder al directorio (Error: %d - %s)No puedo bloquear archivo: (Error: %d - %s)No puedo abrir archivo: '%-.200s' (Error: %d - %s)No puedo encontrar archivo: '%-.200s' (Error: %d - %s)No puedo leer el directorio de '%-.192s' (Error: %d - %s)No puedo cambiar al directorio de '%-.192s' (Error: %d - %s)El registro ha cambiado desde la ultima lectura de la tabla '%-.192s'Disco lleno (%s). Esperando para que se libere algo de espacio... (Error: %d - %s)No puedo escribir, clave duplicada en la tabla '%-.192s'Error en el cierre de '%-.192s' (Error: %d - %s)Error leyendo el fichero '%-.200s' (Error: %d - %s)Error en el renombrado de '%-.210s' a '%-.210s' (Error: %d - %s)Error escribiendo el archivo '%-.200s' (Error: %d - %s)'%-.192s' esta bloqueado contra cambiosOrdeancion canceladaLa vista '%-.192s' no existe para '%-.192s'Error %d desde el manejador de la tablaEl manejador de la tabla de '%-.192s' no tiene esta opcionNo puedo encontrar el registro en '%-.192s'Informacion erronea en el archivo: '%-.200s'Clave de archivo erronea para la tabla: '%-.200s'; intente repararloClave de archivo antigua para la tabla '%-.192s'; reparelo!'%-.192s' es de solo lecturaMemoria insuficiente. Reinicie el demonio e intentelo otra vez (necesita %d bytes)Memoria de ordenacion insuficiente. Incremente el tamano del buffer de ordenacionInesperado fin de ficheroU mientras leiamos el archivo '%-.192s' (Error: %d - %s)Demasiadas conexionesMemoria/espacio de tranpaso insuficienteNo puedo obtener el nombre de maquina de tu direccionProtocolo erroneoAcceso negado para usuario: '%-.48s'@'%-.64s' para la base de datos '%-.192s'Acceso negado para usuario: '%-.48s'@'%-.64s' (Usando clave: %s)Base de datos no seleccionadaComando desconocidoLa columna '%-.192s' no puede ser nulaBase de datos desconocida '%-.192s'La tabla '%-.192s' ya existeTabla '%-.100s' desconocidaLa columna: '%-.192s' en %-.192s es ambiguaDesconexion de servidor en procesoLa columna '%-.192s' en %-.192s es desconocidaUsado '%-.192s' el cual no esta group byNo puedo agrupar por '%-.192s'El estamento tiene funciones de suma y columnas en el mismo estamentoLa columna con count no tiene valores para contarEl nombre del identificador '%-.100s' es demasiado grandeNombre de columna duplicado '%-.192s'Nombre de clave duplicado '%-.192s'Entrada duplicada '%-.192s' para la clave %dEspecificador de columna erroneo para la columna '%-.192s'%s cerca '%-.80s' en la linea %dLa query estaba vaciaTabla/alias: '%-.192s' es no unicaValor por defecto invalido para '%-.192s'Multiples claves primarias definidasDemasiadas claves primarias declaradas. Un maximo de %d claves son permitidasDemasiadas partes de clave declaradas. Un maximo de %d partes son permitidasDeclaracion de clave demasiado larga. La maxima longitud de clave es %dLa columna clave '%-.192s' no existe en la tablaLa columna Blob '%-.192s' no puede ser usada en una declaracion de claveLongitud de columna demasiado grande para la columna '%-.192s' (maximo = %lu).Usar BLOB en su lugarPuede ser solamente un campo automatico y este debe ser definido como una clave%s: preparado para conexiones Version: '%s' socket: '%s' port: %d"%s: Apagado normal %s: Recibiendo signal %d. Abortando! %s: Apagado completado %s: Forzando a cerrar el thread %ld usuario: '%-.48s' No puedo crear IP socketLa tabla '%-.192s' no tiene indice como el usado en CREATE INDEX. Crea de nuevo la tablaLos separadores de argumentos del campo no son los especificados. Comprueba el manualNo puedes usar longitudes de filas fijos con BLOBs. Por favor usa 'campos terminados por '.El archivo '%-.128s' debe estar en el directorio de la base de datos o ser de lectura por todosEl archivo '%-.200s' ya existeRegistros: %ld Borrados: %ld Saltados: %ld Peligros: %ldRegistros: %ld Duplicados: %ldParte de la clave es erronea. Una parte de la clave no es una cadena o la longitud usada es tan grande como la parte de la claveNo puede borrar todos los campos con ALTER TABLE. Usa DROP TABLE para hacerloNo puedo ELIMINAR '%-.192s'. compuebe que el campo/clave existeRegistros: %ld Duplicados: %ld Peligros: %ldYou can't specify target table '%-.192s' for update in FROM clauseIdentificador del thread: %lu desconocidoTu no eres el propietario del thread%luNo ha tablas usadasMuchas strings para columna %-.192s y SETNo puede crear un unico archivo log %-.200s.(1-999) Tabla '%-.192s' fue trabada con un READ lock y no puede ser actualizadaTabla '%-.192s' no fue trabada con LOCK TABLESCampo Blob '%-.192s' no puede tener valores patronNombre de base de datos ilegal '%-.100s'Nombre de tabla ilegal '%-.100s'El SELECT puede examinar muchos registros y probablemente con mucho tiempo. Verifique tu WHERE y usa SET SQL_BIG_SELECTS=1 si el SELECT esta correctoError desconocidoProcedimiento desconocido %-.192sEquivocado parametro count para procedimiento %-.192sEquivocados parametros para procedimiento %-.192sTabla desconocida '%-.192s' in %-.32sCampo '%-.192s' especificado dos vecesInvalido uso de funciÃ³n en grupoTabla '%-.192s' usa una extensiÃ³n que no existe en esta MySQL versiÃ³nUna tabla debe tener al menos 1 columnaLa tabla '%-.192s' estÃ¡ llenaJuego de caracteres desconocido: '%-.64s'Muchas tablas. MySQL solamente puede usar %d tablas en un joinMuchos camposTamaÃ±o de lÃnea muy grande. MÃ¡ximo tamaÃ±o de lÃnea, no contando blob, es %ld. Tu tienes que cambiar algunos campos para blobSobrecarga de la pila de thread: Usada: %ld de una %ld pila. Use 'mysqld --thread_stack=#' para especificar una mayor pila si necesarioDependencia cruzada encontrada en OUTER JOIN. Examine su condiciÃ³n ONTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerNo puedo cargar funciÃ³n '%-.192s'No puedo inicializar funciÃ³n '%-.192s'; %-.80sNo pasos permitidos para librarias conjugadasFunciÃ³n '%-.192s' ya existeNo puedo abrir libraria conjugada '%-.192s' (errno: %d %-.128s)No puedo encontrar funciÃ³n '%-.128s' en librariaFunciÃ³n '%-.192s' no estÃ¡ definidaServidor '%-.64s' estÃ¡ bloqueado por muchos errores de conexiÃ³n. Desbloquear con 'mysqladmin flush-hosts'Servidor '%-.64s' no estÃ¡ permitido para conectar con este servidor MySQLTu estÃ¡s usando MySQL como un usuario anonimo y usuarios anonimos no tienen permiso para cambiar las clavesTu debes de tener permiso para actualizar tablas en la base de datos mysql para cambiar las claves para otrosNo puedo encontrar una lÃnea correponsdiente en la tabla userLÃneas correspondientes: %ld Cambiadas: %ld Avisos: %ldNo puedo crear un nuevo thread (errno %d). Si tu estÃ¡ con falta de memoria disponible, tu puedes consultar el Manual para posibles problemas con SOEl nÃºmero de columnas no corresponde al nÃºmero en la lÃnea %ldNo puedo reabrir tabla: '%-.192sInvalido uso de valor NULLObtenido error '%-.64s' de regexpMezcla de columnas GROUP (MIN(),MAX(),COUNT()...) con no GROUP columnas es ilegal si no hat la clausula GROUP BYNo existe permiso definido para usuario '%-.48s' en el servidor '%-.64s'%-.128s comando negado para usuario: '%-.48s'@'%-.64s' para tabla '%-.64s'%-.16s comando negado para usuario: '%-.48s'@'%-.64s' para columna '%-.192s' en la tabla '%-.192s'Ilegal comando GRANT/REVOKE. Por favor consulte el manual para cuales permisos pueden ser usados.El argumento para servidor o usuario para GRANT es demasiado grandeTabla '%-.192s.%-.192s' no existeNo existe tal permiso definido para usuario '%-.48s' en el servidor '%-.64s' en la tabla '%-.192s'El comando usado no es permitido con esta versiÃ³n de MySQLAlgo estÃ¡ equivocado en su sintaxThread de inserciÃ³n retarda no pudiendo bloquear para la tabla %-.192sMuchos threads retardados en usoConexiÃ³n abortada %ld para db: '%-.192s' usuario: '%-.48s' (%-.64s)Obtenido un paquete mayor que 'max_allowed_packet'Obtenido un error de lectura de la conexiÃ³n pipeObtenido un error de fcntl()Obtenido paquetes desordenadosNo puedo descomprimir paquetes de comunicaciÃ³nObtenido un error leyendo paquetes de comunicaciÃ³nObtenido timeout leyendo paquetes de comunicaciÃ³nObtenido un error de escribiendo paquetes de comunicaciÃ³nObtenido timeout escribiendo paquetes de comunicaciÃ³nLa string resultante es mayor que max_allowed_packetEl tipo de tabla usada no permite soporte para columnas BLOB/TEXTEl tipo de tabla usada no permite soporte para columnas AUTO_INCREMENTINSERT DELAYED no puede ser usado con tablas '%-.192s', porque esta bloqueada con LOCK TABLESIncorrecto nombre de columna '%-.100s'El manipulador de tabla usado no puede indexar columna '%-.192s'Todas las tablas en la MERGE tabla no estan definidas identicamenteNo puedo escribir, debido al Ãºnico constraint, para tabla '%-.192s'Columna BLOB column '%-.192s' usada en especificaciÃ³n de clave sin tamaÃ±o de la claveTodas las partes de un PRIMARY KEY deben ser NOT NULL; Si necesitas NULL en una clave, use UNIQUEResultado compuesto de mas que una lÃneaEste tipo de tabla necesita de una primary keyEsta versiÃ³n de MySQL no es compilada con soporte RAIDTu estÃ¡s usando modo de actualizaciÃ³n segura y tentado actualizar una tabla sin un WHERE que usa una KEY columnaClave '%-.192s' no existe en la tabla '%-.192s'No puedo abrir tablaEl manipulador de la tabla no permite soporte para %sNo tienes el permiso para ejecutar este comando en una transiciÃ³nObtenido error %d durante COMMITObtenido error %d durante ROLLBACKObtenido error %d durante FLUSH_LOGSObtenido error %d durante CHECKPOINTAbortada conexiÃ³n %ld para db: '%-.192s' usuario: '%-.48s' servidor: '%-.64s' (%-.64s)El manipulador de tabla no soporta dump para tabla binariaBinlog closed, cannot RESET MASTERFalla reconstruyendo el indice de la tabla dumped '%-.192s'Error del master: '%-.64s'Error de red leyendo del masterError de red escribiendo para el masterNo puedo encontrar Ãndice FULLTEXT correspondiendo a la lista de columnasNo puedo ejecutar el comando dado porque tienes tablas bloqueadas o una transiciÃ³n activaDesconocida variable de sistema '%-.64s'Tabla '%-.192s' estÃ¡ marcada como crashed y debe ser reparadaTabla '%-.192s' estÃ¡ marcada como crashed y la Ãºltima reparaciÃ³n (automactica?) fallÃ³Aviso: Algunas tablas no transancionales no pueden tener rolled backMultipla transiciÃ³n necesita mas que 'max_binlog_cache_size' bytes de almacenamiento. Aumente esta variable mysqld y tente de nuevoEsta operaciÃ³n no puede ser hecha con el esclavo funcionando, primero use STOP SLAVEEsta operaciÃ³n necesita el esclavo funcionando, configure esclavo y haga el START SLAVEEl servidor no estÃ¡ configurado como esclavo, edite el archivo config file o con CHANGE MASTER TOCould not initialize master info structure; more error messages can be found in the MySQL error logNo puedo crear el thread esclavo, verifique recursos del sistemaUsario %-.64s ya tiene mas que 'max_user_connections' conexiones activasTu solo debes usar expresiones constantes con SETTiempo de bloqueo de espera excedidoEl nÃºmero total de bloqueos excede el tamaÃ±o de bloqueo de la tablaBloqueos de actualizaciÃ³n no pueden ser adqueridos durante una transiciÃ³n READ UNCOMMITTEDDROP DATABASE no permitido mientras un thread estÃ¡ ejerciendo un bloqueo de lectura globalCREATE DATABASE no permitido mientras un thread estÃ¡ ejerciendo un bloqueo de lectura globalArgumentos errados para %s'%-.48s`@`%-.64s` no es permitido para crear nuevos usuariosIncorrecta definiciÃ³n de la tabla; Todas las tablas MERGE deben estar en el mismo banco de datosEncontrado deadlock cuando tentando obtener el bloqueo; Tente recomenzar la transiciÃ³nEl tipo de tabla usada no soporta Ãndices FULLTEXTNo puede adicionar clave extranjera constraintNo puede adicionar una lÃnea hijo: falla de clave extranjera constraintNo puede deletar una lÃnea padre: falla de clave extranjera constraintError de coneccion a master: %-.128sError executando el query en master: %-.128sError de %s: %-.128sEquivocado uso de %s y %sEl comando SELECT usado tiene diferente nÃºmero de columnasNo puedo ejecutar el query porque usted tiene conflicto de traba de lecturaMezla de transancional y no-transancional tablas estÃ¡ deshabilitadaOpciÃ³n '%s' usada dos veces en el comandoUsuario '%-.64s' ha excedido el recurso '%s' (actual valor: %ld)Acceso negado. Usted necesita el privilegio %-.128s para esta operaciÃ³nVariable '%-.64s' es una SESSION variable y no puede ser usada con SET GLOBALVariable '%-.64s' es una GLOBAL variable y no puede ser configurada con SET GLOBALVariable '%-.64s' no tiene un valor patrÃ³nVariable '%-.64s' no puede ser configurada para el valor de '%-.200s'Tipo de argumento equivocado para variable '%-.64s'Variable '%-.64s' solamente puede ser configurada, no leÃdaEquivocado uso/colocaciÃ³n de '%s'Esta versiÃ³n de MySQL no soporta todavia '%s'RecibiÃ³ fatal error %d: '%-.512s' del master cuando leyendo datos del binary logSlave SQL thread ignorado el query debido a las reglas de replicaciÃ³n-*-tablaVariable '%-.192s' es una %s variableEquivocada definiciÃ³n de llave extranjera para '%-.192s': %sReferencia de llave y referencia de tabla no coincidenOperando debe tener %d columna(s)Subconsulta retorna mas que 1 lÃneaDesconocido preparado comando handler (%.*s) dado para %sBase de datos Help estÃ¡ corrupto o no existeCÃclica referencia en subconsultasConvirtiendo columna '%s' de %s para %sReferencia '%-.64s' no soportada (%s)Cada tabla derivada debe tener su propio aliasSelect %u fuÃ© reducido durante optimizaciÃ³nTabla '%-.192s' de uno de los SELECT no puede ser usada en %-.32sCliente no soporta protocolo de autenticaciÃ³n solicitado por el servidor; considere actualizar el cliente MySQLTodas las partes de una SPATIAL index deben ser NOT NULLCOLLATION '%s' no es vÃ¡lido para CHARACTER SET '%s'Slave ya estÃ¡ funcionandoSlave ya fuÃ© paradoTamaÃ±o demasiado grande para datos descomprimidos. El mÃ¡ximo tamaÃ±o es %d. (probablemente, extensiÃ³n de datos descomprimidos fuÃ© corrompida)Z_MEM_ERROR: No suficiente memoria para zlibZ_BUF_ERROR: No suficiente espacio en el bÃºfer de salida para zlib (probablemente, extensiÃ³n de datos descomprimidos fuÃ© corrompida)ZLIB: Dato de entrada fuÃ© corrompido para zlibRow %u was cut by GROUP_CONCAT()LÃnea %ld no contiene datos para todas las columnasLÃnea %ld fuÃ© truncada; La misma contine mas datos que las que existen en las columnas de entradaDatos truncado, NULL suministrado para NOT NULL columna '%s' en la lÃnea %ldOut of range value for column '%s' at row %ldDatos truncados para columna '%s' en la lÃnea %ldUsando motor de almacenamiento %s para tabla '%s'Ilegal mezcla de collations (%s,%s) y (%s,%s) para operaciÃ³n '%s'Cannot drop one or more of the requested usersNo puede revocar todos los privilegios, derecho para uno o mas de los usuarios solicitadosIlegal mezcla de collations (%s,%s), (%s,%s), (%s,%s) para operaciÃ³n '%s'Ilegal mezcla de collations para operaciÃ³n '%s'Variable '%-.64s' no es una variable componente (No puede ser usada como XXXX.variable_name)Collation desconocida: '%-.64s'Parametros SSL en CHANGE MASTER son ignorados porque este slave MySQL fue compilado sin soporte SSL; pueden ser usados despues cuando el slave MySQL con SSL sea inicializadoServidor estÃ¡ rodando en modo --secure-auth, pero '%s'@'%s' tiene clave en el antiguo formato; por favor cambie la clave para el nuevo formatoCampo o referencia '%-.192s%s%-.192s%s%-.192s' de SELECT #%d fue resolvido en SELECT #%dParametro equivocado o combinaciÃ³n de parametros para START SLAVE UNTILEs recomendado rodar con --skip-slave-start cuando haciendo replicaciÃ³n step-by-step con START SLAVE UNTIL, a menos que usted no estÃ© seguro en caso de inesperada reinicializaciÃ³n del mysqld slaveSQL thread no es inicializado tal que opciones UNTIL son ignoradasNombre de Ãndice incorrecto '%-.100s'Nombre de catalog incorrecto '%-.100s'Query cache fallada para configurar tamaÃ±o %lu, nuevo tamaÃ±o de query cache es %luColumna '%-.192s' no puede ser parte de FULLTEXT indexDesconocida key cache '%-.100s'MySQL esta inicializado en modo --skip-name-resolve. Usted necesita reinicializarlo sin esta opciÃ³n para este derecho funcionarDesconocido motor de tabla '%s''%s' estÃ¡ desaprobado, use '%s' en su lugarLa tabla destino %-.100s del %s no es actualizableEl recurso '%s' fue deshabilitado; usted necesita construir MySQL con '%s' para tener eso funcionandoEl servidor MySQL estÃ¡ rodando con la opciÃ³n %s tal que no puede ejecutar este comandoColumna '%-.100s' tiene valor doblado '%-.64s' en %sEquivocado truncado %-.32s valor: '%-.128s'Incorrecta definiciÃ³n de tabla; Solamente debe haber una columna TIMESTAMP con CURRENT_TIMESTAMP en DEFAULT o ON UPDATE clÃ¡usulaInvÃ¡lido ON UPDATE clÃ¡usula para campo '%-.192s'This 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.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'View's SELECT and view's field list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.64s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s' socket: '%s' port: %d %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too big precision %d specified for column '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error: %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error: %-.64sTrigger in wrong 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 characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tables"You cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function '%-.192s'This function '%-.192s' has the same name as a native functionEntrada duplicada '%-.64s' para la clave '%-.192s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occured on the master. Message: %-.64sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sMaster command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous slave modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The master info structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected master's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128s"Comment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the slave startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the slave.Statement is unsafe because it uses a system variable that may have a different value on the slave.Statement is unsafe because it uses a system function that may return a different value on the slave.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTAcceso negado para usuario: '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `slave_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.32s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on master and the slave.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave.CREATE TABLE... SELECT... on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on master and the slave.INSERT... ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the master delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setParticion '%-.64s' no existeFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded slave mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Slave SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the server with a new server_uuid.Parameters MASTER_LOG_FILE, MASTER_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when MASTER_AUTO_POSITION is active.CHANGE MASTER TO MASTER_AUTO_POSITION = 1 can only be executed when @@GLOBAL.GTID_MODE = ON.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT != AUTOMATIC.@@GLOBAL.GTID_MODE = ON or UPGRADE_STEP_2 requires @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1.@@GLOBAL.GTID_MODE = ON or UPGRADE_STEP_1 or UPGRADE_STEP_2 requires --log-bin and --log-slave-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event or Previous_gtids_log_event when @@GLOBAL.GTID_MODE = OFF.When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.CREATE TABLE ... SELECT is forbidden when @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1.When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, the statements CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can be executed in a non-transactional context only, and require that AUTOCOMMIT = 1. These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only change one step at a time: OFF <-> UPGRADE_STEP_1 <-> UPGRADE_STEP_2 <-> ON. Also note that this value must be stepped up or down simultaneously on all servers; see the Manual for instructions.The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires. Replicate the missing transactions from elsewhere, or provision a new slave from backup. Consider increasing the master's binary log expiration period. %s.@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Slave is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a slave. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE MASTER cannot be executed when the slave was stopped with an error or killed in MTS mode. Consider using RESET SLAVE or START SLAVE UNTIL.Cannot recover after SLAVE errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedSlave must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table '%-.192s'Tablespace for table '%-.192s' exists. Please DISCARD the tablespace before IMPORT.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE '%-.192s' IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sYEAR(%lu) column type is deprecated. Creating YEAR(4) column instead.Your password does not satisfy the current policy requirementsYou must SET PASSWORD before executing this statementFailed to add the foreign key constaint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constaint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format. Check if the correct password algorithm is being used with the PASSWORD() function.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_slave_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionEntrada duplicada para la clave '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of slave_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Slave failed to initialize master info structure from the repositorySlave failed to initialize relay log info structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP SLAVE command execution is incomplete: Slave SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP SLAVE command execution is incomplete: Slave IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_forced_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been committed on master but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.