Chapter 2 Server Error Message Reference The MySQL server writes some error messages to its error log, and sends others to client programs. Example server-side error messages written to the error log:

2018-10-28T13:01:32.735983Z 0 [Note] [MY-010303] [Server] Skipping
generation of SSL certificates as options related to SSL are specified.
2018-10-02T03:20:39.410387Z 768 [ERROR] [MY-010045] [Server] Event Scheduler:
[evtuser@localhost][myschema.e_daily] Unknown database 'mydb'

Example server-side error message sent to client programs, as displayed by the mysql client:

mysql> SELECT * FROM no_such_table;
ERROR 1146 (42S02): Table 'test.no_such_table' doesn't exist

Each server error message includes an error code, SQLSTATE value, and message string, as described in Error Message Sources and Elements . These elements are available as described in Error Information Interfaces . In addition to the errors in the following list, the server can also produce error messages that have error codes in the range from 1 to 999. See Chapter 4, Global Error Message Reference Extended EXPLAIN format generates Note messages. ER_YES is used in the Code column for these messages in subsequent SHOW WARNINGS output. InnoDB reports this error when a table cannot be created. If the error message refers to error 150, table creation failed because a foreign key constraint was not correctly formed. If the error message refers to error −1, table creation probably failed because the table includes a column name that matched the name of an internal InnoDB table. Drop the database first if you really want to replace an existing database, or add an IF NOT EXISTS clause to the CREATE DATABASE statement if to retain an existing database without having the statement produce an error. Check the %d value to see what the OS error means. For example, 28 indicates that you have run out of disk space. Message: Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space %s = location of column (for example, "field list") Likely cause: A column appears in a query without appropriate qualification, such as in a select list or ON clause. Examples:

mysql> SELECT i FROM t INNER JOIN t AS t2;
ERROR 1052 (23000): Column 'i' in field list is ambiguous
mysql> SELECT * FROM t LEFT JOIN t AS t2 ON i = i;
ERROR 1052 (23000): Column 'i' in on clause is ambiguous

