File: //usr/share/mysql/danish/errmsg.sys
v L , { % \ M
B t # G Y $ e Y 7 x B Y
[
O m . h
g
3 F , + A > d 5 f 1 O G s , R m 6 k N ~ D 3 d Y z A L e $ O % S 3! ! !
" N" " " # I# r# # $ o$ $ $ % % % % & ;& n& & & ' l' ' ' ( ( C( j( ( ) >) x) ) '* * + ]+ + ), c, , , , ;- }- - . +. `. . . "/ D/ / / / 0 >0 [0 0 0 1 ?1 1 1 !2 j2 2 2 2 +3 M3 |3 3 4 24 e4 4 4 4 5 95 X5 }5 5 5 5 :6 6 6 7 7 87 7 7 8 ;8 \8 8 8 #9 Q9 {9 9 9 : U: : : ; 9; ; `< < < = = > 5> u> > > 0? L? ? ? "@ u@ @ @ OA }A A A B 5B gB B B B 1C FC [C pC C C C C C 7D \D D D ]E }E E E E F 4F UF jF F F F F G G 3G KG `G vG G G H 6H XH H H H I `I I I I J RJ wJ J J K iK K 3L oL L L L L -M NM {M M M M /N UN N N N O 9O kO }O O O O P /P yP P P P Q YQ |Q Q Q Q R RR R R R R 3S S S &T XT T T U @U SU U U V :V qV V W .W rW 0X X Y Z *Z tZ Z Z <[ [ [ "\ R\ \ ] v] ] ] ^ ^ ^ ^ _ B_ k_ _ G` ` -a La a b bb b b 6c nc /d td d Ie je e e =f if f f g *g bg lg vg g g >h ch h h 7i i i 9j j j j ,k ok k l Gl l l m Fm {m m m 3n en n n .o o o o 1p ^p p p
q Bq }q q Br }r r r s As bs s s Qt t t u 'u Iu qu u u u u Iv v v v w w w w x 1x Cx nx x x x y hy y y y z 2z rz z { +{ { &| | | $} R} } } } } ~ \~ ~ ~ L i b ˁ G f ! Q DŽ / X , j F l ɇ ! C ̈ ( Q i k ; o v , O y ͍ X k ̏ = А P ۑ - ۓ 2 З , { # ^ Ě | ћ U Ü f ؝ S u ՞ g % m T j W < ٦ c Ȩ ) 7 5 T Ϭ 7 s ! N p $ ˯ & q Y ű X a d Z 0 ' ݹ % L ^ & 8 ߽ 1 l G # ` ! a Q 6 # H d 1 D V # b P ) t 9 Y s U " H { # o ! 4 V N 4 - B = [ G l hashchk isamchk NEJ JA Kan ikke oprette filen '%-.200s' (Fejlkode: %d - %s) Kan ikke oprette tabellen '%-.200s' (Fejlkode: %d) Kan ikke oprette databasen '%-.192s' (Fejlkode: %d) Kan ikke oprette databasen '%-.192s'; databasen eksisterer Kan ikke slette (droppe) '%-.192s'; databasen eksisterer ikke Fejl ved sletning (drop) af databasen (kan ikke slette '%-.192s', Fejlkode %d) Fejl ved sletting af database (kan ikke slette folderen '%-.192s', Fejlkode %d) Fejl ved sletning af '%-.192s' (Fejlkode: %d - %s) Kan ikke læse posten i systemfolderen Kan ikke læse status af '%-.200s' (Fejlkode: %d - %s) Kan ikke læse aktive folder (Fejlkode: %d - %s) Kan ikke låse fil (Fejlkode: %d - %s) Kan ikke åbne fil: '%-.200s' (Fejlkode: %d - %s) Kan ikke finde fila: '%-.200s' (Fejlkode: %d - %s) Kan ikke læse folder '%-.192s' (Fejlkode: %d - %s) Kan ikke skifte folder til '%-.192s' (Fejlkode: %d - %s) Posten er ændret siden sidste læsning '%-.192s' Ikke mere diskplads (%s). Venter på at få frigjort plads... (Fejlkode: %d - %s) Kan ikke skrive, flere ens nøgler i tabellen '%-.192s' Fejl ved lukning af '%-.192s' (Fejlkode: %d - %s) Fejl ved læsning af '%-.200s' (Fejlkode: %d - %s) Fejl ved omdøbning af '%-.210s' til '%-.210s' (Fejlkode: %d - %s) Fejl ved skriving av filen '%-.200s' (Fejlkode: %d - %s) '%-.192s' er låst mod opdateringer Sortering afbrudt View '%-.192s' eksisterer ikke for '%-.192s' Modtog fejl %d fra tabel håndteringen Denne mulighed eksisterer ikke for tabeltypen '%-.192s' Kan ikke finde posten i '%-.192s' Forkert indhold i: '%-.200s' Fejl i indeksfilen til tabellen '%-.200s'; prøv at reparere den Gammel indeksfil for tabellen '%-.192s'; reparer den '%-.192s' er skrivebeskyttet Ikke mere hukommelse. Genstart serveren og prøv igen (mangler %d bytes) Ikke mere sorteringshukommelse. Øg sorteringshukommelse (sort buffer size) for serveren Uventet afslutning på fil (eof) ved læsning af filen '%-.192s' (Fejlkode: %d - %s) For mange forbindelser (connections) Udgået for tråde/hukommelse Kan ikke få værtsnavn for din adresse Forkert håndtryk (handshake) Adgang nægtet bruger: '%-.48s'@'%-.64s' til databasen '%-.192s' Adgang nægtet bruger: '%-.48s'@'%-.64s' (Bruger adgangskode: %s) Ingen database valgt Ukendt kommando Kolonne '%-.192s' kan ikke være NULL Ukendt database '%-.192s' Tabellen '%-.192s' findes allerede Ukendt tabel '%-.100s' Felt: '%-.192s' i tabel %-.192s er ikke entydigt Database nedlukning er i gang Ukendt kolonne '%-.192s' i tabel %-.192s Brugte '%-.192s' som ikke var i group by Kan ikke gruppere på '%-.192s' Udtrykket har summer (sum) funktioner og kolonner i samme udtryk Kolonne tæller stemmer ikke med antallet af værdier Navnet '%-.100s' er for langt Feltnavnet '%-.192s' findes allerede Indeksnavnet '%-.192s' findes allerede Ens værdier '%-.192s' for indeks %d Forkert kolonnespecifikaton for felt '%-.192s' %s nær '%-.80s' på linje %d Forespørgsel var tom Tabellen/aliaset: '%-.192s' er ikke unikt Ugyldig standardværdi for '%-.192s' Flere primærnøgler specificeret For mange nøgler specificeret. Kun %d nøgler må bruges For mange nøgledele specificeret. Kun %d dele må bruges Specificeret nøgle var for lang. Maksimal nøglelængde er %d Nøglefeltet '%-.192s' eksisterer ikke i tabellen BLOB feltet '%-.192s' kan ikke bruges ved specifikation af indeks For stor feltlængde for kolonne '%-.192s' (maks = %lu). Brug BLOB i stedet Der kan kun specificeres eet AUTO_INCREMENT-felt, og det skal være indekseret %s: klar til tilslutninger
Version: '%s' socket: '%s' port: %d" %s: Normal nedlukning
%s: Fangede signal %d. Afslutter!!
%s: Server lukket
%s: Forceret nedlukning af tråd: %ld bruger: '%-.48s'
Kan ikke oprette IP socket Tabellen '%-.192s' har ikke den nøgle, som blev brugt i CREATE INDEX. Genopret tabellen Felt adskiller er ikke som forventet, se dokumentationen Man kan ikke bruge faste feltlængder med BLOB. Brug i stedet 'fields terminated by'. Filen '%-.128s' skal være i database-folderen og kunne læses af alle Filen '%-.200s' eksisterer allerede Poster: %ld Fjernet: %ld Sprunget over: %ld Advarsler: %ld Poster: %ld Ens: %ld Forkert indeksdel. Den anvendte nøgledel er ikke en streng eller længden er større end nøglelængden Man kan ikke slette alle felter med ALTER TABLE. Brug DROP TABLE i stedet. Kan ikke udføre DROP '%-.192s'. Undersøg om feltet/nøglen eksisterer. Poster: %ld Ens: %ld Advarsler: %ld You can't specify target table '%-.192s' for update in FROM clause Ukendt tråd id: %lu Du er ikke ejer af tråden %lu Ingen tabeller i brug For mange tekststrenge til specifikationen af SET i kolonne %-.192s Kan ikke lave unikt log-filnavn %-.200s.(1-999)
Tabellen '%-.192s' var låst med READ lås og kan ikke opdateres Tabellen '%-.192s' var ikke låst med LOCK TABLES BLOB feltet '%-.192s' kan ikke have en standard værdi Ugyldigt database navn '%-.100s' Ugyldigt tabel navn '%-.100s' SELECT ville undersøge for mange poster og ville sandsynligvis tage meget lang tid. Undersøg WHERE delen og brug SET SQL_BIG_SELECTS=1 hvis udtrykket er korrekt Ukendt fejl Ukendt procedure %-.192s Forkert antal parametre til proceduren %-.192s Forkert(e) parametre til proceduren %-.192s Ukendt tabel '%-.192s' i %-.32s Feltet '%-.192s' er anvendt to gange Forkert brug af grupperings-funktion Tabellen '%-.192s' bruger et filtypenavn som ikke findes i denne MySQL version En tabel skal have mindst een kolonne Tabellen '%-.192s' er fuld Ukendt tegnsæt: '%-.64s' For mange tabeller. MySQL kan kun bruge %d tabeller i et join For mange felter For store poster. Max post størrelse, uden BLOB's, er %ld. Du må lave nogle felter til BLOB's Thread stack brugt: Brugt: %ld af en %ld stak. Brug 'mysqld --thread_stack=#' for at allokere en større stak om nødvendigt Krydsreferencer fundet i OUTER JOIN; check dine ON conditions Table handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handler Kan ikke læse funktionen '%-.192s' Kan ikke starte funktionen '%-.192s'; %-.80s Angivelse af sti ikke tilladt for delt bibliotek Funktionen '%-.192s' findes allerede Kan ikke åbne delt bibliotek '%-.192s' (errno: %d %-.128s) Kan ikke finde funktionen '%-.128s' i bibliotek Funktionen '%-.192s' er ikke defineret Værten '%-.64s' er blokeret på grund af mange fejlforespørgsler. Lås op med 'mysqladmin flush-hosts' Værten '%-.64s' kan ikke tilkoble denne MySQL-server Du bruger MySQL som anonym bruger. Anonyme brugere må ikke ændre adgangskoder Du skal have tilladelse til at opdatere tabeller i MySQL databasen for at ændre andres adgangskoder Kan ikke finde nogen tilsvarende poster i bruger tabellen Poster fundet: %ld Ændret: %ld Advarsler: %ld Kan ikke danne en ny tråd (fejl nr. %d). Hvis computeren ikke er løbet tør for hukommelse, kan du se i brugervejledningen for en mulig operativ-system - afhængig fejl Kolonne antallet stemmer ikke overens med antallet af værdier i post %ld Kan ikke genåbne tabel '%-.192s Forkert brug af nulværdi (NULL) Fik fejl '%-.64s' fra regexp Sammenblanding af GROUP kolonner (MIN(),MAX(),COUNT()...) uden GROUP kolonner er ikke tilladt, hvis der ikke er noget GROUP BY prædikat Denne tilladelse findes ikke for brugeren '%-.48s' på vært '%-.64s' %-.128s-kommandoen er ikke tilladt for brugeren '%-.48s'@'%-.64s' for tabellen '%-.64s' %-.16s-kommandoen er ikke tilladt for brugeren '%-.48s'@'%-.64s' for kolonne '%-.192s' in tabellen '%-.192s' Forkert GRANT/REVOKE kommando. Se i brugervejledningen hvilke privilegier der kan specificeres. Værts- eller brugernavn for langt til GRANT Tabellen '%-.192s.%-.192s' eksisterer ikke Denne tilladelse eksisterer ikke for brugeren '%-.48s' på vært '%-.64s' for tabellen '%-.192s' Den brugte kommando er ikke tilladt med denne udgave af MySQL Der er en fejl i SQL syntaksen Forsinket indsættelse tråden (delayed insert thread) kunne ikke opnå lås på tabellen %-.192s For mange slettede tråde (threads) i brug Afbrudt forbindelse %ld til database: '%-.192s' bruger: '%-.48s' (%-.64s) Modtog en datapakke som var større end 'max_allowed_packet' Fik læsefejl fra forbindelse (connection pipe) Fik fejlmeddelelse fra fcntl() Modtog ikke datapakker i korrekt rækkefølge Kunne ikke dekomprimere kommunikations-pakke (communication packet) Fik fejlmeddelelse ved læsning af kommunikations-pakker (communication packets) Timeout-fejl ved læsning af kommunukations-pakker (communication packets) Fik fejlmeddelelse ved skrivning af kommunukations-pakker (communication packets) Timeout-fejl ved skrivning af kommunukations-pakker (communication packets) Strengen med resultater er større end 'max_allowed_packet' Denne tabeltype understøtter ikke brug af BLOB og TEXT kolonner Denne tabeltype understøtter ikke brug af AUTO_INCREMENT kolonner INSERT DELAYED kan ikke bruges med tabellen '%-.192s', fordi tabellen er låst med LOCK TABLES Forkert kolonnenavn '%-.100s' Den brugte tabeltype kan ikke indeksere kolonnen '%-.192s' Tabellerne i MERGE er ikke defineret ens Kan ikke skrive til tabellen '%-.192s' fordi det vil bryde CONSTRAINT regler BLOB kolonnen '%-.192s' brugt i nøglespecifikation uden nøglelængde Alle dele af en PRIMARY KEY skal være NOT NULL; Hvis du skal bruge NULL i nøglen, brug UNIQUE istedet Resultatet bestod af mere end een række Denne tabeltype kræver en primærnøgle Denne udgave af MySQL er ikke oversat med understøttelse af RAID Du bruger sikker opdaterings modus ('safe update mode') og du forsøgte at opdatere en tabel uden en WHERE klausul, der gør brug af et KEY felt Nøglen '%-.192s' eksisterer ikke i tabellen '%-.192s' Kan ikke åbne tabellen Denne tabeltype understøtter ikke %s Du må ikke bruge denne kommando i en transaktion Modtog fejl %d mens kommandoen COMMIT blev udført Modtog fejl %d mens kommandoen ROLLBACK blev udført Modtog fejl %d mens kommandoen FLUSH_LOGS blev udført Modtog fejl %d mens kommandoen CHECKPOINT blev udført Afbrød forbindelsen %ld til databasen '%-.192s' bruger: '%-.48s' vært: '%-.64s' (%-.64s) Denne tabeltype unserstøtter ikke binært tabeldump Binlog closed, cannot RESET MASTER Kunne ikke genopbygge indekset for den dumpede tabel '%-.192s' Fejl fra master: '%-.64s' Netværksfejl ved læsning fra master Netværksfejl ved skrivning til master Kan ikke finde en FULLTEXT nøgle som svarer til kolonne listen Kan ikke udføre den givne kommando fordi der findes aktive, låste tabeller eller fordi der udføres en transaktion Ukendt systemvariabel '%-.64s' Tabellen '%-.192s' er markeret med fejl og bør repareres Tabellen '%-.192s' er markeret med fejl og sidste (automatiske?) REPAIR fejlede Advarsel: Visse data i tabeller der ikke understøtter transaktioner kunne ikke tilbagestilles Fler-udtryks transaktion krævede mere plads en 'max_binlog_cache_size' bytes. Forhøj værdien af denne variabel og prøv igen Denne handling kunne ikke udføres med kørende slave, brug først kommandoen STOP SLAVE Denne handling kræver en kørende slave. Konfigurer en slave og brug kommandoen START SLAVE Denne server er ikke konfigureret som slave. Ret in config-filen eller brug kommandoen CHANGE MASTER TO Could not initialize master info structure; more error messages can be found in the MySQL error log Kunne ikke danne en slave-tråd; check systemressourcerne Brugeren %-.64s har allerede mere end 'max_user_connections' aktive forbindelser Du må kun bruge konstantudtryk med SET Lock wait timeout overskredet Det totale antal låse overstiger størrelsen på låse-tabellen Update lås kan ikke opnås under en READ UNCOMMITTED transaktion DROP DATABASE er ikke tilladt mens en tråd holder på globalt read lock CREATE DATABASE er ikke tilladt mens en tråd holder på globalt read lock Incorrect arguments to %s '%-.48s'@'%-.64s' is not allowed to create new users Incorrect table definition; all MERGE tables must be in the same database Deadlock found when trying to get lock; try restarting transaction The used table type doesn't support FULLTEXT indexes Cannot add foreign key constraint Cannot add or update a child row: a foreign key constraint fails Cannot delete or update a parent row: a foreign key constraint fails Error connecting to master: %-.128s Error running query on master: %-.128s Error when executing command %s: %-.128s Incorrect usage of %s and %s The used SELECT statements have a different number of columns Can't execute the query because you have a conflicting read lock Mixing of transactional and non-transactional tables is disabled Option '%s' used twice in statement User '%-.64s' has exceeded the '%s' resource (current value: %ld) Access denied; you need (at least one of) the %-.128s privilege(s) for this operation Variable '%-.64s' is a SESSION variable and can't be used with SET GLOBAL Variable '%-.64s' is a GLOBAL variable and should be set with SET GLOBAL Variable '%-.64s' doesn't have a default value Variable '%-.64s' can't be set to the value of '%-.200s' Incorrect argument type to variable '%-.64s' Variable '%-.64s' can only be set, not read Incorrect usage/placement of '%s' This version of MySQL doesn't yet support '%s' Got fatal error %d from master when reading data from binary log: '%-.320s' Slave SQL thread ignored the query because of replicate-*-table rules Variable '%-.192s' is a %s variable Incorrect foreign key definition for '%-.192s': %s Key reference and table reference don't match Operand should contain %d column(s) Subquery returns more than 1 row Unknown prepared statement handler (%.*s) given to %s Help database is corrupt or does not exist Cyclic reference on subqueries Converting column '%s' from %s to %s Reference '%-.64s' not supported (%s) Every derived table must have its own alias Select %u was reduced during optimization Table '%-.192s' from one of the SELECTs cannot be used in %-.32s Client does not support authentication protocol requested by server; consider upgrading MySQL client All parts of a SPATIAL index must be NOT NULL COLLATION '%s' is not valid for CHARACTER SET '%s' Slave is already running Slave already has been stopped Uncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted) ZLIB: Not enough memory ZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted) ZLIB: Input data corrupted Row %u was cut by GROUP_CONCAT() Row %ld doesn't contain data for all columns Row %ld was truncated; it contained more data than there were input columns Column set to default value; NULL supplied to NOT NULL column '%s' at row %ld Out of range value for column '%s' at row %ld Data truncated for column '%s' at row %ld Using storage engine %s for table '%s' Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s' Cannot drop one or more of the requested users Can't revoke all privileges for one or more of the requested users Illegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s' Illegal mix of collations for operation '%s' Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name) Unknown collation: '%-.64s' SSL parameters in CHANGE MASTER are ignored because this MySQL slave was compiled without SSL support; they can be used later if MySQL slave with SSL is started Server is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new format Field or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%d Incorrect parameter or combination of parameters for START SLAVE UNTIL It is recommended to use --skip-slave-start when doing step-by-step replication with START SLAVE UNTIL; otherwise, you will get problems if you get an unexpected slave's mysqld restart SQL thread is not to be started so UNTIL options are ignored Incorrect index name '%-.100s' Incorrect catalog name '%-.100s' Query cache failed to set size %lu; new query cache size is %lu Column '%-.192s' cannot be part of FULLTEXT index Unknown key cache '%-.100s' MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to work Unknown storage engine '%s' '%s' is deprecated and will be removed in a future release. Please use %s instead The target table %-.100s of the %s is not updatable The '%s' feature is disabled; you need MySQL built with '%s' to have it working The MySQL server is running with the %s option so it cannot execute this statement Column '%-.100s' has duplicated value '%-.64s' in %s Truncated incorrect %-.32s value: '%-.128s' Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause Invalid ON UPDATE clause for '%-.192s' column This command is not supported in the prepared statement protocol yet Modtog fejl %d '%-.100s' fra %s Modtog temporary fejl %d '%-.100s' fra %s Unknown or incorrect time zone: '%-.64s' Invalid TIMESTAMP value in column '%s' at row %ld Invalid %s character string: '%.64s' Result of %s() was larger than max_allowed_packet (%ld) - truncated Conflicting declarations: '%s%s' and '%s%s' Can't create a %s from within another stored routine %s %s already exists %s %s does not exist Failed to DROP %s %s Failed to CREATE %s %s %s with no matching label: %s Redefining label %s End-label %s without match Referring to uninitialized variable %s PROCEDURE %s can't return a result set in the given context RETURN is only allowed in a FUNCTION %s is not allowed in stored procedures The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored. The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN. Query execution was interrupted Incorrect number of arguments for %s %s; expected %u, got %u Undefined CONDITION: %s No RETURN found in FUNCTION %s FUNCTION %s ended without RETURN Cursor statement must be a SELECT Cursor SELECT must not have INTO Undefined CURSOR: %s Cursor is already open Cursor is not open Undeclared variable: %s Incorrect number of FETCH variables No data - zero rows fetched, selected, or processed Duplicate parameter: %s Duplicate variable: %s Duplicate condition: %s Duplicate cursor: %s Failed to ALTER %s %s Subquery value not supported %s is not allowed in stored function or trigger Variable or condition declaration after cursor or handler declaration Cursor declaration after handler declaration Case not found for CASE statement Configuration file '%-.192s' is too big Malformed file type header in file '%-.192s' Unexpected end of file while parsing comment '%-.200s' Error while parsing parameter '%-.192s' (line: '%-.192s') Unexpected end of file while skipping unknown parameter '%-.192s' EXPLAIN/SHOW can not be issued; lacking privileges for underlying table File '%-.192s' has unknown type '%-.64s' in its header '%-.192s.%-.192s' is not %s Column '%-.192s' is not updatable View's SELECT contains a subquery in the FROM clause View's SELECT contains a '%s' clause View's SELECT contains a variable or parameter View's SELECT refers to a temporary table '%-.192s' View's SELECT and view's field list have different column counts View merge algorithm can't be used here for now (assumed undefined algorithm) View being updated does not have complete key of underlying table in it View '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them Can't drop or alter a %s from within another stored routine GOTO is not allowed in a stored procedure handler Trigger already exists Trigger does not exist Trigger's '%-.192s' is view or temporary table Updating of %s row is not allowed in %strigger There is no %s row in %s trigger Field '%-.192s' doesn't have a default value Division by 0 Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ld Illegal %s '%-.192s' value found during parsing CHECK OPTION on non-updatable view '%-.192s.%-.192s' CHECK OPTION failed '%-.192s.%-.192s' %-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s' Failed purging old relay logs: %s Password hash should be a %d-digit hexadecimal number Target log not found in binlog index I/O error reading log index file Server configuration does not permit binlog purge Failed on fseek() Fatal error during log purge A purgeable log is in use, will not purge Unknown error during log purge Failed initializing relay log position: %s You are not using binary logging The '%-.64s' syntax is reserved for purposes internal to the MySQL server WSAStartup Failed Can't handle procedures with different groups yet Select must have a group with this procedure Can't use ORDER clause with this procedure Binary logging and replication forbid changing the global server %s Can't map file: %-.200s, errno: %d Wrong magic in %-.64s Prepared statement contains too many placeholders Key part '%-.192s' length cannot be 0 View text checksum failed Can not modify more than one base table through a join view '%-.192s.%-.192s' Can not insert into join view '%-.192s.%-.192s' without fields list Can not delete from join view '%-.192s.%-.192s' Operation %s failed for %.256s XAER_NOTA: Unknown XID XAER_INVAL: Invalid arguments (or unsupported command) XAER_RMFAIL: The command cannot be executed when global transaction is in the %.64s state XAER_OUTSIDE: Some work is done outside global transaction XAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistency XA_RBROLLBACK: Transaction branch was rolled back There is no such grant defined for user '%-.48s' on host '%-.64s' on routine '%-.192s' Failed to grant EXECUTE and ALTER ROUTINE privileges Failed to revoke all privileges to dropped routine Data too long for column '%s' at row %ld Bad SQLSTATE: '%s' %s: ready for connections.
Version: '%s' socket: '%s' port: %d %s Can't load value from file with fixed size rows to variable You are not allowed to create a user with GRANT Incorrect %-.32s value: '%-.128s' for function %-.32s Table definition has changed, please retry transaction Duplicate handler declared in the same block OUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE trigger Not allowed to return a result set from a %s Cannot get geometry object from data you send to the GEOMETRY field A routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changes This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable) You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable) You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it. The statement (%lu) has no open cursor. Explicit or implicit commit is not allowed in stored function or trigger. Field of view '%-.192s.%-.192s' underlying table doesn't have a default value Recursive stored functions and triggers are not allowed. Too big scale %d specified for column '%-.192s'. Maximum is %lu. Too big precision %d specified for 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 types Unable to connect to foreign data source: %.64s There was a problem processing the query on the foreign data source. Data source error: %-.64s The foreign data source you are trying to reference does not exist. Data source error: %-.64s Can't create federated table. The data source connection string '%-.64s' is not in the correct format The data source connection string '%-.64s' is not in the correct format Can't create federated table. Foreign data src error: %-.64s Trigger in wrong schema Thread stack overrun: %ld bytes used of a %ld byte stack, and %ld bytes needed. Use 'mysqld --thread_stack=#' to specify a bigger stack. Routine body for '%-.100s' is too long Cannot drop default keycache Display width out of range for column '%-.192s' (max = %lu) XAER_DUPID: The XID already exists Datetime function: %-.32s field overflow Can't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger. The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'. The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive manner Not allowed to set autocommit from a stored function or trigger Definer is not fully qualified View '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view! You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definer The user specified as a definer ('%-.64s'@'%-.64s') does not exist Changing schema from '%-.192s' to '%-.192s' is not allowed. Cannot delete or update a parent row: a foreign key constraint fails (%.192s) Cannot add or update a child row: a foreign key constraint fails (%.192s) Variable '%-.64s' must be quoted with `...`, or renamed No definer attribute for trigger '%-.192s'.'%-.192s'. The trigger will be activated under the authorization of the invoker, which may have insufficient privileges. Please recreate the trigger. '%-.192s' has an old format, you should re-create the '%s' object(s) Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192s Failed to load routine %-.192s. The table mysql.proc is missing, corrupt, or contains bad data (internal code %d) Incorrect routine name '%-.192s' Table upgrade required. Please do "REPAIR TABLE `%-.32s`" or dump/reload to fix it! AGGREGATE is not supported for stored functions Can't create more than max_prepared_stmt_count statements (current value: %lu) `%-.192s`.`%-.192s` contains view recursion Non-grouping field '%-.192s' is used in %-.64s clause The used table type doesn't support SPATIAL indexes Triggers can not be created on system tables Leading spaces are removed from name '%s' Failed to read auto-increment value from storage engine user name host name String '%-.70s' is too long for %s (should be no longer than %d) The target table %-.100s of the %s is not insertable-into Table '%-.64s' is differently defined or of non-MyISAM type or doesn't exist Too high level of nesting for select Name '%-.64s' has become '' First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BY The foreign server, %s, you are trying to create already exists. The foreign server name you are trying to reference does not exist. Data source error: %-.64s Table storage engine '%-.64s' does not support the create option '%.64s' Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partition Only %-.64s PARTITIONING can use VALUES %-.64s in partition definition MAXVALUE can only be used in last partition definition Subpartitions can only be hash partitions and by key Must define subpartitions on all partitions if on one partition Wrong number of partitions defined, mismatch with previous setting Wrong number of subpartitions defined, mismatch with previous setting Constant, random or timezone-dependent expressions in (sub)partitioning function are not allowed Expression in RANGE/LIST VALUES must be constant Field in list of fields for partition function not found in table List of fields is only allowed in KEY partitions The partition info in the frm file is not consistent with what can be written into the frm file The %-.192s function returns the wrong type For %-.64s partitions each partition must be defined VALUES LESS THAN value must be strictly increasing for each partition VALUES value must be of same type as partition function Multiple definition of same constant in list partitioning Partitioning can not be used stand-alone in query The mix of handlers in the partitions is not allowed in this version of MySQL For the partitioned engine it is necessary to define all %-.64s Too many partitions (including subpartitions) were defined It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioning Failed to create specific handler file A BLOB field is not allowed in partition function A %-.192s must include all columns in the table's partitioning function Number of %-.64s = 0 is not an allowed value Partition management on a not partitioned table is not possible Foreign key clause is not yet supported in conjunction with partitioning Error in list of partitions to %-.64s Cannot remove all partitions, use DROP TABLE instead COALESCE PARTITION can only be used on HASH/KEY partitions REORGANIZE PARTITION can only be used to reorganize partitions not to change their numbers REORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs %-.64s PARTITION can only be used on RANGE/LIST partitions Trying to Add partition(s) with wrong number of subpartitions At least one partition must be added At least one partition must be coalesced More partitions to reorganize than there are partitions Duplicate partition name %-.192s It is not allowed to shut off binlog on this command When reorganizing a set of partitions they must be in consecutive order Reorganize of range partitions cannot change total ranges except for last partition where it can extend the range Partition function not supported in this version for this handler Partition state cannot be defined from CREATE/ALTER TABLE The %-.64s handler only supports 32 bit integers in VALUES Plugin '%-.192s' is not loaded Incorrect %-.32s value: '%-.128s' Table has no partition for value %-.64s It is not allowed to specify %s more than once Failed to create %s Failed to drop %s The handler doesn't support autoextend of tablespaces A size parameter was incorrectly specified, either number or on the form 10M The size number was correct but we don't allow the digit part to be more than 2 billion Failed to alter: %s Writing one row to the row-based binary log failed Table definition on master and slave does not match: %s Slave running with --log-slave-updates must use row-based binary logging to be able to replicate row-based binary log events Event '%-.192s' already exists Failed to store event %s. Error code %d from storage engine. Unknown event '%-.192s' Failed to alter event '%-.192s' Failed to drop %s INTERVAL is either not positive or too big ENDS is either invalid or before STARTS Event execution time is in the past. Event has been disabled Failed to open mysql.event No datetime expression provided Column count of mysql.%s is wrong. Expected %d, found %d. The table is probably corrupted Cannot load from mysql.%s. The table is probably corrupted Failed to delete the event from mysql.event Error during compilation of event's body Same old and new event name Data for column '%s' too long Cannot drop index '%-.192s': needed in a foreign key constraint The syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s instead You can't write-lock a log table. Only read access is possible You can't use locks with log tables. Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entry Column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please use mysql_upgrade to fix this error. Cannot switch out of the row-based binary log format when the session has open temporary tables Cannot change the binary logging format inside a stored function or trigger The NDB cluster engine does not support changing the binlog format on the fly yet Cannot create temporary table with partitions Partition constant is out of partition function domain This partition function is not allowed Error in DDL log Not allowed to use NULL value in VALUES LESS THAN Incorrect partition name Transaction characteristics can't be changed while a transaction is in progress ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s' Internal scheduler error %d Error during starting/stopping of the scheduler. Error code %u Engine cannot be used in partitioned tables Cannot activate '%-.64s' log The server was not built with row-based replication Decoding of base64 string failed Recursion of EVENT DDL statements is forbidden when body is present Cannot proceed because system tables used by Event Scheduler were found damaged at server start Only integers allowed as number here This storage engine cannot be used for log tables" You cannot '%s' a log table if logging is enabled Cannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s' Incorrect parameter count in the call to native function '%-.192s' Incorrect parameters in the call to native function '%-.192s' Incorrect parameters in the call to stored function '%-.192s' This function '%-.192s' has the same name as a native function Ens værdier '%-.64s' for indeks '%-.192s' Too many files opened, please execute the command again Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation. Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future. The incident %s occured on the master. Message: %-.64s Table has no partition for some existing values Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %s Fatal error: %s Relay log read failure: %s Relay log write failure: %s Failed to create %s Master command %s failed: %s Binary logging not possible. Message: %s View `%-.64s`.`%-.64s` has no creation context Creation context of view `%-.64s`.`%-.64s' is invalid Creation context of stored routine `%-.64s`.`%-.64s` is invalid Corrupted TRG file for table `%-.64s`.`%-.64s` Triggers for table `%-.64s`.`%-.64s` have no creation context Trigger creation context of table `%-.64s`.`%-.64s` is invalid Creation context of event `%-.64s`.`%-.64s` is invalid Cannot open table for trigger `%-.64s`.`%-.64s` Cannot create stored routine `%-.64s`. Check warnings Ambiguous slave modes combination. %s The BINLOG statement of type `%s` was not preceded by a format description BINLOG statement. Corrupted replication event was detected Invalid column reference (%-.64s) in LOAD DATA Being purged log %s was not found XA_RBTIMEOUT: Transaction branch was rolled back: took too long XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected Prepared statement needs to be re-prepared DELAYED option not supported for table '%-.192s' The master info structure does not exist <%-.64s> option ignored Built-in plugins cannot be deleted Plugin is busy and will be uninstalled on shutdown %s variable '%s' is read-only. Use SET %s to assign the value Storage engine %s does not support rollback for this statement. Transaction rolled back and must be restarted Unexpected master's heartbeat data: %s The requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds). Bad schema for mysql.ndb_replication table. Message: %-.64s Error in parsing conflict function. Message: %-.64s Write to exceptions table failed. Message: %-.128s" Comment for table '%-.64s' is too long (max = %lu) Comment for field '%-.64s' is too long (max = %lu) FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference Manual Database Table Partition Subpartition Temporary Renamed Too many active concurrent transactions Non-ASCII separator arguments are not fully supported debug sync point wait timed out debug sync point hit limit reached Duplicate condition information item '%s' Unhandled user-defined warning condition Unhandled user-defined not found condition Unhandled user-defined exception condition RESIGNAL when handler not active SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE Data truncated for condition item '%s' Data too long for condition item '%s' Unknown locale: '%-.64s' The requested server id %d clashes with the slave startup option --replicate-same-server-id Query cache is disabled; restart the server with query_cache_type=1 to enable it Duplicate partition field name '%-.192s' Inconsistency in usage of column lists for partitioning Partition column values of incorrect type Too many fields in '%-.192s' Cannot use MAXVALUE as value in VALUES IN Cannot have more than one value for this type of %-.64s partitioning Row expressions in VALUES IN only allowed for multi-field column partitioning Field '%-.192s' is of a not allowed type for this type of partitioning The total length of the partitioning fields is too large Cannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved. Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging. Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %s Cannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging. Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%s Cannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT. Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted. The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves. Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly. Statement is unsafe because it uses a UDF which may not return the same value on the slave. Statement is unsafe because it uses a system variable that may have a different value on the slave. Statement is unsafe because it uses a system function that may return a different value on the slave. Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction. %s Statement: %s Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s' Can't create conversion table for table '%-.192s.%-.192s' Cannot modify @@session.binlog_format inside a transaction The path specified for %.64s is too long. '%s' is deprecated and will be removed in a future release. Native table '%-.64s'.'%-.64s' has the wrong structure Invalid performance_schema usage. Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statement Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction Cannot change the binlog direct flag inside a stored function or trigger A SPATIAL index may only contain a geometrical type column Comment for index '%-.64s' is too long (max = %lu) Wait on a lock was aborted due to a pending exclusive lock %s value is out of range in '%s' A variable of a non-integer based type in LIMIT clause Mixing self-logging and non-self-logging engines in a statement is unsafe. Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them. Cannot modify @@session.sql_log_bin inside a transaction Cannot change the sql_log_bin inside a stored function or trigger Failed to read from the .par file VALUES value for partition '%-.64s' must have type INT Adgang nægtet bruger: '%-.48s'@'%-.64s' SET PASSWORD has no significance for users authenticating via plugins GRANT with IDENTIFIED WITH is illegal because the user %-.*s already exists Cannot truncate a table referenced in a foreign key constraint (%.192s) Plugin '%s' is force_plus_permanent and can not be unloaded The requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled. The requested value for the heartbeat period exceeds the value of `slave_net_timeout' seconds. A sensible value for the period should be less than the timeout. Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try again Primary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'. Table rebuild required. Please do "ALTER TABLE `%-.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 corrupted Undo log record is too big. INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave. INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on master and the slave. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave. CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave. Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it. Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. CREATE TABLE... SELECT... on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on master and the slave. INSERT... ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Table is being used in foreign key check. Storage engine '%s' does not support system tables. [%s.%s] INSERT into autoincrement field which is not the first part in the composed primary key is unsafe. Cannot load from %s.%s. The table is probably corrupted The requested value %s for the master delay exceeds the maximum %u Only Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided) Non matching attribute '%-.64s' between partition and table Table to exchange with partition is partitioned: '%-.64s' Table to exchange with partition is temporary: '%-.64s' Subpartitioned table, use subpartition instead of partition Unknown partition '%-.64s' in table '%-.64s' Tables have different definitions Found a row that does not match the partition Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size. Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s' Table to exchange with partition has foreign key references: '%-.64s' Key value '%-.192s' was not found in table '%-.192s.%-.192s' Data for column '%s' too long Replication event checksum verification failed while reading from network. Replication event checksum verification failed while reading from a log file. Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size. Can't update table '%-.192s' while '%-.192s' is being created. PARTITION () clause on non partitioned table Found a row not matching the given partition set partition '%-.64s' eksisterer ikke Failure while changing the type of replication repository: %s. The creation of some temporary tables could not be rolled back. Some temporary tables were dropped, but these operations could not be rolled back. %s is not supported in multi-threaded slave mode. %s The number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata. Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s. %s FULLTEXT index is not supported for partitioned tables. Invalid condition number Sending passwords in plain text without SSL/TLS is extremely insecure. Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information. Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s' Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child table Setting authentication options is not possible when only the Slave SQL Thread is being started. The table does not have FULLTEXT index to support this query The system variable %.200s cannot be set in stored functions or triggers. The system variable %.200s cannot be set when there is an ongoing transaction. The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST. The system variable @@SESSION.GTID_NEXT cannot change inside a transaction. The statement 'SET %.200s' cannot invoke a stored function. The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL. Skipping transaction %.200s because it has already been executed and logged. Malformed GTID set specification '%.200s'. Malformed GTID set encoding. Malformed GTID specification '%.200s'. Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the server with a new server_uuid. Parameters MASTER_LOG_FILE, MASTER_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when MASTER_AUTO_POSITION is active. CHANGE MASTER TO MASTER_AUTO_POSITION = 1 can only be executed when @@GLOBAL.GTID_MODE = ON. Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT != AUTOMATIC. @@GLOBAL.GTID_MODE = ON or UPGRADE_STEP_2 requires @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1. @@GLOBAL.GTID_MODE = ON or UPGRADE_STEP_1 or UPGRADE_STEP_2 requires --log-bin and --log-slave-updates. @@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF. @@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON. @@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF. Found a Gtid_log_event or Previous_gtids_log_event when @@GLOBAL.GTID_MODE = OFF. When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables. CREATE TABLE ... SELECT is forbidden when @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1. When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, the statements CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can be executed in a non-transactional context only, and require that AUTOCOMMIT = 1. These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions. The value of @@GLOBAL.GTID_MODE can only change one step at a time: OFF <-> UPGRADE_STEP_1 <-> UPGRADE_STEP_2 <-> ON. Also note that this value must be stepped up or down simultaneously on all servers; see the Manual for instructions. The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires. @@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK. Unknown EXPLAIN format name: '%s' Cannot execute statement in a READ ONLY transaction. Comment for table partition '%-.64s' is too long (max = %lu) Slave is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a slave. Additional error messages can be found in the MySQL error log. InnoDB presently supports one FULLTEXT index creation at a time Cannot create FULLTEXT index on temporary InnoDB table Column '%-.192s' is of wrong type for an InnoDB FULLTEXT index Index '%-.192s' is of wrong type for an InnoDB FULLTEXT index Creating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again. Unknown ALGORITHM '%s' Unknown LOCK type '%s' CHANGE MASTER cannot be executed when the slave was stopped with an error or killed in MTS mode. Consider using RESET SLAVE or START SLAVE UNTIL. Cannot recover after SLAVE errored out in parallel execution mode. Additional error messages can be found in the MySQL error log. Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log. Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted Slave must silently retry current transaction There is a foreign key check running on table '%-.192s'. Cannot discard the table. Schema mismatch (%s) Table '%-.192s' in system tablespace IO Read error: (%lu, %s) %s IO Write error: (%lu, %s) %s Tablespace is missing for table '%-.192s' Tablespace for table '%-.192s' exists. Please DISCARD the tablespace before IMPORT. Tablespace has been discarded for table '%-.192s' Internal error: %s ALTER TABLE '%-.192s' IMPORT TABLESPACE failed with error %lu : '%s' Index corrupt: %s YEAR(%lu) column type is deprecated. Creating YEAR(4) column instead. Your password does not satisfy the current policy requirements You must SET PASSWORD before executing this statement Failed to add the foreign key constaint. Missing index for constraint '%s' in the foreign table '%s' Failed to add the foreign key constaint. Missing index for constraint '%s' in the referenced table '%s' Failed to add the foreign key constraint '%s' to system tables Failed to open the referenced table '%s' Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s' Duplicate foreign key constraint name '%s' The password hash doesn't have the expected format. Check if the correct password algorithm is being used with the PASSWORD() function. Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s' Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULL Duplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release. Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s' Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s' Malformed communication packet. Running in read-only mode When @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'. The system variable %.200s cannot be set in stored procedures. @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON. @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty. @@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients). @@GLOBAL.GTID_PURGED was changed from '%s' to '%s'. @@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'. Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to. %s is not supported for this operation. Try %s. %s is not supported. Reason: %s. Try %s. COPY algorithm requires a lock Partition specific operations do not yet support LOCK/ALGORITHM Columns participating in a foreign key are renamed Cannot change column type INPLACE Adding foreign keys needs foreign_key_checks=OFF Creating unique indexes with IGNORE requires COPY algorithm to remove duplicate rows Dropping a primary key is not allowed without also adding a new primary key Adding an auto-increment column requires a lock Cannot replace hidden FTS_DOC_ID with a user-visible one Cannot drop or rename FTS_DOC_ID Fulltext index creation requires a lock sql_slave_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transaction Flere ens nøgler for indeks '%-.192s' Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'. cannot silently convert NULL values, as required in this SQL_MODE Your password has expired. To log in you must change it using a client that supports expired passwords. Found a row in wrong partition %s Cannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of slave_pending_jobs_size_max. Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB table The binary log file '%s' is logically corrupted: %s file %s was not purged because it was being read by %d thread(s), purged only %d out of %d files. file %s was not purged because it is the active log file. Auto-increment value in UPDATE conflicts with internally generated values Row events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s' Slave failed to initialize master info structure from the repository Slave failed to initialize relay log info structure from the repository Access denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting. InnoDB is in read only mode. STOP SLAVE command execution is incomplete: Slave SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete. STOP SLAVE command execution is incomplete: Slave IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete. Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data. Temporary file write failure. Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index. TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format. Operation not allowed when innodb_forced_recovery > 0. The initialization vector supplied to %s is too short. Must be at least %d bytes long Plugin '%s' cannot be uninstalled now. %s Cannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'. Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been committed on master but are not included in GTID_EXECUTED.