Resolution: Message: Incorrect prefix key; the used key part isn't a string, the used length is longer than the key part, or the storage engine doesn't support unique prefix keys This error occurs for attempts to select from and modify the same table within a single statement. If the select attempt occurs within a derived table, you can avoid this error by setting the derived_merge flag of the optimizer_switch system variable to force the subquery to be materialized into a temporary table, which effectively causes it to be a different table from the one modified. See Optimizing Derived Tables, View References, and Common Table Expressions with Merging or Materialization . Message: The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay InnoDB reports this error when the system tablespace runs out of free space. Reconfigure the system tablespace to add a new data file. Message: Row size too large. The maximum row size for the used table type, not counting BLOBs, is %ld. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs Message: Can't create a new thread (errno %d); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug Message: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use Message: Multi-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try again InnoDB reports this error when lock wait timeout expires. The statement that waited too long was rolled back (not the entire transaction ). You can increase the value of the innodb_lock_wait_timeout configuration option if SQL statements should wait longer for other transactions to complete, or decrease it if too many long-running transactions are causing locking problems and reducing concurrency on a busy system. InnoDB reports this error when the total number of locks exceeds the amount of memory devoted to managing locks. To avoid this error, increase the value of innodb_buffer_pool_size . Within an individual application, a workaround may be to break a large operation into smaller pieces. For example, if the error occurs for a large INSERT , perform several smaller INSERT operations. deadlock and is automatically rolled back so that your application can take corrective action. To recover from this error, run all the operations in this transaction again. A deadlock occurs when requests for locks arrive in inconsistent order between transactions. The transaction that was rolled back released all its locks, and the other transaction can now get all the locks it requested. Thus, when you re-run the transaction that was rolled back, it might have to wait for other transactions to complete, but typically the deadlock does not recur. If you encounter frequent deadlocks, make the sequence of locking operations ( LOCK TABLES , SELECT ... FOR UPDATE , and so on) consistent between the different transactions or applications that experience the issue. See Deadlocks in InnoDB for details. InnoDB reports this error when you try to add a row but there is no parent row, and a foreign key constraint fails. Add the parent row first. InnoDB reports this error when you try to delete a parent row that has children, and a foreign key constraint fails. Delete the children first. Message: SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is started Message: It is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restart The named object is incorrect for the type of operation attempted on it. It must be an object of the named type. Example: HANDLER OPEN requires a base table, not a view. It fails if attempted on an INFORMATION_SCHEMA table that is implemented as a view on data dictionary tables. Message: In definition of view, derived table or common table expression, SELECT list and column names list have different column counts Message: 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) Message: 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) Message: Thread stack overrun: %ld bytes used of a %ld byte stack, and %ld bytes needed. Use 'mysqld --thread_stack=#' to specify a bigger stack. Message: Can't update table '%s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger. Message: 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 Message: View '%s'.'%s' has no definer information (old table format). Current user is used as definer. Please recreate the view! InnoDB reports this error when you try to delete a parent row that has children, and a foreign key constraint fails. Delete the children first. InnoDB reports this error when you try to add a row but there is no parent row, and a foreign key constraint fails. Add the parent row first. Message: First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED InnoDB reports this error when you attempt to drop the last index that can enforce a particular referential constraint. For optimal performance with DML statements, InnoDB requires an index to exist on foreign key columns, so that UPDATE and DELETE operations on a parent table can easily check whether corresponding rows exist in the child table . MySQL creates or drops such indexes automatically when needed, as a side-effect of CREATE TABLE , CREATE INDEX , and ALTER TABLE statements. When you drop an index, InnoDB checks if the index is used for checking a foreign key constraint. It is still OK to drop the index if there is another index that can be used to enforce the same constraint. InnoDB prevents you from dropping the last index that can enforce a particular referential constraint. Message: The column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure. Error number: 1560 ; Symbol: ER_STORED_FUNCTION_PREVENTS_SWITCH_BINLOG_FORMAT ; SQLSTATE: HY000 Message: Cannot change the binary logging format inside a stored function or trigger Message: 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' Message: 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. Error number: 1609 ; Symbol: ER_NO_FORMAT_DESCRIPTION_EVENT_BEFORE_BINLOG_STATEMENT ; SQLSTATE: HY000 Message: The BINLOG statement of type `%s` was not preceded by a format description BINLOG statement. Error number: 1659 ; Symbol: ER_FIELD_TYPE_NOT_ALLOWED_AS_PARTITION_FIELD ; SQLSTATE: HY000 Message: Field '%s' is of a not allowed type for this type of partitioning Message: Cannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved. Message: 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. Message: 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 Message: 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. Message: 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 Message: Cannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT. Error number: 1667 ; Symbol: ER_BINLOG_MULTIPLE_ENGINES_AND_SELF_LOGGING_ENGINE ; SQLSTATE: HY000 Message: Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging. Message: The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Message: 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 replicas. Message: 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. Message: Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction. Error number: 1679 ; Symbol: ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_BINLOG_FORMAT ; SQLSTATE: HY000 Message: Cannot modify @@session.binlog_format inside a transaction Error number: 1685 ; Symbol: ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_BINLOG_DIRECT ; SQLSTATE: HY000 Message: Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction Error number: 1686 ; Symbol: ER_STORED_FUNCTION_PREVENTS_SWITCH_BINLOG_DIRECT ; SQLSTATE: HY000 Message: Cannot change the binlog direct flag inside a stored function or trigger Error number: 1692 ; Symbol: ER_BINLOG_UNSAFE_MULTIPLE_ENGINES_AND_SELF_LOGGING_ENGINE ; SQLSTATE: HY000 Message: Mixing self-logging and non-self-logging engines in a statement is unsafe. Error number: 1694 ; Symbol: ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_SQL_LOG_BIN ; SQLSTATE: HY000 Message: Cannot modify @@session.sql_log_bin inside a transaction Error number: 1695 ; Symbol: ER_STORED_FUNCTION_PREVENTS_SWITCH_SQL_LOG_BIN ; SQLSTATE: HY000 Message: Cannot change the sql_log_bin inside a stored function or trigger Message: 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. Message: The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout. Message: Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try again Message: 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 source and the replica. Message: 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 source and the replica. Message: 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 source and the replica. Message: 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 source and the replica. Message: 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 source and the replica. Message: 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 source and the replica. Message: 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 source and the replica. Message: 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 source and the replica. Error number: 1730 ; Symbol: ER_ONLY_FD_AND_RBR_EVENTS_ALLOWED_IN_BINLOG_STATEMENT ; SQLSTATE: HY000 Message: Only Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided) Message: Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size. Message: 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. Error number: 1751 ; Symbol: ER_WARNING_NOT_COMPLETE_ROLLBACK_WITH_CREATED_TEMP_TABLE ; SQLSTATE: HY000 Message: The creation of some temporary tables could not be rolled back. Error number: 1752 ; Symbol: ER_WARNING_NOT_COMPLETE_ROLLBACK_WITH_DROPPED_TEMP_TABLE ; SQLSTATE: HY000 Message: Some temporary tables were dropped, but these operations could not be rolled back. Message: The number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata. Message: 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: Message: Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information. Error number: 1770 ; Symbol: ER_GTID_NEXT_CANT_BE_AUTOMATIC_IF_GTID_NEXT_LIST_IS_NON_NULL ; SQLSTATE: HY000 Message: The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL. Message: Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid. Message: Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active. Error number: 1778 ; Symbol: ER_CANT_DO_IMPLICIT_COMMIT_IN_TRX_WHEN_GTID_NEXT_IS_SET ; SQLSTATE: HY000 Message: Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'. Error number: 1779 ; Symbol: ER_GTID_MODE_ON_REQUIRES_ENFORCE_GTID_CONSISTENCY_ON ; SQLSTATE: HY000 Message: GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON. Error number: 1781 ; Symbol: ER_CANT_SET_GTID_NEXT_TO_GTID_WHEN_GTID_MODE_IS_OFF ; SQLSTATE: HY000 Message: @@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF. Error number: 1782 ; Symbol: ER_CANT_SET_GTID_NEXT_TO_ANONYMOUS_WHEN_GTID_MODE_IS_ON ; SQLSTATE: HY000 Message: @@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON. Error number: 1783 ; Symbol: ER_CANT_SET_GTID_NEXT_LIST_TO_NON_NULL_WHEN_GTID_MODE_IS_OFF ; SQLSTATE: HY000 Message: @@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF. Message: Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables. Error number: 1788 ; Symbol: ER_GTID_MODE_CAN_ONLY_CHANGE_ONE_STEP_AT_A_TIME ; SQLSTATE: HY000 Message: The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions. Message: Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s Message: @@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK. Message: Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log. Message: Creating index '%s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again. Message: CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL. Message: Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log. Message: 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'. Error number: 1840 ; Symbol: ER_CANT_SET_GTID_PURGED_WHEN_GTID_EXECUTED_IS_NOT_EMPTY ; SQLSTATE: HY000 Message: @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty. Error number: 1841 ; Symbol: ER_CANT_SET_GTID_PURGED_WHEN_OWNED_GTIDS_IS_NOT_EMPTY ; SQLSTATE: HY000 Message: @@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients). Message: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to. Error number: 1847 ; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COPY ; SQLSTATE: HY000 Message: COPY algorithm requires a lock Error number: 1848 ; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_PARTITION ; SQLSTATE: HY000 Message: Partition specific operations do not yet support LOCK/ALGORITHM Error number: 1849 ; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_RENAME ; SQLSTATE: HY000 Message: Columns participating in a foreign key are renamed Error number: 1850 ; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COLUMN_TYPE ; SQLSTATE: HY000 Message: Cannot change column type INPLACE Error number: 1851 ; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_CHECK ; SQLSTATE: HY000 Message: Adding foreign keys needs foreign_key_checks=OFF Error number: 1853 ; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_NOPK ; SQLSTATE: HY000 Message: Dropping a primary key is not allowed without also adding a new primary key Error number: 1854 ; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_AUTOINC ; SQLSTATE: HY000 Message: Adding an auto-increment column requires a lock Error number: 1855 ; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_HIDDEN_FTS ; SQLSTATE: HY000 Message: Cannot replace hidden FTS_DOC_ID with a user-visible one Error number: 1856 ; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_CHANGE_FTS ; SQLSTATE: HY000 Message: Cannot drop or rename FTS_DOC_ID Error number: 1861 ; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_NOT_NULL ; SQLSTATE: HY000 Message: cannot silently convert NULL values, as required in this SQL_MODE Message: Cannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max. Message: STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete. Message: STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete. Error number: 1884 ; Symbol: ER_GTID_UNSAFE_BINLOG_SPLITTABLE_STATEMENT_AND_ASSIGNED_GTID ; SQLSTATE: HY000 Message: 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'. Message: Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED. Message: The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly. Message: Query partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s' Message: The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure. Message: This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0. Message: CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file. Error number: 3030 ; Symbol: ER_REPLICA_WORKER_STOPPED_PREVIOUS_THD_ERROR ; SQLSTATE: HY000 Message: Replica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well. Error number: 3031 ; Symbol: ER_DONT_SUPPORT_REPLICA_PRESERVE_COMMIT_ORDER ; SQLSTATE: HY000 Message: replica_preserve_commit_order is not supported %s. Message: Binary geometry function %s given two geometries of different srids: %u and %u, which should have been identical. Geometry values passed as arguments to spatial functions must have the same SRID value. Error number: 3040 ; Symbol: ER_BOOST_GEOMETRY_OVERLAY_INVALID_INPUT_EXCEPTION ; SQLSTATE: HY000 Message: Geometry overlay calculation error: geometry data is invalid in function %s. Error number: 3042 ; Symbol: ER_BOOST_GEOMETRY_SELF_INTERSECTION_POINT_EXCEPTION ; SQLSTATE: HY000 Message: Analysis procedures of intersection points interrupted unexpectedly in function %s. Message: Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition. This error is returned when the metdata locking subsystem detects a deadlock for an attempt to acquire a named lock with GET_LOCK . Message: Expression #%u of ORDER BY clause is not in SELECT list, references column '%s' which is not in SELECT list; this is incompatible with %s Message: To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE. Message: When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter. Message: Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by Message: In aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%s'; this is incompatible with sql_mode=only_full_group_by Error number: 3091 ; Symbol: ER_CANNOT_LOG_PARTIAL_DROP_DATABASE_WITH_GTID ; SQLSTATE: HY000 Message: DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %s; (2) SET GTID_NEXT='%s'; (3) DROP DATABASE `%s`. Error number: 3095 ; Symbol: ER_GROUP_REPLICATION_STOP_APPLIER_THREAD_TIMEOUT ; SQLSTATE: HY000 Message: The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete. Error number: 3096 ; Symbol: ER_GROUP_REPLICATION_COMMUNICATION_LAYER_SESSION_ERROR ; SQLSTATE: HY000 Message: The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer. Error number: 3097 ; Symbol: ER_GROUP_REPLICATION_COMMUNICATION_LAYER_JOIN_ERROR ; SQLSTATE: HY000 Message: The START GROUP_REPLICATION command failed as there was an error when joining the communication group. When using Group Replication, this means that a transaction failed the group certification process, due to one or more members detecting a potential conflict, and was thus rolled back. See Group Replication . Error number: 3103 ; Symbol: ER_UNSUPPORTED_ALTER_INPLACE_ON_VIRTUAL_COLUMN ; SQLSTATE: HY000 Message: INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actions To address this issue, change the table definition to define each generated column later than any generated columns to which it refers. You cannot drop or rename a generated column if another column refers to it. You must either drop those columns as well, or redefine them not to refer to the generated column. Error number: 3112 ; Symbol: ER_CANT_USE_AUTO_POSITION_WITH_GTID_MODE_OFF ; SQLSTATE: HY000 Message: The replication receiver thread%s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF. Error number: 3116 ; Symbol: ER_CANT_ENFORCE_GTID_CONSISTENCY_WITH_ONGOING_GTID_VIOLATING_TX ; SQLSTATE: HY000 Message: Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency. ER_CANT_SET_ENFORCE_GTID_CONSISTENCY_ON_WITH_ONGOING_GTID_VIOLATING_TRANSACTIONS was renamed to ER_CANT_ENFORCE_GTID_CONSISTENCY_WITH_ONGOING_GTID_VIOLATING_TX . Error number: 3117 ; Symbol: ER_ENFORCE_GTID_CONSISTENCY_WARN_WITH_ONGOING_GTID_VIOLATING_TX ; SQLSTATE: HY000 Message: There are ongoing transactions that violate GTID consistency. ER_SET_ENFORCE_GTID_CONSISTENCY_WARN_WITH_ONGOING_GTID_VIOLATING_TRANSACTIONS was renamed to ER_ENFORCE_GTID_CONSISTENCY_WARN_WITH_ONGOING_GTID_VIOLATING_TX . Error number: 3122 ; Symbol: ER_BOOST_GEOMETRY_INCONSISTENT_TURNS_EXCEPTION ; SQLSTATE: HY000 Message: Inconsistent intersection points. Message: MAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements only The MAX_EXECUTION_TIME optimizer hint is supported only for SELECT statements. Message: Please do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state. A locking service name was specified as NULL , the empty string, or a string longer than 64 characters. Namespace and lock names must be non- NULL , nonempty, and no more than 64 characters long. Message: 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release. The client has set its version_tokens_session system variable to the list of tokens it requires the server to match, but the server token list has at least one matching token name that has a value different from what the client requires. See Version Tokens . The client has set its version_tokens_session system variable to the list of tokens it requires the server to match, but the server token list is missing at least one of those tokens. See Version Tokens . Message: Variable %s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK. Message: Connections using insecure transport are prohibited while --require_secure_transport=ON. With the require_secure_transport system variable, clients can connect only using secure transports. Qualifying connections are those using SSL, a Unix socket file, or shared memory. Message: No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON. The require_secure_transport system variable cannot be enabled if the server does not support at least one secure transport. Configure the server with the required SSL keys/certificates to enable SSL connections, or enable the shared_memory system variable to enable shared-memory connections. An attempt was made to create a table or tablespace using a storage engine listed in the value of the disabled_storage_engines system variable, or to change an existing table or tablespace to such an engine. Choose a different storage engine. This error indicates that an audit plugin terminated execution of an event. The message typically indicates the event subclass name and a numeric status value. Error number: 3173 ; Symbol: ER_CANT_WAIT_FOR_EXECUTED_GTID_SET_WHILE_OWNING_A_GTID ; SQLSTATE: HY000 Message: The client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID. Message: Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction. Error number: 3178 ; Symbol: ER_UNSUPPORTED_ALTER_ONLINE_ON_VIRTUAL_COLUMN ; SQLSTATE: HY000 Message: ADD COLUMN col...VIRTUAL, ADD INDEX(col) Message: Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using. Message: It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure. Message: Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements. Error number: 3218 ; Symbol: ER_AUDIT_LOG_UDF_READ_INVALID_MAX_ARRAY_LENGTH_ARG_VALUE ; SQLSTATE: HY000 Message: Invalid "max_array_length" argument value. Message: The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'. Message: For KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535 Message: AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security. Message: Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian. Message: Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined. Error number: 3533 ; Symbol: ER_COMPONENTS_CANT_ACQUIRE_SERVICE_IMPLEMENTATION ; SQLSTATE: HY000 Message: Cannot acquire specified service implementation: '%s'. Error number: 3535 ; Symbol: ER_COMPONENTS_LOAD_CANT_REGISTER_SERVICE_IMPLEMENTATION ; SQLSTATE: HY000 Message: Cannot register service implementation '%s' provided by component '%s'. Error number: 3540 ; Symbol: ER_COMPONENTS_UNLOAD_CANT_UNREGISTER_SERVICE ; SQLSTATE: HY000 Message: Unregistration of service implementation '%s' provided by component '%s' failed during unloading of the component. Error number: 3546 ; Symbol: ER_CANT_SET_GTID_PURGED_DUE_SETS_CONSTRAINTS ; SQLSTATE: HY000 Message: @@GLOBAL.GTID_PURGED cannot be changed: %s Error number: 3555 ; Symbol: ER_NO_SYSTEM_TABLE_ACCESS_FOR_DICTIONARY_TABLE ; SQLSTATE: HY000 Message: data dictionary table Error number: 3574 ; Symbol: ER_CTE_RECURSIVE_REQUIRES_NONRECURSIVE_FIRST ; SQLSTATE: HY000 Message: Recursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive Message: In recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hints Message: In recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery Message: Window '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal Error number: 3595 ; Symbol: ER_WINDOW_NESTED_WINDOW_FUNC_USE_IN_WINDOW_SPEC ; SQLSTATE: HY000 Message: You cannot nest a window function in the specification of window '%s'. Message: Storage engine can't drop table '%s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary. Message: The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles. Message: Non-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password history Message: The SRID of the geometry does not match the SRID of the column '%s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column. Message: The SRID specification on the column '%s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification. Error number: 3647 ; Symbol: ER_WARN_BINLOG_PARTIAL_UPDATES_SUGGESTS_PARTIAL_IMAGES ; SQLSTATE: HY000 Message: When %s, the option binlog_row_value_options=%s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%. Error number: 3671 ; Symbol: ER_PASSWORD_EXPIRATION_NOT_SUPPORTED_BY_AUTH_METHOD ; SQLSTATE: HY000 Message: The selected authentication method %.*s does not support password expiration Message: The spatial index on column '%s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column. Message: Schema directory '%s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location). Message: Schema '%s' does not exist, but schema directory '%s' was found. This must be resolved manually (e.g. by moving the schema directory to another location). Message: Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once. Error number: 3711 ; Symbol: ER_SRS_ORGANIZATION_CANT_BE_EMPTY_OR_WHITESPACE ; SQLSTATE: SR006 Message: The organization name can't be an empty string or start or end with whitespace. Message: The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade. Message: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous. Message: NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous. Message: A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding. Message: Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic. Error number: 3729 ; Symbol: ER_INDEX_TYPE_NOT_SUPPORTED_FOR_SPATIAL_INDEX ; SQLSTATE: HY000 Message: The index type %s is not supported for spatial indexes. Message: %s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message. Message: The spatial reference system definition for SRID %u specifies invalid geographic axes '%s' and '%s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST. Error number: 3745 ; Symbol: ER_TEMP_TABLE_PREVENTS_SWITCH_SESSION_BINLOG_FORMAT ; SQLSTATE: HY000 Message: Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again. Error number: 3746 ; Symbol: ER_TEMP_TABLE_PREVENTS_SWITCH_GLOBAL_BINLOG_FORMAT ; SQLSTATE: HY000 Message: Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try again Error number: 3747 ; Symbol: ER_RUNNING_APPLIER_PREVENTS_SWITCH_GLOBAL_BINLOG_FORMAT ; SQLSTATE: HY000 Message: Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again. Error number: 3748 ; Symbol: ER_CLIENT_GTID_UNSAFE_CREATE_DROP_TEMP_TABLE_IN_TRX_IN_SBR ; SQLSTATE: HY000 Message: Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT. Message: Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting. Error number: 3753 ; Symbol: ER_FUNCTIONAL_INDEX_ON_JSON_OR_GEOMETRY_FUNCTION ; SQLSTATE: 42000 Message: Cannot create a functional index on a function that returns a JSON or GEOMETRY value. Message: Cannot drop column '%s' because it is used by a functional index. In order to drop the column, you must remove the functional index. Error number: 3763 ; Symbol: ER_GENERATED_COLUMN_NAMED_FUNCTION_IS_NOT_ALLOWED ; SQLSTATE: HY000 Message: Expression of generated column '%s' contains a disallowed function: %s. Message: Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value. Error number: 3769 ; Symbol: ER_DEFAULT_VAL_GENERATED_FUNCTION_IS_NOT_ALLOWED ; SQLSTATE: HY000 Message: Default value expression of column '%s' contains a disallowed function. Error number: 3770 ; Symbol: ER_DEFAULT_VAL_GENERATED_NAMED_FUNCTION_IS_NOT_ALLOWED ; SQLSTATE: HY000 Message: Default value expression of column '%s' contains a disallowed function: %s. Error number: 3774 ; Symbol: ER_UNSUPPORTED_ACTION_ON_DEFAULT_VAL_GENERATED ; SQLSTATE: HY000 Message: '%s' is not supported for default value expressions. Error number: 3775 ; Symbol: ER_GTID_UNSAFE_ALTER_ADD_COL_WITH_DEFAULT_EXPRESSION ; SQLSTATE: HY000 Message: Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT. Message: Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'. Message: '%s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead. Message: Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog. Message: Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election. Message: Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually. Error number: 3794 ; Symbol: ER_RPL_ENCRYPTION_MASTER_KEY_RECOVERY_FAILED ; SQLSTATE: HY000 Message: Unable to recover binlog encryption master key, please check if keyring is loaded. Error number: 3795 ; Symbol: ER_SLOW_LOG_MODE_IGNORED_WHEN_NOT_LOGGING_TO_FILE ; SQLSTATE: HY000 Message: slow query log file format changed as requested, but setting will have no effect when not actually logging to a file. Error number: 3800 ; Symbol: ER_FUNCTIONAL_INDEX_ROW_VALUE_IS_NOT_ALLOWED ; SQLSTATE: HY000 Message: Expression of functional index '%s' cannot refer to a row value. Error number: 3805 ; Symbol: ER_RPL_ENCRYPTION_CANNOT_ROTATE_BINLOG_MASTER_KEY ; SQLSTATE: HY000 Message: Cannot rotate binary log master key when 'binlog-encryption' is off. Error number: 3806 ; Symbol: ER_BINLOG_MASTER_KEY_RECOVERY_OUT_OF_COMBINATION ; SQLSTATE: HY000 Message: Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong. Error number: 3807 ; Symbol: ER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_OPERATE_KEY ; SQLSTATE: HY000 Message: Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files. Error number: 3808 ; Symbol: ER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_ROTATE_LOGS ; SQLSTATE: HY000 Message: Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master Error number: 3809 ; Symbol: ER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_REENCRYPT_LOG ; SQLSTATE: HY000 Message: %s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key. Error number: 3810 ; Symbol: ER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_CLEANUP_UNUSED_KEYS ; SQLSTATE: HY000 Message: Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution. Error number: 3811 ; Symbol: ER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_CLEANUP_AUX_KEY ; SQLSTATE: HY000 Message: Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution. Error number: 3813 ; Symbol: ER_COLUMN_CHECK_CONSTRAINT_REFERENCES_OTHER_COLUMN ; SQLSTATE: HY000 Message: Column check constraint '%s' references other column. Error number: 3814 ; Symbol: ER_CHECK_CONSTRAINT_NAMED_FUNCTION_IS_NOT_ALLOWED ; SQLSTATE: HY000 Message: An expression of a check constraint '%s' contains disallowed function: %s. Error number: 3818 ; Symbol: ER_CHECK_CONSTRAINT_REFERS_AUTO_INCREMENT_COLUMN ; SQLSTATE: HY000 Message: Check constraint '%s' cannot refer to an auto-increment column. Error number: 3823 ; Symbol: ER_CHECK_CONSTRAINT_CLAUSE_USING_FK_REFER_ACTION_COLUMN ; SQLSTATE: HY000 Message: Column '%s' cannot be used in a check constraint '%s': needed in a foreign key constraint '%s' referential action. Message: Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege. Message: Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege. Message: This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege. Message: This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege. Error number: 3836 ; Symbol: ER_UKNOWN_AUTH_ID_OR_ACCESS_DENIED_FOR_GRANT_AS ; SQLSTATE: HY000 Message: Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement. Error number: 3839 ; Symbol: ER_INNODB_REDO_LOG_ARCHIVE_START_SUBDIR_PATH ; SQLSTATE: HY000 Message: Redo log archiving start prohibits path name in 'subdir' argument Message: AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%s'. Error number: 3857 ; Symbol: ER_RPL_CANT_STOP_REPLICA_WHILE_LOCKED_BACKUP ; SQLSTATE: HY000 Message: Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first. Message: The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column. Error number: 3880 ; Symbol: ER_DA_AUTH_ID_WITH_SYSTEM_USER_PRIV_IN_MANDATORY_ROLES ; SQLSTATE: HY000 Message: Cannot set mandatory_roles: AuthId `%s`@`%s` has '%s' privilege. Error number: 3894 ; Symbol: ER_PASSWORD_CANNOT_BE_RETAINED_ON_PLUGIN_CHANGE ; SQLSTATE: HY000 Message: Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed. Error number: 3897 ; Symbol: ER_CANNOT_GRANT_SYSTEM_PRIV_TO_MANDATORY_ROLE ; SQLSTATE: HY000 Message: AuthId `%s`@`%s` is set as mandatory_roles. Cannot grant the '%s' privilege. Message: '%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted. Message: Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS. Error number: 3920 ; Symbol: ER_CHANGE_SOURCE_WRONG_COMPRESSION_ALGORITHM_CLIENT ; SQLSTATE: HY000 Message: Invalid SOURCE_COMPRESSION_ALGORITHMS '%s' for channel '%s'. Error number: 3921 ; Symbol: ER_CHANGE_SOURCE_WRONG_COMPRESSION_LEVEL_CLIENT ; SQLSTATE: HY000 Message: Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%s'. Error number: 3924 ; Symbol: ER_CHANGE_SOURCE_WRONG_COMPRESSION_ALGORITHM_LIST_CLIENT ; SQLSTATE: HY000 Message: Specified compression algorithm list '%s' exceeds total count of 3 for channel '%s'. Error number: 3925 ; Symbol: ER_CLIENT_PRIVILEGE_CHECKS_USER_CANNOT_BE_ANONYMOUS ; SQLSTATE: HY000 Message: PRIVILEGE_CHECKS_USER for replication channel '%s' was set to ``@`%s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER. Error number: 3926 ; Symbol: ER_CLIENT_PRIVILEGE_CHECKS_USER_DOES_NOT_EXIST ; SQLSTATE: HY000 Message: PRIVILEGE_CHECKS_USER for replication channel '%s' was set to `%s`@`%s`, but this is not an existing user. Message: Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration. Error number: 3928 ; Symbol: ER_CLIENT_PRIVILEGE_CHECKS_USER_NEEDS_RPL_APPLIER_PRIV ; SQLSTATE: HY000 Message: PRIVILEGE_CHECKS_USER for replication channel '%s' was set to `%s`@`%s`, but this user does not have REPLICATION_APPLIER privilege. Error number: 3934 ; Symbol: ER_JSON_SCHEMA_VALIDATION_ERROR_WITH_DETAILED_REPORT ; SQLSTATE: HY000 Message: %s. Message: Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server. Error number: 3941 ; Symbol: ER_ALTER_CONSTRAINT_ENFORCEMENT_NOT_SUPPORTED ; SQLSTATE: HY000 Message: Altering constraint enforcement is not supported for the constraint '%s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints. Error number: 3942 ; Symbol: ER_TABLE_VALUE_CONSTRUCTOR_MUST_HAVE_COLUMNS ; SQLSTATE: HY000 Message: Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement. Error number: 3943 ; Symbol: ER_TABLE_VALUE_CONSTRUCTOR_CANNOT_HAVE_DEFAULT ; SQLSTATE: HY000 Message: A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement. Error number: 3944 ; Symbol: ER_CLIENT_QUERY_FAILURE_INVALID_NON_ROW_FORMAT ; SQLSTATE: HY000 Message: The query does not comply with variable require_row_format restrictions. Error number: 3952 ; Symbol: ER_DA_UDF_INVALID_RETURN_TYPE_TO_SET_CHARSET ; SQLSTATE: HY000 Message: Character set can be set only for the UDF RETURN type STRING. Error number: 3955 ; Symbol: ER_USER_ACCESS_DENIED_FOR_USER_ACCOUNT_BLOCKED_BY_PASSWORD_LOCK ; SQLSTATE: HY000 Message: Access denied for user '%s'@'%s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Error number: 3961 ; Symbol: ER_WARN_DEPRECATED_JSON_TABLE_ON_ERROR_ON_EMPTY ; SQLSTATE: HY000 Message: Specifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead. Message: The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead. Error number: 3963 ; Symbol: ER_WARN_DEPRECATED_VALUES_FUNCTION_ALWAYS_NULL ; SQLSTATE: HY000 Message: The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause. Message: The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters. Message: Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' Message: Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port). Message: The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints. Error number: 3977 ; Symbol: ER_STATEMENT_NOT_ALLOWED_AFTER_START_TRANSACTION ; SQLSTATE: HY000 Message: Only BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement. Message: Cannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop() Message: Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNING Message: Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON. Message: Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled. Error number: 3992 ; Symbol: ER_DISABLE_GTID_MODE_REQUIRES_ASYNC_RECONNECT_OFF ; SQLSTATE: HY000 Message: The @@GLOBAL.GTID_MODE = %s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1. Error number: 3993 ; Symbol: ER_DISABLE_AUTO_POSITION_REQUIRES_ASYNC_RECONNECT_OFF ; SQLSTATE: HY000 Message: CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1. Message: The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer. Message: None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log. Message: None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services. Message: @@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event. Message: The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica. Message: STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete. Error number: 4013 ; Symbol: ER_CANT_USE_ANONYMOUS_TO_GTID_WITH_GTID_MODE_NOT_ON ; SQLSTATE: HY000 Message: Replication cannot start%s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON. Error number: 4014 ; Symbol: ER_CANT_COMBINE_ANONYMOUS_TO_GTID_AND_AUTOPOSITION ; SQLSTATE: HY000 Message: The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together. Error number: 4015 ; Symbol: ER_ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS_REQUIRES_GTID_MODE_ON ; SQLSTATE: HY000 Message: CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON. Error number: 4016 ; Symbol: ER_SQL_REPLICA_SKIP_COUNTER_USED_WITH_GTID_MODE_ON ; SQLSTATE: HY000 Message: The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF. Error number: 4017 ; Symbol: ER_USING_ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS_AS_LOCAL_OR_UUID ; SQLSTATE: HY000 Message: Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation. Error number: 4019 ; Symbol: ER_CANT_SET_SQL_AFTER_OR_BEFORE_GTIDS_WITH_ANONYMOUS_TO_GTID ; SQLSTATE: HY000 Message: The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. Error number: 4020 ; Symbol: ER_ANONYMOUS_TO_GTID_UUID_SAME_AS_GROUP_NAME ; SQLSTATE: HY000 Message: Replication '%s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_name Message: CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name. Message: The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools. Error number: 4030 ; Symbol: ER_WARN_ASYNC_CONN_FAILOVER_NETWORK_NAMESPACE ; SQLSTATE: HY000 Message: The parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter. Message: The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior. Message: Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID. Error number: 4037 ; Symbol: ER_CHANGE_RPL_SRC_WRONG_COMPRESSION_ALGORITHM_SIZE ; SQLSTATE: HY000 Message: Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%s'. Message: CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid. Error number: 4040 ; Symbol: ER_ANONYMOUS_TO_GTID_UUID_SAME_AS_VIEW_CHANGE_UUID ; SQLSTATE: HY000 Message: Replication '%s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuid Error number: 4041 ; Symbol: ER_GRP_RPL_VIEW_CHANGE_UUID_FAIL_GET_VARIABLE ; SQLSTATE: HY000 Message: Unable to retrieve group_replication_view_change_uuid variable during server checks on replication operations. Error number: 4042 ; Symbol: ER_WARN_ADUIT_LOG_MAX_SIZE_AND_PRUNE_SECONDS ; SQLSTATE: HY000 Message: Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignored Error number: 4043 ; Symbol: ER_WARN_ADUIT_LOG_MAX_SIZE_CLOSE_TO_ROTATE_ON_SIZE ; SQLSTATE: HY000 Message: audit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller. Message: Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm. Message: %d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation. Error number: 4047 ; Symbol: ER_WARN_SQL_AFTER_MTS_GAPS_GAP_NOT_CALCULATED ; SQLSTATE: HY000 Message: The until clause SQL_AFTER_MTS_GAPS is being used for channel '%s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause. Error number: 4050 ; Symbol: ER_GRP_RPL_FAILOVER_CHANNEL_STATUS_PROPAGATION ; SQLSTATE: HY000 Message: Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation. Error number: 4051 ; Symbol: ER_WARN_AUDIT_LOG_FORMAT_UNIX_TIMESTAMP_ONLY_WHEN_JSON ; SQLSTATE: HY000 Message: audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON. Message: Authentication plugin requires registration. Please refer ALTER USER syntax or set --register-factor command line option to do registration. Message: %d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method. Message: %d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable. Message: The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session. Error number: 4064 ; Symbol: ER_INVALID_MFA_OPERATIONS_FOR_PASSWORDLESS_USER ; SQLSTATE: HY000 Message: The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password. Error number: 4065 ; Symbol: ER_CHANGE_REPLICATION_SOURCE_NO_OPTIONS_FOR_GTID_ONLY ; SQLSTATE: HY000 Message: GTID_ONLY cannot be enabled for replication channel '%s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1. Error number: 4066 ; Symbol: ER_CHANGE_REP_SOURCE_CANT_DISABLE_REQ_ROW_FORMAT_WITH_GTID_ONLY ; SQLSTATE: HY000 Message: REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%s' when GTID_ONLY=1. Error number: 4067 ; Symbol: ER_CHANGE_REP_SOURCE_CANT_DISABLE_AUTO_POSITION_WITH_GTID_ONLY ; SQLSTATE: HY000 Message: SOURCE_AUTO_POSITION cannot be disabled for replication channel '%s' when GTID_ONLY=1. Error number: 4068 ; Symbol: ER_CHANGE_REP_SOURCE_CANT_DISABLE_GTID_ONLY_WITHOUT_POSITIONS ; SQLSTATE: HY000 Message: When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid. Error number: 4069 ; Symbol: ER_CHANGE_REP_SOURCE_CANT_DISABLE_AUTO_POS_WITHOUT_POSITIONS ; SQLSTATE: HY000 Message: When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid. Error number: 4070 ; Symbol: ER_CHANGE_REP_SOURCE_GR_CHANNEL_WITH_GTID_MODE_NOT_ON ; SQLSTATE: HY000 Message: When configuring a group replication channel you must do it when GTID_MODE = ON. Error number: 4072 ; Symbol: ER_WARN_C_DISABLE_GTID_ONLY_WITH_SOURCE_AUTO_POS_INVALID_POS ; SQLSTATE: HY000 Message: The replication positions relative to the source may be out-of-date on channel '%s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values. Message: The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying. Error number: 4083 ; Symbol: ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COLUMN_TYPE_INSTANT ; SQLSTATE: HY000 Message: Need to rebuild the table to change column type Message: This function '%s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name. Message: Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock. Error number: 4090 ; Symbol: ER_CANT_EXECUTE_COMMAND_WITH_ASSIGNED_GTID_NEXT ; SQLSTATE: HY000 Message: Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'. Message: Maximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE. Error number: 4094 ; Symbol: ER_OPERATION_NOT_ALLOWED_WHILE_PRIMARY_CHANGE_IS_RUNNING ; SQLSTATE: HY000 Message: All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'. Error number: 4098 ; Symbol: ER_WARN_CANNOT_SECURELY_PERSIST_SENSITIVE_VARIABLES ; SQLSTATE: HY000 Message: SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely. Error number: 4100 ; Symbol: ER_IF_NOT_EXISTS_UNSUPPORTED_TRG_EXISTS_ON_DIFFERENT_TABLE ; SQLSTATE: HY000 Message: Trigger '%s'.'%s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table. Error number: 4101 ; Symbol: ER_IF_NOT_EXISTS_UNSUPPORTED_UDF_NATIVE_FCT_NAME_COLLISION ; SQLSTATE: HY000 Message: This function '%s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function. Message: SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters. Error number: 4112 ; Symbol: ER_CREATE_SELECT_WITH_GIPK_DISALLOWED_IN_SBR ; SQLSTATE: HY000 Message: Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement. Error number: 4115 ; Symbol: ER_COMMAND_BACKEND_FAILED_TO_FETCH_SECURITY_CTX ; SQLSTATE: HY000 Message: Error when trying to fetch information from security context object, when trying to connect the server. Error number: 4117 ; Symbol: ER_CLIENT_FILE_PRIVILEGE_FOR_REPLICATION_CHECKS ; SQLSTATE: HY000 Message: The PRIVILEGE_CHECKS_USER for channel '%s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER. Error number: 4118 ; Symbol: ER_GROUP_REPLICATION_FORCE_MEMBERS_COMMAND_FAILURE ; SQLSTATE: HY000 Message: The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %s Error number: 4121 ; Symbol: ER_TP_QUERY_THRS_PER_GRP_EXCEEDS_TXN_THR_LIMIT ; SQLSTATE: HY000 Message: Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per group Message: Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810). Error number: 4140 ; Symbol: ER_BULK_LOADER_COLUMN_TOO_BIG_FOR_LEFTOVER_BUFFER ; SQLSTATE: HY000 Message: CSV column too big for leftover buffer. Error number: 4142 ; Symbol: ER_BULK_LOADER_FILE_CONTAINS_LESS_LINES_THAN_IGNORE_CLAUSE ; SQLSTATE: HY000 Message: The first file being loaded contained less lines than the ignore clause Error number: 4144 ; Symbol: ER_BULK_PARSER_ROW_BUFFER_MAX_TOTAL_COLS_EXCEEDED ; SQLSTATE: HY000 Message: The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'. Message: The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'. Error number: 4148 ; Symbol: ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_ENDING_ENCLOSED_BY ; SQLSTATE: HY000 Message: Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'. Error number: 4149 ; Symbol: ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_NULL_ESCAPE ; SQLSTATE: HY000 Message: Unexpected characters after NULL escape (\\N) found at row %ld in file '%s'. Error number: 4150 ; Symbol: ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_COLUMN_TERMINATOR ; SQLSTATE: HY000 Message: Unexpected characters after column terminator found at row %ld in file '%s'. Error number: 4155 ; Symbol: ER_REQUIRE_TABLE_PRIMARY_KEY_CHECK_GENERATE_WITH_GR ; SQLSTATE: HY000 Message: On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Error number: 4157 ; Symbol: ER_INNODB_INSTANT_ADD_DROP_NOT_SUPPORTED_MAX_SIZE ; SQLSTATE: HY000 Message: Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY. Error number: 4158 ; Symbol: ER_INNODB_INSTANT_ADD_NOT_SUPPORTED_MAX_FIELDS ; SQLSTATE: HY000 Message: Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY. Message: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead. Message: Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number. Error number: 4165 ; Symbol: ER_VALIDATE_PASSWORD_INSUFFICIENT_CHANGED_CHARACTERS ; SQLSTATE: HY000 Message: The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal. Error number: 6006 ; Symbol: ER_EXPLAIN_INTO_IMPLICIT_FORMAT_NOT_SUPPORTED ; SQLSTATE: 0A000 Message: EXPLAIN INTO does not support implicit FORMAT. Error number: 6009 ; Symbol: ER_EXPLAIN_INTO_FOR_CONNECTION_NOT_SUPPORTED ; SQLSTATE: 0A000 Message: EXPLAIN FOR CONNECTION does not support the INTO clause. Error number: 6011 ; Symbol: ER_INNODB_IMPORT_WRONG_NUMBER_OF_INDEXES_ZERO ; SQLSTATE: HY000 Message: Number of indexes in meta-data file is 0 Error number: 6012 ; Symbol: ER_INNODB_IMPORT_WRONG_NUMBER_OF_INDEXES_TOO_HIGH ; SQLSTATE: HY000 Message: Number of indexes in meta-data file is too high: %llu Error number: 6014 ; Symbol: ER_INNODB_IMPORT_ENUM_NULL_TERMINATOR_MISSING ; SQLSTATE: HY000 Message: Enum/Set element name missing null terminator for column Message: Bulk Loader: Not enough memory available. Memory needed for loading %s data: %s for %u threads, %s with minimal configuration. Total configured memory is %s, Available memory is Error number: 6032 ; Symbol: ER_START_REPLICA_CHANNEL_INVALID_CONFIGURATION ; SQLSTATE: HY000 Message: Cannot start replication channel '%s' because %s. Error number: 6035 ; Symbol: ER_WARN_DEPRECATED_ENGINE_SYNTAX_NO_REPLACEMENT ; SQLSTATE: HY000 Message: '%s' for '%s' storage engine is deprecated and will be removed in a future release. Error number: 6039 ; Symbol: ER_CANT_SET_GTID_NEXT_TO_AUTOMATIC_TAGGED_WHEN_GTID_MODE_IS_OFF ; SQLSTATE: HY000 Message: @@SESSION.GTID_NEXT cannot be set to AUTOMATIC:<TAG> when @@GLOBAL.GTID_MODE = OFF or OFF_PERMISSIVE Message: Column %d in %s: Invalid union encountered. Unions are only supported to represent nullable columns. One of the two types of the union must be null. Error number: 6120 ; Symbol: ER_STMT_EXECUTION_NOT_ALLOWED_WITHIN_SP_OR_TRG_OR_UDF ; SQLSTATE: HY000 Message: Executing SQL statement using %s Statement Handle Interface is not allowed within stored function, trigger or loadable function (UDF). Message: The variable thread_pool_max_transactions_limit cannot be set to 0 when thread_pool_dedicated_listernes is ON. ER_TP_CANNOT_DISABLE_MTL_WITH_DL was added in 8.4.1. Message: While initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u). Message: It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change. Error number: MY-010033 ; Symbol: ER_INVALID_VALUE_FOR_ENFORCE_GTID_CONSISTENCY ; SQLSTATE: HY000 Message: option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF. Error number: MY-010052 ; Symbol: ER_SCHEDULER_STOPPING_FAILED_TO_GET_EVENT ; SQLSTATE: HY000 Message: Event Scheduler: Serious error during getting next event to execute. Stopping Error number: MY-010053 ; Symbol: ER_SCHEDULER_STOPPING_FAILED_TO_CREATE_WORKER ; SQLSTATE: HY000 Message: Event_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event scheduler Message: Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. Message: No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s. Message: Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID. Message: The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored. Message: options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not set Error number: MY-010086 ; Symbol: ER_DEPRECATED_TIMESTAMP_IMPLICIT_DEFAULTS ; SQLSTATE: HY000 Message: TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). Message: Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %s Message: Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path. Message: Insecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory. Message: Insecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory. Message: Current time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process. Error number: MY-010158 ; Symbol: ER_LOWER_CASE_TABLE_NAMES_CS_DD_ON_CI_FS_UNSUPPORTED ; SQLSTATE: HY000 Message: The server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode. Message: lower_case_table_names was set to 2, even though your the file system '%s' is case sensitive. Now setting lower_case_table_names to 0 to avoid future problems. Message: No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem. Message: You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentation Message: Unable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds Message: Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table. Message: using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server. Message: using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled. Error number: MY-010204 ; Symbol: ER_RPL_BINLOG_STORAGE_DELEGATES_INIT_FAILED ; SQLSTATE: HY000 Message: Initialization binlog storage delegates failed. Please report a bug. Error number: MY-010205 ; Symbol: ER_RPL_BINLOG_TRANSMIT_DELEGATES_INIT_FAILED ; SQLSTATE: HY000 Message: Initialization of binlog transmit delegates failed. Please report a bug. Error number: MY-010206 ; Symbol: ER_RPL_BINLOG_RELAY_DELEGATES_INIT_FAILED ; SQLSTATE: HY000 Message: Initialization binlog relay IO delegates failed. Please report a bug. Error number: MY-010218 ; Symbol: ER_LOAD_DATA_INFILE_FAILED_IN_UNEXPECTED_WAY ; SQLSTATE: HY000 Message: LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug. Message: --tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery. Message: Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions. Message: Following users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %s Message: Following users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %s Error number: MY-010237 ; Symbol: ER_ROW_IN_WRONG_PARTITION_PLEASE_REPAIR ; SQLSTATE: HY000 Message: Table '%s' corrupted: row in wrong partition: %s -- Please REPAIR the table! Error number: MY-010257 ; Symbol: ER_CONN_TCP_IS_THERE_ANOTHER_USING_PORT ; SQLSTATE: HY000 Message: Do you already have another mysqld server running on port: %d ? Error number: MY-010258 ; Symbol: ER_CONN_UNIX_IS_THERE_ANOTHER_USING_SOCKET ; SQLSTATE: HY000 Message: Do you already have another mysqld server running on socket: %s ? Error number: MY-010303 ; Symbol: ER_AUTH_SSL_CONF_PREVENTS_CERT_GENERATION ; SQLSTATE: HY000 Message: Skipping generation of SSL certificates as options related to SSL are specified. Error number: MY-010307 ; Symbol: ER_AUTH_RSA_CONF_PREVENTS_KEY_GENERATION ; SQLSTATE: HY000 Message: Skipping generation of RSA key pair through %s as options related to RSA keys are specified. Error number: MY-010308 ; Symbol: ER_AUTH_KEY_GENERATION_SKIPPED_PAIR_PRESENT ; SQLSTATE: HY000 Message: Skipping generation of RSA key pair through %s as key files are present in data directory. Error number: MY-010311 ; Symbol: ER_AUTHCACHE_PROXIES_PRIV_SKIPPED_NEEDS_RESOLVE ; SQLSTATE: HY000 Message: 'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode. Error number: MY-010315 ; Symbol: ER_AUTHCACHE_USER_SKIPPED_NEEDS_RESOLVE ; SQLSTATE: HY000 Message: 'user' entry '%s@%s' ignored in --skip-name-resolve mode. Message: Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure. Error number: MY-010317 ; Symbol: ER_AUTHCACHE_USER_IGNORED_DEPRECATED_PASSWORD ; SQLSTATE: HY000 Message: User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore. Error number: MY-010319 ; Symbol: ER_AUTHCACHE_USER_IGNORED_INVALID_PASSWORD ; SQLSTATE: HY000 Message: Found invalid password for user: '%s@%s'; Ignoring user Error number: MY-010320 ; Symbol: ER_AUTHCACHE_EXPIRED_PASSWORD_UNSUPPORTED ; SQLSTATE: HY000 Message: 'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored. Message: Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual. Error number: MY-010324 ; Symbol: ER_AUTHCACHE_DB_ENTRY_LOWERCASED_REVOKE_WILL_FAIL ; SQLSTATE: HY000 Message: 'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE. Error number: MY-010325 ; Symbol: ER_AUTHCACHE_TABLE_PROXIES_PRIV_MISSING ; SQLSTATE: HY000 Message: The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure. Error number: MY-010326 ; Symbol: ER_AUTHCACHE_CANT_OPEN_AND_LOCK_PRIVILEGE_TABLES ; SQLSTATE: HY000 Message: Fatal error: Can't open and lock privilege tables: %s Error number: MY-010328 ; Symbol: ER_AUTHCACHE_PROCS_PRIV_SKIPPED_NEEDS_RESOLVE ; SQLSTATE: HY000 Message: 'procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode. Error number: MY-010329 ; Symbol: ER_AUTHCACHE_PROCS_PRIV_ENTRY_IGNORED_BAD_ROUTINE_TYPE ; SQLSTATE: HY000 Message: 'procs_priv' entry '%s' ignored, bad routine type Error number: MY-010330 ; Symbol: ER_AUTHCACHE_TABLES_PRIV_SKIPPED_NEEDS_RESOLVE ; SQLSTATE: HY000 Message: 'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode. Error number: MY-010331 ; Symbol: ER_USER_NOT_IN_EXTRA_USERS_BINLOG_POSSIBLY_INCOMPLETE ; SQLSTATE: HY000 Message: Failed to add %s in extra_users. Binary log entry may miss some of the users. Message: Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program! Message: '%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed Error number: MY-010349 ; Symbol: ER_TABLE_CREATED_WITH_DIFFERENT_VERSION ; SQLSTATE: HY000 Message: Table '%s' was created with a different version of MySQL and cannot be read Error number: MY-010354 ; Symbol: ER_AUDIT_PLUGIN_DOES_NOT_SUPPORT_AUDIT_AUTH_EVENTS ; SQLSTATE: HY000 Message: Plugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported. Error number: MY-010357 ; Symbol: ER_TZ_CANT_OPEN_AND_LOCK_TIME_ZONE_TABLE ; SQLSTATE: HY000 Message: Can't open and lock time zone table: %s trying to live without them Error number: MY-010359 ; Symbol: ER_TZ_TOO_MANY_LEAPS_IN_LEAP_SECOND_TABLE ; SQLSTATE: HY000 Message: Fatal error: While loading mysql.time_zone_leap_second table: too much leaps Error number: MY-010361 ; Symbol: ER_TZ_UNKNOWN_OR_ILLEGAL_DEFAULT_TIME_ZONE ; SQLSTATE: HY000 Message: Fatal error: Illegal or unknown default time zone '%s' Error number: MY-010362 ; Symbol: ER_TZ_CANT_FIND_DESCRIPTION_FOR_TIME_ZONE ; SQLSTATE: HY000 Message: Can't find description of time zone '%.*s' Error number: MY-010363 ; Symbol: ER_TZ_CANT_FIND_DESCRIPTION_FOR_TIME_ZONE_ID ; SQLSTATE: HY000 Message: Can't find description of time zone '%u' Error number: MY-010364 ; Symbol: ER_TZ_TRANSITION_TYPE_TABLE_TYPE_TOO_LARGE ; SQLSTATE: HY000 Message: Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type id Error number: MY-010365 ; Symbol: ER_TZ_TRANSITION_TYPE_TABLE_ABBREVIATIONS_EXCEED_SPACE ; SQLSTATE: HY000 Message: Error while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviations Error number: MY-010367 ; Symbol: ER_TZ_TRANSITION_TABLE_TOO_MANY_TRANSITIONS ; SQLSTATE: HY000 Message: Error while loading time zone description from mysql.time_zone_transition table: too much transitions Error number: MY-010368 ; Symbol: ER_TZ_TRANSITION_TABLE_BAD_TRANSITION_TYPE ; SQLSTATE: HY000 Message: Error while loading time zone description from mysql.time_zone_transition table: bad transition type id Error number: MY-010371 ; Symbol: ER_TZ_OOM_LOADING_TIME_ZONE_DESCRIPTION ; SQLSTATE: HY000 Message: Out of memory while loading time zone description Error number: MY-010375 ; Symbol: ER_REPLICA_SQL_THREAD_STOPPED_UNTIL_CONDITION_BAD ; SQLSTATE: HY000 Message: Replica SQL thread is stopped because UNTIL condition is bad(%s:%llu). Error number: MY-010376 ; Symbol: ER_REPLICA_SQL_THREAD_STOPPED_UNTIL_POSITION_REACHED ; SQLSTATE: HY000 Message: Replica SQL thread stopped because it reached its UNTIL position %llu Error number: MY-010377 ; Symbol: ER_REPLICA_SQL_THREAD_STOPPED_BEFORE_GTIDS_ALREADY_APPLIED ; SQLSTATE: HY000 Message: Replica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already applied Error number: MY-010378 ; Symbol: ER_REPLICA_SQL_THREAD_STOPPED_BEFORE_GTIDS_REACHED ; SQLSTATE: HY000 Message: Replica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %s Error number: MY-010379 ; Symbol: ER_REPLICA_SQL_THREAD_STOPPED_AFTER_GTIDS_REACHED ; SQLSTATE: HY000 Message: Replica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %s Error number: MY-010380 ; Symbol: ER_REPLICA_SQL_THREAD_STOPPED_GAP_TRX_PROCESSED ; SQLSTATE: HY000 Message: Replica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session. Error number: MY-010381 ; Symbol: ER_GROUP_REPLICATION_PLUGIN_NOT_INSTALLED ; SQLSTATE: HY000 Message: Group Replication plugin is not installed. Error number: MY-010383 ; Symbol: ER_FAILED_TO_DELETE_FROM_GTID_EXECUTED_TABLE ; SQLSTATE: HY000 Message: Failed to delete the row: '%s' from the gtid_executed table. Error number: MY-010384 ; Symbol: ER_FAILED_TO_COMPRESS_GTID_EXECUTED_TABLE ; SQLSTATE: HY000 Message: Failed to compress the gtid_executed table. Error number: MY-010385 ; Symbol: ER_FAILED_TO_COMPRESS_GTID_EXECUTED_TABLE_OOM ; SQLSTATE: HY000 Message: Failed to compress the gtid_executed table, because it is failed to allocate the THD. Error number: MY-010386 ; Symbol: ER_FAILED_TO_INIT_THREAD_ATTR_FOR_GTID_TABLE_COMPRESSION ; SQLSTATE: HY000 Message: Failed to initialize thread attribute when creating compression thread. Error number: MY-010387 ; Symbol: ER_FAILED_TO_CREATE_GTID_TABLE_COMPRESSION_THREAD ; SQLSTATE: HY000 Message: Can not create thread to compress gtid_executed table (errno= %d) Error number: MY-010388 ; Symbol: ER_FAILED_TO_JOIN_GTID_TABLE_COMPRESSION_THREAD ; SQLSTATE: HY000 Message: Could not join gtid_executed table compression thread. error:%d Error number: MY-010389 ; Symbol: ER_NPIPE_FAILED_TO_INIT_SECURITY_DESCRIPTOR ; SQLSTATE: HY000 Message: Can't start server : Initialize security descriptor: %s Error number: MY-010390 ; Symbol: ER_NPIPE_FAILED_TO_SET_SECURITY_DESCRIPTOR ; SQLSTATE: HY000 Message: Can't start server : Set security descriptor: %s Message: Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld) Error number: MY-010413 ; Symbol: ER_RPL_CHANNELS_REQUIRE_NON_ZERO_SERVER_ID ; SQLSTATE: HY000 Message: For the creation of replication channels the server id must be different from 0 Error number: MY-010415 ; Symbol: ER_RPL_ERROR_CREATING_CONNECTION_METADATA ; SQLSTATE: HY000 Message: Error creating connection metadata: %s. Error number: MY-010420 ; Symbol: ER_RPL_FAILED_TO_DELETE_FROM_REPLICA_WORKERS_INFO_REPOSITORY ; SQLSTATE: HY000 Message: Could not delete from Replica Workers info repository. Error number: MY-010421 ; Symbol: ER_RPL_FAILED_TO_RESET_STATE_IN_REPLICA_INFO_REPOSITORY ; SQLSTATE: HY000 Message: Could not store the reset Replica Worker state into the replica info repository. Error number: MY-010424 ; Symbol: ER_RPL_REPLICA_COULD_NOT_CREATE_CHANNEL_LIST ; SQLSTATE: HY000 Message: Replica: Could not create channel list Error number: MY-010425 ; Symbol: ER_RPL_MULTISOURCE_REQUIRES_TABLE_TYPE_REPOSITORIES ; SQLSTATE: HY000 Message: Replica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE. Error number: MY-010426 ; Symbol: ER_RPL_REPLICA_FAILED_TO_INIT_A_CONNECTION_METADATA_STRUCTURE ; SQLSTATE: HY000 Message: Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it. Error number: MY-010427 ; Symbol: ER_RPL_REPLICA_FAILED_TO_INIT_CONNECTION_METADATA_STRUCTURE ; SQLSTATE: HY000 Message: Failed to initialize the connection metadata structure%s Error number: MY-010428 ; Symbol: ER_RPL_REPLICA_FAILED_TO_CREATE_CHANNEL_FROM_CONNECTION_METADATA ; SQLSTATE: HY000 Message: Replica: Failed to create a channel from connection metadata repository. Error number: MY-010430 ; Symbol: ER_RPL_FAILED_TO_CREATE_CACHE_FOR_INFO_FILE ; SQLSTATE: HY000 Message: Failed to create a cache on info file (file '%s') Error number: MY-010437 ; Symbol: ER_ENGINE_COST_INVALID_DEVICE_TYPE_FOR_SE ; SQLSTATE: HY000 Message: Invalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost table Error number: MY-010438 ; Symbol: ER_ENGINE_COST_INVALID_CONST_CONSTANT_FOR_SE_AND_DEVICE ; SQLSTATE: HY000 Message: Invalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1f Error number: MY-010442 ; Symbol: ER_RPL_UNSUPPORTED_UNIGNORABLE_EVENT_IN_STREAM ; SQLSTATE: HY000 Message: Unsupported non-ignorable event fed into the event stream. Error number: MY-010445 ; Symbol: ER_RPL_UNEXPECTED_COMMIT_ROLLBACK_OR_XID_LOG_EVENT_IN_STREAM ; SQLSTATE: HY000 Message: QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s. Error number: MY-010446 ; Symbol: ER_RPL_UNEXPECTED_XA_ROLLBACK_IN_STREAM ; SQLSTATE: HY000 Message: QUERY(XA ROLLBACK) is not expected in an event stream %s. Error number: MY-010447 ; Symbol: ER_EVENT_EXECUTION_FAILED_CANT_AUTHENTICATE_USER ; SQLSTATE: HY000 Message: Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user. Error number: MY-010448 ; Symbol: ER_EVENT_EXECUTION_FAILED_USER_LOST_EVEN_PRIVILEGE ; SQLSTATE: HY000 Message: Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege. Message: In RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s. Error number: MY-010454 ; Symbol: ER_INIT_GENERATING_TEMP_PASSWORD_FOR_ROOT ; SQLSTATE: HY000 Message: A temporary password is generated for root@localhost: %s Error number: MY-010457 ; Symbol: ER_INIT_DATADIR_NOT_EMPTY_WONT_INITIALIZE ; SQLSTATE: HY000 Message: --initialize specified but the data directory has files in it. Aborting. Error number: MY-010459 ; Symbol: ER_INIT_DATADIR_EXISTS_AND_PATH_TOO_LONG_WONT_INITIALIZE ; SQLSTATE: HY000 Message: --initialize specified but the data directory exists and the path is too long. Aborting. Error number: MY-010460 ; Symbol: ER_INIT_DATADIR_EXISTS_AND_NOT_WRITABLE_WONT_INITIALIZE ; SQLSTATE: HY000 Message: --initialize specified but the data directory exists and is not writable. Aborting. Error number: MY-010464 ; Symbol: ER_RPL_BINLOG_SKIPPING_REMAINING_HEARTBEAT_INFO ; SQLSTATE: HY000 Message: the rest of heartbeat info skipped ... Error number: MY-010465 ; Symbol: ER_RPL_BINLOG_SOURCE_USES_CHECKSUM_AND_REPLICA_CANT ; SQLSTATE: HY000 Message: Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process them Error number: MY-010471 ; Symbol: ER_FAILED_TO_DECREMENT_NUMBER_OF_THREADS ; SQLSTATE: HY000 Message: Failed to decrement the number of threads Error number: MY-010522 ; Symbol: ER_TC_CANT_AUTO_RECOVER_WITH_TC_HEURISTIC_RECOVER ; SQLSTATE: HY000 Message: Cannot perform automatic crash recovery when --tc-heuristic-recover is used Error number: MY-010524 ; Symbol: ER_TC_NEED_N_SE_SUPPORTING_2PC_FOR_RECOVERY ; SQLSTATE: HY000 Message: Recovery failed! You must enable exactly %d storage engines that support two-phase commit protocol Error number: MY-010525 ; Symbol: ER_TC_RECOVERY_FAILED_THESE_ARE_YOUR_OPTIONS ; SQLSTATE: HY000 Message: Crash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback} Error number: MY-010528 ; Symbol: ER_TC_RESTART_WITHOUT_TC_HEURISTIC_RECOVER ; SQLSTATE: HY000 Message: Please restart mysqld without --tc-heuristic-recover Error number: MY-010529 ; Symbol: ER_RPL_REPLICA_FAILED_TO_CREATE_OR_RECOVER_INFO_REPOSITORIES ; SQLSTATE: HY000 Message: Failed to create or recover replication info repositories. Error number: MY-010530 ; Symbol: ER_RPL_REPLICA_AUTO_POSITION_IS_1_AND_GTID_MODE_IS_OFF ; SQLSTATE: HY000 Message: Detected misconfiguration: replication channel '%s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread. Error number: MY-010531 ; Symbol: ER_RPL_REPLICA_CANT_START_REPLICA_FOR_CHANNEL ; SQLSTATE: HY000 Message: Replica: Could not start replica for channel '%s'. operation discontinued Error number: MY-010532 ; Symbol: ER_RPL_REPLICA_CANT_STOP_REPLICA_FOR_CHANNEL ; SQLSTATE: HY000 Message: Replica: Could not stop replica for channel '%s' operation discontinued Error number: MY-010533 ; Symbol: ER_RPL_RECOVERY_NO_ROTATE_EVENT_FROM_SOURCE ; SQLSTATE: HY000 Message: Error during --relay-log-recovery: Could not locate rotate event from the source. Error number: MY-010536 ; Symbol: ER_RPL_RECOVERY_SKIPPED_GROUP_REPLICATION_CHANNEL ; SQLSTATE: HY000 Message: Relay log recovery skipped for group replication channel. Error number: MY-010538 ; Symbol: ER_RPL_RECOVERY_IO_ERROR_READING_RELAY_LOG_INDEX ; SQLSTATE: HY000 Message: Error during --relay-log-recovery: Could not read relay log index file due to an IO error. Message: Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively. Error number: MY-010540 ; Symbol: ER_RPL_RECOVERY_REPLICATE_SAME_SERVER_ID_REQUIRES_POSITION ; SQLSTATE: HY000 Message: Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen. Error number: MY-010541 ; Symbol: ER_RPL_MTA_RECOVERY_STARTING_COORDINATOR ; SQLSTATE: HY000 Message: MTA recovery: starting coordinator thread to fill MTA gaps. Error number: MY-010542 ; Symbol: ER_RPL_MTA_RECOVERY_FAILED_TO_START_COORDINATOR ; SQLSTATE: HY000 Message: MTA recovery: failed to start the coordinator thread. Check the error log for additional details. Message: MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA. Error number: MY-010544 ; Symbol: ER_RPL_MTA_RECOVERY_CANT_OPEN_RELAY_LOG ; SQLSTATE: HY000 Message: Failed to open the relay log '%s' (relay_log_pos %s). Error number: MY-010550 ; Symbol: ER_RPL_REPLICA_USES_CHECKSUM_AND_SOURCE_PRE_50 ; SQLSTATE: HY000 Message: Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0. Error number: MY-010551 ; Symbol: ER_RPL_REPLICA_SECONDS_BEHIND_SOURCE_DUBIOUS ; SQLSTATE: HY000 Message: "SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s Error number: MY-010552 ; Symbol: ER_RPL_REPLICA_CANT_FLUSH_CONNECTION_METADATA_REPOS ; SQLSTATE: HY000 Message: Failed to flush connection metadata repository. Message: The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s. Message: The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s. Error number: MY-010555 ; Symbol: ER_RPL_REPLICA_REPORT_PASSWORD_TOO_LONG ; SQLSTATE: HY000 Message: The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s. Error number: MY-010557 ; Symbol: ER_RPL_REPLICA_ERROR_READING_FROM_SERVER ; SQLSTATE: HY000 Message: Error reading packet from server%s: %s (server_errno=%d) Error number: MY-010558 ; Symbol: ER_RPL_REPLICA_DUMP_THREAD_KILLED_BY_SOURCE ; SQLSTATE: HY000 Message: Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %s Message: Multi-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %llu Error number: MY-010561 ; Symbol: ER_RPL_REPLICA_CANT_INIT_RELAY_LOG_POSITION ; SQLSTATE: HY000 Message: Error initializing relay log position%s: %s Error number: MY-010564 ; Symbol: ER_RPL_REPLICA_IO_THREAD_CANT_REGISTER_ON_SOURCE ; SQLSTATE: HY000 Message: Replica I/O thread couldn't register on source Error number: MY-010565 ; Symbol: ER_RPL_REPLICA_FORCING_TO_RECONNECT_IO_THREAD ; SQLSTATE: HY000 Message: Forcing to reconnect replica I/O thread%s Error number: MY-010566 ; Symbol: ER_RPL_REPLICA_ERROR_REQUESTING_BINLOG_DUMP ; SQLSTATE: HY000 Message: Failed on request_dump()%s Error number: MY-010567 ; Symbol: ER_RPL_LOG_ENTRY_EXCEEDS_REPLICA_MAX_ALLOWED_PACKET ; SQLSTATE: HY000 Message: Log entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packet Error number: MY-010569 ; Symbol: ER_RPL_REPLICA_IO_THREAD_ABORTED_WAITING_FOR_RELAY_LOG_SPACE ; SQLSTATE: HY000 Message: Replica I/O thread aborted while waiting for relay log space Error number: MY-010571 ; Symbol: ER_RPL_REPLICA_CANT_INITIALIZE_REPLICA_WORKER ; SQLSTATE: HY000 Message: Failed during replica worker initialization%s Error number: MY-010572 ; Symbol: ER_RPL_MTA_GROUP_RECOVERY_APPLIER_METADATA_FOR_WORKER ; SQLSTATE: HY000 Message: Replica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %llu Error number: MY-010574 ; Symbol: ER_RPL_MTA_GROUP_RECOVERY_APPLIER_METADATA ; SQLSTATE: HY000 Message: Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu. Error number: MY-010576 ; Symbol: ER_RPL_MTA_CHECKPOINT_PERIOD_DIFFERS_FROM_CNT ; SQLSTATE: HY000 Message: This an error cnt != mta_checkpoint_period Error number: MY-010577 ; Symbol: ER_RPL_REPLICA_WORKER_THREAD_CREATION_FAILED ; SQLSTATE: HY000 Message: Failed during replica worker thread creation%s Error number: MY-010578 ; Symbol: ER_RPL_REPLICA_WORKER_THREAD_CREATION_FAILED_WITH_ERRNO ; SQLSTATE: HY000 Message: Failed during replica worker thread creation%s (errno= Error number: MY-010579 ; Symbol: ER_RPL_REPLICA_FAILED_TO_INIT_PARTITIONS_HASH ; SQLSTATE: HY000 Message: Failed to init partitions hash Message: 'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Error number: MY-010583 ; Symbol: ER_RPL_REPLICA_ADDITIONAL_ERROR_INFO_FROM_DA ; SQLSTATE: HY000 Message: Replica (additional info): %s Error_code: MY-%06d Error number: MY-010585 ; Symbol: ER_RPL_REPLICA_ERROR_LOADING_USER_DEFINED_LIBRARY ; SQLSTATE: HY000 Message: Error loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %s Message: Error running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %s Error number: MY-010588 ; Symbol: ER_RPL_REPLICA_READ_INVALID_EVENT_FROM_SOURCE ; SQLSTATE: HY000 Message: Read invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bug Error number: MY-010589 ; Symbol: ER_RPL_REPLICA_QUEUE_EVENT_FAILED_INVALID_CONFIGURATION ; SQLSTATE: HY000 Message: The queue event failed for channel '%s' as its configuration is invalid. Error number: MY-010590 ; Symbol: ER_RPL_REPLICA_IO_THREAD_DETECTED_UNEXPECTED_EVENT_SEQUENCE ; SQLSTATE: HY000 Message: An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu. Message: '%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source. Error number: MY-010592 ; Symbol: ER_RPL_REPLICA_CONNECTED_TO_SOURCE_REPLICATION_RESUMED ; SQLSTATE: HY000 Message: Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %s Error number: MY-010595 ; Symbol: ER_RPL_REPLICA_SQL_THREAD_IO_ERROR_READING_EVENT ; SQLSTATE: HY000 Message: Replica SQL thread%s: I/O error reading event (errno: %d cur_log->error: %d) Error number: MY-010596 ; Symbol: ER_RPL_REPLICA_ERROR_READING_RELAY_LOG_EVENTS ; SQLSTATE: HY000 Message: Error reading relay log event%s: %s Message: 'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. Error number: MY-010598 ; Symbol: ER_RPL_REPLICA_NEW_C_M_NEEDS_REPOS_TYPE_OTHER_THAN_FILE ; SQLSTATE: HY000 Message: Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources. Error number: MY-010600 ; Symbol: ER_RPL_LOG_NOT_FOUND_WHILE_COUNTING_RELAY_LOG_SPACE ; SQLSTATE: HY000 Message: Could not find first log while counting relay log space. Error number: MY-010602 ; Symbol: ER_RPL_RELAY_LOG_NEEDS_FILE_NOT_DIRECTORY ; SQLSTATE: HY000 Message: Path '%s' is a directory name, please specify a file name for --relay-log option. Error number: MY-010603 ; Symbol: ER_RPL_RELAY_LOG_INDEX_NEEDS_FILE_NOT_DIRECTORY ; SQLSTATE: HY000 Message: Path '%s' is a directory name, please specify a file name for --relay-log-index option. Message: Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem. Error number: MY-010606 ; Symbol: ER_RPL_CANT_INITIALIZE_GTID_SETS_IN_AM_INIT_INFO ; SQLSTATE: HY000 Message: Failed in init_gtid_sets() called from Relay_log_info::rli_init_info(). Error number: MY-010608 ; Symbol: ER_RPL_ERROR_WRITING_RELAY_LOG_CONFIGURATION ; SQLSTATE: HY000 Message: Error writing relay log configuration. Error number: MY-010709 ; Symbol: ER_TREE_CORRUPT_PARENT_SHOULD_POINT_AT_PARENT ; SQLSTATE: HY000 Message: Wrong tree: Parent doesn't point at parent Error number: MY-010717 ; Symbol: ER_RPL_ERROR_READING_REPLICA_WORKER_CONFIGURATION ; SQLSTATE: HY000 Message: Error reading replica worker configuration Error number: MY-010722 ; Symbol: ER_RPL_MTA_REPLICA_COORDINATOR_HAS_WAITED ; SQLSTATE: HY000 Message: Multi-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu. Error number: MY-010723 ; Symbol: ER_BINLOG_FAILED_TO_WRITE_DROP_FOR_TEMP_TABLES ; SQLSTATE: HY000 Message: Failed to write the DROP statement for temporary tables to binary log Error number: MY-010724 ; Symbol: ER_BINLOG_OOM_WRITING_DELETE_WHILE_OPENING_HEAP_TABLE ; SQLSTATE: HY000 Message: When opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary log Error number: MY-010728 ; Symbol: ER_RPL_ERROR_WRITING_SOURCE_CONFIGURATION ; SQLSTATE: HY000 Message: Error writing source configuration. Error number: MY-010729 ; Symbol: ER_RPL_ERROR_READING_SOURCE_CONFIGURATION ; SQLSTATE: HY000 Message: Error reading source configuration. Error number: MY-010730 ; Symbol: ER_RPL_SSL_INFO_IN_CONNECTION_METADATA_IGNORED ; SQLSTATE: HY000 Message: SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support. Error number: MY-010732 ; Symbol: ER_PLUGIN_HAS_NONZERO_REFCOUNT_AFTER_DEINITIALIZATION ; SQLSTATE: HY000 Message: Plugin '%s' has ref_count=%d after deinitialization. Error number: MY-010739 ; Symbol: ER_PLUGIN_HAS_NONZERO_REFCOUNT_AFTER_SHUTDOWN ; SQLSTATE: HY000 Message: Plugin '%s' has ref_count=%d after shutdown. Message: Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag Error number: MY-010743 ; Symbol: ER_PLUGIN_VARIABLE_NOT_ALLOCATED_THREAD_LOCAL ; SQLSTATE: HY000 Message: Thread local variable '%s' not allocated in plugin '%s'. Error number: MY-010748 ; Symbol: ER_PLUGIN_HAS_CONFLICTING_SYSTEM_VARIABLES ; SQLSTATE: HY000 Message: Plugin '%s' has conflicting system variables Error number: MY-010750 ; Symbol: ER_MY_NET_WRITE_FAILED_FALLING_BACK_ON_STDERR ; SQLSTATE: HY000 Message: Failed on my_net_write, writing to stderr instead: %s Error number: MY-010761 ; Symbol: ER_CANT_CREATE_HANDLER_OBJECT_FOR_TABLE ; SQLSTATE: HY000 Message: Error in creating handler object for table %s.%s Error number: MY-010762 ; Symbol: ER_CANT_SET_HANDLER_REFERENCE_FOR_TABLE ; SQLSTATE: HY000 Message: Error in setting handler reference for table %s.%s Error number: MY-010764 ; Symbol: ER_CANT_UPGRADE_GENERATED_COLUMNS_TO_DD ; SQLSTATE: HY000 Message: Error in processing generated columns for table %s.%s Error number: MY-010769 ; Symbol: ER_CANT_OPEN_DB_OPT_USING_DEFAULT_CHARSET ; SQLSTATE: HY000 Message: Unable to open db.opt file %s. Using default Character Error number: MY-010772 ; Symbol: ER_DB_OPT_NOT_FOUND_USING_DEFAULT_CHARSET ; SQLSTATE: HY000 Message: db.opt file not found for %s database. Using default Character set. This error can occur for upgrades to MySQL 8.0 from previous versions. During the upgrade process, the server reads the mysql.event system table and migrates its contents to the internal data dictionary. This error can occur for upgrades to MySQL 8.0 from previous versions. During the upgrade process, the server reads the mysql.event system table and migrates its contents to the internal data dictionary. This error can occur for upgrades to MySQL 8.0 from previous versions. During the upgrade process, the server reads the mysql.event system table and migrates its contents to the internal data dictionary. This error can occur for upgrades to MySQL 8.0 from previous versions. During the upgrade process, the server reads the mysql.event system table and migrates its contents to the internal data dictionary. This error can occur for upgrades to MySQL 8.0 from previous versions. During the upgrade process, the server reads the mysql.event system table and migrates its contents to the internal data dictionary. This error can occur for upgrades to MySQL 8.0 from previous versions. During the upgrade process, the server reads the mysql.proc system table and migrates its contents to the internal data dictionary. This error can occur for upgrades to MySQL 8.0 from previous versions. During the upgrade process, the server reads the mysql.proc system table and migrates its contents to the internal data dictionary. Message: Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again. Error number: MY-010782 ; Symbol: ER_CANT_OPEN_DATADIR_AFTER_UPGRADE_FAILURE ; SQLSTATE: HY000 Message: Unable to open the data directory %s during clean up after upgrade failed Error number: MY-010801 ; Symbol: ER_EVENT_ERROR_CREATING_QUERY_TO_WRITE_TO_BINLOG ; SQLSTATE: HY000 Message: Event Error: An error occurred while creating query string, before writing it into binary log. Error number: MY-010802 ; Symbol: ER_EVENT_SCHEDULER_ERROR_LOADING_FROM_DB ; SQLSTATE: HY000 Message: Event Scheduler: Error while loading from disk. Error number: MY-010803 ; Symbol: ER_EVENT_SCHEDULER_ERROR_GETTING_EVENT_OBJECT ; SQLSTATE: HY000 Message: Event Scheduler: Error getting event object. Error number: MY-010804 ; Symbol: ER_EVENT_SCHEDULER_GOT_BAD_DATA_FROM_TABLE ; SQLSTATE: HY000 Message: Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corrupted Error number: MY-010805 ; Symbol: ER_EVENT_CANT_GET_LOCK_FOR_DROPPING_EVENT ; SQLSTATE: HY000 Message: Unable to obtain lock for dropping event %s from schema Error number: MY-010813 ; Symbol: ER_BINLOG_FILE_EXTENSION_NUMBER_EXHAUSTED ; SQLSTATE: HY000 Message: Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files. Error number: MY-010815 ; Symbol: ER_BINLOG_FILE_EXTENSION_NUMBER_RUNNING_LOW ; SQLSTATE: HY000 Message: Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs. Message: Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it. Error number: MY-010818 ; Symbol: ER_BINLOG_ERROR_READING_GTIDS_FROM_RELAY_LOG ; SQLSTATE: HY000 Message: Error reading GTIDs from relaylog: %d Error number: MY-010819 ; Symbol: ER_BINLOG_EVENTS_READ_FROM_APPLIER_METADATA ; SQLSTATE: HY000 Message: %lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state. Error number: MY-010820 ; Symbol: ER_BINLOG_ERROR_READING_GTIDS_FROM_BINARY_LOG ; SQLSTATE: HY000 Message: Error reading GTIDs from binary log: %d Error number: MY-010823 ; Symbol: ER_BINLOG_FAILED_TO_SYNC_INDEX_FILE_IN_OPEN ; SQLSTATE: HY000 Message: MYSQL_BIN_LOG::open failed to sync the index file. Message: Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it. Error number: MY-010825 ; Symbol: ER_BINLOG_FAILED_TO_CLOSE_INDEX_FILE_WHILE_REBUILDING ; SQLSTATE: HY000 Message: While rebuilding index file %s: Failed to close the index file. Error number: MY-010826 ; Symbol: ER_BINLOG_FAILED_TO_DELETE_INDEX_FILE_WHILE_REBUILDING ; SQLSTATE: HY000 Message: While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process. Error number: MY-010827 ; Symbol: ER_BINLOG_FAILED_TO_RENAME_INDEX_FILE_WHILE_REBUILDING ; SQLSTATE: HY000 Message: While rebuilding index file %s: Failed to rename the new index file to the existing index file. Error number: MY-010828 ; Symbol: ER_BINLOG_FAILED_TO_OPEN_INDEX_FILE_AFTER_REBUILDING ; SQLSTATE: HY000 Message: After rebuilding the index file %s: Failed to open the index file. Error number: MY-010830 ; Symbol: ER_BINLOG_CANT_LOCATE_OLD_BINLOG_OR_RELAY_LOG_FILES ; SQLSTATE: HY000 Message: Failed to locate old binlog or relay log files Error number: MY-010833 ; Symbol: ER_BINLOG_FAILED_TO_OPEN_TEMPORARY_INDEX_FILE ; SQLSTATE: HY000 Message: MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file. Error number: MY-010839 ; Symbol: ER_BINLOG_PURGE_LOGS_CALLED_WITH_FILE_NOT_IN_INDEX ; SQLSTATE: HY000 Message: MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index. Error number: MY-010840 ; Symbol: ER_BINLOG_PURGE_LOGS_CANT_SYNC_INDEX_FILE ; SQLSTATE: HY000 Message: MYSQL_BIN_LOG::purge_logs failed to sync the index file. Error number: MY-010841 ; Symbol: ER_BINLOG_PURGE_LOGS_CANT_COPY_TO_REGISTER_FILE ; SQLSTATE: HY000 Message: MYSQL_BIN_LOG::purge_logs failed to copy %s to register file. Error number: MY-010842 ; Symbol: ER_BINLOG_PURGE_LOGS_CANT_FLUSH_REGISTER_FILE ; SQLSTATE: HY000 Message: MYSQL_BIN_LOG::purge_logs failed to flush register file. Error number: MY-010843 ; Symbol: ER_BINLOG_PURGE_LOGS_CANT_UPDATE_INDEX_FILE ; SQLSTATE: HY000 Message: MYSQL_BIN_LOG::purge_logs failed to update the index file Error number: MY-010844 ; Symbol: ER_BINLOG_PURGE_LOGS_FAILED_TO_PURGE_LOG ; SQLSTATE: HY000 Message: MYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged. Error number: MY-010845 ; Symbol: ER_BINLOG_FAILED_TO_SET_PURGE_INDEX_FILE_NAME ; SQLSTATE: HY000 Message: MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name. Error number: MY-010847 ; Symbol: ER_BINLOG_FAILED_TO_REINIT_REGISTER_FILE ; SQLSTATE: HY000 Message: MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for read Error number: MY-010850 ; Symbol: ER_BINLOG_CANT_DELETE_LOG_FILE_DOES_INDEX_MATCH_FILES ; SQLSTATE: HY000 Message: Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog files Error number: MY-010851 ; Symbol: ER_BINLOG_CANT_DELETE_FILE_AND_READ_BINLOG_INDEX ; SQLSTATE: HY000 Message: Failed to delete file '%s' and read the binlog index file Error number: MY-010853 ; Symbol: ER_BINLOG_LOGGING_INCIDENT_TO_STOP_REPLICAS ; SQLSTATE: HY000 Message: %s An incident event has been written to the binary log which will stop the replicas. Error number: MY-010859 ; Symbol: ER_BINLOG_CANT_CLEAR_IN_USE_FLAG_FOR_CRASHED_BINLOG ; SQLSTATE: HY000 Message: Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it. Error number: MY-010860 ; Symbol: ER_BINLOG_FAILED_TO_RUN_AFTER_SYNC_HOOK ; SQLSTATE: HY000 Message: Failed to run 'after_sync' hooks Error number: MY-010861 ; Symbol: ER_TURNING_LOGGING_OFF_FOR_THE_DURATION ; SQLSTATE: HY000 Message: %s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it. Error number: MY-010862 ; Symbol: ER_BINLOG_FAILED_TO_RUN_AFTER_FLUSH_HOOK ; SQLSTATE: HY000 Message: Failed to run 'after_flush' hooks Error number: MY-010870 ; Symbol: ER_INNODB_INVALID_INNODB_UNDO_DIRECTORY ; SQLSTATE: HY000 Message: syntax error in innodb_undo_directory Message: InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lf Error number: MY-010877 ; Symbol: ER_INNODB_CLOSING_CONNECTION_ROLLS_BACK ; SQLSTATE: HY000 Message: MySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back. Error number: MY-010880 ; Symbol: ER_INNODB_INDEX_COLUMN_INFO_UNLIKE_MYSQLS ; SQLSTATE: HY000 Message: Found index %s whose column info does not match that of MySQL. Error number: MY-010882 ; Symbol: ER_INNODB_CANT_BUILD_INDEX_XLATION_TABLE_FOR ; SQLSTATE: HY000 Message: Build InnoDB index translation table for Table %s failed Message: Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table. Error number: MY-010890 ; Symbol: ER_PARTITION_MOVE_CREATED_DUPLICATE_ROW_PLEASE_FIX ; SQLSTATE: HY000 Message: Table '%s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %s Message: Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information. Message: Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege. Message: Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size. Message: 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. Message: Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict. Error number: MY-010912 ; Symbol: ER_RPL_GTID_MODE_REQUIRES_ENFORCE_GTID_CONSISTENCY_ON ; SQLSTATE: HY000 Message: GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON. Message: You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation. Message: 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release. Error number: MY-010925 ; Symbol: ER_ACCESS_DENIED_ERROR_WITHOUT_PASSWORD ; SQLSTATE: HY000 Message: Access denied for user '%s'@'%s' Error number: MY-010927 ; Symbol: ER_ACCESS_DENIED_FOR_USER_ACCOUNT_LOCKED ; SQLSTATE: HY000 Message: Access denied for user '%s'@'%s'. Account is locked. Error number: MY-010929 ; Symbol: ER_SYSTEM_TABLES_NOT_SUPPORTED_BY_STORAGE_ENGINE ; SQLSTATE: HY000 Message: Storage engine '%s' does not support system tables. [%s.%s]. Message: Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space Message: Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s). Error number: MY-010940 ; Symbol: ER_PERFSCHEMA_COMPONENTS_INFRASTRUCTURE_BOOTSTRAP ; SQLSTATE: HY000 Message: Failed to bootstrap performance schema components infrastructure. Error number: MY-010941 ; Symbol: ER_PERFSCHEMA_COMPONENTS_INFRASTRUCTURE_SHUTDOWN ; SQLSTATE: HY000 Message: Failed to deinit performance schema components infrastructure. Error number: MY-010945 ; Symbol: ER_RESOURCE_GROUP_SUBSYSTEM_INIT_FAILED ; SQLSTATE: HY000 Message: Resource Group subsystem initialization failed. Error number: MY-010951 ; Symbol: ER_RPL_FILTER_ADD_WILD_IGNORE_TABLE_FAILED ; SQLSTATE: HY000 Message: Could not add wild ignore table rule '%s'! Message: The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual. Error number: MY-010959 ; Symbol: ER_BINLOG_EVENT_WRITE_TO_STMT_CACHE_FAILED ; SQLSTATE: HY000 Message: Failed to write an incident event into stmt_cache. Error number: MY-010963 ; Symbol: ER_RPL_REPLICA_GLOBAL_FILTERS_COPY_FAILED ; SQLSTATE: HY000 Message: Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'. Message: There are per-channel replication filter(s) configured for channel '%s' which does not exist. The filter(s) have been discarded. Error number: MY-010967 ; Symbol: ER_ANONYMOUS_AUTH_ID_NOT_ALLOWED_IN_MANDATORY_ROLES ; SQLSTATE: HY000 Message: Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles. Error number: MY-010970 ; Symbol: ER_RESOURCE_GROUP_METADATA_UPDATE_SKIPPED ; SQLSTATE: HY000 Message: Skipped updating resource group metadata in InnoDB read only mode. Error number: MY-010971 ; Symbol: ER_FAILED_TO_PERSIST_RESOURCE_GROUP_METADATA ; SQLSTATE: HY000 Message: Failed to persist resource group %s to Data Dictionary. Error number: MY-010972 ; Symbol: ER_FAILED_TO_DESERIALIZE_RESOURCE_GROUP ; SQLSTATE: HY000 Message: Failed to deserialize resource group %s. Error number: MY-010975 ; Symbol: ER_FAILED_TO_ALLOCATE_MEMORY_FOR_RESOURCE_GROUP ; SQLSTATE: HY000 Message: Unable to allocate memory for Resource Group %s. Error number: MY-010976 ; Symbol: ER_FAILED_TO_ALLOCATE_MEMORY_FOR_RESOURCE_GROUP_HASH ; SQLSTATE: HY000 Message: Failed to allocate memory for resource group hash. Error number: MY-010979 ; Symbol: ER_FAILED_TO_APPLY_RESOURCE_GROUP_CONTROLLER ; SQLSTATE: HY000 Message: Unable to apply resource group controller %s. Error number: MY-010980 ; Symbol: ER_FAILED_TO_ACQUIRE_LOCK_ON_RESOURCE_GROUP ; SQLSTATE: HY000 Message: Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored. Error number: MY-010981 ; Symbol: ER_PFS_NOTIFICATION_FUNCTION_REGISTER_FAILED ; SQLSTATE: HY000 Message: PFS %s notification function registration failed. Error number: MY-010983 ; Symbol: ER_RES_GRP_SET_THR_AFFINITY_TO_CPUS_FAILED ; SQLSTATE: HY000 Message: Unable to bind thread id %llu to cpu ids (error code %d - Error number: MY-010986 ; Symbol: ER_RES_GRP_FAILED_TO_DETERMINE_NICE_CAPABILITY ; SQLSTATE: HY000 Message: Unable to determine CAP_SYS_NICE capability. Error number: MY-010988 ; Symbol: ER_RES_GRP_GET_THREAD_PRIO_NOT_SUPPORTED ; SQLSTATE: HY000 Message: Retrieval of thread priority unsupported on %s. Error number: MY-010992 ; Symbol: ER_RES_GRP_SOLARIS_PROCESSOR_BIND_TO_CPUID_FAILED ; SQLSTATE: HY000 Message: bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %s). Error number: MY-010993 ; Symbol: ER_RES_GRP_SOLARIS_PROCESSOR_BIND_TO_THREAD_FAILED ; SQLSTATE: HY000 Message: bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %s). Error number: MY-010994 ; Symbol: ER_RES_GRP_SOLARIS_PROCESSOR_AFFINITY_FAILED ; SQLSTATE: HY000 Message: %s failed: processor_affinity failed (error code %d - Error number: MY-010995 ; Symbol: ER_DD_UPGRADE_RENAME_IDX_STATS_FILE_FAILED ; SQLSTATE: HY000 Message: Error in renaming mysql_index_stats.ibd. Error number: MY-010997 ; Symbol: ER_DD_UPGRADE_FAILED_TO_FETCH_TABLESPACES ; SQLSTATE: HY000 Message: Error in fetching list of tablespaces. Error number: MY-010998 ; Symbol: ER_DD_UPGRADE_FAILED_TO_ACQUIRE_TABLESPACE ; SQLSTATE: HY000 Message: Error in acquiring Tablespace for SDI insertion %s. Error number: MY-010999 ; Symbol: ER_DD_UPGRADE_FAILED_TO_RESOLVE_TABLESPACE_ENGINE ; SQLSTATE: HY000 Message: Error in resolving Engine name for tablespace %s with engine %s. Error number: MY-011006 ; Symbol: ER_DD_UPGRADE_TABLESPACE_MIGRATION_FAILED ; SQLSTATE: HY000 Message: Got error %d from SE while migrating tablespaces. Error number: MY-011007 ; Symbol: ER_DD_UPGRADE_FAILED_TO_CREATE_TABLE_STATS ; SQLSTATE: HY000 Message: Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command. Error number: MY-011008 ; Symbol: ER_DD_UPGRADE_TABLE_STATS_MIGRATE_COMPLETED ; SQLSTATE: HY000 Message: Finished migrating TABLE statistics data. Error number: MY-011009 ; Symbol: ER_DD_UPGRADE_FAILED_TO_CREATE_INDEX_STATS ; SQLSTATE: HY000 Message: Error in creating Index statistics entry. Fix statistics data by using ANALYZE command. Error number: MY-011010 ; Symbol: ER_DD_UPGRADE_INDEX_STATS_MIGRATE_COMPLETED ; SQLSTATE: HY000 Message: Finished migrating INDEX statistics data. Error number: MY-011011 ; Symbol: ER_DD_UPGRADE_FAILED_FIND_VALID_DATA_DIR ; SQLSTATE: HY000 Message: Failed to find valid data directory. Error number: MY-011014 ; Symbol: ER_DD_UPGRADE_FOUND_PARTIALLY_UPGRADED_DD_ABORT ; SQLSTATE: HY000 Message: Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again. Error number: MY-011015 ; Symbol: ER_DD_UPGRADE_FOUND_PARTIALLY_UPGRADED_DD_CONTINUE ; SQLSTATE: HY000 Message: Found partially upgraded DD. Upgrade will continue and start the server. Error number: MY-011018 ; Symbol: ER_SKIP_UPDATING_METADATA_IN_SE_RO_MODE ; SQLSTATE: HY000 Message: Skip updating %s metadata in InnoDB read-only mode. Error number: MY-011023 ; Symbol: ER_FAILED_TO_CONSTRUCT_DROP_EVENT_QUERY ; SQLSTATE: HY000 Message: Unable to construct DROP EVENT SQL query string. Error number: MY-011029 ; Symbol: ER_REPLICA_NOT_STARTED_ON_SOME_CHANNELS ; SQLSTATE: HY000 Message: Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted. Error number: MY-011031 ; Symbol: ER_PER_CHANNEL_RPL_FILTER_CONF_FOR_GRP_RPL ; SQLSTATE: HY000 Message: There are per-channel replication filter(s) configured for group replication channel '%s' which is disallowed. The filter(s) have been discarded. Message: There are per-channel replication filter(s) configured for channel '%s' which does not exist. The filter(s) have been discarded. Error number: MY-011033 ; Symbol: ER_FAILED_TO_BUILD_DO_AND_IGNORE_TABLE_HASHES ; SQLSTATE: HY000 Message: An error occurred while building do_table and ignore_table rules to hashes for per-channel filter. Message: The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed. Message: The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed. Error number: MY-011042 ; Symbol: ER_INNODB_FAILED_TO_FIND_IDX_WITH_KEY_NO ; SQLSTATE: HY000 Message: InnoDB could not find index %s key no %u for table %s through its index translation table. Error number: MY-011044 ; Symbol: ER_INNODB_FAILED_TO_FIND_IDX_FROM_DICT_CACHE ; SQLSTATE: HY000 Message: InnoDB could not find key no %u with name %s from dict cache for table %s. Error number: MY-011047 ; Symbol: ER_WRONG_TYPE_FOR_COLUMN_PREFIX_IDX_FLD ; SQLSTATE: HY000 Message: MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s. Error number: MY-011050 ; Symbol: ER_INNODB_IDX_CNT_MORE_THAN_DEFINED_IN_MYSQL ; SQLSTATE: HY000 Message: InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL. Error number: MY-011051 ; Symbol: ER_INNODB_IDX_CNT_FEWER_THAN_DEFINED_IN_MYSQL ; SQLSTATE: HY000 Message: Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation? Message: Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation? Message: Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group. Error number: MY-011054 ; Symbol: ER_INNODB_MONITOR_DEFAULT_VALUE_NOT_DEFINED ; SQLSTATE: HY000 Message: Default value is not defined for this set option. Please specify correct counter or module name. Error number: MY-011074 ; Symbol: ER_COMPONENTS_FAILED_TO_ACQUIRE_SERVICE_IMPLEMENTATION ; SQLSTATE: HY000 Message: Cannot acquire specified service implementation: '%s'. Error number: MY-011081 ; Symbol: ER_DD_UPGRADE_VIEW_COLUMN_NAME_TOO_LONG ; SQLSTATE: HY000 Message: Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters. Error number: MY-011083 ; Symbol: ER_DD_UPGRADE_FAILED_TO_UPDATE_VER_NO_IN_TABLESPACE ; SQLSTATE: HY000 Message: Error in updating version number in %s tablespace. Error number: MY-011095 ; Symbol: ER_DD_MINOR_DOWNGRADE_VERSION_NOT_SUPPORTED ; SQLSTATE: HY000 Message: Minor downgrade of the Data dictionary from dictionary version '%u' is not supported. Error number: MY-011097 ; Symbol: ER_THREAD_POOL_NOT_SUPPORTED_ON_PLATFORM ; SQLSTATE: HY000 Message: Thread pool not supported, requires a minimum of %s. Message: thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm. Message: thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server. Error number: MY-011102 ; Symbol: ER_THREAD_POOL_INVALID_PRIO_KICKUP_TIMER ; SQLSTATE: HY000 Message: Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294. Error number: MY-011103 ; Symbol: ER_THREAD_POOL_MAX_UNUSED_THREADS_INVALID ; SQLSTATE: HY000 Message: thread_pool_max_unused_threads cannot be set higher than Error number: MY-011107 ; Symbol: ER_THREAD_POOL_CANNOT_SET_THREAD_SPECIFIC_DATA ; SQLSTATE: HY000 Message: Can't setup connection teardown thread-specific data. Error number: MY-011108 ; Symbol: ER_THREAD_POOL_FAILED_TO_CREATE_CONNECT_HANDLER_THD ; SQLSTATE: HY000 Message: Creation of connect handler thread failed. Error number: MY-011109 ; Symbol: ER_THREAD_POOL_FAILED_TO_CREATE_THD_AND_AUTH_CONN ; SQLSTATE: HY000 Message: Failed to create thd and authenticate connection. Error number: MY-011110 ; Symbol: ER_THREAD_POOL_FAILED_PROCESS_CONNECT_EVENT ; SQLSTATE: HY000 Message: Failed to process connection event. Error number: MY-011127 ; Symbol: ER_SEMISYNC_TRACE_EXIT_WITH_INT_EXIT_CODE ; SQLSTATE: HY000 Message: <--- %s exit (%d). Error number: MY-011128 ; Symbol: ER_SEMISYNC_TRACE_EXIT_WITH_BOOL_EXIT_CODE ; SQLSTATE: HY000 Message: <--- %s exit (%s). Error number: MY-011131 ; Symbol: ER_SEMISYNC_FAILED_TO_ALLOCATE_TRX_NODE ; SQLSTATE: HY000 Message: %s: transaction node allocation failed for: (%s, %lu). Error number: MY-011135 ; Symbol: ER_SEMISYNC_CLEARED_ALL_ACTIVE_TRANSACTION_NODES ; SQLSTATE: HY000 Message: %s: cleared all nodes. Error number: MY-011136 ; Symbol: ER_SEMISYNC_CLEARED_ACTIVE_TRANSACTION_TILL_POS ; SQLSTATE: HY000 Message: %s: cleared %d nodes back until pos (%s, %lu). Error number: MY-011139 ; Symbol: ER_SEMISYNC_REPLY_BINLOG_FILE_TOO_LARGE ; SQLSTATE: HY000 Message: Read semi-sync reply binlog file length too large. Error number: MY-011147 ; Symbol: ER_SEMISYNC_SOURCE_SIGNAL_ALL_WAITING_THREADS ; SQLSTATE: HY000 Message: %s: signal all waiting threads. Error number: MY-011154 ; Symbol: ER_SEMISYNC_WAIT_TIME_ASSESSMENT_FOR_COMMIT_TRX_FAILED ; SQLSTATE: HY000 Message: Assessment of waiting time for commitTrx failed at wait position (%s, %lu). Error number: MY-011164 ; Symbol: ER_SEMISYNC_UPDATE_EXISTING_REPLICA_ACK ; SQLSTATE: HY000 Message: Update an exsiting ack in slot %u. Error number: MY-011165 ; Symbol: ER_SEMISYNC_FAILED_TO_START_ACK_RECEIVER_THD ; SQLSTATE: HY000 Message: Failed to start semi-sync ACK receiver thread, could not create thread(errno:%d). Error number: MY-011167 ; Symbol: ER_SEMISYNC_FAILED_TO_WAIT_ON_DUMP_SOCKET ; SQLSTATE: HY000 Message: Failed to wait on semi-sync dump sockets, error: errno=%d. Error number: MY-011168 ; Symbol: ER_SEMISYNC_STOPPING_ACK_RECEIVER_THREAD ; SQLSTATE: HY000 Message: Stopping ack receiver thread. Error number: MY-011169 ; Symbol: ER_SEMISYNC_FAILED_REGISTER_REPLICA_TO_RECEIVER ; SQLSTATE: HY000 Message: Failed to register replica to semi-sync ACK receiver thread. Error number: MY-011170 ; Symbol: ER_SEMISYNC_START_BINLOG_DUMP_TO_REPLICA ; SQLSTATE: HY000 Message: Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu). Error number: MY-011171 ; Symbol: ER_SEMISYNC_STOP_BINLOG_DUMP_TO_REPLICA ; SQLSTATE: HY000 Message: Stop %s binlog_dump to replica (server_id: %d). Error number: MY-011172 ; Symbol: ER_SEMISYNC_UNREGISTER_TRX_OBSERVER_FAILED ; SQLSTATE: HY000 Message: unregister_trans_observer failed. Error number: MY-011173 ; Symbol: ER_SEMISYNC_UNREGISTER_BINLOG_STORAGE_OBSERVER_FAILED ; SQLSTATE: HY000 Message: unregister_binlog_storage_observer failed. Error number: MY-011174 ; Symbol: ER_SEMISYNC_UNREGISTER_BINLOG_TRANSMIT_OBSERVER_FAILED ; SQLSTATE: HY000 Message: unregister_binlog_transmit_observer failed. Error number: MY-011178 ; Symbol: ER_SEMISYNC_MISSING_MAGIC_NO_FOR_SEMISYNC_PKT ; SQLSTATE: HY000 Message: Missing magic number for semi-sync packet, packet len: Error number: MY-011180 ; Symbol: ER_SEMISYNC_REPLICA_REPLY_WITH_BINLOG_INFO ; SQLSTATE: HY000 Message: %s: reply (%s, %lu). Error number: MY-011181 ; Symbol: ER_SEMISYNC_REPLICA_NET_FLUSH_REPLY_FAILED ; SQLSTATE: HY000 Message: Semi-sync replica net_flush() reply failed. Error number: MY-011186 ; Symbol: ER_SEMISYNC_FAILED_TO_STOP_ACK_RECEIVER_THD ; SQLSTATE: HY000 Message: Failed to stop ack receiver thread on my_thread_join, errno(%d). Error number: MY-011187 ; Symbol: ER_FIREWALL_FAILED_TO_READ_FIREWALL_TABLES ; SQLSTATE: HY000 Message: Failed to read the firewall tables Error number: MY-011188 ; Symbol: ER_FIREWALL_FAILED_TO_REG_DYNAMIC_PRIVILEGES ; SQLSTATE: HY000 Message: Failed to register dynamic privileges Error number: MY-011189 ; Symbol: ER_FIREWALL_RECORDING_STMT_WAS_TRUNCATED ; SQLSTATE: HY000 Message: Statement was truncated and not recorded: %s Error number: MY-011190 ; Symbol: ER_FIREWALL_RECORDING_STMT_WITHOUT_TEXT ; SQLSTATE: HY000 Message: Statement with no text was not recorded Message: Audit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release. Error number: MY-011200 ; Symbol: ER_AUDIT_LOG_CANNOT_SET_LOG_POLICY_WITH_OTHER_POLICIES ; SQLSTATE: HY000 Message: Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy. Error number: MY-011202 ; Symbol: ER_AUDIT_LOG_INDEX_MAP_CANNOT_ACCESS_DIR ; SQLSTATE: HY000 Message: Could not access '%s' directory. Error number: MY-011204 ; Symbol: ER_AUDIT_LOG_WRITER_DEST_FILE_ALREADY_EXISTS ; SQLSTATE: HY000 Message: File '%s' should not exist. It may be incomplete. The server crashed. Error number: MY-011205 ; Symbol: ER_AUDIT_LOG_WRITER_RENAME_FILE_FAILED_REMOVE_FILE_MANUALLY ; SQLSTATE: HY000 Message: Could not rename file from '%s' to '%s'. Remove the file manually. Error number: MY-011206 ; Symbol: ER_AUDIT_LOG_WRITER_INCOMPLETE_FILE_RENAMED ; SQLSTATE: HY000 Message: Incomplete file renamed from '%s' to '%s'. Error number: MY-011207 ; Symbol: ER_AUDIT_LOG_WRITER_FAILED_TO_WRITE_TO_FILE ; SQLSTATE: HY000 Message: Error writing file \'%s\' (errno: %d - %s). Error number: MY-011208 ; Symbol: ER_AUDIT_LOG_EC_WRITER_FAILED_TO_INIT_ENCRYPTION ; SQLSTATE: HY000 Message: Could not initialize audit log file encryption. Error number: MY-011209 ; Symbol: ER_AUDIT_LOG_EC_WRITER_FAILED_TO_INIT_COMPRESSION ; SQLSTATE: HY000 Message: Could not initialize audit log file compression. Error number: MY-011210 ; Symbol: ER_AUDIT_LOG_EC_WRITER_FAILED_TO_CREATE_FILE ; SQLSTATE: HY000 Message: Could not create '%s' file for audit logging. Error number: MY-011211 ; Symbol: ER_AUDIT_LOG_RENAME_LOG_FILE_BEFORE_FLUSH ; SQLSTATE: HY000 Message: Audit log file (%s) must be manually renamed before audit_log_flush is set to true. Error number: MY-011213 ; Symbol: ER_AUDIT_LOG_JSON_READER_FAILED_TO_PARSE ; SQLSTATE: HY000 Message: Error parsing JSON event. Event not accessible. Error number: MY-011215 ; Symbol: ER_AUDIT_LOG_JSON_READER_FAILED_TO_OPEN_FILE ; SQLSTATE: HY000 Message: Could not open JSON file for reading. Reading next file if exists. Error number: MY-011216 ; Symbol: ER_AUDIT_LOG_JSON_READER_FILE_PARSING_ERROR ; SQLSTATE: HY000 Message: JSON file parsing error. Reading next file if exists Error number: MY-011219 ; Symbol: ER_AUDIT_LOG_FILTER_FAILED_TO_STORE_TABLE_FLDS ; SQLSTATE: HY000 Message: Could not store field of the %s table. Error number: MY-011220 ; Symbol: ER_AUDIT_LOG_FILTER_FAILED_TO_UPDATE_TABLE ; SQLSTATE: HY000 Message: Could not update %s table. Error number: MY-011221 ; Symbol: ER_AUDIT_LOG_FILTER_FAILED_TO_INSERT_INTO_TABLE ; SQLSTATE: HY000 Message: Could not insert into %s table. Error number: MY-011222 ; Symbol: ER_AUDIT_LOG_FILTER_FAILED_TO_DELETE_FROM_TABLE ; SQLSTATE: HY000 Message: Could not delete from %s table. Error number: MY-011223 ; Symbol: ER_AUDIT_LOG_FILTER_FAILED_TO_INIT_TABLE_FOR_READ ; SQLSTATE: HY000 Message: Could not initialize %s table for reading. Error number: MY-011224 ; Symbol: ER_AUDIT_LOG_FILTER_FAILED_TO_READ_TABLE ; SQLSTATE: HY000 Message: Could not read %s table. Error number: MY-011225 ; Symbol: ER_AUDIT_LOG_FILTER_FAILED_TO_CLOSE_TABLE_AFTER_READING ; SQLSTATE: HY000 Message: Could not close %s table reading. Error number: MY-011226 ; Symbol: ER_AUDIT_LOG_FILTER_USER_AND_HOST_CANNOT_BE_EMPTY ; SQLSTATE: HY000 Message: Both user and host columns of %s table cannot be empty. Error number: MY-011227 ; Symbol: ER_AUDIT_LOG_FILTER_FLD_FILTERNAME_CANNOT_BE_EMPTY ; SQLSTATE: HY000 Message: Filtername column of %s table cannot be empty. Error number: MY-011228 ; Symbol: ER_VALIDATE_PWD_DICT_FILE_NOT_SPECIFIED ; SQLSTATE: HY000 Message: Dictionary file not specified Error number: MY-011231 ; Symbol: ER_VALIDATE_PWD_FAILED_TO_READ_DICT_FILE ; SQLSTATE: HY000 Message: Exception while reading the dictionary file Error number: MY-011232 ; Symbol: ER_VALIDATE_PWD_FAILED_TO_GET_FLD_FROM_SECURITY_CTX ; SQLSTATE: HY000 Message: Can't retrieve the %s from the security context Error number: MY-011233 ; Symbol: ER_VALIDATE_PWD_FAILED_TO_GET_SECURITY_CTX ; SQLSTATE: HY000 Message: Can't retrieve the security context Error number: MY-011243 ; Symbol: ER_XPLUGIN_USING_SSL_FOR_TLS_CONNECTION ; SQLSTATE: HY000 Message: Using %s for TLS connections Error number: MY-011244 ; Symbol: ER_XPLUGIN_REFERENCE_TO_SECURE_CONN_WITH_XPLUGIN ; SQLSTATE: HY000 Message: For more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation Error number: MY-011247 ; Symbol: ER_SHA_PWD_FAILED_TO_GENERATE_MULTI_ROUND_HASH ; SQLSTATE: HY000 Message: Error in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problem Error number: MY-011250 ; Symbol: ER_PLUGIN_COMMON_FAILED_TO_OPEN_FILTER_TABLES ; SQLSTATE: HY000 Message: Failed to open the %s filter tables Error number: MY-011257 ; Symbol: ER_SYS_VAR_COMPONENT_VARIABLE_SET_READ_ONLY ; SQLSTATE: HY000 Message: variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag. Error number: MY-011258 ; Symbol: ER_SYS_VAR_COMPONENT_UNKNOWN_VARIABLE_TYPE ; SQLSTATE: HY000 Message: Unknown variable type code 0x%x in component '%s'. Error number: MY-011259 ; Symbol: ER_SYS_VAR_COMPONENT_FAILED_TO_PARSE_VARIABLE_OPTIONS ; SQLSTATE: HY000 Message: Parsing options for variable '%s' failed. Error number: MY-011260 ; Symbol: ER_SYS_VAR_COMPONENT_FAILED_TO_MAKE_VARIABLE_PERSISTENT ; SQLSTATE: HY000 Message: Setting persistent options for component variable '%s' failed. Message: Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it. Message: Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server. Error number: MY-011269 ; Symbol: ER_NOT_IMPLEMENTED_GET_TABLESPACE_STATISTICS ; SQLSTATE: HY000 Message: The storage engine '%s' does not provide dynamic table statistics Error number: MY-011279 ; Symbol: ER_CONN_CONTROL_EVENT_COORDINATOR_INIT_FAILED ; SQLSTATE: HY000 Message: Failed to initialize Connection_event_coordinator Error number: MY-011280 ; Symbol: ER_CONN_CONTROL_STAT_CONN_DELAY_TRIGGERED_UPDATE_FAILED ; SQLSTATE: HY000 Message: Failed to update connection delay triggered stats Error number: MY-011281 ; Symbol: ER_CONN_CONTROL_STAT_CONN_DELAY_TRIGGERED_RESET_FAILED ; SQLSTATE: HY000 Message: Failed to reset connection delay triggered stats Error number: MY-011282 ; Symbol: ER_CONN_CONTROL_INVALID_CONN_DELAY_TYPE ; SQLSTATE: HY000 Message: Unexpected option type for connection delay. Error number: MY-011283 ; Symbol: ER_CONN_CONTROL_DELAY_ACTION_INIT_FAILED ; SQLSTATE: HY000 Message: Failed to initialize Connection_delay_action Error number: MY-011284 ; Symbol: ER_CONN_CONTROL_FAILED_TO_SET_CONN_DELAY ; SQLSTATE: HY000 Message: Could not set %s delay for connection delay. Error number: MY-011285 ; Symbol: ER_CONN_CONTROL_FAILED_TO_UPDATE_CONN_DELAY_HASH ; SQLSTATE: HY000 Message: Failed to update connection delay hash for account : %s Error number: MY-011292 ; Symbol: ER_XPLUGIN_FAILED_TO_PREPARE_IO_INTERFACES ; SQLSTATE: HY000 Message: Preparation of I/O interfaces failed, X Protocol won't be accessible Error number: MY-011293 ; Symbol: ER_XPLUGIN_SRV_SESSION_INIT_THREAD_FAILED ; SQLSTATE: HY000 Message: srv_session_init_thread returned error Error number: MY-011294 ; Symbol: ER_XPLUGIN_UNABLE_TO_USE_USER_SESSION_ACCOUNT ; SQLSTATE: HY000 Message: Unable to use user mysql.session account when connecting the server for internal plugin requests. Error number: MY-011295 ; Symbol: ER_XPLUGIN_REFERENCE_TO_USER_ACCOUNT_DOC_SECTION ; SQLSTATE: HY000 Message: For more information, please see the X Plugin User Account section in the MySQL documentation Error number: MY-011296 ; Symbol: ER_XPLUGIN_UNEXPECTED_EXCEPTION_DISPATCHING_CMD ; SQLSTATE: HY000 Message: %s: Unexpected exception dispatching command: %s Error number: MY-011305 ; Symbol: ER_XPLUGIN_FAILED_TO_CREATE_SESSION_FOR_CONN ; SQLSTATE: HY000 Message: %s: Error creating session for connection from %s Error number: MY-011306 ; Symbol: ER_XPLUGIN_FAILED_TO_INITIALIZE_SESSION ; SQLSTATE: HY000 Message: %s: Error initializing session for connection: %s Error number: MY-011309 ; Symbol: ER_XPLUGIN_FAILED_TO_SET_MIN_NUMBER_OF_WORKERS ; SQLSTATE: HY000 Message: Unable to set minimal number of workers to %u; actual value is %i Error number: MY-011315 ; Symbol: ER_XPLUGIN_PEER_DISCONNECTED_WHILE_READING_MSG_BODY ; SQLSTATE: HY000 Message: %s: peer disconnected while reading message body Error number: MY-011316 ; Symbol: ER_XPLUGIN_READ_FAILED_CLOSING_CONNECTION ; SQLSTATE: HY000 Message: client_id:%s - %s while reading from socket, closing connection Error number: MY-011327 ; Symbol: ER_XPLUGIN_EXISTING_USER_ACCOUNT_WITH_INCOMPLETE_GRANTS ; SQLSTATE: HY000 Message: Using existing %s account for authentication. Incomplete grants will be fixed Error number: MY-011345 ; Symbol: ER_XPLUGIN_FAILED_TO_SET_SO_REUSEADDR_FLAG ; SQLSTATE: HY000 Message: Failed to set SO_REUSEADDR flag (error: %d). Error number: MY-011346 ; Symbol: ER_XPLUGIN_FAILED_TO_OPEN_INTERNAL_SESSION ; SQLSTATE: HY000 Message: Could not open internal MySQL session Error number: MY-011351 ; Symbol: ER_XPLUGIN_FAILED_TO_RESET_IPV6_V6ONLY_FLAG ; SQLSTATE: HY000 Message: Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only. Error number: MY-011358 ; Symbol: ER_KEYRING_CHECK_KEY_FAILED_DUE_TO_INVALID_KEY ; SQLSTATE: HY000 Message: Error while %s key: invalid key_type Error number: MY-011359 ; Symbol: ER_KEYRING_CHECK_KEY_FAILED_DUE_TO_EMPTY_KEY_ID ; SQLSTATE: HY000 Message: Error while %s key: key_id cannot be empty Error number: MY-011360 ; Symbol: ER_KEYRING_OPERATION_FAILED_DUE_TO_INTERNAL_ERROR ; SQLSTATE: HY000 Message: Failed to %s due to internal exception inside %s plugin Error number: MY-011363 ; Symbol: ER_KEYRING_FAILED_TO_RESTORE_FROM_BACKUP_FILE ; SQLSTATE: HY000 Message: Error while restoring keyring from backup file cannot overwrite keyring with backup Error number: MY-011364 ; Symbol: ER_KEYRING_FAILED_TO_FLUSH_KEYRING_TO_FILE ; SQLSTATE: HY000 Message: Error while flushing in-memory keyring into keyring file Error number: MY-011371 ; Symbol: ER_KEYRING_FAILED_TO_LOAD_KEYRING_CONTENT ; SQLSTATE: HY000 Message: Error while loading keyring content. The keyring might be malformed Error number: MY-011372 ; Symbol: ER_KEYRING_FAILED_TO_FLUSH_KEYS_TO_KEYRING ; SQLSTATE: HY000 Message: Could not flush keys to keyring Error number: MY-011373 ; Symbol: ER_KEYRING_FAILED_TO_FLUSH_KEYS_TO_KEYRING_BACKUP ; SQLSTATE: HY000 Message: Could not flush keys to keyring's backup Error number: MY-011374 ; Symbol: ER_KEYRING_KEY_FETCH_FAILED_DUE_TO_EMPTY_KEY_ID ; SQLSTATE: HY000 Message: Error while fetching key: key_id cannot be empty Error number: MY-011375 ; Symbol: ER_KEYRING_FAILED_TO_REMOVE_KEY_DUE_TO_EMPTY_ID ; SQLSTATE: HY000 Message: Error while removing key: key_id cannot be empty Error number: MY-011376 ; Symbol: ER_KEYRING_OKV_INCORRECT_KEY_VAULT_CONFIGURED ; SQLSTATE: HY000 Message: For keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materials Error number: MY-011377 ; Symbol: ER_KEYRING_OKV_INIT_FAILED_DUE_TO_INCORRECT_CONF ; SQLSTATE: HY000 Message: keyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running. Error number: MY-011378 ; Symbol: ER_KEYRING_OKV_INIT_FAILED_DUE_TO_INTERNAL_ERROR ; SQLSTATE: HY000 Message: keyring_okv initialization failure due to internal exception inside the plugin Error number: MY-011380 ; Symbol: ER_KEYRING_OKV_INVALID_KEY_LENGTH_FOR_CIPHER ; SQLSTATE: HY000 Message: Invalid key length for given block cipher Error number: MY-011381 ; Symbol: ER_KEYRING_OKV_FAILED_TO_GENERATE_KEY_DUE_TO_INTERNAL_ERROR ; SQLSTATE: HY000 Message: Failed to generate a key due to internal exception inside keyring_okv plugin Error number: MY-011382 ; Symbol: ER_KEYRING_OKV_FAILED_TO_FIND_SERVER_ENTRY ; SQLSTATE: HY000 Message: Could not find entry for server in configuration file %s Error number: MY-011383 ; Symbol: ER_KEYRING_OKV_FAILED_TO_FIND_STANDBY_SERVER_ENTRY ; SQLSTATE: HY000 Message: Could not find entry for standby server in configuration file %s Error number: MY-011384 ; Symbol: ER_KEYRING_OKV_FAILED_TO_PARSE_CONF_FILE ; SQLSTATE: HY000 Message: Could not parse the %s file provided Error number: MY-011386 ; Symbol: ER_KEYRING_OKV_FAILED_TO_INIT_SSL_LAYER ; SQLSTATE: HY000 Message: Could not initialize ssl layer Error number: MY-011388 ; Symbol: ER_KEYRING_OKV_CONNECTION_TO_SERVER_FAILED ; SQLSTATE: HY000 Message: Could not connect to the OKV server Error number: MY-011395 ; Symbol: ER_KEYRING_OKV_FAILED_TO_STORE_OR_GENERATE_KEY ; SQLSTATE: HY000 Message: Could not store/generate the key - failed to set key attribute x-key-ready Error number: MY-011396 ; Symbol: ER_KEYRING_OKV_FAILED_TO_RETRIEVE_KEY_SIGNATURE ; SQLSTATE: HY000 Message: Could not retrieve key signature from custom attributes Error number: MY-011398 ; Symbol: ER_KEYRING_OKV_FAILED_TO_LOAD_SSL_TRUST_STORE ; SQLSTATE: HY000 Message: Error loading trust store Error number: MY-011399 ; Symbol: ER_KEYRING_OKV_FAILED_TO_SET_CERTIFICATE_FILE ; SQLSTATE: HY000 Message: Error setting the certificate file. Message: keyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct. Message: keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct. Error number: MY-011417 ; Symbol: ER_KEYRING_AWS_FAILED_TO_OPEN_CONF_FILE ; SQLSTATE: HY000 Message: Could not open keyring_aws configuration file: %s. OS returned this error: %s Error number: MY-011418 ; Symbol: ER_KEYRING_AWS_FAILED_TO_ACCESS_KEY_ID_FROM_CONF_FILE ; SQLSTATE: HY000 Message: Could not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %s Error number: MY-011419 ; Symbol: ER_KEYRING_AWS_FAILED_TO_ACCESS_KEY_FROM_CONF_FILE ; SQLSTATE: HY000 Message: Could not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %s Error number: MY-011422 ; Symbol: ER_KEYRING_AWS_FAILED_TO_ACCESS_OR_CREATE_KEYRING_DIR ; SQLSTATE: HY000 Message: Unable to create/access keyring directory. Error number: MY-011423 ; Symbol: ER_KEYRING_AWS_FAILED_TO_ACCESS_OR_CREATE_KEYRING_DATA_FILE ; SQLSTATE: HY000 Message: Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location. Error number: MY-011424 ; Symbol: ER_KEYRING_AWS_FAILED_TO_INIT_DUE_TO_INTERNAL_ERROR ; SQLSTATE: HY000 Message: keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s: Error number: MY-011425 ; Symbol: ER_KEYRING_AWS_FAILED_TO_ACCESS_DATA_FILE ; SQLSTATE: HY000 Message: Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Server Error number: MY-011427 ; Symbol: ER_KEYRING_AWS_FAILED_TO_GET_KMS_CREDENTIAL_FROM_CONF_FILE ; SQLSTATE: HY000 Message: Could not get AWS KMS credentials from the configuration Error number: MY-011429 ; Symbol: ER_KEYRING_AWS_FAILED_TO_INIT_DUE_TO_PLUGIN_INTERNAL_ERROR ; SQLSTATE: HY000 Message: keyring_aws initialization failure due to internal exception inside the plugin Error number: MY-011430 ; Symbol: ER_KEYRING_AWS_INVALID_KEY_LENGTH_FOR_CIPHER ; SQLSTATE: HY000 Message: Invalid key length for given block cipher Error number: MY-011431 ; Symbol: ER_KEYRING_AWS_FAILED_TO_GENERATE_KEY_DUE_TO_INTERNAL_ERROR ; SQLSTATE: HY000 Message: Failed to generate a key due to internal exception inside keyring_file plugin Error number: MY-011433 ; Symbol: ER_KEYRING_AWS_FOUND_MALFORMED_BACKUP_FILE ; SQLSTATE: HY000 Message: Found malformed keyring backup file - removing it Error number: MY-011434 ; Symbol: ER_KEYRING_AWS_FAILED_TO_RESTORE_FROM_BACKUP_FILE ; SQLSTATE: HY000 Message: Error while restoring keyring from backup file cannot overwrite keyring with backup Error number: MY-011435 ; Symbol: ER_KEYRING_AWS_FAILED_TO_FLUSH_KEYRING_TO_FILE ; SQLSTATE: HY000 Message: Error while flushing in-memory keyring into keyring file Message: Could not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %s Error number: MY-011438 ; Symbol: ER_KEYRING_AWS_FAILED_TO_GENERATE_NEW_KEY ; SQLSTATE: HY000 Message: Could not generate a new key. AWS KMS returned this error: %s Error number: MY-011440 ; Symbol: ER_KEYRING_AWS_FAILED_TO_RE_ENCRYPT_KEY ; SQLSTATE: HY000 Message: Could not re-encrypt key. AWS KMS returned this error: %s Error number: MY-011450 ; Symbol: ER_GRP_RPL_APPLIER_PIPELINE_NOT_DISPOSED ; SQLSTATE: HY000 Message: The group replication applier pipeline was not properly disposed. Check the error log for further info. Error number: MY-011451 ; Symbol: ER_GRP_RPL_APPLIER_THD_EXECUTION_ABORTED ; SQLSTATE: HY000 Message: The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group. Error number: MY-011452 ; Symbol: ER_GRP_RPL_APPLIER_EXECUTION_FATAL_ERROR ; SQLSTATE: HY000 Message: Fatal error during execution on the Applier process of Group Replication. The server will now leave the group. Error number: MY-011454 ; Symbol: ER_GRP_RPL_ERROR_SENDING_SINGLE_PRIMARY_MSSG ; SQLSTATE: HY000 Message: Error sending single primary message informing that primary did apply relay logs. Error number: MY-011457 ; Symbol: ER_GRP_RPL_BROADCAST_COMMIT_TRANS_MSSG_FAILED ; SQLSTATE: HY000 Message: Broadcast of committed transactions message failed. Error number: MY-011459 ; Symbol: ER_GRP_RPL_ADD_GRPSID_TO_GRPGTIDSID_MAP_ERROR ; SQLSTATE: HY000 Message: Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization. Error number: MY-011460 ; Symbol: ER_GRP_RPL_UPDATE_GRPGTID_EXECUTED_ERROR ; SQLSTATE: HY000 Message: Error updating group_gtid_executed GITD set during the Certification module initialization. Message: Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error. Error number: MY-011463 ; Symbol: ER_GRP_RPL_ERROR_FETCHING_GTID_EXECUTED_SET ; SQLSTATE: HY000 Message: Error when extracting this member GTID executed set. Certification module can't be properly initialized. Error number: MY-011464 ; Symbol: ER_GRP_RPL_ADD_GTID_TO_GRPGTID_EXECUTED_ERROR ; SQLSTATE: HY000 Message: Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization. Error number: MY-011466 ; Symbol: ER_GRP_RPL_ADD_RETRIEVED_SET_TO_GRP_GTID_EXECUTED_ERROR ; SQLSTATE: HY000 Message: Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization. Error number: MY-011467 ; Symbol: ER_GRP_RPL_CERTIFICATION_INITIALIZATION_FAILURE ; SQLSTATE: HY000 Message: Error during Certification module initialization. Error number: MY-011468 ; Symbol: ER_GRP_RPL_UPDATE_LAST_CONFLICT_FREE_TRANS_ERROR ; SQLSTATE: HY000 Message: Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction. Error number: MY-011469 ; Symbol: ER_GRP_RPL_UPDATE_TRANS_SNAPSHOT_REF_VER_ERROR ; SQLSTATE: HY000 Message: Error updating transaction snapshot version reference for internal storage. Message: Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name. Message: There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues. Error number: MY-011480 ; Symbol: ER_GRP_RPL_PROCESS_INTERSECTION_GTID_SET_ERROR ; SQLSTATE: HY000 Message: Error processing intersection of stable transactions set. Error number: MY-011482 ; Symbol: ER_GRP_RPL_CANT_READ_GRP_GTID_EXTRACTED ; SQLSTATE: HY000 Message: Error reading group_gtid_extracted from the View_change_log_event. Error number: MY-011484 ; Symbol: ER_GRP_RPL_INIT_CERTIFICATION_INFO_FAILURE ; SQLSTATE: HY000 Message: Error during certification_info initialization. Error number: MY-011488 ; Symbol: ER_GRP_RPL_CERTIFIER_MSSG_PROCESS_ERROR ; SQLSTATE: HY000 Message: Error processing message in Certifier. Error number: MY-011491 ; Symbol: ER_GRP_RPL_DISABLE_SRV_READ_MODE_RESTRICTED ; SQLSTATE: HY000 Message: When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually. Message: This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership. Message: This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership. Error number: MY-011497 ; Symbol: ER_GRP_RPL_CHANGE_GRP_MEM_NOT_PROCESSED ; SQLSTATE: HY000 Message: A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option. Message: The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked. Error number: MY-011513 ; Symbol: ER_GRP_RPL_SUPER_READ_ONLY_ACTIVATE_ERROR ; SQLSTATE: HY000 Message: Error when activating super_read_only mode on start. The member will now exit the group. Message: Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate. Message: Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery. Message: Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete. Error number: MY-011524 ; Symbol: ER_GRP_RPL_MEMBER_VERSION_LOWER_THAN_GRP ; SQLSTATE: HY000 Message: Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join. Error number: MY-011525 ; Symbol: ER_GRP_RPL_LOCAL_GTID_SETS_PROCESS_ERROR ; SQLSTATE: HY000 Message: Error processing local GTID sets when comparing this member transactions against the group. Error number: MY-011526 ; Symbol: ER_GRP_RPL_MEMBER_TRANS_GREATER_THAN_GRP ; SQLSTATE: HY000 Message: This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %s Message: The member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group. Error number: MY-011528 ; Symbol: ER_GRP_RPL_TRANS_WRITE_SET_EXTRACT_DIFF_FROM_GRP ; SQLSTATE: HY000 Message: The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group. Error number: MY-011529 ; Symbol: ER_GRP_RPL_MEMBER_CFG_INCOMPATIBLE_WITH_GRP_CFG ; SQLSTATE: HY000 Message: The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]). Error number: MY-011530 ; Symbol: ER_GRP_RPL_MEMBER_STOP_RPL_CHANNELS_ERROR ; SQLSTATE: HY000 Message: Error stopping all replication channels while server was leaving the group. %s Message: Detected previous RESET BINARY LOGS AND GTIDS invocation or an issue exists in the group replication applier relay log. Purging existing applier logs. Error number: MY-011532 ; Symbol: ER_GRP_RPL_RESET_APPLIER_MODULE_LOGS_ERROR ; SQLSTATE: HY000 Message: Unknown error occurred while resetting applier's module logs. Error number: MY-011537 ; Symbol: ER_GRP_RPL_REPLICA_IO_THD_PRIMARY_UNKNOWN ; SQLSTATE: HY000 Message: Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known. Error number: MY-011538 ; Symbol: ER_GRP_RPL_SALVE_IO_THD_ON_SECONDARY_MEMBER ; SQLSTATE: HY000 Message: Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member. Error number: MY-011539 ; Symbol: ER_GRP_RPL_REPLICA_SQL_THD_PRIMARY_UNKNOWN ; SQLSTATE: HY000 Message: Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known. Error number: MY-011540 ; Symbol: ER_GRP_RPL_REPLICA_SQL_THD_ON_SECONDARY_MEMBER ; SQLSTATE: HY000 Message: Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member. Message: Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication. Error number: MY-011549 ; Symbol: ER_GRP_RPL_FETCH_FORMAT_DESC_LOG_EVENT_FAILED ; SQLSTATE: HY000 Message: Failed to fetch Format_description_log_event containing required server info for applier Error number: MY-011550 ; Symbol: ER_GRP_RPL_FETCH_TRANS_CONTEXT_LOG_EVENT_FAILED ; SQLSTATE: HY000 Message: Failed to fetch Transaction_context_log_event containing required transaction info for certification Error number: MY-011551 ; Symbol: ER_GRP_RPL_FETCH_SNAPSHOT_VERSION_FAILED ; SQLSTATE: HY000 Message: Failed to read snapshot version from transaction context event required for certification Error number: MY-011553 ; Symbol: ER_GRP_RPL_UPDATE_SERV_CERTIFICATE_FAILED ; SQLSTATE: HY000 Message: Unable to update certification result on server side, thread_id: %lu Error number: MY-011554 ; Symbol: ER_GRP_RPL_ADD_GTID_INFO_WITH_LOCAL_GTID_FAILED ; SQLSTATE: HY000 Message: Unable to add gtid information to the group_gtid_executed set when gtid was provided for local transactions Error number: MY-011555 ; Symbol: ER_GRP_RPL_ADD_GTID_INFO_WITHOUT_LOCAL_GTID_FAILED ; SQLSTATE: HY000 Message: Unable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactions Error number: MY-011556 ; Symbol: ER_GRP_RPL_NOTIFY_CERTIFICATION_OUTCOME_FAILED ; SQLSTATE: HY000 Message: Failed to notify certification outcome Error number: MY-011557 ; Symbol: ER_GRP_RPL_ADD_GTID_INFO_WITH_REMOTE_GTID_FAILED ; SQLSTATE: HY000 Message: Unable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactions Error number: MY-011558 ; Symbol: ER_GRP_RPL_ADD_GTID_INFO_WITHOUT_REMOTE_GTID_FAILED ; SQLSTATE: HY000 Message: Unable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactions Error number: MY-011559 ; Symbol: ER_GRP_RPL_FETCH_VIEW_CHANGE_LOG_EVENT_FAILED ; SQLSTATE: HY000 Message: Failed to fetch View_change_log_event containing required info for certification Message: Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade. Message: The member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connection Error number: MY-011574 ; Symbol: ER_GRP_RPL_MAXIMUM_CONNECTION_RETRIES_REACHED ; SQLSTATE: HY000 Message: Maximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery. Error number: MY-011575 ; Symbol: ER_GRP_RPL_ALL_DONORS_LEFT_ABORT_RECOVERY ; SQLSTATE: HY000 Message: All donors left. Aborting group replication incremental recovery. Error number: MY-011576 ; Symbol: ER_GRP_RPL_ESTABLISH_RECOVERY_WITH_DONOR ; SQLSTATE: HY000 Message: Establishing group recovery connection with a possible donor. Attempt %d/%d Error number: MY-011577 ; Symbol: ER_GRP_RPL_ESTABLISH_RECOVERY_WITH_ANOTHER_DONOR ; SQLSTATE: HY000 Message: Retrying group recovery connection with another donor. Attempt %d/%d Error number: MY-011580 ; Symbol: ER_GRP_RPL_ESTABLISHING_CONN_GRP_REC_DONOR ; SQLSTATE: HY000 Message: Establishing connection to a group replication recovery donor %s at %s port: %d. Message: There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable. Message: For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery. Error number: MY-011588 ; Symbol: ER_GRP_RPL_UNABLE_TO_KILL_CONN_REC_DONOR_APPLIER ; SQLSTATE: HY000 Message: Unable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown. Error number: MY-011589 ; Symbol: ER_GRP_RPL_UNABLE_TO_KILL_CONN_REC_DONOR_FAILOVER ; SQLSTATE: HY000 Message: Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown. Error number: MY-011590 ; Symbol: ER_GRP_RPL_FAILED_TO_NOTIFY_GRP_MEMBERSHIP_EVENT ; SQLSTATE: HY000 Message: Unexpected error when notifying an internal component named %s regarding a group membership event. Error number: MY-011591 ; Symbol: ER_GRP_RPL_FAILED_TO_BROADCAST_GRP_MEMBERSHIP_NOTIFICATION ; SQLSTATE: HY000 Message: An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning! Error number: MY-011592 ; Symbol: ER_GRP_RPL_FAILED_TO_BROADCAST_MEMBER_STATUS_NOTIFICATION ; SQLSTATE: HY000 Message: An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning! Error number: MY-011593 ; Symbol: ER_GRP_RPL_OOM_FAILED_TO_GENERATE_IDENTIFICATION_HASH ; SQLSTATE: HY000 Message: No memory to generate write identification hash Error number: MY-011594 ; Symbol: ER_GRP_RPL_WRITE_IDENT_HASH_BASE64_ENCODING_FAILED ; SQLSTATE: HY000 Message: Base 64 encoding of the write identification hash failed Error number: MY-011599 ; Symbol: ER_GRP_RPL_CANNOT_EXECUTE_TRANS_WHILE_STOPPING ; SQLSTATE: HY000 Message: Transaction cannot be executed while Group Replication is stopping. Error number: MY-011600 ; Symbol: ER_GRP_RPL_CANNOT_EXECUTE_TRANS_WHILE_RECOVERING ; SQLSTATE: HY000 Message: Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE. Error number: MY-011601 ; Symbol: ER_GRP_RPL_CANNOT_EXECUTE_TRANS_IN_ERROR_STATE ; SQLSTATE: HY000 Message: Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the plugin Error number: MY-011602 ; Symbol: ER_GRP_RPL_CANNOT_EXECUTE_TRANS_IN_OFFLINE_MODE ; SQLSTATE: HY000 Message: Transaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the plugin Error number: MY-011603 ; Symbol: ER_GRP_RPL_MULTIPLE_CACHE_TYPE_NOT_SUPPORTED_FOR_SESSION ; SQLSTATE: HY000 Message: We can only use one cache type at a time on session %u Error number: MY-011604 ; Symbol: ER_GRP_RPL_FAILED_TO_REINIT_BINLOG_CACHE_FOR_READ ; SQLSTATE: HY000 Message: Failed to reinit binlog cache log for read on session %u Error number: MY-011605 ; Symbol: ER_GRP_RPL_FAILED_TO_CREATE_TRANS_CONTEXT ; SQLSTATE: HY000 Message: Failed to create the context of the current transaction on session %u Error number: MY-011606 ; Symbol: ER_GRP_RPL_FAILED_TO_EXTRACT_TRANS_WRITE_SET ; SQLSTATE: HY000 Message: Failed to extract the set of items written during the execution of the current transaction on session %u Error number: MY-011607 ; Symbol: ER_GRP_RPL_FAILED_TO_GATHER_TRANS_WRITE_SET ; SQLSTATE: HY000 Message: Failed to gather the set of items written during the execution of the current transaction on session %u Message: Error on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option. Error number: MY-011611 ; Symbol: ER_GRP_RPL_WRITE_TO_TRANSACTION_MESSAGE_FAILED ; SQLSTATE: HY000 Message: Error while writing to transaction message on session %u Error number: MY-011612 ; Symbol: ER_GRP_RPL_FAILED_TO_REGISTER_TRANS_OUTCOME_NOTIFICTION ; SQLSTATE: HY000 Message: Unable to register for getting notifications regarding the outcome of the transaction on session %u Error number: MY-011613 ; Symbol: ER_GRP_RPL_MSG_TOO_LONG_BROADCASTING_TRANS_FAILED ; SQLSTATE: HY000 Message: Error broadcasting transaction to the group on session %u. Message is too big. Error number: MY-011614 ; Symbol: ER_GRP_RPL_BROADCASTING_TRANS_TO_GRP_FAILED ; SQLSTATE: HY000 Message: Error while broadcasting the transaction to the group on session %u Error number: MY-011615 ; Symbol: ER_GRP_RPL_ERROR_WHILE_WAITING_FOR_CONFLICT_DETECTION ; SQLSTATE: HY000 Message: Error while waiting for conflict detection procedure to finish on session %u Error number: MY-011622 ; Symbol: ER_GRP_RPL_UNABLE_TO_EVALUATE_APPLIER_STATUS ; SQLSTATE: HY000 Message: Unable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption. Error number: MY-011625 ; Symbol: ER_GRP_RPL_UNABLE_TO_ENSURE_EXECUTION_REC ; SQLSTATE: HY000 Message: Unable to ensure the execution of group transactions received during recovery. Error number: MY-011628 ; Symbol: ER_GRP_RPL_READ_UNABLE_FOR_READ_ONLY_SUPER_READ_ONLY ; SQLSTATE: HY000 Message: Unable to read the server values for the read_only and super_read_only variables. Error number: MY-011629 ; Symbol: ER_GRP_RPL_UNABLE_TO_RESET_SERVER_READ_MODE ; SQLSTATE: HY000 Message: Unable to reset the server read mode settings. Try to reset them manually. Error number: MY-011630 ; Symbol: ER_GRP_RPL_UNABLE_TO_CERTIFY_PLUGIN_TRANS ; SQLSTATE: HY000 Message: Due to a plugin error, some transactions were unable to be certified and will now rollback. Message: Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the service Error number: MY-011633 ; Symbol: ER_GRP_RPL_FAILED_TO_START_WITH_INVALID_SERVER_ID ; SQLSTATE: HY000 Message: Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0. Error number: MY-011635 ; Symbol: ER_GRP_RPL_PLUGIN_STRUCT_INIT_NOT_POSSIBLE_ON_SERVER_START ; SQLSTATE: HY000 Message: It was not possible to guarantee the initialization of plugin structures on server start Error number: MY-011636 ; Symbol: ER_GRP_RPL_FAILED_TO_ENABLE_SUPER_READ_ONLY_MODE ; SQLSTATE: HY000 Message: Could not enable the server read only mode and guarantee a safe recovery execution Error number: MY-011637 ; Symbol: ER_GRP_RPL_FAILED_TO_INIT_COMMUNICATION_ENGINE ; SQLSTATE: HY000 Message: Error on group communication engine initialization Error number: MY-011638 ; Symbol: ER_GRP_RPL_FAILED_TO_START_ON_SECONDARY_WITH_ASYNC_CHANNELS ; SQLSTATE: HY000 Message: Can't start group replication on secondary member with single-primary mode while asynchronous replication channels are running. Error number: MY-011639 ; Symbol: ER_GRP_RPL_FAILED_TO_START_COMMUNICATION_ENGINE ; SQLSTATE: HY000 Message: Error on group communication engine start Error number: MY-011640 ; Symbol: ER_GRP_RPL_TIMEOUT_ON_VIEW_AFTER_JOINING_GRP ; SQLSTATE: HY000 Message: Timeout on wait for view after joining group Error number: MY-011641 ; Symbol: ER_GRP_RPL_FAILED_TO_CALL_GRP_COMMUNICATION_INTERFACE ; SQLSTATE: HY000 Message: Error calling group communication interfaces Error number: MY-011642 ; Symbol: ER_GRP_RPL_MEMBER_SERVER_UUID_IS_INCOMPATIBLE_WITH_GRP ; SQLSTATE: HY000 Message: Member server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s. Message: Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s"; Error number: MY-011644 ; Symbol: ER_GRP_RPL_FAILED_TO_CONFIRM_IF_SERVER_LEFT_GRP ; SQLSTATE: HY000 Message: Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information. Error number: MY-011648 ; Symbol: ER_GRP_RPL_TIMEOUT_RECEIVING_VIEW_CHANGE_ON_SHUTDOWN ; SQLSTATE: HY000 Message: While leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more details Error number: MY-011649 ; Symbol: ER_GRP_RPL_REQUESTING_NON_MEMBER_SERVER_TO_LEAVE ; SQLSTATE: HY000 Message: Requesting to leave the group despite of not being a member Error number: MY-011652 ; Symbol: ER_GRP_RPL_FAILED_TO_ENABLE_READ_ONLY_MODE_ON_SHUTDOWN ; SQLSTATE: HY000 Message: On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed. Error number: MY-011653 ; Symbol: ER_GRP_RPL_RECOVERY_MODULE_TERMINATION_TIMED_OUT_ON_SHUTDOWN ; SQLSTATE: HY000 Message: On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more details Error number: MY-011654 ; Symbol: ER_GRP_RPL_APPLIER_TERMINATION_TIMED_OUT_ON_SHUTDOWN ; SQLSTATE: HY000 Message: On shutdown there was a timeout on the Group Replication applier termination. Error number: MY-011655 ; Symbol: ER_GRP_RPL_FAILED_TO_SHUTDOWN_REGISTRY_MODULE ; SQLSTATE: HY000 Message: Unexpected failure while shutting down registry module! Error number: MY-011657 ; Symbol: ER_GRP_RPL_FAILED_TO_REGISTER_SERVER_STATE_OBSERVER ; SQLSTATE: HY000 Message: Failure when registering the server state observers Error number: MY-011658 ; Symbol: ER_GRP_RPL_FAILED_TO_REGISTER_TRANS_STATE_OBSERVER ; SQLSTATE: HY000 Message: Failure when registering the transactions state observers Error number: MY-011659 ; Symbol: ER_GRP_RPL_FAILED_TO_REGISTER_BINLOG_STATE_OBSERVER ; SQLSTATE: HY000 Message: Failure when registering the binlog state observers Error number: MY-011661 ; Symbol: ER_GRP_RPL_FAILED_TO_STOP_ON_PLUGIN_UNINSTALL ; SQLSTATE: HY000 Message: Failure when stopping Group Replication on plugin uninstall Error number: MY-011662 ; Symbol: ER_GRP_RPL_FAILED_TO_UNREGISTER_SERVER_STATE_OBSERVER ; SQLSTATE: HY000 Message: Failure when unregistering the server state observers Error number: MY-011663 ; Symbol: ER_GRP_RPL_FAILED_TO_UNREGISTER_TRANS_STATE_OBSERVER ; SQLSTATE: HY000 Message: Failure when unregistering the transactions state observers Error number: MY-011664 ; Symbol: ER_GRP_RPL_FAILED_TO_UNREGISTER_BINLOG_STATE_OBSERVER ; SQLSTATE: HY000 Message: Failure when unregistering the binlog state observers Error number: MY-011666 ; Symbol: ER_GRP_RPL_FAILED_TO_PARSE_THE_GRP_NAME ; SQLSTATE: HY000 Message: Unable to parse the group_replication_group_name. Error number: MY-011667 ; Symbol: ER_GRP_RPL_FAILED_TO_GENERATE_SIDNO_FOR_GRP ; SQLSTATE: HY000 Message: Unable to parse the group_replication_group_name. Error number: MY-011668 ; Symbol: ER_GRP_RPL_APPLIER_NOT_STARTED_DUE_TO_RUNNING_PREV_SHUTDOWN ; SQLSTATE: HY000 Message: Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete. Error number: MY-011669 ; Symbol: ER_GRP_RPL_FAILED_TO_INIT_APPLIER_MODULE ; SQLSTATE: HY000 Message: Unable to initialize the Group Replication applier module. Message: Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s" Error number: MY-011672 ; Symbol: ER_GRP_RPL_ABORTS_AS_SSL_NOT_SUPPORTED_BY_MYSQLD ; SQLSTATE: HY000 Message: MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abort Error number: MY-011674 ; Symbol: ER_GRP_RPL_UNABLE_TO_INIT_COMMUNICATION_ENGINE ; SQLSTATE: HY000 Message: Unable to initialize the group communication engine Error number: MY-011679 ; Symbol: ER_GRP_RPL_APPLIER_METADATA_REPO_MUST_BE_TABLE ; SQLSTATE: HY000 Message: Applier metadata repository must be set to TABLE Error number: MY-011680 ; Symbol: ER_GRP_RPL_CONNECTION_METADATA_REPO_MUST_BE_TABLE ; SQLSTATE: HY000 Message: Connection metadata repository must be set to TABLE. Error number: MY-011681 ; Symbol: ER_GRP_RPL_INCORRECT_TYPE_SET_FOR_PARALLEL_APPLIER ; SQLSTATE: HY000 Message: In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'. Error number: MY-011682 ; Symbol: ER_GRP_RPL_REPLICA_PRESERVE_COMMIT_ORDER_NOT_SET ; SQLSTATE: HY000 Message: Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads. Error number: MY-011683 ; Symbol: ER_GRP_RPL_SINGLE_PRIM_MODE_NOT_ALLOWED_WITH_UPDATE_EVERYWHERE ; SQLSTATE: HY000 Message: It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled. Error number: MY-011688 ; Symbol: ER_GRP_RPL_FLOW_CTRL_MIN_QUOTA_GREATER_THAN_MAX_QUOTA ; SQLSTATE: HY000 Message: group_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quota Error number: MY-011689 ; Symbol: ER_GRP_RPL_FLOW_CTRL_MIN_RECOVERY_QUOTA_GREATER_THAN_MAX_QUOTA ; SQLSTATE: HY000 Message: group_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quota Error number: MY-011690 ; Symbol: ER_GRP_RPL_FLOW_CTRL_MAX_QUOTA_SMALLER_THAN_MIN_QUOTAS ; SQLSTATE: HY000 Message: group_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quota Message: The given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limit Error number: MY-011694 ; Symbol: ER_GRP_RPL_GRP_COMMUNICATION_INIT_WITH_CONF ; SQLSTATE: HY000 Message: Initialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu' Error number: MY-011695 ; Symbol: ER_GRP_RPL_UNKNOWN_GRP_RPL_APPLIER_PIPELINE_REQUESTED ; SQLSTATE: HY000 Message: Unknown group replication applier pipeline requested Error number: MY-011696 ; Symbol: ER_GRP_RPL_FAILED_TO_BOOTSTRAP_EVENT_HANDLING_INFRASTRUCTURE ; SQLSTATE: HY000 Message: Unable to bootstrap group replication event handling infrastructure. Unknown handler type: %d Error number: MY-011697 ; Symbol: ER_GRP_RPL_APPLIER_HANDLER_NOT_INITIALIZED ; SQLSTATE: HY000 Message: One of the group replication applier handlers is null due to an initialization error Error number: MY-011699 ; Symbol: ER_GRP_RPL_APPLIER_HANDLER_ROLE_IS_IN_USE ; SQLSTATE: HY000 Message: A group replication applier handler role, that was marked as unique, is already in use. Error number: MY-011700 ; Symbol: ER_GRP_RPL_FAILED_TO_INIT_APPLIER_HANDLER ; SQLSTATE: HY000 Message: Error on group replication applier handler initialization Error number: MY-011701 ; Symbol: ER_GRP_RPL_SQL_SERVICE_FAILED_TO_INIT_SESSION_THREAD ; SQLSTATE: HY000 Message: Error when initializing a session thread for internal server connection. Error number: MY-011702 ; Symbol: ER_GRP_RPL_SQL_SERVICE_COMM_SESSION_NOT_INITIALIZED ; SQLSTATE: HY000 Message: Error running internal SQL query: %s. The internal server communication session is not initialized Error number: MY-011703 ; Symbol: ER_GRP_RPL_SQL_SERVICE_SERVER_SESSION_KILLED ; SQLSTATE: HY000 Message: Error running internal SQL query: %s. The internal server session was killed or server is shutting down. Error number: MY-011704 ; Symbol: ER_GRP_RPL_SQL_SERVICE_FAILED_TO_RUN_SQL_QUERY ; SQLSTATE: HY000 Message: Error running internal SQL query: %s. Got internal SQL error: %s(%d) Error number: MY-011705 ; Symbol: ER_GRP_RPL_SQL_SERVICE_SERVER_INTERNAL_FAILURE ; SQLSTATE: HY000 Message: Error running internal SQL query: %s. Internal failure. Error number: MY-011706 ; Symbol: ER_GRP_RPL_SQL_SERVICE_RETRIES_EXCEEDED_ON_SESSION_STATE ; SQLSTATE: HY000 Message: Error, maximum number of retries exceeded when waiting for the internal server session state to be operating Error number: MY-011707 ; Symbol: ER_GRP_RPL_SQL_SERVICE_FAILED_TO_FETCH_SECURITY_CTX ; SQLSTATE: HY000 Message: Error when trying to fetch security context when contacting the server for internal plugin requests. Error number: MY-011708 ; Symbol: ER_GRP_RPL_SQL_SERVICE_SERVER_ACCESS_DENIED_FOR_USER ; SQLSTATE: HY000 Message: There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly. Error number: MY-011709 ; Symbol: ER_GRP_RPL_SQL_SERVICE_MAX_CONN_ERROR_FROM_SERVER ; SQLSTATE: HY000 Message: Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i. Error number: MY-011710 ; Symbol: ER_GRP_RPL_SQL_SERVICE_SERVER_ERROR_ON_CONN ; SQLSTATE: HY000 Message: Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: Error number: MY-011711 ; Symbol: ER_GRP_RPL_UNREACHABLE_MAJORITY_TIMEOUT_FOR_MEMBER ; SQLSTATE: HY000 Message: This member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option. Error number: MY-011712 ; Symbol: ER_GRP_RPL_SERVER_SET_TO_READ_ONLY_DUE_TO_ERRORS ; SQLSTATE: HY000 Message: The server was automatically set into read only mode after an error was detected. Error number: MY-011713 ; Symbol: ER_GRP_RPL_GMS_LISTENER_FAILED_TO_LOG_NOTIFICATION ; SQLSTATE: HY000 Message: Unable to log notification to table (errno: %lu) (res: %d)! Message: %s Error number: MY-011714 ; Symbol: ER_GRP_RPL_GRP_COMMUNICATION_ENG_INIT_FAILED ; SQLSTATE: HY000 Message: Failure in group communication engine '%s' initialization Error number: MY-011715 ; Symbol: ER_GRP_RPL_SET_GRP_COMMUNICATION_ENG_LOGGER_FAILED ; SQLSTATE: HY000 Message: Unable to set the group communication engine logger Error number: MY-011721 ; Symbol: ER_GRP_RPL_FORCE_MEMBER_VALUE_SET_ERROR ; SQLSTATE: HY000 Message: Error setting group_replication_force_members value '%s' on group communication interfaces Message: Timeout on wait for view after setting group_replication_force_members value '%s' into group communication interfaces Error number: MY-011724 ; Symbol: ER_GRP_RPL_BROADCAST_COMMIT_MSSG_TOO_BIG ; SQLSTATE: HY000 Message: Broadcast of committed transactions message failed. Message is too big. Message: Flow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%d Message: Flow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lld Error number: MY-011728 ; Symbol: ER_GRP_RPL_UNABLE_TO_CONVERT_PACKET_TO_EVENT ; SQLSTATE: HY000 Message: Unable to convert a packet into an event on the applier. Error: %s Error number: MY-011730 ; Symbol: ER_GRP_RPL_PIPELINE_REINIT_FAILED_WRITE ; SQLSTATE: HY000 Message: Failed to reinit group replication pipeline cache for write. Error number: MY-011731 ; Symbol: ER_GRP_RPL_UNABLE_TO_CONVERT_EVENT_TO_PACKET ; SQLSTATE: HY000 Message: Unable to convert the event into a packet on the applier. Error: %s Error number: MY-011738 ; Symbol: ER_GRP_RPL_REPLICA_APPLIER_THREAD_UNBLOCKED ; SQLSTATE: HY000 Message: The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now. Error number: MY-011739 ; Symbol: ER_GRP_RPL_REPLICA_APPLIER_THREAD_ERROR_OUT ; SQLSTATE: HY000 Message: The replica applier thread of channel '%s' will error out as the member failed to come ONLINE. Error number: MY-011740 ; Symbol: ER_LDAP_AUTH_FAILED_TO_CREATE_OR_GET_CONNECTION ; SQLSTATE: HY000 Message: LDAP authentication initialize: failed to create/ get connection from the pool. Error number: MY-011742 ; Symbol: ER_LDAP_AUTH_SKIPPING_USER_GROUP_SEARCH ; SQLSTATE: HY000 Message: Skipping group search, No group attribute mentioned Error number: MY-011743 ; Symbol: ER_LDAP_AUTH_POOL_DISABLE_MAX_SIZE_ZERO ; SQLSTATE: HY000 Message: Pool max size is 0, connection pool is disabled Error number: MY-011744 ; Symbol: ER_LDAP_AUTH_FAILED_TO_CREATE_LDAP_OBJECT_CREATOR ; SQLSTATE: HY000 Message: Connection pool initialization, failed to create LDAP object creator Error number: MY-011745 ; Symbol: ER_LDAP_AUTH_FAILED_TO_CREATE_LDAP_OBJECT ; SQLSTATE: HY000 Message: Connection pool initialization, failed to create LDAP object Error number: MY-011751 ; Symbol: ER_LDAP_AUTH_ZERO_MAX_POOL_SIZE_UNCHANGED ; SQLSTATE: HY000 Message: Pool max size old and new values are 0 Error number: MY-011762 ; Symbol: ER_LDAP_AUTH_USER_HAS_MULTIPLE_GRP_NAMES ; SQLSTATE: HY000 Message: For user %s has multiple user group names. Please check if group attribute name is correct Error number: MY-011767 ; Symbol: ER_LDAP_AUTH_FAILED_TO_INITIALIZE_POOL_IN_RECONSTRUCTING ; SQLSTATE: HY000 Message: Pool initialization failed: pool is already initialized Error number: MY-011768 ; Symbol: ER_LDAP_AUTH_FAILED_TO_INITIALIZE_POOL_IN_INIT_STATE ; SQLSTATE: HY000 Message: Pool initialization failed: pool is initializing Error number: MY-011769 ; Symbol: ER_LDAP_AUTH_FAILED_TO_INITIALIZE_POOL_IN_DEINIT_STATE ; SQLSTATE: HY000 Message: Pool initialization failed: pool is de-initializing Error number: MY-011770 ; Symbol: ER_LDAP_AUTH_FAILED_TO_DEINITIALIZE_POOL_IN_RECONSTRUCT_STATE ; SQLSTATE: HY000 Message: Failed to pool deinitialized: pool is already reconstructing Error number: MY-011771 ; Symbol: ER_LDAP_AUTH_FAILED_TO_DEINITIALIZE_NOT_READY_POOL ; SQLSTATE: HY000 Message: Failed to pool deinitialized : pool is not ready Error number: MY-011772 ; Symbol: ER_LDAP_AUTH_FAILED_TO_GET_CONNECTION_AS_PLUGIN_NOT_READY ; SQLSTATE: HY000 Message: Ldap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializing Error number: MY-011773 ; Symbol: ER_LDAP_AUTH_CONNECTION_POOL_INIT_FAILED ; SQLSTATE: HY000 Message: Connection pool has failed to initialized Error number: MY-011774 ; Symbol: ER_LDAP_AUTH_MAX_ALLOWED_CONNECTION_LIMIT_HIT ; SQLSTATE: HY000 Message: Ldap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit. Error number: MY-011776 ; Symbol: ER_LDAP_AUTH_PLUGIN_FAILED_TO_READ_PACKET ; SQLSTATE: HY000 Message: Plug-in has failed to read the packet from client Error number: MY-011778 ; Symbol: ER_LDAP_AUTH_GETTING_CONNECTION_FROM_POOL ; SQLSTATE: HY000 Message: Ldap_authentication::initialize: getting connection from pool. Error number: MY-011779 ; Symbol: ER_LDAP_AUTH_RETURNING_CONNECTION_TO_POOL ; SQLSTATE: HY000 Message: Ldap_authentication::de_initialize putting back connection in the pool Error number: MY-011780 ; Symbol: ER_LDAP_AUTH_SEARCH_USER_GROUP_ATTR_NOT_FOUND ; SQLSTATE: HY000 Message: Ldap_authentication::search_user_group no group attribute found Error number: MY-011786 ; Symbol: ER_LDAP_AUTH_CONNECTION_GET_LDAP_INFO_NULL ; SQLSTATE: HY000 Message: Ldap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info) Error number: MY-011801 ; Symbol: ER_LDAP_AUTH_POOL_GET_FAILED_TO_CREATE_CONNECTION ; SQLSTATE: HY000 Message: Connection pool get: Failed to create LDAP connection. %s Error number: MY-011802 ; Symbol: ER_LDAP_AUTH_FAILED_TO_CREATE_LDAP_CONNECTION ; SQLSTATE: HY000 Message: Failed to create new LDAP connection: %s Error number: MY-011803 ; Symbol: ER_LDAP_AUTH_FAILED_TO_ESTABLISH_TLS_CONNECTION ; SQLSTATE: HY000 Message: Failed to establish TLS connection: %s Error number: MY-011805 ; Symbol: ER_LDAP_AUTH_CONNECTION_POOL_REINIT_ENTER ; SQLSTATE: HY000 Message: Ldap_connection_pool::reinit Message: The path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket. Message: Cannot replicate to server with server_uuid='%s' 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. Message: Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory. Error number: MY-011812 ; Symbol: ER_VALIDATE_PWD_STATUS_VAR_REGISTRATION_FAILED ; SQLSTATE: HY000 Message: validate_password status variables registration failed. Error number: MY-011813 ; Symbol: ER_VALIDATE_PWD_STATUS_VAR_UNREGISTRATION_FAILED ; SQLSTATE: HY000 Message: validate_password status variables unregistration failed. Error number: MY-011816 ; Symbol: ER_VALIDATE_PWD_STRING_CONV_TO_LOWERCASE_FAILED ; SQLSTATE: HY000 Message: failed to convert the password string to lower case Error number: MY-011817 ; Symbol: ER_VALIDATE_PWD_STRING_CONV_TO_BUFFER_FAILED ; SQLSTATE: HY000 Message: failed to convert the password string into a buffer Error number: MY-011818 ; Symbol: ER_VALIDATE_PWD_STRING_HANDLER_MEM_ALLOCATION_FAILED ; SQLSTATE: HY000 Message: memory allocation failed for string handler Error number: MY-011819 ; Symbol: ER_VALIDATE_PWD_STRONG_POLICY_DICT_FILE_UNSPECIFIED ; SQLSTATE: HY000 Message: Since the validate_password_policy is mentioned as Strong, dictionary file must be specified Error number: MY-011820 ; Symbol: ER_VALIDATE_PWD_CONVERT_TO_BUFFER_FAILED ; SQLSTATE: HY000 Message: convert_to_buffer service failed Error number: MY-011821 ; Symbol: ER_VALIDATE_PWD_VARIABLE_REGISTRATION_FAILED ; SQLSTATE: HY000 Message: %s variable registration failed. Error number: MY-011822 ; Symbol: ER_VALIDATE_PWD_VARIABLE_UNREGISTRATION_FAILED ; SQLSTATE: HY000 Message: %s variable unregistration failed. Message: Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet. Message: You must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu. Message: Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended. Message: The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL. Message: posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information. Message: The datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories. Error number: MY-012213 ; Symbol: ER_IB_MSG_GENERAL_TABLESPACE_UNDER_DATADIR ; SQLSTATE: HY000 Message: A general tablespace cannot be located under the datadir. Cannot open file '%s'. Error number: MY-012214 ; Symbol: ER_IB_MSG_IMPLICIT_TABLESPACE_IN_DATADIR ; SQLSTATE: HY000 Message: A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'. Error number: MY-012445 ; Symbol: ER_IB_MSG_IBUF_CURSOR_RESTORATION_FAILED ; SQLSTATE: HY000 Message: ibuf cursor restoration fails!. ibuf record inserted to page %s:%s Error number: MY-012447 ; Symbol: ER_IB_MSG_IBUF_FAILED_TO_RESTORE_POSITION ; SQLSTATE: HY000 Message: Failed to restore ibuf position. Message: Blocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim. Message: Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %llu Message: The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s Error number: MY-012525 ; Symbol: ER_IB_MSG_LOG_FORMAT_OLD_AND_LOG_CORRUPTED ; SQLSTATE: HY000 Message: Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %s Error number: MY-012526 ; Symbol: ER_IB_MSG_LOG_FORMAT_OLD_AND_NO_CLEAN_SHUTDOWN ; SQLSTATE: HY000 Message: Upgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at Error number: MY-012531 ; Symbol: ER_IB_MSG_RECOVERY_CHECKPOINT_NOT_FOUND ; SQLSTATE: HY000 Message: No valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort. Error number: MY-012546 ; Symbol: ER_IB_MSG_RECOVERY_SKIPPED_IN_READ_ONLY_MODE ; SQLSTATE: HY000 Message: Skipped necessary redo log applying, --innodb-read-only Error number: MY-012554 ; Symbol: ER_IB_MSG_LOG_FILES_CREATED_BY_MEB_AND_READ_ONLY_MODE ; SQLSTATE: HY000 Message: Cannot restore from mysqlbackup, InnoDB running in read-only mode! Error number: MY-012559 ; Symbol: ER_IB_MSG_RECOVERY_CHECKPOINT_FROM_BEFORE_CLEAN_SHUTDOWN ; SQLSTATE: HY000 Message: Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu. Message: We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt! Error number: MY-012772 ; Symbol: ER_IB_IMPORT_INDEX_METADATA_READ_FAILED ; SQLSTATE: HY000 Message: IO Error: %s Message: Old log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.com Error number: MY-012889 ; Symbol: ER_IB_MSG_LOG_FILES_CREATE_AND_READ_ONLY_MODE ; SQLSTATE: HY000 Message: Cannot create redo log files in read-only mode (--innodb-read-only). Error number: MY-012891 ; Symbol: ER_IB_MSG_LOG_FILE_PREPARE_ON_CREATE_FAILED ; SQLSTATE: HY000 Message: Failed to create redo log file %s (error: %d) for start LSN %llu Message: InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again. Message: Size of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory. Message: MySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang. Message: Startup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime. Message: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data! Error number: MY-012960 ; Symbol: ER_IB_MSG_DATA_DIRECTORY_NOT_INITIALIZED_OR_CORRUPTED ; SQLSTATE: HY000 Message: Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files. Message: Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s) Message: The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup! Message: Cannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database. Message: Cannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database. Error number: MY-012991 ; Symbol: ER_IB_MSG_UNDO_TRUNCATE_FAIL_TO_READ_LOG_FILE ; SQLSTATE: HY000 Message: Unable to read the existing undo truncate log file '%s'. The error is %s Error number: MY-012996 ; Symbol: ER_IB_MSG_UNDO_TRUNCATE_DELAY_BY_LOG_CREATE ; SQLSTATE: HY000 Message: Cannot create truncate log for undo tablespace '%s'. Error number: MY-012998 ; Symbol: ER_IB_MSG_UNDO_TRUNCATE_DELAY_BY_FAILURE ; SQLSTATE: HY000 Message: Failed to truncate undo tablespace '%s'. Error number: MY-013009 ; Symbol: ER_IB_ERR_ACCESSING_OUT_OF_BOUND_FIELD_IN_INDEX ; SQLSTATE: HY000 Message: Trying to access update undo rec field %llu in index %s of table %s but index has only %llu fields. %s. Run also CHECK TABLE %s. n_fields = %llu, i = %llu, ptr = %p. Error number: MY-013015 ; Symbol: ER_IB_MSG_TRX_RECOVERY_ROLLBACK_COMPLETED ; SQLSTATE: HY000 Message: Rollback of non-prepared transactions completed Message: Resizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET. Error number: MY-013061 ; Symbol: ER_IB_MSG_LOG_WRITER_ABORTS_LOG_ARCHIVER ; SQLSTATE: HY000 Message: Log writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity. Error number: MY-013062 ; Symbol: ER_IB_MSG_LOG_WRITER_WAITING_FOR_ARCHIVER ; SQLSTATE: HY000 Message: Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity. Error number: MY-013067 ; Symbol: ER_IB_MSG_LOG_FILES_CANNOT_ENCRYPT_IN_READ_ONLY ; SQLSTATE: HY000 Message: Can't set redo log files to be encrypted in read-only mode. Error number: MY-013068 ; Symbol: ER_IB_MSG_LOG_FILES_ENCRYPTION_INIT_FAILED ; SQLSTATE: HY000 Message: Can't set redo log files to be encrypted. Message: MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery! Error number: MY-013089 ; Symbol: ER_IB_MSG_LOG_FILE_HEADER_INVALID_CHECKSUM ; SQLSTATE: HY000 Message: Invalid redo log header checksum. Error number: MY-013092 ; Symbol: ER_IB_MSG_LOG_PARAMS_CONCURRENCY_MARGIN_UNSAFE ; SQLSTATE: HY000 Message: Cannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s Error number: MY-013096 ; Symbol: ER_RPL_REPLICA_SQL_THREAD_STOP_CMD_EXEC_TIMEOUT ; SQLSTATE: HY000 Message: STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete. Error number: MY-013097 ; Symbol: ER_RPL_REPLICA_IO_THREAD_STOP_CMD_EXEC_TIMEOUT ; SQLSTATE: HY000 Message: STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete. Error number: MY-013098 ; Symbol: ER_RPL_GTID_UNSAFE_STMT_ON_NON_TRANS_TABLE ; SQLSTATE: HY000 Message: Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables. Error number: MY-013103 ; Symbol: ER_BINLOG_ROW_VALUE_OPTION_USED_ONLY_FOR_AFTER_IMAGES ; SQLSTATE: HY000 Message: When %s, the option binlog_row_value_options=%s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%. Error number: MY-013107 ; Symbol: ER_GRP_RPL_LOWER_CASE_TABLE_NAMES_DIFF_FROM_GRP ; SQLSTATE: HY000 Message: The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group. Message: The lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'. Message: Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s' Error number: MY-013114 ; Symbol: ER_SERVER_SOURCE_FATAL_ERROR_READING_BINLOG ; SQLSTATE: HY000 Message: Got fatal error %d from source when reading data from binary log: '%s' Message: A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %s Error number: MY-013142 ; Symbol: ER_SERVER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE_V2 ; SQLSTATE: HY000 Message: The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure. Error number: MY-013143 ; Symbol: ER_SERVER_COL_COUNT_DOESNT_MATCH_CORRUPTED_V2 ; SQLSTATE: HY000 Message: Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted. Error number: MY-013148 ; Symbol: ER_CANT_REPLICATE_ANONYMOUS_WITH_AUTO_POSITION ; SQLSTATE: HY000 Message: Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %s, position %lld. Error number: MY-013149 ; Symbol: ER_CANT_REPLICATE_ANONYMOUS_WITH_GTID_MODE_ON ; SQLSTATE: HY000 Message: Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %s, position %lld. Error number: MY-013150 ; Symbol: ER_CANT_REPLICATE_GTID_WITH_GTID_MODE_OFF ; SQLSTATE: HY000 Message: Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %s, position %lld. Error number: MY-013153 ; Symbol: ER_AUDIT_LOG_JSON_FILTERING_NOT_ENABLED ; SQLSTATE: HY000 Message: Audit Log filtering has not been installed. Error number: MY-013156 ; Symbol: ER_AUDIT_LOG_JSON_FILTER_NAME_CANNOT_BE_EMPTY ; SQLSTATE: HY000 Message: Filter name cannot be empty. Error number: MY-013157 ; Symbol: ER_AUDIT_LOG_USER_NAME_INVALID_CHARACTER ; SQLSTATE: HY000 Message: Invalid character in the user name. Error number: MY-013158 ; Symbol: ER_AUDIT_LOG_UDF_INSUFFICIENT_PRIVILEGE ; SQLSTATE: HY000 Message: Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operation Error number: MY-013159 ; Symbol: ER_AUDIT_LOG_NO_KEYRING_PLUGIN_INSTALLED ; SQLSTATE: HY000 Message: No keyring installed. Error number: MY-013160 ; Symbol: ER_AUDIT_LOG_HOST_NAME_INVALID_CHARACTER ; SQLSTATE: HY000 Message: Invalid character in the host name. Error number: MY-013161 ; Symbol: ER_AUDIT_LOG_ENCRYPTION_PASSWORD_HAS_NOT_BEEN_SET ; SQLSTATE: HY000 Message: Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one. Error number: MY-013163 ; Symbol: ER_AUDIT_LOG_ENCRYPTION_PASSWORD_CANNOT_BE_FETCHED ; SQLSTATE: HY000 Message: Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption. Error number: MY-013164 ; Symbol: ER_COULD_NOT_REINITIALIZE_AUDIT_LOG_FILTERS ; SQLSTATE: HY000 Message: Could not reinitialize audit log filters. Error number: MY-013165 ; Symbol: ER_AUDIT_LOG_JSON_USER_NAME_CANNOT_BE_EMPTY ; SQLSTATE: HY000 Message: User cannot be empty. Error number: MY-013166 ; Symbol: ER_AUDIT_LOG_USER_FIRST_CHARACTER_MUST_BE_ALPHANUMERIC ; SQLSTATE: HY000 Message: First character of the user name must be alphanumeric. Error number: MY-013167 ; Symbol: ER_AUDIT_LOG_JSON_FILTER_DOES_NOT_EXIST ; SQLSTATE: HY000 Message: Specified filter has not been found. Error number: MY-013177 ; Symbol: ER_AUDIT_LOG_TABLE_DEFINITION_NOT_UPDATED ; SQLSTATE: HY000 Message: '%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure. Error number: MY-013185 ; Symbol: ER_UNKNOWN_VARIABLE_IN_PERSISTED_CONFIG_FILE ; SQLSTATE: HY000 Message: Currently unknown variable '%s' was read from the persisted config file. Error number: MY-013202 ; Symbol: ER_CANT_SET_ERROR_SUPPRESSION_LIST_FROM_COMMAND_LINE ; SQLSTATE: HY000 Message: %s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message. Error number: MY-013206 ; Symbol: ER_GRP_RPL_MISSING_GRP_RPL_ACTION_COORDINATOR ; SQLSTATE: HY000 Message: Message received without a proper group coordinator module. Error number: MY-013207 ; Symbol: ER_GRP_RPL_JOIN_WHEN_GROUP_ACTION_RUNNING ; SQLSTATE: HY000 Message: A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'. Error number: MY-013208 ; Symbol: ER_GRP_RPL_JOINER_EXIT_WHEN_GROUP_ACTION_RUNNING ; SQLSTATE: HY000 Message: A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group. Error number: MY-013209 ; Symbol: ER_GRP_RPL_CHANNEL_THREAD_WHEN_GROUP_ACTION_RUNNING ; SQLSTATE: HY000 Message: Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'. Error number: MY-013210 ; Symbol: ER_GRP_RPL_APPOINTED_PRIMARY_NOT_PRESENT ; SQLSTATE: HY000 Message: A primary election was invoked but the requested primary member is not in the group. Request ignored. Error number: MY-013213 ; Symbol: ER_GRP_RPL_CONFIGURATION_ACTION_LOCAL_TERMINATION ; SQLSTATE: HY000 Message: Configuration operation '%s' terminated. %s Error number: MY-013216 ; Symbol: ER_GRP_RPL_CONFIGURATION_ACTION_KILLED_ERROR ; SQLSTATE: HY000 Message: A configuration change was killed in this member. The member will now leave the group as its configuration may have diverged. Error number: MY-013217 ; Symbol: ER_GRP_RPL_PRIMARY_ELECTION_PROCESS_ERROR ; SQLSTATE: HY000 Message: There was an issue on the primary election process: %s The member will now leave the group. Message: Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove it Message: Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the plugin Error number: MY-013228 ; Symbol: ER_COULD_NOT_CREATE_WINDOWS_REGISTRY_KEY ; SQLSTATE: HY000 Message: %s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident. Error number: MY-013229 ; Symbol: ER_SERVER_GTID_UNSAFE_CREATE_DROP_TEMP_TABLE_IN_TRX_IN_SBR ; SQLSTATE: HY000 Message: Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT. Error number: MY-013233 ; Symbol: ER_XPLUGIN_FAILED_TO_SWITCH_SECURITY_CTX ; SQLSTATE: HY000 Message: Unable to switch security context to user: %s Error number: MY-013234 ; Symbol: ER_RPL_GTID_UNSAFE_ALTER_ADD_COL_WITH_DEFAULT_EXPRESSION ; SQLSTATE: HY000 Message: Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT. Error number: MY-013237 ; Symbol: ER_LDAP_AUTH_USER_GROUP_SEARCH_ROOT_BIND ; SQLSTATE: HY000 Message: Group search rebinding via root DN: %s Error number: MY-013240 ; Symbol: ER_SHARED_TABLESPACE_USED_BY_PARTITIONED_TABLE ; SQLSTATE: HY000 Message: Partitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade. Message: %s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous. Error number: MY-013243 ; Symbol: ER_WARN_DEPRECATED_UTF8MB3_CHARSET_OPTION ; SQLSTATE: HY000 Message: %s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead. Error number: MY-013244 ; Symbol: ER_WARN_DEPRECATED_UTF8MB3_COLLATION_OPTION ; SQLSTATE: HY000 Message: %s: '%s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead. Error number: MY-013245 ; Symbol: ER_SSL_MEMORY_INSTRUMENTATION_INIT_FAILED ; SQLSTATE: HY000 Message: The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented. Message: Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platform Error number: MY-013267 ; Symbol: ER_IB_MSG_DEPRECATED_INNODB_UNDO_TABLESPACES ; SQLSTATE: HY000 Message: The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used. InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE. Error number: MY-013277 ; Symbol: ER_INNODB_INVALID_INNODB_UNDO_DIRECTORY_LOCATION ; SQLSTATE: HY000 Message: The innodb_undo_directory is not allowed to be an ancestor of the datadir. Error number: MY-013278 ; Symbol: ER_SERVER_RPL_ENCRYPTION_FAILED_TO_FETCH_KEY ; SQLSTATE: HY000 Message: Failed to fetch key from keyring, please check if keyring is loaded. Error number: MY-013280 ; Symbol: ER_SERVER_RPL_ENCRYPTION_KEYRING_INVALID_KEY ; SQLSTATE: HY000 Message: Fetched an invalid key from keyring. Error number: MY-013282 ; Symbol: ER_SERVER_RPL_ENCRYPTION_FAILED_TO_ROTATE_LOGS ; SQLSTATE: HY000 Message: Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually. Error number: MY-013283 ; Symbol: ER_SERVER_RPL_ENCRYPTION_KEY_EXISTS_UNEXPECTED ; SQLSTATE: HY000 Message: Key %s exists unexpected. Error number: MY-013284 ; Symbol: ER_SERVER_RPL_ENCRYPTION_FAILED_TO_GENERATE_KEY ; SQLSTATE: HY000 Message: Failed to generate key, please check if keyring is loaded. Error number: MY-013285 ; Symbol: ER_SERVER_RPL_ENCRYPTION_FAILED_TO_STORE_KEY ; SQLSTATE: HY000 Message: Failed to store key, please check if keyring is loaded. Error number: MY-013286 ; Symbol: ER_SERVER_RPL_ENCRYPTION_FAILED_TO_REMOVE_KEY ; SQLSTATE: HY000 Message: Failed to remove key, please check if keyring is loaded. Error number: MY-013287 ; Symbol: ER_SERVER_RPL_ENCRYPTION_MASTER_KEY_RECOVERY_FAILED ; SQLSTATE: HY000 Message: Unable to recover binlog encryption master key, please check if keyring is loaded. Error number: MY-013288 ; Symbol: ER_SERVER_RPL_ENCRYPTION_UNABLE_TO_INITIALIZE ; SQLSTATE: HY000 Message: Failed to initialize binlog encryption, please check if keyring is loaded. Error number: MY-013289 ; Symbol: ER_SERVER_RPL_ENCRYPTION_UNABLE_TO_ROTATE_MASTER_KEY_AT_STARTUP ; SQLSTATE: HY000 Message: Failed to rotate binlog encryption master key at startup, please check if keyring is loaded. Error number: MY-013290 ; Symbol: ER_SERVER_RPL_ENCRYPTION_IGNORE_ROTATE_MASTER_KEY_AT_STARTUP ; SQLSTATE: HY000 Message: Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled. Error number: MY-013294 ; Symbol: ER_WARNING_RETAIN_CURRENT_PASSWORD_CLAUSE_VOID ; SQLSTATE: HY000 Message: RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords. Error number: MY-013295 ; Symbol: ER_WARNING_DISCARD_OLD_PASSWORD_CLAUSE_VOID ; SQLSTATE: HY000 Message: DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords. Error number: MY-013299 ; Symbol: ER_WARNING_AUTHCACHE_INVALID_USER_ATTRIBUTES ; SQLSTATE: HY000 Message: Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user. Error number: MY-013300 ; Symbol: ER_MYSQL_NATIVE_PASSWORD_SECOND_PASSWORD_USED_INFORMATION ; SQLSTATE: HY000 Message: Second password was used for login by user: '%s'@'%s'. Error number: MY-013301 ; Symbol: ER_SHA256_PASSWORD_SECOND_PASSWORD_USED_INFORMATION ; SQLSTATE: HY000 Message: Second password was used for login by user: '%s'@'%s'. Error number: MY-013302 ; Symbol: ER_CACHING_SHA2_PASSWORD_SECOND_PASSWORD_USED_INFORMATION ; SQLSTATE: HY000 Message: Second password was used for login by user: '%s'@'%s'. Error number: MY-013303 ; Symbol: ER_GRP_RPL_SEND_TRX_PREPARED_MESSAGE_FAILED ; SQLSTATE: HY000 Message: Error sending transaction '%s:%lld' prepared message from session '%u'. Error number: MY-013304 ; Symbol: ER_GRP_RPL_RELEASE_COMMIT_AFTER_GROUP_PREPARE_FAILED ; SQLSTATE: HY000 Message: Error releasing transaction '%s:%lld' for commit on session '%u' after being prepared on all group members. Error number: MY-013305 ; Symbol: ER_GRP_RPL_TRX_ALREADY_EXISTS_ON_TCM_ON_AFTER_CERTIFICATION ; SQLSTATE: HY000 Message: Transaction '%s:%lld' already exists on Group Replication consistency manager while being registered after conflict detection. Error number: MY-013306 ; Symbol: ER_GRP_RPL_FAILED_TO_INSERT_TRX_ON_TCM_ON_AFTER_CERTIFICATION ; SQLSTATE: HY000 Message: Error registering transaction '%s:%lld' on Group Replication consistency manager after conflict detection. Error number: MY-013307 ; Symbol: ER_GRP_RPL_REGISTER_TRX_TO_WAIT_FOR_GROUP_PREPARE_FAILED ; SQLSTATE: HY000 Message: Error registering transaction '%s:%lld' from session '%u' to wait for being prepared on all group members. Error number: MY-013308 ; Symbol: ER_GRP_RPL_TRX_WAIT_FOR_GROUP_PREPARE_FAILED ; SQLSTATE: HY000 Message: Error on transaction '%s:%lld' from session '%u' while waiting for being prepared on all group members. Error number: MY-013309 ; Symbol: ER_GRP_RPL_TRX_DOES_NOT_EXIST_ON_TCM_ON_HANDLE_REMOTE_PREPARE ; SQLSTATE: HY000 Message: Transaction '%s:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare. Error number: MY-013310 ; Symbol: ER_GRP_RPL_RELEASE_BEGIN_TRX_AFTER_DEPENDENCIES_COMMIT_FAILED ; SQLSTATE: HY000 Message: Error releasing transaction '%s:%lld' for execution on session '%u' after its dependencies did complete commit. Error number: MY-013311 ; Symbol: ER_GRP_RPL_REGISTER_TRX_TO_WAIT_FOR_DEPENDENCIES_FAILED ; SQLSTATE: HY000 Message: Error registering transaction from session '%u' to wait for its dependencies to complete commit. Error number: MY-013312 ; Symbol: ER_GRP_RPL_WAIT_FOR_DEPENDENCIES_FAILED ; SQLSTATE: HY000 Message: Error on session '%u' while waiting for its dependencies to complete commit. Error number: MY-013313 ; Symbol: ER_GRP_RPL_REGISTER_TRX_TO_WAIT_FOR_SYNC_BEFORE_EXECUTION_FAILED ; SQLSTATE: HY000 Message: Error registering transaction from session '%u' to wait for sync before execution. Error number: MY-013314 ; Symbol: ER_GRP_RPL_SEND_TRX_SYNC_BEFORE_EXECUTION_FAILED ; SQLSTATE: HY000 Message: Error sending sync before execution message from session '%u'. Error number: MY-013315 ; Symbol: ER_GRP_RPL_TRX_WAIT_FOR_SYNC_BEFORE_EXECUTION_FAILED ; SQLSTATE: HY000 Message: Error on transaction from session '%u' while waiting for sync before execution. Error number: MY-013316 ; Symbol: ER_GRP_RPL_RELEASE_BEGIN_TRX_AFTER_WAIT_FOR_SYNC_BEFORE_EXEC ; SQLSTATE: HY000 Message: Error releasing transaction for execution on session '%u' after wait for sync before execution. Error number: MY-013317 ; Symbol: ER_GRP_RPL_TRX_WAIT_FOR_GROUP_GTID_EXECUTED ; SQLSTATE: HY000 Message: Error waiting for group executed transactions commit on session '%u'. Error number: MY-013322 ; Symbol: ER_GRP_RPL_GTID_SET_EXTRACT_ERROR_DURING_RECOVERY ; SQLSTATE: HY000 Message: Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery. Error number: MY-013323 ; Symbol: ER_SERVER_RPL_ENCRYPTION_FAILED_TO_ENCRYPT ; SQLSTATE: HY000 Message: Failed to encrypt content to write into binlog file: %s. Error number: MY-013324 ; Symbol: ER_CANNOT_GET_SERVER_VERSION_FROM_TABLESPACE_HEADER ; SQLSTATE: HY000 Message: Cannot get the server version number from the dictionary tablespace header. Error number: MY-013325 ; Symbol: ER_CANNOT_SET_SERVER_VERSION_IN_TABLESPACE_HEADER ; SQLSTATE: HY000 Message: Cannot set the server version number in the dictionary tablespace header. Error number: MY-013326 ; Symbol: ER_SERVER_UPGRADE_VERSION_NOT_SUPPORTED ; SQLSTATE: HY000 Message: Upgrading the server from server version '%u' is not supported. Error number: MY-013332 ; Symbol: ER_LDAP_AUTH_GRP_SEARCH_NOT_SPECIAL_HDL ; SQLSTATE: HY000 Message: Special handling for group search, {GA} not found Error number: MY-013333 ; Symbol: ER_LDAP_AUTH_GRP_USER_OBJECT_HAS_GROUP_INFO ; SQLSTATE: HY000 Message: User group retrieval: User object has group information Error number: MY-013334 ; Symbol: ER_LDAP_AUTH_GRP_INFO_FOUND_IN_MANY_OBJECTS ; SQLSTATE: HY000 Message: Group information found in multiple user objects. Search filter configuration is incorrect. Message: Get user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user. Error number: MY-013347 ; Symbol: ER_LDAP_MAPPING_PROCESS_DELIMITER_EQUAL_NOT_FOUND ; SQLSTATE: HY000 Message: Processing delimiter, separator = not found, resetting position Error number: MY-013348 ; Symbol: ER_LDAP_MAPPING_PROCESS_DELIMITER_TRY_COMMA ; SQLSTATE: HY000 Message: Processing delimiter, failed to get data for = separator try for separator ,. Error number: MY-013349 ; Symbol: ER_LDAP_MAPPING_PROCESS_DELIMITER_COMMA_NOT_FOUND ; SQLSTATE: HY000 Message: Processing delimiter, separator , not found, resetting position Error number: MY-013350 ; Symbol: ER_LDAP_MAPPING_NO_SEPEARATOR_END_OF_GROUP ; SQLSTATE: HY000 Message: Processing delimiter: No mapping separator is found, end of group information Error number: MY-013358 ; Symbol: ER_INVALID_NAMED_PIPE_FULL_ACCESS_GROUP ; SQLSTATE: HY000 Message: Invalid value for named_pipe_full_access_group. Error number: MY-013361 ; Symbol: ER_AUTH_ID_WITH_SYSTEM_USER_PRIV_IN_MANDATORY_ROLES ; SQLSTATE: HY000 Message: Cannot set mandatory_roles: AuthId `%s`@`%s` has '%s' privilege. Error number: MY-013362 ; Symbol: ER_SERVER_BINLOG_MASTER_KEY_RECOVERY_OUT_OF_COMBINATION ; SQLSTATE: HY000 Message: Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong. Error number: MY-013363 ; Symbol: ER_SERVER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_CLEANUP_AUX_KEY ; SQLSTATE: HY000 Message: Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution. Message: For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted. Error number: MY-013370 ; Symbol: ER_WARN_INCORRECT_PRIVILEGE_FOR_DB_RESTRICTIONS ; SQLSTATE: HY000 Message: For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges. Message: For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted. Error number: MY-013372 ; Symbol: ER_GRP_RPL_INVALID_COMMUNICATION_PROTOCOL ; SQLSTATE: HY000 Message: '%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's version Error number: MY-013374 ; Symbol: ER_GRP_RPL_TIMEOUT_RECEIVED_VC_ON_REJOIN ; SQLSTATE: HY000 Message: Timeout while waiting for a view change event during the auto-rejoin procedure Error number: MY-013376 ; Symbol: ER_GRP_RPL_DEFAULT_TABLE_ENCRYPTION_DIFF_FROM_GRP ; SQLSTATE: HY000 Message: The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group. Message: A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed. Error number: MY-013392 ; Symbol: ER_SERVER_UPGRADE_SYS_SCHEMA_UP_TO_DATE ; SQLSTATE: HY000 Message: The sys schema is already up to date (version %s). Error number: MY-013393 ; Symbol: ER_SERVER_UPGRADE_SYS_SCHEMA_OBJECT_COUNT ; SQLSTATE: HY000 Message: Found %d sys %s, but expected %d. Re-installing the sys schema. Error number: MY-013399 ; Symbol: ER_SERVER_BINLOG_UNSAFE_SYSTEM_FUNCTION ; SQLSTATE: HY000 Message: '%s' statement is unsafe because it uses a system function that may return a different value on the replica. Error number: MY-013404 ; Symbol: ER_BINLOG_UNABLE_TO_ROTATE_GTID_TABLE_READONLY ; SQLSTATE: HY000 Message: Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %s Error number: MY-013407 ; Symbol: ER_NETWORK_NAMESPACE_NOT_ALLOWED_FOR_WILDCARD_ADDRESS ; SQLSTATE: HY000 Message: Network namespace not allowed for wildcard interface address Error number: MY-013409 ; Symbol: ER_WILDCARD_NOT_ALLOWED_FOR_MULTIADDRESS_BIND ; SQLSTATE: HY000 Message: Wildcard address value not allowed for multivalued bind address Error number: MY-013410 ; Symbol: ER_NETWORK_NAMESPACE_FILE_PATH_TOO_LONG ; SQLSTATE: HY000 Message: The path to a special network namespace file is too long. (got %u > max %u) Error number: MY-013425 ; Symbol: ER_BINLOG_UNSAFE_DEFAULT_EXPRESSION_IN_SUBSTATEMENT ; SQLSTATE: HY000 Message: The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica. Error number: MY-013428 ; Symbol: ER_AUDIT_LOG_KEYRING_ID_TIMESTAMP_VALUE_IS_INVALID ; SQLSTATE: HY000 Message: Keyring ID timestamp value is invalid: '%s' Error number: MY-013429 ; Symbol: ER_AUDIT_LOG_FILE_NAME_TIMESTAMP_VALUE_IS_MISSING_OR_INVALID ; SQLSTATE: HY000 Message: Cannot process audit log file. File name timestamp value is missing or invalid: '%s' Error number: MY-013430 ; Symbol: ER_AUDIT_LOG_FILE_NAME_DOES_NOT_HAVE_REQUIRED_FORMAT ; SQLSTATE: HY000 Message: Cannot process audit log file. File name does not have required format: '%s' Error number: MY-013431 ; Symbol: ER_AUDIT_LOG_FILE_NAME_KEYRING_ID_VALUE_IS_MISSING ; SQLSTATE: HY000 Message: Cannot process audit log file. File name keyring ID value is missing: '%s' Error number: MY-013432 ; Symbol: ER_AUDIT_LOG_FILE_HAS_BEEN_SUCCESSFULLY_PROCESSED ; SQLSTATE: HY000 Message: Audit log file has been successfully processed: '%s' Error number: MY-013433 ; Symbol: ER_AUDIT_LOG_COULD_NOT_OPEN_FILE_FOR_READING ; SQLSTATE: HY000 Message: Could not open audit log file for reading: '%s' Message: The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made. Message: No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page. Message: No valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs. Error number: MY-013469 ; Symbol: ER_GRP_RPL_RECOVERY_STRAT_CLONE_THRESHOLD ; SQLSTATE: HY000 Message: This member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu. Message: This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs. Message: Due to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group. Error number: MY-013474 ; Symbol: ER_GRP_RPL_REPLICA_THREAD_ERROR_ON_CLONE ; SQLSTATE: HY000 Message: The '%s' thread of channel '%s' will error out as the server will attempt to clone another server Error number: MY-013476 ; Symbol: ER_IDENT_CAUSES_TOO_LONG_PATH_IN_UPGRADE ; SQLSTATE: HY000 Message: Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'. Error number: MY-013480 ; Symbol: ER_AUDIT_LOG_UDF_INVALID_ARGUMENT_COUNT ; SQLSTATE: HY000 Message: Invalid argument count Error number: MY-013482 ; Symbol: ER_AUDIT_LOG_UDF_READ_INVALID_MAX_ARRAY_LENGTH_ARG_TYPE ; SQLSTATE: HY000 Message: Invalid "max_array_length" argument type. Error number: MY-013486 ; Symbol: ER_GRP_RPL_SERVER_SET_TO_OFFLINE_MODE_DUE_TO_ERRORS ; SQLSTATE: HY000 Message: The server was automatically set into offline mode after an error was detected. Message: A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem. Error number: MY-013488 ; Symbol: ER_WARN_WRONG_COMPRESSION_ALGORITHM_LOG ; SQLSTATE: HY000 Message: Invalid SOURCE_COMPRESSION_ALGORITHMS '%s' found in repository for channel '%s'. Resetting to 'uncompressed' (no compression). Error number: MY-013494 ; Symbol: ER_WARN_LOG_PRIVILEGE_CHECKS_USER_DOES_NOT_EXIST ; SQLSTATE: HY000 Message: PRIVILEGE_CHECKS_USER for replication channel '%s' was set to `%s`@`%s`, but this is not an existing user. Correct this before starting replication threads. Error number: MY-013495 ; Symbol: ER_WARN_LOG_PRIVILEGE_CHECKS_USER_CORRUPT ; SQLSTATE: HY000 Message: Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration. Error number: MY-013496 ; Symbol: ER_WARN_LOG_PRIVILEGE_CHECKS_USER_NEEDS_RPL_APPLIER_PRIV ; SQLSTATE: HY000 Message: PRIVILEGE_CHECKS_USER for replication channel '%s' was set to `%s`@`%s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads. Error number: MY-013497 ; Symbol: ER_OBSOLETE_FILE_PRIVILEGE_FOR_REPLICATION_CHECKS ; SQLSTATE: HY000 Message: The PRIVILEGE_CHECKS_USER for channel '%s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER. Error number: MY-013498 ; Symbol: ER_RPL_REPLICA_SQL_THREAD_STARTING_WITH_PRIVILEGE_CHECKS ; SQLSTATE: HY000 Message: Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%s'@'%s', roles: %s Error number: MY-013500 ; Symbol: ER_INIT_FAILED_TO_GENERATE_ROOT_PASSWORD ; SQLSTATE: HY000 Message: Failed to generate a random password for root. Probabably not enough enthropy. Error number: MY-013502 ; Symbol: ER_WARN_AUTH_ID_WITH_SYSTEM_USER_PRIV_IN_MANDATORY_ROLES ; SQLSTATE: HY000 Message: Cannot set mandatory_roles: AuthId `%s`@`%s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored. Error number: MY-013504 ; Symbol: ER_WARN_RPL_RECOVERY_NO_ROTATE_EVENT_FROM_SOURCE_EOF ; SQLSTATE: HY000 Message: Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel. Error number: MY-013506 ; Symbol: ER_CANT_PROCESS_EXPRESSION_FOR_GENERATED_COLUMN_TO_DD ; SQLSTATE: HY000 Message: Error in processing (possibly deprecated) expression or function '%s' for generated column %s.%s.%s Error number: MY-013507 ; Symbol: ER_RPL_REPLICA_QUEUE_EVENT_FAILED_INVALID_NON_ROW_FORMAT ; SQLSTATE: HY000 Message: The queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found. Error number: MY-013508 ; Symbol: ER_OBSOLETE_REQUIRE_ROW_FORMAT_VIOLATION ; SQLSTATE: HY000 Message: The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found. Error number: MY-013509 ; Symbol: ER_LOG_PRIV_CHECKS_REQUIRE_ROW_FORMAT_NOT_SET ; SQLSTATE: HY000 Message: PRIVILEGE_CHECKS_USER for replication channel '%s' can't be set to `%s`@`%s` unless REQUIRE_ROW_FORMAT is also set to %d. Error number: MY-013510 ; Symbol: ER_RPL_REPLICA_SQL_THREAD_DETECTED_UNEXPECTED_EVENT_SEQUENCE ; SQLSTATE: HY000 Message: An unexpected event sequence was detected by the SQL thread while applying an event. Error number: MY-013513 ; Symbol: ER_IB_MSG_UPGRADE_PARTITION_FILE_IMPORT ; SQLSTATE: HY000 Message: Updating partition file name '%s' to '%s' for import Message: Unable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths Error number: MY-013520 ; Symbol: ER_SCHEMA_NAME_IN_UPPER_CASE_NOT_ALLOWED ; SQLSTATE: HY000 Message: Schema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1. Error number: MY-013521 ; Symbol: ER_TABLE_NAME_IN_UPPER_CASE_NOT_ALLOWED ; SQLSTATE: HY000 Message: Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1. Error number: MY-013522 ; Symbol: ER_SCHEMA_NAME_IN_UPPER_CASE_NOT_ALLOWED_FOR_FK ; SQLSTATE: HY000 Message: Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1. Error number: MY-013523 ; Symbol: ER_TABLE_NAME_IN_UPPER_CASE_NOT_ALLOWED_FOR_FK ; SQLSTATE: HY000 Message: Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1. Error number: MY-013525 ; Symbol: ER_ACCESS_DENIED_FOR_USER_ACCOUNT_BLOCKED_BY_PASSWORD_LOCK ; SQLSTATE: HY000 Message: Access denied for user '%s'@'%s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset. Error number: MY-013529 ; Symbol: ER_RPL_RELAY_LOG_RECOVERY_INFO_AFTER_CLONE ; SQLSTATE: HY000 Message: Applier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO' Message: The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6 Error number: MY-013564 ; Symbol: ER_IB_MSG_DBLWR_OPEN_OR_CREATE_WRONG_SIZE ; SQLSTATE: HY000 Message: Doublewrite open or create file %s size %llu is not a multiple of the configured page size %zu Error number: MY-013580 ; Symbol: ER_IB_ERR_PAGE_ARCH_INVALID_DOUBLE_WRITE_BUF ; SQLSTATE: HY000 Message: Page archiver's doublewrite buffer for %ld is not valid. Error number: MY-013583 ; Symbol: ER_INVALID_XPLUGIN_SOCKET_SAME_AS_SERVER ; SQLSTATE: HY000 Message: X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket Error number: MY-013588 ; Symbol: ER_IB_MSG_INVALID_LOCATION_FOR_TABLESPACE ; SQLSTATE: HY000 Message: Cannot create tablespace %s because the directory is not a valid location. %s Message: Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used. Message: Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port). Message: The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints. Error number: MY-013593 ; Symbol: ER_GRP_RPL_RECOVERY_ENDPOINT_INVALID_DONOR_ENDPOINT ; SQLSTATE: HY000 Message: Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped. Error number: MY-013594 ; Symbol: ER_GRP_RPL_RECOVERY_ENDPOINT_INTERFACES_IPS ; SQLSTATE: HY000 Message: Failed to retrieve IP addresses from enabled host network interfaces. Error number: MY-013595 ; Symbol: ER_WARN_TLS_CHANNEL_INITIALIZATION_ERROR ; SQLSTATE: HY000 Message: Failed to initialize TLS for channel: %s. See below for the description of exact issue. Error number: MY-013597 ; Symbol: ER_XPLUGIN_FAILED_TO_BIND_INTERFACE_ADDRESS ; SQLSTATE: HY000 Message: Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value. Message: Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6 Message: InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency. Error number: MY-013604 ; Symbol: ER_IB_TABLESPACE_PATH_VALIDATION_SKIPPED ; SQLSTATE: HY000 Message: Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected! Error number: MY-013605 ; Symbol: ER_IB_CANNOT_UPGRADE_WITH_DISCARDED_TABLESPACES ; SQLSTATE: HY000 Message: Upgrade failed because database contains discarded tablespaces. Error number: MY-013608 ; Symbol: ER_IB_MSG_TRX_RECOVERY_ROLLBACK_NOT_COMPLETED ; SQLSTATE: HY000 Message: Rollback of non-prepared transactions not completed, due to fast shutdown Error number: MY-013609 ; Symbol: ER_AUTHCACHE_ROLE_EDGES_IGNORED_EMPTY_NAME ; SQLSTATE: HY000 Message: Found an entry in the 'role_edges' table with empty authorization ID; Skipped Error number: MY-013610 ; Symbol: ER_AUTHCACHE_ROLE_EDGES_UNKNOWN_AUTHORIZATION_ID ; SQLSTATE: HY000 Message: Found an entry in the 'role_edges' table with unknown authorization ID '%s'; Skipped Error number: MY-013611 ; Symbol: ER_AUTHCACHE_DEFAULT_ROLES_IGNORED_EMPTY_NAME ; SQLSTATE: HY000 Message: Found an entry in the 'default_roles' table with empty authorization ID; Skipped Error number: MY-013612 ; Symbol: ER_AUTHCACHE_DEFAULT_ROLES_UNKNOWN_AUTHORIZATION_ID ; SQLSTATE: HY000 Message: Found an entry in the 'default_roles' table with unknown authorization ID '%s'; Skipped Error number: MY-013614 ; Symbol: ER_IB_LOCK_VALIDATE_LATCH_ORDER_VIOLATION ; SQLSTATE: HY000 Message: %s Error number: MY-013625 ; Symbol: ER_IB_UNABLE_TO_EXPAND_TEMPORARY_TABLESPACE_POOL ; SQLSTATE: HY000 Message: %s Error number: MY-013626 ; Symbol: ER_IB_TMP_TABLESPACE_CANNOT_CREATE_DIRECTORY ; SQLSTATE: HY000 Message: %s Error number: MY-013628 ; Symbol: ER_IB_ERR_TEMP_TABLESPACE_DIR_DOESNT_EXIST ; SQLSTATE: HY000 Message: %s Error number: MY-013630 ; Symbol: ER_IB_ERR_TEMP_TABLESPACE_DIR_CONTAINS_SEMICOLON ; SQLSTATE: HY000 Message: %s Error number: MY-013631 ; Symbol: ER_IB_ERR_TEMP_TABLESPACE_DIR_SUBDIR_OF_DATADIR ; SQLSTATE: HY000 Message: %s Error number: MY-013635 ; Symbol: ER_IB_ERR_NOT_ENOUGH_MEMORY_FOR_PARSE_BUFFER ; SQLSTATE: HY000 Message: %s Error number: MY-013659 ; Symbol: ER_GRP_RPL_TIMEOUT_RECEIVED_VC_LEAVE_ON_REJOIN ; SQLSTATE: HY000 Message: Timeout while waiting for a view change event during the leave step before a auto-rejoin attempt. Message: A tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it. Message: None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log. Message: The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source. Message: The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table. Message: The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table. Error number: MY-013682 ; Symbol: ER_RPL_ASYNC_CHANNEL_STOPPED_QUORUM_LOST ; SQLSTATE: HY000 Message: The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source. Error number: MY-013683 ; Symbol: ER_RPL_ASYNC_CHANNEL_CANT_CONNECT_NO_QUORUM ; SQLSTATE: HY000 Message: The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source. Error number: MY-013685 ; Symbol: ER_RPL_REPLICA_MONITOR_IO_THREAD_EXITING ; SQLSTATE: HY000 Message: Replica Monitor IO thread exiting. Message: The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table. Message: The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table. Error number: MY-013689 ; Symbol: ER_RPL_REPLICA_MONITOR_IO_THREAD_RECONNECT_CHANNEL ; SQLSTATE: HY000 Message: Error %s the channel '%s', the operation will be automatically retried. Error number: MY-013690 ; Symbol: ER_REPLICA_ANON_TO_GTID_IS_LOCAL_OR_UUID_AND_GTID_MODE_NOT_ON ; SQLSTATE: HY000 Message: Replication channel '%s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'. Error number: MY-013691 ; Symbol: ER_REPLICA_ANONYMOUS_TO_GTID_UUID_SAME_AS_GROUP_NAME ; SQLSTATE: HY000 Message: Replication channel '%s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS. Error number: MY-013692 ; Symbol: ER_GRP_RPL_GRP_NAME_IS_SAME_AS_ANONYMOUS_TO_GTID_UUID ; SQLSTATE: HY000 Message: The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channel Message: The integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action. Message: %s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB Message: %s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB Message: %s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB Error number: MY-013701 ; Symbol: ER_GRP_RPL_APPLIER_CHANNEL_STILL_RUNNING ; SQLSTATE: HY000 Message: The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools. Error number: MY-013702 ; Symbol: ER_RPL_ASYNC_RECONNECT_GTID_MODE_OFF_CHANNEL ; SQLSTATE: HY000 Message: Detected misconfiguration: replication channel \'%s\' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL \'%s\', or change GTID_MODE to value ON, before starting the replica receiver thread. Error number: MY-013709 ; Symbol: ER_COMPONENTS_INFRASTRUCTURE_MANIFEST_INIT ; SQLSTATE: HY000 Message: Received an error while processing components from manifest file: %s Error number: MY-013710 ; Symbol: ER_COMPONENTS_INFRASTRUCTURE_MANIFEST_DEINIT ; SQLSTATE: HY000 Message: Received an error while unloading components read from manifest file: %s Error number: MY-013711 ; Symbol: ER_WARN_COMPONENTS_INFRASTRUCTURE_MANIFEST_NOT_RO ; SQLSTATE: HY000 Message: Manifest file '%s' is not read-only. For better security, please make sure that the file is read-only. Error number: MY-013712 ; Symbol: ER_WARN_NO_KEYRING_COMPONENT_SERVICE_FOUND ; SQLSTATE: HY000 Message: No suitable '%s' service implementation found to fulfill the request. Message: The component is not initialized properly. Error: %s. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component. Error number: MY-013716 ; Symbol: ER_KEYRING_COMPONENT_MEMORY_ALLOCATION_ERROR ; SQLSTATE: HY000 Message: Failed to allocated memory for '%s' while executing: '%s' API of service: '%s' Error number: MY-013717 ; Symbol: ER_NOTE_KEYRING_COMPONENT_AES_INVALID_MODE_BLOCK_SIZE ; SQLSTATE: HY000 Message: Empty or 0 values for AES encryption mode and/or block size are not permitted. Error number: MY-013718 ; Symbol: ER_NOTE_KEYRING_COMPONENT_AES_DATA_IDENTIFIER_EMPTY ; SQLSTATE: HY000 Message: A valid data identifier is required in order to fetch the key required for the AES operation. Error number: MY-013719 ; Symbol: ER_NOTE_KEYRING_COMPONENT_AES_INVALID_KEY ; SQLSTATE: HY000 Message: Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES. Error number: MY-013720 ; Symbol: ER_NOTE_KEYRING_COMPONENT_AES_OPERATION_ERROR ; SQLSTATE: HY000 Message: Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'. Error number: MY-013721 ; Symbol: ER_NOTE_KEYRING_COMPONENT_READ_DATA_NOT_FOUND ; SQLSTATE: HY000 Message: Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'. Error number: MY-013722 ; Symbol: ER_NOTE_KEYRING_COMPONENT_WRITE_MAXIMUM_DATA_LENGTH ; SQLSTATE: HY000 Message: Maximum permissible size of data is '%zu' bits Message: Error writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error. Error number: MY-013724 ; Symbol: ER_NOTE_KEYRING_COMPONENT_REMOVE_FAILED ; SQLSTATE: HY000 Message: Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error. Error number: MY-013725 ; Symbol: ER_NOTE_KEYRING_COMPONENT_GENERATE_FAILED ; SQLSTATE: HY000 Message: Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error. Error number: MY-013726 ; Symbol: ER_NOTE_KEYRING_COMPONENT_KEYS_METADATA_ITERATOR_FETCH_FAILED ; SQLSTATE: HY000 Message: Failed to get metadata from current keys metadata iterator position. Error number: MY-013727 ; Symbol: ER_NOTE_KEYRING_COMPONENT_METADATA_ITERATOR_INVALID_OUT_PARAM ; SQLSTATE: HY000 Message: Key and value length parameters must not be null. Message: Column %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade. Error number: MY-013732 ; Symbol: ER_GRP_RPL_MEMBER_ACTION_FAILURE_IGNORE ; SQLSTATE: HY000 Message: The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure. Message: The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure. Error number: MY-013734 ; Symbol: ER_GRP_RPL_MEMBER_ACTION_PARSE_ON_RECEIVE ; SQLSTATE: HY000 Message: Unable to parse the member actions configuration sent by the primary. Error number: MY-013735 ; Symbol: ER_GRP_RPL_MEMBER_ACTION_UPDATE_ACTIONS ; SQLSTATE: HY000 Message: Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'. Error number: MY-013736 ; Symbol: ER_GRP_RPL_MEMBER_ACTION_GET_EXCHANGEABLE_DATA ; SQLSTATE: HY000 Message: Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'. Error number: MY-013737 ; Symbol: ER_GRP_RPL_MEMBER_ACTION_DEFAULT_CONFIGURATION ; SQLSTATE: HY000 Message: This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one. Error number: MY-013738 ; Symbol: ER_GRP_RPL_MEMBER_ACTION_UNABLE_TO_SET_DEFAULT_CONFIGURATION ; SQLSTATE: HY000 Message: Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'. Error number: MY-013739 ; Symbol: ER_GRP_RPL_MEMBER_ACTION_PARSE_ON_MEMBER_JOIN ; SQLSTATE: HY000 Message: Unable to parse the member actions configuration sent by the group on member join. Error number: MY-013740 ; Symbol: ER_GRP_RPL_MEMBER_ACTION_UPDATE_ACTIONS_ON_MEMBER_JOIN ; SQLSTATE: HY000 Message: Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'. Error number: MY-013741 ; Symbol: ER_GRP_RPL_MEMBER_ACTION_INVALID_ACTIONS_ON_MEMBER_JOIN ; SQLSTATE: HY000 Message: The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members. Message: Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID. Error number: MY-013749 ; Symbol: ER_GRP_RPL_VIEW_CHANGE_UUID_SAME_AS_GROUP_NAME ; SQLSTATE: HY000 Message: Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC. Error number: MY-013750 ; Symbol: ER_GRP_RPL_GROUP_NAME_SAME_AS_VIEW_CHANGE_UUID ; SQLSTATE: HY000 Message: group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATIC Error number: MY-013751 ; Symbol: ER_GRP_RPL_VIEW_CHANGE_UUID_IS_SAME_AS_ANONYMOUS_TO_GTID_UUID ; SQLSTATE: HY000 Message: The group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channel Error number: MY-013752 ; Symbol: ER_GRP_RPL_GRP_VIEW_CHANGE_UUID_IS_INCOMPATIBLE_WITH_SERVER_UUID ; SQLSTATE: HY000 Message: group_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid Error number: MY-013753 ; Symbol: ER_GRP_RPL_VIEW_CHANGE_UUID_DIFF_FROM_GRP ; SQLSTATE: HY000 Message: The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group. Error number: MY-013754 ; Symbol: ER_WARN_REPLICA_ANONYMOUS_TO_GTID_UUID_SAME_AS_VIEW_CHANGE_UUID ; SQLSTATE: HY000 Message: Replication channel '%s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS. Error number: MY-013755 ; Symbol: ER_GRP_RPL_FAILED_TO_PARSE_THE_VIEW_CHANGE_UUID ; SQLSTATE: HY000 Message: Unable to parse the group_replication_view_change_uuid. Error number: MY-013756 ; Symbol: ER_GRP_RPL_FAILED_TO_GENERATE_SIDNO_FOR_VIEW_CHANGE_UUID ; SQLSTATE: HY000 Message: Unable to generate sidno for group_replication_view_change_uuid. Error number: MY-013757 ; Symbol: ER_GRP_RPL_VIEW_CHANGE_UUID_PARSE_ERROR ; SQLSTATE: HY000 Message: Unable to parse the group_replication_view_change_uuid during the Certification module initialization. Error number: MY-013758 ; Symbol: ER_GRP_RPL_UPDATE_GRPGTID_VIEW_CHANGE_UUID_EXECUTED_ERROR ; SQLSTATE: HY000 Message: Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization. Error number: MY-013759 ; Symbol: ER_GRP_RPL_ADD_VIEW_CHANGE_UUID_TO_GRP_SID_MAP_ERROR ; SQLSTATE: HY000 Message: Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization. Error number: MY-013760 ; Symbol: ER_GRP_RPL_DONOR_VIEW_CHANGE_UUID_TRANS_INFO_ERROR ; SQLSTATE: HY000 Message: Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error. Error number: MY-013761 ; Symbol: ER_WARN_GRP_RPL_VIEW_CHANGE_UUID_FAIL_GET_VARIABLE ; SQLSTATE: HY000 Message: Unable to retrieve group_replication_view_change_uuid during server checks on replication operations. Error number: MY-013762 ; Symbol: ER_WARN_ADUIT_LOG_MAX_SIZE_AND_PRUNE_SECONDS_LOG ; SQLSTATE: HY000 Message: Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignored Error number: MY-013763 ; Symbol: ER_WARN_ADUIT_LOG_MAX_SIZE_CLOSE_TO_ROTATE_ON_SIZE_LOG ; SQLSTATE: HY000 Message: audit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller. Error number: MY-013767 ; Symbol: ER_DEPRECATED_PERSISTED_VARIABLE_WITH_ALIAS ; SQLSTATE: HY000 Message: The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version. Message: %d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation. Message: Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security. Error number: MY-013770 ; Symbol: ER_IB_MSG_REENCRYPTED_GENERAL_TABLESPACE_KEY ; SQLSTATE: HY000 Message: Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security. Error number: MY-013772 ; Symbol: ER_IB_MSG_RECOVERY_NO_SPACE_IN_REDO_LOG__SKIP_IBUF_MERGES ; SQLSTATE: HY000 Message: There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4. Error number: MY-013773 ; Symbol: ER_IB_MSG_RECOVERY_NO_SPACE_IN_REDO_LOG__UNEXPECTED ; SQLSTATE: HY000 Message: There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6). Error number: MY-013774 ; Symbol: ER_WARN_AUDIT_LOG_FORMAT_UNIX_TIMESTAMP_ONLY_WHEN_JSON_LOG ; SQLSTATE: HY000 Message: audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON. Error number: MY-013780 ; Symbol: ER_GRP_RPL_MYSQL_NETWORK_PROVIDER_CLIENT_ERROR_CONN_ERR ; SQLSTATE: HY000 Message: Failed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections. Error number: MY-013781 ; Symbol: ER_GRP_RPL_MYSQL_NETWORK_PROVIDER_CLIENT_ERROR_COMMAND_ERR ; SQLSTATE: HY000 Message: Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections. Error number: MY-013782 ; Symbol: ER_GRP_RPL_FAILOVER_CONF_GET_EXCHANGEABLE_DATA ; SQLSTATE: HY000 Message: Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'. Error number: MY-013783 ; Symbol: ER_GRP_RPL_FAILOVER_CONF_DEFAULT_CONFIGURATION ; SQLSTATE: HY000 Message: This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one. Error number: MY-013784 ; Symbol: ER_GRP_RPL_FAILOVER_CONF_UNABLE_TO_SET_DEFAULT_CONFIGURATION ; SQLSTATE: HY000 Message: Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'. Error number: MY-013785 ; Symbol: ER_GRP_RPL_FAILOVER_CONF_PARSE_ON_MEMBER_JOIN ; SQLSTATE: HY000 Message: Unable to parse the replication failover channels configuration sent by the group on member join. Error number: MY-013786 ; Symbol: ER_GRP_RPL_FAILOVER_CONF_CHANNEL_DOES_NOT_EXIST ; SQLSTATE: HY000 Message: Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group. Error number: MY-013787 ; Symbol: ER_GRP_RPL_FAILOVER_REGISTER_MESSAGE_LISTENER_SERVICE ; SQLSTATE: HY000 Message: Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'. Error number: MY-013788 ; Symbol: ER_GRP_RPL_FAILOVER_PRIMARY_WITHOUT_MAJORITY ; SQLSTATE: HY000 Message: This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority. Error number: MY-013789 ; Symbol: ER_GRP_RPL_FAILOVER_PRIMARY_BACK_TO_MAJORITY ; SQLSTATE: HY000 Message: This server is back to the group majority. Replication failover channels handling is resumed. Error number: MY-013790 ; Symbol: ER_RPL_INCREMENTING_MEMBER_ACTION_VERSION ; SQLSTATE: HY000 Message: Error incrementing member action configuration version for %s.%s table. Error number: MY-013791 ; Symbol: ER_GRP_RPL_REPLICA_THREAD_ERROR_ON_SECONDARY_MEMBER ; SQLSTATE: HY000 Message: The '%s' thread of channel '%s' will error out as this server is a group secondary. Error number: MY-013796 ; Symbol: ER_IB_WRN_ENCRYPTION_INFO_SIZE_MISMATCH ; SQLSTATE: HY000 Message: Ignoring encryption INFO size in redo log: %zu, expected: Message: Option --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid. Error number: MY-013798 ; Symbol: ER_AUTHENTICATION_PLUGIN_REGISTRATION_FAILED ; SQLSTATE: HY000 Message: Signature verification failed during registration. Error number: MY-013799 ; Symbol: ER_AUTHENTICATION_PLUGIN_REGISTRATION_INSUFFICIENT_BUFFER ; SQLSTATE: HY000 Message: Buffer too small to hold registration challenge response. Error number: MY-013800 ; Symbol: ER_AUTHENTICATION_PLUGIN_AUTH_DATA_CORRUPT ; SQLSTATE: HY000 Message: FIDO device authenticator data corrupt. Error number: MY-013801 ; Symbol: ER_AUTHENTICATION_PLUGIN_SIGNATURE_CORRUPT ; SQLSTATE: HY000 Message: FIDO device signature corrupt. Error number: MY-013802 ; Symbol: ER_AUTHENTICATION_PLUGIN_VERIFY_SIGNATURE_FAILED ; SQLSTATE: HY000 Message: Signature verification failed during authentication. Error number: MY-013805 ; Symbol: ER_WARN_REPLICA_GTID_ONLY_AND_GTID_MODE_NOT_ON ; SQLSTATE: HY000 Message: Replication channel '%s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0. Error number: MY-013806 ; Symbol: ER_WARN_L_DISABLE_GTID_ONLY_WITH_SOURCE_AUTO_POS_INVALID_POS ; SQLSTATE: HY000 Message: The replication positions relative to the source may be out-of-date on channel '%s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values. Error number: MY-013808 ; Symbol: ER_AUTHENTICATION_OCI_PLUGIN_NOT_INITIALIZED ; SQLSTATE: HY000 Message: Authentication plugin not initialized. Error number: MY-013809 ; Symbol: ER_AUTHENTICATION_OCI_PRIVATE_KEY_ERROR ; SQLSTATE: HY000 Message: Cannot use the generated private key file. Error number: MY-013810 ; Symbol: ER_AUTHENTICATION_OCI_DOWNLOAD_PUBLIC_KEY ; SQLSTATE: HY000 Message: Unavailable public key with fingerprint %s for user %s in tenancy %s . Error number: MY-013813 ; Symbol: ER_AUTHENTICATION_OCI_INVALID_AUTHENTICATION_STRING ; SQLSTATE: HY000 Message: Invalid authentication string details for user: `%s`@`%s`. Error number: MY-013814 ; Symbol: ER_AUTHENTICATION_OCI_NO_MATCHING_GROUPS ; SQLSTATE: HY000 Message: None of the groups returned by IAM matches any of the entries from authentication string. Error number: MY-013821 ; Symbol: ER_GRP_RPL_ERROR_SET_SINGLE_CONSENSUS_LEADER ; SQLSTATE: HY000 Message: Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong. Error number: MY-013823 ; Symbol: ER_GRP_RPL_ERROR_SET_MULTI_CONSENSUS_LEADER ; SQLSTATE: HY000 Message: Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong. Error number: MY-013824 ; Symbol: ER_GRP_RPL_PAXOS_SINGLE_LEADER_DIFF_FROM_GRP ; SQLSTATE: HY000 Message: This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group. Message: %s: '%s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead. Message: More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu. Error number: MY-013831 ; Symbol: ER_IB_MSG_TRYING_TO_OPEN_FILE_FOR_LONG_TIME ; SQLSTATE: HY000 Message: Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher. Message: Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions. Error number: MY-013837 ; Symbol: ER_KEYRING_OKV_STANDBY_SERVER_COUNT_EXCEEDED ; SQLSTATE: HY000 Message: Number of STANDBY_SERVER values exceeded maximum limit of Error number: MY-013839 ; Symbol: ER_WARN_CANNOT_PERSIST_SENSITIVE_VARIABLES ; SQLSTATE: HY000 Message: Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available. Error number: MY-013840 ; Symbol: ER_CANNOT_INTERPRET_PERSISTED_SENSITIVE_VARIABLES ; SQLSTATE: HY000 Message: Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available. Error number: MY-013841 ; Symbol: ER_PERSISTED_VARIABLES_KEYRING_SUPPORT_REQUIRED ; SQLSTATE: HY000 Message: Keyring has to be loaded through manifest file in order to support secure storage for persisted variables Error number: MY-013842 ; Symbol: ER_PERSISTED_VARIABLES_MASTER_KEY_NOT_FOUND ; SQLSTATE: HY000 Message: Could not find master key %s in keyring Error number: MY-013843 ; Symbol: ER_PERSISTED_VARIABLES_MASTER_KEY_CANNOT_BE_GENERATED ; SQLSTATE: HY000 Message: A new master key %s could not be generated Error number: MY-013844 ; Symbol: ER_PERSISTED_VARIABLES_ENCRYPTION_FAILED ; SQLSTATE: HY000 Message: Failed to encrypt %s using %s Error number: MY-013845 ; Symbol: ER_PERSISTED_VARIABLES_DECRYPTION_FAILED ; SQLSTATE: HY000 Message: Failed to decrypt %s using %s Error number: MY-013846 ; Symbol: ER_PERSISTED_VARIABLES_LACK_KEYRING_SUPPORT ; SQLSTATE: HY000 Message: Persisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file. Message: Password for the account '%s'@'%s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator. Error number: MY-013853 ; Symbol: ER_THREAD_POOL_DEDICATED_LISTENERS_INVALID ; SQLSTATE: HY000 Message: thread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0 Message: The redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6. Message: The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file. Message: The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file. Error number: MY-013860 ; Symbol: ER_IB_MSG_LOG_INIT_DIR_NOT_EMPTY_WONT_INITIALIZE ; SQLSTATE: HY000 Message: --initialize specified but the redo log directory %s has redo log files inside. Aborting. Error number: MY-013863 ; Symbol: ER_IB_MSG_LOG_FILES_CREATED_BY_CLONE_AND_READ_ONLY_MODE ; SQLSTATE: HY000 Message: Cannot restore cloned data directory, InnoDB running in read-only mode! Error number: MY-013865 ; Symbol: ER_IB_MSG_LOG_WRITER_WAIT_ON_NEW_LOG_FILE ; SQLSTATE: HY000 Message: Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. Error number: MY-013866 ; Symbol: ER_IB_MSG_RECOVERY_CHECKPOINT_OUTSIDE_LOG_FILE ; SQLSTATE: HY000 Message: Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted. Error number: MY-013867 ; Symbol: ER_IB_MSG_LOG_WRITER_ENTERED_EXTRA_MARGIN ; SQLSTATE: HY000 Message: Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity. Error number: MY-013868 ; Symbol: ER_IB_MSG_LOG_WRITER_EXITED_EXTRA_MARGIN ; SQLSTATE: HY000 Message: Redo log reclaimed some free space, resuming user threads. Error number: MY-013872 ; Symbol: ER_IB_MSG_LOG_UPGRADE_IN_READ_ONLY_MODE ; SQLSTATE: HY000 Message: Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only). Message: Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2). Error number: MY-013874 ; Symbol: ER_IB_MSG_LOG_UPGRADE_UNINITIALIZED_FILES ; SQLSTATE: HY000 Message: Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2). Error number: MY-013875 ; Symbol: ER_IB_MSG_LOG_UPGRADE_CORRUPTION__UNEXPECTED ; SQLSTATE: HY000 Message: Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2). Error number: MY-013889 ; Symbol: ER_IB_MSG_LOG_FILE_MARK_CURRENT_AS_INCOMPLETE ; SQLSTATE: HY000 Message: Marked the current redo log file %s as incomplete. Error number: MY-013891 ; Symbol: ER_IB_MSG_LOG_FILE_RENAME_ON_CREATE_FAILED ; SQLSTATE: HY000 Message: Failed to rename %s when creating redo log file %s (error: %d) Error number: MY-013892 ; Symbol: ER_IB_MSG_LOG_FILES_CREATED_BY_UNKNOWN_CREATOR ; SQLSTATE: HY000 Message: Redo log files created by unknown creator %s. Message: Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0. Error number: MY-013898 ; Symbol: ER_IB_MSG_LOG_PFS_ACQUIRE_SERVICES_FAILED ; SQLSTATE: HY000 Message: Failed to initialize services required to handle redo log PFS tables. Error number: MY-013901 ; Symbol: ER_IB_MSG_LOG_FILE_UNUSED_RESIZE_FAILED ; SQLSTATE: HY000 Message: Failed to resize unused redo log file %s to %llu MB (%s). Error number: MY-013902 ; Symbol: ER_IB_MSG_LOG_FILE_UNUSED_REMOVE_FAILED ; SQLSTATE: HY000 Message: Failed to remove unused redo log file %s. Error number: MY-013903 ; Symbol: ER_IB_MSG_LOG_FILE_UNUSED_RENAME_FAILED ; SQLSTATE: HY000 Message: Failed to rename unused redo log file %s to %s. Error number: MY-013904 ; Symbol: ER_IB_MSG_LOG_FILE_UNUSED_MARK_AS_IN_USE_FAILED ; SQLSTATE: HY000 Message: Failed to mark unused redo log file %s as in use (by renaming to %s). Error number: MY-013905 ; Symbol: ER_IB_MSG_LOG_FILE_MARK_AS_UNUSED_FAILED ; SQLSTATE: HY000 Message: Failed to mark redo log file %s as unused (by renaming to Error number: MY-013906 ; Symbol: ER_IB_MSG_LOG_PARAMS_DEDICATED_SERVER_IGNORED ; SQLSTATE: HY000 Message: Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM. Message: Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead. Message: This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group. Message: Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology. Error number: MY-013910 ; Symbol: ER_BINLOG_CRASH_RECOVERY_ERROR_RETURNED_SE ; SQLSTATE: HY000 Message: Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files. Error number: MY-013911 ; Symbol: ER_BINLOG_CRASH_RECOVERY_ENGINE_RESULTS ; SQLSTATE: HY000 Message: Crash recovery finished in %s engine. %s Error number: MY-013913 ; Symbol: ER_BINLOG_CRASH_RECOVERY_ROLLBACK_FAILED ; SQLSTATE: HY000 Message: Failed to rollback %s in %s, with failure code %s. Error number: MY-013914 ; Symbol: ER_BINLOG_CRASH_RECOVERY_PREPARE_FAILED ; SQLSTATE: HY000 Message: Failed to prepare %s in %s, with failure code %s. Error number: MY-013915 ; Symbol: ER_COMPONENT_EE_SYS_VAR_REGISTRATION_FAILURE ; SQLSTATE: HY000 Message: Cannot register variable '%s'. Please check if it is not already registered by another component. Error number: MY-013916 ; Symbol: ER_COMPONENT_EE_SYS_VAR_DEREGISTRATION_FAILURE ; SQLSTATE: HY000 Message: Cannot unregister variable '%s'. Please check if it was registered properly in the first place. Error number: MY-013917 ; Symbol: ER_COMPONENT_EE_FUNCTION_REGISTRATION_FAILURE ; SQLSTATE: HY000 Message: Cannot register function '%s'. Please check if it is not already registered. Error number: MY-013918 ; Symbol: ER_COMPONENT_EE_FUNCTION_DEREGISTRATION_FAILURE ; SQLSTATE: HY000 Message: Cannot unregister function '%s'. Please check if it was registered properly in the first place. Error number: MY-013919 ; Symbol: ER_COMPONENT_EE_FUNCTION_INVALID_ARGUMENTS ; SQLSTATE: HY000 Message: Invalid arguments to function '%s'. Expected values: %s. Error number: MY-013920 ; Symbol: ER_COMPONENT_EE_FUNCTION_INVALID_ALGORITHM ; SQLSTATE: HY000 Message: Invalid algorithm value '%s' in function %s. Error number: MY-013921 ; Symbol: ER_COMPONENT_EE_FUNCTION_KEY_LENGTH_OUT_OF_RANGE ; SQLSTATE: HY000 Message: Invalid key length '%d' for function '%s' with algorithm '%s'. Please provide a value between [%d, %d]. Error number: MY-013922 ; Symbol: ER_COMPONENT_EE_FUNCTION_PRIVATE_KEY_GENERATION_FAILURE ; SQLSTATE: HY000 Message: Failed to generate private key of length '%d' with algorithm '%s' in function '%s'. More details about the error would have been logged before this message. Error number: MY-013923 ; Symbol: ER_COMPONENT_EE_FUNCTION_PUBLIC_KEY_GENERATION_FAILURE ; SQLSTATE: HY000 Message: Failed to generate public key with algorithm '%s' for given private key in function '%s'. More details about the error would have been logged before this message. Error number: MY-013924 ; Symbol: ER_COMPONENT_EE_DATA_LENGTH_OUT_OF_RAGE ; SQLSTATE: HY000 Message: Invalid data length '%d' (in bytes) for function '%s' with algorithm '%s'. The maximum support data length for given private key is %d (in bytes). Message: Could not encrypt data in function '%s' using algorithm '%s'. Data length was '%d' bytes. More details about the error would have been logged before this message. Message: Could not decrypt data in function '%s' using algorithm '%s'. Data length was '%d' bytes. More details about the error would have been logged before this message. Message: Could not sign data in function '%s' using algorithm '%s' and digest type '%s'. More details about the error would have logged before this message. Error number: MY-013933 ; Symbol: ER_THREAD_POOL_CANNOT_REGISTER_DYNAMIC_PRIVILEGE ; SQLSTATE: HY000 Message: Failed to register dynamic privilege %s. Message: Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity. Error number: MY-013941 ; Symbol: ER_IB_MSG_CLEAR_INSTANT_DROP_COLUMN_METADATA ; SQLSTATE: HY000 Message: Failed to clear instant drop column metadata for table %s Error number: MY-013943 ; Symbol: ER_COMPONENT_KEYRING_OCI_CREATE_PRIVATE_KEY ; SQLSTATE: HY000 Message: Out of memory! Cannot create private key. Error number: MY-013945 ; Symbol: ER_NOTE_COMPONENT_KEYRING_OCI_MISSING_NAME_OR_TYPE ; SQLSTATE: HY000 Message: Incomplete key: missing Name/Type for the Key: %s. Error number: MY-013946 ; Symbol: ER_WARN_COMPONENT_KEYRING_OCI_DUPLICATE_KEY ; SQLSTATE: HY000 Message: Duplicate key found in keyring with Name: %s and Owner: Error number: MY-013952 ; Symbol: ER_IB_MSG_BUF_POOL_RESIZE_COMPLETE_CUR_CODE ; SQLSTATE: HY000 Message: Status code %u: Completed Error number: MY-013953 ; Symbol: ER_IB_MSG_BUF_POOL_RESIZE_PROGRESS_UPDATE ; SQLSTATE: HY000 Message: Status code %u: %u%% complete Error number: MY-013955 ; Symbol: ER_THREAD_POOL_QUERY_THREADS_PER_GROUP_INVALID ; SQLSTATE: HY000 Message: Invalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u. Error number: MY-013956 ; Symbol: ER_THREAD_POOL_QUERY_THRS_PER_GRP_EXCEEDS_TXN_THR_LIMIT ; SQLSTATE: HY000 Message: Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per group Message: %s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics. Message: %s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux! Error number: MY-013964 ; Symbol: ER_REPLICATION_INCOMPATIBLE_TABLE_WITH_GIPK ; SQLSTATE: HY000 Message: Failed to apply row event with %d columns, originating from a server of version %s on table '%s.%s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication. Error number: MY-013967 ; Symbol: ER_BULK_LOADER_FILE_CONTAINS_LESS_LINES_THAN_IGNORE_CLAUSE_LOG ; SQLSTATE: HY000 Message: The first file being loaded contained less lines than the ignore clause Error number: MY-013974 ; Symbol: ER_BULK_PARSER_ROW_BUFFER_MAX_TOTAL_COLS_EXCEEDED_LOG ; SQLSTATE: HY000 Message: The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'. Error number: MY-013975 ; Symbol: ER_BULK_PARSER_COPY_BUFFER_SIZE_EXCEEDED_LOG ; SQLSTATE: HY000 Message: The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'. Error number: MY-013976 ; Symbol: ER_BULK_PARSER_UNEXPECTED_END_OF_INPUT_LOG ; SQLSTATE: HY000 Message: Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing. Error number: MY-013977 ; Symbol: ER_BULK_PARSER_UNEXPECTED_ROW_TERMINATOR_LOG ; SQLSTATE: HY000 Message: Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing. Error number: MY-013978 ; Symbol: ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_ENDING_ENCLOSED_BY_LOG ; SQLSTATE: HY000 Message: Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'. Error number: MY-013979 ; Symbol: ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_NULL_ESCAPE_LOG ; SQLSTATE: HY000 Message: Unexpected characters after NULL escape (\\N) found at row %ld in file '%s'. Error number: MY-013980 ; Symbol: ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_COLUMN_TERMINATOR_LOG ; SQLSTATE: HY000 Message: Unexpected characters after column terminator found at row %ld in file '%s'. Error number: MY-013981 ; Symbol: ER_BULK_PARSER_INCOMPLETE_ESCAPE_SEQUENCE_LOG ; SQLSTATE: HY000 Message: Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence. Error number: MY-013982 ; Symbol: ER_LOAD_BULK_DATA_WRONG_VALUE_FOR_FIELD_LOG ; SQLSTATE: HY000 Message: Incorrect %s value: '%s' for column '%s' at row %ld in file '%s' Error number: MY-013983 ; Symbol: ER_LOAD_BULK_DATA_WARN_NULL_TO_NOTNULL_LOG ; SQLSTATE: HY000 Message: NULL supplied to NOT NULL column '%s' at row %ld in file Error number: MY-013988 ; Symbol: ER_REQUIRE_TABLE_PRIMARY_KEY_CHECK_GENERATE_WITH_GR_IN_REPO ; SQLSTATE: HY000 Message: Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it. Error number: MY-013990 ; Symbol: ER_GRP_RPL_PAXOS_SINGLE_LEADER_DIFF_FROM_OLD_GRP ; SQLSTATE: HY000 Message: This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group. Message: Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging Error number: MY-013997 ; Symbol: ER_RPL_ASYNC_NEXT_FAILOVER_CHANNEL_SELECTED ; SQLSTATE: HY000 Message: The connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d' Error number: MY-013998 ; Symbol: ER_RPL_REPLICA_SOURCE_UUID_HAS_NOT_CHANGED ; SQLSTATE: HY000 Message: The Replica which was connected to source \'%s:%d\', is now connected to new source \'%s:%d\', but still has the same server_uuid %s. Error number: MY-013999 ; Symbol: ER_RPL_REPLICA_SOURCE_UUID_HAS_CHANGED_HOST_PORT_UNCHANGED ; SQLSTATE: HY000 Message: The server_uuid for source server \'%s:%d\' has changed from %s to %s. This should not happen unless you have changed it manually. Error number: MY-014000 ; Symbol: ER_RPL_REPLICA_SOURCE_UUID_HOST_PORT_HAS_CHANGED ; SQLSTATE: HY000 Message: The source server has changed from \'%s:%d\' with server_uuid %s, to \'%s:%d\' with server_uuid %s. Error number: MY-014001 ; Symbol: ER_RPL_REPLICA_CONNECTED_TO_SOURCE_RPL_STARTED_FILE_BASED ; SQLSTATE: HY000 Message: Replica receiver thread%s: connected to source \'%s@%s:%d\' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'. Error number: MY-014002 ; Symbol: ER_RPL_REPLICA_CONNECTED_TO_SOURCE_RPL_STARTED_GTID_BASED ; SQLSTATE: HY000 Message: Replica receiver thread%s: connected to source \'%s@%s:%d\' with server_uuid=%s, server_id=%d. Starting GTID-based replication. Error number: MY-014005 ; Symbol: ER_WARN_DEPRECATED_USER_DEFINED_COLLATIONS_OPTION ; SQLSTATE: HY000 Message: %s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead. Message: Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes. Message: Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version. Error number: MY-014009 ; Symbol: ER_WARN_COMPONENTS_INFRASTRUCTURE_MANIFEST_MULTIPLE_KEYRING ; SQLSTATE: HY000 Message: Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time. Error number: MY-014013 ; Symbol: ER_NOTE_COMPONENT_SLOT_REGISTRATION_SUCCESS ; SQLSTATE: HY000 Message: Successfully registered slot '%d' for component '%s'. Error number: MY-014014 ; Symbol: ER_NOTE_COMPONENT_SLOT_DEREGISTRATION_SUCCESS ; SQLSTATE: HY000 Message: Successfully de-registered slot '%d' from component '%s'. Error number: MY-014015 ; Symbol: ER_WARN_CANNOT_FREE_COMPONENT_DATA_DEALLOCATION_FAILED ; SQLSTATE: HY000 Message: Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources. Error number: MY-014025 ; Symbol: ER_AUTHENTICATION_OCI_TOKEN_DETAILS_MISMATCH ; SQLSTATE: HY000 Message: Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'. Error number: MY-014026 ; Symbol: ER_AUTHENTICATION_OCI_TOKEN_NOT_VERIFIED ; SQLSTATE: HY000 Message: Verification failed for security token provided by '%s' for '%s'@'%s' : %s. Error number: MY-014027 ; Symbol: ER_AUTHENTICATION_OCI_DOWNLOAD_IDDP_PUBLIC_KEY ; SQLSTATE: HY000 Message: Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid. Error number: MY-014045 ; Symbol: ER_COMPONENT_MASKING_RANDOM_CREATE_REASON ; SQLSTATE: HY000 Message: Creation of random context failed because %s. Error number: MY-014046 ; Symbol: ER_COMPONENT_MASKING_CANNOT_ACCESS_TABLE ; SQLSTATE: HY000 Message: Cannot access %s.%s table. Message: Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode. Error number: MY-014053 ; Symbol: ER_AUDIT_LOG_INVALID_FLUSH_INTERVAL_VALUE ; SQLSTATE: HY000 Message: Invalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %d Error number: MY-014054 ; Symbol: ER_LOG_CANNOT_PURGE_BINLOG_WITH_BACKUP_LOCK ; SQLSTATE: HY000 Message: Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock. Message: Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u. Message: Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u. Message: Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not. Message: Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details. Message: DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'. Message: bulkflusher: Failed to punch hole: table=%s, index=%s, space_id=%zu, page_no=%zu, disk_page_size=%zu, hole_size=%zu, file=%s, err=%zu Error number: MY-015006 ; Symbol: ER_FAILED_TO_VALIDATE_CERTIFICATES_SERVER_EXIT ; SQLSTATE: HY000 Message: Certificate validation has failed. Stopping the server as tls-certificates-enforced-validation is enabled Error number: MY-015021 ; Symbol: ER_COMPONENTS_INFRASTRUCTURE_SHUTDOWN_START ; SQLSTATE: HY000 Message: MySQL Server: Components Shutdown - start. Error number: MY-015022 ; Symbol: ER_COMPONENTS_INFRASTRUCTURE_SHUTDOWN_END ; SQLSTATE: HY000 Message: MySQL Server: Components Shutdown - end (with return value = %d). Error number: MY-015027 ; Symbol: ER_GRP_RPL_MYSQL_NETWORK_PROVIDER_SERVER_ERROR_COMMAND_ERR ; SQLSTATE: HY000 Message: Failed to accept a MySQL connection for Group Replication. %s. Please retry. Error number: MY-015028 ; Symbol: ER_COMPONENT_KEYRING_OCI_INVALID_CONFIG_VAR ; SQLSTATE: HY000 Message: Invalid value of argument %s (%s). Error number: MY-015029 ; Symbol: ER_WARN_OPTION_RESET_AND_IGNORED_DURING_INITIALIZE ; SQLSTATE: HY000 Message: Ignoring a non-default value for %s during --initialize. Error number: MY-015031 ; Symbol: ER_FIREWALL_INVALID_RELOAD_INTERVAL_VALUE ; SQLSTATE: HY000 Message: Invalid reload interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %d. Error number: MY-015032 ; Symbol: ER_WARN_DEPRECATED_DYNAMIC_PRIV_FOR_USER ; SQLSTATE: HY000 Message: '%s' (granted to '%s@%s') is deprecated and will be removed in a future release. Message: Fixed wrong page_id with sync read: buf_block_t[space_id=%zu, page_no=%zu], buf_frame_t[space_id=%zu, page_no=%zu], file=%s, retry=%zu Message: Wrong page_id after sync read: buf_block_t[space_id=%zu, page_no=%zu], buf_frame_t[space_id=%zu, page_no=%zu], file=%s, retry=%zu Message: Sync read to fix wrong page_id failed: buf_block_t[space_id=%zu, page_no=%zu], file=%s, err=%zu, retry=%zu Error number: MY-015043 ; Symbol: ER_START_REPLICA_CHANNEL_INVALID_CONFIGURATION_LOG ; SQLSTATE: HY000 Message: Cannot start replication channel '%s' because %s. Error number: MY-015044 ; Symbol: ER_GROUP_REPLICATION_CERTIFIER_MESSAGE_LARGE ; SQLSTATE: HY000 Message: The certification information, part of the required information to the new member join the group, is too big and cannot be send. Please wait until the value of the column COUNT_TRANSACTIONS_ROWS_VALIDATING of the table performance_schema.replication_group_member_stats decreases and try to join the new member again. Error number: MY-015045 ; Symbol: ER_GROUP_REPLICATION_METADATA_SENDER_IS_REMOTE ; SQLSTATE: HY000 Message: The member %s:%u will be the one sending the recovery metadata message. Error number: MY-015047 ; Symbol: ER_GROUP_REPLICATION_ERROR_COMPRESS_INITIALIZE ; SQLSTATE: HY000 Message: Error initializing the %s compression context. Data cannot be compressed. Error number: MY-015049 ; Symbol: ER_GROUP_REPLICATION_UNKOWN_COMPRESSION_TYPE ; SQLSTATE: HY000 Message: Error unknown Compression Library requested. Error number: MY-015050 ; Symbol: ER_GROUP_REPLICATION_COMPRESS_EXCEEDS_MAX_SIZE ; SQLSTATE: HY000 Message: Error while compressing data using %s compression. The operation could not be performed as buffer size exceeded configured maximum size. Please wait until the value of the column COUNT_TRANSACTIONS_ROWS_VALIDATING of the table performance_schema.replication_group_member_stats decreases and try to join the new member again. Error number: MY-015051 ; Symbol: ER_GROUP_REPLICATION_COMPRESS_OUT_OF_MEMORY ; SQLSTATE: HY000 Message: Error while compressing data using %s compression. The operation could not be performed as memory allocation failed. Error number: MY-015052 ; Symbol: ER_GROUP_REPLICATION_ERROR_DECOMPRESS_INITIALIZE ; SQLSTATE: HY000 Message: Error initializing the %s decompression context. Data cannot be decompressed. Error number: MY-015053 ; Symbol: ER_GROUP_REPLICATION_DECOMPRESS_EXCEEDS_MAX_SIZE ; SQLSTATE: HY000 Message: Error while decompressing data using %s compression. The operation could not be performed as buffer size exceeded configured maximum size. Please wait until the value of the column COUNT_TRANSACTIONS_ROWS_VALIDATING of the table performance_schema.replication_group_member_stats decreases and try to join the new member again. Error number: MY-015054 ; Symbol: ER_GROUP_REPLICATION_DECOMPRESS_OUT_OF_MEMORY ; SQLSTATE: HY000 Message: Error while decompressing data using %s compression. The operation could not be performed as memory allocation failed. Error number: MY-015055 ; Symbol: ER_GROUP_REPLICATION_DECOMPRESS_TRUNCATED ; SQLSTATE: HY000 Message: Error while decompressing data using %s compression. The operation could not be performed as all the input provided to decompress is consumed, but the decompressed output produced is less than required. Error number: MY-015056 ; Symbol: ER_GROUP_REPLICATION_DECOMPRESS_CORRUPTED ; SQLSTATE: HY000 Message: Error while decompressing data using %s compression. The operation could not be performed as the compression library reported an error. Message: Error while decompressing data using %s compression. The operation could not be performed as no more input bytes remaining to decompress. The decompressed output has not been changed. Error number: MY-015058 ; Symbol: ER_GROUP_REPLICATION_DECOMPRESS_PROCESS ; SQLSTATE: HY000 Message: Error while decompressing data using %s compression. Data cannot be decompressed. Error number: MY-015060 ; Symbol: ER_GROUP_REPLICATION_METADATA_PROTOBUF_PARSING ; SQLSTATE: HY000 Message: Error while parsing serialzed Certification_info from received Recovery Metadata to Protobuf format using Protobuf library. Error number: MY-015061 ; Symbol: ER_GROUP_REPLICATION_PROTOBUF_SERIALIZING_ERROR ; SQLSTATE: HY000 Message: Error while serializing % data using Protobuf library. Error number: MY-015062 ; Symbol: ER_GROUP_REPLICATION_ERROR_RECEIVED_WAITING_METADATA ; SQLSTATE: HY000 Message: Error received while the Recovery thread was waiting for the Recovery Metadata. The Recovery will be terminated. Error number: MY-015063 ; Symbol: ER_GROUP_REPLICATION_TIMEOUT_ERROR_FETCHING_METADATA ; SQLSTATE: HY000 Message: Error fetching AFTER_GTIDS from Recovery Metadata by Recovery thread. The Recovery thread timeout after waiting for %d seconds. The Recovery will be terminated. Error number: MY-015064 ; Symbol: ER_GROUP_REPLICATION_METADATA_PAYLOAD_EMPTY ; SQLSTATE: HY000 Message: Error while decoding the received Recovery Metadata Message. The received payload is empty which could be due to error in decoding of received Recovery Metadata Message. The joining member will leave the group. Error number: MY-015065 ; Symbol: ER_GROUP_REPLICATION_METADATA_MESSAGE_PAYLOAD_EMPTY ; SQLSTATE: HY000 Message: The %s payload type of the received Recovery Metadata Message is empty. Error number: MY-015066 ; Symbol: ER_GROUP_REPLICATION_METADATA_READ_GTID_EXECUTED ; SQLSTATE: HY000 Message: Error reading gtid_executed from the received Recovery Metadata Message. Error number: MY-015067 ; Symbol: ER_GROUP_REPLICATION_METADATA_PAYLOAD_DECODING ; SQLSTATE: HY000 Message: Error while decoding the received Recovery Metadata Message. Error number: MY-015068 ; Symbol: ER_GROUP_REPLICATION_METADATA_SEND_ERROR ; SQLSTATE: HY000 Message: The group was unable to send the Recovery Metadata to a joining member. Error number: MY-015069 ; Symbol: ER_GROUP_REPLICATION_METADATA_SAVE_RECOVERY_COPY ; SQLSTATE: HY000 Message: Error while saving copy of Recovery Metadata Message. Error number: MY-015070 ; Symbol: ER_GROUP_REPLICATION_METADATA_CERT_INFO_ERROR_PROCESSING ; SQLSTATE: HY000 Message: Error while processing received Certification Information from the Recovery Metadata Message. Error number: MY-015071 ; Symbol: ER_GROUP_REPLICATION_METADATA_CERT_INFO_PACKET_EMPTY ; SQLSTATE: HY000 Message: Error Certification Information packet from the received Recovery Metadata Message is empty. Error number: MY-015072 ; Symbol: ER_GROUP_REPLICATION_METADATA_ERROR_ON_SEND_ERROR_MESSAGE ; SQLSTATE: HY000 Message: Error while sending Recovery metadata error message. If this is a temporary failure of send message and member itself hasn't left the group, then joiner will timeout waiting for Recovery metadata message. If this is a permanent failure, the member will leave the group and another member will send the Recovery metadata message. Error number: MY-015073 ; Symbol: ER_GROUP_REPLICATION_METADATA_SET_IN_RECOVERY_FAILED ; SQLSTATE: HY000 Message: Error when transferring Recovery Metadata Message to Recovery. The joining member will leave the group. Error number: MY-015074 ; Symbol: ER_GROUP_REPLICATION_CERTIFICATION_MODULE_FAILURE ; SQLSTATE: HY000 Message: Error Certification module wasn't properly initialized. Error number: MY-015075 ; Symbol: ER_GROUP_REPLICATION_METADATA_INITIALIZATION_FAILURE ; SQLSTATE: HY000 Message: Error Recovery Metadata Message module wasn't properly initialized. Error number: MY-015076 ; Symbol: ER_GROUP_REPLICATION_METADATA_MEMORY_ALLOC ; SQLSTATE: HY000 Message: Error while %s. The operation could not be performed as memory allocation failed. Error number: MY-015077 ; Symbol: ER_GROUP_REPLICATION_RECOVERY_SKIPPED_GTID_PRESENT ; SQLSTATE: HY000 Message: The group replication recovery is skipped as the joiner's gtid executed set %s already has all the transactions of the donor's gtid set %s. Error number: MY-015078 ; Symbol: ER_GROUP_REPLICATION_RECOVERY_FETCHING_GTID_EXECUTED_SET ; SQLSTATE: HY000 Message: Error in Group Replication Recovery while getting member's global GTID executed set. Error number: MY-015079 ; Symbol: ER_GROUP_REPLICATION_RECOVERY_ERROR_ADD_GTID_EXECUTED ; SQLSTATE: HY000 Message: Error in Group Replication Recovery while adding GTIDs in string format to Gtid_set. Error number: MY-015080 ; Symbol: ER_GROUP_REPLICATION_RECOVERY_METADATA_SENDER_NOT_FOUND ; SQLSTATE: HY000 Message: Error computing the current Recovery metadata sender. Check if this MEMBER is not leaving the group and the joiner is able to successfully fetch the recovery metadata or not. Error number: MY-015081 ; Symbol: ER_GROUP_REPLICATION_METADATA_CERT_INFO_PACKET_COUNT_ERROR ; SQLSTATE: HY000 Message: Error in the received Recovery Metadata Message the number of compressed Certification Information packet count mismatch with the number of sent compressed Certification Information packets. Error number: MY-015082 ; Symbol: ER_GROUP_REPLICATION_METADATA_CERT_INFO_ENCODING_ERROR ; SQLSTATE: HY000 Message: Error while encoding Certification Information for the Recovery Metadata Message. Error number: MY-015083 ; Symbol: ER_GROUP_REPLICATION_METADATA_NO_VALID_DONOR ; SQLSTATE: HY000 Message: There are no valid recovery metadata donors. The joining member will leave the group. Error number: MY-015084 ; Symbol: ER_GROUP_REPLICATION_NO_CERTIFICATION_DONOR_AVAILABLE ; SQLSTATE: HY000 Message: No donor available to provide the certification information, part of the required information to the new member join the group. Please wait until there are ONLINE members on the group and try to join the new member again. Error number: MY-015085 ; Symbol: ER_GROUP_REPLICATION_RECOVERY_STOPPED_GTID_PRESENT ; SQLSTATE: HY000 Message: The group replication recovery is complete, joiner gtid executed set has all the transactions of the donor's gtid set %s. Message: The Monitor IO thread encountered an error while executing the query to check connection to the source server. Error: %s. The query failed to execute on the source (host:%s port:%u network_namespace:%s) for channel '%s'. Error number: MY-015087 ; Symbol: ER_RPL_ASYNC_MONITOR_IO_THD_FETCH_GROUP_MAJORITY_ERROR ; SQLSTATE: HY000 Message: The Monitor IO thread failed to detect if the source belongs to the group majority. Error: %s. The query failed to execute on the source (host:%s port:%u network_namespace:%s) for channel '%s'. Error number: MY-015088 ; Symbol: ER_RPL_ASYNC_REPLICA_IO_THD_FETCH_GROUP_MAJORITY_ERROR ; SQLSTATE: HY000 Message: The replica IO thread failed to detect if the source belongs to the group majority. Error: %s. The query failed to execute on the source (host:%s port:%u network_namespace:%s) for channel '%s'. Error number: MY-015089 ; Symbol: ER_RPL_ASYNC_GET_GROUP_MEMBERSHIP_DETAILS_ERROR ; SQLSTATE: HY000 Message: The Monitor IO thread failed to get group membership details. Error: %s. The query failed to execute on the source (host:%s port:%u network_namespace:%s) for channel '%s'. Error number: MY-015090 ; Symbol: ER_IB_ERR_CORRUPT_TABLESPACE_UNRECOVERABLE ; SQLSTATE: HY000 Message: Tablespace '%u' mentioned in the redo log is corrupted in a way it is unrecoverable by double-write buffer, so further redo log recovery is not possible! Error number: MY-015092 ; Symbol: ER_COMPONENT_MASKING_INVALID_FLUSH_INTERVAL_VALUE ; SQLSTATE: HY000 Message: Invalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %d. Error number: MY-015093 ; Symbol: ER_COMPONENT_MASKING_VAR_REGISTRATION_FAILURE ; SQLSTATE: HY000 Message: Cannot register variable '%s'.'%s'. Error number: MY-015094 ; Symbol: ER_COMPONENT_MASKING_NOTIFICATION_REGISTRATION_FAILURE ; SQLSTATE: HY000 Message: Masking component failed to register notification service. Periodical masking dictionaries flush will not work. Error number: MY-015096 ; Symbol: ER_GRP_RPL_APPLIER_ERROR_PACKET_RECEIVED ; SQLSTATE: HY000 Message: The Applier process of Group Replication found an error and was requested to stop: %s Error number: MY-015098 ; Symbol: ER_WARN_LANGUAGE_COMPONENT_CANNOT_UNINSTALL ; SQLSTATE: HY000 Message: Cannot uninstall the language component: %s. Error number: MY-015101 ; Symbol: ER_LANGUAGE_COMPONENT_VM_API_FUNCTION_ERROR ; SQLSTATE: HY000 Message: Internal VM API function failed: %s. Error number: MY-015102 ; Symbol: ER_LANGUAGE_COMPONENT_VM_INTERNAL_ERROR ; SQLSTATE: HY000 Message: Internal VM error while %s. Error number: MY-015103 ; Symbol: ER_WARN_LANGUAGE_COMPONENT_RESOURCE_LIMIT ; SQLSTATE: HY000 Message: The resource limit has been exceeded. Details: %s. Error number: MY-015105 ; Symbol: ER_KEYRING_COMPONENT_KEYRING_FILE_NAME_EMPTY ; SQLSTATE: HY000 Message: Keyring file path is empty in configuration file. Error number: MY-015106 ; Symbol: ER_KEYRING_COMPONENT_KEYRING_FILE_READ_FAILED ; SQLSTATE: HY000 Message: Failed to read keyring file: %s. Error number: MY-015107 ; Symbol: ER_KEYRING_COMPONENT_KEYRING_FILE_DECRYPT_FAILED ; SQLSTATE: HY000 Message: Failed to decrypt keyring file: %s. Error number: MY-015108 ; Symbol: ER_KEYRING_COMPONENT_KEYRING_FILE_INVALID_FORMAT ; SQLSTATE: HY000 Message: The keyring file content is not in a valid JSON format. Error number: MY-015109 ; Symbol: ER_KEYRING_COMPONENT_KEYRING_FILE_JSON_EXTRACT_FAILED ; SQLSTATE: HY000 Message: Failed to extract a valid JSON data from keyring file. Error number: MY-015110 ; Symbol: ER_KEYRING_COMPONENT_KEYRING_FILE_KEY_EXTRACT_FAILED ; SQLSTATE: HY000 Message: Failed to extract key from keyring file JSON data. Error number: MY-015111 ; Symbol: ER_NOTE_KEYRING_COMPONENT_NOT_INITIALIZED ; SQLSTATE: HY000 Message: Keyring component is not initialized. Error number: MY-015112 ; Symbol: ER_NOTE_KEYRING_COMPONENT_EMPTY_DATA_ID ; SQLSTATE: HY000 Message: Provided Data ID is empty. Error number: MY-015113 ; Symbol: ER_NOTE_KEYRING_COMPONENT_KEYS_METADATA_ITERATOR_INIT_FAILED ; SQLSTATE: HY000 Message: Failed to initialize metadata iterator. Error number: MY-015114 ; Symbol: ER_NOTE_KEYRING_COMPONENT_KEY_READ_ITERATOR_INIT_FAILED ; SQLSTATE: HY000 Message: Failed to initialize key reader iterator. Error number: MY-015115 ; Symbol: ER_NOTE_KEYRING_COMPONENT_KEY_READ_ITERATOR_FETCH_FAILED ; SQLSTATE: HY000 Message: Failed to read key from key reader iterator. Error number: MY-015118 ; Symbol: ER_AUTO_INCREMENT_NOT_SUPPORTED_FOR_FLOAT_DOUBLE ; SQLSTATE: HY000 Message: AUTO_INCREMENT is not supported with DOUBLE/FLOAT field. Please consider fixing (Schema:%s, Table:%s, Column:%s). Error number: MY-015122 ; Symbol: ER_KEYRING_MIGRATE_MEMORY_DEALLOCATION_FAILED ; SQLSTATE: HY000 Message: Failed to deallocate reader_object. Message: A connection from %s was closed by the server due to a timeout in the communication layer (vio:%d, packet:%d) %ld seconds after the last command started. Currently configured wait_timeout is %ld seconds. Error number: MY-015124 ; Symbol: ER_GRP_RPL_PREEMPTIVE_GARBAGE_COLLECTION_DIFF_FROM_GRP ; SQLSTATE: HY000 Message: The member is configured with a group_replication_preemptive_garbage_collection option value '%d' different from the group '%d'. The member will now exit the group. Message: Still rolling back transaction %llu; %llu undo records rolled back out of %llu total (%lu%% complete). Transaction info: last state: %s Error number: MY-015129 ; Symbol: ER_WARN_LOG_DEPRECATED_NON_STANDARD_KEY ; SQLSTATE: HY000 Message: Foreign key '%s' on table '%s'.'%s' refers to non-unique key or partial key. This is deprecated and will be removed in a future release. Error number: MY-015132 ; Symbol: ER_LOG_PARTITION_PREFIX_KEY_NOT_SUPPORTED ; SQLSTATE: HY000 Message: Column '%s.%s.%s' having prefix key part '%s(%u)' in the PARTITION BY KEY() clause is not supported. Error number: MY-015134 ; Symbol: ER_ACCESS_DENIED_NO_PROXY_GRANT_WITH_NAME ; SQLSTATE: HY000 Message: Access denied for user '%s'@'%s', missing proxy privilege to '%s'. Error number: MY-015136 ; Symbol: ER_GRP_RPL_RECOVERY_WAIT_APPLIER_BACKLOG_START ; SQLSTATE: HY000 Message: Distributed recovery will wait until the transactions '%s' contained on the 'group_replication_applier' channel are applied. Error number: MY-015137 ; Symbol: ER_GRP_RPL_RECOVERY_WAIT_APPLIER_BACKLOG_FINISH ; SQLSTATE: HY000 Message: Distributed recovery finished applying the transactions '%s' contained on the 'group_replication_applier' channel. Error number: MY-015142 ; Symbol: ER_LOG_DEPRECATE_NON_COMPOSABLE_MULTIPLE_ENGINE ; SQLSTATE: HY000 Message: Combining the storage engines %s and %s is deprecated, but the statement or transaction updates both the %s table %s.%s and the %s table %s.%s. ER_LOG_DEPRECATE_NON_COMPOSABLE_MULTIPLE_ENGINE was added in 8.4.1. Message: Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown ER_DD_UPDATE_DATADIR_FLAG_FAIL was added in 8.4.1. Message: %s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORY ER_IB_MSG_FIL_STATE_MOVED_PREV was added in 8.4.1.