# Copyright (c) 2017, 2024, Oracle and/or its affiliates.
# Copyright (c) 2023, 2025, GreatDB Software Co., Ltd.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License, version 2.0,
# as published by the Free Software Foundation.
#
# This program is designed to work with certain software (including
# but not limited to OpenSSL) that is licensed under separate terms,
# as designated in a particular file or component or in included license
# documentation.  The authors of MySQL hereby grant you an additional
# permission to link the program and your derivative works with the
# separately licensed software that they have either included with
# the program or referenced in the documentation.
#
# Without limiting anything contained in the foregoing, this file,
# which is part of C Driver for MySQL (Connector/C), is also subject to the
# Universal FOSS Exception, version 1.0, a copy of which can be found at
# http://oss.oracle.com/licenses/universal-foss-exception.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License, version 2.0, for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301  USA

################################################################################
# DO NOT add server-to-client messages here;
# they go in messages_to_clients.txt
# in the same directory as this file.
#
# This file is for messages intended for the error log only.
#
# See the FAQ in errmsg_readme.txt in the
# same directory as this file for more
# information.
################################################################################


# "languages" and "default-language" directives should not be set in this
# file; their values are carried over from messages_to_clients.txt.


################################################################################
#
# Start of 8.0 error messages (error log).
#
# The build process automatically starts with this offset
# for messages intended for the error-log. Setting it again
# here would be harmless; changing it would not as this
# offset is mentioned in the documentation and #defined in
# the source:
# start-error-number 10000

ER_PARSER_TRACE XX999
  eng "Parser saw: %s"
  chinese "解析器看到: %s"

ER_BOOTSTRAP_CANT_THREAD
  eng "Can't create thread to handle bootstrap (errno: %d)"
  chinese "无法创建处理引导程序的线程(错误代码: %d)"

ER_TRIGGER_INVALID_VALUE
  eng "Trigger for table '%s'.'%s': invalid %s value (%s)."
  chinese "表'%s'.'%s'的触发器: 无效的%s值(%s)。"

ER_OPT_WRONG_TREE
  eng "Wrong tree: %s"
  chinese "错误的树:%s"

ER_DD_FAILSAFE
  eng "Error: Invalid %s"
  chinese "错误:无效%s"

ER_DD_NO_WRITES_NO_REPOPULATION
  eng "Skip re-populating collations and character sets tables in %s%sread-only mode."
  chinese "跳过在%s%s只读模式下重新填充排序规则和字符集表。"

ER_DD_VERSION_FOUND
  eng "Using data dictionary with version '%d'."
  chinese "使用版本为'%d'的数据字典。"

ER_DD_VERSION_INSTALLED
  eng "Installed data dictionary with version %d"
  chinese "已安装版本为%d的数据字典"

ER_DD_VERSION_UNSUPPORTED
  eng "Data Dictionary version '%d' not supported."
  chinese "不支持数据字典版本'%d'。"

OBSOLETE_ER_LOG_SYSLOG_FACILITY_FAIL
  eng "Failed to set syslog facility to \"%s\", setting to \"%s\" (%d) instead."
  chinese "无法将系统日志工具设置为\"%s\",将设置为\"%s\"(%d)。"

ER_LOG_SYSLOG_CANNOT_OPEN
  eng "Cannot open %s; check privileges, or remove syseventlog from --log-error-services!"
  chinese "无法打开%s；请检查权限,或从--log-error-services中删除系统日志！"

ER_LOG_SLOW_CANNOT_OPEN
  eng " either restart the query logging by using \"SET GLOBAL SLOW_QUERY_LOG=ON\" or"
  chinese "使用\"SET GLOBAL LOW_QUERY_LOG=ON\"重新启动查询日志记录或"

ER_LOG_GENERAL_CANNOT_OPEN
  eng " either restart the query logging by using \"SET GLOBAL GENERAL_LOG=ON\" or"
  chinese "使用\"SET GLOBAL_LOG=ON\"重新启动查询日志记录或"

ER_LOG_CANNOT_WRITE
  eng "Failed to write to %s: %s"
  chinese "写入%s失败:%s"

OBSOLETE_ER_RPL_ZOMBIE_ENCOUNTERED
  eng "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)."
  chinese "初始化从属%s<%s>的转储线程时,发现具有相同%s的僵尸转储线程。主机正在终止僵尸转储线程(%u)。"

ER_RPL_GTID_TABLE_CANNOT_OPEN
  eng "Gtid table is not ready to be used. Table '%s.%s' cannot be opened."
  chinese "GTID表尚未准备好使用。表'%s.%s'无法打开。"

ER_SYSTEM_SCHEMA_NOT_FOUND
  eng "System schema directory does not exist."
  chinese "系统架构目录不存在。"

ER_DD_INIT_UPGRADE_FAILED
  eng "Error in initializing dictionary, upgrade will do a cleanup and exit"
  chinese "初始化词典时出错,升级将进行清理并退出"

ER_VIEW_UNKNOWN_CHARSET_OR_COLLATION
  eng "View '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s')."
  chinese "查看'%s'。'%s':未知的字符集名称和/或排序规则名称(客户端:'%s'；连接:'%s')。"

ER_DD_VIEW_CANT_ALLOC_CHARSET
  eng "Error in allocating memory for character set name for view %s.%s."
  chinese "为视图%s.%s的字符集名称分配内存时出错。"

ER_DD_INIT_FAILED
  eng "Data Dictionary initialization failed."
  chinese "数据字典初始化失败。"

ER_DD_UPDATING_PLUGIN_MD_FAILED
  eng "Failed to update plugin metadata in dictionary tables."
  chinese "无法更新字典表中的插件元数据。"

OBSOLETE_ER_DD_POPULATING_TABLES_FAILED
  eng "Failed to Populate DD tables."
  chinese "无法填充DD表。"

ER_DD_VIEW_CANT_CREATE
  eng "Error in Creating View %s.%s"
  chinese "创建视图%s.%s时出错。"

ER_DD_METADATA_NOT_FOUND
  eng "Unable to start server. Cannot find the meta data for data dictionary table '%s'."
  chinese "无法启动服务器。找不到数据字典表'%s'的元数据。"

ER_DD_CACHE_NOT_EMPTY_AT_SHUTDOWN
  eng "Dictionary cache not empty at shutdown."
  chinese "关闭时词典缓存不为空。"

ER_DD_OBJECT_REMAINS
  eng "Dictionary objects used but not released."
  chinese "已使用但未释放的字典对象。"

ER_DD_OBJECT_REMAINS_IN_RELEASER
  eng "Dictionary objects left in default releaser."
  chinese "字典对象留在默认释放程序中。"

ER_DD_OBJECT_RELEASER_REMAINS
  eng "Dictionary object auto releaser not deleted"
  chinese "未删除词典对象自动释放程序"

ER_DD_CANT_GET_OBJECT_KEY
  eng "Error: Unable to create primary object key"
  chinese "错误:无法创建主对象键"

ER_DD_CANT_CREATE_OBJECT_KEY
  eng "Error: Unable to create object key"
  chinese "错误:无法创建对象键"

ER_CANT_CREATE_HANDLE_MGR_THREAD
  eng "Can't create handle_manager thread (errno= %d)"
  chinese "无法创建HANDLE_MANAGER线程(错误号=%d)"

ER_RPL_REPO_HAS_GAPS
  eng "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."
  chinese "无法更改中继日志存储库的类型,因为存在有间隙的工作人员存储库。请先修复间隙,然后再进行此类更改。"

ER_INVALID_VALUE_FOR_ENFORCE_GTID_CONSISTENCY
  eng "option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF."
  chinese "选项'enforce-gtid-consistency':无法识别值'%s'。请将enforce-gtid-consistency设置为OFF。"

ER_CHANGED_ENFORCE_GTID_CONSISTENCY
  eng "Changed ENFORCE_GTID_CONSISTENCY from %s to %s."
  chinese "已将ENFORCE_GTID_CONSISTENMENT从%s更改为%s。"

ER_CHANGED_GTID_MODE
  eng "Changed GTID_MODE from %s to %s."
  chinese "将GTID_MODE从%s更改为%s。"

ER_DISABLED_STORAGE_ENGINE_AS_DEFAULT
  eng "%s is set to a disabled storage engine %s."
  chinese "%s设置为禁用的存储引擎%s。"

ER_DEBUG_SYNC_HIT
  eng "Debug sync points hit:                   %22s"
  chinese "调试同步点命中:%22s"

ER_DEBUG_SYNC_EXECUTED
  eng "Debug sync points executed:              %22s"
  chinese "已执行调试同步点:%22s"

ER_DEBUG_SYNC_THREAD_MAX
  eng "Debug sync points max active per thread: %22s"
  chinese "每个线程的调试同步点最大活动点数:%22s"

ER_DEBUG_SYNC_OOM
  eng "Debug Sync Facility disabled due to lack of memory."
  chinese "由于内存不足,调试同步工具已禁用。"

ER_CANT_INIT_TC_LOG
  eng "Can't init tc log"
  chinese "无法初始化TC日志"

ER_EVENT_CANT_INIT_QUEUE
  eng "Event Scheduler: Can't initialize the execution queue"
  chinese "事件计划程序:无法初始化执行队列"

ER_EVENT_PURGING_QUEUE
  eng "Event Scheduler: Purging the queue. %u events"
  chinese "事件计划程序:正在清除队列。%u个事件"

ER_EVENT_LAST_EXECUTION
  eng "Event Scheduler: Last execution of %s.%s. %s"
  chinese "事件计划程序:上次执行%s.%s.%s"

ER_EVENT_MESSAGE_STACK
  eng "%*s"
  chinese "%*s"

ER_EVENT_EXECUTION_FAILED
  eng "Event Scheduler: [%s].[%s.%s] event execution failed."
  chinese "事件计划程序:[%s].[%s.%s]事件执行失败。"

ER_CANT_INIT_SCHEDULER_THREAD
  eng "Event Scheduler: Cannot initialize the scheduler thread"
  chinese "事件计划程序:无法初始化计划程序线程"

ER_SCHEDULER_STOPPED
  eng "Event Scheduler: Stopped"
  chinese "事件计划程序:已停止"

ER_CANT_CREATE_SCHEDULER_THREAD
  eng "Event scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)"
  chinese "事件调度程序:无法启动调度程序,无法为事件调度程序创建线程(错误号=%d)"

ER_SCHEDULER_WAITING
  eng "Event Scheduler: Waiting for the scheduler thread to reply"
  chinese "事件计划程序:正在等待计划程序线程响应"

ER_SCHEDULER_STARTED
  eng "Event Scheduler: scheduler thread started with id %u"
  chinese "事件计划程序:计划程序线程以ID%u启动"

ER_SCHEDULER_STOPPING_FAILED_TO_GET_EVENT
  eng "Event Scheduler: Serious error during getting next event to execute. Stopping"
  chinese "事件计划程序:获取要执行的下一个事件时出现严重错误。正在停止"

ER_SCHEDULER_STOPPING_FAILED_TO_CREATE_WORKER
  eng "Event_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event scheduler"
  chinese "EVENT_SCHEDULER::EXECUTE_TOP:无法创建事件工作线程(错误号=%d)。正在停止事件调度程序"

ER_SCHEDULER_KILLING
  eng "Event Scheduler: Killing the scheduler thread, thread id %u"
  chinese "事件计划程序:正在终止计划程序线程,线程ID%u"

ER_UNABLE_TO_RESOLVE_IP
  eng "IP address '%s' could not be resolved: %s"
  chinese "无法解析IP地址'%s':%s"

ER_UNABLE_TO_RESOLVE_HOSTNAME
  eng "Host name '%s' could not be resolved: %s"
  chinese "无法解析主机名'%s':%s"

ER_HOSTNAME_RESEMBLES_IPV4
  eng "IP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself."
  chinese "IP地址'%s'已解析为主机名'%s',该名称与IPv4地址本身相似。"

ER_HOSTNAME_DOESNT_RESOLVE_TO
  eng "Hostname '%s' does not resolve to '%s'."
  chinese "主机名'%s'未解析为'%s'。"

ER_ADDRESSES_FOR_HOSTNAME_HEADER
  eng "Hostname '%s' has the following IP addresses:"
  chinese "主机名'%s'具有以下IP地址:"

ER_ADDRESSES_FOR_HOSTNAME_LIST_ITEM
  eng " - %s"
  chinese " - %s"

ER_TRG_WITHOUT_DEFINER
  eng "Definer clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer."
  chinese "表%s的触发器中缺少Definer子句。请重新生成触发器以修复定义器。"

ER_TRG_NO_CLIENT_CHARSET
  eng "Client character set is missing for trigger of table %s. Using default character set."
  chinese "表%s的触发器缺少客户端字符集。使用默认字符集。"

ER_PARSING_VIEW
  eng "Error in parsing view %s.%s"
  chinese "分析视图%s.%s时出错。"

ER_COMPONENTS_INFRASTRUCTURE_BOOTSTRAP
  eng "Failed to bootstrap components infrastructure."
  chinese "无法引导组件基础结构。"

ER_COMPONENTS_INFRASTRUCTURE_SHUTDOWN
  eng "Failed to shutdown components infrastructure."
  chinese "无法关闭组件基础结构。"

ER_COMPONENTS_PERSIST_LOADER_BOOTSTRAP
  eng "Failed to bootstrap persistent components loader."
  chinese "无法引导永久组件加载器。"

ER_DEPART_WITH_GRACE
  eng "Giving %d client threads a chance to die gracefully"
  chinese "给%d个客户端线程一个优雅地死掉的机会"

ER_CA_SELF_SIGNED
  eng "CA certificate %s is self signed."
  chinese "CA证书%s是自签名的。"

ER_SSL_LIBRARY_ERROR
  eng "Failed to set up SSL because of the following SSL library error: %s"
  chinese "由于以下SSL库错误,无法设置SSL:%s"

ER_NO_THD_NO_UUID
  eng "Failed to generate a server UUID because it is failed to allocate the THD."
  chinese "无法生成服务器UUID,因为它无法分配THD。"

ER_UUID_SALT
  eng "Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, "
  chinese "正在存储UUID生成器变量,CURRENT_PID:%lu,SERVER_START_TIME:%lu,已发送字节:%llu,"

ER_UUID_IS
  eng "Generated uuid: '%s', server_start_time: %lu, bytes_sent: %llu"
  chinese "生成的UUID:'%s',服务器启动时间:%lu,发送的字节数:%llu"

ER_UUID_INVALID
  eng "The server_uuid stored in auto.cnf file is not a valid UUID."
  chinese "存储在au.cnf文件中的SERVER_UUID不是有效的UUID。"

ER_UUID_SCRUB
  eng "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. "
  chinese "在Auto.cnf文件中的SERVER_UUID值的末尾找到垃圾字符。它的长度应该是'%d'(UUID_LENGTH)。请清除它并重新启动服务器。"

ER_CREATING_NEW_UUID
  eng "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."
  chinese "未找到现有的UUID,因此我们假定这是该服务器首次启动。正在生成新的UUID:%s。"

ER_CANT_CREATE_UUID
  eng "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."
  chinese "服务器的UUID初始化失败,因为无法从au.cnf文件中读取它。如果这是新服务器,则初始化失败,因为无法生成新的UUID。"

ER_UNKNOWN_UNSUPPORTED_STORAGE_ENGINE
  eng "Unknown/unsupported storage engine: %s"
  chinese "未知/不受支持的存储引擎:%s"

ER_SECURE_AUTH_VALUE_UNSUPPORTED
  eng "Unsupported value 0 for secure-auth"
  chinese "secure-auth的值0不受支持"

ER_INVALID_INSTRUMENT
  eng "Invalid instrument name or value for performance_schema_instrument '%s'."
  chinese "PERFORMANCE_SCHEMA_INVALUMENT'%s'的仪器名称或值无效。"

ER_INNODB_MANDATORY
  eng "The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored."
  chinese "从MySQL 5.7开始强制使用InnoDB。以前的选项,如'--Innodb=0/1/off/on'或'--Skip-Innodb'被忽略。"

OBSOLETE_ER_INNODB_CANNOT_BE_IGNORED
  eng "ignore-builtin-innodb is ignored and will be removed in future releases."
  chinese "Ignore-Builtin-Innodb将被忽略,并将在未来的版本中删除。"

OBSOLETE_ER_OLD_PASSWORDS_NO_MIDDLE_GROUND
  eng "Invalid old_passwords mode: 1. Valid values are 2 and 0"
  chinese "OLD_PASSWODS模式无效:1。有效值为2和0"

ER_VERBOSE_REQUIRES_HELP
  eng "--verbose is for use with --help; did you mean --log-error-verbosity?"
  chinese "--Verbose用于与--Help一起使用；您的意思是--log-error-verbosity吗？"

ER_POINTLESS_WITHOUT_SLOWLOG
  eng "options --log-slow-admin-statements, --log-queries-not-using-indexes, --log-slow-replica-statements and --log-query-errors have no effect if --slow-query-log is not set"
  chinese "如果未设置--low-Query-log,则选项--log-low-admin-Statements、--log-queries-Not-Using-index和--log-low-Replica-语句不起作用"

ER_WASTEFUL_NET_BUFFER_SIZE
  eng "net_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify."
  chinese "NET_BUFFER_LENGTH(%lu)设置为大于max_Allowed_Packet(%lu)。请更正。"

ER_DEPRECATED_TIMESTAMP_IMPLICIT_DEFAULTS
  eng "TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details)."
  chinese "不推荐使用隐式默认值的时间戳。请使用--EXPLICIT_DEFAULTS_FOR_TIMESTAMP服务器选项(有关详细信息,请参阅文档)。"

ER_FT_BOOL_SYNTAX_INVALID
  eng "Invalid ft-boolean-syntax string: %s"
  chinese "无效的ft布尔语法字符串:%s"

ER_CREDENTIALLESS_AUTO_USER_BAD
  eng "'NO_AUTO_CREATE_USER' sql mode was not set."
  chinese "未设置'NO_AUTO_CREATE_USER'SQL模式。"

ER_CONNECTION_HANDLING_OOM
  eng "Could not allocate memory for connection handling"
  chinese "无法为连接处理分配内存"

ER_THREAD_HANDLING_OOM
  eng "Could not allocate memory for thread handling"
  chinese "无法为线程处理分配内存"

ER_CANT_CREATE_TEST_FILE
  eng "Can't create test file %s"
  chinese "无法创建测试文件%s"

ER_CANT_CREATE_PID_FILE
  eng "Can't start server: can't create PID file: %s"
  chinese "无法启动服务器:无法创建PID文件:%s"

ER_CANT_REMOVE_PID_FILE
  eng "Unable to delete pid file: %s"
  chinese "无法删除PID文件:%s"

ER_CANT_CREATE_SHUTDOWN_THREAD
  eng "Can't create thread to handle shutdown requests (errno= %d)"
  chinese "无法创建线程来处理关闭请求(错误号=%d)"

ER_SEC_FILE_PRIV_CANT_ACCESS_DIR
  eng "Failed to access directory for --%s. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %s"
  chinese "无法访问--%s的目录。请确保该目录存在并且可以由MySQL服务器访问。提供的值:%s"

ER_SEC_FILE_PRIV_IGNORED
  eng "Ignoring --%s value as server is running with --initialize(-insecure)."
  chinese "忽略--%s值,因为服务器正在使用--INSIGNALE(-INSECURE)运行。"

ER_SEC_FILE_PRIV_EMPTY
  eng "Insecure configuration for --%s: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path."
  chinese "--%s:当前值的不安全配置不限制生成的文件的位置。请考虑将其设置为有效的非空路径。"

ER_SEC_FILE_PRIV_NULL
  eng "--%s is set to NULL. Operations related to importing and exporting data are disabled"
  chinese "--%s设置为NULL。与导入和导出数据相关的操作被禁用"

ER_SEC_FILE_PRIV_DIRECTORY_INSECURE
  eng "Insecure configuration for --%s: %s is accessible through --%s. Consider choosing a different directory."
  chinese "--%s:%s的不安全配置可通过--%s访问。请考虑选择其他目录。"

ER_SEC_FILE_PRIV_CANT_STAT
  eng "Failed to get stat for directory pointed out by --%s"
  chinese "无法获取--%s指出的目录的统计信息"

ER_SEC_FILE_PRIV_DIRECTORY_PERMISSIONS
  eng "Insecure configuration for --%s: Location is accessible to all OS users. Consider choosing a different directory."
  chinese "所有OS用户都可以访问--%s:位置的不安全配置。请考虑选择其他目录。"

ER_SEC_FILE_PRIV_ARGUMENT_TOO_LONG
  eng "Value for --%s is longer than maximum limit of %d"
  chinese "--%s的值长于最大限制%d"

ER_CANT_CREATE_NAMED_PIPES_THREAD
  eng "Can't create thread to handle named pipes (errno= %d)"
  chinese "无法创建线程来处理命名管道(错误号=%d)"

ER_CANT_CREATE_TCPIP_THREAD
  eng "Can't create thread to handle TCP/IP (errno= %d)"
  chinese "无法创建线程来处理TCP/IP(错误号=%d)"

ER_CANT_CREATE_SHM_THREAD
  eng "Can't create thread to handle shared memory (errno= %d)"
  chinese "无法创建线程来处理共享内存(错误号=%d)"

ER_CANT_CREATE_INTERRUPT_THREAD
  eng "Can't create interrupt-thread (error %d, errno: %d)"
  chinese "无法创建中断线程(错误%d,错误号:%d)"

ER_WRITABLE_CONFIG_REMOVED
  eng "World-writable config file '%s' has been removed."
  chinese "全局可写配置文件'%s'已被删除。"

ER_CORE_VALUES
  eng "setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signals"
  chinese "setrlimit无法将核心文件的大小更改为'infinity'；我们可能无法生成有关信号的核心文件"

ER_WRONG_DATETIME_SPEC
  eng "Wrong date/time format specifier: %s"
  chinese "错误的日期/时间格式说明符:%s"

ER_RPL_BINLOG_FILTERS_OOM
  eng "Could not allocate replication and binlog filters: %s"
  chinese "无法分配复制和binlog筛选器:%s"

ER_KEYCACHE_OOM
  eng "Cannot allocate the keycache"
  chinese "无法分配密钥缓存"

ER_CONFIRMING_THE_FUTURE
  eng "Current time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process."
  chinese "当前时间已超过2038年。在启动正常的服务器关闭过程之前,正在使用%d次迭代验证当前时间。"

ER_BACK_IN_TIME
  eng "Iteration %d: Obtained valid current time from system"
  chinese "迭代%d:从系统获取有效的当前时间"

ER_FUTURE_DATE
  eng "Iteration %d: Current time obtained from system is greater than 2038"
  chinese "迭代%d:从系统获取的当前时间大于2038"

ER_UNSUPPORTED_DATE
  eng "This MySQL server doesn't support dates later then 2038"
  chinese "此MySQL服务器不支持晚于2038的日期"

ER_STARTING_AS
  eng "%s (mysqld %s) starting as process %lu"
  chinese "%s(mysqld %s)作为进程%lu启动"

ER_SHUTTING_DOWN_REPLICA_THREADS
  eng "Shutting down replica threads"
  chinese "正在关闭从属线程"

ER_DISCONNECTING_REMAINING_CLIENTS
  eng "Forcefully disconnecting %d remaining clients"
  chinese "正在强制断开%d个剩余客户端的连接"

ER_ABORTING
  eng "Aborting"
  chinese "正在中止"

ER_BINLOG_END
  eng "Binlog end"
  chinese "Binlog 结束"

ER_CALL_ME_LOCALHOST
  eng "gethostname failed, using '%s' as hostname"
  chinese "获取主机名失败,使用'%s'作为主机名"

ER_USER_REQUIRES_ROOT
  eng "One can only use the --user switch if running as root"
  chinese "如果以超级用户身份运行,则只能使用--USER开关"

ER_REALLY_RUN_AS_ROOT
  eng "Fatal error: Please read \"Security\" section of the manual to find out how to run mysqld as root!"
  chinese "致命错误:请阅读手册的\"安全\"部分,以了解如何以超级用户身份运行mysqld！"

ER_USER_WHAT_USER
  eng "Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!"
  chinese "致命错误:无法更改为以用户'%s'的身份运行；请检查该用户是否存在！"

ER_TRANSPORTS_WHAT_TRANSPORTS
  eng "Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured."
  chinese "服务器启动时启用了--REQUIRED-SECURE-TRANSPORT=ON,但未配置安全传输(SSL或共享内存)。"

ER_FAIL_SETGID
  eng "setgid: %s"
  chinese "setgid: %s"

ER_FAIL_SETUID
  eng "setuid: %s"
  chinese "setuid: %s"

ER_FAIL_SETREGID
  eng "setregid: %s"
  chinese "setregid: %s"

ER_FAIL_SETREUID
  eng "setreuid: %s"
  chinese "setreuid: %s"

ER_FAIL_CHROOT
  eng "chroot: %s"
  chinese "chroot: %s"

ER_WIN_LISTEN_BUT_HOW
  eng "TCP/IP, --shared-memory, or --named-pipe should be configured on NT OS"
  chinese "应在NT OS上配置TCP/IP、--共享内存或--命名管道"

ER_NOT_RIGHT_NOW
  eng "CTRL-C ignored during startup"
  chinese "启动期间忽略CTRL-C"

ER_FIXING_CLIENT_CHARSET
  eng "'%s' can not be used as client character set. '%s' will be used as default client character set."
  chinese "'%s'不能用作客户端字符集。'%s'将用作默认客户端字符集。"

ER_OOM
  eng "Out of memory"
  chinese "内存不足"

ER_FAILED_TO_LOCK_MEM
  eng "Failed to lock memory. Errno: %d"
  chinese "无法锁定内存。错误号:%d"

ER_MYINIT_FAILED
  eng "my_init() failed."
  chinese "my_init()失败。"

ER_BEG_INITFILE
  eng "Execution of init_file \'%s\' started."
  chinese "已开始执行init_file \'%s\'。"

ER_END_INITFILE
  eng "Execution of init_file \'%s\' ended."
  chinese "init_file \'%s\'的执行结束。"

ER_CHANGED_MAX_OPEN_FILES
  eng "Changed limits: max_open_files: %lu (requested %lu)"
  chinese "更改限制:MAX_OPEN_FILES:%lu(请求%lu)"

ER_CANT_INCREASE_MAX_OPEN_FILES
  eng "Could not increase number of max_open_files to more than %lu (request: %lu)"
  chinese "无法将max_open_files的数量增加到%lu以上(请求:%lu)"

ER_CHANGED_MAX_CONNECTIONS
  eng "Changed limits: max_connections: %lu (requested %lu)"
  chinese "更改限制:Max_Connections:%lu(请求%lu)"

ER_CHANGED_TABLE_OPEN_CACHE
  eng "Changed limits: table_open_cache: %lu (requested %lu)"
  chinese "更改限制:TABLE_OPEN_CACHE:%lu(请求%lu)"

ER_THE_USER_ABIDES
  eng "Ignoring user change to '%s' because the user was set to '%s' earlier on the command line"
  chinese "正在忽略对'%s'的用户更改,因为该用户先前在命令行中被设置为'%s'"

ER_RPL_CANT_ADD_DO_TABLE
  eng "Could not add do table rule '%s'!"
  chinese "无法添加DO表规则'%s'！"

ER_RPL_CANT_ADD_IGNORE_TABLE
  eng "Could not add ignore table rule '%s'!"
  chinese "无法添加忽略表规则'%s'！"

ER_TRACK_VARIABLES_BOGUS
  eng "The variable session_track_system_variables either has duplicate values or invalid values."
  chinese "变量SESSION_TRACK_SYSTEM_Variables具有重复值或无效值。"

ER_EXCESS_ARGUMENTS
  eng "Too many arguments (first extra is '%s')."
  chinese "参数太多(第一个额外参数是'%s')。"

ER_VERBOSE_HINT
  eng "Use --verbose --help to get a list of available options!"
  chinese "使用--Verbose--Help获取可用选项列表！"

ER_CANT_READ_ERRMSGS
  eng "Unable to read errmsg.sys file"
  chinese "无法读取errmsg.sys文件"

ER_CANT_INIT_DBS
  eng "Can't init databases"
  chinese "无法初始化数据库"

ER_LOG_OUTPUT_CONTRADICTORY
  eng "There were other values specified to log-output besides NONE. Disabling slow and general logs anyway."
  chinese "除了NONE之外,还有其他指定给日志输出的值。仍要禁用慢速日志和常规日志。"

ER_NO_CSV_NO_LOG_TABLES
  eng "CSV engine is not present, falling back to the log files"
  chinese "CSV引擎不存在,正在回退到日志文件"

ER_RPL_REWRITEDB_MISSING_ARROW
  eng "Bad syntax in replicate-rewrite-db - missing '->'!"
  chinese "REPLICATE-REWRITE-DB - 丢失'->'的语法错误！"

ER_RPL_REWRITEDB_EMPTY_FROM
  eng "Bad syntax in replicate-rewrite-db - empty FROM db!"
  chinese "REPLICATE-REWRITE-db中的语法错误,db中为空！"

ER_RPL_REWRITEDB_EMPTY_TO
  eng "Bad syntax in replicate-rewrite-db - empty TO db!"
  chinese "REPLICATE-REWRITE-db中的语法错误,空为db！"

ER_LOG_FILES_GIVEN_LOG_OUTPUT_IS_TABLE
  eng "Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option."
  chinese "虽然为%s指定了路径,但仍使用日志表。要启用到文件的日志记录,请使用--log-out=FILE选项。"

ER_LOG_FILE_INVALID
  eng "Invalid value for %s: %s"
  chinese "%s的值无效:%s"

ER_LOWER_CASE_TABLE_NAMES_CS_DD_ON_CI_FS_UNSUPPORTED
  eng "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."
  chinese "服务器选项'LOWER_CASE_TABLE_NAMES'配置为使用区分大小写的表名称,但数据目录位于不区分大小写的文件系统上,这是不受支持的组合。请考虑对数据目录使用区分大小写的文件系统,或切换到不区分大小写的表名模式。"

ER_LOWER_CASE_TABLE_NAMES_USING_2
  eng "Setting lower_case_table_names=2 because file system for %s is case insensitive"
  chinese "正在设置LOWER_CASE_TABLE_NAMES=2,因为%s的文件系统不区分大小写"

ER_LOWER_CASE_TABLE_NAMES_USING_0
  eng "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."
  chinese "LOWER_CASE_TABLE_NAMES设置为2,即使您的文件系统'%s'区分大小写。现在将LOWER_CASE_TABLE_NAMES设置为0以避免将来出现问题。"

ER_NEED_LOG_BIN
  eng "You need to use --log-bin to make %s work."
  chinese "您需要使用--log-bin才能使%s工作。"

ER_NEED_FILE_INSTEAD_OF_DIR
  eng "Path '%s' is a directory name, please specify a file name for %s option"
  chinese "路径'%s'是目录名,请为%s选项指定文件名"

# Unused since MySQL 8.0.3
ER_LOG_BIN_BETTER_WITH_NAME
  eng "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."
  chinese "没有为--log-bin提供参数,也没有使用--log-bin-index；因此,当此MySQL服务器充当主服务器并更改其主机名时,复制可能会中断！！请使用'--log-bin=%s'来避免此问题。"

ER_BINLOG_NEEDS_SERVERID
  eng "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"
  chinese "您已启用二进制日志,但尚未提供必需的服务器ID。请参阅正确的服务器启动参数文档"

ER_RPL_CANT_MAKE_PATHS
  eng "Unable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d)."
  chinese "无法创建复制路径名:内存不足或路径名太长(路径名超过%d或文件名超过%d)。"

ER_CANT_INITIALIZE_GTID
  eng "Failed to initialize GTID structures."
  chinese "无法初始化GTID结构。"

ER_CANT_INITIALIZE_EARLY_PLUGINS
  eng "Failed to initialize early plugins."
  chinese "无法初始化早期插件。"

ER_CANT_INITIALIZE_BUILTIN_PLUGINS
  eng "Failed to initialize builtin plugins."
  chinese "无法初始化内置插件。"

ER_CANT_INITIALIZE_DYNAMIC_PLUGINS
  eng "Failed to initialize dynamic plugins."
  chinese "无法初始化动态插件。"

ER_PERFSCHEMA_INIT_FAILED
  eng "Performance schema disabled (reason: init failed)."
  chinese "性能架构已禁用(原因:初始化失败)。"

ER_STACKSIZE_UNEXPECTED
  eng "Asked for %lu thread stack, but got %ld"
  chinese "请求%lu线程堆栈,但获得%ld"

OBSOLETE_ER_CANT_SET_DATADIR
  eng "failed to set datadir to %s"
  chinese "无法将数据目录设置为%s"

ER_CANT_STAT_DATADIR
  eng "Can't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/group"
  chinese "无法读取数据目录的统计信息(%d):%s。假定它不属于同一用户/组"

ER_CANT_CHOWN_DATADIR
  eng "Can't change data directory owner to %s"
  chinese "无法将数据目录所有者更改为%s"

ER_CANT_SET_UP_PERSISTED_VALUES
  eng "Setting persistent options failed."
  chinese "设置永久选项失败。"

ER_CANT_SAVE_GTIDS
  eng "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."
  chinese "在服务器关闭时,无法将上一个二进制日志的全局事务标识符集保存到mysql.gtid_Executed表中。下次重新启动服务器时,将再次尝试将全局事务标识符保存到表中。"

OBSOLETE_ER_AUTH_CANT_SET_DEFAULT_PLUGIN
  eng "Can't start server: Invalid value for --default-authentication-plugin"
  chinese "无法启动服务器:--default-authentication-plugin的值无效"

ER_CANT_JOIN_SHUTDOWN_THREAD
  eng "Could not join %sthread. error:%d"
  chinese "无法联接%shad。错误:%d"

ER_CANT_HASH_DO_AND_IGNORE_RULES
  eng "An error occurred while building do_table and ignore_table rules to hashes for global replication filter."
  chinese "为全局复制筛选器的哈希构建DO_TABLE和IGNORE_TABLE规则时出错。"

ER_CANT_OPEN_CA
  eng "Error opening CA certificate file"
  chinese "打开CA证书文件时出错"

ER_CANT_ACCESS_CAPATH
  eng "Error accessing directory pointed by --ssl-capath"
  chinese "访问--ssl-capath指向的目录时出错"

ER_SSL_TRYING_DATADIR_DEFAULTS
  eng "Found %s, %s and %s in data directory. Trying to enable SSL support using them."
  chinese "在数据目录中找到%s、%s和%s。正在尝试使用它们启用SSL支持。"

ER_AUTO_OPTIONS_FAILED
  eng "Failed to create %s(file: '%s', errno %d)"
  chinese "无法创建%s(文件:'%s',错误号%d)"

ER_CANT_INIT_TIMER
  eng "Failed to initialize timer component (errno %d)."
  chinese "无法初始化计时器组件(错误号%d)。"

ER_SERVERID_TOO_LARGE
  eng "server-id configured is too large to represent with server-id-bits configured."
  chinese "配置的服务器ID太大,无法使用配置的服务器ID位表示。"

ER_DEFAULT_SE_UNAVAILABLE
  eng "Default%s storage engine (%s) is not available"
  chinese "默认%s存储引擎(%s)不可用"

ER_CANT_OPEN_ERROR_LOG
  eng "Could not open file '%s' for error logging%s%s"
  chinese "无法打开文件'%s'以记录错误%s%s"

ER_INVALID_ERROR_LOG_NAME
  eng "Invalid log file name after expanding symlinks: '%s'"
  chinese "展开符号链接后,日志文件名无效:'%s'"

ER_RPL_INFINITY_DENIED
  eng "using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server."
  chinese "将--REPLICATE-SAME-SERVER-ID与--LOG-REPLICATE-UPDATES一起使用是不可能的,这将导致此服务器中出现无限循环。"

ER_RPL_INFINITY_IGNORED
  eng "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."
  chinese "将--REPLICATE-Same-SERVER-ID与--LOG-REPLICATE-UPDATE一起使用将导致此服务器中出现无限循环。但是,这将被忽略,因为未定义--LOG-bin选项,或者您的服务器正在运行时启用了全局事务标识符。"

OBSOLETE_ER_NDB_TABLES_NOT_READY
  eng "NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value"
  chinese "NDB:表在%lu秒后不可用。请考虑增加--NDB-WAIT-SETUP值"

# could use verbatim, but we want an error-code
ER_TABLE_CHECK_INTACT
  eng "%s"
  chinese "%s"

ER_DD_TABLESPACE_NOT_FOUND
  eng "Unable to start server. The data dictionary tablespace '%s' does not exist."
  chinese "无法启动服务器。数据字典表空间'%s'不存在。"

ER_DD_TRG_CONNECTION_COLLATION_MISSING
  eng "Connection collation is missing for trigger of table %s. Using default connection collation."
  chinese "表%s的触发器缺少连接排序规则。使用默认连接排序规则。"

ER_DD_TRG_DB_COLLATION_MISSING
  eng "Database collation is missing for trigger of table %s. Using Default character set."
  chinese "表%s的触发器缺少数据库排序规则。使用默认字符集。"

ER_DD_TRG_DEFINER_OOM
  eng "Error in Memory allocation for Definer %s for Trigger."
  chinese "触发器的定义器%s的内存分配错误。"

# ER_TRG_CORRUPTED_FILE
ER_DD_TRG_FILE_UNREADABLE
  eng "Error in reading %s.TRG file."
  chinese "读取%s.TRG文件时出错。"

ER_TRG_CANT_PARSE
  eng "Error in parsing Triggers from %s.TRG file."
  chinese "从%s.TRG文件解析触发器时出错。"

ER_DD_TRG_CANT_ADD
  eng "Error in creating DD entry for Trigger %s.%s"
  chinese "为触发器%s.%s创建DD条目时出错。"

ER_DD_CANT_RESOLVE_VIEW
  eng "Resolving dependency for the view '%s.%s' failed. View is no more valid to use"
  chinese "解析视图'%s.%s'的依赖关系失败。视图不再有效,无法使用"

ER_DD_VIEW_WITHOUT_DEFINER
  eng "%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view."
  chinese "解析视图'%s.%s'的依赖关系失败。视图不再有效,无法使用"

ER_PLUGIN_INIT_FAILED
  eng "Plugin '%s' init function returned error."
  chinese "插件'%s'初始化函数返回错误。"

ER_RPL_TRX_DELEGATES_INIT_FAILED
  eng "Initialization of transaction delegates failed. Please report a bug."
  chinese "事务委托初始化失败。请报告错误。"

ER_RPL_BINLOG_STORAGE_DELEGATES_INIT_FAILED
  eng "Initialization binlog storage delegates failed. Please report a bug."
  chinese "初始化binlog存储委派失败。请报告错误。"

ER_RPL_BINLOG_TRANSMIT_DELEGATES_INIT_FAILED
  eng "Initialization of binlog transmit delegates failed. Please report a bug."
  chinese "初始化binlog传输委派失败。请报告错误。"

ER_RPL_BINLOG_RELAY_DELEGATES_INIT_FAILED
  eng "Initialization binlog relay IO delegates failed. Please report a bug."
  chinese "初始化binlog中继IO委派失败。请报告错误。"

ER_RPL_PLUGIN_FUNCTION_FAILED
  eng "Run function '...' in plugin '%s' failed"
  chinese "插件'%s'中的运行函数'...'失败"

ER_SQL_HA_READ_FAILED
  eng "mysql_ha_read: Got error %d when reading table '%s'"
  chinese "mySQL_ha_read:出现错误%d,读取表格'%s'时"

ER_SR_BOGUS_VALUE
  eng "Stored routine '%s'.'%s': invalid value in column %s."
  chinese "存储例程'%s'.'%s':列%s中的值无效。"

ER_SR_INVALID_CONTEXT
  eng "Invalid creation context '%s.%s'."
  chinese "无效的创建上下文'%s.%s'。"

ER_READING_TABLE_FAILED
  eng "Got error %d when reading table '%s'"
  chinese "出现错误%d读取表格%s时"

ER_DES_FILE_WRONG_KEY
  eng "load_des_file:  Found wrong key_number: %c"

OBSOLETE_ER_CANT_SET_PERSISTED
  eng "Failed to set persisted options."
  chinese "无法设置持久选项。"

ER_JSON_PARSE_ERROR
  eng "Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON."
  chinese "持久化配置文件已损坏。请确保mysqld-Auto.cnf文件是有效的JSON。"

ER_CONFIG_OPTION_WITHOUT_GROUP
  eng "Found option without preceding group in config file"
  chinese "在配置文件中找到没有前面组的选项"

ER_VALGRIND_DO_QUICK_LEAK_CHECK
  eng "VALGRIND_DO_QUICK_LEAK_CHECK"
  chinese "VALGRIND_DO_QUICK_LEAK_CHECK"

ER_VALGRIND_COUNT_LEAKS
  eng "VALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'"
  chinese "VALGRIND_COUNT_LEAKS报告%lu个查询'%.*s'泄漏的字节数"

ER_LOAD_DATA_INFILE_FAILED_IN_UNEXPECTED_WAY
  eng "LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug."
  chinese "从SQL线程中的LOAD DATA INFILE只能从--Replica-Load-tmpdir读取。请报告错误。"

ER_UNKNOWN_ERROR_NUMBER
  eng "Got unknown error: %d"
  chinese "收到未知错误:%d"

ER_UDF_CANT_ALLOC_FOR_STRUCTURES
  eng "Can't allocate memory for udf structures"
  chinese "无法为UDF结构分配内存"

ER_UDF_CANT_ALLOC_FOR_FUNCTION
  eng "Can't alloc memory for udf function: '%.64s'"
  chinese "无法为UDF函数分配内存:'%.64s'"

ER_UDF_INVALID_ROW_IN_FUNCTION_TABLE
  eng "Invalid row in mysql.func table for function '%.64s'"
  chinese "函数'%.64s'的mysql.func表中的行无效"

ER_UDF_CANT_OPEN_FUNCTION_TABLE
  eng "Could not open the mysql.func table. Please perform the MySQL upgrade procedure."
  chinese "无法打开mysql.func表。请执行MySQL升级过程。"

ER_XA_RECOVER_FOUND_TRX_IN_SE
  eng "Found %d prepared transaction(s) in %s"
  chinese "找到%d个已准备好的事务在%s中"

ER_XA_RECOVER_FOUND_XA_TRX
  eng "Found %d prepared XA transactions"
  chinese "找到%d个准备好的XA交易记录"

OBSOLETE_ER_XA_IGNORING_XID
  eng "ignore xid %s"
  chinese "忽略xid %s"

OBSOLETE_ER_XA_COMMITTING_XID
  eng "commit xid %s"
  chinese "提交xid %s"

OBSOLETE_ER_XA_ROLLING_BACK_XID
  eng "rollback xid %s"
  chinese "回滚xid %s"

ER_XA_STARTING_RECOVERY
  eng "Starting XA crash recovery..."
  chinese "正在启动XA崩溃恢复..."

ER_XA_NO_MULTI_2PC_HEURISTIC_RECOVER
  eng "--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery."
  chinese "--TC-Heuristic-Recover回滚策略在具有多个支持两阶段提交的存储引擎的系统上不安全。正在中止崩溃恢复。"

ER_XA_RECOVER_EXPLANATION
  eng "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."
  chinese "找到%d个已准备好的事务！这意味着上次没有正确关闭mysqld,关键恢复信息(最后一个binlog或%s文件)在崩溃后已被手动删除。您必须使用--TC-Heuristic-Recover开关启动mysqld才能提交或回滚挂起的事务。"

ER_XA_RECOVERY_DONE
  eng "XA crash recovery finished."
  chinese "XA崩溃恢复已完成。"

ER_TRX_GTID_COLLECT_REJECT
  eng "Failed to collect GTID to send in the response packet!"
  chinese "无法收集GTID以发送响应数据包！"

ER_SQL_AUTHOR_DEFAULT_ROLES_FAIL
  eng "MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %s"
  chinese "无法为授权标识符%s更新MYSQL.DEFAULT_ROLES"

ER_SQL_USER_TABLE_CREATE_WARNING
  eng "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"
  chinese "在CREATE USER中指定了下列用户(如果不存在但已存在)。二进制日志中的相应条目使用默认身份验证插件'%s'重写身份验证信息(如果有):%s"

ER_SQL_USER_TABLE_ALTER_WARNING
  eng "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"
  chinese "在ALTER USER中指定了下列用户(如果存在但不存在)。二进制日志中的相应条目使用默认身份验证插件'%s'来重写他们的身份验证信息(如果有):%s"

ER_ROW_IN_WRONG_PARTITION_PLEASE_REPAIR
  eng "Table '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!"
  chinese "表'%-192s'已损坏:错误分区中的行:%s--请修复该表！"

ER_MYISAM_CRASHED_ERROR_IN_THREAD
  eng "Got an error from thread_id=%u, %s:%d"
  chinese "从线程id=%u,%s:%d获取错误"

ER_MYISAM_CRASHED_ERROR_IN
  eng "Got an error from unknown thread, %s:%d"
  chinese "从未知线程%s:%d获取错误"

ER_TOO_MANY_STORAGE_ENGINES
  eng "Too many storage engines!"
  chinese "存储引擎太多了！"

ER_SE_TYPECODE_CONFLICT
  eng "Storage engine '%s' has conflicting typecode. Assigning value %d."
  chinese "存储引擎'%s'的类型代码冲突。正在分配值%d。"

ER_TRX_WRITE_SET_OOM
  eng "Out of memory on transaction write set extraction"
  chinese "事务写入集提取时内存不足"

ER_HANDLERTON_OOM
  eng "Unable to allocate memory for plugin '%s' handlerton."
  chinese "无法为插件'%s'处理程序分配内存。"

ER_CONN_SHM_LISTENER
  eng "Shared memory setting up listener"
  chinese "共享内存设置监听程序"

ER_CONN_SHM_CANT_CREATE_SERVICE
  eng "Can't create shared memory service: %s. : %s"
  chinese "无法创建共享内存服务:%s。错误:%s"

ER_CONN_SHM_CANT_CREATE_CONNECTION
  eng "Can't create shared memory connection: %s. : %s"
  chinese "无法创建共享内存连接:%s。错误:%s"

ER_CONN_PIP_CANT_CREATE_EVENT
  eng "Can't create event, last error=%u"
  chinese "无法创建事件,上一个错误=%u"

ER_CONN_PIP_CANT_CREATE_PIPE
  eng "Can't create new named pipe!: %s"
  chinese "无法创建新命名管道！:%s"

ER_CONN_PER_THREAD_NO_THREAD
  eng "Can't create thread to handle new connection(errno= %d)"
  chinese "无法创建线程来处理新连接(错误号=%d)"

ER_CONN_TCP_NO_SOCKET
  eng "Failed to create a socket for %s '%s': errno: %d."
  chinese "无法为%s '%s'创建套接字:错误号:%d。"

ER_CONN_TCP_CREATED
  eng "Server socket created on IP: '%s'."
  chinese "在IP上创建的服务器套接字:'%s'。"

ER_CONN_TCP_ADDRESS
  eng "Server hostname (bind-address): '%s'; port: %d"
  chinese "服务器主机名(绑定地址):'%s'；端口:%d"

ER_CONN_TCP_IPV6_AVAILABLE
  eng "IPv6 is available."
  chinese "IPv6是可用的。"

ER_CONN_TCP_IPV6_UNAVAILABLE
  eng "IPv6 is not available."
  chinese "IPv6不可用。"

ER_CONN_TCP_ERROR_WITH_STRERROR
  eng "Can't create IP socket: %s"
  chinese "无法创建IP套接字:%s"

ER_CONN_TCP_CANT_RESOLVE_HOSTNAME
  eng "Can't start server: cannot resolve hostname!"
  chinese "无法启动服务器:无法解析主机名！"

ER_CONN_TCP_IS_THERE_ANOTHER_USING_PORT
  eng "Do you already have another mysqld server running on port: %d ?"
  chinese "您是否已在端口%d上运行另一台mysqld服务器？"

ER_CONN_UNIX_IS_THERE_ANOTHER_USING_SOCKET
  eng "Do you already have another mysqld server running on socket: %s ?"
  chinese "您已经在套接字%s上运行了另一台mysqld服务器吗？"

ER_CONN_UNIX_PID_CLAIMED_SOCKET_FILE
  eng "Another process with pid %d is using unix socket file."
  chinese "另一个ID为%d的进程正在使用Unix套接字文件。"

ER_CONN_TCP_CANT_RESET_V6ONLY
  eng "Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only."
  chinese "无法重置IPv6_V6ONLY标志(错误:%d)。服务器将仅侦听IPv6地址。"

ER_CONN_TCP_BIND_RETRY
  eng "Retrying bind on TCP/IP port %u"
  chinese "正在重试在TCP/IP端口%u上绑定"

ER_CONN_TCP_BIND_FAIL
  eng "Can't start server: Bind on TCP/IP port: %s"
  chinese "无法启动服务器:在TCP/IP端口上绑定:%s"

ER_CONN_TCP_IP_NOT_LOGGED
  eng "Fails to print out IP-address."
  chinese "无法打印IP地址。"

ER_CONN_TCP_RESOLVE_INFO
  eng "  - '%s' resolves to '%s';"
  chinese "-'%s'解析为'%s'；"

ER_CONN_TCP_START_FAIL
  eng "Can't start server: listen() on TCP/IP port: %s"
  chinese "无法启动服务器:在TCP/IP端口上侦听:%s"

ER_CONN_TCP_LISTEN_FAIL
  eng "listen() on TCP/IP failed with error %d"
  chinese "在TCP/IP上的Listen()失败,错误为%d"

ER_CONN_UNIX_PATH_TOO_LONG
  eng "The socket file path is too long (> %u): %s"
  chinese "套接字文件路径太长(>%u):%s"

ER_CONN_UNIX_LOCK_FILE_FAIL
  eng "Unable to setup unix socket lock file."
  chinese "无法设置Unix套接字锁定文件。"

ER_CONN_UNIX_NO_FD
  eng "Can't start server: UNIX Socket : %s"
  chinese "无法启动服务器:Unix套接字:%s"

ER_CONN_UNIX_NO_BIND_NO_START
  eng "Can't start server : Bind on unix socket: %s"
  chinese "无法启动服务器:Unix套接字上的绑定:%s"

ER_CONN_UNIX_LISTEN_FAILED
  eng "listen() on Unix socket failed with error %d"
  chinese "Unix套接字上的Listen()失败,错误为%d"

ER_CONN_UNIX_LOCK_FILE_GIVING_UP
  eng "Unable to create unix socket lock file %s after retries."
  chinese "重试后无法创建Unix套接字锁定文件%s。"

ER_CONN_UNIX_LOCK_FILE_CANT_CREATE
  eng "Could not create unix socket lock file %s."
  chinese "无法创建Unix套接字锁定文件%s。"

ER_CONN_UNIX_LOCK_FILE_CANT_OPEN
  eng "Could not open unix socket lock file %s."
  chinese "无法打开Unix套接字锁定文件%s。"

ER_CONN_UNIX_LOCK_FILE_CANT_READ
  eng "Could not read unix socket lock file %s."
  chinese "无法读取Unix套接字锁定文件%s。"

ER_CONN_UNIX_LOCK_FILE_EMPTY
  eng "Unix socket lock file is empty %s."
  chinese "Unix套接字锁定文件为空%s。"

ER_CONN_UNIX_LOCK_FILE_PIDLESS
  eng "Invalid pid in unix socket lock file %s."
  chinese "Unix套接字锁定文件%s中的ID无效。"

ER_CONN_UNIX_LOCK_FILE_CANT_WRITE
  eng "Could not write unix socket lock file %s errno %d."
  chinese "无法写入Unix套接字锁定文件%s,错误号%d。"

ER_CONN_UNIX_LOCK_FILE_CANT_DELETE
  eng "Could not remove unix socket lock file %s errno %d."
  chinese "无法删除Unix套接字锁定文件%s,错误号%d。"

ER_CONN_UNIX_LOCK_FILE_CANT_SYNC
  eng "Could not sync unix socket lock file %s errno %d."
  chinese "无法同步Unix套接字锁定文件%s,错误号%d。"

ER_CONN_UNIX_LOCK_FILE_CANT_CLOSE
  eng "Could not close unix socket lock file %s errno %d."
  chinese "无法关闭Unix套接字锁定文件%s,错误号%d。"

ER_CONN_SOCKET_SELECT_FAILED
  eng "mysqld: Got error %d from select"
  chinese "mysqld:从SELECT中获取错误%d"

ER_CONN_SOCKET_ACCEPT_FAILED
  eng "Error in accept: %s"
  chinese "接受时出错:%s"

ER_AUTH_RSA_CANT_FIND
  eng "RSA %s key file not found: %s. Some authentication plugins will not work."
  chinese "找不到RSA%s密钥文件:%s。某些身份验证插件将无法工作。"

ER_AUTH_RSA_CANT_PARSE
  eng "Failure to parse RSA %s key (file exists): %s: %s"
  chinese "无法解析RSA%s密钥(文件存在):%s:%s"

ER_AUTH_RSA_CANT_READ
  eng "Failure to read key file: %s"
  chinese "无法读取密钥文件:%s"

ER_AUTH_RSA_FILES_NOT_FOUND
  eng "RSA key files not found. Some authentication plugins will not work."
  chinese "找不到RSA密钥文件。某些身份验证插件将无法工作。"

ER_CONN_ATTR_TRUNCATED
  eng "Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %s"
  chinese "长度为%lu的连接属性已被截断(丢失%d字节),用于连接%llu,用户%s@%s(作为%s),身份验证:%s"

ER_X509_CIPHERS_MISMATCH
  eng "X.509 ciphers mismatch: should be '%s' but is '%s'"
  chinese "X.509密码不匹配:应该是'%s',但却是'%s'"

ER_X509_ISSUER_MISMATCH
  eng "X.509 issuer mismatch: should be '%s' but is '%s'"
  chinese "X.509颁发者不匹配:应该是'%s',但却是'%s'"

ER_X509_SUBJECT_MISMATCH
  eng "X.509 subject mismatch: should be '%s' but is '%s'"
  chinese "X.509主题不匹配:应该是'%s',但却是'%s'"

ER_AUTH_CANT_ACTIVATE_ROLE
  eng "Failed to activate default role %s for %s"
  chinese "无法激活%s的默认角色%s"

ER_X509_NEEDS_RSA_PRIVKEY
  eng "Could not generate RSA private key required for X.509 certificate."
  chinese "无法生成X.509证书所需的RSA私钥。"

ER_X509_CANT_WRITE_KEY
  eng "Could not write key file: %s"
  chinese "无法写入密钥文件:%s"

ER_X509_CANT_CHMOD_KEY
  eng "Could not set file permission for %s"
  chinese "无法为%s设置文件权限"

ER_X509_CANT_READ_CA_KEY
  eng "Could not read CA key file: %s"
  chinese "无法读取CA密钥文件:%s"

ER_X509_CANT_READ_CA_CERT
  eng "Could not read CA certificate file: %s"
  chinese "无法读取CA证书文件:%s"

ER_X509_CANT_CREATE_CERT
  eng "Could not generate X.509 certificate."
  chinese "无法生成X.509证书。"

ER_X509_CANT_WRITE_CERT
  eng "Could not write certificate file: %s"
  chinese "无法写入证书文件:%s"

ER_AUTH_CANT_CREATE_RSA_PAIR
  eng "Could not generate RSA Private/Public key pair"
  chinese "无法生成RSA私钥/公钥对"

ER_AUTH_CANT_WRITE_PRIVKEY
  eng "Could not write private key file: %s"
  chinese "无法写入私钥文件:%s"

ER_AUTH_CANT_WRITE_PUBKEY
  eng "Could not write public key file: %s"
  chinese "无法写入公钥文件:%s"

ER_AUTH_SSL_CONF_PREVENTS_CERT_GENERATION
  eng "Skipping generation of SSL certificates as options related to SSL are specified."
  chinese "正在跳过生成SSL证书,因为指定了与SSL相关的选项。"

ER_AUTH_USING_EXISTING_CERTS
  eng "Skipping generation of SSL certificates as certificate files are present in data directory."
  chinese "跳过生成SSL证书,因为证书文件存在于数据目录中。"

ER_AUTH_CERTS_SAVED_TO_DATADIR
  eng "Auto generated SSL certificates are placed in data directory."
  chinese "自动生成的SSL证书放在数据目录中。"

ER_AUTH_CERT_GENERATION_DISABLED
  eng "Skipping generation of SSL certificates as --auto_generate_certs is set to OFF."
  chinese "跳过生成SSL证书,因为--AUTO_GENERATE_CERTS设置为OFF。"

ER_AUTH_RSA_CONF_PREVENTS_KEY_GENERATION
  eng "Skipping generation of RSA key pair through %s as options related to RSA keys are specified."
  chinese "正在跳过通过%s生成RSA密钥对,因为指定了与RSA密钥相关的选项。"

ER_AUTH_KEY_GENERATION_SKIPPED_PAIR_PRESENT
  eng "Skipping generation of RSA key pair through %s as key files are present in data directory."
  chinese "正在跳过通过%s生成RSA密钥对,因为数据目录中存在密钥文件。"

ER_AUTH_KEYS_SAVED_TO_DATADIR
  eng "Auto generated RSA key files through %s are placed in data directory."
  chinese "通过%s自动生成的RSA密钥文件放置在数据目录中。"

ER_AUTH_KEY_GENERATION_DISABLED
  eng "Skipping generation of RSA key pair as %s is set to OFF."
  chinese "由于%s设置为OFF,正在跳过RSA密钥对的生成。"

ER_AUTHCACHE_PROXIES_PRIV_SKIPPED_NEEDS_RESOLVE
  eng "'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode."
  chinese "'proxies_prv'条目'%s@%s %s@%s'在--skip-name-resolve模式中被忽略。"

ER_AUTHCACHE_PLUGIN_MISSING
  eng "The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account."
  chinese "插件'%.*s'未加载被用于验证用户'%s'@'%.*s'的。当前没有人可以使用此帐户登录。"

ER_AUTHCACHE_PLUGIN_CONFIG
  eng "The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account."
  chinese "插件'%s'用于验证用户'%s'@'%.*s',已配置%s。目前没有人可以使用此帐户登录。"

OBSOLETE_ER_AUTHCACHE_ROLE_TABLES_DODGY
  eng "Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed."
  chinese "无法加载mysql.Role_Edges和mysql.Default_Roles表。除非执行MySQL升级过程,否则ACL DDL将不起作用。"

ER_AUTHCACHE_USER_SKIPPED_NEEDS_RESOLVE
  eng "'user' entry '%s@%s' ignored in --skip-name-resolve mode."
  chinese "'用户'条目'%s@%s'在--skip-name-resolve模式下被忽略。"

ER_AUTHCACHE_USER_TABLE_DODGY
  eng "Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure."
  chinese "致命错误:无法从表'mysql.user'中读取列'AUTHENTICATION_STRING'。请执行MySQL升级过程。"

ER_AUTHCACHE_USER_IGNORED_DEPRECATED_PASSWORD
  eng "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."
  chinese "用户条目'%s'@'%s'的密码低于4.1版本。该用户将被忽略,任何人都不能再使用该用户登录。"

ER_AUTHCACHE_USER_IGNORED_NEEDS_PLUGIN
  eng "User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore."
  chinese "用户条目'%s'@'%s'的插件值为空。该用户将被忽略,任何人都不能再以该用户登录。"

ER_AUTHCACHE_USER_IGNORED_INVALID_PASSWORD
  eng "Found invalid password for user: '%s@%s'; Ignoring user"
  chinese "找到用户'%s@%s'的无效密码；忽略用户"

ER_AUTHCACHE_EXPIRED_PASSWORD_UNSUPPORTED
  eng "'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."
  chinese "'用户'条目'%s@%s'引发了密码忽略标志,但其身份验证插件不支持密码过期。用户ID将被忽略。"

ER_NO_SUPER_WITHOUT_USER_PLUGIN
  eng "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."
  chinese "由于mysql.user.plugin值为空,某些具有超级权限的用户帐户被禁用。如果您要从MySQL 5.6升级到MySQL 5.7,这意味着不可能替换空的插件列。可能是因为4.1之前的密码哈希。如果您的帐户被禁用,您将需要执行MySQL升级过程。有关如何将MySQL升级到新版本的完整说明,请参阅MySQL手册中的'升级MySQL'一节。"

ER_AUTHCACHE_DB_IGNORED_EMPTY_NAME
  eng "Found an entry in the 'db' table with empty database name; Skipped"
  chinese "在'db'表中找到数据库名称为空的条目；已跳过"

ER_AUTHCACHE_DB_SKIPPED_NEEDS_RESOLVE
  eng "'db' entry '%s %s@%s' ignored in --skip-name-resolve mode."
  chinese "'db'条目'%s %s@%s'在--skip-name-resolve模式中被忽略。"

ER_AUTHCACHE_DB_ENTRY_LOWERCASED_REVOKE_WILL_FAIL
  eng "'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."
  chinese "'db'条目'%s %s@%s'具有大小写混合的数据库,由于设置了LOWER_CASE_TABLE_NAMES,该数据库已被强制为小写。无法使用REVOKE删除此权限。"

ER_AUTHCACHE_TABLE_PROXIES_PRIV_MISSING
  eng "The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure."
  chinese "缺少系统表mysql.proxies_priv。请执行MySQL升级过程。"

ER_AUTHCACHE_CANT_OPEN_AND_LOCK_PRIVILEGE_TABLES
  eng "Fatal error: Can't open and lock privilege tables: %s"
  chinese "致命错误:无法打开和锁定特权表:%s"

ER_AUTHCACHE_CANT_INIT_GRANT_SUBSYSTEM
  eng "Fatal: can't initialize grant subsystem - '%s'"
  chinese "致命:无法初始化授予子系统-'%s'"

ER_AUTHCACHE_PROCS_PRIV_SKIPPED_NEEDS_RESOLVE
  eng "'procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode."
  chinese "'pros_prv'条目'%s %s@%s'在--跳过名称解析模式中被忽略。"

ER_AUTHCACHE_PROCS_PRIV_ENTRY_IGNORED_BAD_ROUTINE_TYPE
  eng "'procs_priv' entry '%s' ignored, bad routine type"
  chinese "'pros_prv'条目'%s'被忽略,错误的例程类型"

ER_AUTHCACHE_TABLES_PRIV_SKIPPED_NEEDS_RESOLVE
  eng "'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode."
  chinese "'TABLES_PRIV'条目'%s %s@%s'在--skip-name-resolve模式中被忽略。"

ER_USER_NOT_IN_EXTRA_USERS_BINLOG_POSSIBLY_INCOMPLETE
  eng "Failed to add %s in extra_users. Binary log entry may miss some of the users."
  chinese "无法在EXTRA_USERS中添加%s。二进制日志条目可能遗漏了某些用户。"

ER_DD_SCHEMA_NOT_FOUND
  eng "Unable to start server. The data dictionary schema '%s' does not exist."
  chinese "无法启动服务器。数据字典架构'%s'不存在。"

ER_DD_TABLE_NOT_FOUND
  eng "Unable to start server. The data dictionary table '%s' does not exist."
  chinese "无法启动服务器。数据字典表'%s'不存在。"

ER_DD_SE_INIT_FAILED
  eng "Failed to initialize DD Storage Engine"
  chinese "无法初始化DD存储引擎"

ER_DD_ABORTING_PARTIAL_UPGRADE
  eng "Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again."
  chinese "找到部分升级的DD。正在中止升级并删除所有DD表。重新开始升级过程。"

ER_DD_FRM_EXISTS_FOR_TABLE
  eng "Found .frm file with same name as one of the Dictionary Tables."
  chinese "找到与其中一个字典表同名的.frm文件。"

ER_DD_CREATED_FOR_UPGRADE
  eng "Created Data Dictionary for upgrade"
  chinese "已创建用于升级的数据字典"

ER_ERRMSG_CANT_FIND_FILE
  eng "Can't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive."
  chinese "找不到错误消息文件'%s'。请检查错误消息文件位置和'lc-Messages-dir'配置指令。"

OBSOLETE_ER_ERRMSG_LOADING_55_STYLE
  eng "Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters."
  chinese "使用5.5版之前的语义从%s加载错误消息。如果这不是故意的,请参阅文档以了解--lc-Messages-dir和--language参数的有效用法。"

ER_ERRMSG_MISSING_IN_FILE
  eng "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!"
  chinese "错误消息文件'%s'只有%d条错误消息,但它至少应该包含%d条错误消息。请检查上面的文件是否为该程序的正确版本！"

ER_ERRMSG_OOM
  eng "Not enough memory for messagefile '%s'"
  chinese "内存不足,无法存储邮件文件'%s'"

ER_ERRMSG_CANT_READ
  eng "Can't read from messagefile '%s'"
  chinese "无法从消息文件'%s'中读取"

ER_TABLE_INCOMPATIBLE_DECIMAL_FIELD
  eng "Found incompatible DECIMAL field '%s' in %s; Please do \"ALTER TABLE `%s` FORCE\" to fix it!"
  chinese "在%s中发现不兼容的小数字段'%s'；请执行\"ALTER TABLE`%s`FORCE\"以修复它！"

ER_TABLE_INCOMPATIBLE_YEAR_FIELD
  eng "Found incompatible YEAR(x) field '%s' in %s; Please do \"ALTER TABLE `%s` FORCE\" to fix it!"
  chinese "在%s中发现不兼容的年份(X)字段'%s'；请执行\"ALTER TABLE`%s`FORCE\"以修复它！"

ER_INVALID_CHARSET_AND_DEFAULT_IS_MB
  eng "'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed"
  chinese "'%s'没有字符集或字符集无效,并且默认字符集为多字节,因此字符列大小可能已更改"

ER_TABLE_WRONG_KEY_DEFINITION
  eng "Found wrong key definition in %s; Please do \"ALTER TABLE `%s` FORCE \" to fix it!"
  chinese "在%s中发现错误的键定义；请执行\"ALTER TABLE`%s`FORCE\"以修复它！"

ER_CANT_OPEN_FRM_FILE
  eng "Unable to open file %s"
  chinese "无法打开文件%s"

ER_CANT_READ_FRM_FILE
  eng "Error in reading file %s"
  chinese "读取文件%s时出错"

ER_TABLE_CREATED_WITH_DIFFERENT_VERSION
  eng "Table '%s' was created with a different version of MySQL and cannot be read"
  chinese "表'%s'是用不同版本的MySQL创建的,无法读取"

ER_VIEW_UNPARSABLE
  eng "Unable to read view %s"
  chinese "无法读取视图%s"

ER_FILE_TYPE_UNKNOWN
  eng "File %s has unknown type in its header."
  chinese "文件%s的头中有未知类型。"

ER_INVALID_INFO_IN_FRM
  eng "Incorrect information in file %s"
  chinese "文件%s中的信息不正确"

ER_CANT_OPEN_AND_LOCK_PRIVILEGE_TABLES
  eng "Can't open and lock privilege tables: %s"
  chinese "无法打开和锁定特权表:%s"

ER_AUDIT_PLUGIN_DOES_NOT_SUPPORT_AUDIT_AUTH_EVENTS
  eng "Plugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported."
  chinese "插件'%s'无法订阅MYSQL_AUDIT_AUTHORIZATION事件。当前不支持。"

ER_AUDIT_PLUGIN_HAS_INVALID_DATA
  eng "Plugin '%s' has invalid data."
  chinese "插件'%s'包含无效数据。"

ER_TZ_OOM_INITIALIZING_TIME_ZONES
  eng "Fatal error: OOM while initializing time zones"
  chinese "致命错误:初始化时区时出现OOM"

ER_TZ_CANT_OPEN_AND_LOCK_TIME_ZONE_TABLE
  eng "Can't open and lock time zone table: %s trying to live without them"
  chinese "无法打开并锁定时区表:%s尝试在没有它们的情况下生活"

ER_TZ_OOM_LOADING_LEAP_SECOND_TABLE
  eng "Fatal error: Out of memory while loading mysql.time_zone_leap_second table"
  chinese "致命错误:加载mysql.time_zone_leap_Second表时内存不足"

ER_TZ_TOO_MANY_LEAPS_IN_LEAP_SECOND_TABLE
  eng "Fatal error: While loading mysql.time_zone_leap_second table: too much leaps"
  chinese "致命错误:加载mysql.time_zone_leap_Second表时:跳跃太多"

ER_TZ_ERROR_LOADING_LEAP_SECOND_TABLE
  eng "Fatal error: Error while loading mysql.time_zone_leap_second table"
  chinese "致命错误:加载mysql.time_zone_leap_Second表时出错"

ER_TZ_UNKNOWN_OR_ILLEGAL_DEFAULT_TIME_ZONE
  eng "Fatal error: Illegal or unknown default time zone '%s'"
  chinese "致命错误:默认时区'%s'非法或未知"

ER_TZ_CANT_FIND_DESCRIPTION_FOR_TIME_ZONE
  eng "Can't find description of time zone '%.*s'"
  chinese "找不到时区'%.*s'的描述"

ER_TZ_CANT_FIND_DESCRIPTION_FOR_TIME_ZONE_ID
  eng "Can't find description of time zone '%u'"
  chinese "找不到时区'%u'的描述"

ER_TZ_TRANSITION_TYPE_TABLE_TYPE_TOO_LARGE
  eng "Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type id"
  chinese "从mysql.time_zone_Migration_type表中加载时区描述时出错:转换类型ID太大"

ER_TZ_TRANSITION_TYPE_TABLE_ABBREVIATIONS_EXCEED_SPACE
  eng "Error while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviations"
  chinese "从mysql.time_ZONE_TRANSION_TYPE表中加载时区描述时出错:没有足够的缩写空间"

ER_TZ_TRANSITION_TYPE_TABLE_LOAD_ERROR
  eng "Error while loading time zone description from mysql.time_zone_transition_type table"
  chinese "从mysql.time_zone_Migration_type表加载时区描述时出错"

ER_TZ_TRANSITION_TABLE_TOO_MANY_TRANSITIONS
  eng "Error while loading time zone description from mysql.time_zone_transition table: too much transitions"
  chinese "从mysql.time_ZONE_TRANSITION表加载时区描述时出错:转换太多"

ER_TZ_TRANSITION_TABLE_BAD_TRANSITION_TYPE
  eng "Error while loading time zone description from mysql.time_zone_transition table: bad transition type id"
  chinese "从mysql.time_ZONE_TRANSITION表加载时区描述时出错:转换类型ID错误"

ER_TZ_TRANSITION_TABLE_LOAD_ERROR
  eng "Error while loading time zone description from mysql.time_zone_transition table"
  chinese "从mysql.time_zone_interfort表加载时区描述时出错"

ER_TZ_NO_TRANSITION_TYPES_IN_TIME_ZONE
  eng "loading time zone without transition types"
  chinese "加载不带转换类型的时区"

ER_TZ_OOM_LOADING_TIME_ZONE_DESCRIPTION
  eng "Out of memory while loading time zone description"
  chinese "加载时区描述时内存不足"

ER_TZ_CANT_BUILD_MKTIME_MAP
  eng "Unable to build mktime map for time zone"
  chinese "无法为时区构建mktime映射"

ER_TZ_OOM_WHILE_LOADING_TIME_ZONE
  eng "Out of memory while loading time zone"
  chinese "加载时区时内存不足"

ER_TZ_OOM_WHILE_SETTING_TIME_ZONE
  eng "Fatal error: Out of memory while setting new time zone"
  chinese "致命错误:设置新时区时内存不足"

ER_REPLICA_SQL_THREAD_STOPPED_UNTIL_CONDITION_BAD
  eng "Replica SQL thread is stopped because UNTIL condition is bad(%s:%llu)."
  chinese "从SQL线程已停止,因为Until条件不好(%s:%llu)。"

ER_REPLICA_SQL_THREAD_STOPPED_UNTIL_POSITION_REACHED
  eng "Replica SQL thread stopped because it reached its UNTIL position %llu"
  chinese "从SQL线程已停止,因为它已到达其截止位置%llu"

ER_REPLICA_SQL_THREAD_STOPPED_BEFORE_GTIDS_ALREADY_APPLIED
  eng "Replica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already applied"
  chinese "从SQL线程已停止,因为已经应用了SQL_BEFORE_GTIDS%s"

ER_REPLICA_SQL_THREAD_STOPPED_BEFORE_GTIDS_REACHED
  eng "Replica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %s"
  chinese "从SQL线程停止,因为它到达了SQL_BEFORE_GTIDS%s"

ER_REPLICA_SQL_THREAD_STOPPED_AFTER_GTIDS_REACHED
  eng "Replica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %s"
  chinese "从SQL线程停止,因为它到达了SQL_AFTER_GTIDS%s"

ER_REPLICA_SQL_THREAD_STOPPED_GAP_TRX_PROCESSED
  eng "Replica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session."
  chinese "从属SQL线程根据Until SQL_AFTER_MTS_GAP停止,因为它已处理了上一个从属会话剩余的所有间隙事务。"

ER_GROUP_REPLICATION_PLUGIN_NOT_INSTALLED
  eng "Group Replication plugin is not installed."
  chinese "未安装组复制插件。"

ER_GTID_ALREADY_ADDED_BY_USER
  eng "The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client."
  chinese "事务拥有的GTID已在%s表中,这是由用户客户端的显式修改引起的。"

ER_FAILED_TO_DELETE_FROM_GTID_EXECUTED_TABLE
  eng "Failed to delete the row: '%s' from the gtid_executed table."
  chinese "无法从gtid_Executed表中删除行:'%s'。"

ER_FAILED_TO_COMPRESS_GTID_EXECUTED_TABLE
  eng "Failed to compress the gtid_executed table."
  chinese "无法压缩gtid_Executed表。"

ER_FAILED_TO_COMPRESS_GTID_EXECUTED_TABLE_OOM
  eng "Failed to compress the gtid_executed table, because it is failed to allocate the THD."
  chinese "无法压缩gtid_ecuted表,因为它无法分配THD。"

ER_FAILED_TO_INIT_THREAD_ATTR_FOR_GTID_TABLE_COMPRESSION
  eng "Failed to initialize thread attribute when creating compression thread."
  chinese "创建压缩线程时无法初始化线程属性。"

ER_FAILED_TO_CREATE_GTID_TABLE_COMPRESSION_THREAD
  eng "Can not create thread to compress gtid_executed table (errno= %d)"
  chinese "无法创建线程来压缩gtid_Executed表(错误号=%d)"

ER_FAILED_TO_JOIN_GTID_TABLE_COMPRESSION_THREAD
  eng "Could not join gtid_executed table compression thread. error:%d"
  chinese "无法联接GTID_EXECUTED表压缩线程。错误:%d"

ER_NPIPE_FAILED_TO_INIT_SECURITY_DESCRIPTOR
  eng "Can't start server : Initialize security descriptor: %s"
  chinese "无法启动服务器:初始化安全描述符:%s"

ER_NPIPE_FAILED_TO_SET_SECURITY_DESCRIPTOR
  eng "Can't start server : Set security descriptor: %s"
  chinese "无法启动服务器:设置安全描述符:%s"

ER_NPIPE_PIPE_ALREADY_IN_USE
  eng "Can't start server : Named Pipe \"%s\" already in use."
  chinese "无法启动服务器:命名管道\"%s\"已在使用。"

OBSOLETE_ER_NDB_SLAVE_SAW_EPOCH_LOWER_THAN_PREVIOUS_ON_START
  eng "NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning."
  chinese "NDB从属:在SQL线程开始应用纪元%llu/%llu(%llu),来自主服务器ID%u的,它低于以前应用的纪元%llu/%llu(%llu)。组主日志:%s,组主日志位置:%llu。请检查从属位置。"

OBSOLETE_ER_NDB_SLAVE_SAW_EPOCH_LOWER_THAN_PREVIOUS
  eng "NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu"
  chinese "NDB从属:SQL线程停止,因为正在应用纪元%llu/%llu(%llu),来自主服务器ID%u的,低于以前应用的纪元%llu/%llu(%llu)。组主日志:%s组主日志位置:%llu"

OBSOLETE_ER_NDB_SLAVE_SAW_ALREADY_COMMITTED_EPOCH
  eng "NDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu."
  chinese "NDB从属:SQL线程已停止,因为试图重新应用已提交的纪元%llu/%llu(%llu)从服务器ID%u。组主日志:%s组主日志位置:%llu。"

OBSOLETE_ER_NDB_SLAVE_PREVIOUS_EPOCH_NOT_COMMITTED
  eng "NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu."
  chinese "NDB从属:SQL线程停止,因为正在尝试应用新的纪元%llu/%llu(%llu),而尚未提交较低的接收纪元%llu/%llu(%llu)。主服务器ID:%u。组主日志:%s组主日志位置:%llu。"

OBSOLETE_ER_NDB_SLAVE_MISSING_DATA_FOR_TIMESTAMP_COLUMN
  eng "NDB Replica: missing data for %s timestamp column %u."
  chinese "NDB Replica :缺少%s时间戳列%u的数据。"

OBSOLETE_ER_NDB_SLAVE_LOGGING_EXCEPTIONS_TO
  eng "NDB Replica: Table %s.%s logging exceptions to %s.%s"
  chinese "NDB从属:表%s.%s将异常记录到%s.%s"

OBSOLETE_ER_NDB_SLAVE_LOW_EPOCH_RESOLUTION
  eng "NDB Replica: Table %s.%s : %s, low epoch resolution"
  chinese "NDB从属:表%s。%s:%s,低纪元分辨率"

OBSOLETE_ER_NDB_INFO_FOUND_UNEXPECTED_FIELD_TYPE
  eng "Found unexpected field type %u"
  chinese "发现意外的字段类型%u"

OBSOLETE_ER_NDB_INFO_FAILED_TO_CREATE_NDBINFO
  eng "Failed to create NdbInfo"
  chinese "无法创建NdbInfo"

OBSOLETE_ER_NDB_INFO_FAILED_TO_INIT_NDBINFO
  eng "Failed to init NdbInfo"
  chinese "无法初始化NdbInfo"

OBSOLETE_ER_NDB_CLUSTER_WRONG_NUMBER_OF_FUNCTION_ARGUMENTS
  eng "ndb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u"
  chinese "NDB_SERIALIZE_COND:找到的函数参数数与预期的函数参数数意外不匹配%u"

OBSOLETE_ER_NDB_CLUSTER_SCHEMA_INFO
  eng "%s - %s.%s"
  chinese "%s - %s.%s"

OBSOLETE_ER_NDB_CLUSTER_GENERIC_MESSAGE
  eng "%s"
  chinese "%s"

ER_RPL_CANT_OPEN_INFO_TABLE
  eng "Info table is not ready to be used. Table '%s.%s' cannot be opened."
  chinese "INFO表尚未准备好使用。表'%s.%s'无法打开。"

ER_RPL_CANT_SCAN_INFO_TABLE
  eng "Info table is not ready to be used. Table '%s.%s' cannot be scanned."
  chinese "INFO表尚未准备好使用。无法扫描表'%s.%s'。"

ER_RPL_CORRUPTED_INFO_TABLE
  eng "Corrupted table %s.%s. Check out table definition."
  chinese "表%s.%s已损坏。请检查表定义。"

ER_RPL_CORRUPTED_KEYS_IN_INFO_TABLE
  eng "Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead."
  chinese "INFO表的关键字字段有问题。表'%s.%s'要求字段#%u是'%s',但却发现是'%s'。"

ER_RPL_WORKER_ID_IS
  eng "Choosing worker id %lu, the following is going to be %lu"
  chinese "正在选择工作ID%lu,下面将是%lu"

ER_RPL_INCONSISTENT_TIMESTAMPS_IN_TRX
  eng "Transaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)"
  chinese "使用不一致的逻辑时间戳标记事务:SEQUENCE_NUMBER(%lld)<=LAST_COMMITTED(%lld)"

ER_RPL_INCONSISTENT_SEQUENCE_NO_IN_TRX
  eng "Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)"
  chinese "事务的序列号与前一个的序列号不一致:SEQUENCE_NUMBER(%lld)<=上一个SEQUENCE_NUMBER(%lld)"

OBSOLETE_ER_RPL_CHANNELS_REQUIRE_TABLES_AS_INFO_REPOSITORIES
  eng "For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLE"
  chinese "要创建复制通道,必须将主信息存储库和中继日志信息存储库设置为表"

ER_RPL_CHANNELS_REQUIRE_NON_ZERO_SERVER_ID
  eng "For the creation of replication channels the server id must be different from 0"
  chinese "要创建复制通道,服务器ID必须不同于0"

OBSOLETE_ER_RPL_REPO_SHOULD_BE_TABLE
  eng "Replica: Wrong repository. Repository should be TABLE"
  chinese "Slave:错误的存储库。存储库应该是表"

ER_RPL_ERROR_CREATING_CONNECTION_METADATA
  eng "Error creating connection metadata: %s."
  chinese "创建主信息时出错:%s。"

OBSOLETE_ER_RPL_ERROR_CHANGING_CONNECTION_METADATA_REPO_TYPE
  eng "Error changing the type of connection metadata's repository: %s."
  chinese "更改主信息存储库的类型时出错:%s。"

OBSOLETE_ER_RPL_CHANGING_AM_TYPE_FAILED_DUE_TO_GAPS
  eng "It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change."
  chinese "无法更改中继日志储存库的类型,因为存在可能存在执行间隙的工作储存库。--Relay_LOG_INFO_REPORATION的值已更改为找到的工作储存库之一。必须先对间隙进行排序,然后才能继续进行类型更改。"

ER_RPL_ERROR_CREATING_APPLIER_METADATA
  eng "Error creating applier metadata: %s."
  chinese "创建中继日志信息时出错:%s。"

OBSOLETE_ER_RPL_ERROR_CHANGING_APPLIER_METADATA_REPO_TYPE
  eng "Error changing the type of applier metadata's repository: %s."
  chinese "更改中继日志信息存储库的类型时出错:%s。"

ER_RPL_FAILED_TO_DELETE_FROM_REPLICA_WORKERS_INFO_REPOSITORY
  eng "Could not delete from Replica Workers info repository."
  chinese "无法从从属工作器信息存储库中删除。"

ER_RPL_FAILED_TO_RESET_STATE_IN_REPLICA_INFO_REPOSITORY
  eng "Could not store the reset Replica Worker state into the replica info repository."
  chinese "无法将重置从属工作进程状态存储到从属信息库。"

OBSOLETE_ER_RPL_ERROR_CHECKING_REPOSITORY
  eng "Error in checking %s repository."

ER_RPL_REPLICA_GENERIC_MESSAGE
  eng "Replica: %s"
  chinese "从属:%s"

ER_RPL_REPLICA_COULD_NOT_CREATE_CHANNEL_LIST
  eng "Replica: Could not create channel list"
  chinese "Slave:无法创建频道列表"

ER_RPL_MULTISOURCE_REQUIRES_TABLE_TYPE_REPOSITORIES
  eng "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."
  chinese "从属:此从属以前是多源从属,只有基于表的主信息库和中继日志信息库都支持它。发现一个或两个信息存储库都是文件类型。将这两个存储库都设置为表类型。"

ER_RPL_REPLICA_FAILED_TO_INIT_A_CONNECTION_METADATA_STRUCTURE
  eng "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."
  chinese "从属:未能初始化通道'%s'的主信息结构；其记录可能仍存在于'mysql.lave_master_info'表中,请考虑将其删除。"

ER_RPL_REPLICA_FAILED_TO_INIT_CONNECTION_METADATA_STRUCTURE
  eng "Failed to initialize the connection metadata structure%s"
  chinese "无法初始化主信息结构%s"

ER_RPL_REPLICA_FAILED_TO_CREATE_CHANNEL_FROM_CONNECTION_METADATA
  eng "Replica: Failed to create a channel from connection metadata repository."
  chinese "从属:无法从主信息表存储库创建频道。"

ER_RPL_FAILED_TO_CREATE_NEW_INFO_FILE
  eng "Failed to create a new info file (file '%s', errno %d)"
  chinese "无法创建新的信息文件(文件'%s',错误号%d)"

ER_RPL_FAILED_TO_CREATE_CACHE_FOR_INFO_FILE
  eng "Failed to create a cache on info file (file '%s')"
  chinese "无法在信息文件(文件'%s')上创建缓存"

ER_RPL_FAILED_TO_OPEN_INFO_FILE
  eng "Failed to open the existing info file (file '%s', errno %d)"
  chinese "无法打开现有的信息文件(文件'%s',错误号%d)"

ER_RPL_GTID_MEMORY_FINALLY_AVAILABLE
  eng "Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs."
  chinese "服务器在为存储GTID分配新的间隔块时,克服了'%d'次尝试中的临时'内存不足'。"

ER_SERVER_COST_UNKNOWN_COST_CONSTANT
  eng "Unknown cost constant \"%s\" in mysql.server_cost table"
  chinese "mySQL_SERVER_COST表中的未知成本常量\"%s\""

ER_SERVER_COST_INVALID_COST_CONSTANT
  eng "Invalid value for cost constant \"%s\" in mysql.server_cost table: %.1f"

ER_ENGINE_COST_UNKNOWN_COST_CONSTANT
  eng "Unknown cost constant \"%s\" in mysql.engine_cost table"
  chinese "mysql.Engine_Cost表中的未知成本常量\"%s\""

ER_ENGINE_COST_UNKNOWN_STORAGE_ENGINE
  eng "Unknown storage engine \"%s\" in mysql.engine_cost table"
  chinese "mysql.Engine_Cost表中的存储引擎\"%s\"未知"

ER_ENGINE_COST_INVALID_DEVICE_TYPE_FOR_SE
  eng "Invalid device type %d for \"%s\" storage engine for cost constant \"%s\" in mysql.engine_cost table"
  chinese "设备类型%d对于mysql.Engine_Cost表\"%s\"中的成本常量\"%s\"存储引擎无效"

ER_ENGINE_COST_INVALID_CONST_CONSTANT_FOR_SE_AND_DEVICE
  eng "Invalid value for cost constant \"%s\" for \"%s\" storage engine and device type %d in mysql.engine_cost table: %.1f"

ER_SERVER_COST_FAILED_TO_READ
  eng "Error while reading from mysql.server_cost table."
  chinese "读取mySQL_SERVER_COST表时出错。"

ER_ENGINE_COST_FAILED_TO_READ
  eng "Error while reading from mysql.engine_cost table."
  chinese "读取mysql.Engine_Cost表时出错。"

ER_FAILED_TO_OPEN_COST_CONSTANT_TABLES
  eng "Failed to open optimizer cost constant tables"
  chinese "无法打开优化程序成本不变表"

ER_RPL_UNSUPPORTED_UNIGNORABLE_EVENT_IN_STREAM
  eng "Unsupported non-ignorable event fed into the event stream."
  chinese "反馈到事件流中的不受支持的不可忽略事件。"

ER_RPL_GTID_LOG_EVENT_IN_STREAM
  eng "GTID_LOG_EVENT, GTID_TAGGED_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s."
  chinese "事件流%s中不应包含GTID_LOG_EVENT、ANNOWARY_GTID_LOG_EVENT或ANONYMOUS_GTID_LOG_EVENT。"

ER_RPL_UNEXPECTED_BEGIN_IN_STREAM
  eng "QUERY(BEGIN) is not expected in an event stream in the middle of a %s."
  chinese "在%s中间的事件流中不应出现查询(BEGIN)。"

ER_RPL_UNEXPECTED_COMMIT_ROLLBACK_OR_XID_LOG_EVENT_IN_STREAM
  eng "QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s."
  chinese "事件流%s中不应包含查询(COMMIT或ROLLBACK)或XID_LOG_EVENT。"

ER_RPL_UNEXPECTED_XA_ROLLBACK_IN_STREAM
  eng "QUERY(XA ROLLBACK) is not expected in an event stream %s."
  chinese "事件流%s中不需要查询(XA回滚)。"

ER_EVENT_EXECUTION_FAILED_CANT_AUTHENTICATE_USER
  eng "Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user."
  chinese "事件计划程序:[%s].[%s.%s]执行失败,无法对用户进行身份验证。"

ER_EVENT_EXECUTION_FAILED_USER_LOST_EVEN_PRIVILEGE
  eng "Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege."
  chinese "事件计划程序:[%s].[%s.%s]执行失败,用户不再具有事件权限。"

ER_EVENT_ERROR_DURING_COMPILATION
  eng "Event Scheduler: %serror during compilation of %s.%s"
  chinese "事件计划程序:%s编译期间出现错误%s。%s"

ER_EVENT_DROPPING
  eng "Event Scheduler: Dropping %s.%s"
  chinese "事件计划程序:正在丢弃%s.%s"

OBSOLETE_ER_NDB_SCHEMA_GENERIC_MESSAGE
  eng "Ndb schema[%s.%s]: %s"
  chinese "NDB架构[%s.%s]:%s"

ER_RPL_INCOMPATIBLE_DECIMAL_IN_RBR
  eng "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."
  chinese "在RBR模式下,Slave在创建转换表时从Master接收到不兼容的小数字段(旧式小数字段)。请考虑通过对列名%s.%s.%s执行ALTER命令,将Master上的数据类型更改为新样式DECIMAL。"

ER_INIT_ROOT_WITHOUT_PASSWORD
  eng "root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option."
  chinese "Root@Localhost是用空密码创建的！请考虑关闭--初始化-不安全选项。"

ER_INIT_GENERATING_TEMP_PASSWORD_FOR_ROOT
  eng "A temporary password is generated for root@localhost: %s"
  chinese "为root@localhost主机生成临时密码:%s"

ER_INIT_CANT_OPEN_BOOTSTRAP_FILE
  eng "Failed to open the bootstrap file %s"
  chinese "无法打开引导程序文件%s"

ER_INIT_BOOTSTRAP_COMPLETE
  eng "Bootstrapping complete"
  chinese "引导完成"

ER_INIT_DATADIR_NOT_EMPTY_WONT_INITIALIZE
  eng "--initialize specified but the data directory has files in it. Aborting."
  chinese "--指定了初始化,但数据目录中有文件。正在中止。"

ER_INIT_DATADIR_EXISTS_WONT_INITIALIZE
  eng "--initialize specified on an existing data directory."
  chinese "--在现有数据目录上指定的初始化。"

ER_INIT_DATADIR_EXISTS_AND_PATH_TOO_LONG_WONT_INITIALIZE
  eng "--initialize specified but the data directory exists and the path is too long. Aborting."
  chinese "--已指定初始化,但数据目录存在且路径太长。正在中止。"

ER_INIT_DATADIR_EXISTS_AND_NOT_WRITABLE_WONT_INITIALIZE
  eng "--initialize specified but the data directory exists and is not writable. Aborting."
  chinese "--指定了初始化,但数据目录存在且不可写。正在中止。"

ER_INIT_CREATING_DD
  eng "Creating the data directory %s"
  chinese "正在创建数据目录%s"

ER_RPL_BINLOG_STARTING_DUMP
  eng "Start binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)"
  chinese "启动到主线程id(%u)、从属服务器(%u)、位置(%s,%llu)的binlog_dump"

ER_RPL_BINLOG_SOURCE_SENDS_HEARTBEAT
  eng "source sends heartbeat message"
  chinese "主机发送心跳消息"

ER_RPL_BINLOG_SKIPPING_REMAINING_HEARTBEAT_INFO
  eng "the rest of heartbeat info skipped ..."
  chinese "其余的心跳信息已跳过..."

ER_RPL_BINLOG_SOURCE_USES_CHECKSUM_AND_REPLICA_CANT
  eng "Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process them"
  chinese "主服务器配置为使用校验和记录复制事件,但不会将此类事件发送给无法处理它们的从属服务器"

OBSOLETE_ER_NDB_QUERY_FAILED
  eng "NDB: Query '%s' failed, error: %d: %s"
  chinese "NDB:查询'%s'失败,错误:%d:%s"

ER_KILLING_THREAD
  eng "Killing thread %lu"
  chinese "正在删除线程%lu"

ER_DETACHING_SESSION_LEFT_BY_PLUGIN
  eng "Plugin %s is deinitializing a thread but left a session attached. Detaching it forcefully."
  chinese "插件%s正在取消初始化线程,但保留了一个连接的会话。正在强制分离它。"

ER_CANT_DETACH_SESSION_LEFT_BY_PLUGIN
  eng "Failed to detach the session."
  chinese "无法分离会话。"

ER_DETACHED_SESSIONS_LEFT_BY_PLUGIN
  eng "Closed forcefully %u session%s left opened by plugin %s"
  chinese "已强制关闭%u会话%s,并由插件%s打开"

ER_FAILED_TO_DECREMENT_NUMBER_OF_THREADS
  eng "Failed to decrement the number of threads"
  chinese "无法减少线程数"

ER_PLUGIN_DID_NOT_DEINITIALIZE_THREADS
  eng "Plugin %s did not deinitialize %u threads"
  chinese "插件%s未取消初始化%u个线程"

ER_KILLED_THREADS_OF_PLUGIN
  eng "Killed %u threads of plugin %s"
  chinese "杀死了%u个线程插件%s的"

OBSOLETE_ER_NDB_SLAVE_MAX_REPLICATED_EPOCH_UNKNOWN
  eng "NDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %s"
  chinese "NDB从属:无法确定从%s复制的最大纪元。从属启动时为%s,错误%u%s"

OBSOLETE_ER_NDB_SLAVE_MAX_REPLICATED_EPOCH_SET_TO
  eng "NDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica start"
  chinese "NDB从属:从属启动时将MaxReplicatedEpoch设置为%llu(%u/%u)"

OBSOLETE_ER_NDB_NODE_ID_AND_MANAGEMENT_SERVER_INFO
  eng "NDB: NodeID is %lu, management server '%s:%lu'"
  chinese "NDB:节点ID为%lu,管理服务器'%s:%lu'"

OBSOLETE_ER_NDB_DISCONNECT_INFO
  eng "tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%u"
  chinese "tid%u:节点[%u]TRANSACTION_HINT=%u,TRANSACTION_NO_HINT=%u"

OBSOLETE_ER_NDB_COLUMN_DEFAULTS_DIFFER
  eng "NDB Internal error: Default values differ for column %u, ndb_default: %d"
  chinese "NDB内部错误:列%u的默认值不同,NDB_DEFAULT:%d"

OBSOLETE_ER_NDB_COLUMN_SHOULD_NOT_HAVE_NATIVE_DEFAULT
  eng "NDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%u"
  chinese "NDB内部错误:列%u具有本机默认设置,但不应该。标志=%u,类型=%u"

OBSOLETE_ER_NDB_FIELD_INFO
  eng "field[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]"
  chinese "字段[名称:'%s',类型:%u,REAL_TYPE:%u,标志:0x%x,IS_NULL:%d]"

OBSOLETE_ER_NDB_COLUMN_INFO
  eng "ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]"
  chinese "ndbCol[名称:'%s',类型:%u,Column_no:%d,可为空:%d]"

OBSOLETE_ER_NDB_OOM_IN_FIX_UNIQUE_INDEX_ATTR_ORDER
  eng "fix_unique_index_attr_order: my_malloc(%u) failure"
  chinese "FIX_UNIQUE_INDEX_ATRR_ORDER:my_malloc(%u)失败"

OBSOLETE_ER_NDB_SLAVE_MALFORMED_EVENT_RECEIVED_ON_TABLE
  eng "NDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica."
  chinese "NDB Slave:无法分析表%s上收到的格式错误的事件。正在停止Slave。"

OBSOLETE_ER_NDB_SLAVE_CONFLICT_FUNCTION_REQUIRES_ROLE
  eng "NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica."
  chinese "NDB从属:定义的冲突函数%s在表%s上需要设置NDB_SLAVE_CONFULT_ROLE变量。正在停止从属。"

OBSOLETE_ER_NDB_SLAVE_CONFLICT_TRANSACTION_IDS
  eng "NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster."
  chinese "NDB从属:在表%s上定义了事务冲突检测,但收到的事件没有事务ID。请检查上游群集上的--ndb-log-Transaction-id设置。"

OBSOLETE_ER_NDB_SLAVE_BINLOG_MISSING_INFO_FOR_CONFLICT_DETECTION
  eng "NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster."
  chinese "NDB从属:表%s上的Binlog事件缺少冲突检测所需的信息。请检查上游群集上的binlog格式选项。"

OBSOLETE_ER_NDB_ERROR_IN_READAUTOINCREMENTVALUE
  eng "Error %lu in readAutoIncrementValue(): %s"
  chinese "ReadAutoIncrementValue()中出现错误%lu:%s"

OBSOLETE_ER_NDB_FOUND_UNCOMMITTED_AUTOCOMMIT
  eng "found uncommitted autocommit+rbwr transaction, commit status: %d"
  chinese "找到未提交的自动提交+rbwr事务,提交状态:%d"

OBSOLETE_ER_NDB_SLAVE_TOO_MANY_RETRIES
  eng "Ndb replica retried transaction %u time(s) in vain.  Giving up."
  chinese "NDB从属数据库重试事务%u次无效。正在放弃。"

OBSOLETE_ER_NDB_SLAVE_ERROR_IN_UPDATE_CREATE_INFO
  eng "Error %lu in ::update_create_info(): %s"
  chinese "Error %lu in ::update_create_info(): %s"

OBSOLETE_ER_NDB_SLAVE_CANT_ALLOCATE_TABLE_SHARE
  eng "NDB: allocating table share for %s failed"
  chinese "NDB:为%s分配表共享失败"

OBSOLETE_ER_NDB_BINLOG_ERROR_INFO_FROM_DA
  eng "NDB Binlog: (%d)%s"
  chinese "NDB Binlog: (%d)%s"

OBSOLETE_ER_NDB_BINLOG_CREATE_TABLE_EVENT
  eng "NDB Binlog: CREATE TABLE Event: %s"
  chinese "NDB Binlog:创建表事件:%s"

OBSOLETE_ER_NDB_BINLOG_FAILED_CREATE_TABLE_EVENT_OPERATIONS
  eng "NDB Binlog: FAILED CREATE TABLE event operations. Event: %s"
  chinese "NDB Binlog:CREATE TABLE事件操作失败。事件:%s"

OBSOLETE_ER_NDB_BINLOG_RENAME_EVENT
  eng "NDB Binlog: RENAME Event: %s"
  chinese "NDB Binlog:重命名事件:%s"

OBSOLETE_ER_NDB_BINLOG_FAILED_CREATE_DURING_RENAME
  eng "NDB Binlog: FAILED create event operations during RENAME. Event %s"
  chinese "NDB Binlog:重命名期间创建事件操作失败。事件%s"

OBSOLETE_ER_NDB_UNEXPECTED_RENAME_TYPE
  eng "Unexpected rename case detected, sql_command: %d"
  chinese "检测到意外重命名大小写,SQL_COMMAND:%d"

OBSOLETE_ER_NDB_ERROR_IN_GET_AUTO_INCREMENT
  eng "Error %lu in ::get_auto_increment(): %s"
  chinese "错误%lu在::GET_AUTO_INCREMENT()中:%s"

OBSOLETE_ER_NDB_CREATING_SHARE_IN_OPEN
  eng "Calling ndbcluster_create_binlog_setup(%s) in ::open"
  chinese "在::Open中调用nDBCLUSTER_CREATE_BINLOG_SETUP(%s)"

OBSOLETE_ER_NDB_TABLE_OPENED_READ_ONLY
  eng "table '%s' opened read only"
  chinese "表'%s'以只读方式打开"

OBSOLETE_ER_NDB_INITIALIZE_GIVEN_CLUSTER_PLUGIN_DISABLED
  eng "NDB: '--initialize' -> ndbcluster plugin disabled"
  chinese "NDB:'--INITIALIZE'->nDBCLUSTER插件禁用"

OBSOLETE_ER_NDB_BINLOG_FORMAT_CHANGED_FROM_STMT_TO_MIXED
  eng "NDB: Changed global value of binlog_format from STATEMENT to MIXED"
  chinese "NDB:将binlog_Format的全局值从语句更改为MIXED"

OBSOLETE_ER_NDB_TRAILING_SHARE_RELEASED_BY_CLOSE_CACHED_TABLES
  eng "NDB_SHARE: trailing share %s, released by close_cached_tables"
  chinese "NDB_SHARE:后续共享%s,由CLOSE_CACHED_TABLES释放"

OBSOLETE_ER_NDB_SHARE_ALREADY_EXISTS
  eng "NDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak."
  chinese "NDB_SHARE:%s已存在USE_COUNT=%d。为安全起见,请将其移开,但可能会发生内存泄漏。"

OBSOLETE_ER_NDB_HANDLE_TRAILING_SHARE_INFO
  eng "handle_trailing_share: %s use_count: %u"
  chinese "HANDLE_TRAILING_SHARE:%s使用计数:%u"

OBSOLETE_ER_NDB_CLUSTER_GET_SHARE_INFO
  eng "ndbcluster_get_share: %s use_count: %u"
  chinese "nDBCLUSTER_GET_SHARE:%s使用计数:%u"

OBSOLETE_ER_NDB_CLUSTER_REAL_FREE_SHARE_INFO
  eng "ndbcluster_real_free_share: %s use_count: %u"
  chinese "ndbcluster_real_free_share: %s use_count: %u"

OBSOLETE_ER_NDB_CLUSTER_REAL_FREE_SHARE_DROP_FAILED
  eng "ndbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)"
  chinese "nDBCLUSTER_REAL_FREE_SHARE:%s,仍处于打开状态-忽略'FREE'(泄漏？)"

OBSOLETE_ER_NDB_CLUSTER_FREE_SHARE_INFO
  eng "ndbcluster_free_share: %s use_count: %u"
  chinese "nDBCLUSTER_FREE_SHARE:%s使用计数:%u"

OBSOLETE_ER_NDB_CLUSTER_MARK_SHARE_DROPPED_INFO
  eng "ndbcluster_mark_share_dropped: %s use_count: %u"
  chinese "nDBCLUSTER_MARK_SHARE_DROP:%s使用计数:%u"

OBSOLETE_ER_NDB_CLUSTER_MARK_SHARE_DROPPED_DESTROYING_SHARE
  eng "ndbcluster_mark_share_dropped: destroys share %s"
  chinese "nDBCLUSTER_MARK_SHARE_DROP:销毁共享%s"

OBSOLETE_ER_NDB_CLUSTER_OOM_THD_NDB
  eng "Could not allocate Thd_ndb object"
  chinese "无法分配THD_NDB对象"

OBSOLETE_ER_NDB_BINLOG_NDB_TABLES_INITIALLY_READ_ONLY
  eng "NDB Binlog: Ndb tables initially read only."
  chinese "NDB Binlog:NDB表最初为只读。"

OBSOLETE_ER_NDB_UTIL_THREAD_OOM
  eng "ndb util thread: malloc failure, query cache not maintained properly"
  chinese "NDB util线程:Malloc失败,查询缓存维护不正确"

OBSOLETE_ER_NDB_ILLEGAL_VALUE_FOR_NDB_RECV_THREAD_CPU_MASK
  eng "Trying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignored"
  chinese "正在尝试将NDB_Recv_THREAD_CPU_MASK设置为非法值=%s,已忽略"

OBSOLETE_ER_NDB_TOO_MANY_CPUS_IN_NDB_RECV_THREAD_CPU_MASK
  eng "Trying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %s"
  chinese "尝试在ndb_recv_线程_cpu_掩码中设置过多的CPU,忽略此变量,错误值=%s"

ER_DBUG_CHECK_SHARES_OPEN
  eng "dbug_check_shares open:"
  chinese "dbug_check_Shares打开:"

ER_DBUG_CHECK_SHARES_INFO
  eng "  %s.%s: state: %s(%u) use_count: %u"
  chinese "  %s.%s: state: %s(%u) use_count: %u"

ER_DBUG_CHECK_SHARES_DROPPED
  eng "dbug_check_shares dropped:"
  chinese "dbug_check_Shares已删除:"

ER_INVALID_OR_OLD_TABLE_OR_DB_NAME
  eng "Invalid (old?) table or database name '%s'"
  chinese "无效(旧？)表或数据库名称'%s'"

ER_TC_RECOVERING_AFTER_CRASH_USING
  eng "Recovering after a crash using %s"
  chinese "使用%s在崩溃后恢复"

ER_TC_CANT_AUTO_RECOVER_WITH_TC_HEURISTIC_RECOVER
  eng "Cannot perform automatic crash recovery when --tc-heuristic-recover is used"
  chinese "使用--TC-Heuristic-Recover时无法执行自动崩溃恢复"

ER_TC_BAD_MAGIC_IN_TC_LOG
  eng "Bad magic header in tc log"
  chinese "TC日志中出现错误的魔术标题"

ER_TC_NEED_N_SE_SUPPORTING_2PC_FOR_RECOVERY
  eng "Recovery failed! You must enable exactly %d storage engines that support two-phase commit protocol"
  chinese "恢复失败！您必须正好启用支持两阶段提交协议的%d个存储引擎"

ER_TC_RECOVERY_FAILED_THESE_ARE_YOUR_OPTIONS
  eng "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}"
  chinese "崩溃恢复失败。请更正问题(例如,内存不足错误)并重新启动,或者删除TC日志并使用--TC-Heuristic-Recover={COMMIT|ROLLBACK}启动mysqld"

ER_TC_HEURISTIC_RECOVERY_MODE
  eng "Heuristic crash recovery mode"
  chinese "启发式崩溃恢复模式"

ER_TC_HEURISTIC_RECOVERY_FAILED
  eng "Heuristic crash recovery failed"
  chinese "启发式崩溃恢复失败"

ER_TC_RESTART_WITHOUT_TC_HEURISTIC_RECOVER
  eng "Please restart mysqld without --tc-heuristic-recover"
  chinese "请在不使用--TC-Heuristic-Recover的情况下重新启动mysqld"

ER_RPL_REPLICA_FAILED_TO_CREATE_OR_RECOVER_INFO_REPOSITORIES
  eng "Failed to create or recover replication info repositories."
  chinese "无法创建或恢复复制信息库。"

ER_RPL_REPLICA_AUTO_POSITION_IS_1_AND_GTID_MODE_IS_OFF
  eng "Detected misconfiguration: replication channel '%.192s' 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 '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread."
  chinese "检测到配置错误:复制通道'%.192s'被配置为AUTO_POSITION=1,但服务器是在--gtid-MODE=OFF的情况下启动的。在启动从属接收器线程之前,请使用将通道'%.192s'的MASTER更改为MASTER_AUTO_POSITION=0来重新配置复制,或将GTID_MODE更改为OFF以外的某个值。"

ER_RPL_REPLICA_CANT_START_REPLICA_FOR_CHANNEL
  eng "Replica: Could not start replica for channel '%s'. operation discontinued"
  chinese "从属:无法启动通道'%s'的从属。操作已停止"

ER_RPL_REPLICA_CANT_STOP_REPLICA_FOR_CHANNEL
  eng "Replica: Could not stop replica for channel '%s' operation discontinued"
  chinese "从属:无法停止通道'%s'操作中止的从属"

ER_RPL_RECOVERY_NO_ROTATE_EVENT_FROM_SOURCE
  eng "Error during --relay-log-recovery: Could not locate rotate event from the source."
  chinese "--RELAY-LOG-RECOVERY过程中出错:找不到来自主服务器的旋转事件。"

ER_RPL_RECOVERY_ERROR_READ_RELAY_LOG
  eng "Error during --relay-log-recovery: Error reading events from relay log: %d"
  chinese "--RELAY-LOG-RECOVERY过程中出错:从中继日志读取事件时出错:%d"

OBSOLETE_ER_RPL_RECOVERY_ERROR_FREEING_IO_CACHE
  eng "Error during --relay-log-recovery: Error while freeing IO_CACHE object"
  chinese "错误期间--RELAY-LOG-RECOVERY:释放IO_CACHE对象时出错"

ER_RPL_RECOVERY_SKIPPED_GROUP_REPLICATION_CHANNEL
  eng "Relay log recovery skipped for group replication channel."
  chinese "已跳过组复制通道的中继日志恢复。"

ER_RPL_RECOVERY_ERROR
  eng "Error during --relay-log-recovery: %s"
  chinese "在--relay-log-recovery期间出错:%s"

ER_RPL_RECOVERY_IO_ERROR_READING_RELAY_LOG_INDEX
  eng "Error during --relay-log-recovery: Could not read relay log index file due to an IO error."
  chinese "--RELAY-LOG-RECOVERY过程中出错:由于IO错误,无法读取中继日志索引文件。"

ER_RPL_RECOVERY_FILE_SOURCE_POS_INFO
  eng "Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively."
  chinese "从主位置%ld和文件%s%s恢复。以前的中继日志位置和中继日志文件已分别设置为%lld和%s。"

ER_RPL_RECOVERY_REPLICATE_SAME_SERVER_ID_REQUIRES_POSITION
  eng "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."
  chinese "--RELAY-LOG-RECOVERY过程中出错:REPLICATE_Same_SERVER_ID正在使用中,并且SQL线程的位置未初始化,因此无法进行中继日志恢复。"

ER_RPL_MTA_RECOVERY_STARTING_COORDINATOR
  eng "MTA recovery: starting coordinator thread to fill MTA gaps."
  chinese "MTA恢复:正在启动协调程序线程以填补MTA空白。"

ER_RPL_MTA_RECOVERY_FAILED_TO_START_COORDINATOR
  eng "MTA recovery: failed to start the coordinator thread. Check the error log for additional details."
  chinese "MTA恢复:无法启动协调程序线程。有关其他详细信息,请查看错误日志。"

ER_RPL_MTA_AUTOMATIC_RECOVERY_FAILED
  eng "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."
  chinese "MTA恢复:自动恢复失败。从属服务器因上一个会话中的错误而停止,或者中继日志已损坏。请修复从属端错误的原因,然后重新启动从属服务器或考虑使用重置从属服务器。"

ER_RPL_MTA_RECOVERY_CANT_OPEN_RELAY_LOG
  eng "Failed to open the relay log '%s' (relay_log_pos %s)."
  chinese "无法打开中继日志'%s'(RELAY_LOG_POS%s)。"

ER_RPL_MTA_RECOVERY_SUCCESSFUL
  eng "MTA recovery: completed successfully."
  chinese "MTA恢复:已成功完成。"

ER_RPL_SERVER_ID_MISSING
  eng "Server id not set, will not start replica%s"
  chinese "未设置服务器ID,将不会启动从属%s"

ER_RPL_CANT_CREATE_REPLICA_THREAD
  eng "Can't create replica thread%s."
  chinese "无法创建从线程%s。"

ER_RPL_REPLICA_IO_THREAD_WAS_KILLED
  eng "The replica IO thread%s was killed while executing initialization query '%s'"
  chinese "执行初始化查询'%s'时,从IO线程%s被终止"

OBSOLETE_ER_RPL_REPLICA_SOURCE_UUID_HAS_CHANGED
  eng "The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s."
  chinese "主机的UUID已更改,但除非您手动更改,否则不会发生这种情况。旧的UUID是%s。"

ER_RPL_REPLICA_USES_CHECKSUM_AND_SOURCE_PRE_50
  eng "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."
  chinese "找到MySQL服务器版本早于5.0的主服务器。在从属服务器上启用校验和后,复制可能无法正常工作。要确保正确复制,请使用--REPLICE_SQL_VERIFY_CHECKSUM=0重新启动从属服务器。"

ER_RPL_REPLICA_SECONDS_BEHIND_SOURCE_DUBIOUS
  eng "\"SELECT UNIX_TIMESTAMP()\" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)"
  chinese "\"SELECT UNIXTIMESTAMP()\"在主机上失败,不信任SHOW REPLICA STATUS的SELECT_BACKING_MASTER列。错误:%s(%d)"

ER_RPL_REPLICA_CANT_FLUSH_CONNECTION_METADATA_REPOS
  eng "Failed to flush connection metadata repository."
  chinese "刷新主信息文件失败。"

ER_RPL_REPLICA_REPORT_HOST_TOO_LONG
  eng "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."
  chinese "REPORT_HOST的长度为%zu。它大于最大长度(%d),因此无法将此从属服务器注册到主服务器%s。"

ER_RPL_REPLICA_REPORT_USER_TOO_LONG
  eng "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."
  chinese "REPORT_USER的长度为%zu。它大于最大长度(%d),因此无法将此从属服务器注册到主服务器%s。"

ER_RPL_REPLICA_REPORT_PASSWORD_TOO_LONG
  eng "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."
  chinese "REPORT_PASSWORD的长度为%zu。它大于最大长度(%d),因此无法将此从属服务器注册到主服务器%s。"

ER_RPL_REPLICA_ERROR_RETRYING
  eng "Error on %s: %d  %s, will retry in %d secs"
  chinese "%s上的错误:%d %s,将在%d秒后重试"

ER_RPL_REPLICA_ERROR_READING_FROM_SERVER
  eng "Error reading packet from server%s: %s (server_errno=%d)"
  chinese "从服务器%s读取数据包时出错:%s(server_errno=%d)"

ER_RPL_REPLICA_DUMP_THREAD_KILLED_BY_SOURCE
  eng "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"
  chinese "从%s:由于主服务器上的转储线程被终止,从服务器收到了END数据包。例如,在主服务器关闭期间,用户明确地或当主服务器从重复的服务器UUID<%s>接收到binlog发送请求时,转储线程被终止:错误%s"

ER_RPL_MTA_STATISTICS
  eng "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"
  chinese "多线程从属统计信息%s:已用秒数=%lu；分配的事件=%llu；工作队列已填满溢出级别=%lu；因工作队列已满而等待=%lu；因总大小=%lu；等待时钟冲突=%llu当工作进程被占用时等待=%lu当工作进程被占用时等待=%llu"

ER_RPL_MTA_RECOVERY_COMPLETE
  eng "Replica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu."
  chinese "从%s:MTS恢复已在中继日志%s、位置%llu主日志%s、位置%llu完成。"

ER_RPL_REPLICA_CANT_INIT_RELAY_LOG_POSITION
  eng "Error initializing relay log position%s: %s"
  chinese "初始化中继日志位置%s时出错:%s"

OBSOLETE_ER_RPL_REPLICA_CONNECTED_TO_SOURCE_REPLICATION_STARTED
  eng "Replica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %s"
  chinese "从I/O线程%s:已连接到主'%s@%s:%d',复制已在日志'%s'中的位置%s开始"

ER_RPL_REPLICA_IO_THREAD_KILLED
  eng "Replica I/O thread%s killed while connecting to source"
  chinese "连接到主服务器时,从I/O线程%s被终止"

ER_RPL_REPLICA_IO_THREAD_CANT_REGISTER_ON_SOURCE
  eng "Replica I/O thread couldn't register on source"
  chinese "从属I/O线程无法在主服务器上注册"

ER_RPL_REPLICA_FORCING_TO_RECONNECT_IO_THREAD
  eng "Forcing to reconnect replica I/O thread%s"
  chinese "强制重新连接从属I/O线程%s"

ER_RPL_REPLICA_ERROR_REQUESTING_BINLOG_DUMP
  eng "Failed on request_dump()%s"
  chinese "REQUEST_DUMP()%s失败"

ER_RPL_LOG_ENTRY_EXCEEDS_REPLICA_MAX_ALLOWED_PACKET
  eng "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"
  chinese "主服务器上的日志条目比从属服务器上的REPLICATE_MAX_ALLOWED_PACKET(%lu)长。如果条目正确,请使用较高的REPLICATE_MAX_ALLOWED_PACKET值重新启动服务器"

ER_RPL_REPLICA_STOPPING_AS_SOURCE_OOM
  eng "Stopping replica I/O thread due to out-of-memory error from source"
  chinese "由于来自主服务器的内存不足错误,正在停止从I/O线程"

ER_RPL_REPLICA_IO_THREAD_ABORTED_WAITING_FOR_RELAY_LOG_SPACE
  eng "Replica I/O thread aborted while waiting for relay log space"
  chinese "从I/O线程在等待中继日志空间时中止"

ER_RPL_REPLICA_IO_THREAD_EXITING
  eng "Replica I/O thread exiting%s, read up to log '%s', position %s"
  chinese "从I/O线程正在退出%s,向上读取到日志'%s',位置%s"

ER_RPL_REPLICA_CANT_INITIALIZE_REPLICA_WORKER
  eng "Failed during replica worker initialization%s"
  chinese "从属工作进程初始化%s失败"

ER_RPL_MTA_GROUP_RECOVERY_APPLIER_METADATA_FOR_WORKER
  eng "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"
  chinese "从属:基于Worker-ID %lu、GROUP_RELAY_LOG_NAME %s、GROUP_RELAY_LOG_POS %llu、GROUP_SOURCE_LOG_NAME %s、GROUP_SOURCE_LOG_POS %llu的MTS组恢复中继日志信息"

ER_RPL_ERROR_LOOKING_FOR_LOG
  eng "Error looking for %s."
  chinese "查找%s时出错。"

ER_RPL_MTA_GROUP_RECOVERY_APPLIER_METADATA
  eng "Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu."
  chinese "从属:MTA组恢复中继日志信息GROUP_SOURCE_LOG_NAME%s,EVENT_SOURCE_LOG_POS%llu。"

ER_RPL_CANT_FIND_FOLLOWUP_FILE
  eng "Error looking for file after %s."
  chinese "在%s之后查找文件时出错。"

ER_RPL_MTA_CHECKPOINT_PERIOD_DIFFERS_FROM_CNT
  eng "This an error cnt != mta_checkpoint_period"
  chinese "这是一个错误！=MTA_CHECKPOINT_PERIOD"

ER_RPL_REPLICA_WORKER_THREAD_CREATION_FAILED
  eng "Failed during replica worker thread creation%s"
  chinese "创建从属工作线程%s时失败"

ER_RPL_REPLICA_WORKER_THREAD_CREATION_FAILED_WITH_ERRNO
  eng "Failed during replica worker thread creation%s (errno= %d)"
  chinese "创建从属工作线程%s时失败(错误号=%d)"

ER_RPL_REPLICA_FAILED_TO_INIT_PARTITIONS_HASH
  eng "Failed to init partitions hash"
  chinese "无法初始化分区哈希"

OBSOLETE_ER_RPL_SLAVE_NDB_TABLES_NOT_AVAILABLE
  eng "Replica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value"
  chinese "从属SQL线程:ndb:表在%lu秒后不可用。请考虑增加--ndb-wait-setup值"

ER_RPL_REPLICA_SQL_THREAD_STARTING
  eng "Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s"
  chinese "从属SQL线程%s已初始化,正在开始复制日志'%s'中的位置%s,中继日志'%s'的位置:%s"

ER_RPL_REPLICA_SKIP_COUNTER_EXECUTED
  eng "'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' "

ER_RPL_REPLICA_ADDITIONAL_ERROR_INFO_FROM_DA
  eng "Replica (additional info): %s Error_code: MY-%06d"
  chinese "从属(其他信息):%s错误代码:MY-%06d"

ER_RPL_REPLICA_ERROR_INFO_FROM_DA
  eng "Replica: %s Error_code: MY-%06d"
  chinese "从属:%s错误代码:MY-%06d"

ER_RPL_REPLICA_ERROR_LOADING_USER_DEFINED_LIBRARY
  eng "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"
  chinese "加载用户定义的库时出错,从SQL线程已中止。请安装缺少的库,然后使用\"START REPLICA\"重新启动从SQL线程。我们在日志'%s'位置%s处停止"

ER_RPL_REPLICA_ERROR_RUNNING_QUERY
  eng "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"
  chinese "运行查询时出错,从属SQL线程已中止。请解决此问题,然后使用\"START REPLICA\"重新启动从属SQL线程。我们在日志'%s'位置%s处停止"

ER_RPL_REPLICA_SQL_THREAD_EXITING
  eng "Replica SQL thread%s exiting, replication stopped in log '%s' at position %s"
  chinese "从SQL线程%s正在退出,复制在位置%s处的日志'%s'中停止"

ER_RPL_REPLICA_READ_INVALID_EVENT_FROM_SOURCE
  eng "Read invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bug"
  chinese "从主机读取无效事件:'%s',主可能已损坏,但更有可能的原因是错误"

ER_RPL_REPLICA_QUEUE_EVENT_FAILED_INVALID_CONFIGURATION
  eng "The queue event failed for channel '%s' as its configuration is invalid."
  chinese "通道'%s'的队列事件失败,因为其配置无效。"

ER_RPL_REPLICA_IO_THREAD_DETECTED_UNEXPECTED_EVENT_SEQUENCE
  eng "An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu."
  chinese "将主'%s'二进制日志文件从位置%llu的接收的事件排队时,IO线程检测到意外事件序列。"

ER_RPL_REPLICA_CANT_USE_CHARSET
  eng "'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source."
  chinese "'%s'不能用作客户端字符集。在连接到SOURCE时,'%s'将用作默认客户端字符集。"

ER_RPL_REPLICA_CONNECTED_TO_SOURCE_REPLICATION_RESUMED
  eng "Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %s"
  chinese "从属%s:已连接到主'%s@%s:%d',在日志'%s'中位置%s处恢复复制"

ER_RPL_REPLICA_NEXT_LOG_IS_ACTIVE
  eng "next log '%s' is active"
  chinese "下一个日志'%s'处于活动状态"

ER_RPL_REPLICA_NEXT_LOG_IS_INACTIVE
  eng "next log '%s' is not active"
  chinese "下一个日志'%s'处于非活动状态"

ER_RPL_REPLICA_SQL_THREAD_IO_ERROR_READING_EVENT
  eng "Replica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)"
  chinese "从SQL线程%s:读取事件时出现I/O错误(错误号:%d CUR_LOG->error:%d)"

ER_RPL_REPLICA_ERROR_READING_RELAY_LOG_EVENTS
  eng "Error reading relay log event%s: %s"
  chinese "读取中继日志事件%s时出错:%s"

ER_REPLICA_CHANGE_SOURCE_TO_EXECUTED
  eng "'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'."

ER_RPL_REPLICA_NEW_C_M_NEEDS_REPOS_TYPE_OTHER_THAN_FILE
  eng "Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources."
  chinese "从属:当资料库为文件类型时,无法创建新的主信息结构。请将从属资料库转换为表,以便从多个来源进行复制。"

ER_RPL_FAILED_TO_STAT_LOG_IN_INDEX
  eng "log %s listed in the index, but failed to stat."
  chinese "日志%s列在索引中,但无法统计。"

ER_RPL_LOG_NOT_FOUND_WHILE_COUNTING_RELAY_LOG_SPACE
  eng "Could not find first log while counting relay log space."
  chinese "在计算中继日志空间时找不到第一个日志。"

ER_REPLICA_CANT_USE_TEMPDIR
  eng "Unable to use replica's temporary directory '%s'."
  chinese "无法使用从属的临时目录'%s'。"

ER_RPL_RELAY_LOG_NEEDS_FILE_NOT_DIRECTORY
  eng "Path '%s' is a directory name, please specify a file name for --relay-log option."
  chinese "路径'%s'是一个目录名,请为--relay-log选项指定一个文件名。"

ER_RPL_RELAY_LOG_INDEX_NEEDS_FILE_NOT_DIRECTORY
  eng "Path '%s' is a directory name, please specify a file name for --relay-log-index option."
  chinese "路径'%s'是一个目录名,请为--relay-log-index选项指定一个文件名。"

ER_RPL_PLEASE_USE_OPTION_RELAY_LOG
  eng "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."
  chinese "既没有使用--relay-log,也没有使用--relay-log-index；因此,当此MySQL服务器充当从属服务器并更改主名时,复制可能会中断！！请使用'--relay-log=%s'来避免此问题。"

ER_RPL_OPEN_INDEX_FILE_FAILED
  eng "Failed in open_index_file() called from Relay_log_info::rli_init_info()."
  chinese "从RELAY_LOG_INFO::RLI_INIT_INFO()调用OPEN_INDEX_FILE()失败。"

ER_RPL_CANT_INITIALIZE_GTID_SETS_IN_AM_INIT_INFO
  eng "Failed in init_gtid_sets() called from Relay_log_info::rli_init_info()."
  chinese "从RELAY_LOG_INFO::RLI_INIT_INFO()调用init_gtid_sets()失败。"

ER_RPL_CANT_OPEN_LOG_IN_AM_INIT_INFO
  eng "Failed in open_log() called from Relay_log_info::rli_init_info()."
  chinese "从RELAY_LOG_INFO::RLI_INIT_INFO()调用OPEN_LOG()失败。"

ER_RPL_ERROR_WRITING_RELAY_LOG_CONFIGURATION
  eng "Error writing relay log configuration."
  chinese "写入中继日志配置时出错。"

OBSOLETE_ER_NDB_OOM_GET_NDB_BLOBS_VALUE
  eng "get_ndb_blobs_value: my_malloc(%u) failed"
  chinese "GET_NDB_BLOBS_VALUE:MY_Malloc(%u)失败"

OBSOLETE_ER_NDB_THREAD_TIMED_OUT
  eng "NDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u."
  chinese "NDB:线程ID%u超时(30s),等待处理纪元%u/%u。进度:%u/%u->%u/%u。"

OBSOLETE_ER_NDB_TABLE_IS_NOT_DISTRIBUTED
  eng "NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributed"
  chinese "NDB:在分布式权限表中检测到不一致。表'%s.%s'未分发"

OBSOLETE_ER_NDB_CREATING_TABLE
  eng "NDB: Creating %s.%s"
  chinese "NDB:正在创建%s.%s"

OBSOLETE_ER_NDB_FLUSHING_TABLE_INFO
  eng "NDB: Flushing %s.%s"
  chinese "NDB:刷新%s.%s"

OBSOLETE_ER_NDB_CLEANING_STRAY_TABLES
  eng "NDB: Cleaning stray tables from database '%s'"
  chinese "NDB:正在清除数据库'%s'中的杂乱表"

OBSOLETE_ER_NDB_DISCOVERED_MISSING_DB
  eng "NDB: Discovered missing database '%s'"
  chinese "NDB:发现缺少数据库'%s'"

OBSOLETE_ER_NDB_DISCOVERED_REMAINING_DB
  eng "NDB: Discovered remaining database '%s'"
  chinese "NDB:发现剩余的数据库'%s'"

OBSOLETE_ER_NDB_CLUSTER_FIND_ALL_DBS_RETRY
  eng "NDB: ndbcluster_find_all_databases retry: %u - %s"
  chinese "NDB:nDBCLUSTER_FIND_ALL_DATABASES重试:%u-%s"

OBSOLETE_ER_NDB_CLUSTER_FIND_ALL_DBS_FAIL
  eng "NDB: ndbcluster_find_all_databases fail: %u - %s"
  chinese "NDB:nDBCLUSTER_FIND_ALL_DATABASES失败:%u-%s"

OBSOLETE_ER_NDB_SKIPPING_SETUP_TABLE
  eng "NDB: skipping setup table %s.%s, in state %d"
  chinese "NDB:正在跳过设置表%s.%s,状态为%d"

OBSOLETE_ER_NDB_FAILED_TO_SET_UP_TABLE
  eng "NDB: failed to setup table %s.%s, error: %d, %s"
  chinese "NDB:无法设置表%s.%s,错误:%d,%s"

OBSOLETE_ER_NDB_MISSING_FRM_DISCOVERING
  eng "NDB: missing frm for %s.%s, discovering..."
  chinese "NDB:缺少%s.%s的FRM,正在发现..."

OBSOLETE_ER_NDB_MISMATCH_IN_FRM_DISCOVERING
  eng "NDB: mismatch in frm for %s.%s, discovering..."
  chinese "NDB:%s.%s的FRM不匹配,正在发现..."

OBSOLETE_ER_NDB_BINLOG_CLEANING_UP_SETUP_LEFTOVERS
  eng "ndb_binlog_setup: Clean up leftovers"
  chinese "NDB_BINLOG_SETUP:清理剩菜"

OBSOLETE_ER_NDB_WAITING_INFO
  eng "NDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s"
  chinese "NDB%s:最长%u秒正在等待%s%s的。期间:(%u/%u,%u/%u,%u/%u)注入器proc_info:%s"

OBSOLETE_ER_NDB_WAITING_INFO_WITH_MAP
  eng "NDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08x"
  chinese "NDB%s:最长%u秒正在等待%s%s的。期间:(%u/%u,%u/%u,%u/%u)注入器proc_info:%s映射:%x%08x"

OBSOLETE_ER_NDB_TIMEOUT_WHILE_DISTRIBUTING
  eng "NDB %s: distributing %s timed out. Ignoring..."
  chinese "NDB%s:分发%s超时。正在忽略..."

OBSOLETE_ER_NDB_NOT_WAITING_FOR_DISTRIBUTING
  eng "NDB %s: not waiting for distributing %s"
  chinese "NDB%s:未等待分发%s"

OBSOLETE_ER_NDB_DISTRIBUTED_INFO
  eng "NDB: distributed %s.%s(%u/%u) type: %s(%u) query: \'%s\' to %x%08x"
  chinese "NDB:分布式%s.%s(%u/%u)类型:%s(%u)查询:\'%s\'到%x%08x"

OBSOLETE_ER_NDB_DISTRIBUTION_COMPLETE
  eng "NDB: distribution of %s.%s(%u/%u) type: %s(%u) query: \'%s\' - complete!"
  chinese "NDB:分发%s.%s(%u/%u)类型:%s(%u)查询:\'%s\'-完成！"

OBSOLETE_ER_NDB_SCHEMA_DISTRIBUTION_FAILED
  eng "NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08x"
  chinese "NDB架构位置:数据节点:%d失败,订阅服务器位掩码%x%08x"

OBSOLETE_ER_NDB_SCHEMA_DISTRIBUTION_REPORTS_SUBSCRIBE
  eng "NDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08x"
  chinese "NDB架构位置:数据节点:%d报告订阅自节点%d,订阅方位掩码%x%08x"

OBSOLETE_ER_NDB_SCHEMA_DISTRIBUTION_REPORTS_UNSUBSCRIBE
  eng "NDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08x"
  chinese "NDB架构位置:数据节点:%d报告取消订阅节点%d,订阅方位掩码%x%08x"

OBSOLETE_ER_NDB_BINLOG_CANT_DISCOVER_TABLE_FROM_SCHEMA_EVENT
  eng "NDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %d"
  chinese "NDB Binlog:无法发现表'%s.%s'架构事件'%s'中从节点%d的binlog。my_errno:%d"

OBSOLETE_ER_NDB_BINLOG_SIGNALLING_UNKNOWN_VALUE
  eng "NDB: unknown value for binlog signalling 0x%X, %s not logged"
  chinese "NDB:binlog信令0x%X的未知值,%s未记录"

OBSOLETE_ER_NDB_BINLOG_REPLY_TO
  eng "NDB: reply to %s.%s(%u/%u) from %s to %x%08x"
  chinese "NDB:答复%s.%s(%u/%u)从%s到%x%08x"

OBSOLETE_ER_NDB_BINLOG_CANT_RELEASE_SLOCK
  eng "NDB: Could not release slock on '%s.%s', Error code: %d Message: %s"
  chinese "NDB:无法在'%s.%s'上释放锁,错误代码:%d消息:%s"

OBSOLETE_ER_NDB_CANT_FIND_TABLE
  eng "NDB schema: Could not find table '%s.%s' in NDB"
  chinese "NDB架构:在NDB中找不到表'%s.%s'"

OBSOLETE_ER_NDB_DISCARDING_EVENT_NO_OBJ
  eng "NDB: Discarding event...no obj: %s (%u/%u)"
  chinese "NDB:正在丢弃事件...无对象:%s(%u/%u)"

OBSOLETE_ER_NDB_DISCARDING_EVENT_ID_VERSION_MISMATCH
  eng "NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]"
  chinese "NDB:正在丢弃事件...密钥:%s ID/版本[%u/%u]不匹配！=[%u/%u]"

OBSOLETE_ER_NDB_CLEAR_SLOCK_INFO
  eng "NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08x"
  chinese "NDB:CLEAR_SLOCK密钥:%s(%u/%u)%x%08x,从%s到%x%08x"

OBSOLETE_ER_NDB_BINLOG_SKIPPING_LOCAL_TABLE
  eng "NDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d."
  chinese "NDB Binlog:正在跳过本地定义的表'%s.%s',该表来自binlog架构事件'%s'(来自节点%d)。"

OBSOLETE_ER_NDB_BINLOG_ONLINE_ALTER_RENAME
  eng "NDB Binlog: handling online alter/rename"
  chinese "NDB Binlog:处理联机更改/重命名"

OBSOLETE_ER_NDB_BINLOG_CANT_REOPEN_SHADOW_TABLE
  eng "NDB Binlog: Failed to re-open shadow table %s.%s"
  chinese "NDB Binlog:无法重新打开影子表%s。%s"

OBSOLETE_ER_NDB_BINLOG_ONLINE_ALTER_RENAME_COMPLETE
  eng "NDB Binlog: handling online alter/rename done"
  chinese "NDB Binlog:处理联机更改/重命名已完成"

OBSOLETE_ER_NDB_BINLOG_SKIPPING_DROP_OF_LOCAL_TABLE
  eng "NDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. "
  chinese "NDB Binlog:正在跳过删除本地定义的表'%s.%s'(binlog架构事件'%s'来自节点%d的)。"

OBSOLETE_ER_NDB_BINLOG_SKIPPING_RENAME_OF_LOCAL_TABLE
  eng "NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. "
  chinese "NDB Binlog:正在跳过重命名本地定义的表'%s.%s'(binlog架构事件'%s'来自节点%d的)。"

OBSOLETE_ER_NDB_BINLOG_SKIPPING_DROP_OF_TABLES
  eng "NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. "
  chinese "NDB Binlog:正在跳过删除数据库'%s',因为它包含本地表Binlog架构事件'%s'来自节点%d的。"

OBSOLETE_ER_NDB_BINLOG_GOT_DIST_PRIV_EVENT_FLUSHING_PRIVILEGES
  eng "Got dist_priv event: %s, flushing privileges"
  chinese "获取dist_prv事件:%s,刷新权限"

OBSOLETE_ER_NDB_BINLOG_GOT_SCHEMA_EVENT
  eng "NDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08x"
  chinese "NDB:在%s上获取架构事件。%s(%u/%u)查询:'%s'类型:%s(%d)节点:%u块:%x%08x"

OBSOLETE_ER_NDB_BINLOG_SKIPPING_OLD_SCHEMA_OPERATION
  eng "NDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%s"
  chinese "NDB架构:正在跳过%s上的旧架构操作(RENAME_TABLE_NEW)。%s"

OBSOLETE_ER_NDB_CLUSTER_FAILURE
  eng "NDB Schema dist: cluster failure at epoch %u/%u."
  chinese "NDB架构分布:在纪元%u/%u出现群集故障。"

OBSOLETE_ER_NDB_TABLES_INITIALLY_READ_ONLY_ON_RECONNECT
  eng "NDB Binlog: ndb tables initially read only on reconnect."
  chinese "NDB Binlog:NDB表在重新连接时最初是只读的。"

OBSOLETE_ER_NDB_IGNORING_UNKNOWN_EVENT
  eng "NDB Schema dist: unknown event %u, ignoring..."
  chinese "NDB架构分布:未知事件%u,正在忽略..."

OBSOLETE_ER_NDB_BINLOG_OPENING_INDEX
  eng "NDB Binlog: Opening ndb_binlog_index: %d, '%s'"
  chinese "NDB Binlog:正在打开NDB_BINLOG_INDEX:%d,'%s'"

OBSOLETE_ER_NDB_BINLOG_CANT_LOCK_NDB_BINLOG_INDEX
  eng "NDB Binlog: Unable to lock table ndb_binlog_index"
  chinese "NDB Binlog:无法锁定表NDB_BINLOG_INDEX"

OBSOLETE_ER_NDB_BINLOG_INJECTING_RANDOM_WRITE_FAILURE
  eng "NDB Binlog: Injecting random write failure"
  chinese "NDB Binlog:注入随机写入失败"

OBSOLETE_ER_NDB_BINLOG_CANT_WRITE_TO_NDB_BINLOG_INDEX
  eng "NDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d."
  chinese "NDB Binlog:写入纪元%u/%u的ndb_binlog_index失败,orig_server_id %u orig_epoch %u/%u,错误为%d。"

OBSOLETE_ER_NDB_BINLOG_WRITING_TO_NDB_BINLOG_INDEX
  eng "NDB Binlog: Writing row (%s) to ndb_binlog_index - %s"
  chinese "NDB Binlog:正在将行(%s)写入ndb_binlog_index-%s"

OBSOLETE_ER_NDB_BINLOG_CANT_COMMIT_TO_NDB_BINLOG_INDEX
  eng "NDB Binlog: Failed committing transaction to ndb_binlog_index with error %d."
  chinese "NDB Binlog:无法将事务提交到NDB_BINLOG_INDEX,错误为%d。"

OBSOLETE_ER_NDB_BINLOG_WRITE_INDEX_FAILED_AFTER_KILL
  eng "NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdown"
  chinese "NDB Binlog:在关闭期间删除后重试时,无法写入NDB_BINLOG_INDEX表"

OBSOLETE_ER_NDB_BINLOG_USING_SERVER_ID_0_SLAVES_WILL_NOT
  eng "NDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqlds"
  chinese "NDB: server id设置为零-记录到server id为零的bin日志的更改将由从mysqlds用另一个server id记录"

OBSOLETE_ER_NDB_SERVER_ID_RESERVED_OR_TOO_LARGE
  eng "NDB: server id provided is too large to be represented in opt_server_id_bits or is reserved"
  chinese "NDB:提供的服务器ID太大,无法在opt_server_id_bit中表示或已保留"

OBSOLETE_ER_NDB_BINLOG_REQUIRES_V2_ROW_EVENTS
  eng "NDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1."
  chinese "ndb:--ndb-log-Transaction-id需要v2 Binlog行事件,但服务器正在使用v1。"

OBSOLETE_ER_NDB_BINLOG_STATUS_FORCING_FULL_USE_WRITE
  eng "NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITE"
  chinese "NDB:NDB-LOG-APPLY-STATUS正在强制%s.%s完全使用_写入"

OBSOLETE_ER_NDB_BINLOG_GENERIC_MESSAGE
  eng "NDB Binlog: %s"
  chinese "NDB Binlog:%s"

OBSOLETE_ER_NDB_CONFLICT_GENERIC_MESSAGE
  eng "%s"
  chinese "%s"

OBSOLETE_ER_NDB_TRANS_DEPENDENCY_TRACKER_ERROR
  eng "%s"
  chinese "%s"

OBSOLETE_ER_NDB_CONFLICT_FN_PARSE_ERROR
  eng "NDB Replica: Table %s.%s : Parse error on conflict fn : %s"
  chinese "NDB从属:表%s.%s:冲突fn上的分析错误:%s"

OBSOLETE_ER_NDB_CONFLICT_FN_SETUP_ERROR
  eng "NDB Replica: Table %s.%s : %s"
  chinese "NDB从属:表%s.%s:%s"

OBSOLETE_ER_NDB_BINLOG_FAILED_TO_GET_TABLE
  eng "NDB Binlog: Failed to get table %s from ndb: %s, %d"
  chinese "NDB Binlog:无法从NDB获取表%s:%s,%d"

OBSOLETE_ER_NDB_BINLOG_NOT_LOGGING
  eng "NDB Binlog: NOT logging %s"
  chinese "NDB Binlog:未记录%s"

OBSOLETE_ER_NDB_BINLOG_CREATE_TABLE_EVENT_FAILED
  eng "NDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %s"
  chinese "NDB Binlog:创建(发现)表事件失败:%s"

OBSOLETE_ER_NDB_BINLOG_CREATE_TABLE_EVENT_INFO
  eng "NDB Binlog: CREATE (DISCOVER) TABLE Event: %s"
  chinese "NDB Binlog:创建(发现)表事件:%s"

OBSOLETE_ER_NDB_BINLOG_DISCOVER_TABLE_EVENT_INFO
  eng "NDB Binlog: DISCOVER TABLE Event: %s"
  chinese "NDB Binlog:发现表事件:%s"

OBSOLETE_ER_NDB_BINLOG_BLOB_REQUIRES_PK
  eng "NDB Binlog: logging of table %s with BLOB attribute and no PK is not supported"
  chinese "NDB Binlog:不支持记录具有BLOB属性但没有PK的表%s"

OBSOLETE_ER_NDB_BINLOG_CANT_CREATE_EVENT_IN_DB
  eng "NDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %s"
  chinese "NDB Binlog:无法在数据库中创建事件。事件:%s错误代码:%d消息:%s"

OBSOLETE_ER_NDB_BINLOG_CANT_CREATE_EVENT_IN_DB_AND_CANT_DROP
  eng "NDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %s"
  chinese "NDB Binlog:无法在数据库中创建事件。尝试使用DROP更正失败。事件:%s错误代码:%d消息:%s"

OBSOLETE_ER_NDB_BINLOG_CANT_CREATE_EVENT_IN_DB_DROPPED
  eng "NDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %s"
  chinese "NDB Binlog:无法在数据库中创建事件。尝试使用DROP OK更正,但CREATE失败。事件:%s错误代码:%d消息:%s"

OBSOLETE_ER_NDB_BINLOG_DISCOVER_REUSING_OLD_EVENT_OPS
  eng "NDB Binlog: discover reusing old ev op"
  chinese "NDB Binlog:发现重复使用旧的EV操作"

OBSOLETE_ER_NDB_BINLOG_CREATING_NDBEVENTOPERATION_FAILED
  eng "NDB Binlog: Creating NdbEventOperation failed for %s"
  chinese "NDB Binlog:为%s创建NdbEventOperation失败"

OBSOLETE_ER_NDB_BINLOG_CANT_CREATE_BLOB
  eng "NDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %s"
  chinese "NDB Binlog:创建字段%u NdbEventOperation Blob(代码=%d)句柄失败为%s"

OBSOLETE_ER_NDB_BINLOG_NDBEVENT_EXECUTE_FAILED
  eng "NDB Binlog: ndbevent->execute failed for %s; %d %s"
  chinese "NDB Binlog:ndbevent%s的执行失败；%d%s"

OBSOLETE_ER_NDB_CREATE_EVENT_OPS_LOGGING_INFO
  eng "NDB Binlog: logging %s (%s,%s)"
  chinese "NDB Binlog:记录%s(%s,%s)"

OBSOLETE_ER_NDB_BINLOG_CANT_DROP_EVENT_FROM_DB
  eng "NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %s"
  chinese "NDB Binlog:无法删除数据库中的事件。事件:%s错误代码:%d消息:%s"

OBSOLETE_ER_NDB_TIMED_OUT_IN_DROP_TABLE
  eng "NDB %s: %s timed out. Ignoring..."
  chinese "NDB%s:%s超时。正在忽略..."

OBSOLETE_ER_NDB_BINLOG_UNHANDLED_ERROR_FOR_TABLE
  eng "NDB Binlog: unhandled error %d for table %s"
  chinese "NDB Binlog:未处理错误%d 表%s的"

OBSOLETE_ER_NDB_BINLOG_CLUSTER_FAILURE
  eng "NDB Binlog: cluster failure for %s at epoch %u/%u."
  chinese "NDB Binlog:%s在时期%u/%u的群集故障。"

OBSOLETE_ER_NDB_BINLOG_UNKNOWN_NON_DATA_EVENT
  eng "NDB Binlog: unknown non data event %d for %s. Ignoring..."
  chinese "NDB Binlog:未知非数据事件%d %s的。正在忽略..."

OBSOLETE_ER_NDB_BINLOG_INJECTOR_DISCARDING_ROW_EVENT_METADATA
  eng "NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)"
  chinese "NDB:绑定日志注入器正在丢弃行事件元数据,因为服务器正在使用v1行事件。(%u%x)"

OBSOLETE_ER_NDB_REMAINING_OPEN_TABLES
  eng "remove_all_event_operations: Remaining open tables: "
  chinese "REMOVE_ALL_EVENT_OPERATIONS:其余打开的表:"

OBSOLETE_ER_NDB_REMAINING_OPEN_TABLE_INFO
  eng "  %s.%s, use_count: %u"
  chinese "  %s.%s, use_count: %u"

OBSOLETE_ER_NDB_COULD_NOT_GET_APPLY_STATUS_SHARE
  eng "NDB: Could not get apply status share"
  chinese "NDB:无法获取应用状态共享"

OBSOLETE_ER_NDB_BINLOG_SERVER_SHUTDOWN_DURING_NDB_CLUSTER_START
  eng "NDB Binlog: Server shutdown detected while waiting for ndbcluster to start..."
  chinese "NDB Binlog:在等待ndb群集启动时检测到服务器关闭..."

OBSOLETE_ER_NDB_BINLOG_CLUSTER_RESTARTED_RESET_MASTER_SUGGESTED
  eng "NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET BINARY LOGS AND GTIDS should be issued. Resetting ndb_latest_handled_binlog_epoch."

OBSOLETE_ER_NDB_BINLOG_CLUSTER_HAS_RECONNECTED
  eng "NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlog"
  chinese "NDB Binlog:群集已重新连接。在断开连接时对数据库所做的更改将不会记录在binlog中"

OBSOLETE_ER_NDB_BINLOG_STARTING_LOG_AT_EPOCH
  eng "NDB Binlog: starting log at epoch %u/%u"
  chinese "NDB Binlog:在纪元%u/%u开始日志"

OBSOLETE_ER_NDB_BINLOG_NDB_TABLES_WRITABLE
  eng "NDB Binlog: ndb tables writable"
  chinese "NDB Binlog:NDB表可写"

OBSOLETE_ER_NDB_BINLOG_SHUTDOWN_DETECTED
  eng "NDB Binlog: Server shutdown detected..."
  chinese "NDB Binlog:检测到服务器关闭..."

OBSOLETE_ER_NDB_BINLOG_LOST_SCHEMA_CONNECTION_WAITING
  eng "NDB Binlog: Just lost schema connection, hanging around"
  chinese "NDB Binlog:刚刚失去架构连接,挂起"

OBSOLETE_ER_NDB_BINLOG_LOST_SCHEMA_CONNECTION_CONTINUING
  eng "NDB Binlog: ...and on our way"
  chinese "NDB Binlog:……在我们的路上"

OBSOLETE_ER_NDB_BINLOG_ERROR_HANDLING_SCHEMA_EVENT
  eng "NDB: error %lu (%s) on handling binlog schema event"
  chinese "NDB:处理binlog架构事件时出现错误%lu(%s)"

OBSOLETE_ER_NDB_BINLOG_CANT_INJECT_APPLY_STATUS_WRITE_ROW
  eng "NDB Binlog: Failed to inject apply status write row"
  chinese "NDB Binlog:无法注入应用状态写入行"

OBSOLETE_ER_NDB_BINLOG_ERROR_DURING_GCI_ROLLBACK
  eng "NDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %d"
  chinese "NDB Binlog:回滚GCI%u/%u时出错。错误:%d"

OBSOLETE_ER_NDB_BINLOG_ERROR_DURING_GCI_COMMIT
  eng "NDB Binlog: Error during COMMIT of GCI. Error: %d"
  chinese "NDB Binlog:提交GCI时出错。错误:%d"

OBSOLETE_ER_NDB_BINLOG_LATEST_TRX_IN_EPOCH_NOT_IN_BINLOG
  eng "NDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%u"
  chinese "NDB Binlog:在纪元%u/%u中的最新事务不在binlog中,因为最新处理的纪元为%u/%u"

OBSOLETE_ER_NDB_BINLOG_RELEASING_EXTRA_SHARE_REFERENCES
  eng "NDB Binlog: Release extra share references"
  chinese "NDB Binlog:释放额外的共享引用"

OBSOLETE_ER_NDB_BINLOG_REMAINING_OPEN_TABLES
  eng "NDB Binlog: remaining open tables: "
  chinese "NDB Binlog:剩余打开的表:"

OBSOLETE_ER_NDB_BINLOG_REMAINING_OPEN_TABLE_INFO
  eng "  %s.%s state: %u use_count: %u"
  chinese "  %s.%s state: %u use_count: %u"

ER_TREE_CORRUPT_PARENT_SHOULD_POINT_AT_PARENT
  eng "Wrong tree: Parent doesn't point at parent"
  chinese "错误的树:父级没有指向父级"

ER_TREE_CORRUPT_ROOT_SHOULD_BE_BLACK
  eng "Wrong tree: Root should be black"
  chinese "错误的树:根应该是黑色的"

ER_TREE_CORRUPT_2_CONSECUTIVE_REDS
  eng "Wrong tree: Found two red in a row"
  chinese "错误的树:连续发现两棵红色的树"

ER_TREE_CORRUPT_RIGHT_IS_LEFT
  eng "Wrong tree: Found right == left"
  chinese "错误的树:找到右==左"

ER_TREE_CORRUPT_INCORRECT_BLACK_COUNT
  eng "Wrong tree: Incorrect black-count: %d - %d"
  chinese "错误的树:不正确的黑色计数:%d-%d"

ER_WRONG_COUNT_FOR_ORIGIN
  eng "Use_count: Wrong count %lu for origin %p"

ER_WRONG_COUNT_FOR_KEY
  eng "Use_count: Wrong count for key at %p, %lu should be %lu"
  chinese "USE_COUNT:%p处的密钥计数错误,%lu应为%lu"

ER_WRONG_COUNT_OF_ELEMENTS
  eng "Wrong number of elements: %u (should be %u) for tree at %p"

ER_RPL_ERROR_READING_REPLICA_WORKER_CONFIGURATION
  eng "Error reading replica worker configuration"
  chinese "读取从属Worker配置时出错"

OBSOLETE_ER_RPL_ERROR_WRITING_SLAVE_WORKER_CONFIGURATION
  eng "Error writing replica worker configuration"
  chinese "写入从属Worker配置时出错"

ER_RPL_FAILED_TO_OPEN_RELAY_LOG
  eng "Failed to open relay log %s, error: %s"
  chinese "无法打开中继日志%s,错误:%s"

ER_RPL_WORKER_CANT_READ_RELAY_LOG
  eng "Error when worker read relay log events,relay log name %s, position %llu"
  chinese "Worker读取中继日志事件时出错,中继日志名称%s,位置%llu"

ER_RPL_WORKER_CANT_FIND_NEXT_RELAY_LOG
  eng "Failed to find next relay log when retrying the transaction, current relay log is %s"
  chinese "重试事务时找不到下一个中继日志,当前的中继日志为%s"

ER_RPL_MTA_REPLICA_COORDINATOR_HAS_WAITED
  eng "Multi-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu."
  chinese "多线程从属:协调程序已等待%lu次达到REPLICAT_PENDING_JOBS_SIZE_MAX；当前事件大小=%zu。"

ER_BINLOG_FAILED_TO_WRITE_DROP_FOR_TEMP_TABLES
  eng "Failed to write the DROP statement for temporary tables to binary log"
  chinese "无法将临时表的DROP语句写入二进制日志"

ER_BINLOG_OOM_WRITING_DELETE_WHILE_OPENING_HEAP_TABLE
  eng "When opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary log"
  chinese "打开堆表时,无法分配内存以将'DELETE FROM`%s`.`%s`'写入二进制日志"

ER_FAILED_TO_REPAIR_TABLE
  eng "Couldn't repair table: %s.%s"
  chinese "无法修复表:%s.%s"

ER_FAILED_TO_REMOVE_TEMP_TABLE
  eng "Could not remove temporary table: '%s', error: %d"
  chinese "无法删除临时表:'%s',错误:%d"

ER_SYSTEM_TABLE_NOT_TRANSACTIONAL
  eng "System table '%.*s' is expected to be transactional."
  chinese "系统表'%.*s'应该是事务性的。"

ER_RPL_ERROR_WRITING_SOURCE_CONFIGURATION
  eng "Error writing source configuration."
  chinese "写入主配置时出错。"

ER_RPL_ERROR_READING_SOURCE_CONFIGURATION
  eng "Error reading source configuration."
  chinese "读取主配置时出错。"

ER_RPL_SSL_INFO_IN_CONNECTION_METADATA_IGNORED
  eng "SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support."
  chinese "主信息文件中的SSL信息被忽略,因为此MySQL从属程序是在没有SSL支持的情况下编译的。"

ER_PLUGIN_FAILED_DEINITIALIZATION
  eng "Plugin '%s' of type %s failed deinitialization"
  chinese "%s类型的插件'%s'取消初始化失败"

ER_PLUGIN_HAS_NONZERO_REFCOUNT_AFTER_DEINITIALIZATION
  eng "Plugin '%s' has ref_count=%d after deinitialization."
  chinese "取消初始化后,插件'%s'的ref_count=%d。"

ER_PLUGIN_SHUTTING_DOWN_PLUGIN
  eng "Shutting down plugin '%s'"
  chinese "正在关闭插件'%s'"

ER_PLUGIN_REGISTRATION_FAILED
  eng "Plugin '%s' registration as a %s failed."
  chinese "插件'%s'注册为%s失败。"

ER_PLUGIN_CANT_OPEN_PLUGIN_TABLE
  eng "Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure."
  chinese "无法打开mysql.plugin表。请执行MySQL升级过程。"

ER_PLUGIN_CANT_LOAD
  eng "Couldn't load plugin named '%s' with soname '%s'."
  chinese "无法加载名为'%s'、名为'%s'的插件。"

ER_PLUGIN_LOAD_PARAMETER_TOO_LONG
  eng "plugin-load parameter too long"
  chinese "插件-加载参数太长"

ER_PLUGIN_FORCING_SHUTDOWN
  eng "Plugin '%s' will be forced to shutdown"
  chinese "插件'%s'将被强制关闭"

ER_PLUGIN_HAS_NONZERO_REFCOUNT_AFTER_SHUTDOWN
  eng "Plugin '%s' has ref_count=%d after shutdown."
  chinese "插件'%s'关闭后ref_count=%d。"

ER_PLUGIN_UNKNOWN_VARIABLE_TYPE
  eng "Unknown variable type code 0x%x in plugin '%s'."
  chinese "未知变量类型代码0x%x(在插件'%s'中)。"

ER_PLUGIN_VARIABLE_SET_READ_ONLY
  eng "Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag"
  chinese "插件%s的服务器变量%s被强制为只读:没有UPDATE_FUNC和PLUGIN_VAR_MEMALLOC标志的字符串变量"

ER_PLUGIN_VARIABLE_MISSING_NAME
  eng "Missing variable name in plugin '%s'."
  chinese "插件'%s'中缺少变量名。"

ER_PLUGIN_VARIABLE_NOT_ALLOCATED_THREAD_LOCAL
  eng "Thread local variable '%s' not allocated in plugin '%s'."
  chinese "未在插件'%s'中分配线程局部变量'%s'。"

ER_PLUGIN_OOM
  eng "Out of memory for plugin '%s'."
  chinese "插件'%s'内存不足。"

ER_PLUGIN_BAD_OPTIONS
  eng "Bad options for plugin '%s'."
  chinese "插件'%s'的选项不正确。"

ER_PLUGIN_PARSING_OPTIONS_FAILED
  eng "Parsing options for plugin '%s' failed."
  chinese "分析插件'%s'的选项失败。"

ER_PLUGIN_DISABLED
  eng "Plugin '%s' is disabled."
  chinese "插件'%s'被禁用。"

ER_PLUGIN_HAS_CONFLICTING_SYSTEM_VARIABLES
  eng "Plugin '%s' has conflicting system variables"
  chinese "插件'%s'具有冲突的系统变量"

ER_PLUGIN_CANT_SET_PERSISTENT_OPTIONS
  eng "Setting persistent options for plugin '%s' failed."
  chinese "为插件'%s'设置永久选项失败。"

ER_MY_NET_WRITE_FAILED_FALLING_BACK_ON_STDERR
  eng "Failed on my_net_write, writing to stderr instead: %s"
  chinese "写入MY_NET_WRITE失败,改为写入标准错误:%s"

ER_RETRYING_REPAIR_WITHOUT_QUICK
  eng "Retrying repair of: '%s' without quick"
  chinese "正在重试修复:'%s'而不使用快速"

ER_RETRYING_REPAIR_WITH_KEYCACHE
  eng "Retrying repair of: '%s' with keycache"
  chinese "正在使用密钥缓存重试修复:'%s'"

ER_FOUND_ROWS_WHILE_REPAIRING
  eng "Found %s of %s rows when repairing '%s'"
  chinese "在修复'%s'时找到%s行,共%s行"

ER_ERROR_DURING_OPTIMIZE_TABLE
  eng "Warning: Optimize table got errno %d on %s.%s, retrying"
  chinese "警告:错误号%d优化表在%s.%s,正在重试"

ER_ERROR_ENABLING_KEYS
  eng "Warning: Enabling keys got errno %d on %s.%s, retrying"
  chinese "警告:错误号%d启用密钥在%s.%s,正在重试"

ER_CHECKING_TABLE
  eng "Checking table:   '%s'"
  chinese "检查表:'%s'"

ER_RECOVERING_TABLE
  eng "Recovering table: '%s'"
  chinese "正在恢复表:'%s'"

ER_CANT_CREATE_TABLE_SHARE_FROM_FRM
  eng "Error in creating TABLE_SHARE from %s.frm file."
  chinese "从%s.frm文件创建TABLE_SHARE时出错。"

ER_CANT_LOCK_TABLE
  eng "Unable to acquire lock on %s.%s"
  chinese "无法获取%s上的锁。%s"

ER_CANT_ALLOC_TABLE_OBJECT
  eng "Error in allocation memory for TABLE object."
  chinese "为表对象分配内存时出错。"

ER_CANT_CREATE_HANDLER_OBJECT_FOR_TABLE
  eng "Error in creating handler object for table %s.%s"
  chinese "为表%s创建处理程序对象时出错。%s"

ER_CANT_SET_HANDLER_REFERENCE_FOR_TABLE
  eng "Error in setting handler reference for table %s.%s"
  chinese "设置表%s的处理程序引用时出错。%s"

ER_CANT_LOCK_TABLESPACE
  eng "Unable to acquire lock on tablespace name %s"
  chinese "无法获取表空间名称%s上的锁"

ER_CANT_UPGRADE_GENERATED_COLUMNS_TO_DD
  eng "Error in processing generated columns for table %s.%s"
  chinese "处理为表%s生成的列时出错。%s"

ER_DD_ERROR_CREATING_ENTRY
  eng "Error in Creating DD entry for %s.%s"
  chinese "为%s.%s创建DD条目时出错。"

ER_DD_CANT_FETCH_TABLE_DATA
  eng "Error in fetching %s.%s table data from dictionary"
  chinese "从词典获取%s.%s表数据时出错"

ER_DD_CANT_FIX_SE_DATA
  eng "Error in fixing SE data for %s.%s"
  chinese "修复%s.%s的SE数据时出错。"

ER_DD_CANT_CREATE_SP
  eng "Error in creating stored program '%s.%s'"
  chinese "创建存储程序'%s.%s'时出错"

ER_CANT_OPEN_DB_OPT_USING_DEFAULT_CHARSET
  eng "Unable to open db.opt file %s. Using default Character set."
  chinese "无法打开数据库.opt文件%s。使用默认字符集。"

ER_CANT_CREATE_CACHE_FOR_DB_OPT
  eng "Unable to intialize IO cache to open db.opt file %s. "
  chinese "无法初始化IO缓存以打开数据库.opt文件%s。"

ER_CANT_IDENTIFY_CHARSET_USING_DEFAULT
  eng "Unable to identify the charset in %s. Using default character set."
  chinese "无法识别%s中的字符集。使用默认字符集。"

ER_DB_OPT_NOT_FOUND_USING_DEFAULT_CHARSET
  eng "db.opt file not found for %s database. Using default Character set."
  chinese "找不到%s数据库的db.opt文件。正在使用默认字符集。"

ER_EVENT_CANT_GET_TIMEZONE_FROM_FIELD
  eng "Event '%s'.'%s': invalid value in column mysql.event.time_zone."
  chinese "事件'%s'.'%s':列mysql.vent.time_zone中的值无效。"

ER_EVENT_CANT_FIND_TIMEZONE
  eng "Event '%s'.'%s': has invalid time zone value "
  chinese "事件'%s'.'%s':时区值无效"

ER_EVENT_CANT_GET_CHARSET
  eng "Event '%s'.'%s': invalid value in column mysql.event.character_set_client."
  chinese "事件'%s'.'%s':列mysql.event.Character_Set_Client中的值无效。"

ER_EVENT_CANT_GET_COLLATION
  eng "Event '%s'.'%s': invalid value in column mysql.event.collation_connection."
  chinese "事件'%s'.'%s':列mySQL_Event.Colation_Connection中的值无效。"

ER_EVENT_CANT_OPEN_TABLE_MYSQL_EVENT
  eng "Failed to open mysql.event Table."
  chinese "无法打开mysql.Event表。"

ER_CANT_PARSE_STORED_ROUTINE_BODY
  eng "Parsing '%s.%s' routine body failed.%s"
  chinese "分析'%s.%s'例程正文失败。%s"

ER_CANT_OPEN_TABLE_MYSQL_PROC
  eng "Failed to open mysql.proc Table."
  chinese "无法打开mysql.proc表。"

ER_CANT_READ_TABLE_MYSQL_PROC
  eng "Failed to read mysql.proc table."
  chinese "无法读取mysql.proc表。"

ER_FILE_EXISTS_DURING_UPGRADE
  eng "Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again."
  chinese "在MySQL架构中找到%s文件。DD将创建同名的.ibd文件。请重命名表并重新开始升级过程。"

ER_CANT_OPEN_DATADIR_AFTER_UPGRADE_FAILURE
  eng "Unable to open the data directory %s during clean up after upgrade failed"
  chinese "升级失败后,在清理过程中无法打开数据目录%s"

ER_CANT_SET_PATH_FOR
  eng "Failed to set path %s"
  chinese "无法设置路径%s"

ER_CANT_OPEN_DIR
  eng "Failed to open dir %s"
  chinese "无法打开目录%s"

OBSOLETE_ER_NDB_CLUSTER_CONNECTION_POOL_NODEIDS
  eng "NDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'."
  chinese "ndb:在--ndb-cluster-Connection-pool-nodeids='%s'中找到指定的空节点ID。"

OBSOLETE_ER_NDB_CANT_PARSE_NDB_CLUSTER_CONNECTION_POOL_NODEIDS
  eng "NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'."
  chinese "ndb:无法在--ndb-cluster-Connection-pool-nodeids='%s'中分析'%s'。"

OBSOLETE_ER_NDB_INVALID_CLUSTER_CONNECTION_POOL_NODEIDS
  eng "NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'."
  chinese "ndb:节点ID%d无效,位于--ndb-cluster-Connection-pool-nodeids='%s'中。"

OBSOLETE_ER_NDB_DUPLICATE_CLUSTER_CONNECTION_POOL_NODEIDS
  eng "NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'."
  chinese "ndb:发现重复的节点ID%d,位于--ndb-cluster-Connection-pool-nodeids='%s'。"

OBSOLETE_ER_NDB_POOL_SIZE_CLUSTER_CONNECTION_POOL_NODEIDS
  eng "NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'."
  chinese "ndb:群集连接池的大小必须等于--ndb-CLUSTER-CONNECTION-POOL-NODEID='%s'中的节点ID数。"

OBSOLETE_ER_NDB_NODEID_NOT_FIRST_CONNECTION_POOL_NODEIDS
  eng "NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'."
  chinese "ndb:--ndb-nodeid指定的nodeid必须等于--ndb-cluster-Connection-pool-nodeids='%s'中的第一个节点ID。"

OBSOLETE_ER_NDB_USING_NODEID
  eng "NDB: using nodeid %u"
  chinese "NDB:使用节点ID%u"

OBSOLETE_ER_NDB_CANT_ALLOC_GLOBAL_NDB_CLUSTER_CONNECTION
  eng "NDB: failed to allocate global ndb cluster connection"
  chinese "NDB:无法分配全局NDB群集连接"

OBSOLETE_ER_NDB_CANT_ALLOC_GLOBAL_NDB_OBJECT
  eng "NDB: failed to allocate global ndb object"
  chinese "NDB:无法分配全局NDB对象"

OBSOLETE_ER_NDB_USING_NODEID_LIST
  eng "NDB[%u]: using nodeid %u"
  chinese "NDB[%u]:使用节点ID %u"

OBSOLETE_ER_NDB_CANT_ALLOC_NDB_CLUSTER_CONNECTION
  eng "NDB[%u]: failed to allocate cluster connect object"
  chinese "NDB[%u]:无法分配群集连接对象"

OBSOLETE_ER_NDB_STARTING_CONNECT_THREAD
  eng "NDB[%u]: starting connect thread"
  chinese "NDB[%u]:正在启动连接线程"

OBSOLETE_ER_NDB_NODE_INFO
  eng "NDB[%u]: NodeID: %d, %s"
  chinese "NDB[%u]:节点ID:%d,%s"

OBSOLETE_ER_NDB_CANT_START_CONNECT_THREAD
  eng "NDB[%u]: failed to start connect thread"
  chinese "NDB[%u]:无法启动连接线程"

OBSOLETE_ER_NDB_GENERIC_ERROR
  eng "NDB: error (%u) %s"
  chinese "NDB:错误(%u)%s"

OBSOLETE_ER_NDB_CPU_MASK_TOO_SHORT
  eng "Ignored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs provided"
  chinese "已忽略接收线程CPU掩码,掩码太短,掩码中需要%u个CPU,仅提供%u个CPU"

ER_EVENT_ERROR_CREATING_QUERY_TO_WRITE_TO_BINLOG
  eng "Event Error: An error occurred while creating query string, before writing it into binary log."
  chinese "事件错误:在将查询字符串写入二进制日志之前,创建查询字符串时出错。"

ER_EVENT_SCHEDULER_ERROR_LOADING_FROM_DB
  eng "Event Scheduler: Error while loading from disk."
  chinese "事件计划程序:从磁盘加载时出错。"

ER_EVENT_SCHEDULER_ERROR_GETTING_EVENT_OBJECT
  eng "Event Scheduler: Error getting event object."
  chinese "事件计划程序:获取事件对象时出错。"

ER_EVENT_SCHEDULER_GOT_BAD_DATA_FROM_TABLE
  eng "Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corrupted"
  chinese "Event Scheduler:从mysql.event加载事件时出错。表可能包含错误数据或已损坏"

ER_EVENT_CANT_GET_LOCK_FOR_DROPPING_EVENT
  eng "Unable to obtain lock for dropping event %s from schema %s"
  chinese "无法获取从架构%s删除事件%s的锁定"

ER_EVENT_UNABLE_TO_DROP_EVENT
  eng "Unable to drop event %s from schema %s"
  chinese "无法从架构%s删除事件%s"

OBSOLETE_ER_BINLOG_ATTACHING_THREAD_MEMORY_FINALLY_AVAILABLE
  eng "Server overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase."
  chinese "服务器在组提交阶段连接到会话线程时,在'%d'次尝试中克服了临时'内存不足'的问题。"

ER_BINLOG_CANT_RESIZE_CACHE
  eng "Unable to resize binlog IOCACHE auxiliary file"
  chinese "无法调整binlog IOCACHE辅助文件的大小"

ER_BINLOG_FILE_BEING_READ_NOT_PURGED
  eng "file %s was not purged because it was being read by thread number %u"
  chinese "文件%s未被清除,因为它正被线程号%u读取"

ER_BINLOG_IO_ERROR_READING_HEADER
  eng "I/O error reading the header from the binary log, errno=%d, io cache code=%d"
  chinese "从二进制日志中读取头时出现I/O错误,错误号=%d,io缓存代码=%d"

OBSOLETE_ER_BINLOG_CANT_OPEN_LOG
  eng "Failed to open log (file '%s', errno %d)"
  chinese "无法打开日志(文件'%s',错误号%d)"

OBSOLETE_ER_BINLOG_CANT_CREATE_CACHE_FOR_LOG
  eng "Failed to create a cache on log (file '%s')"
  chinese "无法在日志(文件'%s')上创建缓存"

ER_BINLOG_FILE_EXTENSION_NUMBER_EXHAUSTED
  eng "Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files."
  chinese "日志文件扩展名耗尽:%06lu。请通过存档旧日志并更新索引文件来修复此问题。"

ER_BINLOG_FILE_NAME_TOO_LONG
  eng "Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files."
  chinese "日志文件名太大:%s%s(%zu)。请通过存档旧日志并更新索引文件来解决此问题。"

ER_BINLOG_FILE_EXTENSION_NUMBER_RUNNING_LOW
  eng "Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs."
  chinese "下一个日志扩展名:%lu。剩余的日志文件扩展名:%lu。请考虑存档一些日志。"

ER_BINLOG_CANT_OPEN_FOR_LOGGING
  eng "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."
  chinese "无法打开%s进行日志记录(错误%d)。在整个MySQL服务器进程期间关闭日志记录。要再次打开它:修复原因,关闭MySQL服务器,然后重新启动它。"

ER_BINLOG_FAILED_TO_SYNC_INDEX_FILE
  eng "MYSQL_BIN_LOG::open_index_file failed to sync the index file."
  chinese "MySQL_BIN_LOG::OPEN_INDEX_FILE无法同步索引文件。"

ER_BINLOG_ERROR_READING_GTIDS_FROM_RELAY_LOG
  eng "Error reading GTIDs from relaylog: %d"
  chinese "从中继日志读取GTID时出错:%d"

ER_BINLOG_EVENTS_READ_FROM_APPLIER_METADATA
  eng "%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state."
  chinese "读取了%lu个事件在relaylog文件'%s'中,用于更新RETRIED_GTID_SET和/或IO线程事务解析器状态。"

ER_BINLOG_ERROR_READING_GTIDS_FROM_BINARY_LOG
  eng "Error reading GTIDs from binary log: %d"
  chinese "从二进制日志读取GTID时出错:%d"

ER_BINLOG_EVENTS_READ_FROM_BINLOG_INFO
  eng "Read %lu events from binary log file '%s' to determine the GTIDs purged from binary logs."
  chinese "读取%lu个事件从二进制日志文件'%s'中以确定从二进制日志中清除的GTID。"

ER_BINLOG_CANT_GENERATE_NEW_FILE_NAME
  eng "MYSQL_BIN_LOG::open failed to generate new file name."
  chinese "MySQL_BIN_LOG::OPEN无法生成新文件名。"

ER_BINLOG_FAILED_TO_SYNC_INDEX_FILE_IN_OPEN
  eng "MYSQL_BIN_LOG::open failed to sync the index file."
  chinese "MySQL_BIN_LOG::OPEN无法同步索引文件。"

ER_BINLOG_CANT_USE_FOR_LOGGING
  eng "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."
  chinese "无法使用%s进行日志记录(错误%d)。在MySQL服务器进程的整个持续时间内关闭日志记录。要再次打开它:修复原因,关闭MySQL服务器并重新启动它。"

ER_BINLOG_FAILED_TO_CLOSE_INDEX_FILE_WHILE_REBUILDING
  eng "While rebuilding index file %s: Failed to close the index file."
  chinese "重建索引文件%s时:无法关闭索引文件。"

ER_BINLOG_FAILED_TO_DELETE_INDEX_FILE_WHILE_REBUILDING
  eng "While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process."
  chinese "重建索引文件%s时:删除现有索引文件失败。可能是该文件正被某个其他进程使用。"

ER_BINLOG_FAILED_TO_RENAME_INDEX_FILE_WHILE_REBUILDING
  eng "While rebuilding index file %s: Failed to rename the new index file to the existing index file."
  chinese "重建索引文件%s时:无法将新索引文件重命名为现有索引文件。"

ER_BINLOG_FAILED_TO_OPEN_INDEX_FILE_AFTER_REBUILDING
  eng "After rebuilding the index file %s: Failed to open the index file."
  chinese "重新生成索引文件%s后:无法打开索引文件。"

ER_BINLOG_CANT_APPEND_LOG_TO_TMP_INDEX
  eng "MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file."
  chinese "MYSQL_BIN_LOG::ADD_LOG_TO_INDEX无法将日志文件名:%s追加到崩溃安全索引文件。"

ER_BINLOG_CANT_LOCATE_OLD_BINLOG_OR_RELAY_LOG_FILES
  eng "Failed to locate old binlog or relay log files"
  chinese "找不到旧的binlog或中继日志文件"

ER_BINLOG_CANT_DELETE_FILE
  eng "Failed to delete file '%s'"
  chinese "无法删除文件'%s'"

ER_BINLOG_CANT_SET_TMP_INDEX_NAME
  eng "MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name."
  chinese "MYSQL_BIN_LOG::set_crash_safe_index_file_name无法设置文件名。"

ER_BINLOG_FAILED_TO_OPEN_TEMPORARY_INDEX_FILE
  eng "MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file."
  chinese "MySQL_BIN_LOG::OPEN_CRASH_SAFE_INDEX_FILE无法打开临时索引文件。"

OBSOLETE_ER_BINLOG_ERROR_GETTING_NEXT_LOG_FROM_INDEX
  eng "next log error: %d  offset: %s  log: %s included: %d"
  chinese "下一个日志错误:%d偏移量:%s日志:%s包含:%d"

ER_BINLOG_CANT_OPEN_TMP_INDEX
  eng "%s failed to open the crash safe index file."
  chinese "%s无法打开崩溃安全索引文件。"

ER_BINLOG_CANT_COPY_INDEX_TO_TMP
  eng "%s failed to copy index file to crash safe index file."
  chinese "%s无法将索引文件复制到崩溃安全索引文件。"

ER_BINLOG_CANT_CLOSE_TMP_INDEX
  eng "%s failed to close the crash safe index file."
  chinese "%s无法关闭崩溃安全索引文件。"

ER_BINLOG_CANT_MOVE_TMP_TO_INDEX
  eng "%s failed to move crash safe index file to index file."
  chinese "%s无法将崩溃安全索引文件移动到索引文件。"

ER_BINLOG_PURGE_LOGS_CALLED_WITH_FILE_NOT_IN_INDEX
  eng "MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index."
  chinese "使用索引中未列出的文件%s调用了MySQL_BIN_LOG::PURGE_LOGS。"

ER_BINLOG_PURGE_LOGS_CANT_SYNC_INDEX_FILE
  eng "MYSQL_BIN_LOG::purge_logs failed to sync the index file."
  chinese "MySQL_BIN_LOG::PURGE_LOGS无法同步索引文件。"

ER_BINLOG_PURGE_LOGS_CANT_COPY_TO_REGISTER_FILE
  eng "MYSQL_BIN_LOG::purge_logs failed to copy %s to register file."
  chinese "MYSQL_BIN_LOG::PURGE_LOGS无法将%s复制到注册文件。"

ER_BINLOG_PURGE_LOGS_CANT_FLUSH_REGISTER_FILE
  eng "MYSQL_BIN_LOG::purge_logs failed to flush register file."
  chinese "MySQL_BIN_LOG::PURGE_LOGS刷新寄存器文件失败。"

ER_BINLOG_PURGE_LOGS_CANT_UPDATE_INDEX_FILE
  eng "MYSQL_BIN_LOG::purge_logs failed to update the index file"
  chinese "MySQL_BIN_LOG::PURGE_LOGS无法更新索引文件"

ER_BINLOG_PURGE_LOGS_FAILED_TO_PURGE_LOG
  eng "MYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged."
  chinese "MySQL_BIN_LOG::PURGE_LOGS无法处理要清除的注册文件。"

ER_BINLOG_FAILED_TO_SET_PURGE_INDEX_FILE_NAME
  eng "MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name."
  chinese "MySQL_BIN_LOG::SET_PURGE_INDEX_FILE_NAME设置文件名失败。"

ER_BINLOG_FAILED_TO_OPEN_REGISTER_FILE
  eng "MYSQL_BIN_LOG::open_purge_index_file failed to open register file."
  chinese "MySQL_BIN_LOG::OPEN_PURGE_INDEX_FILE无法打开寄存器文件。"

ER_BINLOG_FAILED_TO_REINIT_REGISTER_FILE
  eng "MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for read"
  chinese "MYSQL_BIN_LOG::PURGE_INDEX_ENTRY无法重新启动寄存器文件以进行读取"

ER_BINLOG_FAILED_TO_READ_REGISTER_FILE
  eng "MYSQL_BIN_LOG::purge_index_entry error %d reading from register file."
  chinese "MYSQL_BIN_LOG::PURGE_INDEX_ENTRY从寄存器文件读取时出现错误%d。"

ER_CANT_STAT_FILE
  eng "Failed to execute mysql_file_stat on file '%s'"
  chinese "无法在文件'%s'上执行MYSQL_FILE_STAT"

ER_BINLOG_CANT_DELETE_LOG_FILE_DOES_INDEX_MATCH_FILES
  eng "Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog files"
  chinese "无法删除日志文件'%s'；请考虑检查binlog索引文件与实际binlog文件的对应关系"

ER_BINLOG_CANT_DELETE_FILE_AND_READ_BINLOG_INDEX
  eng "Failed to delete file '%s' and read the binlog index file"
  chinese "无法删除文件'%s'并读取binlog索引文件"

ER_BINLOG_FAILED_TO_DELETE_LOG_FILE
  eng "Failed to delete log file '%s'"
  chinese "无法删除日志文件'%s'"

ER_BINLOG_LOGGING_INCIDENT_TO_STOP_REPLICAS
  eng "%s An incident event has been written to the binary log which will stop the replicas."
  chinese "%s已将事件写入二进制日志,这将停止从属。"

ER_BINLOG_CANT_FIND_LOG_IN_INDEX
  eng "find_log_pos() failed (error: %d)"
  chinese "find_log_pos()失败(错误:%d)"

ER_BINLOG_RECOVERING_AFTER_CRASH_USING
  eng "Recovering after a crash using %s"
  chinese "使用%s在崩溃后恢复"

ER_BINLOG_CANT_OPEN_CRASHED_BINLOG
  eng "Failed to open the crashed binlog file when source server is recovering it."
  chinese "主服务器正在恢复崩溃的binlog文件时,无法打开该文件。"

ER_BINLOG_CANT_TRIM_CRASHED_BINLOG
  eng "Failed to trim the crashed binlog file when source server is recovering it."
  chinese "当主服务器正在恢复崩溃的binlog文件时,无法修剪该文件。"

ER_BINLOG_CRASHED_BINLOG_TRIMMED
  eng "Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes."
  chinese "崩溃的binlog文件%s的大小为%llu,但已恢复到%llu。Binlog已修剪为%llu字节。"

ER_BINLOG_CANT_CLEAR_IN_USE_FLAG_FOR_CRASHED_BINLOG
  eng "Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it."
  chinese "主服务器正在恢复崩溃的binlog文件时,无法清除该文件的LOG_EVENT_BINLOG_IN_USE_F。"

ER_BINLOG_FAILED_TO_RUN_AFTER_SYNC_HOOK
  eng "Failed to run 'after_sync' hooks"
  chinese "无法运行'After_sync'挂接"

ER_TURNING_LOGGING_OFF_FOR_THE_DURATION
  eng "%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."
  chinese "%s因此在MySQL服务器进程的整个持续时间内关闭登录。要重新打开它:修复原因,关闭MySQL服务器并重新启动。"

ER_BINLOG_FAILED_TO_RUN_AFTER_FLUSH_HOOK
  eng "Failed to run 'after_flush' hooks"
  chinese "无法运行'After_Flush'挂钩"

OBSOLETE_ER_BINLOG_CRASH_RECOVERY_FAILED
  eng "Crash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}"
  chinese "崩溃恢复失败。请更正问题(例如,内存不足错误)并重新启动,或者删除(或重命名)二进制日志并使用--TC-Heuristic-Recover={COMMIT|ROLLBACK}启动mysqld"

ER_BINLOG_WARNING_SUPPRESSED
  eng "The following warning was suppressed %d times during the last %d seconds in the error log"
  chinese "以下警告在错误日志中的最后%d秒内被取消%d次"

ER_NDB_LOG_ENTRY
  eng "NDB: %s"
  chinese "NDB: %s"

ER_NDB_LOG_ENTRY_WITH_PREFIX
  eng "NDB %s: %s"
  chinese "NDB %s: %s"

OBSOLETE_ER_NDB_BINLOG_CANT_CREATE_PURGE_THD
  eng "NDB: Unable to purge %s.%s File=%s (failed to setup thd)"
  chinese "NDB:无法清除%s。%s文件=%s(安装失败)"

ER_INNODB_UNKNOWN_COLLATION
  eng "Unknown collation #%lu."
  chinese "未知排序规则#%lu。"

ER_INNODB_INVALID_LOG_GROUP_HOME_DIR
  eng "syntax error in innodb_log_group_home_dir"
  chinese "Innodb_LOG_GROUP_HOME_DIR中的语法错误"

ER_INNODB_INVALID_INNODB_UNDO_DIRECTORY
  eng "syntax error in innodb_undo_directory"
  chinese "Innodb_undo_目录中的语法错误"

ER_INNODB_ILLEGAL_COLON_IN_POOL
  eng "InnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name."
  chinese "InnoDB:Innodb_Buffer_Pool_Filename文件名中不能有冒号(:)。"

ER_INNODB_INVALID_PAGE_SIZE
  eng "InnoDB: Invalid page size=%lu."
  chinese "InnoDB:页面大小无效=%lu。"

ER_INNODB_DIRTY_WATER_MARK_NOT_LOW
  eng "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"

ER_INNODB_IO_CAPACITY_EXCEEDS_MAX
  eng "InnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu"
  chinese "InnoDB:Innodb_io_Capacity不能设置为高于Innodb_io_Capacity_max。将Innodb_io_Capacity设置为%lu"

ER_INNODB_FILES_SAME
  eng "%s and %s file names seem to be the same."
  chinese "%s和%s文件名似乎相同。"

ER_INNODB_UNREGISTERED_TRX_ACTIVE
  eng "Transaction not registered for MySQL 2PC, but transaction is active"
  chinese "未为MySQL 2PC注册事务,但事务处于活动状态"

ER_INNODB_CLOSING_CONNECTION_ROLLS_BACK
  eng "MySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back."
  chinese "MySQL正在关闭具有活动InnoDB事务的连接。%llu行修改将回滚。"

ER_INNODB_TRX_XLATION_TABLE_OOM
  eng "InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%lu"
  chinese "InnoDB:无法为索引转换表分配内存。索引数:%lu,数组大小:%lu"

ER_INNODB_CANT_FIND_INDEX_IN_INNODB_DD
  eng "Cannot find index %s in InnoDB index dictionary."
  chinese "在InnoDB索引词典中找不到索引%s。"

ER_INNODB_INDEX_COLUMN_INFO_UNLIKE_MYSQLS
  eng "Found index %s whose column info does not match that of MySQL."
  chinese "发现索引%s的列信息与MySQL的列信息不匹配。"

OBSOLETE_ER_INNODB_CANT_OPEN_TABLE
  eng "Failed to open table %s."
  chinese "无法打开表%s。"

ER_INNODB_CANT_BUILD_INDEX_XLATION_TABLE_FOR
  eng "Build InnoDB index translation table for Table %s failed"
  chinese "为表%s构建InnoDB索引转换表失败"

ER_INNODB_PK_NOT_IN_MYSQL
  eng "Table %s has a primary key in InnoDB data dictionary, but not in MySQL!"
  chinese "表%s在InnoDB数据字典中有主键,但在MySQL中没有！"

ER_INNODB_PK_ONLY_IN_MYSQL
  eng "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."
  chinese "表%s在InnoDB数据字典中没有主键,但在MySQL中有主键！如果您使用低于3.23.54版的MySQL创建该表,并且没有定义主键,但定义了一个具有所有非空列的唯一键,则MySQL会在内部将该键视为主键。您可以通过转储+删除+创建+重新导入该表来修复此错误。"

ER_INNODB_CLUSTERED_INDEX_PRIVATE
  eng "Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB."
  chinese "即使InnoDB内部没有主键,表%s KEY_USED_ON_SCAN也是%lu。"

OBSOLETE_ER_INNODB_PARTITION_TABLE_LOWERCASED
  eng "Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system."
  chinese "分区表%s在转换为小写后打开。该表可能已从不区分大小写的文件系统中移出。请在当前文件系统中重新创建该表。"

ER_ERRMSG_REPLACEMENT_DODGY
  eng "Cannot replace error message (%s,%s,%s) \"%s\" with \"%s\"; wrong number or type of %% subsitutions."

ER_ERRMSG_REPLACEMENTS_FAILED
  eng "Table for error message replacements could not be found or read, or one or more replacements could not be applied."
  chinese "找不到或无法读取错误消息替换表,或者无法应用一个或多个替换。"

ER_NPIPE_CANT_CREATE
  eng "%s: %s"
  chinese "%s: %s"

ER_PARTITION_MOVE_CREATED_DUPLICATE_ROW_PLEASE_FIX
  eng "Table '%-192s': 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"
  chinese "表'%-192s':从第%d部分删除失败,出现错误%d。但在移动放错位置的行时已将其插入到第%d部分！请手动修复重复行:%s"

ER_AUDIT_CANT_ABORT_COMMAND
  eng "Command '%s' cannot be aborted. The trigger error was (%d) [%s]: %s"
  chinese "无法中止命令'%s'。触发器错误为(%d)[%s]:%s"

ER_AUDIT_CANT_ABORT_EVENT
  eng "Event '%s' cannot be aborted. The trigger error was (%d) [%s]: %s"
  chinese "无法中止事件'%s'。触发器错误为(%d)[%s]:%s"

ER_AUDIT_WARNING
  eng "%s. The trigger error was (%d) [%s]: %s"
  chinese "无法中止事件'%s'。触发器错误为(%d)[%s]:%s"

OBSOLETE_ER_NDB_NUMBER_OF_CHANNELS
  eng "Replica SQL: Configuration with number of replication sources = %u' is not supported when applying to Ndb"
  chinese "从属SQL:应用于NDB时不支持复制主机数=%u'的配置"

OBSOLETE_ER_NDB_REPLICA_PARALLEL_WORKERS
  eng "Replica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to Ndb"
  chinese "从属SQL:应用于NDB时不支持配置'REPLICATE_PARALLEL_WORKER=%lu'"

OBSOLETE_ER_NDB_DISTRIBUTING_ERR
  eng "NDB %s: distributing %s err: %u"
  chinese "NDB%s:分发%s错误:%u"

ER_RPL_REPLICA_INSECURE_CHANGE_SOURCE
  eng "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."
  chinese "将MySQL用户名或密码信息存储在主信息存储库中是不安全的,因此不建议使用。请考虑使用启动从属程序的用户和密码连接选项；有关详细信息,请参阅MySQL手册中的'启动从属程序语法'。"

OBSOLETE_ER_RPL_SLAVE_FLUSH_RELAY_LOGS_NOT_ALLOWED
  eng "FLUSH RELAY LOGS cannot be performed on channel '%-.192s'."
  chinese "无法在通道'%-.192s'上执行刷新中继日志。"

ER_RPL_REPLICA_INCORRECT_CHANNEL
  eng "Replica channel '%s' does not exist."
  chinese "从频道'%s'不存在。"

ER_FAILED_TO_FIND_DL_ENTRY
  eng "Can't find symbol '%-.128s' in library."
  chinese "在库中找不到符号'%-.128s'。"

ER_FAILED_TO_OPEN_SHARED_LIBRARY
  eng "Can't open shared library '%-.192s' (errno: %d %-.192s)."
  chinese "无法打开共享库'%-.192s'(错误号:%d%-.192s)。"

ER_THREAD_PRIORITY_IGNORED
  eng "Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege."
  chinese "由于平台不受支持或权限不足,应忽略资源组SQL中的线程优先级属性设置。"

ER_BINLOG_CACHE_SIZE_TOO_LARGE
  eng "Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size."
  chinese "选项binlog_缓存_大小(%lu)大于max_binlog_缓存_大小(%lu)；将binlog_缓存大小设置为等于max_binlog_缓存大小。"

ER_BINLOG_STMT_CACHE_SIZE_TOO_LARGE
  eng "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."
  chinese "选项binlog_stmt_缓存大小(%lu)大于max_binlog_stmt_缓存大小(%lu)；将binlog_stmt_缓存大小设置为等于max_binlog_stmt_缓存大小。"

ER_FAILED_TO_GENERATE_UNIQUE_LOGFILE
  eng "Can't generate a unique log-filename %-.200s.(1-999)."
  chinese "无法生成唯一的日志文件名%-.200s.(1-999)。"

ER_FAILED_TO_READ_FILE
  eng "Error reading file '%-.200s' (errno: %d - %s)"
  chinese "读取文件'%-.200s'时出错(错误号:%d-%s)"

ER_FAILED_TO_WRITE_TO_FILE
  eng "Error writing file '%-.200s' (errno: %d - %s)"
  chinese "写入文件'%-.200s'时出错(错误号:%d-%s)"

ER_BINLOG_UNSAFE_MESSAGE_AND_STATEMENT
  eng "%s Statement: %s"
  chinese "%s语句:%s"

ER_FORCE_CLOSE_THREAD
  eng "%s: Forcing close of thread %ld  user: '%-.48s'."
  chinese "%s:正在强制关闭线程%ld用户:'%-.48s'。"

ER_SERVER_SHUTDOWN_COMPLETE
  eng "%s: Shutdown complete (mysqld %s)  %s."
  chinese "%s:关闭完成(mysqld%s)%s。"

ER_RPL_CANT_HAVE_SAME_BASENAME
  eng "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."
  chinese "二进制日志和中继日志不能具有相同的基本名称'%s'。请检查%s(如果未使用--log-bin选项,则为默认'%s'；如果使用--log-bin选项,则为默认'%s')和%s(默认为'%s')选项,以确保它们不会冲突。"

ER_RPL_GTID_MODE_REQUIRES_ENFORCE_GTID_CONSISTENCY_ON
  eng "GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON."
  chinese "GTID_MODE = ON 要求 ENFORCE_GTID_CONSISTENCY = ON."

ER_WARN_NO_SERVERID_SPECIFIED
  eng "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."
  chinese "您没有提供必需的服务器ID。复制拓扑中的服务器必须具有唯一的服务器ID。请参阅正确的服务器启动参数文档。"

ER_ABORTING_USER_CONNECTION
  eng "Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s)."
  chinese "已中止与数据库的连接%u:'%-.192s'用户:'%-.48s'主机:'%-.255s'(%-.64s)。"

ER_SQL_MODE_MERGED_WITH_STRICT_MODE
  eng "'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."
  chinese "'NO_ZERO_DATE'、'NO_ZERO_IN_DATE'和'ERROR_FOR_DIVATION_BY_ZERO'SQL模式应与严格模式一起使用。在将来的版本中,它们将与严格模式合并。"

ER_GTID_PURGED_WAS_UPDATED
  eng "@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'."
  chinese "@@GLOBAL.GTID_PURGED已从'%s'更改为'%s'。"

ER_GTID_EXECUTED_WAS_UPDATED
  eng "@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'."
  chinese "@@GLOBAL.GTID_EXECUTED已从'%s'更改为'%s'。"

ER_DEPRECATE_MSG_WITH_REPLACEMENT
  eng "'%s' is deprecated and will be removed in a future release. Please use %s instead."
  chinese "'%s'已弃用,将在将来的版本中删除。请改用%s。"

ER_TRG_CREATION_CTX_NOT_SET
  eng "Triggers for table `%-.64s`.`%-.64s` have no creation context"
  chinese "表`%-.64s`.`%-.64s`的触发器没有创建上下文"

ER_FILE_HAS_OLD_FORMAT
  eng "'%-.192s' has an old format, you should re-create the '%s' object(s)"
  chinese "'%-.192s'具有旧格式,您应该重新创建'%s'对象"

ER_VIEW_CREATION_CTX_NOT_SET
  eng "View `%-.64s`.`%-.64s` has no creation context"
  chinese "视图`%-.64s`.`%-.64s`没有创建上下文"

OBSOLETE_ER_TABLE_NAME_CAUSES_TOO_LONG_PATH
  eng "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."
  chinese "对象的长数据库名称和标识符导致表'%s'的路径长度太长。请检查您的操作系统的路径限制。"

ER_TABLE_UPGRADE_REQUIRED
  eng "Table upgrade required. Please do \"REPAIR TABLE `%-.64s`\" or dump/reload to fix it!"
  chinese "需要表升级。请执行\"修复表`%-.64s`\"或转储/重新加载以修复它！"

ER_GET_ERRNO_FROM_STORAGE_ENGINE
  eng "Got error %d - '%-.192s' from storage engine."
  chinese "从存储引擎获得错误%d-'%-.192s'。"

ER_ACCESS_DENIED_ERROR_WITHOUT_PASSWORD
  eng "Access denied for user '%-.48s'@'%-.64s'"
  chinese "拒绝用户'%-.48s'@'%-.64s'的访问"

ER_ACCESS_DENIED_ERROR_WITH_PASSWORD
  eng "Access denied for user '%-.48s'@'%-.64s' (using password: %s)"
  chinese "拒绝用户'%-.48s'@'%-.64s'的访问(使用密码:%s)"

ER_ACCESS_DENIED_FOR_USER_ACCOUNT_LOCKED
  eng "Access denied for user '%-.48s'@'%-.64s'. Account is locked."
  chinese "用户'%-.48s'@'%-.64s'的访问被拒绝。帐户已锁定。"

OBSOLETE_ER_MUST_CHANGE_EXPIRED_PASSWORD
  eng "Your password has expired. To log in you must change it using a client that supports expired passwords."
  chinese "您的密码已过期。要登录,您必须使用支持过期密码的客户端进行更改。"

ER_SYSTEM_TABLES_NOT_SUPPORTED_BY_STORAGE_ENGINE
  eng "Storage engine '%s' does not support system tables. [%s.%s]."
  chinese "存储引擎'%s'不支持系统表。[%s.%s]。"

OBSOLETE_ER_FILESORT_TERMINATED
  eng "Sort aborted"
  chinese "排序已中止"

ER_SERVER_STARTUP_MSG
  eng "%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s."
  chinese "%s:准备连接。版本:'%s'套接字:'%s'端口:%d %s。"

ER_FAILED_TO_FIND_LOCALE_NAME
  eng "Unknown locale: '%-.64s'."
  chinese "本地未知:'%-.64s'."

ER_FAILED_TO_FIND_COLLATION_NAME
  eng "Unknown collation: '%-.64s'."
  chinese "未知排序规则:'%-.64s'。"

ER_SERVER_OUT_OF_RESOURCES
  eng "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"
  chinese "内存不足；检查mysqld或某些其他进程是否使用了所有可用内存；如果不是,您可能必须使用'ulimit'来允许mysqld使用更多内存,或者您可以添加更多交换空间"

ER_SERVER_OUTOFMEMORY
  eng "Out of memory; restart server and try again (needed %d bytes)"
  chinese "内存不足；重新启动服务器并重试(需要%d字节)"

ER_INVALID_COLLATION_FOR_CHARSET
  eng "COLLATION '%s' is not valid for CHARACTER SET '%s'"
  chinese "归类'%s'对字符集'%s'无效"

ER_CANT_START_ERROR_LOG_SERVICE
  eng "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)."
  chinese "无法将%s设置在\"%s\"或其周围--服务有效,但无法初始化；请检查其配置,并确保它可以读取其输入和写入其输出。"

ER_CREATING_NEW_UUID_FIRST_START
  eng "Generating a new UUID: %s."
  chinese "正在生成新的UUID:%s。"

ER_FAILED_TO_GET_ABSOLUTE_PATH
  eng "Failed to get absolute path of program executable %s"
  chinese "无法获取程序可执行文件%s的绝对路径"

ER_PERFSCHEMA_COMPONENTS_INFRASTRUCTURE_BOOTSTRAP
  eng "Failed to bootstrap performance schema components infrastructure."
  chinese "无法引导性能架构组件基础结构。"

ER_PERFSCHEMA_COMPONENTS_INFRASTRUCTURE_SHUTDOWN
  eng "Failed to deinit performance schema components infrastructure."
  chinese "无法取消初始化性能架构组件基础结构。"

ER_DUP_FD_OPEN_FAILED
  eng "Could not open duplicate fd for %s: %s."
  chinese "无法打开%s的重复fd:%s。"

ER_SYSTEM_VIEW_INIT_FAILED
  eng "System views initialization failed."
  chinese "系统视图初始化失败。"

ER_RESOURCE_GROUP_POST_INIT_FAILED
  eng "Resource group post initialization failed."
  chinese "资源组POST初始化失败。"

ER_RESOURCE_GROUP_SUBSYSTEM_INIT_FAILED
  eng "Resource Group subsystem initialization failed."
  chinese "资源组子系统初始化失败。"

ER_FAILED_START_MYSQLD_DAEMON
  eng "Failed to start mysqld daemon. Check mysqld error log."
  chinese "无法启动mysqld守护程序。请检查mysqld错误日志。"

ER_CANNOT_CHANGE_TO_ROOT_DIR
  eng "Cannot change to root directory: %s."
  chinese "无法更改到根目录:%s。"

ER_PERSISTENT_PRIVILEGES_BOOTSTRAP
  eng "Failed to bootstrap persistent privileges."
  chinese "无法引导永久权限。"

ER_BASEDIR_SET_TO
  eng "Basedir set to %s."
  chinese "Basedir设置为%s。"

ER_RPL_FILTER_ADD_WILD_DO_TABLE_FAILED
  eng "Could not add wild do table rule '%s'!"
  chinese "无法添加全域DO表规则'%s'！"

ER_RPL_FILTER_ADD_WILD_IGNORE_TABLE_FAILED
  eng "Could not add wild ignore table rule '%s'!"
  chinese "无法添加全域忽略表规则'%s'！"

ER_PRIVILEGE_SYSTEM_INIT_FAILED
  eng "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."
  chinese "特权系统无法正确初始化。有关如何将MySQL升级到新版本的完整说明,请参阅MySQL手册中的'升级MySQL'一节。"

ER_CANNOT_SET_LOG_ERROR_SERVICES
  eng "Cannot set services \"%s\" requested in --log-error-services, using defaults."
  chinese "无法使用默认值设置在--log-error-services中请求的服务\"%s\"。"

ER_PERFSCHEMA_TABLES_INIT_FAILED
  eng "Performance schema tables initialization failed."
  chinese "性能架构表初始化失败。"

OBSOLETE_ER_TX_EXTRACTION_ALGORITHM_FOR_BINLOG_TX_DEPEDENCY
  eng "The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s."
  chinese "当binlog_Transaction_Dependency_Tracing为%s时,TRANSACTION_WRITE_SET_EXTRACTION必须设置为%s。"

OBSOLETE_ER_INVALID_REPLICATION_TIMESTAMPS
  eng "Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again."
  chinese "无效的复制时间戳:原始提交时间戳比立即提交时间戳晚。如果延迟的复制处于活动状态,这可能是一个问题。请确保服务器的时钟设置为正确的时间。在时间戳再次生效之前,不会发出进一步的消息。"

OBSOLETE_ER_RPL_TIMESTAMPS_RETURNED_TO_NORMAL
  eng "The replication timestamps have returned to normal values."
  chinese "复制时间戳已恢复为正常值。"

ER_BINLOG_FILE_OPEN_FAILED
  eng "%s."
  chinese "%s."

ER_BINLOG_EVENT_WRITE_TO_STMT_CACHE_FAILED
  eng "Failed to write an incident event into stmt_cache."
  chinese "无法将事件事件写入stmt_cache。"

ER_REPLICA_RELAY_LOG_TRUNCATE_INFO
  eng "Relaylog file %s size was %llu, but was truncated at %llu."
  chinese "中继日志文件%s的大小为%llu,但在%llu处被截断。"

ER_REPLICA_RELAY_LOG_PURGE_FAILED
  eng "Unable to purge relay log files. %s:%s."
  chinese "无法清除中继日志文件。%s:%s。"

ER_RPL_REPLICA_FILTER_CREATE_FAILED
  eng "Replica: failed in creating filter for channel '%s'."
  chinese "从属:无法为频道'%s'创建筛选器。"

ER_RPL_REPLICA_GLOBAL_FILTERS_COPY_FAILED
  eng "Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'."
  chinese "从属:无法在通道'%s'的配置上将全局筛选器复制到它自己的每个通道筛选器。"

ER_RPL_REPLICA_RESET_FILTER_OPTIONS
  eng "There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded."
  chinese "为不存在的通道'%.192s'配置了每个通道的复制筛选器。筛选器已被丢弃。"

ER_MISSING_GRANT_SYSTEM_TABLE
  eng "The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure."
  chinese "缺少系统表mysql.global_grants。请执行MySQL升级过程。"

ER_MISSING_ACL_SYSTEM_TABLE
  eng "ACL table mysql.%.*s missing. Some operations may fail."
  chinese "缺少ACL表MySQL%.*s。某些操作可能会失败。"

ER_ANONYMOUS_AUTH_ID_NOT_ALLOWED_IN_MANDATORY_ROLES
  eng "Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles."
  chinese "无法设置MANDIRED_ROLE%s@%s:不允许匿名授权ID作为角色。"

ER_UNKNOWN_AUTH_ID_IN_MANDATORY_ROLE
  eng "Can't set mandatory_role: There's no such authorization ID %s@%s."
  chinese "无法设置MANDIRED_ROLE:没有这样的授权ID%s@%s。"

ER_WRITE_ROW_TO_PARTITION_FAILED
  eng "Table '%-192s' failed to move/insert a row from part %d into part %d: %s."
  chinese "表'%-192s'无法将行从部件%d移动/插入到部件%d:%s。"

ER_RESOURCE_GROUP_METADATA_UPDATE_SKIPPED
  eng "Skipped updating resource group metadata in InnoDB read only mode."
  chinese "已跳过在InnoDB只读模式下更新资源组元数据。"

ER_FAILED_TO_PERSIST_RESOURCE_GROUP_METADATA
  eng "Failed to persist resource group %s to Data Dictionary."
  chinese "无法将资源组%s保存到数据字典。"

ER_FAILED_TO_DESERIALIZE_RESOURCE_GROUP
  eng "Failed to deserialize resource group %s."
  chinese "无法反序列化资源组%s。"

ER_FAILED_TO_UPDATE_RESOURCE_GROUP
  eng "Update of resource group %s failed."
  chinese "更新资源组%s失败。"

ER_RESOURCE_GROUP_VALIDATION_FAILED
  eng "Validation of resource group %s failed. Resource group is disabled."
  chinese "资源组%s的验证失败。资源组被禁用。"

ER_FAILED_TO_ALLOCATE_MEMORY_FOR_RESOURCE_GROUP
  eng "Unable to allocate memory for Resource Group %s."
  chinese "无法为资源组%s分配内存。"

ER_FAILED_TO_ALLOCATE_MEMORY_FOR_RESOURCE_GROUP_HASH
  eng "Failed to allocate memory for resource group hash."
  chinese "无法为资源组哈希分配内存。"

ER_FAILED_TO_ADD_RESOURCE_GROUP_TO_MAP
  eng "Failed to add resource group %s to resource group map."
  chinese "无法将资源组%s添加到资源组映射。"

ER_RESOURCE_GROUP_IS_DISABLED
  eng "Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD)."
  chinese "资源组功能已禁用。(服务器使用DISABLE_PSI_THREAD编译)。"

ER_FAILED_TO_APPLY_RESOURCE_GROUP_CONTROLLER
  eng "Unable to apply resource group controller %s."
  chinese "无法应用资源组控制器%s。"

ER_FAILED_TO_ACQUIRE_LOCK_ON_RESOURCE_GROUP
  eng "Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored."
  chinese "无法获取资源组%s上的锁。切换资源组的提示应被忽略。"

ER_PFS_NOTIFICATION_FUNCTION_REGISTER_FAILED
  eng "PFS %s notification function registration failed."
  chinese "PFS %s通知函数注册失败。"

ER_RES_GRP_SET_THR_AFFINITY_FAILED
  eng "Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s)."
  chinese "无法将线程ID%llu绑定到CPU ID%u(错误代码%d-%-.192s)。"

ER_RES_GRP_SET_THR_AFFINITY_TO_CPUS_FAILED
  eng "Unable to bind thread id %llu to cpu ids (error code %d - %-.192s)."
  chinese "无法将线程ID%llu绑定到CPU ID(错误代码%d-%-.192s)。"

ER_RES_GRP_THD_UNBIND_FROM_CPU_FAILED
  eng "Unbind thread id %llu failed. (error code %d - %-.192s)."
  chinese "解除绑定线程ID%llu失败。(错误代码%d-%-.192s)。"

ER_RES_GRP_SET_THREAD_PRIORITY_FAILED
  eng "Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s)."
  chinese "将线程优先级%d设置为线程ID%llu失败。(错误代码%d-%-.192s)。"

ER_RES_GRP_FAILED_TO_DETERMINE_NICE_CAPABILITY
  eng "Unable to determine CAP_SYS_NICE capability."
  chinese "无法确定CAP_SYS_NICE功能。"

ER_RES_GRP_FAILED_TO_GET_THREAD_HANDLE
  eng "%s failed: Failed to get handle for thread %llu."
  chinese "%s失败:无法获取线程%llu的句柄。"

ER_RES_GRP_GET_THREAD_PRIO_NOT_SUPPORTED
  eng "Retrieval of thread priority unsupported on %s."
  chinese "%s上不支持线程优先级的检索。"

ER_RES_GRP_FAILED_DETERMINE_CPU_COUNT
  eng "Unable to determine the number of CPUs."
  chinese "无法确定CPU的数量。"

ER_RES_GRP_FEATURE_NOT_AVAILABLE
  eng "Resource group feature shall not be available. Incompatible thread handling option."
  chinese "资源组功能不可用。线程处理选项不兼容。"

ER_RES_GRP_INVALID_THREAD_PRIORITY
  eng "Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d]."
  chinese "线程优先级%d对于%s资源组无效。允许的范围是[%d,%d]。"

ER_RES_GRP_SOLARIS_PROCESSOR_BIND_TO_CPUID_FAILED
  eng "bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s)."
  chinese "BIND_TO_CPU失败:cpuid%u的PROCESOR_BIND失败(错误代码%d-%-.192s)。"

ER_RES_GRP_SOLARIS_PROCESSOR_BIND_TO_THREAD_FAILED
  eng "bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s)."
  chinese "BIND_TO_CPU失败:线程%%llx的CPU ID为%u的PROCESSOR_BIND(错误代码%d - %-.192s)。"

ER_RES_GRP_SOLARIS_PROCESSOR_AFFINITY_FAILED
  eng "%s failed: processor_affinity failed (error code %d - %-.192s)."
  chinese "%s失败:PROCESS_AFFINITY失败(错误代码%d-%-.192s)。"

ER_DD_UPGRADE_RENAME_IDX_STATS_FILE_FAILED
  eng "Error in renaming mysql_index_stats.ibd."
  chinese "重命名mysql_index_stats.ibd时出错。"

ER_DD_UPGRADE_DD_OPEN_FAILED
  eng "Error in opening data directory %s."
  chinese "打开数据目录%s时出错。"

ER_DD_UPGRADE_FAILED_TO_FETCH_TABLESPACES
  eng "Error in fetching list of tablespaces."
  chinese "获取表空间列表时出错。"

ER_DD_UPGRADE_FAILED_TO_ACQUIRE_TABLESPACE
  eng "Error in acquiring Tablespace for SDI insertion %s."
  chinese "获取SDI插入%s的表空间时出错。"

ER_DD_UPGRADE_FAILED_TO_RESOLVE_TABLESPACE_ENGINE
  eng "Error in resolving Engine name for tablespace %s with engine %s."
  chinese "解析表空间%s的引擎名称时出错,引擎为%s。"

ER_FAILED_TO_CREATE_SDI_FOR_TABLESPACE
  eng "Error in creating SDI for %s tablespace."
  chinese "为%s表空间创建SDI时出错。"

ER_FAILED_TO_STORE_SDI_FOR_TABLESPACE
  eng "Error in storing SDI for %s tablespace."
  chinese "存储%s表空间的SDI时出错。"

ER_DD_UPGRADE_FAILED_TO_FETCH_TABLES
  eng "Error in fetching list of tables."
  chinese "获取表列表时出错。"

ER_DD_UPGRADE_DD_POPULATED
  eng "Finished populating Data Dictionary tables with data."
  chinese "已完成使用数据填充数据字典表。"

ER_DD_UPGRADE_INFO_FILE_OPEN_FAILED
  eng "Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d."
  chinese "无法打开MySQL服务器数据目录中的升级信息文件'%s',错误号:%d。"

ER_DD_UPGRADE_INFO_FILE_CLOSE_FAILED
  eng "Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d."
  chinese "无法关闭MySQL服务器数据目录中的升级信息文件'%s',错误号:%d。"

ER_DD_UPGRADE_TABLESPACE_MIGRATION_FAILED
  eng "Got error %d from SE while migrating tablespaces."
  chinese "在迁移表空间时,从SE获得错误%d。"

ER_DD_UPGRADE_FAILED_TO_CREATE_TABLE_STATS
  eng "Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command."
  chinese "创建表统计数据项时出错。请使用分析命令修复统计数据。"

ER_DD_UPGRADE_TABLE_STATS_MIGRATE_COMPLETED
  eng "Finished migrating TABLE statistics data."
  chinese "已完成迁移表统计数据。"

ER_DD_UPGRADE_FAILED_TO_CREATE_INDEX_STATS
  eng "Error in creating Index statistics entry. Fix statistics data by using ANALYZE command."
  chinese "创建索引统计项时出错。请使用分析命令修复统计数据。"

ER_DD_UPGRADE_INDEX_STATS_MIGRATE_COMPLETED
  eng "Finished migrating INDEX statistics data."
  chinese "已完成迁移索引统计数据。"

ER_DD_UPGRADE_FAILED_FIND_VALID_DATA_DIR
  eng "Failed to find valid data directory."
  chinese "无法找到有效的数据目录。"

ER_DD_UPGRADE_START
  eng "Starting upgrade of data directory."
  chinese "开始升级数据目录。"

ER_DD_UPGRADE_FAILED_INIT_DD_SE
  eng "Failed to initialize DD Storage Engine."
  chinese "无法初始化DD存储引擎。"

ER_DD_UPGRADE_FOUND_PARTIALLY_UPGRADED_DD_ABORT
  eng "Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again."
  chinese "找到部分升级的DD。正在中止升级并删除所有DD表。重新开始升级过程。"

ER_DD_UPGRADE_FOUND_PARTIALLY_UPGRADED_DD_CONTINUE
  eng "Found partially upgraded DD. Upgrade will continue and start the server."
  chinese "找到部分升级的DD。升级将继续并启动服务器。"

ER_DD_UPGRADE_SE_LOGS_FAILED
  eng "Error in upgrading engine logs."
  chinese "升级引擎日志时出错。"

ER_DD_UPGRADE_SDI_INFO_UPDATE_FAILED
  eng "Error in updating SDI information."
  chinese "更新SDI信息时出错。"

ER_SKIP_UPDATING_METADATA_IN_SE_RO_MODE
  eng "Skip updating %s metadata in InnoDB read-only mode."
  chinese "跳过在InnoDB只读模式下更新%s元数据。"

ER_CREATED_SYSTEM_WITH_VERSION
  eng "Created system views with I_S version %d."
  chinese "已创建I_S版本为%d的系统视图。"

ER_UNKNOWN_ERROR_DETECTED_IN_SE
  eng "Unknown error detected %d in handler."
  chinese "在处理程序中检测到未知错误%d。"

ER_READ_LOG_EVENT_FAILED
  eng "Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d."
  chinese "LOG_EVENT::READ_LOG_EVENT()中出错:'%s',data_len:%lu,Event_type:%d。"

ER_ROW_DATA_TOO_BIG_TO_WRITE_IN_BINLOG
  eng "The row data is greater than 4GB, which is too big to write to the binary log."
  chinese "行数据大于4 GB,太大,无法写入二进制日志。"

ER_FAILED_TO_CONSTRUCT_DROP_EVENT_QUERY
  eng "Unable to construct DROP EVENT SQL query string."
  chinese "无法构造DROP EVENT SQL查询字符串。"

ER_FAILED_TO_BINLOG_DROP_EVENT
  eng "Unable to binlog drop event %s.%s."
  chinese "无法绑定日志删除事件%s.%s。"

ER_FAILED_TO_START_REPLICA_THREAD
  eng "Failed to start replica threads for channel '%s'."
  chinese "无法启动通道'%s'的从属线程。"

ER_RPL_IO_THREAD_KILLED
  eng "%s%s."
  chinese "%s%s."

ER_REPLICA_RECONNECT_FAILED
  eng "Failed registering on source, reconnecting to try again, log '%s' at position %s. %s."
  chinese "在主服务器上注册失败,请重新连接以重试,将'%s'记录在位置%s. %s。"

ER_REPLICA_KILLED_AFTER_RECONNECT
  eng "Replica I/O thread killed during or after reconnect."
  chinese "从属I/O线程在重新连接期间或之后被杀死。"

ER_REPLICA_NOT_STARTED_ON_SOME_CHANNELS
  eng "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."
  chinese "某些通道未正确创建/初始化。请检查上面的其他消息。在解决问题并重新启动服务器之前,您将无法在这些通道上启动复制。"

ER_FAILED_TO_ADD_RPL_FILTER
  eng "Failed to add a replication filter into filter map for channel '%.192s'."
  chinese "无法将复制筛选器添加到通道'%.192s'的筛选器映射中。"

ER_PER_CHANNEL_RPL_FILTER_CONF_FOR_GRP_RPL
  eng "There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded."
  chinese "为不允许的组复制通道'%.192s'配置了每个通道的复制筛选器。筛选器已被丢弃。"

ER_RPL_FILTERS_NOT_ATTACHED_TO_CHANNEL
  eng "There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded."
  chinese "为不存在的通道'%.192s'配置了每个通道的复制筛选器。筛选器已被丢弃。"

ER_FAILED_TO_BUILD_DO_AND_IGNORE_TABLE_HASHES
  eng "An error occurred while building do_table and ignore_table rules to hashes for per-channel filter."
  chinese "为每个通道筛选器的哈希构建DO_TABLE和IGNORE_TABLE规则时出错。"

ER_CLONE_PLUGIN_NOT_LOADED_TRACE
  eng "Clone plugin cannot be loaded."
  chinese "无法加载克隆插件。"

ER_CLONE_HANDLER_EXIST_TRACE
  eng "Clone Handler exists."
  chinese "克隆处理程序存在。"

ER_CLONE_CREATE_HANDLER_FAIL_TRACE
  eng "Could not create Clone Handler."
  chinese "无法创建克隆处理程序。"

ER_CYCLE_TIMER_IS_NOT_AVAILABLE
  eng "The CYCLE timer is not available. WAIT events in the performance_schema will not be timed."
  chinese "周期计时器不可用。将不会对PERFORMANCE_SCHEMA中的等待事件进行计时。"

ER_NANOSECOND_TIMER_IS_NOT_AVAILABLE
  eng "The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed."
  chinese "纳秒计时器不可用。将不会对PERFORMANCE_SCHEMA中的IDLE/STAGE/STATEMENT/TRANSACTION事件计时。"

ER_MICROSECOND_TIMER_IS_NOT_AVAILABLE
  eng "The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed."
  chinese "微秒计时器不可用。不会对PERFORMANCE_SCHEMA中的IDLE/STAGE/STATEMENT/TRANSACTION事件计时。"

ER_PFS_MALLOC_ARRAY_OVERFLOW
  eng "Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow."
  chinese "由于溢出,无法为%zu个区块分配内存,每个区块的大小为%zu(缓冲区'%s')。"

ER_PFS_MALLOC_ARRAY_OOM
  eng "Failed to allocate %zu bytes for buffer '%s' due to out-of-memory."
  chinese "由于内存不足,无法分配%zu字节为缓冲区'%s'。"

ER_INNODB_FAILED_TO_FIND_IDX_WITH_KEY_NO
  eng "InnoDB could not find index %s key no %u for table %s through its index translation table."
  chinese "InnoDB无法通过其索引转换表找到索引%s关键字%u表%s的。"

ER_INNODB_FAILED_TO_FIND_IDX
  eng "Cannot find index %s in InnoDB index translation table."
  chinese "在InnoDB索引转换表中找不到索引%s。"

ER_INNODB_FAILED_TO_FIND_IDX_FROM_DICT_CACHE
  eng "InnoDB could not find key no %u with name %s from dict cache for table %s."
  chinese "InnoDB在字典缓存中找不到密钥编号%u,名称为%s表%s的。"

ER_INNODB_ACTIVE_INDEX_CHANGE_FAILED
  eng "InnoDB: change_active_index(%u) failed."
  chinese "InnoDB:CHANGE_ACTIVE_INDEX(%u)失败。"

ER_INNODB_DIFF_IN_REF_LEN
  eng "Stored ref len is %lu, but table ref len is %lu."
  chinese "存储的引用长度是%lu,但表引用长度是%lu。"

ER_WRONG_TYPE_FOR_COLUMN_PREFIX_IDX_FLD
  eng "MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s."
  chinese "MySQL试图在不正确的数据类型上创建列前缀索引字段。表名%s,列名%s。"

ER_INNODB_CANNOT_CREATE_TABLE
  eng "Cannot create table %s."
  chinese "无法创建表%s。"

ER_INNODB_INTERNAL_INDEX
  eng "Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index."
  chinese "在InnoDB索引列表中找到索引%s,但未找到其MySQL索引号。它可能是InnoDB内部索引。"

ER_INNODB_IDX_CNT_MORE_THAN_DEFINED_IN_MYSQL
  eng "InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL."
  chinese "InnoDB:表%s在InnoDB中包含%lu个索引,这与MySQL中定义的索引数%u不同。"

ER_INNODB_IDX_CNT_FEWER_THAN_DEFINED_IN_MYSQL
  eng "Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?"
  chinese "表%s在InnoDB中包含的索引少于MySQL中定义的索引。您是否混淆了来自不同安装的数据字典？"

ER_INNODB_IDX_COLUMN_CNT_DIFF
  eng "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?"
  chinese "索引%s的%s在InnoDB中具有唯一的%lu列,但MySQL正在查询%lu列的统计信息。您是否混合了来自不同安装的数据字典？"

ER_INNODB_USE_MONITOR_GROUP_NAME
  eng "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."
  chinese "监视器计数器'%s'不能单独打开/关闭。请使用其模块名称将模块中的计数器作为一个组打开/关闭。"

ER_INNODB_MONITOR_DEFAULT_VALUE_NOT_DEFINED
  eng "Default value is not defined for this set option. Please specify correct counter or module name."
  chinese "没有为此SET选项定义默认值。请指定正确的计数器或模块名称。"

ER_INNODB_MONITOR_IS_ENABLED
  eng "InnoDB: Monitor %s is already enabled."
  chinese "InnoDB:监视器%s已启用。"

ER_INNODB_INVALID_MONITOR_COUNTER_NAME
  eng "Invalid monitor counter : %s."
  chinese "无效的监视计数器:%s。"

ER_WIN_LOAD_LIBRARY_FAILED
  eng "LoadLibrary(\"%s\") failed: GetLastError returns %lu."
  chinese "LoadLibrary(\"%s\")失败:GetLastError返回%lu。"

ER_PARTITION_HANDLER_ADMIN_MSG
  eng "%s."
  chinese "%s."

ER_RPL_AM_INIT_INFO_MSG
  eng "%s."
  chinese "%s."

ER_DD_UPGRADE_TABLE_INTACT_ERROR
  eng "%s."
  chinese "%s."

ER_SERVER_INIT_COMPILED_IN_COMMANDS
  eng "%s."
  chinese "%s."

ER_MYISAM_CHECK_METHOD_ERROR
  eng "%s."
  chinese "%s."

ER_MYISAM_CRASHED_ERROR
  eng "%s."
  chinese "%s."

ER_WAITPID_FAILED
  eng "Unable to wait for process %lld."
  chinese "无法等待进程%lld。"

ER_FAILED_TO_FIND_MYSQLD_STATUS
  eng "Unable to determine if daemon is running: %s (rc=%d)."
  chinese "无法确定守护程序是否正在运行:%s(返回代码=%d)。"

ER_INNODB_ERROR_LOGGER_MSG
  eng "%s"
  chinese "%s"

ER_INNODB_ERROR_LOGGER_FATAL_MSG
  eng "[FATAL] InnoDB: %s"
  chinese "[致命]InnoDB:%s"

ER_DEPRECATED_SYNTAX_WITH_REPLACEMENT
  eng "The syntax '%s' is deprecated and will be removed in a future release. Please use %s instead."
  chinese "语法'%s'已弃用,将在将来的版本中删除。请改用%s。"

ER_DEPRECATED_SYNTAX_NO_REPLACEMENT
  eng "The syntax '%s' is deprecated and will be removed in a future release."
  chinese "语法'%s'已弃用,将在将来的版本中删除。"

ER_DEPRECATE_MSG_NO_REPLACEMENT
  eng "'%s' is deprecated and will be removed in a future release."
  chinese "'%s'已弃用,将在将来的版本中删除。"

ER_LOG_PRINTF_MSG
  eng "%s"
  chinese "%s"

ER_BINLOG_LOGGING_NOT_POSSIBLE
  eng "Binary logging not possible. Message: %s."
  chinese "无法进行二进制日志记录。消息:%s。"

ER_FAILED_TO_SET_PERSISTED_OPTIONS
  eng "Failed to set persisted options."
  chinese "无法设置持久选项。"

ER_COMPONENTS_FAILED_TO_ACQUIRE_SERVICE_IMPLEMENTATION
  eng "Cannot acquire specified service implementation: '%.192s'."
  chinese "无法获取指定的服务实现:'%.192s'。"

ER_RES_GRP_INVALID_VCPU_RANGE
  eng "Invalid VCPU range %u-%u."
  chinese "无效的vCPU范围%u-%u。"

ER_RES_GRP_INVALID_VCPU_ID
  eng "Invalid cpu id %u."
  chinese "无效的CPU ID%u。"

ER_ERROR_DURING_FLUSH_LOG_COMMIT_PHASE
  eng "Got error %d during FLUSH_LOGS."
  chinese "在Flush_Logs期间出现错误%d。"

ER_DROP_DATABASE_FAILED_RMDIR_MANUALLY
  eng "Problem while dropping database. Can't remove database directory (%s). Please remove it manually."
  chinese "删除数据库时出现问题。无法删除数据库目录(%s)。请手动删除它。"

OBSOLETE_ER_EXPIRE_LOGS_DAYS_IGNORED
  eng "The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored."
  chinese "选项EXPIRE_LOGS_DAYS不能与选项binlog_EXPIRE_LOGS_Second一起使用。因此,EXPIRE_LOGS_DAYS的值将被忽略。"

ER_BINLOG_MALFORMED_OR_OLD_RELAY_LOG
  eng "malformed or very old relay log which does not have FormatDescriptor."
  chinese "格式错误或非常旧的没有FormatDescriptor的中继日志。"

ER_DD_UPGRADE_VIEW_COLUMN_NAME_TOO_LONG
  eng "Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters."
  chinese "升级视图'%s.%s'失败。请重新创建显式列名少于64个字符的视图。"

ER_TABLE_NEEDS_DUMP_UPGRADE
  eng "Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!"
  chinese "需要对`%-.64s`.`%-.64s`进行表升级。请转储/重新加载表以修复它！"

ER_DD_UPGRADE_FAILED_TO_UPDATE_VER_NO_IN_TABLESPACE
  eng "Error in updating version number in %s tablespace."
  chinese "更新%s表空间中的版本号时出错。"

ER_KEYRING_MIGRATION_FAILED
  eng "Keyring migration failed."
  chinese "密钥环迁移失败。"

ER_KEYRING_MIGRATION_SUCCESSFUL
  eng "Keyring migration successful."
  chinese "密钥环迁移成功。"

ER_RESTART_RECEIVED_INFO
  eng "Received RESTART from user %s.  Restarting mysqld (Version: %s)."
  chinese "收到来自用户%s的重新启动。正在重新启动mysqld(版本:%s)。"

ER_LCTN_CHANGED
  eng "Different lower_case_table_names settings for server ('%u') and data dictionary ('%u')."
  chinese "服务器('%u')和数据字典('%u')的LOWER_CASE_TABLE_NAMES设置不同。"

ER_DD_INITIALIZE
  eng "Data dictionary initializing version '%u'."
  chinese "数据字典正在初始化版本'%u'。"

ER_DD_RESTART
  eng "Data dictionary restarting version '%u'."
  chinese "数据字典正在重新启动版本'%u'。"

ER_DD_UPGRADE
  eng "Data dictionary upgrading from version '%u' to '%u'."
  chinese "数据字典从版本'%u'升级到'%u'。"

ER_DD_UPGRADE_OFF
  eng "Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'."
  chinese "命令行选项'--no_dd_Upgrade'禁止数据字典升级。"

ER_DD_UPGRADE_VERSION_NOT_SUPPORTED
  eng "Upgrading the data dictionary from dictionary version '%u' is not supported."
  chinese "不支持从字典版本'%u'升级数据字典。"

ER_DD_UPGRADE_SCHEMA_UNAVAILABLE
  eng "Upgrading the data dictionary failed, temporary schema name '%-.192s' not available."
  chinese "升级数据字典失败,临时架构名称'%-.192s'不可用。"

ER_DD_MINOR_DOWNGRADE
  eng "Data dictionary minor downgrade from version '%u' to '%u'."
  chinese "数据字典从版本'%u'小幅降级到'%u'。"

ER_DD_MINOR_DOWNGRADE_VERSION_NOT_SUPPORTED
  eng "Minor downgrade of the Data dictionary from dictionary version '%u' is not supported."
  chinese "不支持将数据字典从字典版本'%u'小幅降级。"

ER_DD_NO_VERSION_FOUND
  eng "No data dictionary version number found."
  chinese "未找到数据字典版本号。"

ER_THREAD_POOL_NOT_SUPPORTED_ON_PLATFORM
  eng "Thread pool not supported, requires a minimum of %s."
  chinese "不支持线程池,至少需要%s。"

ER_THREAD_POOL_SIZE_TOO_LOW
  eng "thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d."
  chinese "THREAD_POOL_SIZE=0表示线程池已禁用,允许的THREAD_POOL_SIZE范围为%d-%d。"

ER_THREAD_POOL_SIZE_TOO_HIGH
  eng "thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d."
  chinese "THREAD_POOL_SIZE=%lu太高,%d是最大值,线程池被禁用。THREAD_POOL_SIZE的允许范围是%d-%d。"

ER_THREAD_POOL_ALGORITHM_INVALID
  eng "thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm."
  chinese "THREAD_POOL_ALGORM可以设置为0和1,0表示默认低并发算法,1表示高并发算法。"

ER_THREAD_POOL_INVALID_STALL_LIMIT
  eng "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."
  chinese "THREAD_POOL_STALL_LIMIT最少可以是%d,最大可以是%d,较小的值会使线程池变得非常无用,较高的值可能会使MySQL Server中出现未检测到的死锁问题。"

ER_THREAD_POOL_INVALID_PRIO_KICKUP_TIMER
  eng "Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294."
  chinese "指定的THREAD_POOL_PRIO_KICKUP_TIMER的值无效。THREAD_POOL_PRIO_KICKUP_TIMER的值应该在0-4294967294范围内。"

ER_THREAD_POOL_MAX_UNUSED_THREADS_INVALID
  eng "thread_pool_max_unused_threads cannot be set higher than %d."
  chinese "THREAD_POOL_MAX_UNUSED_THREADS不能设置为大于%d。"

ER_THREAD_POOL_CON_HANDLER_INIT_FAILED
  eng "Failed to instantiate the connection handler object."
  chinese "无法实例化连接处理程序对象。"

ER_THREAD_POOL_INIT_FAILED
  eng "Failed to initialize thread pool plugin."
  chinese "无法初始化线程池插件。"

OBSOLETE_ER_THREAD_POOL_PLUGIN_STARTED
  eng "Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d."
  chinese "线程池插件已成功启动,参数为:THREAD_POOL_SIZE=%lu、THREAD_POOL_ALGORM=%s、THREAD_POOL_STALL_LIMIT=%u、THREAD_POOL_PRIO_KICKUP_TIMER=%u、THREAD_POOL_MAX_UNUSED_THREADS=%u、THREAD_POOL_HIGH_PRIORITY_CONNECTION=%d。"

ER_THREAD_POOL_CANNOT_SET_THREAD_SPECIFIC_DATA
  eng "Can't setup connection teardown thread-specific data."
  chinese "无法设置连接拆卸线程特定数据。"

ER_THREAD_POOL_FAILED_TO_CREATE_CONNECT_HANDLER_THD
  eng "Creation of connect handler thread failed."
  chinese "创建连接处理程序线程失败。"

ER_THREAD_POOL_FAILED_TO_CREATE_THD_AND_AUTH_CONN
  eng "Failed to create thd and authenticate connection."
  chinese "无法创建连接并进行身份验证。"

ER_THREAD_POOL_FAILED_PROCESS_CONNECT_EVENT
  eng "Failed to process connection event."
  chinese "无法处理连接事件。"

ER_THREAD_POOL_FAILED_TO_CREATE_POOL
  eng "Can't create pool thread (error %d, errno: %d)."
  chinese "无法创建池线程(错误%d,错误号:%d)。"

ER_THREAD_POOL_RATE_LIMITED_ERROR_MSGS
  eng "%.*s."
  chinese "%.*s."

ER_TRHEAD_POOL_LOW_LEVEL_INIT_FAILED
  eng "tp_group_low_level_init() failed."
  chinese "tp_group_low_level_init() 失败。"

ER_THREAD_POOL_LOW_LEVEL_REARM_FAILED
  eng "Rearm failed even after 30 seconds, can't continue without notify socket."
  chinese "重新武装即使在30秒后也失败,在没有通知套接字的情况下无法继续。"

ER_THREAD_POOL_BUFFER_TOO_SMALL
  eng "%s: %s buffer is too small"
  chinese "%s:%s缓冲区太小"

ER_MECAB_NOT_SUPPORTED
  eng "Mecab v%s is not supported, the lowest version supported is v%s."
  chinese "不支持Mecab v%s,支持的最低版本为v%s。"

ER_MECAB_NOT_VERIFIED
  eng "Mecab v%s is not verified, the highest version supported is v%s."
  chinese "未验证Mecab v%s,支持的最高版本为v%s。"

ER_MECAB_CREATING_MODEL
  eng "Mecab: Trying createModel(%s)."
  chinese "Mecab:正在尝试创建模型(%s)。"

ER_MECAB_FAILED_TO_CREATE_MODEL
  eng "Mecab: createModel() failed: %s."
  chinese "Mecab:createModel()失败:%s。"

ER_MECAB_FAILED_TO_CREATE_TRIGGER
  eng "Mecab: createTagger() failed: %s."
  chinese "Mecab:createTagger()失败:%s。"

ER_MECAB_UNSUPPORTED_CHARSET
  eng "Mecab: Unsupported dictionary charset %s."
  chinese "Mecab:不支持的字典字符集%s。"

ER_MECAB_CHARSET_LOADED
  eng "Mecab: Loaded dictionary charset is %s."
  chinese "Mecab:加载的词典字符集是%s。"

ER_MECAB_PARSE_FAILED
  eng "Mecab: parse() failed: %s."
  chinese "Mecab:parse()失败:%s。"

ER_MECAB_OOM_WHILE_PARSING_TEXT
  eng "Mecab: parse() failed: out of memory."
  chinese "Mecab:parse()失败:内存不足。"

ER_MECAB_CREATE_LATTICE_FAILED
  eng "Mecab: createLattice() failed: %s."
  chinese "Mecab:createLattice()失败:%s。"

ER_SEMISYNC_TRACE_ENTER_FUNC
  eng "---> %s enter."
  chinese "---> %s 确认."

ER_SEMISYNC_TRACE_EXIT_WITH_INT_EXIT_CODE
  eng "<--- %s exit (%d)."
  chinese "<--- %s 退出 (%d)."

ER_SEMISYNC_TRACE_EXIT_WITH_BOOL_EXIT_CODE
  eng "<--- %s exit (%s)."
  chinese "<--- %s 退出 (%s)."

ER_SEMISYNC_TRACE_EXIT
  eng "<--- %s exit."
  chinese "<--- %s 退出."

ER_SEMISYNC_RPL_INIT_FOR_TRX
  eng "Semi-sync replication initialized for transactions."
  chinese "已为事务初始化半同步复制。"

ER_SEMISYNC_FAILED_TO_ALLOCATE_TRX_NODE
  eng "%s: transaction node allocation failed for: (%s, %lu)."
  chinese "%s:事务节点分配失败:(%s,%lu)。"

ER_SEMISYNC_BINLOG_WRITE_OUT_OF_ORDER
  eng "%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu)."
  chinese "%s:binlog写入无序,尾部(%s,%lu),新节点(%s,%lu)。"

ER_SEMISYNC_INSERT_LOG_INFO_IN_ENTRY
  eng "%s: insert (%s, %lu) in entry(%u)."
  chinese "%s:插入(%s,%lu)在条目(%u)中。"

ER_SEMISYNC_PROBE_LOG_INFO_IN_ENTRY
  eng "%s: probe (%s, %lu) in entry(%u)."
  chinese "%s:探测(%s,%lu)在条目(%u)中。"

ER_SEMISYNC_CLEARED_ALL_ACTIVE_TRANSACTION_NODES
  eng "%s: cleared all nodes."
  chinese "%s:已清除所有节点。"

ER_SEMISYNC_CLEARED_ACTIVE_TRANSACTION_TILL_POS
  eng "%s: cleared %d nodes back until pos (%s, %lu)."
  chinese "%s:已清除%d个节点,直到位置(%s,%lu)。"

ER_SEMISYNC_REPLY_MAGIC_NO_ERROR
  eng "Read semi-sync reply magic number error."
  chinese "读取半同步回复幻数错误。"

ER_SEMISYNC_REPLY_PKT_LENGTH_TOO_SMALL
  eng "Read semi-sync reply length error: packet is too small."
  chinese "读取半同步回复长度错误:数据包太小。"

ER_SEMISYNC_REPLY_BINLOG_FILE_TOO_LARGE
  eng "Read semi-sync reply binlog file length too large."
  chinese "读取半同步回复binlog文件长度太大。"

ER_SEMISYNC_SERVER_REPLY
  eng "%s: Got reply(%s, %lu) from server %u."
  chinese "%s:收到回复(%s,%lu)从服务器%u。"

ER_SEMISYNC_FUNCTION_CALLED_TWICE
  eng "%s called twice."
  chinese "%s调用了两次。"

ER_SEMISYNC_RPL_ENABLED_ON_SOURCE
  eng "Semi-sync replication enabled on the source."
  chinese "已在主服务器上启用半同步复制。"

ER_SEMISYNC_SOURCE_OOM
  eng "Cannot allocate memory to enable semi-sync on the source."
  chinese "无法分配内存以在主服务器上启用半同步。"

ER_SEMISYNC_DISABLED_ON_SOURCE
  eng "Semi-sync replication disabled on the source."
  chinese "已在主服务器上禁用半同步复制。"

ER_SEMISYNC_FORCED_SHUTDOWN
  eng "SEMISYNC: Forced shutdown. Some updates might not be replicated."
  chinese "SEMISYNC:强制关闭。某些更新可能无法复制。"

ER_SEMISYNC_SOURCE_GOT_REPLY_AT_POS
  eng "%s: Got reply at (%s, %lu)."
  chinese "%s:在(%s,%lu)收到回复。"

ER_SEMISYNC_SOURCE_SIGNAL_ALL_WAITING_THREADS
  eng "%s: signal all waiting threads."
  chinese "%s:向所有等待的线程发送信号。"

ER_SEMISYNC_SOURCE_TRX_WAIT_POS
  eng "%s: wait pos (%s, %lu), repl(%d)."
  chinese "%s:等待位置(%s,%lu),重复位置(%d)。"

ER_SEMISYNC_BINLOG_REPLY_IS_AHEAD
  eng "%s: Binlog reply is ahead (%s, %lu)."
  chinese "%s:Binlog回复在前面(%s,%lu)。"

ER_SEMISYNC_MOVE_BACK_WAIT_POS
  eng "%s: move back wait position (%s, %lu)."
  chinese "%s:移回等待位置(%s,%lu)。"

ER_SEMISYNC_INIT_WAIT_POS
  eng "%s: init wait position (%s, %lu)."
  chinese "%s:初始化等待位置(%s,%lu)。"

ER_SEMISYNC_WAIT_TIME_FOR_BINLOG_SENT
  eng "%s: wait %lu ms for binlog sent (%s, %lu)."
  chinese "%s:等待%lu毫秒以等待发送的binlog(%s,%lu)。"

ER_SEMISYNC_WAIT_FOR_BINLOG_TIMEDOUT
  eng "Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu."
  chinese "等待回复binlog(文件:%s,位置:%lu)时超时,半同步到文件%s,位置%lu。"

ER_SEMISYNC_WAIT_TIME_ASSESSMENT_FOR_COMMIT_TRX_FAILED
  eng "Assessment of waiting time for commitTrx failed at wait position (%s, %lu)."
  chinese "在等待位置(%s,%lu)评估CommitTrx的等待时间失败。"

ER_SEMISYNC_RPL_SWITCHED_OFF
  eng "Semi-sync replication switched OFF."
  chinese "半同步复制已关闭。"

ER_SEMISYNC_RPL_SWITCHED_ON
  eng "Semi-sync replication switched ON at (%s, %lu)."
  chinese "半同步复制已在(%s,%lu)打开。"

ER_SEMISYNC_NO_SPACE_IN_THE_PKT
  eng "No enough space in the packet for semi-sync extra header, semi-sync replication disabled."
  chinese "数据包中没有足够的空间用于半同步额外标头,半同步复制已禁用。"

ER_SEMISYNC_SYNC_HEADER_UPDATE_INFO
  eng "%s: server(%d), (%s, %lu) sync(%d), repl(%d)."
  chinese "%s:服务器(%d),(%s,%lu)同步(%d),重复(%d)。"

ER_SEMISYNC_FAILED_TO_INSERT_TRX_NODE
  eng "Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu."
  chinese "半同步无法插入binlog文件的Tranx_node:%s,位置:%lu。"

ER_SEMISYNC_TRX_SKIPPED_AT_POS
  eng "%s: Transaction skipped at (%s, %lu)."
  chinese "%s:在(%s,%lu)跳过事务。"

ER_SEMISYNC_SOURCE_FAILED_ON_NET_FLUSH
  eng "Semi-sync source failed on net_flush() before waiting for replica reply."
  chinese "在等待副本回复之前,半同步主机在net_flush()上失败。"

ER_SEMISYNC_RECEIVED_ACK_IS_SMALLER
  eng "The received ack is smaller than m_greatest_ack."
  chinese "收到的ACK小于m_Greatest_ACK。"

ER_SEMISYNC_ADD_ACK_TO_SLOT
  eng "Add the ack into slot %u."
  chinese "将ACK添加到插槽%u中。"

ER_SEMISYNC_UPDATE_EXISTING_REPLICA_ACK
  eng "Update an exsiting ack in slot %u."
  chinese "更新插槽%u中的现有ACK。"

ER_SEMISYNC_FAILED_TO_START_ACK_RECEIVER_THD
  eng "Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d)."
  chinese "无法启动半同步确认接收器线程,无法创建线程(错误号:%d)。"

ER_SEMISYNC_STARTING_ACK_RECEIVER_THD
  eng "Starting ack receiver thread."
  chinese "正在启动确认接收器线程。"

ER_SEMISYNC_FAILED_TO_WAIT_ON_DUMP_SOCKET
  eng "Failed to wait on semi-sync dump sockets, error: errno=%d."
  chinese "无法等待半同步转储套接字,错误:错误号=%d。"

ER_SEMISYNC_STOPPING_ACK_RECEIVER_THREAD
  eng "Stopping ack receiver thread."
  chinese "停止确认接收器线程。"

ER_SEMISYNC_FAILED_REGISTER_REPLICA_TO_RECEIVER
  eng "Failed to register replica to semi-sync ACK receiver thread."
  chinese "无法将从属注册到半同步ACK接收器线程。"

ER_SEMISYNC_START_BINLOG_DUMP_TO_REPLICA
  eng "Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu)."
  chinese "将%s binlog_ump启动到从属服务器(server_id:%d),位置(%s,%lu)。"

ER_SEMISYNC_STOP_BINLOG_DUMP_TO_REPLICA
  eng "Stop %s binlog_dump to replica (server_id: %d)."
  chinese "停止%s binlog_转储到从属服务器(服务器ID:%d)。"

ER_SEMISYNC_UNREGISTER_TRX_OBSERVER_FAILED
  eng "unregister_trans_observer failed."
  chinese "unregister_trans_observer失败。"

ER_SEMISYNC_UNREGISTER_BINLOG_STORAGE_OBSERVER_FAILED
  eng "unregister_binlog_storage_observer failed."
  chinese "unregister_binlog_storage_observer失败。"

ER_SEMISYNC_UNREGISTER_BINLOG_TRANSMIT_OBSERVER_FAILED
  eng "unregister_binlog_transmit_observer failed."
  chinese "unregister_binlog_transmit_observer 失败。"

ER_SEMISYNC_UNREGISTERED_REPLICATOR
  eng "unregister_replicator OK."
  chinese "unregister_replicator 成功."

ER_SEMISYNC_SOCKET_FD_TOO_LARGE
  eng "Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE)."
  chinese "半同步从属套接字fd为%u。如果套接字fd大于%u(Fd_SETSIZE),则select()无法处理。"

ER_SEMISYNC_REPLICA_REPLY
  eng "%s: reply - %d."
  chinese "%s:回复-%d。"

ER_SEMISYNC_MISSING_MAGIC_NO_FOR_SEMISYNC_PKT
  eng "Missing magic number for semi-sync packet, packet len: %lu."
  chinese "缺少半同步数据包的幻数,数据包长度:%lu。"

ER_SEMISYNC_REPLICA_START
  eng "Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu."
  chinese "从属I/O线程:开始%s复制到主'%s@%s:%d'(在日志'%s'中位置%lu)。"

ER_SEMISYNC_REPLICA_REPLY_WITH_BINLOG_INFO
  eng "%s: reply (%s, %lu)."
  chinese "%s:回复(%s,%lu)。"

ER_SEMISYNC_REPLICA_NET_FLUSH_REPLY_FAILED
  eng "Semi-sync replica net_flush() reply failed."
  chinese "半同步从属Net_Flush()回复失败。"

ER_SEMISYNC_REPLICA_SEND_REPLY_FAILED
  eng "Semi-sync replica send reply failed: %s (%d)."
  chinese "半同步从属发送回复失败:%s(%d)。"

ER_SEMISYNC_EXECUTION_FAILED_ON_SOURCE
  eng "Execution failed on source: %s; error %d"
  chinese "在主服务器上执行失败:%s；错误%d"

ER_SEMISYNC_NOT_SUPPORTED_BY_SOURCE
  eng "Source server does not support semi-sync, fallback to asynchronous replication"
  chinese "主服务器不支持半同步,回退到异步复制"

ER_SEMISYNC_REPLICA_SET_FAILED
  eng "Set 'rpl_semi_sync_replica=1' on source failed"
  chinese "在主服务器上设置'RPL_SEMI_SYNC_REPLICATION=1'失败"

ER_SEMISYNC_FAILED_TO_STOP_ACK_RECEIVER_THD
  eng "Failed to stop ack receiver thread on my_thread_join, errno(%d)."
  chinese "无法停止MY_THREAD_JOIN上的ACK接收器线程,错误号(%d)。"

ER_FIREWALL_FAILED_TO_READ_FIREWALL_TABLES
  eng "Failed to read the firewall tables"
  chinese "无法读取防火墙表"

ER_FIREWALL_FAILED_TO_REG_DYNAMIC_PRIVILEGES
  eng "Failed to register dynamic privileges"
  chinese "无法注册动态权限"

ER_FIREWALL_RECORDING_STMT_WAS_TRUNCATED
  eng "Statement was truncated and not recorded: %s"
  chinese "语句被截断且未记录:%s"

ER_FIREWALL_RECORDING_STMT_WITHOUT_TEXT
  eng "Statement with no text was not recorded"
  chinese "未记录无文本的语句"

ER_FIREWALL_SUSPICIOUS_STMT
  eng "SUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %s"
  chinese "来自'%s'的可疑语句。原因:%s语句:%s"

ER_FIREWALL_ACCESS_DENIED
  eng "ACCESS DENIED for '%s'. Reason: %s Statement: %s"
  chinese "拒绝访问'%s'。原因:%s语句:%s"

ER_FIREWALL_SKIPPED_UNKNOWN_USER_MODE
  eng "Skipped unknown user mode '%s'"
  chinese "跳过未知用户模式'%s'"

ER_FIREWALL_RELOADING_CACHE
  eng "Reloading cache from disk"
  chinese "正在从磁盘重新加载缓存"

ER_FIREWALL_RESET_FOR_USER
  eng "FIREWALL RESET for '%s'"
  chinese "为'%s'重置防火墙"

ER_FIREWALL_STATUS_FLUSHED
  eng "Counters are reset to zero"
  chinese "计数器重置为零"

ER_KEYRING_LOGGER_ERROR_MSG
  eng "%s"
  chinese "%s"

ER_AUDIT_LOG_FILTER_IS_NOT_INSTALLED
  eng "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."

ER_AUDIT_LOG_SWITCHING_TO_INCLUDE_LIST
  eng "Previously exclude list is used, now we start using include list, exclude list is set to NULL."
  chinese "审核日志插件支持尚未安装的筛选。审核日志插件将在旧模式下运行,该模式将在下一个版本中禁用。"

ER_AUDIT_LOG_CANNOT_SET_LOG_POLICY_WITH_OTHER_POLICIES
  eng "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."
  chinese "无法同时设置AUDIT_LOG_CONNECTION_POLICY或AUDIT_LOG_STATEMENT_POLICY,请根据AUDIT_LOG_POLICY设置AUDIT_LOG_CONNECTION_POLICY和AUDIT_LOG_STATEMENT_POLICY。"

ER_AUDIT_LOG_ONLY_INCLUDE_LIST_USED
  eng "Both include and exclude lists provided, include list is preferred, exclude list is set to NULL."
  chinese "同时提供了包含列表和排除列表,首选包含列表,排除列表设置为空。"

ER_AUDIT_LOG_INDEX_MAP_CANNOT_ACCESS_DIR
  eng "Could not access '%s' directory."
  chinese "无法访问'%s'目录。"

ER_AUDIT_LOG_WRITER_RENAME_FILE_FAILED
  eng "Could not rename file from '%s' to '%s'."
  chinese "无法将文件从'%s'重命名为'%s'。"

ER_AUDIT_LOG_WRITER_DEST_FILE_ALREADY_EXISTS
  eng "File '%s' should not exist. It may be incomplete. The server crashed."
  chinese "文件'%s'不应该存在。它可能不完整。服务器崩溃。"

ER_AUDIT_LOG_WRITER_RENAME_FILE_FAILED_REMOVE_FILE_MANUALLY
  eng "Could not rename file from '%s' to '%s'. Remove the file manually."
  chinese "无法将文件从'%s'重命名为'%s'。请手动删除该文件。"

ER_AUDIT_LOG_WRITER_INCOMPLETE_FILE_RENAMED
  eng "Incomplete file renamed from '%s' to '%s'."
  chinese "不完整的文件已从'%s'重命名为'%s'。"

ER_AUDIT_LOG_WRITER_FAILED_TO_WRITE_TO_FILE
  eng "Error writing file \'%-.200s\' (errno: %d - %s)."
  chinese "写入文件\'%-.200s\'时出错(错误号:%d-%s)。"

ER_AUDIT_LOG_EC_WRITER_FAILED_TO_INIT_ENCRYPTION
  eng "Could not initialize audit log file encryption."
  chinese "无法初始化审核日志文件加密。"

ER_AUDIT_LOG_EC_WRITER_FAILED_TO_INIT_COMPRESSION
  eng "Could not initialize audit log file compression."
  chinese "无法初始化审核日志文件压缩。"

ER_AUDIT_LOG_EC_WRITER_FAILED_TO_CREATE_FILE
  eng "Could not create '%s' file for audit logging."
  chinese "无法为审核日志记录创建'%s'文件。"

ER_AUDIT_LOG_RENAME_LOG_FILE_BEFORE_FLUSH
  eng "Audit log file (%s) must be manually renamed before audit_log_flush is set to true."
  chinese "在AUDIT_LOG_FLUSH设置为TRUE之前,必须手动重命名审核日志文件(%s)。"

ER_AUDIT_LOG_FILTER_RESULT_MSG
  eng "%s"
  chinese "%s"

ER_AUDIT_LOG_JSON_READER_FAILED_TO_PARSE
  eng "Error parsing JSON event. Event not accessible."
  chinese "分析JSON事件时出错。事件不可访问。"

ER_AUDIT_LOG_JSON_READER_BUF_TOO_SMALL
  eng "Buffer is too small to hold JSON event. Number of events skipped: %zu."
  chinese "缓冲区太小,无法容纳JSON事件。跳过的事件数:%zu。"

ER_AUDIT_LOG_JSON_READER_FAILED_TO_OPEN_FILE
  eng "Could not open JSON file for reading. Reading next file if exists."
  chinese "无法打开JSON文件进行读取。正在读取下一个文件(如果存在)。"

ER_AUDIT_LOG_JSON_READER_FILE_PARSING_ERROR
  eng "JSON file parsing error. Reading next file if exists"
  chinese "JSON文件解析错误。如果存在正在读取下一个文件"

OBSOLETE_ER_AUDIT_LOG_FILTER_INVALID_COLUMN_COUNT
  eng "Invalid column count in the '%s.%s' table."
  chinese "'%s.%s'表中的列计数无效。"

OBSOLETE_ER_AUDIT_LOG_FILTER_INVALID_COLUMN_DEFINITION
  eng "Invalid column definition of the '%s.%s' table."
  chinese "'%s.%s'表的列定义无效。"

ER_AUDIT_LOG_FILTER_FAILED_TO_STORE_TABLE_FLDS
  eng "Could not store field of the %s table."
  chinese "无法存储%s表的字段。"

ER_AUDIT_LOG_FILTER_FAILED_TO_UPDATE_TABLE
  eng "Could not update %s table."
  chinese "无法更新%s表。"

ER_AUDIT_LOG_FILTER_FAILED_TO_INSERT_INTO_TABLE
  eng "Could not insert into %s table."
  chinese "无法插入到%s表中。"

ER_AUDIT_LOG_FILTER_FAILED_TO_DELETE_FROM_TABLE
  eng "Could not delete from %s table."
  chinese "无法从%s表中删除。"

ER_AUDIT_LOG_FILTER_FAILED_TO_INIT_TABLE_FOR_READ
  eng "Could not initialize %s table for reading."
  chinese "无法初始化%s表以进行读取。"

ER_AUDIT_LOG_FILTER_FAILED_TO_READ_TABLE
  eng "Could not read %s table."
  chinese "无法读取%s表。"

ER_AUDIT_LOG_FILTER_FAILED_TO_CLOSE_TABLE_AFTER_READING
  eng "Could not close %s table reading."
  chinese "无法关闭%s表读取。"

ER_AUDIT_LOG_FILTER_USER_AND_HOST_CANNOT_BE_EMPTY
  eng "Both user and host columns of %s table cannot be empty."
  chinese "%s表的用户列和主机列都不能为空。"

ER_AUDIT_LOG_FILTER_FLD_FILTERNAME_CANNOT_BE_EMPTY
  eng "Filtername column of %s table cannot be empty."
  chinese "%s表的筛选器名列不能为空。"

ER_VALIDATE_PWD_DICT_FILE_NOT_SPECIFIED
  eng "Dictionary file not specified"
  chinese "未指定词典文件"

ER_VALIDATE_PWD_DICT_FILE_NOT_LOADED
  eng "Dictionary file not loaded"
  chinese "未加载词典文件"

ER_VALIDATE_PWD_DICT_FILE_TOO_BIG
  eng "Dictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loaded"
  chinese "词典文件大小超过MAX_DICTIONARY_FILE_LENGTH,未加载"

ER_VALIDATE_PWD_FAILED_TO_READ_DICT_FILE
  eng "Exception while reading the dictionary file"
  chinese "读取词典文件时出现异常"

ER_VALIDATE_PWD_FAILED_TO_GET_FLD_FROM_SECURITY_CTX
  eng "Can't retrieve the %s from the security context"
  chinese "无法从安全上下文中检索%s"

ER_VALIDATE_PWD_FAILED_TO_GET_SECURITY_CTX
  eng "Can't retrieve the security context"
  chinese "无法检索安全上下文"

ER_VALIDATE_PWD_LENGTH_CHANGED
  eng "Effective value of validate_password_length is changed. New value is %d"
  chinese "VALIDATE_PASSWORD_LENGTH的有效值已更改。新值为%d"

ER_REWRITER_QUERY_ERROR_MSG
  eng "%s"
  chinese "%s"

ER_REWRITER_QUERY_FAILED
  eng "Rewritten query failed to parse:%s"
  chinese "重写的查询无法分析:%s"

ER_XPLUGIN_STARTUP_FAILED
  eng "Startup failed with error \"%s\""
  chinese "启动失败,错误为\"%s\""

OBSOLETE_ER_XPLUGIN_SERVER_EXITING
  eng "Exiting"
  chinese "退出"

OBSOLETE_ER_XPLUGIN_SERVER_EXITED
  eng "Exit done"
  chinese "退出完成"

ER_XPLUGIN_USING_SSL_CONF_FROM_SERVER
  eng "Using SSL configuration from MySQL Server"
  chinese "从MySQL服务器使用SSL配置"

ER_XPLUGIN_USING_SSL_CONF_FROM_MYSQLX
  eng "Using SSL configuration from Mysqlx Plugin"
  chinese "从Mysqlx插件使用SSL配置"

ER_XPLUGIN_FAILED_TO_USE_SSL_CONF
  eng "Neither MySQL Server nor Mysqlx Plugin has valid SSL configuration"
  chinese "MySQL服务器和Mysqlx插件都没有有效的SSL配置"

ER_XPLUGIN_USING_SSL_FOR_TLS_CONNECTION
  eng "Using %s for TLS connections"
  chinese "将%s用于TLS连接"

ER_XPLUGIN_REFERENCE_TO_SECURE_CONN_WITH_XPLUGIN
  eng "For more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation"
  chinese "有关详细信息,请参阅MySQL文档中的使用X插件的安全连接部分"

ER_XPLUGIN_ERROR_MSG
  eng "%s"
  chinese "%s"

ER_SHA_PWD_FAILED_TO_PARSE_AUTH_STRING
  eng "Failed to parse stored authentication string for %s. Please check if mysql.user table not corrupted"
  chinese "无法为%s解析存储的身份验证字符串。请检查mysql.user表是否已损坏"

ER_SHA_PWD_FAILED_TO_GENERATE_MULTI_ROUND_HASH
  eng "Error in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problem"
  chinese "为%s生成多轮哈希时出错。没有它插件无法执行身份验证。这可能是一个暂时性问题"

ER_SHA_PWD_AUTH_REQUIRES_RSA_OR_SSL
  eng "Authentication requires either RSA keys or SSL encryption"
  chinese "身份验证需要RSA密钥或SSL加密"

ER_SHA_PWD_RSA_KEY_TOO_LONG
  eng "RSA key cipher length of %u is too long. Max value is %u"
  chinese "%u的RSA密钥密码长度太长。最大值为%u"

ER_PLUGIN_COMMON_FAILED_TO_OPEN_FILTER_TABLES
  eng "Failed to open the %s filter tables"
  chinese "无法打开%s筛选表"

ER_PLUGIN_COMMON_FAILED_TO_OPEN_TABLE
  eng "Failed to open '%s.%s' %s table"
  chinese "无法打开'%s.%s'%s表"

ER_AUTH_LDAP_ERROR_LOGGER_ERROR_MSG
  eng "%s"
  chinese "%s"

ER_CONN_CONTROL_ERROR_MSG
  eng "%s"
  chinese "%s"

ER_GRP_RPL_ERROR_MSG
  eng "%s"
  chinese "%s"

ER_SHA_PWD_SALT_FOR_USER_CORRUPT
  eng "Password salt for user '%s' is corrupt"
  chinese "用户'%s'的密码密码已损坏"

ER_SYS_VAR_COMPONENT_OOM
  eng "Out of memory for component system variable '%s'."
  chinese "组件系统变量'%s'内存不足。"

ER_SYS_VAR_COMPONENT_VARIABLE_SET_READ_ONLY
  eng "variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag."
  chinese "组件%s的变量%s被强制为只读:没有UPDATE_FUNC和PLUGIN_VAR_MEMALLOC标志的字符串变量。"

ER_SYS_VAR_COMPONENT_UNKNOWN_VARIABLE_TYPE
  eng "Unknown variable type code 0x%x in component '%s'."
  chinese "未知变量类型代码0x%x(在组件'%s'中)。"

ER_SYS_VAR_COMPONENT_FAILED_TO_PARSE_VARIABLE_OPTIONS
  eng "Parsing options for variable '%s' failed."
  chinese "分析变量'%s'的选项失败。"

ER_SYS_VAR_COMPONENT_FAILED_TO_MAKE_VARIABLE_PERSISTENT
  eng "Setting persistent options for component variable '%s' failed."
  chinese "为组件变量'%s'设置永久选项失败。"

ER_COMPONENT_FILTER_CONFUSED
  eng "The log-filter component \"%s\" got confused at \"%s\" (state: %s) ..."
  chinese "日志筛选器组件\"%s\"在\"%s\"(状态:%s)被混淆..."

ER_STOP_REPLICA_IO_THREAD_DISK_SPACE
  eng "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."
  chinese "等待通道'%s'的I/O线程完成对磁盘的写入,然后停止。释放一些磁盘空间或使用'KILL'中止I/O线程操作。请注意,在旋转中继日志时中止I/O线程可能会损坏中继日志,需要重新启动服务器才能修复它。"

ER_LOG_FILE_CANNOT_OPEN
  eng "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."
  chinese "无法使用%s进行日志记录(错误%d-%s)。正在关闭服务器进程的日志记录。要再次打开它:解决问题,然后%s重新启动MySQL服务器。"

OBSOLETE_ER_UNABLE_TO_COLLECT_LOG_STATUS
  eng "Unable to collect information for column '%-.192s': %-.192s."
  chinese "无法收集列'%-.192s'的信息:%-.192s。"

OBSOLETE_ER_DEPRECATED_UTF8_ALIAS
  eng "'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous."
  chinese "'UTF8'当前是字符集UTF8MB3的别名,在将来的版本中将被UTF8MB4所取代。请考虑使用UTF8MB4,以便更加明确。"

OBSOLETE_ER_DEPRECATED_NATIONAL
  eng "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."
  chinese "National/NCHAR/NVARCHAR暗示字符集UTF8MB3,它将在将来的版本中被UTF8MB4取代。为了明确起见,请考虑使用CHAR(X)字符集UTF8MB4。"

OBSOLETE_ER_SLAVE_POSSIBLY_DIVERGED_AFTER_DDL
  eng "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."
  chinese "在主服务器和从属服务器上提交原子DDL语句失败。从属服务器支持原子DDL语句,但主服务器不支持,因此从属服务器和主服务器采取的操作可能不同。请检查它们的状态是否存在差异,然后再继续。"

ER_PERSIST_OPTION_STATUS
  eng "Configuring persisted options failed: \"%s\"."
  chinese "配置持久化选项失败:'%s'。"

ER_NOT_IMPLEMENTED_GET_TABLESPACE_STATISTICS
  eng "The storage engine '%-.192s' does not provide dynamic table statistics"
  chinese "存储引擎'%-.192s'不提供动态表统计信息"

OBSOLETE_ER_UNABLE_TO_SET_OPTION
  eng "This option cannot be set %s."
  chinese "无法设置此选项%s。"

OBSOLETE_ER_RESERVED_TABLESPACE_NAME
  eng "The table '%-.192s' may not be created in the reserved tablespace '%-.192s'."
  chinese "表'%-.192s'不能在保留的表空间'%-.192s'中创建。"

ER_SSL_FIPS_MODE_ERROR
   eng "SSL fips mode error: %s"
  chinese "SSL FIPS模式错误:%s"

ER_CONN_INIT_CONNECT_IGNORED
  eng "init_connect variable is ignored for user: %s host: %s due to expired password."
  chinese "由于密码过期,用户%s主机%s的init_CONNECT变量被忽略。"

OBSOLETE_ER_UNSUPPORTED_SQL_MODE
  eng "sql_mode=0x%08x is not supported"
  chinese "不支持SQL_MODE=0x%08x"

ER_REWRITER_OOM
  eng "Out of memory."
  chinese "内存不足。"

ER_REWRITER_TABLE_MALFORMED_ERROR
  eng "Wrong column count or names when loading rules."
  chinese "加载规则时出现错误的列数或名称。"

ER_REWRITER_LOAD_FAILED
  eng "Some rules failed to load."
  chinese "无法加载某些规则。"

ER_REWRITER_READ_FAILED
  eng "Got error from storage engine while refreshing rewrite rules."
  chinese "刷新重写规则时从存储引擎获取错误。"

ER_CONN_CONTROL_EVENT_COORDINATOR_INIT_FAILED
  eng "Failed to initialize Connection_event_coordinator"
  chinese "无法初始化CONNECTION_EVENT_COLIDATOR"

ER_CONN_CONTROL_STAT_CONN_DELAY_TRIGGERED_UPDATE_FAILED
  eng "Failed to update connection delay triggered stats"
  chinese "无法更新连接延迟触发的统计信息"

ER_CONN_CONTROL_STAT_CONN_DELAY_TRIGGERED_RESET_FAILED
  eng "Failed to reset connection delay triggered stats"
  chinese "无法重置连接延迟触发统计信息"

ER_CONN_CONTROL_INVALID_CONN_DELAY_TYPE
  eng "Unexpected option type for connection delay."
  chinese "连接延迟的意外选项类型。"

ER_CONN_CONTROL_DELAY_ACTION_INIT_FAILED
  eng "Failed to initialize Connection_delay_action"
  chinese "无法初始化CONNECTION_DELAY_ACTION"

ER_CONN_CONTROL_FAILED_TO_SET_CONN_DELAY
  eng "Could not set %s delay for connection delay."
  chinese "无法为连接延迟设置%s延迟。"

ER_CONN_CONTROL_FAILED_TO_UPDATE_CONN_DELAY_HASH
  eng "Failed to update connection delay hash for account : %s"
  chinese "无法更新帐户%s的连接延迟哈希"

ER_XPLUGIN_FORCE_STOP_CLIENT
  eng "%s: Force stopping client because exception occurred: %s"
  chinese "%s:由于发生异常而强制停止客户端:%s"

ER_XPLUGIN_MAX_AUTH_ATTEMPTS_REACHED
  eng "%s.%u: Maximum number of authentication attempts reached, login failed."
  chinese "%s.%u:已达到最大身份验证尝试次数,登录失败。"

ER_XPLUGIN_BUFFER_PAGE_ALLOC_FAILED
  eng "Error allocating Buffer_page: %s"
  chinese "分配BUFFER_PAGE时出错:%s"

ER_XPLUGIN_DETECTED_HANGING_CLIENTS
  eng "Detected %u hanging client(s)"
  chinese "检测到%u个挂起的客户端"

ER_XPLUGIN_FAILED_TO_ACCEPT_CLIENT
  eng "Error accepting client"
  chinese "接受客户端时出错"

ER_XPLUGIN_FAILED_TO_SCHEDULE_CLIENT
  eng "Internal error scheduling client for execution"
  chinese "安排客户端执行时发生内部错误"

ER_XPLUGIN_FAILED_TO_PREPARE_IO_INTERFACES
  eng "Preparation of I/O interfaces failed, X Protocol won't be accessible"
  chinese "准备I/O接口失败,将无法访问X协议"

ER_XPLUGIN_SRV_SESSION_INIT_THREAD_FAILED
  eng "srv_session_init_thread returned error"
  chinese "srv_SESSION_INIT_THREAD返回错误"

ER_XPLUGIN_UNABLE_TO_USE_USER_SESSION_ACCOUNT
  eng "Unable to use user mysql.session account when connecting the server for internal plugin requests."
  chinese "在连接服务器以进行内部插件请求时,无法使用用户mysql.ession帐户。"

ER_XPLUGIN_REFERENCE_TO_USER_ACCOUNT_DOC_SECTION
  eng "For more information, please see the X Plugin User Account section in the MySQL documentation"
  chinese "有关详细信息,请参阅MySQL文档中的X插件用户帐户部分"

ER_XPLUGIN_UNEXPECTED_EXCEPTION_DISPATCHING_CMD
  eng "%s: Unexpected exception dispatching command: %s"
  chinese "%s:调度命令时出现意外异常:%s"

ER_XPLUGIN_EXCEPTION_IN_TASK_SCHEDULER
  eng "Exception in post: %s"
  chinese "开机自检中出现异常:%s"

ER_XPLUGIN_TASK_SCHEDULING_FAILED
  eng "Internal error scheduling task"
  chinese "计划任务时出现内部错误"

ER_XPLUGIN_EXCEPTION_IN_EVENT_LOOP
  eng "Exception in event loop: \"%s\": %s"
  chinese "事件循环中出现异常:\"%s\":%s"

ER_XPLUGIN_LISTENER_SETUP_FAILED
  eng "Setup of %s failed, %s"
  chinese "设置%s失败,%s"

ER_XPLUING_NET_STARTUP_FAILED
  eng "%s"
  chinese "%s"

ER_XPLUGIN_FAILED_AT_SSL_CONF
  eng "Failed at SSL configuration: \"%s\""
  chinese "SSL配置失败:\"%s\""

OBSOLETE_ER_XPLUGIN_CLIENT_SSL_HANDSHAKE_FAILED
  eng "Error during SSL handshake for client connection (%i)"

OBSOLETE_ER_XPLUGIN_SSL_HANDSHAKE_WITH_SERVER_FAILED
  eng "%s: Error during SSL handshake"
  chinese "%s:在SSL握手期间出错"

ER_XPLUGIN_FAILED_TO_CREATE_SESSION_FOR_CONN
  eng "%s: Error creating session for connection from %s"
  chinese "%s:从%s为连接创建会话时出错"

ER_XPLUGIN_FAILED_TO_INITIALIZE_SESSION
  eng "%s: Error initializing session for connection: %s"
  chinese "%s:初始化连接的会话时出错:%s"

ER_XPLUGIN_MESSAGE_TOO_LONG
  eng "%s: Message of size %u received, exceeding the limit of %i"

ER_XPLUGIN_UNINITIALIZED_MESSAGE
  eng "Message is not properly initialized: %s"
  chinese "消息未正确初始化:%s"

ER_XPLUGIN_FAILED_TO_SET_MIN_NUMBER_OF_WORKERS
  eng "Unable to set minimal number of workers to %u; actual value is %i"

ER_XPLUGIN_UNABLE_TO_ACCEPT_CONNECTION
  eng "Unable to accept connection, disconnecting client"
  chinese "无法接受连接,正在断开客户端连接"

ER_XPLUGIN_ALL_IO_INTERFACES_DISABLED
  eng "All I/O interfaces are disabled, X Protocol won't be accessible"
  chinese "所有I/O接口都被禁用,将无法访问X协议"

OBSOLETE_ER_XPLUGIN_INVALID_MSG_DURING_CLIENT_INIT
  eng "%s: Invalid message %i received during client initialization"

OBSOLETE_ER_XPLUGIN_CLOSING_CLIENTS_ON_SHUTDOWN
  eng "%s: closing client because of shutdown (state: %i)"

ER_XPLUGIN_ERROR_READING_SOCKET
  eng "%s: Error reading from socket %s (%i)"

ER_XPLUGIN_PEER_DISCONNECTED_WHILE_READING_MSG_BODY
  eng "%s: peer disconnected while reading message body"
  chinese "%s:读取邮件正文时对等方断开连接"

ER_XPLUGIN_READ_FAILED_CLOSING_CONNECTION
  eng "client_id:%s - %s while reading from socket, closing connection"
  chinese "从套接字读取时,客户端ID:%s-%s,正在关闭连接"

OBSOLETE_ER_XPLUGIN_INVALID_AUTH_METHOD
  eng "%s.%u: Invalid authentication method %s"
  chinese "%s.%u:身份验证方法%s无效"

OBSOLETE_ER_XPLUGIN_UNEXPECTED_MSG_DURING_AUTHENTICATION
  eng "%s: Unexpected message of type %i received during authentication"

OBSOLETE_ER_XPLUGIN_ERROR_WRITING_TO_CLIENT
  eng "Error writing to client: %s (%i)"

OBSOLETE_ER_XPLUGIN_SCHEDULER_STARTED
  eng "Scheduler \"%s\" started."
  chinese "计划程序\"%s\"已启动。"

OBSOLETE_ER_XPLUGIN_SCHEDULER_STOPPED
  eng "Scheduler \"%s\" stopped."
  chinese "计划程序\"%s\"已停止。"

ER_XPLUGIN_LISTENER_SYS_VARIABLE_ERROR
  eng "Please see the MySQL documentation for '%s' system variables to fix the error"
  chinese "请参阅'%s'系统变量的MySQL文档以修复错误"

ER_XPLUGIN_LISTENER_STATUS_MSG
  eng "X Plugin ready for connections. %s"
  chinese "X插件已准备好连接。%s"

ER_XPLUGIN_RETRYING_BIND_ON_PORT
  eng "Retrying `bind()` on TCP/IP port %i"

OBSOLETE_ER_XPLUGIN_SHUTDOWN_TRIGGERED
  eng "Shutdown triggered by mysqld abort flag"
  chinese "由mysqld中止标志触发的关闭"

OBSOLETE_ER_XPLUGIN_USER_ACCOUNT_WITH_ALL_PERMISSIONS
  eng "Using %s account for authentication which has all required permissions"
  chinese "使用%s帐户进行身份验证,该帐户具有所有必需的权限"

ER_XPLUGIN_EXISTING_USER_ACCOUNT_WITH_INCOMPLETE_GRANTS
  eng "Using existing %s account for authentication. Incomplete grants will be fixed"
  chinese "使用现有%s帐户进行身份验证。不完整的授权将被修复"

OBSOLETE_ER_XPLUGIN_SERVER_STARTS_HANDLING_CONNECTIONS
  eng "Server starts handling incoming connections"
  chinese "服务器开始处理传入连接"

OBSOLETE_ER_XPLUGIN_SERVER_STOPPED_HANDLING_CONNECTIONS
  eng "Stopped handling incoming connections"
  chinese "已停止处理传入连接"

OBSOLETE_ER_XPLUGIN_FAILED_TO_INTERRUPT_SESSION
  eng "%s: Could not interrupt client session"
  chinese "%s:无法中断客户端会话"

OBSOLETE_ER_XPLUGIN_CLIENT_RELEASE_TRIGGERED
  eng "%s: release triggered by timeout in state:%i"

ER_XPLUGIN_IPv6_AVAILABLE
  eng "IPv6 is available"
  chinese "IPv6可用"

OBSOLETE_ER_XPLUGIN_UNIX_SOCKET_NOT_CONFIGURED
  eng "UNIX socket not configured"
  chinese "未配置UNIX套接字"

ER_XPLUGIN_CLIENT_KILL_MSG
  eng "Kill client: %i %s"
  chinese "终止客户端:%i %s"

ER_XPLUGIN_FAILED_TO_GET_SECURITY_CTX
  eng "Could not get security context for session"
  chinese "无法获取会话的安全上下文"

OBSOLETE_ER_XPLUGIN_FAILED_TO_SWITCH_SECURITY_CTX_TO_ROOT
  eng "Unable to switch security context to root"
  chinese "无法将安全上下文切换到根目录"

ER_XPLUGIN_FAILED_TO_CLOSE_SQL_SESSION
  eng "Error closing SQL session"
  chinese "关闭SQL会话时出错"

ER_XPLUGIN_FAILED_TO_EXECUTE_ADMIN_CMD
  eng "Error executing admin command %s: %s"
  chinese "执行管理命令%s时出错:%s"

ER_XPLUGIN_EMPTY_ADMIN_CMD
  eng "Error executing empty admin command"
  chinese "执行空管理命令时出错"

ER_XPLUGIN_FAILED_TO_GET_SYS_VAR
  eng "Unable to retrieve system variable \'%s\'"
  chinese "无法检索系统变量\'%s\'"

ER_XPLUGIN_FAILED_TO_GET_CREATION_STMT
  eng "Unable to get creation stmt for collection \'%s\'; query result size: %lu"
  chinese "无法获取集合\'%s\'的创建stmt；查询结果大小:%lu"

ER_XPLUGIN_FAILED_TO_GET_ENGINE_INFO
  eng "Unable to get engine info for collection \'%s\'; creation stmt: %s"
  chinese "无法获取集合\'%s\'的引擎信息；创建stmt:%s"

OBSOLETE_ER_XPLUGIN_FAIL_TO_GET_RESULT_DATA
  eng "Error getting result data: %s"
  chinese "获取结果数据时出错:%s"

OBSOLETE_ER_XPLUGIN_CAPABILITY_EXPIRED_PASSWORD
  eng "Capability expired password failed with error: %s"
  chinese "功能过期密码失败,错误为:%s"

ER_XPLUGIN_FAILED_TO_SET_SO_REUSEADDR_FLAG
  eng "Failed to set SO_REUSEADDR flag (error: %d)."
  chinese "无法设置SO_REUSEADDR标志(错误:%d)。"

ER_XPLUGIN_FAILED_TO_OPEN_INTERNAL_SESSION
  eng "Could not open internal MySQL session"
  chinese "无法打开内部MySQL会话"

ER_XPLUGIN_FAILED_TO_SWITCH_CONTEXT
  eng "Unable to switch context to user %s"
  chinese "无法将上下文切换到用户%s"

ER_XPLUGIN_FAILED_TO_UNREGISTER_UDF
  eng "Can\'t unregister \'%s\' user defined function"
  chinese "无法注销\'%s\'用户定义函数"

OBSOLETE_ER_XPLUGIN_GET_PEER_ADDRESS_FAILED
  eng "%s: get peer address failed, can't resolve IP to hostname"
  chinese "%s:获取对等地址失败,无法将IP解析为主机名"

OBSOLETE_ER_XPLUGIN_CAPABILITY_CLIENT_INTERACTIVE_FAILED
  eng "Capability client interactive failed with error: %s"
  chinese "功能客户端交互失败,错误为:%s"

ER_XPLUGIN_FAILED_TO_RESET_IPV6_V6ONLY_FLAG
  eng "Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only."
  chinese "无法重置IPv6_V6ONLY标志(错误:%d)。服务器将仅侦听IPv6地址。"

ER_KEYRING_INVALID_KEY_TYPE
  eng "Invalid key type"
  chinese "无效的密钥类型"

ER_KEYRING_INVALID_KEY_LENGTH
  eng "Invalid key length for given block cipher"
  chinese "给定块密码的密钥长度无效"

OBSOLETE_ER_KEYRING_FAILED_TO_CREATE_KEYRING_DIR
  eng "Could not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets provided"
  chinese "无法创建KEYRING目录。在提供KEYRING目录的正确路径之前,KEYRING_FILE将不可用"

OBSOLETE_ER_KEYRING_FILE_INIT_FAILED
  eng "keyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets provided"
  chinese "KEYRING_FILE初始化失败。请检查指向可读KEYRING文件的KEYRING_FILE_DATA或是否可以在指定位置创建KEYRING文件。在提供KEYRING文件的正确路径之前,KEYRING_FILE将不可用"

OBSOLETE_ER_KEYRING_INTERNAL_EXCEPTION_FAILED_FILE_INIT
  eng "keyring_file initialization failure due to internal exception inside the plugin."
  chinese "由于插件内部出现内部异常,KEYRING_FILE初始化失败。"

OBSOLETE_ER_KEYRING_FAILED_TO_GENERATE_KEY
  eng "Failed to generate a key due to internal exception inside keyring_file plugin"
  chinese "由于KEYRING_FILE插件内部异常,无法生成密钥"

ER_KEYRING_CHECK_KEY_FAILED_DUE_TO_INVALID_KEY
  eng "Error while %s key: invalid key_type"
  chinese "%s密钥时出错:KEY_TYPE无效"

ER_KEYRING_CHECK_KEY_FAILED_DUE_TO_EMPTY_KEY_ID
  eng "Error while %s key: key_id cannot be empty"
  chinese "%s密钥时出错:key_id不能为空"

ER_KEYRING_OPERATION_FAILED_DUE_TO_INTERNAL_ERROR
  eng "Failed to %s due to internal exception inside %s plugin"
  chinese "由于%s插件内部出现内部异常,%s失败"

ER_KEYRING_INCORRECT_FILE
  eng "Incorrect Keyring file"
  chinese "不正确的密钥环文件"

ER_KEYRING_FOUND_MALFORMED_BACKUP_FILE
  eng "Found malformed keyring backup file - removing it"
  chinese "发现格式错误的密钥环备份文件-正在将其删除"

ER_KEYRING_FAILED_TO_RESTORE_FROM_BACKUP_FILE
  eng "Error while restoring keyring from backup file cannot overwrite keyring with backup"
  chinese "从备份文件恢复KEYRING时出错,无法用备份覆盖KEYRING"

ER_KEYRING_FAILED_TO_FLUSH_KEYRING_TO_FILE
  eng "Error while flushing in-memory keyring into keyring file"
  chinese "将内存中的密钥环刷新到密钥环文件时出错"

ER_KEYRING_FAILED_TO_GET_FILE_STAT
  eng "Error while reading stat for %s.Please check if file %s was not removed. OS returned this error: %s"
  chinese "读取%s的STAT时出错。请检查文件%s是否未被删除。操作系统返回此错误:%s"

ER_KEYRING_FAILED_TO_REMOVE_FILE
  eng "Could not remove file %s OS retuned this error: %s"
  chinese "无法删除文件%s操作系统返回此错误:%s"

ER_KEYRING_FAILED_TO_TRUNCATE_FILE
  eng "Could not truncate file %s. OS retuned this error: %s"
  chinese "无法截断文件%s。操作系统返回此错误:%s"

ER_KEYRING_UNKNOWN_ERROR
  eng "Unknown error %d"
  chinese "未知错误%d"

OBSOLETE_ER_KEYRING_FAILED_TO_SET_KEYRING_FILE_DATA
  eng "keyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path"
  chinese "无法将KEYRING_FILE_DATA设置为新值,因为无法在提供的路径中创建/访问KEYRING文件"

ER_KEYRING_FILE_IO_ERROR
  eng "%s"
  chinese "%s"

ER_KEYRING_FAILED_TO_LOAD_KEYRING_CONTENT
  eng "Error while loading keyring content. The keyring might be malformed"
  chinese "加载密钥环内容时出错。密钥环可能格式不正确"

ER_KEYRING_FAILED_TO_FLUSH_KEYS_TO_KEYRING
  eng "Could not flush keys to keyring"
  chinese "无法将密钥刷新到密钥环"

ER_KEYRING_FAILED_TO_FLUSH_KEYS_TO_KEYRING_BACKUP
  eng "Could not flush keys to keyring's backup"
  chinese "无法将密钥刷新到密钥环的备份"

ER_KEYRING_KEY_FETCH_FAILED_DUE_TO_EMPTY_KEY_ID
  eng "Error while fetching key: key_id cannot be empty"
  chinese "获取密钥时出错:key_id不能为空"

ER_KEYRING_FAILED_TO_REMOVE_KEY_DUE_TO_EMPTY_ID
  eng "Error while removing key: key_id cannot be empty"
  chinese "删除密钥时出错:key_id不能为空"

ER_KEYRING_OKV_INCORRECT_KEY_VAULT_CONFIGURED
  eng "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"
  chinese "要初始化KEYRING_OKV,请将KEYRING_OKV_CONF_DIR变量指向包含Oracle Key Vault配置文件和SSL材料的目录"

ER_KEYRING_OKV_INIT_FAILED_DUE_TO_INCORRECT_CONF
  eng "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."
  chinese "KEYRING_OKV初始化失败。请检查KEYRING_OKV_CONF_DIR是否指向可读目录,并且该目录是否包含Oracle Key Vault配置文件和SSL材料。还请检查Oracle Key Vault是否已启动并正在运行。"

ER_KEYRING_OKV_INIT_FAILED_DUE_TO_INTERNAL_ERROR
  eng "keyring_okv initialization failure due to internal exception inside the plugin"
  chinese "插件内部出现内部异常,导致KEYRING_OKV初始化失败"

ER_KEYRING_OKV_INVALID_KEY_TYPE
  eng "Invalid key type"
  chinese "无效的密钥类型"

ER_KEYRING_OKV_INVALID_KEY_LENGTH_FOR_CIPHER
  eng "Invalid key length for given block cipher"
  chinese "给定块密码的密钥长度无效"

ER_KEYRING_OKV_FAILED_TO_GENERATE_KEY_DUE_TO_INTERNAL_ERROR
  eng "Failed to generate a key due to internal exception inside keyring_okv plugin"
  chinese "由于KEYRING_OKV插件内部异常,无法生成密钥"

ER_KEYRING_OKV_FAILED_TO_FIND_SERVER_ENTRY
  eng "Could not find entry for server in configuration file %s"
  chinese "在配置文件%s中找不到服务器的条目"

ER_KEYRING_OKV_FAILED_TO_FIND_STANDBY_SERVER_ENTRY
  eng "Could not find entry for standby server in configuration file %s"
  chinese "在配置文件%s中找不到备用服务器的条目"

ER_KEYRING_OKV_FAILED_TO_PARSE_CONF_FILE
  eng "Could not parse the %s file provided"
  chinese "无法分析提供的%s文件"

ER_KEYRING_OKV_FAILED_TO_LOAD_KEY_UID
  eng "Could not load keys' uids from the OKV server"
  chinese "无法从OKV服务器加载密钥的UID"

ER_KEYRING_OKV_FAILED_TO_INIT_SSL_LAYER
  eng "Could not initialize ssl layer"
  chinese "无法初始化SSL层"

ER_KEYRING_OKV_FAILED_TO_INIT_CLIENT
  eng "Could not initialize OKV client"
  chinese "无法初始化OKV客户端"

ER_KEYRING_OKV_CONNECTION_TO_SERVER_FAILED
  eng "Could not connect to the OKV server"
  chinese "无法连接到OKV服务器"

ER_KEYRING_OKV_FAILED_TO_REMOVE_KEY
  eng "Could not remove the key"
  chinese "无法删除密钥"

ER_KEYRING_OKV_FAILED_TO_ADD_ATTRIBUTE
  eng "Could not add attribute, attribute_name=%s attribute value=%s"
  chinese "无法添加属性,ATTRIBUTE_NAME=%s属性值=%s"

ER_KEYRING_OKV_FAILED_TO_GENERATE_KEY
  eng "Could not generate the key."
  chinese "无法生成密钥。"

ER_KEYRING_OKV_FAILED_TO_STORE_KEY
  eng "Could not store the key."
  chinese "无法存储密钥。"

ER_KEYRING_OKV_FAILED_TO_ACTIVATE_KEYS
  eng "Could not activate the key."
  chinese "无法激活密钥。"

ER_KEYRING_OKV_FAILED_TO_FETCH_KEY
  eng "Could not fetch generated key"
  chinese "无法获取生成的密钥"

ER_KEYRING_OKV_FAILED_TO_STORE_OR_GENERATE_KEY
  eng "Could not store/generate the key - failed to set key attribute x-key-ready"
  chinese "无法存储/生成密钥-无法设置密钥属性x-Key-Ready"

ER_KEYRING_OKV_FAILED_TO_RETRIEVE_KEY_SIGNATURE
  eng "Could not retrieve key signature from custom attributes"
  chinese "无法从自定义属性检索密钥签名"

ER_KEYRING_OKV_FAILED_TO_RETRIEVE_KEY
  eng "Could not retrieve key from OKV"
  chinese "无法从OKV检索密钥"

ER_KEYRING_OKV_FAILED_TO_LOAD_SSL_TRUST_STORE
  eng "Error loading trust store"
  chinese "加载信任存储时出错"

ER_KEYRING_OKV_FAILED_TO_SET_CERTIFICATE_FILE
  eng "Error setting the certificate file."
  chinese "设置证书文件时出错。"

ER_KEYRING_OKV_FAILED_TO_SET_KEY_FILE
  eng "Error setting the key file."
  chinese "设置密钥文件时出错。"

ER_KEYRING_OKV_KEY_MISMATCH
  eng "Private key does not match the certificate public key"
  chinese "私钥与证书公钥不匹配"

OBSOLETE_ER_KEYRING_ENCRYPTED_FILE_INCORRECT_KEYRING_FILE
  eng "Incorrect Keyring file"
  chinese "不正确的密钥环文件"

OBSOLETE_ER_KEYRING_ENCRYPTED_FILE_DECRYPTION_FAILED
  eng "Keyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value."
  chinese "KEYRING_ENCRYPTED_FILE解密失败。请验证--KEYRING-ENCRYPTED-FILE-PASSWORD选项的值。"

OBSOLETE_ER_KEYRING_ENCRYPTED_FILE_FOUND_MALFORMED_BACKUP_FILE
  eng "Found malformed keyring backup file - removing it"
  chinese "发现格式错误的密钥环备份文件-正在将其删除"

OBSOLETE_ER_KEYRING_ENCRYPTED_FILE_FAILED_TO_RESTORE_KEYRING
  eng "Error while restoring keyring from backup file cannot overwrite keyring with backup"
  chinese "从备份文件恢复KEYRING时出错,无法用备份覆盖KEYRING"

OBSOLETE_ER_KEYRING_ENCRYPTED_FILE_FAILED_TO_FLUSH_KEYRING
  eng "Error while flushing in-memory keyring into keyring file"
  chinese "将内存中的密钥环刷新到密钥环文件时出错"

OBSOLETE_ER_KEYRING_ENCRYPTED_FILE_ENCRYPTION_FAILED
  eng "Keyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value."
  chinese "KEYRING_ENCRYPTED_FILE加密失败。请验证--KEYRING-ENCRYPTED-FILE-PASSWORD选项的值。"

OBSOLETE_ER_KEYRING_ENCRYPTED_FILE_INVALID_KEYRING_DIR
  eng "keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path"
  chinese "无法将KEYRING_ENCRYPTED_FILE_DATA设置为新值,因为无法在提供的路径中创建/访问KEYRING文件"

OBSOLETE_ER_KEYRING_ENCRYPTED_FILE_FAILED_TO_CREATE_KEYRING_DIR
  eng "Could not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets provided"
  chinese "无法创建KEYRING目录在提供KEYRING目录的正确路径之前,KEYRING_ENCRYPTED_FILE将保持不可用状态"

OBSOLETE_ER_KEYRING_ENCRYPTED_FILE_PASSWORD_IS_INVALID
  eng "The keyring_encrypted_file_password must be set to a valid value."
  chinese "必须将KEYRING_ENCRYPTED_FILE_PASSWORD设置为有效值。"

OBSOLETE_ER_KEYRING_ENCRYPTED_FILE_PASSWORD_IS_TOO_LONG
  eng "Too long keyring_encrypted_file_password value."
  chinese "KEYRING_ENCRYPTED_FILE_PASSWORD值太长。"

OBSOLETE_ER_KEYRING_ENCRYPTED_FILE_INIT_FAILURE
  eng "keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct."
  chinese "KEYRING_ENCRYPTED_FILE初始化失败。请检查指向可读KEYRING文件的KEYRING_ENCRYPTED_FILE_DATA是否可在指定位置创建KEYRING文件或解密KEYRING文件的密码是否正确。"

OBSOLETE_ER_KEYRING_ENCRYPTED_FILE_INIT_FAILED_INTERNAL_ERROR
  eng "keyring_encrypted_file initialization failure due to internal exception inside the plugin"
  chinese "插件内部出现内部异常,导致KEYRING_ENCRYPTED_FILE初始化失败"

OBSOLETE_ER_KEYRING_ENCRYPTED_FILE_GEN_KEY_FAILED_INTERNAL_ERROR
  eng "Failed to generate a key due to internal exception inside keyring_encrypted_file plugin"
  chinese "由于KEYRING_ENCRYPTED_FILE插件内部异常,无法生成密钥"

ER_KEYRING_AWS_FAILED_TO_SET_CMK_ID
  eng "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."
  chinese "无法将KEYRING_AWS_CMK_ID设置为新值,因为AWS KMS似乎无法理解提供的ID。请检查提供的CMK ID是否正确。"

ER_KEYRING_AWS_FAILED_TO_SET_REGION
  eng "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."
  chinese "无法将KEYRING_AWS_REGION设置为新值,因为AWS KMS似乎不理解提供的区域。请检查提供的区域是否正确。"

ER_KEYRING_AWS_FAILED_TO_OPEN_CONF_FILE
  eng "Could not open keyring_aws configuration file: %s. OS returned this error: %s"
  chinese "无法打开KEYRING_AWS配置文件:%s。操作系统返回此错误:%s"

ER_KEYRING_AWS_FAILED_TO_ACCESS_KEY_ID_FROM_CONF_FILE
  eng "Could not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %s"
  chinese "无法从KEYRING_AWS配置文件读取AWS访问密钥ID:%s。操作系统返回此错误:%s"

ER_KEYRING_AWS_FAILED_TO_ACCESS_KEY_FROM_CONF_FILE
  eng "Could not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %s"
  chinese "无法从KEYRING_AWS配置文件读取AWS访问密钥:%s。操作系统返回此错误:%s"

ER_KEYRING_AWS_INVALID_CONF_FILE_PATH
  eng "Path to keyring aws configuration file cannot be empty"
  chinese "密钥环AWS配置文件的路径不能为空"

ER_KEYRING_AWS_INVALID_DATA_FILE_PATH
  eng "Path to keyring_aws storage file cannot be empty."
  chinese "KEYRING_AWS存储文件路径不能为空。"

ER_KEYRING_AWS_FAILED_TO_ACCESS_OR_CREATE_KEYRING_DIR
  eng "Unable to create/access keyring directory."
  chinese "无法创建/访问密钥环目录。"

ER_KEYRING_AWS_FAILED_TO_ACCESS_OR_CREATE_KEYRING_DATA_FILE
  eng "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."
  chinese "无法创建/访问KEYRING_AWS存储文件。请检查KEYRING_AWS_DATA_FILE是否指向可以创建/访问KEYRING文件的位置。还请确保MySQL服务器的用户有足够高的权限访问此位置。"

ER_KEYRING_AWS_FAILED_TO_INIT_DUE_TO_INTERNAL_ERROR
  eng "keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:"
  chinese "由于初始化同步原语时出现内部错误,KEYRING_AWS初始化失败-%s。操作系统返回此错误:%s:"

ER_KEYRING_AWS_FAILED_TO_ACCESS_DATA_FILE
  eng "Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Server"
  chinese "无法访问所提供路径中的KEYRING_AWS存储文件。请检查MySQL服务器是否可以访问KEYRING_AWS目录"

ER_KEYRING_AWS_CMK_ID_NOT_SET
  eng "keyring_aws_cmk_id has to be set"
  chinese "必须设置KEYRING_AWS_CMK_ID"

ER_KEYRING_AWS_FAILED_TO_GET_KMS_CREDENTIAL_FROM_CONF_FILE
  eng "Could not get AWS KMS credentials from the configuration file"
  chinese "无法从配置文件获取AWS KMS凭据"

ER_KEYRING_AWS_INIT_FAILURE
  eng "keyring_aws initialization failure."
  chinese "Keyring_AWS初始化失败。"

ER_KEYRING_AWS_FAILED_TO_INIT_DUE_TO_PLUGIN_INTERNAL_ERROR
  eng "keyring_aws initialization failure due to internal exception inside the plugin"
  chinese "插件内部出现内部异常,导致KEYRING_AWS初始化失败"

ER_KEYRING_AWS_INVALID_KEY_LENGTH_FOR_CIPHER
  eng "Invalid key length for given block cipher"
  chinese "给定块密码的密钥长度无效"

ER_KEYRING_AWS_FAILED_TO_GENERATE_KEY_DUE_TO_INTERNAL_ERROR
  eng "Failed to generate a key due to internal exception inside keyring_file plugin"
  chinese "由于KEYRING_FILE插件内部异常,无法生成密钥"

ER_KEYRING_AWS_INCORRECT_FILE
  eng "Incorrect Keyring file"
  chinese "不正确的密钥环文件"

ER_KEYRING_AWS_FOUND_MALFORMED_BACKUP_FILE
  eng "Found malformed keyring backup file - removing it"
  chinese "发现格式错误的密钥环备份文件-正在将其删除"

ER_KEYRING_AWS_FAILED_TO_RESTORE_FROM_BACKUP_FILE
  eng "Error while restoring keyring from backup file cannot overwrite keyring with backup"
  chinese "从备份文件恢复KEYRING时出错,无法用备份覆盖KEYRING"

ER_KEYRING_AWS_FAILED_TO_FLUSH_KEYRING_TO_FILE
  eng "Error while flushing in-memory keyring into keyring file"
  chinese "将内存中的密钥环刷新到密钥环文件时出错"

ER_KEYRING_AWS_INCORRECT_REGION
  eng "Wrong region"
  chinese "错误的地域"

ER_KEYRING_AWS_FAILED_TO_CONNECT_KMS
  eng "Could not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %s"
  chinese "无法使用提供的凭据连接到AWS KMS。请确保凭据正确。AWS KMS返回此错误:%s"

ER_KEYRING_AWS_FAILED_TO_GENERATE_NEW_KEY
  eng "Could not generate a new key. AWS KMS returned this error: %s"
  chinese "无法生成新密钥。AWS KMS返回此错误:%s"

ER_KEYRING_AWS_FAILED_TO_ENCRYPT_KEY
  eng "Could not encrypt key. AWS KMS returned this error: %s"
  chinese "无法加密密钥。AWS KMS返回此错误:%s"

ER_KEYRING_AWS_FAILED_TO_RE_ENCRYPT_KEY
  eng "Could not re-encrypt key. AWS KMS returned this error: %s"
  chinese "无法重新加密密钥。AWS KMS返回此错误:%s"

ER_KEYRING_AWS_FAILED_TO_DECRYPT_KEY
  eng "Could not decrypt key. AWS KMS returned this error: %s"
  chinese "无法解密密钥。AWS KMS返回此错误:%s"

ER_KEYRING_AWS_FAILED_TO_ROTATE_CMK
  eng "Could not rotate the CMK. AWS KMS returned this error: %s"
  chinese "无法旋转CMK。AWS KMS返回此错误:%s"

ER_GRP_RPL_GTID_ALREADY_USED
  eng "The requested GTID '%s:%lld' was already used, the transaction will rollback."
  chinese "请求的GTID'%s:%lld'已被使用,事务将回滚。"

ER_GRP_RPL_APPLIER_THD_KILLED
  eng "The group replication applier thread was killed."
  chinese "组复制应用程序线程已终止。"

ER_GRP_RPL_EVENT_HANDLING_ERROR
  eng "Error at event handling! Got error: %d."
  chinese "处理事件时出错！收到错误:%d。"

ER_GRP_RPL_ERROR_GTID_EXECUTION_INFO
  eng "Error when extracting group GTID execution information, some recovery operations may face future issues."
  chinese "提取组GTID执行信息时出错,某些恢复操作可能会面临未来的问题。"

ER_GRP_RPL_CERTIFICATE_SIZE_ERROR
  eng "An error occurred when trying to reduce the Certification information size for transmission."
  chinese "尝试减小证书信息大小以进行传输时出错。"

ER_GRP_RPL_CREATE_APPLIER_CACHE_ERROR
  eng "Failed to create group replication pipeline applier cache!"
  chinese "无法创建组复制管道应用程序缓存！"

ER_GRP_RPL_UNBLOCK_WAITING_THD
  eng "Unblocking the group replication thread waiting for applier to start, as the start group replication was killed."
  chinese "取消阻止正在等待应用程序启动的组复制线程,因为启动组复制已终止。"

ER_GRP_RPL_APPLIER_PIPELINE_NOT_DISPOSED
  eng "The group replication applier pipeline was not properly disposed. Check the error log for further info."
  chinese "未正确处理组复制应用程序管道。有关详细信息,请查看错误日志。"

ER_GRP_RPL_APPLIER_THD_EXECUTION_ABORTED
  eng "The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group."
  chinese "应用程序线程执行已中止。无法处理更多事务,此成员现在将离开该组。"

ER_GRP_RPL_APPLIER_EXECUTION_FATAL_ERROR
  eng "Fatal error during execution on the Applier process of Group Replication. The server will now leave the group."
  chinese "在组复制的应用程序进程上执行时发生致命错误。服务器现在将离开该组。"

ER_GRP_RPL_ERROR_STOPPING_CHANNELS
  eng "Error stopping all replication channels while server was leaving the group. %s"
  chinese "服务器离开组时停止所有复制通道时出错。%s"

ER_GRP_RPL_ERROR_SENDING_SINGLE_PRIMARY_MSSG
  eng "Error sending single primary message informing that primary did apply relay logs."
  chinese "发送通知主服务器确实应用了中继日志的单个主服务器消息时出错。"

OBSOLETE_ER_GRP_RPL_UPDATE_TRANS_SNAPSHOT_VER_ERROR
  eng "Error updating transaction snapshot version after transaction being positively certified."
  chinese "在事务被确认认证后更新事务快照版本时出错。"

OBSOLETE_ER_GRP_RPL_SIDNO_FETCH_ERROR
  eng "Error fetching transaction sidno after transaction being positively certified."
  chinese "在事务被确认认证后获取事务SIDNO时出错。"

ER_GRP_RPL_BROADCAST_COMMIT_TRANS_MSSG_FAILED
  eng "Broadcast of committed transactions message failed."
  chinese "广播提交的事务消息失败。"

ER_GRP_RPL_GROUP_NAME_PARSE_ERROR
  eng "Unable to parse the group_replication_group_name during the Certification module initialization."
  chinese "无法在证书模块初始化期间分析GROUP_REPLICATION_GROUP_NAME。"

ER_GRP_RPL_ADD_GRPSID_TO_GRPGTIDSID_MAP_ERROR
  eng "Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization."
  chinese "在认证模块初始化期间,无法在group_gtid_sid_map中添加group_sid。"

ER_GRP_RPL_UPDATE_GRPGTID_EXECUTED_ERROR
  eng "Error updating group_gtid_executed GITD set during the Certification module initialization."
  chinese "在证书模块初始化期间更新GROUP_GTID_EXECUTED GITD集时出错。"

ER_GRP_RPL_DONOR_TRANS_INFO_ERROR
  eng "Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error."
  chinese "初始化冲突检测组件时,无法处理提供方的交易信息。可能是内存不足错误。"

ER_GRP_RPL_SERVER_CONN_ERROR
  eng "Error when establishing a server connection during the Certification module initialization."
  chinese "在证书模块初始化期间建立服务器连接时出错。"

ER_GRP_RPL_ERROR_FETCHING_GTID_EXECUTED_SET
  eng "Error when extracting this member GTID executed set. Certification module can't be properly initialized."
  chinese "提取此成员GTID执行集时出错。无法正确初始化证书模块。"

ER_GRP_RPL_ADD_GTID_TO_GRPGTID_EXECUTED_ERROR
  eng "Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization."
  chinese "在认证模块初始化期间,将服务器GTID EXECUTE集合添加到GROUP_GTID_EXECUTE时出错。"

ER_GRP_RPL_ERROR_FETCHING_GTID_SET
  eng "Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized."
  chinese "提取为其应用程序检索的此成员集时出错。无法正确初始化证书模块。"

ER_GRP_RPL_ADD_RETRIEVED_SET_TO_GRP_GTID_EXECUTED_ERROR
  eng "Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization."
  chinese "在证书模块初始化期间,将检索到的成员集添加到组_gtid_Executed时出错。"

ER_GRP_RPL_CERTIFICATION_INITIALIZATION_FAILURE
  eng "Error during Certification module initialization."
  chinese "认证模块初始化过程中出错。"

ER_GRP_RPL_UPDATE_LAST_CONFLICT_FREE_TRANS_ERROR
  eng "Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction."
  chinese "无法更新上一个无冲突的事务,将不会在performance_schema.replication_group_member_stats.last_conflict_free_transaction上跟踪此事务"

ER_GRP_RPL_UPDATE_TRANS_SNAPSHOT_REF_VER_ERROR
  eng "Error updating transaction snapshot version reference for internal storage."
  chinese "更新内部存储的事务快照版本引用时出错。"

OBSOLETE_ER_GRP_RPL_FETCH_TRANS_SIDNO_ERROR
  eng "Error fetching transaction sidno while adding to the group_gtid_executed set."
  chinese "将GROUP_GTID_EXECUTED集合添加到GROUP_GTID_EXECUTED集合时获取事务SIDNO时出错。"

OBSOLETE_ER_GRP_RPL_ERROR_VERIFYING_SIDNO
  eng "Error while ensuring the sidno be present in the group_gtid_executed."
  chinese "确保组_gtid_Executed中存在SIDNO时出错。"

ER_GRP_RPL_CANT_GENERATE_GTID
  eng "Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name."
  chinese "无法生成全局事务标识符:整数部分已达到最大值。请使用新的GROUP_REPLICATION_GROUP_NAME重新启动该组。"

ER_GRP_RPL_INVALID_GTID_SET
  eng "Invalid stable transactions set."
  chinese "设置的稳定事务无效。"

ER_GRP_RPL_UPDATE_GTID_SET_ERROR
  eng "Error updating stable transactions set."
  chinese "更新稳定事务集时出错。"

ER_GRP_RPL_RECEIVED_SET_MISSING_GTIDS
  eng "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."
  chinese "在应用程序通道接收集上填充缺少的GTID时出错。尽管不是关键的,但从长远来看,这可能会导致性能问题。"

ER_GRP_RPL_SKIP_COMPUTATION_TRANS_COMMITTED
  eng "Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing."
  chinese "跳过TRANSACTIONS_COMMITTED_ALL_MEMBERS字段作为此计算的较旧实例的计算仍在进行中。"

ER_GRP_RPL_NULL_PACKET
  eng "Null packet on certifier's queue."
  chinese "认证器队列上的数据包为空。"

ER_GRP_RPL_CANT_READ_GTID
  eng "Error reading GTIDs from the message."
  chinese "从消息中读取GTID时出错。"

ER_GRP_RPL_PROCESS_GTID_SET_ERROR
  eng "Error processing stable transactions set."
  chinese "处理稳定事务集时出错。"

ER_GRP_RPL_PROCESS_INTERSECTION_GTID_SET_ERROR
  eng "Error processing intersection of stable transactions set."
  chinese "处理稳定事务集的交集时出错。"

ER_GRP_RPL_SET_STABLE_TRANS_ERROR
  eng "Error setting stable transactions set."
  chinese "设置稳定事务集时出错。"

ER_GRP_RPL_CANT_READ_GRP_GTID_EXTRACTED
  eng "Error reading group_gtid_extracted from the View_change_log_event."
  chinese "读取从View_Change_LOG_EVENT中提取的group_gtid_时出错。"

ER_GRP_RPL_CANT_READ_WRITE_SET_ITEM
  eng "Error reading the write set item '%s' from the View_change_log_event."
  chinese "从VIEW_CHANGE_LOG_EVENT读取写入集项目'%s'时出错。"

ER_GRP_RPL_INIT_CERTIFICATION_INFO_FAILURE
  eng "Error during certification_info initialization."
  chinese "CERTIFICATION_INFO初始化期间出错。"

ER_GRP_RPL_CONFLICT_DETECTION_DISABLED
  eng "Primary had applied all relay logs, disabled conflict detection."
  chinese "主服务器已应用所有中继日志,并禁用了冲突检测。"

ER_GRP_RPL_MSG_DISCARDED
  eng "Message received while the plugin is not ready, message discarded."
  chinese "插件未就绪时收到消息,消息已丢弃。"

ER_GRP_RPL_MISSING_GRP_RPL_APPLIER
  eng "Message received without a proper group replication applier."
  chinese "在没有正确的组复制应用程序的情况下收到消息。"

ER_GRP_RPL_CERTIFIER_MSSG_PROCESS_ERROR
  eng "Error processing message in Certifier."
  chinese "在认证器中处理消息时出错。"

ER_GRP_RPL_SRV_NOT_ONLINE
  eng "This server was not declared online since it is on status %s."
  chinese "此服务器未声明为联机,因为它处于状态%s。"

ER_GRP_RPL_SRV_ONLINE
  eng "This server was declared online within the replication group."
  chinese "此服务器已在复制组中声明为联机。"

ER_GRP_RPL_DISABLE_SRV_READ_MODE_RESTRICTED
  eng "When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually."
  chinese "在声明插件联机时,无法禁用服务器读取模式设置。请尝试手动禁用它。"

ER_GRP_RPL_MEM_ONLINE
  eng "The member with address %s:%u was declared online within the replication group."
  chinese "地址为%s:%u的成员在复制组中被声明为联机。"

ER_GRP_RPL_MEM_UNREACHABLE
  eng "Member with address %s:%u has become unreachable."
  chinese "无法访问地址为%s:%u的成员。"

ER_GRP_RPL_MEM_REACHABLE
  eng "Member with address %s:%u is reachable again."
  chinese "地址为%s:%u的成员再次可访问。"

ER_GRP_RPL_SRV_BLOCKED
  eng "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."
  chinese "此服务器无法访问组中的大多数成员。此服务器现在将阻止所有更新。服务器将保持阻止状态,直到恢复与大多数成员的联系。可以使用GROUP_REPLICATION_FORCE_MEMBERS强制新的组成员身份。"

ER_GRP_RPL_SRV_BLOCKED_FOR_SECS
  eng "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."
  chinese "此服务器无法访问组中的大多数成员。此服务器现在将阻止所有更新。服务器将在接下来的%lu秒内保持阻止状态。除非恢复与大多数成员的联系,否则此时间之后成员将出错并离开组。可以使用GROUP_REPLICATION_FORCE_MEMBERS强制新的组成员身份。"

ER_GRP_RPL_CHANGE_GRP_MEM_NOT_PROCESSED
  eng "A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option."
  chinese "已收到组成员身份更改,但由于配置的group_replication_unreachable_majority_timeout超时选项,插件已离开。"

ER_GRP_RPL_MEMBER_CONTACT_RESTORED
  eng "The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked."
  chinese "该成员已恢复与群中大多数成员的联系。正常运行已恢复,交易已解锁。"

ER_GRP_RPL_MEMBER_REMOVED
  eng "Members removed from the group: %s"
  chinese "已从组中删除成员:%s"

ER_GRP_RPL_PRIMARY_MEMBER_LEFT_GRP
  eng "Primary server with address %s left the group. Electing new Primary."
  chinese "地址为%s的主服务器已离开组。正在选择新的主服务器。"

ER_GRP_RPL_MEMBER_ADDED
  eng "Members joined the group: %s"
  chinese "成员加入组:%s"

ER_GRP_RPL_MEMBER_EXIT_PLUGIN_ERROR
  eng "There was a previous plugin error while the member joined the group. The member will now exit the group."
  chinese "成员加入组时出现以前的插件错误。成员现在将退出组。"

ER_GRP_RPL_MEMBER_CHANGE
  eng "Group membership changed to %s on view %s."
  chinese "组成员身份已更改为%s(在视图%s上)。"

ER_GRP_RPL_MEMBER_LEFT_GRP
  eng "Group membership changed: This member has left the group."
  chinese "组成员身份已更改:此成员已离开组。"

ER_GRP_RPL_MEMBER_EXPELLED
  eng "Member was expelled from the group due to network failures, changing member status to ERROR."
  chinese "由于网络故障,成员被逐出组,将成员状态更改为错误。"

ER_GRP_RPL_SESSION_OPEN_FAILED
  eng "Unable to open session to (re)set read only mode. Skipping."
  chinese "无法打开会话以(重新)设置只读模式。正在跳过。"

ER_GRP_RPL_NEW_PRIMARY_ELECTED
  eng "A new primary with address %s:%u was elected. %s"
  chinese "已选举地址为%s:%u的新主服务器。%s"

ER_GRP_RPL_DISABLE_READ_ONLY_FAILED
  eng "Unable to disable super read only flag. Try to disable it manually"
  chinese "无法禁用超级只读标志。尝试手动禁用它"

ER_GRP_RPL_ENABLE_READ_ONLY_FAILED
  eng "Unable to set super read only flag. Try to set it manually."
  chinese "无法设置超级只读标志。请尝试手动设置。"

ER_GRP_RPL_SRV_PRIMARY_MEM
  eng "This server is working as primary member."
  chinese "此服务器正在作为主要成员工作。"

ER_GRP_RPL_SRV_SECONDARY_MEM
  eng "This server is working as secondary member with primary member address %s:%u."
  chinese "此服务器作为主要成员地址为%s:%u的辅助成员工作。"

ER_GRP_RPL_NO_SUITABLE_PRIMARY_MEM
  eng "Unable to set any member as primary. No suitable candidate."
  chinese "无法将任何成员设置为主要成员。没有合适的候选人。"

ER_GRP_RPL_SUPER_READ_ONLY_ACTIVATE_ERROR
  eng "Error when activating super_read_only mode on start. The member will now exit the group."
  chinese "启动时激活SUPER_READ_ONLY模式时出错。成员现在将退出组。"

ER_GRP_RPL_EXCEEDS_AUTO_INC_VALUE
  eng "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."
  chinese "组包含%lu个成员,大于GROUP_REPLICATION_AUTO_INCREMENT_INCREMENT值%lu。这可能会导致较高的事务中止率。"

ER_GRP_RPL_DATA_NOT_PROVIDED_BY_MEM
  eng "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."
  chinese "地址为'%s:%u'的成员在上次组更改期间未提供任何数据。组信息可能已过时,并导致恢复时出错。"

ER_GRP_RPL_MEMBER_ALREADY_EXISTS
  eng "There is already a member with server_uuid %s. The member will now exit the group."
  chinese "已存在SERVER_UUID为%s的成员。该成员现在将退出该组。"

OBSOLETE_ER_GRP_RPL_GRP_CHANGE_INFO_EXTRACT_ERROR
  eng "Error when extracting information for group change. Operations and checks made to group joiners may be incomplete."
  chinese "提取组更改信息时出错。对组加入器进行的操作和检查可能不完整。"

ER_GRP_RPL_GTID_EXECUTED_EXTRACT_ERROR
  eng "Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete."
  chinese "提取此成员GTID执行集时出错。对组联结器进行的操作和检查可能不完整。"

ER_GRP_RPL_GTID_SET_EXTRACT_ERROR
  eng "Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete."
  chinese "提取为其应用程序检索的此成员集时出错。对组连接器进行的操作和检查可能不完整。"

ER_GRP_RPL_START_FAILED
  eng "The START GROUP_REPLICATION command failed since the group already has 9 members."
  chinese "由于组已有9个成员,因此START GROUP_REPLICATION命令失败。"

ER_GRP_RPL_MEMBER_VER_INCOMPATIBLE
  eng "Member version is incompatible with the group."
  chinese "成员版本与组不兼容。"

ER_GRP_RPL_TRANS_NOT_PRESENT_IN_GRP
  eng "The member contains transactions not present in the group. The member will now exit the group."
  chinese "该成员包含组中不存在的事务。该成员现在将退出该组。"

ER_GRP_RPL_TRANS_GREATER_THAN_GRP
  eng "It was not possible to assess if the member has more transactions than the group. The member will now exit the group."
  chinese "无法评估该成员的交易量是否比群多。该成员现在将退出群。"

ER_GRP_RPL_MEMBER_VERSION_LOWER_THAN_GRP
  eng "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."
  chinese "成员版本低于某些组成员,但由于启用了选项'group_replication_allow_local_lower_version_join,因此将允许成员加入。"

ER_GRP_RPL_LOCAL_GTID_SETS_PROCESS_ERROR
  eng "Error processing local GTID sets when comparing this member transactions against the group."
  chinese "将此成员事务与组进行比较时,处理本地GTID集时出错。"

ER_GRP_RPL_MEMBER_TRANS_GREATER_THAN_GRP
  eng "This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %s"
  chinese "此成员的已执行事务多于组中的事务。本地事务:%s>组事务:%s"

ER_GRP_RPL_BLOCK_SIZE_DIFF_FROM_GRP
  eng "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."
  chinese "该成员配置了GROUP_REPLICATION_GTID_ASSIGNMENT_BLOCK_SIZE选项值'%llu',与组'%llu'不同。该成员现在将退出该组。"

ER_GRP_RPL_TRANS_WRITE_SET_EXTRACT_DIFF_FROM_GRP
  eng "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."
  chinese "该成员配置了一个事务-写入-设置-提取选项值'%s',与组'%s'不同。该成员现在将退出该组。"

ER_GRP_RPL_MEMBER_CFG_INCOMPATIBLE_WITH_GRP_CFG
  eng "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])."
  chinese "成员配置与组配置不兼容。变量GROUP_REPLICATION_SINGLE_PRIMARY_MODE或group_replication_enforce_update_everywhere_checks在组中的每台服务器上必须具有相同的值。(成员配置选项:[%s],组配置选项:[%s])。"

ER_GRP_RPL_MEMBER_STOP_RPL_CHANNELS_ERROR
  eng "Error stopping all replication channels while server was leaving the group. %s"
  chinese "服务器离开组时停止所有复制通道时出错。%s"

ER_GRP_RPL_PURGE_APPLIER_LOGS
  eng "Detected previous RESET BINARY LOGS AND GTIDS invocation or an issue exists in the group replication applier relay log. Purging existing applier logs."
  chinese "检测到以前的重置主调用或组复制应用程序中继日志中存在问题。正在清除现有应用日志。"

ER_GRP_RPL_RESET_APPLIER_MODULE_LOGS_ERROR
  eng "Unknown error occurred while resetting applier's module logs."
  chinese "重置应用程序的模块日志时发生未知错误。"

ER_GRP_RPL_APPLIER_THD_SETUP_ERROR
  eng "Failed to setup the group replication applier thread."
  chinese "无法设置组复制应用程序线程。"

ER_GRP_RPL_APPLIER_THD_START_ERROR
  eng "Error while starting the group replication applier thread"
  chinese "启动组复制应用程序线程时出错"

ER_GRP_RPL_APPLIER_THD_STOP_ERROR
  eng "Failed to stop the group replication applier thread."
  chinese "无法停止组复制应用程序线程。"

ER_GRP_RPL_FETCH_TRANS_DATA_FAILED
  eng "Failed to fetch transaction data containing required transaction info for applier"
  chinese "无法获取包含申请者所需交易信息的交易数据"

ER_GRP_RPL_REPLICA_IO_THD_PRIMARY_UNKNOWN
  eng "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."
  chinese "当组复制以单主模式运行并且主成员未知时,无法启动通道'%s'的从属IO线程。"

ER_GRP_RPL_SALVE_IO_THD_ON_SECONDARY_MEMBER
  eng "Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member."
  chinese "当组复制在辅助成员上以单主模式运行时,无法启动通道'%s'的从属IO线程。"

ER_GRP_RPL_REPLICA_SQL_THD_PRIMARY_UNKNOWN
  eng "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."
  chinese "当组复制以单主模式运行并且主成员未知时,无法启动通道'%s'的从属SQL线程。"

ER_GRP_RPL_REPLICA_SQL_THD_ON_SECONDARY_MEMBER
  eng "Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member."
  chinese "当组复制在辅助成员上以单主模式运行时,无法启动通道'%s'的从属SQL线程。"

ER_GRP_RPL_NEEDS_INNODB_TABLE
  eng "Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication."
  chinese "表%s未使用InnoDB存储引擎。这与组复制不兼容。"

ER_GRP_RPL_PRIMARY_KEY_NOT_DEFINED
  eng "Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication."
  chinese "表%s没有任何主键。这与组复制不兼容。"

ER_GRP_RPL_FK_WITH_CASCADE_UNSUPPORTED
  eng "Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication."
  chinese "表%s的外键带有'CASCADE'、'SET NULL'或'SET DEFAULT'子句。这与组复制不兼容。"

ER_GRP_RPL_AUTO_INC_RESET
  eng "group_replication_auto_increment_increment is reset to %lu"
  chinese "GROUP_REPLICATION_AUTO_INCREMENT_INCREMENT被重置为%lu"

ER_GRP_RPL_AUTO_INC_OFFSET_RESET
  eng "auto_increment_offset is reset to %lu"
  chinese "AUTO_INCREMENT_OFFSET被重置为%lu"

ER_GRP_RPL_AUTO_INC_SET
  eng "group_replication_auto_increment_increment is set to %lu"
  chinese "GROUP_REPLICATION_AUTO_INCREMENT_INCREMENT设置为%lu"

ER_GRP_RPL_AUTO_INC_OFFSET_SET
  eng "auto_increment_offset is set to %lu"
  chinese "AUTO_INCREMENT_OFFSET设置为%lu"

ER_GRP_RPL_FETCH_TRANS_CONTEXT_FAILED
  eng "Failed to fetch transaction context containing required transaction info for certification"
  chinese "无法获取包含认证所需事务信息的事务上下文"

ER_GRP_RPL_FETCH_FORMAT_DESC_LOG_EVENT_FAILED
  eng "Failed to fetch Format_description_log_event containing required server info for applier"
  chinese "无法获取包含Applier所需服务器信息的FORMAT_DESCRIPTION_LOG_EVENT"

ER_GRP_RPL_FETCH_TRANS_CONTEXT_LOG_EVENT_FAILED
  eng "Failed to fetch Transaction_context_log_event containing required transaction info for certification"
  chinese "无法获取包含认证所需事务信息的TRANSACTION_CONTEXT_LOG_EVENT"

ER_GRP_RPL_FETCH_SNAPSHOT_VERSION_FAILED
  eng "Failed to read snapshot version from transaction context event required for certification"
  chinese "无法从认证所需的事务上下文事件中读取快照版本"

ER_GRP_RPL_FETCH_GTID_LOG_EVENT_FAILED
  eng "Failed to fetch Gtid_log_event containing required transaction info for certification"
  chinese "无法获取包含认证所需事务信息的GTID_LOG_EVENT"

ER_GRP_RPL_UPDATE_SERV_CERTIFICATE_FAILED
  eng "Unable to update certification result on server side, thread_id: %lu"
  chinese "无法更新服务器端的认证结果,线程ID:%lu"

ER_GRP_RPL_ADD_GTID_INFO_WITH_LOCAL_GTID_FAILED
  eng "Unable to add gtid information to the group_gtid_executed set when gtid was provided for local transactions"
  chinese "为本地事务提供GTID时,无法将GTID信息添加到GROUP_GTID_EXECUTED集合"

ER_GRP_RPL_ADD_GTID_INFO_WITHOUT_LOCAL_GTID_FAILED
  eng "Unable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactions"
  chinese "未为本地事务提供GTID时,无法将GTID信息添加到GROUP_GTID_EXECUTED集合"

ER_GRP_RPL_NOTIFY_CERTIFICATION_OUTCOME_FAILED
  eng "Failed to notify certification outcome"
  chinese "未能通知认证结果"

ER_GRP_RPL_ADD_GTID_INFO_WITH_REMOTE_GTID_FAILED
  eng "Unable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactions"
  chinese "为远程事务提供GTID时,无法将GTID信息添加到GROUP_GTID_EXECUTED集合"

ER_GRP_RPL_ADD_GTID_INFO_WITHOUT_REMOTE_GTID_FAILED
  eng "Unable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactions"
  chinese "未为远程事务提供GTID时,无法将GTID信息添加到GROUP_GTID_EXECUTED集合"

ER_GRP_RPL_FETCH_VIEW_CHANGE_LOG_EVENT_FAILED
  eng "Failed to fetch View_change_log_event containing required info for certification"
  chinese "无法获取包含认证所需信息的View_CHANGE_LOG_EVENT"

OBSOLETE_ER_GRP_RPL_CONTACT_WITH_SRV_FAILED
  eng "Error when contacting the server to ensure the proper logging of a group change in the binlog"
  chinese "联系服务器以确保在binlog中正确记录组更改时出错"

OBSOLETE_ER_GRP_RPL_SRV_WAIT_TIME_OUT
  eng "Timeout when waiting for the server to execute local transactions in order assure the group change proper logging"
  chinese "等待服务器执行本地事务以确保组更改正确记录时超时"

ER_GRP_RPL_FETCH_LOG_EVENT_FAILED
  eng "Failed to fetch Log_event containing required server info for applier"
  chinese "无法获取包含应用程序所需服务器信息的Log_Event"

ER_GRP_RPL_START_GRP_RPL_FAILED
  eng "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."
  chinese "无法启动组复制。复制应用程序基础结构未初始化,因为在服务器升级时使用--INITIALIZE、--INITIALIZE-INSECURE或--UPDATE=MINIMAL启动了服务器。"

ER_GRP_RPL_CONN_INTERNAL_PLUGIN_FAIL
  eng "Failed to establish an internal server connection to execute plugin operations"
  chinese "无法建立内部服务器连接以执行插件操作"

ER_GRP_RPL_SUPER_READ_ON
  eng "Setting super_read_only=ON."
  chinese "正在设置SUPER_READ_ONLY=ON。"

ER_GRP_RPL_SUPER_READ_OFF
  eng "Setting super_read_only=OFF."
  chinese "设置SUPER_READ_ONLY=OFF。"

ER_GRP_RPL_KILLED_SESSION_ID
  eng "killed session id: %d status: %d"
  chinese "已终止会话ID:%d状态:%d"

ER_GRP_RPL_KILLED_FAILED_ID
  eng "killed failed id: %d failed: %d"
  chinese "终止失败ID:%d失败:%d"

ER_GRP_RPL_INTERNAL_QUERY
  eng "Internal query: %s result in error. Error number: %ld"
  chinese "内部查询:%s导致错误。错误号:%ld"

ER_GRP_RPL_COPY_FROM_EMPTY_STRING
  eng "Error copying from empty string "
  chinese "从空字符串复制时出错"

ER_GRP_RPL_QUERY_FAIL
  eng "Query execution resulted in failure. errno: %d"
  chinese "查询执行导致失败。错误号:%d"

ER_GRP_RPL_CREATE_SESSION_UNABLE
  eng "Unable to create a session for executing the queries on the server"
  chinese "无法创建用于在服务器上执行查询的会话"

ER_GRP_RPL_MEMBER_NOT_FOUND
  eng "The member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connection"
  chinese "地址为%s:%u的成员意外消失,终止当前组复制恢复连接"

ER_GRP_RPL_MAXIMUM_CONNECTION_RETRIES_REACHED
  eng "Maximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery."
  chinese "已达到尝试连接到原服务器时的最大重试次数。正在中止组复制增量恢复。"

ER_GRP_RPL_ALL_DONORS_LEFT_ABORT_RECOVERY
  eng "All donors left. Aborting group replication incremental recovery."
  chinese "所有捐赠者都已离开。正在中止组复制增量恢复。"

ER_GRP_RPL_ESTABLISH_RECOVERY_WITH_DONOR
  eng "Establishing group recovery connection with a possible donor. Attempt %d/%d"
  chinese "正在与可能的供方建立组恢复连接。尝试%d/%d"

ER_GRP_RPL_ESTABLISH_RECOVERY_WITH_ANOTHER_DONOR
  eng "Retrying group recovery connection with another donor. Attempt %d/%d"
  chinese "正在重试与另一原供方的组恢复连接。尝试%d/%d"

ER_GRP_RPL_NO_VALID_DONOR
  eng "No valid donors exist in the group, retrying"
  chinese "组中不存在有效的捐赠者,正在重试"

ER_GRP_RPL_CONFIG_RECOVERY
  eng "Error when configuring the asynchronous recovery channel connection to the donor."
  chinese "配置与原服务器的异步恢复通道连接时出错。"

ER_GRP_RPL_ESTABLISHING_CONN_GRP_REC_DONOR
  eng "Establishing connection to a group replication recovery donor %s at %s port: %d."
  chinese "正在建立与组复制恢复提供方%s的连接,位于%s端口:%d。"

ER_GRP_RPL_CREATE_GRP_RPL_REC_CHANNEL
  eng "Error while creating the group replication recovery channel with donor %s at %s port: %d."
  chinese "使用%s端口上的原%s创建组复制恢复通道时出错:%d。"

ER_GRP_RPL_DONOR_SERVER_CONN
  eng "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."
  chinese "连接到原服务器时出错。请检查GROUP_REPLICATION_RECOVERY通道凭据和PERFORMANCE_SCHEMA的所有MEMBER_HOST列值是否正确并且是可解析的DNS。"

ER_GRP_RPL_CHECK_STATUS_TABLE
  eng "For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery."
  chinese "有关详细信息,请查看通道GROUP_REPLICATION_RECOVERY的performance_schema.replication_connection_status表和从属I/O的错误日志消息。"

ER_GRP_RPL_STARTING_GRP_REC
  eng "Error while starting the group replication incremental recovery receiver/applier threads"
  chinese "启动组复制增量恢复接收器/应用程序线程时出错"

ER_GRP_RPL_DONOR_CONN_TERMINATION
  eng "Terminating existing group replication donor connection and purging the corresponding logs."
  chinese "正在终止现有的组复制提供方连接并清除相应的日志。"

ER_GRP_RPL_STOPPING_GRP_REC
  eng "Error when stopping the group replication incremental recovery's donor connection"
  chinese "停止组复制增量恢复的原连接时出错"

ER_GRP_RPL_PURGE_REC
  eng "Error when purging the group replication recovery's relay logs"
  chinese "清除组复制恢复的中继日志时出错"

ER_GRP_RPL_UNABLE_TO_KILL_CONN_REC_DONOR_APPLIER
  eng "Unable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown."
  chinese "出现应用程序错误后,无法终止当前组复制恢复原连接。增量恢复将关闭。"

ER_GRP_RPL_UNABLE_TO_KILL_CONN_REC_DONOR_FAILOVER
  eng "Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown."
  chinese "无法在故障转移期间终止当前组复制恢复原连接。增量恢复将关闭。"

ER_GRP_RPL_FAILED_TO_NOTIFY_GRP_MEMBERSHIP_EVENT
  eng "Unexpected error when notifying an internal component named %s regarding a group membership event."
  chinese "通知名为%s的内部组件有关组成员身份事件时发生意外错误。"

ER_GRP_RPL_FAILED_TO_BROADCAST_GRP_MEMBERSHIP_NOTIFICATION
  eng "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!"
  chinese "广播内部组成员资格通知时发现未定义的错误！如果您的组件或插件未正确加载或出现故障,很可能会发生这种情况！"

ER_GRP_RPL_FAILED_TO_BROADCAST_MEMBER_STATUS_NOTIFICATION
  eng "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!"
  chinese "广播内部组成员状态通知时发现未定义的错误！如果您的组件或插件未正确加载或出现故障,很可能会发生这种情况！"

ER_GRP_RPL_OOM_FAILED_TO_GENERATE_IDENTIFICATION_HASH
  eng "No memory to generate write identification hash"
  chinese "没有内存来生成写入标识哈希"

ER_GRP_RPL_WRITE_IDENT_HASH_BASE64_ENCODING_FAILED
  eng "Base 64 encoding of the write identification hash failed"
  chinese "写入标识哈希的Base 64编码失败"

ER_GRP_RPL_INVALID_BINLOG_FORMAT
  eng "Binlog format should be ROW for Group Replication"
  chinese "组复制的Binlog格式应为行"

OBSOLETE_ER_GRP_RPL_BINLOG_CHECKSUM_SET
  eng "binlog_checksum should be NONE for Group Replication"
  chinese "对于组复制,binlog_check sum应为NONE"

OBSOLETE_ER_GRP_RPL_TRANS_WRITE_SET_EXTRACTION_NOT_SET
  eng "A transaction_write_set_extraction algorithm should be selected when running Group Replication"
  chinese "运行组复制时应选择TRANSACTION_WRITE_SET_EXTRACTION算法"

ER_GRP_RPL_UNSUPPORTED_TRANS_ISOLATION
  eng "Transaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group Replication"
  chinese "事务隔离级别(TX_ISOLATION)设置为与组复制不兼容的SERIALIZABLE"

ER_GRP_RPL_CANNOT_EXECUTE_TRANS_WHILE_STOPPING
  eng "Transaction cannot be executed while Group Replication is stopping."
  chinese "正在停止组复制时,无法执行事务。"

ER_GRP_RPL_CANNOT_EXECUTE_TRANS_WHILE_RECOVERING
  eng "Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE."
  chinese "组复制正在恢复时无法执行事务。请在服务器联机时重试。"

ER_GRP_RPL_CANNOT_EXECUTE_TRANS_IN_ERROR_STATE
  eng "Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the plugin"
  chinese "当组复制处于错误状态时,无法执行事务。请检查错误并重新启动插件"

ER_GRP_RPL_CANNOT_EXECUTE_TRANS_IN_OFFLINE_MODE
  eng "Transaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the plugin"
  chinese "组复制脱机时无法执行事务。请检查错误并重新启动插件"

ER_GRP_RPL_MULTIPLE_CACHE_TYPE_NOT_SUPPORTED_FOR_SESSION
  eng "We can only use one cache type at a time on session %u"
  chinese "我们一次只能在会话%u上使用一种缓存类型"

ER_GRP_RPL_FAILED_TO_REINIT_BINLOG_CACHE_FOR_READ
  eng "Failed to reinit binlog cache log for read on session %u"
  chinese "无法重新启动用于在会话%u上读取的binlog缓存日志"

ER_GRP_RPL_FAILED_TO_CREATE_TRANS_CONTEXT
  eng "Failed to create the context of the current transaction on session %u"
  chinese "无法在会话%u上创建当前事务的上下文"

ER_GRP_RPL_FAILED_TO_EXTRACT_TRANS_WRITE_SET
  eng "Failed to extract the set of items written during the execution of the current transaction on session %u"
  chinese "无法提取在会话%u上执行当前事务期间写入的项目集"

ER_GRP_RPL_FAILED_TO_GATHER_TRANS_WRITE_SET
  eng "Failed to gather the set of items written during the execution of the current transaction on session %u"
  chinese "无法收集在会话%u上执行当前事务期间写入的项目集"

ER_GRP_RPL_TRANS_SIZE_EXCEEDS_LIMIT
  eng "Error on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option."
  chinese "会话%u出错。大小为%llu的事务超出了指定的限制%lu。若要增加限制,请调整GROUP_REPLICATION_TRANSACTION_SIZE_LIMIT选项。"

OBSOLETE_ER_GRP_RPL_REINIT_OF_INTERNAL_CACHE_FOR_READ_FAILED
  eng "Error while re-initializing an internal cache, for read operations, on session %u"
  chinese "在会话%u上为读取操作重新初始化内部缓存时出错"

OBSOLETE_ER_GRP_RPL_APPENDING_DATA_TO_INTERNAL_CACHE_FAILED
  eng "Error while appending data to an internal cache on session %u"
  chinese "将数据追加到会话%u上的内部缓存时出错"

ER_GRP_RPL_WRITE_TO_TRANSACTION_MESSAGE_FAILED
  eng "Error while writing to transaction message on session %u"
  chinese "写入会话%u上的事务消息时出错"

ER_GRP_RPL_FAILED_TO_REGISTER_TRANS_OUTCOME_NOTIFICTION
  eng "Unable to register for getting notifications regarding the outcome of the transaction on session %u"
  chinese "无法注册以获取有关会话%u上的事务结果的通知"

ER_GRP_RPL_MSG_TOO_LONG_BROADCASTING_TRANS_FAILED
  eng "Error broadcasting transaction to the group on session %u. Message is too big."
  chinese "向会话%u上的组广播事务时出错。消息太大。"

ER_GRP_RPL_BROADCASTING_TRANS_TO_GRP_FAILED
  eng "Error while broadcasting the transaction to the group on session %u"
  chinese "将事务广播到会话%u上的组时出错"

ER_GRP_RPL_ERROR_WHILE_WAITING_FOR_CONFLICT_DETECTION
  eng "Error while waiting for conflict detection procedure to finish on session %u"
  chinese "等待会话%u上的冲突检测过程完成时出错"

OBSOLETE_ER_GRP_RPL_REINIT_OF_INTERNAL_CACHE_FOR_WRITE_FAILED
  eng "Error while re-initializing an internal cache, for write operations, on session %u"
  chinese "重新初始化会话%u上用于写入操作的内部缓存时出错"

OBSOLETE_ER_GRP_RPL_FAILED_TO_CREATE_COMMIT_CACHE
  eng "Failed to create group replication commit cache on session %u"
  chinese "无法在会话%u上创建组复制提交缓存"

OBSOLETE_ER_GRP_RPL_REINIT_OF_COMMIT_CACHE_FOR_WRITE_FAILED
  eng "Failed to reinit group replication commit cache for write on session %u"
  chinese "无法为会话%u上的写入重新插入组复制提交缓存"

OBSOLETE_ER_GRP_RPL_PREV_REC_SESSION_RUNNING
  eng "A previous recovery session is still running. Please stop the group replication plugin and wait for it to stop"
  chinese "上一个恢复会话仍在运行。请停止组复制插件并等待其停止"

ER_GRP_RPL_FATAL_REC_PROCESS
  eng "Fatal error during the incremental recovery process of Group Replication. The server will leave the group."
  chinese "组复制的增量恢复过程中出现致命错误。服务器将离开该组。"

OBSOLETE_ER_GRP_RPL_WHILE_STOPPING_REP_CHANNEL
  eng "Error stopping all replication channels while server was leaving the group. %s"
  chinese "服务器离开组时停止所有复制通道时出错。%s"

ER_GRP_RPL_UNABLE_TO_EVALUATE_APPLIER_STATUS
  eng "Unable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption."
  chinese "无法评估组复制应用程序执行状态。组复制恢复将关闭以避免数据损坏。"

ER_GRP_RPL_ONLY_ONE_SERVER_ALIVE
  eng "Only one server alive. Declaring this server as online within the replication group"
  chinese "只有一台服务器处于活动状态。正在声明此服务器在复制组中处于联机状态"

ER_GRP_RPL_CERTIFICATION_REC_PROCESS
  eng "Error when processing certification information in the incremental recovery process"
  chinese "在增量恢复过程中处理证书信息时出错"

ER_GRP_RPL_UNABLE_TO_ENSURE_EXECUTION_REC
  eng "Unable to ensure the execution of group transactions received during recovery."
  chinese "无法确保执行在恢复期间收到的组事务。"

ER_GRP_RPL_WHILE_SENDING_MSG_REC
  eng "Error while sending message in the group replication incremental recovery process."
  chinese "在组复制增量恢复过程中发送消息时出错。"

OBSOLETE_ER_GRP_RPL_READ_UNABLE_FOR_SUPER_READ_ONLY
  eng "Unable to read the server value for the super_read_only variable."
  chinese "无法读取SUPER_READ_ONLY变量的服务器值。"

ER_GRP_RPL_READ_UNABLE_FOR_READ_ONLY_SUPER_READ_ONLY
  eng "Unable to read the server values for the read_only and super_read_only variables."
  chinese "无法读取READ_ONLY和SUPER_READ_ONLY变量的服务器值。"

ER_GRP_RPL_UNABLE_TO_RESET_SERVER_READ_MODE
  eng "Unable to reset the server read mode settings. Try to reset them manually."
  chinese "无法重置服务器读取模式设置。请尝试手动重置。"

ER_GRP_RPL_UNABLE_TO_CERTIFY_PLUGIN_TRANS
  eng "Due to a plugin error, some transactions were unable to be certified and will now rollback."
  chinese "由于插件错误,某些交易无法通过认证,现在将回滚。"

ER_GRP_RPL_UNBLOCK_CERTIFIED_TRANS
  eng "Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the service"
  chinese "尝试取消阻止未认证或一致的事务时出错。重新启动服务时检查一致性错误"

OBSOLETE_ER_GRP_RPL_SERVER_WORKING_AS_SECONDARY
  eng "This server is working as secondary member with primary member address %s:%u."
  chinese "此服务器作为主要成员地址为%s:%u的辅助成员工作。"

ER_GRP_RPL_FAILED_TO_START_WITH_INVALID_SERVER_ID
  eng "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."
  chinese "无法启动组复制。复制应用程序基础结构未初始化,因为服务器是在server_id=0的情况下启动的。请使用大于0的server_id重新启动服务器。"

ER_GRP_RPL_FORCE_MEMBERS_MUST_BE_EMPTY
  eng "group_replication_force_members must be empty on group start. Current value: '%s'"
  chinese "GROUP_REPLICATION_FORCE_MEMBERS在组启动时必须为空。当前值:'%s'"

ER_GRP_RPL_PLUGIN_STRUCT_INIT_NOT_POSSIBLE_ON_SERVER_START
  eng "It was not possible to guarantee the initialization of plugin structures on server start"
  chinese "无法保证在服务器启动时初始化插件结构"

ER_GRP_RPL_FAILED_TO_ENABLE_SUPER_READ_ONLY_MODE
  eng "Could not enable the server read only mode and guarantee a safe recovery execution"
  chinese "无法启用服务器只读模式并保证安全恢复执行"

ER_GRP_RPL_FAILED_TO_INIT_COMMUNICATION_ENGINE
  eng "Error on group communication engine initialization"
  chinese "组通信引擎初始化出错"

ER_GRP_RPL_FAILED_TO_START_ON_SECONDARY_WITH_ASYNC_CHANNELS
  eng "Can't start group replication on secondary member with single-primary mode while asynchronous replication channels are running."
  chinese "当异步复制通道正在运行时,无法使用单主模式在辅助成员上启动组复制。"

ER_GRP_RPL_FAILED_TO_START_COMMUNICATION_ENGINE
  eng "Error on group communication engine start"
  chinese "组通信引擎启动时出错"

ER_GRP_RPL_TIMEOUT_ON_VIEW_AFTER_JOINING_GRP
  eng "Timeout on wait for view after joining group"
  chinese "加入组后等待查看超时"

ER_GRP_RPL_FAILED_TO_CALL_GRP_COMMUNICATION_INTERFACE
  eng "Error calling group communication interfaces"
  chinese "调用组通信接口时出错"

ER_GRP_RPL_MEMBER_SERVER_UUID_IS_INCOMPATIBLE_WITH_GRP
  eng "Member server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s."
  chinese "成员SERVER_UUID与组不兼容。SERVER_UUID%s与GROUP_REPLICATION_GROUP_NAME%s匹配。"

ER_GRP_RPL_MEMBER_CONF_INFO
  eng "Member configuration: member_id: %lu; member_uuid: \"%s\"; single-primary mode: \"%s\"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: \"%s\";"
  chinese "成员配置:MEMBER_ID:%lu；MEMBER_UUID:\"%s\"；单主模式:\"%s\"；GROUP_REPLICATION_AUTO_INCREMENT_INCREMENT:%lu；GROUP_REPLICATION_VIEW_CHANGE_UUID:\"%s\"；"

ER_GRP_RPL_FAILED_TO_CONFIRM_IF_SERVER_LEFT_GRP
  eng "Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information."
  chinese "无法确认服务器是否已离开该组。请检查PERFORMANCE_SCHEMA_REPLICATION_GROUP_MEMBERS以检查组成员身份信息。"

ER_GRP_RPL_SERVER_IS_ALREADY_LEAVING
  eng "Skipping leave operation: concurrent attempt to leave the group is on-going."
  chinese "跳过休假操作:正在同时尝试离开组。"

ER_GRP_RPL_SERVER_ALREADY_LEFT
  eng "Skipping leave operation: member already left the group."
  chinese "正在跳过休假操作:成员已离开群。"

ER_GRP_RPL_WAITING_FOR_VIEW_UPDATE
  eng "Going to wait for view modification"
  chinese "正在等待视图修改"

ER_GRP_RPL_TIMEOUT_RECEIVING_VIEW_CHANGE_ON_SHUTDOWN
  eng "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"
  chinese "由于停止、关闭或失败而离开组时,接收视图更改时超时。这可能会导致状态不一致。有关详细信息,请查看日志"

ER_GRP_RPL_REQUESTING_NON_MEMBER_SERVER_TO_LEAVE
  eng "Requesting to leave the group despite of not being a member"
  chinese "尽管不是成员,但仍要求离开该组织"

ER_GRP_RPL_IS_STOPPING
  eng "Plugin 'group_replication' is stopping."
  chinese "插件'GROUP_REPLICATION'正在停止。"

ER_GRP_RPL_IS_STOPPED
  eng "Plugin 'group_replication' has been stopped."
  chinese "插件'GROUP_REPLICATION'已停止。"

ER_GRP_RPL_FAILED_TO_ENABLE_READ_ONLY_MODE_ON_SHUTDOWN
  eng "On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed."
  chinese "插件关闭后,无法启用服务器只读模式。将接受并提交本地事务。"

ER_GRP_RPL_RECOVERY_MODULE_TERMINATION_TIMED_OUT_ON_SHUTDOWN
  eng "On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more details"
  chinese "关闭时,组复制恢复模块终止超时。有关详细信息,请查看日志"

ER_GRP_RPL_APPLIER_TERMINATION_TIMED_OUT_ON_SHUTDOWN
  eng "On shutdown there was a timeout on the Group Replication applier termination."
  chinese "关闭时,组复制应用程序终止超时。"

ER_GRP_RPL_FAILED_TO_SHUTDOWN_REGISTRY_MODULE
  eng "Unexpected failure while shutting down registry module!"
  chinese "关闭注册表模块时出现意外故障！"

ER_GRP_RPL_FAILED_TO_INIT_HANDLER
  eng "Failure during Group Replication handler initialization"
  chinese "组复制处理程序初始化期间失败"

ER_GRP_RPL_FAILED_TO_REGISTER_SERVER_STATE_OBSERVER
  eng "Failure when registering the server state observers"
  chinese "注册服务器状态观察器时失败"

ER_GRP_RPL_FAILED_TO_REGISTER_TRANS_STATE_OBSERVER
  eng "Failure when registering the transactions state observers"
  chinese "注册事务状态观察器时失败"

ER_GRP_RPL_FAILED_TO_REGISTER_BINLOG_STATE_OBSERVER
  eng "Failure when registering the binlog state observers"
  chinese "注册binlog状态观察器时失败"

ER_GRP_RPL_FAILED_TO_START_ON_BOOT
  eng "Unable to start Group Replication on boot"
  chinese "无法在引导时启动组复制"

ER_GRP_RPL_FAILED_TO_STOP_ON_PLUGIN_UNINSTALL
  eng "Failure when stopping Group Replication on plugin uninstall"
  chinese "卸载插件时停止组复制时失败"

ER_GRP_RPL_FAILED_TO_UNREGISTER_SERVER_STATE_OBSERVER
  eng "Failure when unregistering the server state observers"
  chinese "注销服务器状态观察器时失败"

ER_GRP_RPL_FAILED_TO_UNREGISTER_TRANS_STATE_OBSERVER
  eng "Failure when unregistering the transactions state observers"
  chinese "取消注册事务状态观察器时失败"

ER_GRP_RPL_FAILED_TO_UNREGISTER_BINLOG_STATE_OBSERVER
  eng "Failure when unregistering the binlog state observers"
  chinese "注销binlog状态观察器时失败"

ER_GRP_RPL_ALL_OBSERVERS_UNREGISTERED
  eng "All Group Replication server observers have been successfully unregistered"
  chinese "已成功注销所有组复制服务器观察者"

ER_GRP_RPL_FAILED_TO_PARSE_THE_GRP_NAME
  eng "Unable to parse the group_replication_group_name."
  chinese "无法分析GROUP_REPLICATION_GROUP_NAME。"

ER_GRP_RPL_FAILED_TO_GENERATE_SIDNO_FOR_GRP
  eng "Unable to parse the group_replication_group_name."
  chinese "无法分析GROUP_REPLICATION_GROUP_NAME。"

ER_GRP_RPL_APPLIER_NOT_STARTED_DUE_TO_RUNNING_PREV_SHUTDOWN
  eng "Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete."
  chinese "无法启动组复制应用程序,因为上一次关闭仍在运行:线程将在其任务完成后停止。"

ER_GRP_RPL_FAILED_TO_INIT_APPLIER_MODULE
  eng "Unable to initialize the Group Replication applier module."
  chinese "无法初始化组复制应用程序模块。"

ER_GRP_RPL_APPLIER_INITIALIZED
  eng "Group Replication applier module successfully initialized!"
  chinese "组复制应用程序模块已成功初始化！"

ER_GRP_RPL_COMMUNICATION_SSL_CONF_INFO
  eng "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\""
  chinese "组通信SSL配置:GROUP_REPLICATION_SSLLMODE:\"%s\"；SERVER_KEY_FILE:\"%s\"；SERVER_CERT_FILE:\"%s\"；CLIENT_KEY_FILE:\"%s\"；CLIENT_CERT_FILE:\"%s\"；ca_FILE:\"%s\"；CA_PATH:\"%s\"；密码:\"%s\"；TLS_VERSION:\"%s\"；TLS_CIPHER套件:\"%s\"；CRL_FILE:\"%s\"；CRL_PATH:\"%s\"；SSL_FIPS_MODE:\"%s\""

ER_GRP_RPL_ABORTS_AS_SSL_NOT_SUPPORTED_BY_MYSQLD
  eng "MySQL server does not have SSL support and group_replication_ssl_mode is \"%s\", START GROUP_REPLICATION will abort"
  chinese "MySQL服务器不支持SSL,并且GROUP_REPLICATION_SSL_MODE为\"%s\",则START GROUP_REPLICATION将中止"

ER_GRP_RPL_SSL_DISABLED
  eng "Group communication SSL configuration: group_replication_ssl_mode: \"%s\""
  chinese "组通信SSL配置:GROUP_REPLICATION_SSL_MODE:\"%s\""

ER_GRP_RPL_UNABLE_TO_INIT_COMMUNICATION_ENGINE
  eng "Unable to initialize the group communication engine"
  chinese "无法初始化组通信引擎"

ER_GRP_RPL_BINLOG_DISABLED
  eng "Binlog must be enabled for Group Replication"
  chinese "必须为组复制启用Binlog"

ER_GRP_RPL_GTID_MODE_OFF
  eng "Gtid mode should be ON for Group Replication"
  chinese "组复制的GTID模式应为打开"

ER_GRP_RPL_LOG_REPLICA_UPDATES_NOT_SET
  eng "LOG_REPLICA_UPDATES should be ON for Group Replication"
  chinese "组复制应打开LOG_REPLICATE_UPDATES"

OBSOLETE_ER_GRP_RPL_INVALID_TRANS_WRITE_SET_EXTRACTION_VALUE
  eng "Extraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm."
  chinese "提取事务写入集需要哈希算法配置。请仔细检查参数Transaction-WRITE-SET-EXTRACTION是否设置为有效算法。"

ER_GRP_RPL_APPLIER_METADATA_REPO_MUST_BE_TABLE
  eng "Applier metadata repository must be set to TABLE"
  chinese "必须将中继日志信息库设置为表"

ER_GRP_RPL_CONNECTION_METADATA_REPO_MUST_BE_TABLE
  eng "Connection metadata repository must be set to TABLE."
  chinese "必须将主信息存储库设置为表。"

ER_GRP_RPL_INCORRECT_TYPE_SET_FOR_PARALLEL_APPLIER
  eng "In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'."
  chinese "要在组复制上使用并行应用程序,参数REPLICATE-PARALLEL-TYPE必须设置为'LOGICAL_CLOCK'。"

ER_GRP_RPL_REPLICA_PRESERVE_COMMIT_ORDER_NOT_SET
  eng "Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads."
  chinese "使用1个以上的应用程序线程时,组复制要求将副本-保留-提交-顺序设置为开。"

ER_GRP_RPL_SINGLE_PRIM_MODE_NOT_ALLOWED_WITH_UPDATE_EVERYWHERE
  eng "It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled."
  chinese "不允许在启用'group_replication_enforce_update_everywhere_checks'的情况下运行单一主模式。"

ER_GRP_RPL_MODULE_TERMINATE_ERROR
  eng "error_message: %s"
  chinese "错误消息:%s"

ER_GRP_RPL_GRP_NAME_OPTION_MANDATORY
  eng "The group_replication_group_name option is mandatory"
  chinese "GROUP_REPLICATION_GROUP_NAME选项是必需的"

ER_GRP_RPL_GRP_NAME_IS_TOO_LONG
  eng "The group_replication_group_name '%s' is not a valid UUID, its length is too big"
  chinese "GROUP_REPLICATION_GROUP_NAME'%s'不是有效的UUID,其长度太大"

ER_GRP_RPL_GRP_NAME_IS_NOT_VALID_UUID
  eng "The group_replication_group_name '%s' is not a valid UUID"
  chinese "GROUP_REPLICATION_GROUP_NAME'%s'不是有效的UUID"

ER_GRP_RPL_FLOW_CTRL_MIN_QUOTA_GREATER_THAN_MAX_QUOTA
  eng "group_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quota"
  chinese "GROUP_REPLICATION_FLOW_CONTROL_MIN_QUOTA不能大于GROUP_REPLICATION_FLOW_CONTROL_MAX_QUOTA"

ER_GRP_RPL_FLOW_CTRL_MIN_RECOVERY_QUOTA_GREATER_THAN_MAX_QUOTA
  eng "group_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quota"
  chinese "group_replication_flow_control_min_recovery_quota不能大于GROUP_REPLICATION_FLOW_CONTROL_MAX_QUOTA"

ER_GRP_RPL_FLOW_CTRL_MAX_QUOTA_SMALLER_THAN_MIN_QUOTAS
  eng "group_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quota"
  chinese "GROUP_REPLICATION_FLOW_CONTROL_MAX_QUOTA不能小于GROUP_REPLICATION_FLOW_CONTROL_MIN_QUOTA或group_replication_flow_control_min_recovery_quota"

ER_GRP_RPL_INVALID_SSL_RECOVERY_STRING
  eng "The given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limit"
  chinese "为恢复SSL选项'GROUP_REPLICATION_%s'指定的值无效,因为其长度超出限制"

OBSOLETE_ER_GRP_RPL_SUPPORTS_ONLY_ONE_FORCE_MEMBERS_SET
  eng "There is one group_replication_force_members operation already ongoing"
  chinese "已有一个GROUP_REPLICATION_FORCE_MEMBERS操作正在进行"

OBSOLETE_ER_GRP_RPL_FORCE_MEMBERS_SET_UPDATE_NOT_ALLOWED
  eng "group_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachable"
  chinese "GROUP_REPLICATION_FORCE_MEMBERS只能在组复制正在运行且大多数成员无法访问时更新"

ER_GRP_RPL_GRP_COMMUNICATION_INIT_WITH_CONF
  eng "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'"
  chinese "已使用以下配置初始化组通信: 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'"

ER_GRP_RPL_UNKNOWN_GRP_RPL_APPLIER_PIPELINE_REQUESTED
  eng "Unknown group replication applier pipeline requested"
  chinese "请求的未知组复制应用程序管道"

ER_GRP_RPL_FAILED_TO_BOOTSTRAP_EVENT_HANDLING_INFRASTRUCTURE
  eng "Unable to bootstrap group replication event handling infrastructure. Unknown handler type: %d"
  chinese "无法引导组复制事件处理基础结构。未知的处理程序类型:%d"

ER_GRP_RPL_APPLIER_HANDLER_NOT_INITIALIZED
  eng "One of the group replication applier handlers is null due to an initialization error"
  chinese "由于初始化错误,其中一个组复制应用程序处理程序为空"

ER_GRP_RPL_APPLIER_HANDLER_IS_IN_USE
  eng "A group replication applier handler, marked as unique, is already in use."
  chinese "标记为唯一的组复制应用程序处理程序已在使用。"

ER_GRP_RPL_APPLIER_HANDLER_ROLE_IS_IN_USE
  eng "A group replication applier handler role, that was marked as unique, is already in use."
  chinese "标记为唯一的组复制应用程序处理者角色已在使用中。"

ER_GRP_RPL_FAILED_TO_INIT_APPLIER_HANDLER
  eng "Error on group replication applier handler initialization"
  chinese "组复制应用程序处理程序初始化出错"

ER_GRP_RPL_SQL_SERVICE_FAILED_TO_INIT_SESSION_THREAD
  eng "Error when initializing a session thread for internal server connection."
  chinese "初始化用于内部服务器连接的会话线程时出错。"

ER_GRP_RPL_SQL_SERVICE_COMM_SESSION_NOT_INITIALIZED
  eng "Error running internal SQL query: %s. The internal server communication session is not initialized"
  chinese "运行内部SQL查询时出错:%s。内部服务器通信会话未初始化"

ER_GRP_RPL_SQL_SERVICE_SERVER_SESSION_KILLED
  eng "Error running internal SQL query: %s. The internal server session was killed or server is shutting down."
  chinese "运行内部SQL查询时出错:%s。内部服务器会话已终止或服务器正在关闭。"

ER_GRP_RPL_SQL_SERVICE_FAILED_TO_RUN_SQL_QUERY
  eng "Error running internal SQL query: %s. Got internal SQL error: %s(%d)"
  chinese "运行内部SQL查询时出错:%s。获取内部SQL错误:%s(%d)"

ER_GRP_RPL_SQL_SERVICE_SERVER_INTERNAL_FAILURE
  eng "Error running internal SQL query: %s. Internal failure."
  chinese "运行内部SQL查询时出错:%s。内部故障。"

ER_GRP_RPL_SQL_SERVICE_RETRIES_EXCEEDED_ON_SESSION_STATE
  eng "Error, maximum number of retries exceeded when waiting for the internal server session state to be operating"
  chinese "错误,等待内部服务器会话状态运行时超过最大重试次数"

ER_GRP_RPL_SQL_SERVICE_FAILED_TO_FETCH_SECURITY_CTX
  eng "Error when trying to fetch security context when contacting the server for internal plugin requests."
  chinese "联系服务器以获取内部插件请求时,尝试获取安全上下文时出错。"

ER_GRP_RPL_SQL_SERVICE_SERVER_ACCESS_DENIED_FOR_USER
  eng "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."
  chinese "尝试使用用户%s访问服务器时出错。请确保该用户存在于服务器中,并且MySQL升级过程运行正确。"

ER_GRP_RPL_SQL_SERVICE_MAX_CONN_ERROR_FROM_SERVER
  eng "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."

ER_GRP_RPL_SQL_SERVICE_SERVER_ERROR_ON_CONN
  eng "Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %s"

ER_GRP_RPL_UNREACHABLE_MAJORITY_TIMEOUT_FOR_MEMBER
  eng "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."
  chinese "此成员在超过%ld秒内无法联系到大多数成员。该成员现在将按照group_replication_unreachable_majority_timeout选项的指示离开该组。"

ER_GRP_RPL_SERVER_SET_TO_READ_ONLY_DUE_TO_ERRORS
  eng "The server was automatically set into read only mode after an error was detected."
  chinese "检测到错误后,服务器自动设置为只读模式。"

ER_GRP_RPL_GMS_LISTENER_FAILED_TO_LOG_NOTIFICATION
  eng "Unable to log notification to table (errno: %lu) (res: %d)! Message: %s"
  chinese "无法将通知记录到表(错误号:%lu)(资源:%d)！消息:%s"

ER_GRP_RPL_GRP_COMMUNICATION_ENG_INIT_FAILED
  eng "Failure in group communication engine '%s' initialization"
  chinese "组通信引擎'%s'初始化失败"

ER_GRP_RPL_SET_GRP_COMMUNICATION_ENG_LOGGER_FAILED
  eng "Unable to set the group communication engine logger"
  chinese "无法设置组通信引擎记录器"

ER_GRP_RPL_DEBUG_OPTIONS
  eng "Current debug options are: '%s'."
  chinese "当前调试选项为:'%s'。"

ER_GRP_RPL_INVALID_DEBUG_OPTIONS
  eng "Some debug options in '%s' are not valid."
  chinese "'%s'中的某些调试选项无效。"

ER_GRP_RPL_EXIT_GRP_GCS_ERROR
  eng "Error calling group communication interfaces while trying to leave the group"
  chinese "尝试离开组时调用组通信接口时出错"

ER_GRP_RPL_GRP_MEMBER_OFFLINE
  eng "Member is not ONLINE, it is not possible to force a new group membership"
  chinese "成员未联机,无法强制新的组成员身份"

ER_GRP_RPL_GCS_INTERFACE_ERROR
  eng "Error calling group communication interfaces"
  chinese "调用组通信接口时出错"

ER_GRP_RPL_FORCE_MEMBER_VALUE_SET_ERROR
  eng "Error setting group_replication_force_members value '%s' on group communication interfaces"
  chinese "在组通信接口上设置GROUP_REPLICATION_FORCE_MEMBERS值'%s'时出错"

ER_GRP_RPL_FORCE_MEMBER_VALUE_SET
  eng "The group_replication_force_members value '%s' was set in the group communication interfaces"
  chinese "在组通信接口中设置了GROUP_REPLICATION_FORCE_MEMBERS值'%s'"

ER_GRP_RPL_FORCE_MEMBER_VALUE_TIME_OUT
  eng "Timeout on wait for view after setting group_replication_force_members value '%s' into group communication interfaces"
  chinese "将GROUP_REPLICATION_FORCE_MEMBERS值'%s'设置到组通信接口后,等待查看超时"

ER_GRP_RPL_BROADCAST_COMMIT_MSSG_TOO_BIG
  eng "Broadcast of committed transactions message failed. Message is too big."
  chinese "广播提交的事务消息失败。消息太大。"

ER_GRP_RPL_SEND_STATS_ERROR
  eng "Error while sending stats message"
  chinese "发送统计信息时出错"

ER_GRP_RPL_MEMBER_STATS_INFO
  eng "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"
  chinese "流控制 - 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"

ER_GRP_RPL_FLOW_CONTROL_STATS
  eng "Flow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lld"
  chinese "流控制:限制到每%ld秒%ld个提交,%d个写入和%d个非恢复成员,最小容量%lld,限制%lld"

ER_GRP_RPL_UNABLE_TO_CONVERT_PACKET_TO_EVENT
  eng "Unable to convert a packet into an event on the applier. Error: %s"
  chinese "无法将数据包转换为应用程序上的事件。错误:%s"

ER_GRP_RPL_PIPELINE_CREATE_FAILED
  eng "Failed to create group replication pipeline cache."
  chinese "无法创建组复制管道缓存。"

ER_GRP_RPL_PIPELINE_REINIT_FAILED_WRITE
  eng "Failed to reinit group replication pipeline cache for write."
  chinese "无法重新插入组复制管道缓存以进行写入。"

ER_GRP_RPL_UNABLE_TO_CONVERT_EVENT_TO_PACKET
  eng "Unable to convert the event into a packet on the applier. Error: %s"
  chinese "无法将事件转换为应用程序上的包。错误:%s"

ER_GRP_RPL_PIPELINE_FLUSH_FAIL
  eng "Failed to flush group replication pipeline cache."
  chinese "无法刷新组复制管道缓存。"

ER_GRP_RPL_PIPELINE_REINIT_FAILED_READ
  eng "Failed to reinit group replication pipeline cache for read."
  chinese "无法重新插入组复制管道缓存以进行读取。"

OBSOLETE_ER_GRP_RPL_STOP_REP_CHANNEL
  eng "Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details."
  chinese "服务器离开组时停止所有复制通道时出错。获得错误:%d。有关详细信息,请查看错误日志。"

ER_GRP_RPL_GCS_GR_ERROR_MSG
  eng "%s"
  chinese "%s"

ER_GRP_RPL_REPLICA_IO_THREAD_UNBLOCKED
  eng "The replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now."
  chinese "通道'%s'的从属IO线程已解除阻止,因为该成员现在已声明为联机。"

ER_GRP_RPL_REPLICA_IO_THREAD_ERROR_OUT
  eng "The replica IO thread of channel '%s' will error out as the member failed to come ONLINE."
  chinese "由于成员无法联机,通道'%s'的从属IO线程将出错。"

ER_GRP_RPL_REPLICA_APPLIER_THREAD_UNBLOCKED
  eng "The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now."
  chinese "通道'%s'的从属应用程序线程已被解锁,因为该成员现在已声明为联机。"

ER_GRP_RPL_REPLICA_APPLIER_THREAD_ERROR_OUT
  eng "The replica applier thread of channel '%s' will error out as the member failed to come ONLINE."
  chinese "由于成员无法联机,通道'%s'的从属应用程序线程将出错。"

ER_LDAP_AUTH_FAILED_TO_CREATE_OR_GET_CONNECTION
  eng "LDAP authentication initialize: failed to create/ get connection from the pool. "
  chinese "ldap身份验证初始化:无法从池创建/获取连接。"

ER_LDAP_AUTH_DEINIT_FAILED
  eng "LDAP authentication de_initialize Failed"
  chinese "ldap身份验证初始化失败"

ER_LDAP_AUTH_SKIPPING_USER_GROUP_SEARCH
  eng "Skipping group search, No group attribute mentioned"
  chinese "跳过组搜索,未提及组属性"

ER_LDAP_AUTH_POOL_DISABLE_MAX_SIZE_ZERO
  eng "Pool max size is 0, connection pool is disabled"
  chinese "池最大大小为0,连接池已禁用"

ER_LDAP_AUTH_FAILED_TO_CREATE_LDAP_OBJECT_CREATOR
  eng "Connection pool initialization, failed to create LDAP object creator"
  chinese "连接池初始化,无法创建ldap对象创建者"

ER_LDAP_AUTH_FAILED_TO_CREATE_LDAP_OBJECT
  eng "Connection pool initialization, failed to create LDAP object"
  chinese "连接池初始化,无法创建LDAP对象"

ER_LDAP_AUTH_TLS_CONF
  eng "LDAP TLS configuration"
  chinese "ldap TLS配置"

ER_LDAP_AUTH_TLS_CONNECTION
  eng "LDAP TLS connection"
  chinese "LDAPTLS连接"

ER_LDAP_AUTH_CONN_POOL_NOT_CREATED
  eng "LDAP pool is not created."
  chinese "未创建LDAP池。"

ER_LDAP_AUTH_CONN_POOL_INITIALIZING
  eng "LDAP pool is initializing"
  chinese "正在初始化LDAP池"

ER_LDAP_AUTH_CONN_POOL_DEINITIALIZING
  eng "LDAP pool is de-initializing"
  chinese "正在取消初始化LDAP池"

ER_LDAP_AUTH_ZERO_MAX_POOL_SIZE_UNCHANGED
  eng "Pool max size old and new values are 0"
  chinese "池最大大小旧值和新值均为0"

ER_LDAP_AUTH_POOL_REINITIALIZING
  eng "LDAP pool is re-initializing"
  chinese "正在重新初始化LDAP池"

ER_LDAP_AUTH_FAILED_TO_WRITE_PACKET
  eng "Plug-in has failed to write the packet."
  chinese "插件无法写入数据包。"

ER_LDAP_AUTH_SETTING_USERNAME
  eng "Setting LDAP user name as : %s"
  chinese "将ldap用户名设置为:%s"

ER_LDAP_AUTH_USER_AUTH_DATA
  eng "User authentication data: %s size: %lu"
  chinese "用户身份验证数据:%s大小:%lu"

OBSOLETE_ER_LDAP_AUTH_INFO_FOR_USER
  eng "User is authenticated as: %s external user: %s"
  chinese "用户身份验证为:%s外部用户:%s"

ER_LDAP_AUTH_USER_GROUP_SEARCH_INFO
  eng "Group search information base DN: %s scope: %d filter: %s attribute: %s"
  chinese "组搜索信息库DN:%s作用域:%d筛选器:%s属性:%s"

ER_LDAP_AUTH_GRP_SEARCH_SPECIAL_HDL
  eng "Special handling for group search, {GA} found"
  chinese "组搜索的特殊处理,找到{GA}"

ER_LDAP_AUTH_GRP_IS_FULL_DN
  eng "Group search special handling, group full DN found. "
  chinese "组搜索特殊处理,找到组完全目录号码。"

ER_LDAP_AUTH_USER_NOT_FOUND_IN_ANY_GRP
  eng "User %s is not member of any group."
  chinese "用户%s不是任何组的成员。"

ER_LDAP_AUTH_USER_FOUND_IN_MANY_GRPS
  eng "User %s is member of more than one group"
  chinese "用户%s是多个组的成员"

ER_LDAP_AUTH_USER_HAS_MULTIPLE_GRP_NAMES
  eng "For user %s has multiple user group names. Please check if group attribute name is correct"
  chinese "用户%s有多个用户组名。请检查组属性名称是否正确"

ER_LDAP_AUTH_SEARCHED_USER_GRP_NAME
  eng "Searched group name: %s"
  chinese "搜索的组名:%s"

ER_LDAP_AUTH_OBJECT_CREATE_TIMESTAMP
  eng "LDAP authentication object creation time_stamp: %s dn: %s"
  chinese "ldap身份验证对象创建时间戳:%s DN:%s"

ER_LDAP_AUTH_CERTIFICATE_NAME
  eng "Certificate name: %s"
  chinese "证书名称:%s"

ER_LDAP_AUTH_FAILED_TO_POOL_DEINIT
  eng "Failed to pool de-initialized: pool is already reconstructing"
  chinese "池取消初始化失败:池已在重建"

ER_LDAP_AUTH_FAILED_TO_INITIALIZE_POOL_IN_RECONSTRUCTING
  eng "Pool initialization failed: pool is already initialized"
  chinese "池初始化失败:池已初始化"

ER_LDAP_AUTH_FAILED_TO_INITIALIZE_POOL_IN_INIT_STATE
  eng "Pool initialization failed: pool is initializing"
  chinese "池初始化失败:池正在初始化"

ER_LDAP_AUTH_FAILED_TO_INITIALIZE_POOL_IN_DEINIT_STATE
  eng "Pool initialization failed: pool is de-initializing"
  chinese "池初始化失败:池正在取消初始化"

ER_LDAP_AUTH_FAILED_TO_DEINITIALIZE_POOL_IN_RECONSTRUCT_STATE
  eng "Failed to pool deinitialized: pool is already reconstructing"
  chinese "池取消初始化失败:池已在重建"

ER_LDAP_AUTH_FAILED_TO_DEINITIALIZE_NOT_READY_POOL
  eng "Failed to pool deinitialized : pool is not ready"
  chinese "池取消初始化失败:池未就绪"

ER_LDAP_AUTH_FAILED_TO_GET_CONNECTION_AS_PLUGIN_NOT_READY
  eng "Ldap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializing"
  chinese "ldap_CONNECTION_POOL::GET:由于插件未就绪,无法返回连接/正在初始化/正在取消初始化"

ER_LDAP_AUTH_CONNECTION_POOL_INIT_FAILED
  eng "Connection pool has failed to initialized"
  chinese "连接池初始化失败"

ER_LDAP_AUTH_MAX_ALLOWED_CONNECTION_LIMIT_HIT
  eng "Ldap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit."
  chinese "ldap_connetion_pool::获取已达到允许的最大连接大小。请增加最大限制。"

ER_LDAP_AUTH_MAX_POOL_SIZE_SET_FAILED
  eng "Set max pool size failed."
  chinese "设置最大池大小失败。"

ER_LDAP_AUTH_PLUGIN_FAILED_TO_READ_PACKET
  eng "Plug-in has failed to read the packet from client"
  chinese "插件无法从客户端读取数据包"

ER_LDAP_AUTH_CREATING_LDAP_CONNECTION
  eng "Ldap_authentication::initialize: creating new LDAP connection. "
  chinese "LDAP_AUTHENTICATION::INITIALIZE:正在创建新的LDAP连接。"

ER_LDAP_AUTH_GETTING_CONNECTION_FROM_POOL
  eng "Ldap_authentication::initialize: getting connection from pool. "
  chinese "ldap_AUTHENTICATION::INITIALIZE:从池获取连接。"

ER_LDAP_AUTH_RETURNING_CONNECTION_TO_POOL
  eng "Ldap_authentication::de_initialize putting back connection in the pool"
  chinese "ldap_AUTHENTICATION::DE_INITIALIZE正在池中恢复连接"

ER_LDAP_AUTH_SEARCH_USER_GROUP_ATTR_NOT_FOUND
  eng "Ldap_authentication::search_user_group no group attribute found"
  chinese "ldap_身份验证::Search_User_GROUP未找到组属性"

ER_LDAP_AUTH_LDAP_INFO_NULL
  eng "Ldap_connetion_pool::put ldap info null"
  chinese "ldap_connetion_pool::PUT ldap信息为空"

ER_LDAP_AUTH_FREEING_CONNECTION
  eng "Ldap_connection_pool::put connection is freeing. "
  chinese "ldap_CONNECTION_POOL::PUT连接正在释放。"

ER_LDAP_AUTH_CONNECTION_PUSHED_TO_POOL
  eng "Ldap_connection_pool::put connection in pushed in the pool"
  chinese "ldap_CONNECTION_POOL::将连接放入池中"

ER_LDAP_AUTH_CONNECTION_CREATOR_ENTER
  eng "Ldap_connection_creator::Ldap_connection_creator"
  chinese "Ldap_connection_creator::Ldap_connection_creator"

ER_LDAP_AUTH_STARTING_TLS
  eng "starting TLS"
  chinese "启动TLS"

ER_LDAP_AUTH_CONNECTION_GET_LDAP_INFO_NULL
  eng "Ldap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)"
  chinese "ldap_CONNECTION_POOL::GET:(ldap_info==NULL)||(*ldap_info)"

ER_LDAP_AUTH_DELETING_CONNECTION_KEY
  eng "Ldap_connection_pool::deinit: deleting connection key %s"
  chinese "ldap_CONNECTION_POOL::deinit:删除连接密钥%s"

ER_LDAP_AUTH_POOLED_CONNECTION_KEY
  eng " Ldap_connection_pool::get pooled connection key: %s"
  chinese "ldap_CONNECTION_POOL::获取池连接密钥:%s"

ER_LDAP_AUTH_CREATE_CONNECTION_KEY
  eng "Ldap_connection_pool::get create connection key: %s"
  chinese "ldap_CONNECTION_POOL::获取创建连接密钥:%s"

ER_LDAP_AUTH_COMMUNICATION_HOST_INFO
  eng "LDAP communication host %s port %u"
  chinese "ldap通信主机%s端口%u"

ER_LDAP_AUTH_METHOD_TO_CLIENT
  eng "Sending authentication method to client : %s"
  chinese "将身份验证方法发送到客户端:%s"

ER_LDAP_AUTH_SASL_REQUEST_FROM_CLIENT
  eng "SASL request received from mysql client: %s"
  chinese "从MySQL客户端收到SASL请求:%s"

ER_LDAP_AUTH_SASL_PROCESS_SASL
  eng "Ldap_sasl_authentication::process_sasl rc: %s"
  chinese "ldap_sasl_身份验证::process_sasl返回代码:%s"

ER_LDAP_AUTH_SASL_BIND_SUCCESS_INFO
  eng "Ldap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %s"
  chinese "ldap_sasl_身份验证::process_sasl sasl绑定成功。DN:%s方法:%s服务器凭据:%s"

ER_LDAP_AUTH_STARTED_FOR_USER
  eng "LDAP authentication started for user name: %s"
  chinese "已为用户名%s启动了LDAP身份验证"

ER_LDAP_AUTH_DISTINGUISHED_NAME
  eng "%s"
  chinese "%s"

ER_LDAP_AUTH_INIT_FAILED
  eng "LDAP authentication initialize is failed with: %s"
  chinese "ldap身份验证初始化失败,错误为:%s"

ER_LDAP_AUTH_OR_GROUP_RETRIEVAL_FAILED
  eng "LDAP authentication failed or group retrieval failed: %s"
  chinese "ldap身份验证失败或组检索失败:%s"

ER_LDAP_AUTH_USER_GROUP_SEARCH_FAILED
  eng "Search user group has failed: %s"
  chinese "搜索用户组失败:%s"

ER_LDAP_AUTH_USER_BIND_FAILED
  eng "LDAP user bind has failed: %s"
  chinese "ldap用户绑定失败:%s"

ER_LDAP_AUTH_POOL_GET_FAILED_TO_CREATE_CONNECTION
  eng "Connection pool get: Failed to create LDAP connection. %s"
  chinese "连接池获取:无法创建LDAP连接。%s"

ER_LDAP_AUTH_FAILED_TO_CREATE_LDAP_CONNECTION
  eng "Failed to create new LDAP connection:  %s"
  chinese "无法创建新的ldap连接:%s"

ER_LDAP_AUTH_FAILED_TO_ESTABLISH_TLS_CONNECTION
  eng "Failed to establish TLS connection:  %s"
  chinese "无法建立TLS连接:%s"

ER_LDAP_AUTH_FAILED_TO_SEARCH_DN
  eng "Failed to search user full dn: %s"
  chinese "无法搜索用户完整的DN:%s"

ER_LDAP_AUTH_CONNECTION_POOL_REINIT_ENTER
  eng "Ldap_connection_pool::reinit"
  chinese "Ldap_connection_pool::reinit"

ER_SYSTEMD_NOTIFY_PATH_TOO_LONG
  eng "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."
  chinese "NOTIFY_SOCKET环境变量中的路径'%s'太长。在%u字节,它超出了AF_UNIX套接字的%u字节限制。"

ER_SYSTEMD_NOTIFY_CONNECT_FAILED
  eng "Failed to connect to systemd notification socket named %s. Error: '%s'"
  chinese "无法连接到名为%s的SYSTEM通知套接字。错误:'%s'"

ER_SYSTEMD_NOTIFY_WRITE_FAILED
  eng "Failed to write '%s' to systemd notification. Error: '%s'"
  chinese "无法将'%s'写入系统通知。错误:'%s'"

ER_FOUND_MISSING_GTIDS
  eng "Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s."
  chinese "无法复制到SERVER_UUID='%.36s'的服务器,因为当前服务器已清除了所需的二进制日志。连接的服务器需要从其他位置复制丢失的事务,或者替换为从较新的备份创建的新服务器。若要防止将来出现此错误,请考虑延长当前服务器上的二进制日志过期时间。%s"

ER_PID_FILE_PRIV_DIRECTORY_INSECURE
  eng "Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory."
  chinese "--id-file的不安全配置:所有OS用户都可以访问路径中的位置'%s'。请考虑选择其他目录。"

ER_CANT_CHECK_PID_PATH
  eng "Can't start server: can't check PID filepath: %s"
  chinese "无法启动服务器:无法检查PID文件路径:%s"

ER_VALIDATE_PWD_STATUS_VAR_REGISTRATION_FAILED
  eng "validate_password status variables registration failed."
  chinese "VALIDATE_PASSWORD状态变量注册失败。"

ER_VALIDATE_PWD_STATUS_VAR_UNREGISTRATION_FAILED
  eng "validate_password status variables unregistration failed."
  chinese "VALIDATE_PASSWORD状态变量取消注册失败。"

ER_VALIDATE_PWD_DICT_FILE_OPEN_FAILED
  eng "Dictionary file open failed"
  chinese "打开词典文件失败"

ER_VALIDATE_PWD_COULD_BE_NULL
  eng "given password string could be null"
  chinese "给定的密码字符串可能为空"

ER_VALIDATE_PWD_STRING_CONV_TO_LOWERCASE_FAILED
  eng "failed to convert the password string to lower case"
  chinese "无法将密码字符串转换为小写"

ER_VALIDATE_PWD_STRING_CONV_TO_BUFFER_FAILED
  eng "failed to convert the password string into a buffer"
  chinese "无法将密码字符串转换为缓冲区"

ER_VALIDATE_PWD_STRING_HANDLER_MEM_ALLOCATION_FAILED
  eng "memory allocation failed for string handler"
  chinese "字符串处理程序的内存分配失败"

ER_VALIDATE_PWD_STRONG_POLICY_DICT_FILE_UNSPECIFIED
  eng "Since the validate_password_policy is mentioned as Strong, dictionary file must be specified"
  chinese "由于VALIDATE_PASSWORD_POLICY被提及为强,因此必须指定字典文件"

ER_VALIDATE_PWD_CONVERT_TO_BUFFER_FAILED
  eng "convert_to_buffer service failed"
  chinese "Convert_to_Buffer服务失败"

ER_VALIDATE_PWD_VARIABLE_REGISTRATION_FAILED
  eng "%s variable registration failed."
  chinese "%s变量注册失败。"

ER_VALIDATE_PWD_VARIABLE_UNREGISTRATION_FAILED
  eng "%s variable unregistration failed."
  chinese "%s变量注销失败。"

ER_KEYRING_MIGRATION_EXTRA_OPTIONS
  eng "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."
  chinese "请指定特定于密钥环迁移的选项。任何其他选项都可以忽略。注意:虽然某些选项有效,但迁移工具仍可以报告错误示例:插件变量尚未加载。"

OBSOLETE_ER_INVALID_DEFAULT_UTF8MB4_COLLATION
  eng "Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected"
  chinese "无效的默认排序规则%s:需要utf8mb4_0900_ai_ci或utf8mb4_General_ci"

ER_IB_MSG_0
  eng "%s"
  chinese "%s"

ER_IB_MSG_1
  eng "%s"
  chinese "%s"

ER_IB_MSG_2
  eng "%s"
  chinese "%s"

ER_IB_MSG_3
  eng "%s"
  chinese "%s"

ER_IB_MSG_4
  eng "%s"
  chinese "%s"

ER_IB_MSG_5
  eng "%s"
  chinese "%s"

ER_IB_MSG_6
  eng "%s"
  chinese "%s"

ER_IB_MSG_7
  eng "%s"
  chinese "%s"

ER_IB_MSG_8
  eng "%s"
  chinese "%s"

ER_IB_MSG_9
  eng "%s"
  chinese "%s"

ER_IB_MSG_10
  eng "%s"
  chinese "%s"

ER_IB_MSG_11
  eng "%s"
  chinese "%s"

ER_IB_MSG_12
  eng "%s"
  chinese "%s"

ER_IB_MSG_13
  eng "%s"
  chinese "%s"

ER_IB_MSG_14
  eng "%s"
  chinese "%s"

ER_IB_MSG_15
  eng "%s"
  chinese "%s"

ER_IB_MSG_16
  eng "%s"
  chinese "%s"

ER_IB_MSG_17
  eng "%s"
  chinese "%s"

ER_IB_MSG_18
  eng "%s"
  chinese "%s"

ER_IB_MSG_19
  eng "%s"
  chinese "%s"

ER_IB_MSG_20
  eng "%s"
  chinese "%s"

ER_IB_MSG_21
  eng "%s"
  chinese "%s"

ER_IB_MSG_22
  eng "%s"
  chinese "%s"

ER_IB_MSG_23
  eng "%s"
  chinese "%s"

ER_IB_MSG_24
  eng "%s"
  chinese "%s"

ER_IB_MSG_25
  eng "%s"
  chinese "%s"

ER_IB_MSG_26
  eng "%s"
  chinese "%s"

ER_IB_MSG_27
  eng "%s"
  chinese "%s"

ER_IB_MSG_28
  eng "%s"
  chinese "%s"

ER_IB_MSG_29
  eng "%s"
  chinese "%s"

ER_IB_MSG_30
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_31
  eng "%s"
  chinese "%s"

ER_IB_MSG_32
  eng "%s"
  chinese "%s"

ER_IB_MSG_33
  eng "%s"
  chinese "%s"

ER_IB_MSG_34
  eng "%s"
  chinese "%s"

ER_IB_MSG_35
  eng "%s"
  chinese "%s"

ER_IB_MSG_36
  eng "%s"
  chinese "%s"

ER_IB_MSG_37
  eng "%s"
  chinese "%s"

ER_IB_MSG_38
  eng "%s"
  chinese "%s"

ER_IB_MSG_39
  eng "%s"
  chinese "%s"

ER_IB_MSG_40
  eng "%s"
  chinese "%s"

ER_IB_MSG_41
  eng "%s"
  chinese "%s"

ER_IB_MSG_42
  eng "%s"
  chinese "%s"

ER_IB_MSG_43
  eng "%s"
  chinese "%s"

ER_IB_MSG_44
  eng "%s"
  chinese "%s"

ER_IB_MSG_45
  eng "%s"
  chinese "%s"

ER_IB_MSG_46
  eng "%s"
  chinese "%s"

ER_IB_MSG_47
  eng "%s"
  chinese "%s"

ER_IB_MSG_48
  eng "%s"
  chinese "%s"

ER_IB_MSG_49
  eng "%s"
  chinese "%s"

ER_IB_MSG_50
  eng "%s"
  chinese "%s"

ER_IB_MSG_51
  eng "%s"
  chinese "%s"

ER_IB_MSG_52
  eng "%s"
  chinese "%s"

ER_IB_MSG_53
  eng "%s"
  chinese "%s"

ER_IB_MSG_54
  eng "Failed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s"
  chinese "无法设置缓冲区池页帧的NUMA内存策略,MBind(%p,%zu,%s,...,...,%s)失败,错误代码为%s"

ER_IB_MSG_55
  eng "%s"
  chinese "%s"

ER_IB_MSG_56
  eng "%s"
  chinese "%s"

ER_IB_MSG_57
  eng "%s"
  chinese "%s"

ER_IB_MSG_58
  eng "%s"
  chinese "%s"

ER_IB_MSG_59
  eng "%s"
  chinese "%s"

ER_IB_MSG_60
  eng "%s"
  chinese "%s"

ER_IB_MSG_61
  eng "%s"
  chinese "%s"

ER_IB_MSG_62
  eng "%s"
  chinese "%s"

ER_IB_MSG_63
  eng "%s"
  chinese "%s"

ER_IB_MSG_64
  eng "%s"
  chinese "%s"

ER_IB_MSG_65
  eng "%s"
  chinese "%s"

ER_IB_MSG_66
  eng "%s"
  chinese "%s"

ER_IB_MSG_67
  eng "%s"
  chinese "%s"

ER_IB_MSG_68
  eng "%s"
  chinese "%s"

ER_IB_MSG_69
  eng "%s"
  chinese "%s"

ER_IB_MSG_70
  eng "%s"
  chinese "%s"

ER_IB_MSG_71
  eng "%s"
  chinese "%s"

ER_IB_MSG_72
  eng "%s"
  chinese "%s"

ER_IB_MSG_73
  eng "%s"
  chinese "%s"

ER_IB_MSG_74
  eng "%s"
  chinese "%s"

ER_IB_MSG_75
  eng "%s"
  chinese "%s"

ER_IB_MSG_76
  eng "%s"
  chinese "%s"

ER_IB_MSG_77
  eng "%s"
  chinese "%s"

ER_IB_MSG_78
  eng "%s"
  chinese "%s"

ER_IB_MSG_79
  eng "%s"
  chinese "%s"

ER_IB_MSG_80
  eng "%s"
  chinese "%s"

ER_IB_MSG_81
  eng "%s"
  chinese "%s"

ER_IB_MSG_82
  eng "%s"
  chinese "%s"

ER_IB_MSG_83
  eng "%s"
  chinese "%s"

ER_IB_MSG_84
  eng "%s"
  chinese "%s"

ER_IB_MSG_85
  eng "%s"
  chinese "%s"

ER_IB_MSG_86
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_87
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_88
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_89
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_90
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_91
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_92
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_93
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_94
  eng "%s"
  chinese "%s"

ER_IB_MSG_95
  eng "%s"
  chinese "%s"

ER_IB_MSG_96
  eng "%s"
  chinese "%s"

ER_IB_MSG_97
  eng "%s"
  chinese "%s"

ER_IB_MSG_98
  eng "%s"
  chinese "%s"

ER_IB_MSG_99
  eng "%s"
  chinese "%s"

ER_IB_MSG_100
  eng "%s"
  chinese "%s"

ER_IB_MSG_101
  eng "%s"
  chinese "%s"

ER_IB_MSG_102
  eng "%s"
  chinese "%s"

ER_IB_MSG_103
  eng "%s"
  chinese "%s"

ER_IB_MSG_104
  eng "%s"
  chinese "%s"

ER_IB_MSG_105
  eng "%s"
  chinese "%s"

ER_IB_MSG_106
  eng "%s"
  chinese "%s"

ER_IB_MSG_107
  eng "%s"
  chinese "%s"

ER_IB_MSG_108
  eng "%s"
  chinese "%s"

ER_IB_MSG_109
  eng "%s"
  chinese "%s"

ER_IB_MSG_110
  eng "%s"
  chinese "%s"

ER_IB_MSG_111
  eng "%s"
  chinese "%s"

ER_IB_MSG_112
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_113
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_114
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_115
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_116
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_117
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_118
  eng "%s"
  chinese "%s"

ER_IB_MSG_119
  eng "%s"
  chinese "%s"

ER_IB_MSG_120
  eng "%s"
  chinese "%s"

ER_IB_MSG_121
  eng "%s"
  chinese "%s"

ER_IB_MSG_122
  eng "%s"
  chinese "%s"

ER_IB_MSG_123
  eng "%s"
  chinese "%s"

ER_IB_MSG_124
  eng "%s"
  chinese "%s"

ER_IB_MSG_125
  eng "%s"
  chinese "%s"

ER_IB_MSG_126
  eng "%s"
  chinese "%s"

ER_IB_MSG_127
  eng "%s"
  chinese "%s"

ER_IB_MSG_128
  eng "%s"
  chinese "%s"

ER_IB_MSG_129
  eng "%s"
  chinese "%s"

ER_IB_MSG_130
  eng "%s"
  chinese "%s"

ER_IB_MSG_131
  eng "%s"
  chinese "%s"

ER_IB_MSG_132
  eng "%s"
  chinese "%s"

ER_IB_MSG_133
  eng "%s"
  chinese "%s"

ER_IB_MSG_134
  eng "%s"
  chinese "%s"

ER_IB_MSG_135
  eng "%s"
  chinese "%s"

ER_IB_MSG_136
  eng "%s"
  chinese "%s"

ER_IB_MSG_137
  eng "%s"
  chinese "%s"

ER_IB_MSG_138
  eng "%s"
  chinese "%s"

ER_IB_MSG_139
  eng "%s"
  chinese "%s"

ER_IB_MSG_140
  eng "%s"
  chinese "%s"

ER_IB_MSG_141
  eng "%s"
  chinese "%s"

ER_IB_MSG_142
  eng "%s"
  chinese "%s"

ER_IB_MSG_143
  eng "%s"
  chinese "%s"

ER_IB_MSG_144
  eng "%s"
  chinese "%s"

ER_IB_MSG_145
  eng "%s"
  chinese "%s"

ER_IB_MSG_146
  eng "%s"
  chinese "%s"

ER_IB_MSG_147
  eng "%s"
  chinese "%s"

ER_IB_MSG_148
  eng "%s"
  chinese "%s"

ER_IB_CLONE_INTERNAL
  eng "%s"
  chinese "%s"

ER_IB_CLONE_TIMEOUT
  eng "%s"
  chinese "%s"

ER_IB_CLONE_STATUS_FILE
  eng "%s"
  chinese "%s"

ER_IB_CLONE_SQL
  eng "%s"
  chinese "%s"

ER_IB_CLONE_VALIDATE
  eng "%s"
  chinese "%s"

ER_IB_CLONE_PUNCH_HOLE
  eng "%s"
  chinese "%s"

ER_IB_CLONE_GTID_PERSIST
  eng "%s"
  chinese "%s"

ER_IB_MSG_156
  eng "%s"
  chinese "%s"

ER_IB_MSG_157
  eng "%s"
  chinese "%s"

ER_IB_MSG_158
  eng "%s"
  chinese "%s"

ER_IB_MSG_159
  eng "%s"
  chinese "%s"

ER_IB_MSG_160
  eng "%s"
  chinese "%s"

ER_IB_MSG_161
  eng "%s"
  chinese "%s"

ER_IB_MSG_162
  eng "%s"
  chinese "%s"

ER_IB_MSG_163
  eng "%s"
  chinese "%s"

ER_IB_MSG_164
  eng "%s"
  chinese "%s"

ER_IB_MSG_165
  eng "%s"
  chinese "%s"

ER_IB_MSG_166
  eng "%s"
  chinese "%s"

ER_IB_MSG_167
  eng "%s"
  chinese "%s"

ER_IB_MSG_168
  eng "%s"
  chinese "%s"

ER_IB_MSG_169
  eng "%s"
  chinese "%s"

ER_IB_MSG_170
  eng "%s"
  chinese "%s"

ER_IB_MSG_171
  eng "%s"
  chinese "%s"

ER_IB_MSG_172
  eng "%s"
  chinese "%s"

ER_IB_MSG_173
  eng "%s"
  chinese "%s"

ER_IB_MSG_174
  eng "%s"
  chinese "%s"

ER_IB_MSG_175
  eng "%s"
  chinese "%s"

ER_IB_MSG_176
  eng "%s"
  chinese "%s"

ER_IB_MSG_177
  eng "%s"
  chinese "%s"

ER_IB_MSG_178
  eng "%s"
  chinese "%s"

ER_IB_MSG_179
  eng "%s"
  chinese "%s"

ER_IB_MSG_180
  eng "%s"
  chinese "%s"

ER_IB_LONG_AHI_DISABLE_WAIT
  eng "Waited for %u secs for hash index ref_count (%zu) to drop to 0. index: \"%s\" table: \"%s\""
  chinese "已等待%u秒以使哈希索引ref_count(%zu)降至0。索引:'%s'表:'%s'"

ER_IB_MSG_182
  eng "%s"
  chinese "%s"

ER_IB_MSG_183
  eng "%s"
  chinese "%s"

ER_IB_MSG_184
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_185
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_186
  eng "%s"
  chinese "%s"

ER_IB_MSG_187
  eng "%s"
  chinese "%s"

ER_IB_MSG_188
  eng "%s"
  chinese "%s"

ER_IB_MSG_189
  eng "%s"
  chinese "%s"

ER_IB_MSG_190
  eng "%s"
  chinese "%s"

ER_IB_MSG_191
  eng "%s"
  chinese "%s"

ER_IB_MSG_192
  eng "%s"
  chinese "%s"

ER_IB_MSG_193
  eng "%s"
  chinese "%s"

ER_IB_MSG_194
  eng "%s"
  chinese "%s"

ER_IB_MSG_195
  eng "%s"
  chinese "%s"

ER_IB_MSG_196
  eng "%s"
  chinese "%s"

ER_IB_MSG_197
  eng "%s"
  chinese "%s"

ER_IB_MSG_198
  eng "%s"
  chinese "%s"

ER_IB_MSG_199
  eng "%s"
  chinese "%s"

ER_IB_MSG_200
  eng "%s"
  chinese "%s"

ER_IB_MSG_201
  eng "%s"
  chinese "%s"

ER_IB_MSG_202
  eng "%s"
  chinese "%s"

ER_IB_MSG_203
  eng "%s"
  chinese "%s"

ER_IB_MSG_204
  eng "%s"
  chinese "%s"

ER_IB_MSG_205
  eng "%s"
  chinese "%s"

ER_IB_MSG_206
  eng "%s"
  chinese "%s"

ER_IB_MSG_207
  eng "%s"
  chinese "%s"

ER_IB_MSG_208
  eng "%s"
  chinese "%s"

ER_IB_MSG_209
  eng "%s"
  chinese "%s"

ER_IB_MSG_210
  eng "%s"
  chinese "%s"

ER_IB_MSG_211
  eng "%s"
  chinese "%s"

ER_IB_MSG_212
  eng "%s"
  chinese "%s"

ER_IB_MSG_213
  eng "%s"
  chinese "%s"

ER_IB_MSG_214
  eng "%s"
  chinese "%s"

ER_IB_MSG_215
  eng "%s"
  chinese "%s"

ER_IB_MSG_216
  eng "%s"
  chinese "%s"

ER_IB_MSG_217
  eng "%s"
  chinese "%s"

ER_IB_MSG_218
  eng "%s"
  chinese "%s"

ER_IB_MSG_219
  eng "%s"
  chinese "%s"

ER_IB_MSG_220
  eng "%s"
  chinese "%s"

ER_IB_MSG_221
  eng "%s"
  chinese "%s"

ER_IB_MSG_222
  eng "%s"
  chinese "%s"

ER_IB_MSG_223
  eng "%s"
  chinese "%s"

ER_IB_MSG_224
  eng "%s"
  chinese "%s"

ER_IB_MSG_225
  eng "%s"
  chinese "%s"

ER_IB_MSG_226
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_227
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_228
  eng "%s"
  chinese "%s"

ER_IB_MSG_229
  eng "%s"
  chinese "%s"

ER_IB_MSG_230
  eng "%s"
  chinese "%s"

ER_IB_MSG_231
  eng "%s"
  chinese "%s"

ER_IB_MSG_232
  eng "%s"
  chinese "%s"

ER_IB_MSG_233
  eng "%s"
  chinese "%s"

ER_IB_MSG_234
  eng "%s"
  chinese "%s"

ER_IB_MSG_235
  eng "%s"
  chinese "%s"

ER_IB_MSG_236
  eng "%s"
  chinese "%s"

ER_IB_MSG_237
  eng "%s"
  chinese "%s"

ER_IB_MSG_238
  eng "%s"
  chinese "%s"

ER_IB_MSG_239
  eng "%s"
  chinese "%s"

ER_IB_MSG_240
  eng "%s"
  chinese "%s"

ER_IB_MSG_241
  eng "%s"
  chinese "%s"

ER_IB_MSG_242
  eng "%s"
  chinese "%s"

ER_IB_MSG_243
  eng "%s"
  chinese "%s"

ER_IB_MSG_244
  eng "%s"
  chinese "%s"

ER_IB_MSG_245
  eng "%s"
  chinese "%s"

ER_IB_MSG_246
  eng "%s"
  chinese "%s"

ER_IB_MSG_247
  eng "%s"
  chinese "%s"

ER_IB_MSG_248
  eng "%s"
  chinese "%s"

ER_IB_MSG_249
  eng "%s"
  chinese "%s"

ER_IB_MSG_250
  eng "%s"
  chinese "%s"

ER_IB_MSG_251
  eng "%s"
  chinese "%s"

ER_IB_MSG_252
  eng "%s"
  chinese "%s"

ER_IB_MSG_253
  eng "%s"
  chinese "%s"

ER_IB_MSG_254
  eng "%s"
  chinese "%s"

ER_IB_MSG_255
  eng "%s"
  chinese "%s"

ER_IB_MSG_256
  eng "%s"
  chinese "%s"

ER_IB_MSG_257
  eng "%s"
  chinese "%s"

ER_IB_MSG_258
  eng "%s"
  chinese "%s"

ER_IB_MSG_259
  eng "%s"
  chinese "%s"

ER_IB_MSG_260
  eng "%s"
  chinese "%s"

ER_IB_MSG_261
  eng "%s"
  chinese "%s"

ER_IB_MSG_262
  eng "%s"
  chinese "%s"

ER_IB_MSG_263
  eng "%s"
  chinese "%s"

ER_IB_MSG_264
  eng "%s"
  chinese "%s"

ER_IB_MSG_265
  eng "%s"
  chinese "%s"

ER_IB_MSG_266
  eng "%s"
  chinese "%s"

ER_IB_MSG_267
  eng "%s"
  chinese "%s"

ER_IB_MSG_268
  eng "%s"
  chinese "%s"

ER_IB_MSG_269
  eng "%s"
  chinese "%s"

ER_IB_MSG_270
  eng "%s"
  chinese "%s"

ER_IB_MSG_271
  eng "%s"
  chinese "%s"

ER_IB_MSG_272
  eng "Table flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!"
  chinese "表标志在数据字典中为 0x%lx ,但文件%s中的标志为 0x%llx "

ER_IB_MSG_273
  eng "Can't read encryption key from file %s!"
  chinese "无法从文件%s读取加密密钥！"

OBSOLETE_ER_IB_MSG_274
  eng "Cannot close file %s, because n_pending_flushes %zu"
  chinese "无法关闭文件%s,因为n_ending_flushes%zu"

OBSOLETE_ER_IB_MSG_275
  eng "Cannot close file %s, because modification count %lld != flush count %lld"
  chinese "无法关闭文件%s,因为修改计数%lld！=刷新计数%lld"

OBSOLETE_ER_IB_MSG_276
  eng "Cannot close file %s, because it is in use"
  chinese "无法关闭文件%s,因为它正在使用中"

OBSOLETE_ER_IB_MSG_277
  eng "Open file list len in shard %zu is %llu"
  chinese "碎片%zu中的打开文件列表长度为%llu"

ER_IB_MSG_278
  eng "Tablespace %s, waiting for IO to stop for %lld seconds"
  chinese "表空间%s,正在等待IO停止%lld秒"

OBSOLETE_ER_IB_MSG_279
  eng "%s"
  chinese "%s"

ER_IB_MSG_280
  eng "%s"
  chinese "%s"

ER_IB_MSG_281
  eng "%s"
  chinese "%s"

ER_IB_MSG_282
  eng "%s"
  chinese "%s"

ER_IB_MSG_283
  eng "%s"
  chinese "%s"

ER_IB_MSG_284
  eng "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."
  chinese "您必须提高my.cnf中Innodb_OPEN_FILES的值！请记住,InnoDB在mysqld运行的整个过程中始终保持打开所有重做日志文件和所有系统表空间文件,如果使用逐个表存储模型,还需要打开一些.ibd文件。当前打开的文件%zu,允许的最大打开文件%zu。"

ER_IB_MSG_285
  eng "Max tablespace id is too high, %lu"
  chinese "最大表空间ID太高,%lu"

ER_IB_WARN_ACCESSING_NONEXISTINC_SPACE
  eng "Trying to access missing tablespace %lu"
  chinese "正在尝试访问缺少的表空间%lu"

ER_IB_MSG_287
  eng "Trying to close/delete tablespace '%s' but there are %lu pending operations on it."
  chinese "正在尝试关闭/删除表空间'%s'',但它上有%lu个挂起的操作。"

ER_IB_MSG_288
  eng "Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it."
  chinese "正在尝试删除/关闭表空间'%s',但其上有%lu个刷新和%zu个挂起的I/O。"

ER_IB_MSG_289
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_290
  eng "Cannot delete tablespace %lu because it is not found in the tablespace memory cache."
  chinese "无法删除表空间%lu,因为在表空间内存缓存中找不到它。"

ER_IB_MSG_291
  eng "While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %s"
  chinese "删除丢弃表空间中的表空间%lu时。文件重命名/删除失败:%s"

ER_IB_MSG_292
  eng "Cannot delete tablespace %lu in DISCARD TABLESPACE: %s"
  chinese "无法删除磁盘表空间%lu中的表空间:%s"

ER_IB_MSG_293
  eng "Cannot rename '%s' to '%s' for space ID %lu because the source file does not exist."
  chinese "无法将'%s'重命名为'%s',空间ID%lu的,因为源文件不存在。"

ER_IB_MSG_294
  eng "Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again."
  chinese "无法将'%s'重命名为'%s',空间ID%lu的,因为目标文件存在。请删除目标文件,然后重试。"

ER_IB_MSG_295
  eng "Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended."
  chinese "无法重命名文件'%s'(空间ID%lu)重试%llu次。存在挂起的IO或刷新,或者正在扩展文件。"

ER_IB_MSG_296
  eng "Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID."
  chinese "在表空间内存缓存中找不到空间ID%lu,尽管重命名操作中的文件'%s'应该具有该ID。"

ER_IB_MSG_297
  eng "Rename waiting for IO to resume"
  chinese "重命名等待IO恢复"

ER_IB_MSG_298
  eng "Cannot find tablespace for '%s' in the tablespace memory cache"
  chinese "在表空间内存缓存中找不到'%s'的表空间"

ER_IB_MSG_299
  eng "Cannot find tablespace for '%s' in the tablespace memory cache"
  chinese "在表空间内存缓存中找不到'%s'的表空间"

ER_IB_MSG_300
  eng "Tablespace '%s' is already in the tablespace memory cache"
  chinese "表空间'%s'已在表空间内存缓存中"

ER_IB_MSG_301
  eng "Cannot create file '%s'"
  chinese "无法创建文件'%s'"

ER_IB_MSG_UNEXPECTED_FILE_EXISTS
  eng "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."
  chinese "文件'%s'已经存在,但相应的表不存在。您是在没有使用SQL命令DIRED TABLESPACE和IMPORT TABLESPACE的情况下移动InnoDB.ibd文件,还是在CREATE TABLE中间崩溃了？您可以通过删除MySQL'datadir'下的文件'%s'来解决这个问题。"

ER_IB_MSG_303
  eng "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."
  chinese "POSIX_FALLOCATE():无法为文件%s预分配数据,所需大小%llu操作系统错误号%d-%s。请检查磁盘是否未满或是否超过了磁盘配额。请确保文件系统支持此功能。有关操作系统错误代码信息,请参阅操作系统文档。"

ER_IB_MSG_304
  eng "Could not write the first page to tablespace '%s'"
  chinese "无法将第一页写入表空间'%s'"

ER_IB_MSG_305
  eng "File flush of tablespace '%s' failed"
  chinese "表空间'%s'的文件刷新失败"

ER_IB_MSG_306
  eng "Could not find a valid tablespace file for `%s`. %s"
  chinese "找不到`%s'的有效表空间文件。%s"

ER_IB_MSG_307
  eng "Ignoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID"
  chinese "正在忽略数据文件'%s'空间ID为%lu的。另一个名为'%s'的数据文件具有相同的空间ID"

ER_IB_MSG_308
  eng "%s"
  chinese "%s"

ER_IB_MSG_309
  eng "%s"
  chinese "%s"

ER_IB_MSG_310
  eng "%s"
  chinese "%s"

ER_IB_MSG_311
  eng "%s"
  chinese "%s"

ER_IB_MSG_312
  eng "Can't set encryption information for tablespace %s!"
  chinese "无法为表空间%s设置加密信息！"

ER_IB_MSG_313
  eng "%s"
  chinese "%s"

ER_IB_MSG_314
  eng "%s"
  chinese "%s"

ER_IB_MSG_315
  eng "%s"
  chinese "%s"

ER_IB_MSG_316
  eng "%s"
  chinese "%s"

ER_IB_MSG_317
  eng "%s"
  chinese "%s"

ER_IB_MSG_318
  eng "%s"
  chinese "%s"

ER_IB_MSG_319
  eng "%s"
  chinese "%s"

ER_IB_MSG_320
  eng "%s"
  chinese "%s"

ER_IB_MSG_321
  eng "%s"
  chinese "%s"

ER_IB_MSG_322
  eng "%s"
  chinese "%s"

ER_IB_MSG_323
  eng "%s"
  chinese "%s"

ER_IB_MSG_324
  eng "%s"
  chinese "%s"

ER_IB_MSG_325
  eng "%s"
  chinese "%s"

ER_IB_MSG_326
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_327
  eng "%s"
  chinese "%s"

ER_IB_MSG_328
  eng "%s"
  chinese "%s"

ER_IB_MSG_329
  eng "%s"
  chinese "%s"

ER_IB_MSG_330
  eng "%s"
  chinese "%s"

ER_IB_MSG_331
  eng "%s"
  chinese "%s"

ER_IB_MSG_332
  eng "%s"
  chinese "%s"

ER_IB_MSG_333
  eng "%s"
  chinese "%s"

ER_IB_MSG_334
  eng "%s"
  chinese "%s"

ER_IB_MSG_335
  eng "%s"
  chinese "%s"

ER_IB_MSG_336
  eng "%s"
  chinese "%s"

ER_IB_MSG_337
  eng "%s"
  chinese "%s"

ER_IB_MSG_338
  eng "%s"
  chinese "%s"

ER_IB_MSG_339
  eng "%s"
  chinese "%s"

ER_IB_MSG_340
  eng "%s"
  chinese "%s"

ER_IB_MSG_341
  eng "%s"
  chinese "%s"

ER_IB_MSG_342
  eng "%s"
  chinese "%s"

ER_IB_MSG_343
  eng "%s"
  chinese "%s"

ER_IB_MSG_344
  eng "%s"
  chinese "%s"

ER_IB_MSG_345
  eng "%s"
  chinese "%s"

ER_IB_MSG_346
  eng "%s"
  chinese "%s"

ER_IB_MSG_347
  eng "%s"
  chinese "%s"

ER_IB_MSG_348
  eng "%s"
  chinese "%s"

ER_IB_MSG_349
  eng "%s"
  chinese "%s"

ER_IB_MSG_350
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_351
  eng "%s"
  chinese "%s"

ER_IB_MSG_UNPROTECTED_LOCATION_ALLOWED
  eng "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."
  chinese "表空间%s的数据文件'%s'位于不受保护的位置。该文件在崩溃后无法恢复,直到将该位置添加到Innodb_DIRECTORIES。"

OBSOLETE_ER_IB_MSG_353
  eng "%s"
  chinese "%s"

ER_IB_MSG_354
  eng "%s"
  chinese "%s"

ER_IB_MSG_355
  eng "%s"
  chinese "%s"

ER_IB_MSG_356
  eng "%s"
  chinese "%s"

ER_IB_MSG_357
  eng "%s"
  chinese "%s"

ER_IB_MSG_358
  eng "%s"
  chinese "%s"

ER_IB_MSG_359
  eng "%s"
  chinese "%s"

ER_IB_MSG_360
  eng "%s"
  chinese "%s"

ER_IB_MSG_361
  eng "%s"
  chinese "%s"

ER_IB_MSG_362
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_363
  eng "%s"
  chinese "%s"

ER_IB_MSG_364
  eng "%s"
  chinese "%s"

ER_IB_MSG_365
  eng "%s"
  chinese "%s"

ER_IB_MSG_IGNORE_SCAN_PATH
  eng "Scan path '%s' is ignored because %s"
  chinese "由于%s,扫描路径'%s'被忽略"

ER_IB_MSG_367
  eng "%s"
  chinese "%s"

ER_IB_MSG_368
  eng "%s"
  chinese "%s"

ER_IB_MSG_369
  eng "%s"
  chinese "%s"

ER_IB_MSG_370
  eng "%s"
  chinese "%s"

ER_IB_MSG_371
  eng "%s"
  chinese "%s"

ER_IB_MSG_372
  eng "%s"
  chinese "%s"

ER_IB_MSG_373
  eng "%s"
  chinese "%s"

ER_IB_MSG_374
  eng "%s"
  chinese "%s"

ER_IB_MSG_375
  eng "%s"
  chinese "%s"

ER_IB_MSG_376
  eng "%s"
  chinese "%s"

ER_IB_MSG_377
  eng "%s"
  chinese "%s"

ER_IB_MSG_378
  eng "%s"
  chinese "%s"

ER_IB_MSG_379
  eng "%s"
  chinese "%s"

ER_IB_MSG_380
  eng "%s"
  chinese "%s"

ER_IB_MSG_381
  eng "%s"
  chinese "%s"

ER_IB_MSG_382
  eng "%s"
  chinese "%s"

ER_IB_MSG_383
  eng "%s"
  chinese "%s"

ER_IB_MSG_384
  eng "%s"
  chinese "%s"

ER_IB_MSG_385
  eng "%s"
  chinese "%s"

ER_IB_MSG_386
  eng "%s"
  chinese "%s"

ER_IB_MSG_387
  eng "%s"
  chinese "%s"

ER_IB_MSG_GENERAL_TABLESPACE_UNDER_DATADIR
  eng "A general tablespace cannot be located under the datadir. Cannot open file '%s'."
  chinese "在数据目录下找不到常规表空间。无法打开文件'%s'。"

ER_IB_MSG_IMPLICIT_TABLESPACE_IN_DATADIR
  eng "A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'."
  chinese "在数据目录中找不到每个表的文件表空间。无法打开文件'%s'。"

ER_IB_MSG_390
  eng "%s"
  chinese "%s"

ER_IB_MSG_391
  eng "%s"
  chinese "%s"

ER_IB_MSG_392
  eng "%s"
  chinese "%s"

ER_IB_MSG_393
  eng "%s"
  chinese "%s"

ER_IB_MSG_394
  eng "%s"
  chinese "%s"

ER_IB_MSG_395
  eng "%s"
  chinese "%s"

ER_IB_MSG_396
  eng "%s"
  chinese "%s"

ER_IB_MSG_397
  eng "%s"
  chinese "%s"

ER_IB_MSG_398
  eng "%s"
  chinese "%s"

ER_IB_MSG_399
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_400
  eng "%s"
  chinese "%s"

ER_IB_MSG_401
  eng "%s"
  chinese "%s"

ER_IB_MSG_402
  eng "%s"
  chinese "%s"

ER_IB_MSG_403
  eng "%s"
  chinese "%s"

ER_IB_MSG_404
  eng "%s"
  chinese "%s"

ER_IB_MSG_405
  eng "%s"
  chinese "%s"

ER_IB_MSG_406
  eng "%s"
  chinese "%s"

ER_IB_MSG_407
  eng "%s"
  chinese "%s"

ER_IB_MSG_408
  eng "%s"
  chinese "%s"

ER_IB_MSG_409
  eng "%s"
  chinese "%s"

ER_IB_MSG_410
  eng "%s"
  chinese "%s"

ER_IB_MSG_411
  eng "%s"
  chinese "%s"

ER_IB_MSG_412
  eng "%s"
  chinese "%s"

ER_IB_MSG_413
  eng "%s"
  chinese "%s"

ER_IB_MSG_414
  eng "%s"
  chinese "%s"

ER_IB_MSG_415
  eng "%s"
  chinese "%s"

ER_IB_MSG_416
  eng "%s"
  chinese "%s"

ER_IB_MSG_417
  eng "%s"
  chinese "%s"

ER_IB_MSG_418
  eng "%s"
  chinese "%s"

ER_IB_MSG_419
  eng "%s"
  chinese "%s"

ER_IB_MSG_420
  eng "%s"
  chinese "%s"

ER_IB_MSG_421
  eng "%s"
  chinese "%s"

ER_IB_MSG_422
  eng "%s"
  chinese "%s"

ER_IB_MSG_423
  eng "%s"
  chinese "%s"

ER_IB_MSG_424
  eng "%s"
  chinese "%s"

ER_IB_MSG_425
  eng "%s"
  chinese "%s"

ER_IB_MSG_426
  eng "%s"
  chinese "%s"

ER_IB_MSG_427
  eng "%s"
  chinese "%s"

ER_IB_MSG_428
  eng "%s"
  chinese "%s"

ER_IB_MSG_429
  eng "%s"
  chinese "%s"

ER_IB_MSG_430
  eng "%s"
  chinese "%s"

ER_IB_MSG_431
  eng "%s"
  chinese "%s"

ER_IB_MSG_432
  eng "%s"
  chinese "%s"

ER_IB_MSG_433
  eng "%s"
  chinese "%s"

ER_IB_MSG_434
  eng "%s"
  chinese "%s"

ER_IB_MSG_435
  eng "%s"
  chinese "%s"

ER_IB_MSG_436
  eng "%s"
  chinese "%s"

ER_IB_MSG_437
  eng "%s"
  chinese "%s"

ER_IB_MSG_438
  eng "%s"
  chinese "%s"

ER_IB_MSG_439
  eng "%s"
  chinese "%s"

ER_IB_MSG_440
  eng "%s"
  chinese "%s"

ER_IB_MSG_441
  eng "%s"
  chinese "%s"

ER_IB_MSG_442
  eng "%s"
  chinese "%s"

ER_IB_MSG_443
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_444
  eng "%s"
  chinese "%s"

ER_IB_MSG_445
  eng "%s"
  chinese "%s"

ER_IB_MSG_446
  eng "%s"
  chinese "%s"

ER_IB_MSG_447
  eng "%s"
  chinese "%s"

ER_IB_MSG_448
  eng "%s"
  chinese "%s"

ER_IB_MSG_449
  eng "%s"
  chinese "%s"

ER_IB_MSG_450
  eng "%s"
  chinese "%s"

ER_IB_MSG_451
  eng "%s"
  chinese "%s"

ER_IB_MSG_452
  eng "%s"
  chinese "%s"

ER_IB_MSG_453
  eng "%s"
  chinese "%s"

ER_IB_MSG_454
  eng "%s"
  chinese "%s"

ER_IB_MSG_455
  eng "%s"
  chinese "%s"

ER_IB_MSG_456
  eng "%s"
  chinese "%s"

ER_IB_MSG_457
  eng "%s"
  chinese "%s"

ER_IB_MSG_458
  eng "%s"
  chinese "%s"

ER_IB_MSG_459
  eng "%s"
  chinese "%s"

ER_IB_MSG_460
  eng "%s"
  chinese "%s"

ER_IB_MSG_461
  eng "%s"
  chinese "%s"

ER_IB_MSG_462
  eng "%s"
  chinese "%s"

ER_IB_MSG_463
  eng "%s"
  chinese "%s"

ER_IB_MSG_464
  eng "%s"
  chinese "%s"

ER_IB_MSG_465
  eng "%s"
  chinese "%s"

ER_IB_MSG_466
  eng "%s"
  chinese "%s"

ER_IB_MSG_467
  eng "%s"
  chinese "%s"

ER_IB_MSG_468
  eng "%s"
  chinese "%s"

ER_IB_MSG_469
  eng "%s"
  chinese "%s"

ER_IB_MSG_470
  eng "%s"
  chinese "%s"

ER_IB_MSG_471
  eng "%s"
  chinese "%s"

ER_IB_MSG_472
  eng "%s"
  chinese "%s"

ER_IB_MSG_473
  eng "%s"
  chinese "%s"

ER_IB_MSG_474
  eng "%s"
  chinese "%s"

ER_IB_MSG_475
  eng "%s"
  chinese "%s"

ER_IB_MSG_476
  eng "%s"
  chinese "%s"

ER_IB_MSG_477
  eng "%s"
  chinese "%s"

ER_IB_MSG_478
  eng "%s"
  chinese "%s"

ER_IB_MSG_479
  eng "%s"
  chinese "%s"

ER_IB_MSG_480
  eng "%s"
  chinese "%s"

ER_IB_MSG_481
  eng "%s"
  chinese "%s"

ER_IB_MSG_482
  eng "%s"
  chinese "%s"

ER_IB_MSG_483
  eng "%s"
  chinese "%s"

ER_IB_MSG_484
  eng "%s"
  chinese "%s"

ER_IB_MSG_485
  eng "%s"
  chinese "%s"

ER_IB_MSG_486
  eng "%s"
  chinese "%s"

ER_IB_MSG_487
  eng "%s"
  chinese "%s"

ER_IB_MSG_488
  eng "%s"
  chinese "%s"

ER_IB_MSG_489
  eng "%s"
  chinese "%s"

ER_IB_MSG_490
  eng "%s"
  chinese "%s"

ER_IB_MSG_491
  eng "%s"
  chinese "%s"

ER_IB_MSG_492
  eng "%s"
  chinese "%s"

ER_IB_MSG_493
  eng "%s"
  chinese "%s"

ER_IB_MSG_494
  eng "%s"
  chinese "%s"

ER_IB_MSG_495
  eng "%s"
  chinese "%s"

ER_IB_MSG_496
  eng "%s"
  chinese "%s"

ER_IB_MSG_497
  eng "%s"
  chinese "%s"

ER_IB_MSG_498
  eng "%s"
  chinese "%s"

ER_IB_MSG_499
  eng "%s"
  chinese "%s"

ER_IB_MSG_500
  eng "%s"
  chinese "%s"

ER_IB_MSG_501
  eng "%s"
  chinese "%s"

ER_IB_MSG_502
  eng "%s"
  chinese "%s"

ER_IB_MSG_503
  eng "%s"
  chinese "%s"

ER_IB_MSG_504
  eng "%s"
  chinese "%s"

ER_IB_MSG_505
  eng "%s"
  chinese "%s"

ER_IB_MSG_506
  eng "%s"
  chinese "%s"

ER_IB_MSG_507
  eng "%s"
  chinese "%s"

ER_IB_MSG_508
  eng "%s"
  chinese "%s"

ER_IB_MSG_509
  eng "%s"
  chinese "%s"

ER_IB_MSG_510
  eng "%s"
  chinese "%s"

ER_IB_MSG_511
  eng "%s"
  chinese "%s"

ER_IB_MSG_512
  eng "%s"
  chinese "%s"

ER_IB_MSG_513
  eng "%s"
  chinese "%s"

ER_IB_MSG_514
  eng "%s"
  chinese "%s"

ER_IB_MSG_515
  eng "%s"
  chinese "%s"

ER_IB_MSG_516
  eng "%s"
  chinese "%s"

ER_IB_MSG_517
  eng "%s"
  chinese "%s"

ER_IB_MSG_518
  eng "%s"
  chinese "%s"

ER_IB_MSG_519
  eng "%s"
  chinese "%s"

ER_IB_MSG_520
  eng "%s"
  chinese "%s"

ER_IB_MSG_521
  eng "%s"
  chinese "%s"

ER_IB_MSG_522
  eng "%s"
  chinese "%s"

ER_IB_MSG_523
  eng "%s"
  chinese "%s"

ER_IB_MSG_524
  eng "%s"
  chinese "%s"

ER_IB_MSG_525
  eng "%s"
  chinese "%s"

ER_IB_MSG_526
  eng "%s"
  chinese "%s"

ER_IB_MSG_527
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_528
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_529
  eng "%s"
  chinese "%s"

ER_IB_MSG_530
  eng "%s"
  chinese "%s"

ER_IB_MSG_531
  eng "%s"
  chinese "%s"

ER_IB_MSG_532
  eng "%s"
  chinese "%s"

ER_IB_MSG_533
  eng "%s"
  chinese "%s"

ER_IB_MSG_534
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_535
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_536
  eng "%s"
  chinese "%s"

ER_IB_MSG_537
  eng "%s"
  chinese "%s"

ER_IB_MSG_538
  eng "%s"
  chinese "%s"

ER_IB_MSG_539
  eng "%s"
  chinese "%s"

ER_IB_MSG_540
  eng "%s"
  chinese "%s"

ER_IB_MSG_541
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_542
  eng "%s"
  chinese "%s"

ER_IB_MSG_543
  eng "%s"
  chinese "%s"

ER_IB_MSG_544
  eng "%s"
  chinese "%s"

ER_IB_MSG_545
  eng "%s"
  chinese "%s"

ER_IB_MSG_546
  eng "%s"
  chinese "%s"

ER_IB_MSG_547
  eng "%s"
  chinese "%s"

ER_IB_MSG_548
  eng "%s"
  chinese "%s"

ER_IB_MSG_549
  eng "%s"
  chinese "%s"

ER_IB_MSG_550
  eng "%s"
  chinese "%s"

ER_IB_MSG_551
  eng "%s"
  chinese "%s"

ER_IB_MSG_552
  eng "%s"
  chinese "%s"

ER_IB_MSG_553
  eng "%s"
  chinese "%s"

ER_IB_MSG_554
  eng "%s"
  chinese "%s"

ER_IB_MSG_555
  eng "%s"
  chinese "%s"

ER_IB_MSG_556
  eng "%s"
  chinese "%s"

ER_IB_MSG_557
  eng "%s"
  chinese "%s"

ER_IB_MSG_558
  eng "%s"
  chinese "%s"

ER_IB_MSG_559
  eng "%s"
  chinese "%s"

ER_IB_MSG_560
  eng "%s"
  chinese "%s"

ER_IB_MSG_561
  eng "%s"
  chinese "%s"

ER_IB_MSG_562
  eng "%s"
  chinese "%s"

ER_IB_MSG_563
  eng "%s"
  chinese "%s"

ER_IB_MSG_564
  eng "%s"
  chinese "%s"

ER_IB_MSG_INVALID_LOCATION_FOR_TABLE
  eng "Cannot create a tablespace for table %s because the directory is not a valid location. %s"
  chinese "无法为表%s创建表空间,因为该目录不是有效位置。%s"

ER_IB_MSG_566
  eng "%s"
  chinese "%s"

ER_IB_MSG_567
  eng "%s"
  chinese "%s"

ER_IB_MSG_568
  eng "%s"
  chinese "%s"

ER_IB_MSG_569
  eng "%s"
  chinese "%s"

ER_IB_MSG_570
  eng "%s"
  chinese "%s"

ER_IB_MSG_571
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_572
  eng "%s"
  chinese "%s"

ER_IB_MSG_573
  eng "%s"
  chinese "%s"

ER_IB_MSG_574
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_575
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_576
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_577
  eng "%s"
  chinese "%s"

ER_IB_MSG_578
  eng "%s"
  chinese "%s"

ER_IB_MSG_579
  eng "%s"
  chinese "%s"

ER_IB_MSG_580
  eng "%s"
  chinese "%s"

ER_IB_MSG_581
  eng "%s"
  chinese "%s"

ER_IB_MSG_582
  eng "%s"
  chinese "%s"

ER_IB_MSG_583
  eng "%s"
  chinese "%s"

ER_IB_MSG_584
  eng "%s"
  chinese "%s"

ER_IB_MSG_585
  eng "%s"
  chinese "%s"

ER_IB_MSG_586
  eng "%s"
  chinese "%s"

ER_IB_MSG_587
  eng "%s"
  chinese "%s"

ER_IB_MSG_588
  eng "%s"
  chinese "%s"

ER_IB_MSG_589
  eng "%s"
  chinese "%s"

ER_IB_MSG_590
  eng "%s"
  chinese "%s"

ER_IB_MSG_591
  eng "%s"
  chinese "%s"

ER_IB_MSG_592
  eng "%s"
  chinese "%s"

ER_IB_MSG_593
  eng "%s"
  chinese "%s"

ER_IB_MSG_594
  eng "%s"
  chinese "%s"

ER_IB_MSG_595
  eng "%s"
  chinese "%s"

ER_IB_MSG_596
  eng "%s"
  chinese "%s"

ER_IB_MSG_597
  eng "%s"
  chinese "%s"

ER_IB_MSG_598
  eng "%s"
  chinese "%s"

ER_IB_MSG_599
  eng "%s"
  chinese "%s"

ER_IB_MSG_600
  eng "%s"
  chinese "%s"

ER_IB_MSG_601
  eng "%s"
  chinese "%s"

ER_IB_MSG_602
  eng "%s"
  chinese "%s"

ER_IB_MSG_603
  eng "%s"
  chinese "%s"

ER_IB_MSG_604
  eng "%s"
  chinese "%s"

ER_IB_MSG_605
  eng "%s"
  chinese "%s"

ER_IB_MSG_606
  eng "%s"
  chinese "%s"

ER_IB_MSG_607
  eng "%s"
  chinese "%s"

ER_IB_MSG_608
  eng "%s"
  chinese "%s"

ER_IB_MSG_609
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_610
  eng "%s"
  chinese "%s"

ER_IB_MSG_611
  eng "%s"
  chinese "%s"

ER_IB_MSG_612
  eng "%s"
  chinese "%s"

ER_IB_MSG_613
  eng "%s"
  chinese "%s"

ER_IB_MSG_614
  eng "%s"
  chinese "%s"

ER_IB_MSG_615
  eng "%s"
  chinese "%s"

ER_IB_MSG_616
  eng "%s"
  chinese "%s"

ER_IB_MSG_617
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_618
  eng "%s"
  chinese "%s"

ER_IB_MSG_619
  eng "%s"
  chinese "%s"

ER_IB_MSG_IBUF_CURSOR_RESTORATION_FAILED
  eng "ibuf cursor restoration fails!. ibuf record inserted to page %s:%s"

OBSOLETE_ER_IB_MSG_621
  eng "%s"
  chinese "%s"

ER_IB_MSG_IBUF_FAILED_TO_RESTORE_POSITION
  eng "Failed to restore ibuf position."

ER_IB_MSG_623
  eng "%s"
  chinese "%s"

ER_IB_MSG_624
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_625
  eng "%s"
  chinese "%s"

ER_IB_MSG_626
  eng "%s"
  chinese "%s"

ER_IB_MSG_627
  eng "%s"
  chinese "%s"

ER_IB_MSG_628
  eng "%s"
  chinese "%s"

ER_IB_MSG_629
  eng "%s"
  chinese "%s"

ER_IB_MSG_630
  eng "%s"
  chinese "%s"

ER_IB_MSG_631
  eng "%s"
  chinese "%s"

ER_IB_MSG_632
  eng "%s"
  chinese "%s"

ER_IB_MSG_633
  eng "%s"
  chinese "%s"

ER_IB_MSG_634
  eng "%s"
  chinese "%s"

ER_IB_MSG_635
  eng "%s"
  chinese "%s"

ER_IB_MSG_636
  eng "Blocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s)."
  chinese "阻止的高优先级事务(ID %llu,线程ID %s)强制回滚正在阻止的事务(ID %llu - %s)。"

ER_IB_MSG_637
  eng "%s"
  chinese "%s"

ER_IB_MSG_638
  eng "%s"
  chinese "%s"

ER_IB_MSG_639
  eng "Blocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim."
  chinese "阻止高优先级事务(线程ID %s)通过假装它是死锁牺牲品来唤醒正在阻止的事务(ID %llu)。"

OBSOLETE_ER_IB_MSG_640
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_641
  eng "%s"
  chinese "%s"

ER_IB_MSG_642
  eng "%s"
  chinese "%s"

ER_IB_MSG_643
  eng "%s"
  chinese "%s"

ER_IB_MSG_644
  eng "%s"
  chinese "%s"

ER_IB_MSG_645
  eng "%s"
  chinese "%s"

ER_IB_MSG_646
  eng "%s"
  chinese "%s"

ER_IB_MSG_647
  eng "%s"
  chinese "%s"

ER_IB_MSG_648
  eng "%s"
  chinese "%s"

ER_IB_MSG_649
  eng "%s"
  chinese "%s"

ER_IB_MSG_650
  eng "%s"
  chinese "%s"

ER_IB_MSG_651
  eng "%s"
  chinese "%s"

ER_IB_MSG_652
  eng "%s"
  chinese "%s"

ER_IB_MSG_DDL_LOG_DELETE_BY_ID_OK
  eng "%s"
  chinese "%s"

ER_IB_MSG_654
  eng "%s"
  chinese "%s"

ER_IB_MSG_655
  eng "%s"
  chinese "%s"

ER_IB_MSG_656
  eng "%s"
  chinese "%s"

ER_IB_MSG_657
  eng "%s"
  chinese "%s"

ER_IB_MSG_658
  eng "%s"
  chinese "%s"

ER_IB_MSG_659
  eng "%s"
  chinese "%s"

ER_IB_MSG_660
  eng "%s"
  chinese "%s"

ER_IB_MSG_661
  eng "%s"
  chinese "%s"

ER_IB_MSG_662
  eng "%s"
  chinese "%s"

ER_IB_MSG_663
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_664
  eng "The transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it."
  chinese "事务日志大小对于Innodb_LOG_BUFFER_SIZE(%lu>=%lu/2)太大。正在尝试扩展它。"

OBSOLETE_ER_IB_MSG_665
  eng "innodb_log_buffer_size was extended to %lu bytes."
  chinese "Innodb_LOG_BUFFER_SIZE已扩展到%lu字节。"

OBSOLETE_ER_IB_MSG_666
  eng "The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu."
  chinese "事务日志文件对于单个事务日志(大小=%lu)来说太小。因此,最后一个检查点期限可能超过日志组容量%llu。"

OBSOLETE_ER_IB_MSG_667
  eng "The age of the last checkpoint is %llu, which exceeds the log group capacity %llu."
  chinese "最后一个检查点的时间为%llu,超过了日志组容量%llu。"

OBSOLETE_ER_IB_MSG_668
  eng "Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %s"
  chinese "无法继续操作。ib_log文件对于Innodb_ThREAD_CONTURRENCE%lu太小。ib_LOGFILES的总大小应大于200 kB*Innodb_THREAD_CONTURREY。若要启动mysqld,请将my.cnf中的INNODB_THREAD_CONTURRENCY设置为一个较小的值,例如,设置为8。在正确关闭mysqld后,您可以调整ib_LOGFILES的大小。%s"

OBSOLETE_ER_IB_MSG_669
  eng "Redo log was encrypted, but keyring plugin is not loaded."
  chinese "重做日志已加密,但未加载密钥环插件。"

OBSOLETE_ER_IB_MSG_670
  eng "Read redo log encryption metadata successful."
  chinese "成功读取重做日志加密元数据。"

OBSOLETE_ER_IB_MSG_671
  eng "Can't set redo log tablespace encryption metadata."
  chinese "无法设置重做日志表空间加密元数据。"

OBSOLETE_ER_IB_MSG_672
  eng "Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists."
  chinese "无法读取日志文件头中的加密信息,请检查是否已加载密钥环插件以及密钥文件是否存在。"

OBSOLETE_ER_IB_MSG_673
  eng "Can't set redo log tablespace to be encrypted in read-only mode."
  chinese "无法将重做日志表空间设置为以只读模式加密。"

OBSOLETE_ER_IB_MSG_674
  eng "Can't set redo log tablespace to be encrypted."
  chinese "无法将重做日志表空间设置为加密。"

OBSOLETE_ER_IB_MSG_675
  eng "Can't set redo log tablespace to be encrypted."
  chinese "无法将重做日志表空间设置为加密。"

OBSOLETE_ER_IB_MSG_676
  eng "Redo log encryption is enabled."
  chinese "已启用重做日志加密。"

OBSOLETE_ER_IB_MSG_677
  eng "Flush waiting for archiver to catch up lag LSN: %llu"
  chinese "刷新正在等待存档程序追上延迟LSN:%llu"

OBSOLETE_ER_IB_MSG_678
  eng "Flush overwriting data to archive - wait too long (1 minute) lag LSN: %llu"
  chinese "刷新覆盖数据以存档-等待太长时间(1分钟)延迟LSN:%llu"

OBSOLETE_ER_IB_MSG_679
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_680
  eng "Starting shutdown..."
  chinese "正在开始关机..."

OBSOLETE_ER_IB_MSG_681
  eng "Waiting for %s to exit"
  chinese "正在等待%s退出"

OBSOLETE_ER_IB_MSG_682
  eng "Waiting for %lu active transactions to finish"
  chinese "正在等待%lu个活动事务完成"

OBSOLETE_ER_IB_MSG_683
  eng "Waiting for master thread to be suspended"
  chinese "正在等待挂起主线程"

OBSOLETE_ER_IB_MSG_684
  eng "Waiting for page_cleaner to finish flushing of buffer pool"
  chinese "正在等待PAGE_CLENER完成缓冲池刷新"

OBSOLETE_ER_IB_MSG_685
  eng "Pending checkpoint_writes: %lu. Pending log flush writes: %lu."
  chinese "挂起的CHECKPOINT_WRITS:%lu。挂起的日志刷新写入:%lu。"

OBSOLETE_ER_IB_MSG_686
  eng "Waiting for %lu buffer page I/Os to complete"
  chinese "正在等待%lu缓冲区页面I/O完成"

OBSOLETE_ER_IB_MSG_687
  eng "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!"
  chinese "MySQL已请求快速关闭,而无需将InnoDB缓冲池刷新到数据文件。在下一次mysqld启动时,InnoDB将执行崩溃恢复！"

OBSOLETE_ER_IB_MSG_688
  eng "Background thread %s woke up during shutdown"
  chinese "后台线程%s在关闭期间被唤醒"

OBSOLETE_ER_IB_MSG_689
  eng "Waiting for archiver to finish archiving page and log"
  chinese "正在等待存档程序完成存档页面和日志"

OBSOLETE_ER_IB_MSG_690
  eng "Background thread %s woke up during shutdown"
  chinese "后台线程%s在关闭期间被唤醒"

OBSOLETE_ER_IB_MSG_691
  eng "Waiting for dirty buffer pages to be flushed"
  chinese "正在等待刷新脏缓冲区页"

OBSOLETE_ER_IB_MSG_692
  eng "Log sequence number at shutdown %llu is lower than at startup %llu!"
  chinese "关闭%llu时的日志序列号低于启动时的%llu！"

OBSOLETE_ER_IB_MSG_693
  eng "Waiting for archiver to finish archiving page and log"
  chinese "正在等待存档程序完成存档页面和日志"

ER_IB_MSG_694
  eng "############### CORRUPT LOG RECORD FOUND ###############"
  chinese "############### 找到损坏的日志记录 ###############"

ER_IB_MSG_695
  eng "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"
  chinese "日志记录类型%d,页%lu:%lu。日志分析已成功进行到%llu。上一个日志记录类型%d,是多个%llu接收偏移量%zd,上一个%llu"

ER_IB_MSG_696
  eng "Hex dump starting %llu bytes before and ending %llu bytes after the corrupted record:"
  chinese "十六进制转储在损坏的记录之前开始%llu字节,在损坏记录之后结束%llu字节:"

ER_IB_MSG_697
  eng "Set innodb_force_recovery to ignore this error."
  chinese "设置Innodb_force_Recovery以忽略此错误。"

ER_IB_MSG_LOG_CORRUPT
  eng "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"
  chinese "重做日志文件可能已损坏,可能是日志扫描在恢复过程中进行得不够深入！请在InnoDB表上运行CHECK TABLE以检查它们是否正常！如果mysqld在此恢复后崩溃；%s"

ER_IB_MSG_699
  eng "%llu pages with log records were left unprocessed!"
  chinese "%llu个包含日志记录的页面未处理！"

ER_IB_MSG_LOG_FORMAT_OLD_AND_LOG_CORRUPTED
  eng "Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %s"
  chinese "不支持崩溃后升级。此重做日志是用%s创建的,它似乎已损坏。请按照%s上的说明进行操作"

ER_IB_MSG_LOG_FORMAT_OLD_AND_NO_CLEAN_SHUTDOWN
  eng "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 %s"
  chinese "在INNODB_FAST_SHUTDOWN=2的崩溃或关机后不支持升级。此重做日志是用%s创建的,从逻辑上看它不是空的。请按照%s的说明操作。"

OBSOLETE_ER_IB_MSG_702
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_703
  eng "%s"
  chinese "%s"

ER_IB_MSG_LOG_FORMAT_BEFORE_8_0_30
  eng "Redo log format is v%lu. The redo log was created before MySQL 8.0.30."
  chinese "重做日志格式为v%lu。重做日志是在MySQL 8.0.30之前创建的。"

ER_IB_MSG_LOG_FILE_FORMAT_UNKNOWN
  eng "Unknown redo log format (v%lu) in file %s. Please follow the instructions at %s"
  chinese "未知的重做日志格式(v%lu)(在文件%s中)。请按照%s中的说明操作"

ER_IB_MSG_RECOVERY_CHECKPOINT_NOT_FOUND
  eng "No valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort."
  chinese "找不到有效的检查点(重做日志已损坏)。您可以尝试--Innodb-force-Recovery=6作为最后手段。"

ER_IB_MSG_707
  eng "Applying a batch of %llu redo log records ..."
  chinese "正在应用批%llu重做日志记录..."

ER_IB_MSG_708
  eng "%s"
  chinese "%s"

ER_IB_MSG_709
  eng "%s"
  chinese "%s"

ER_IB_MSG_710
  eng "Apply batch completed!"
  chinese "应用批处理已完成！"

ER_IB_MSG_711
  eng "%s"
  chinese "%s"

ER_IB_MSG_712
  eng "%s"
  chinese "%s"

ER_IB_MSG_713
  eng "%s"
  chinese "%s"

ER_IB_MSG_714
  eng "%s"
  chinese "%s"

ER_IB_MSG_715
  eng "%s"
  chinese "%s"

ER_IB_MSG_716
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_717
  eng "An optimized (without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet. This offline backup may not be consistent."
  chinese "已执行优化的(没有重做日志记录)DDL操作。可能尚未将所有修改的页刷新到磁盘。此脱机备份可能不一致"

ER_IB_MSG_718
  eng "Extending tablespace : %lu space name: %s to new size: %lu pages during recovery."
  chinese "在恢复过程中将表空间:%lu空间名称:%s扩展到新大小:%lu页。"

ER_IB_MSG_719
  eng "Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery."
  chinese "在恢复过程中,无法将表空间:%lu空间名称:%s扩展到新大小:%lu页。"

ER_IB_MSG_720
  eng "Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu."
  chinese "LSN日志块%lu在%llu处的具有有效标头,但校验和字段包含%lu,应为%lu。"

ER_IB_MSG_RECOVERY_SKIPPED_IN_READ_ONLY_MODE
  eng "Skipped necessary redo log applying, --innodb-read-only set!"
  chinese "已跳过恢复,--Innodb-read-only设置！"

ER_IB_MSG_722
  eng "Log scan progressed past the checkpoint LSN %llu."
  chinese "日志扫描已超过检查点LSN%llu。"

ER_IB_MSG_723
  eng "Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu."
  chinese "日志分析缓冲区溢出。恢复可能已失败！请将LOG_BUFFER_SIZE设置为大于%lu的值。"

ER_IB_MSG_724
  eng "Set innodb_force_recovery to ignore this error."
  chinese "将Innodb_force_Recovery设置为忽略此错误。"

ER_IB_MSG_725
  eng "Doing recovery: scanned up to log sequence number %llu"
  chinese "正在执行恢复:已向上扫描到日志序列号%llu"

ER_IB_MSG_726
  eng "Database was not shutdown normally!"
  chinese "数据库未正常关闭！"

ER_IB_MSG_727
  eng "Starting crash recovery."
  chinese "开始崩溃恢复。"

ER_IB_MSG_728
  eng "The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redo"
  chinese "用户已将SRV_FORCE_NO_LOG_REDO设置为ON,跳过日志重做"

ER_IB_MSG_LOG_FILES_CREATED_BY_MEB_AND_READ_ONLY_MODE
  eng "Cannot restore from mysqlbackup, InnoDB running in read-only mode!"
  chinese "无法从以只读模式运行的mySQlBackup、InnoDB还原！"

ER_IB_MSG_LOG_FILES_CREATED_BY_MEB
  eng "The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore."
  chinese "重做日志文件是由mySQLBACKUP--APPLY-LOG在%s创建的。以下崩溃恢复是正常恢复的一部分。"

ER_IB_MSG_LOG_FILES_CREATED_BY_CLONE
  eng "Opening cloned database"
  chinese "打开克隆数据库"

ER_IB_MSG_LOG_FORMAT_OLD
  eng "Redo log is from an earlier version, v%lu."
  chinese "重做日志来自较早版本v%lu。"

OBSOLETE_ER_IB_MSG_LOG_FORMAT_NOT_SUPPORTED
  eng "Redo log format v%lu not supported. Current supported format is v%lu."
  chinese "不支持重做日志格式v%lu。当前支持的格式是v%lu。"

ER_IB_MSG_RECOVERY_CHECKPOINT_FROM_BEFORE_CLEAN_SHUTDOWN
  eng "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."
  chinese "是否确实使用正确的重做日志文件启动数据库？重做日志文件中的日志序列号为%llu,小于第一个系统表空间文件头%llu中的日志序列号。"

ER_IB_MSG_RECOVERY_IS_NEEDED
  eng "The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!"
  chinese "SYSTEM表空间中的日志序列号%llu与重做日志文件中的日志序列号%llu不匹配！"

ER_IB_MSG_RECOVERY_IN_READ_ONLY
  eng "Can't initiate database recovery, running in read-only-mode."
  chinese "无法启动数据库恢复,正在以只读模式运行。"

ER_IB_MSG_737
  eng "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!"
  chinese "我们扫描的日志最多为%llu。检查点位于%llu,数据库页上的最大LSN为%llu。数据库现在可能已损坏！"

ER_IB_MSG_738
  eng "Waiting for recv_writer to finish flushing of buffer pool"
  chinese "正在等待recv_Writer完成缓冲池刷新"

ER_IB_MSG_739
  eng "Recovery parsing buffer extended to %zu."
  chinese "恢复解析缓冲区已扩展到%zu。"

ER_IB_MSG_740
  eng "Out of memory while resizing recovery parsing buffer."
  chinese "调整恢复解析缓冲区大小时内存不足。"

ER_IB_MSG_741
  eng "%s"
  chinese "%s"

ER_IB_MSG_742
  eng "%s"
  chinese "%s"

ER_IB_MSG_743
  eng "%s"
  chinese "%s"

ER_IB_MSG_744
  eng "%s"
  chinese "%s"

ER_IB_MSG_745
  eng "%s"
  chinese "%s"

ER_IB_MSG_746
  eng "%s"
  chinese "%s"

ER_IB_MSG_747
  eng "%s"
  chinese "%s"

ER_IB_MSG_748
  eng "%s"
  chinese "%s"

ER_IB_MSG_749
  eng "%s"
  chinese "%s"

ER_IB_MSG_750
  eng "%s"
  chinese "%s"

ER_IB_MSG_751
  eng "%s"
  chinese "%s"

ER_IB_MSG_752
  eng "%s"
  chinese "%s"

ER_IB_MSG_753
  eng "%s"
  chinese "%s"

ER_IB_MSG_754
  eng "%s"
  chinese "%s"

ER_IB_MSG_755
  eng "%s"
  chinese "%s"

ER_IB_MSG_756
  eng "%s"
  chinese "%s"

ER_IB_MSG_757
  eng "%s"
  chinese "%s"

ER_IB_MSG_758
  eng "%s"
  chinese "%s"

ER_IB_MSG_759
  eng "%s"
  chinese "%s"

ER_IB_MSG_760
  eng "%s"
  chinese "%s"

ER_IB_MSG_761
  eng "%s"
  chinese "%s"

ER_IB_MSG_762
  eng "%s"
  chinese "%s"

ER_IB_MSG_763
  eng "%s"
  chinese "%s"

ER_IB_MSG_764
  eng "%s"
  chinese "%s"

ER_IB_MSG_765
  eng "%s"
  chinese "%s"

ER_IB_MSG_766
  eng "%s"
  chinese "%s"

ER_IB_MSG_767
  eng "%s"
  chinese "%s"

ER_IB_MSG_768
  eng "%s"
  chinese "%s"

ER_IB_MSG_769
  eng "%s"
  chinese "%s"

ER_IB_MSG_770
  eng "%s"
  chinese "%s"

ER_IB_MSG_771
  eng "%s"
  chinese "%s"

ER_IB_MSG_772
  eng "%s"
  chinese "%s"

ER_IB_MSG_773
  eng "%s"
  chinese "%s"

ER_IB_MSG_774
  eng "%s"
  chinese "%s"

ER_IB_MSG_775
  eng "%s"
  chinese "%s"

ER_IB_MSG_776
  eng "%s"
  chinese "%s"

ER_IB_MSG_777
  eng "%s"
  chinese "%s"

ER_IB_MSG_778
  eng "%s"
  chinese "%s"

ER_IB_MSG_779
  eng "%s"
  chinese "%s"

ER_IB_MSG_780
  eng "%s"
  chinese "%s"

ER_IB_MSG_781
  eng "%s"
  chinese "%s"

ER_IB_MSG_782
  eng "%s"
  chinese "%s"

ER_IB_MSG_783
  eng "%s"
  chinese "%s"

ER_IB_MSG_784
  eng "%s"
  chinese "%s"

ER_IB_MSG_785
  eng "%s"
  chinese "%s"

ER_IB_MSG_786
  eng "%s"
  chinese "%s"

ER_IB_MSG_787
  eng "%s"
  chinese "%s"

ER_IB_MSG_788
  eng "%s"
  chinese "%s"

ER_IB_MSG_789
  eng "%s"
  chinese "%s"

ER_IB_MSG_790
  eng "%s"
  chinese "%s"

ER_IB_MSG_791
  eng "%s"
  chinese "%s"

ER_IB_MSG_792
  eng "%s"
  chinese "%s"

ER_IB_MSG_793
  eng "%s"
  chinese "%s"

ER_IB_MSG_794
  eng "%s"
  chinese "%s"

ER_IB_MSG_795
  eng "%s"
  chinese "%s"

ER_IB_MSG_796
  eng "%s"
  chinese "%s"

ER_IB_MSG_797
  eng "%s"
  chinese "%s"

ER_IB_MSG_798
  eng "%s"
  chinese "%s"

ER_IB_MSG_799
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_800
  eng "%s"
  chinese "%s"

ER_IB_MSG_801
  eng "%s"
  chinese "%s"

ER_IB_MSG_802
  eng "%s"
  chinese "%s"

ER_IB_MSG_803
  eng "%s"
  chinese "%s"

ER_IB_MSG_804
  eng "%s"
  chinese "%s"

ER_IB_MSG_805
  eng "%s"
  chinese "%s"

ER_IB_MSG_806
  eng "%s"
  chinese "%s"

ER_IB_MSG_807
  eng "%s"
  chinese "%s"

ER_IB_MSG_808
  eng "%s"
  chinese "%s"

ER_IB_MSG_809
  eng "%s"
  chinese "%s"

ER_IB_MSG_810
  eng "%s"
  chinese "%s"

ER_IB_MSG_811
  eng "%s"
  chinese "%s"

ER_IB_MSG_812
  eng "%s"
  chinese "%s"

ER_IB_MSG_813
  eng "%s"
  chinese "%s"

ER_IB_MSG_814
  eng "%s"
  chinese "%s"

ER_IB_MSG_815
  eng "%s"
  chinese "%s"

ER_IB_MSG_816
  eng "%s"
  chinese "%s"

ER_IB_MSG_817
  eng "%s"
  chinese "%s"

ER_IB_MSG_818
  eng "%s"
  chinese "%s"

ER_IB_MSG_819
  eng "%s"
  chinese "%s"

ER_IB_MSG_820
  eng "%s"
  chinese "%s"

ER_IB_MSG_821
  eng "%s"
  chinese "%s"

ER_IB_MSG_822
  eng "%s"
  chinese "%s"

ER_IB_MSG_823
  eng "%s"
  chinese "%s"

ER_IB_MSG_824
  eng "%s"
  chinese "%s"

ER_IB_MSG_825
  eng "%s"
  chinese "%s"

ER_IB_MSG_826
  eng "%s"
  chinese "%s"

ER_IB_MSG_827
  eng "%s"
  chinese "%s"

ER_IB_MSG_828
  eng "%s"
  chinese "%s"

ER_IB_MSG_829
  eng "%s"
  chinese "%s"

ER_IB_MSG_830
  eng "%s"
  chinese "%s"

ER_IB_MSG_831
  eng "%s"
  chinese "%s"

ER_IB_MSG_832
  eng "%s"
  chinese "%s"

ER_IB_MSG_833
  eng "%s"
  chinese "%s"

ER_IB_MSG_834
  eng "%s"
  chinese "%s"

ER_IB_MSG_835
  eng "%s"
  chinese "%s"

ER_IB_MSG_836
  eng "%s"
  chinese "%s"

ER_IB_MSG_837
  eng "%s"
  chinese "%s"

ER_IB_MSG_838
  eng "%s"
  chinese "%s"

ER_IB_MSG_839
  eng "%s"
  chinese "%s"

ER_IB_MSG_840
  eng "%s"
  chinese "%s"

ER_IB_MSG_841
  eng "%s"
  chinese "%s"

ER_IB_MSG_842
  eng "%s"
  chinese "%s"

ER_IB_MSG_CANT_ENCRYPT_REDO_LOG_DATA
  eng "Can't encrypt data of redo log"

ER_IB_MSG_844
  eng "%s"
  chinese "%s"

ER_IB_MSG_845
  eng "%s"
  chinese "%s"

ER_IB_MSG_CANT_DECRYPT_REDO_LOG
  eng "Decryption of redo log block at offset %llu in file %s failed because there's no keyring configured"

ER_IB_MSG_847
  eng "%s"
  chinese "%s"

ER_IB_MSG_848
  eng "%s"
  chinese "%s"

ER_IB_MSG_849
  eng "%s"
  chinese "%s"

ER_IB_MSG_850
  eng "%s"
  chinese "%s"

ER_IB_MSG_851
  eng "%s"
  chinese "%s"

ER_IB_MSG_852
  eng "%s"
  chinese "%s"

ER_IB_MSG_853
  eng "%s"
  chinese "%s"

ER_IB_MSG_854
  eng "%s"
  chinese "%s"

ER_IB_MSG_855
  eng "%s"
  chinese "%s"

ER_IB_MSG_856
  eng "%s"
  chinese "%s"

ER_IB_MSG_857
  eng "%s"
  chinese "%s"

ER_IB_MSG_858
  eng "%s"
  chinese "%s"

ER_IB_MSG_859
  eng "%s"
  chinese "%s"

ER_IB_MSG_860
  eng "%s"
  chinese "%s"

ER_IB_MSG_861
  eng "%s"
  chinese "%s"

ER_IB_MSG_862
  eng "%s"
  chinese "%s"

ER_IB_MSG_863
  eng "%s"
  chinese "%s"

ER_IB_MSG_864
  eng "%s"
  chinese "%s"

ER_IB_MSG_865
  eng "%s"
  chinese "%s"

ER_IB_MSG_866
  eng "%s"
  chinese "%s"

ER_IB_MSG_867
  eng "%s"
  chinese "%s"

ER_IB_MSG_868
  eng "%s"
  chinese "%s"

ER_IB_MSG_869
  eng "%s"
  chinese "%s"

ER_IB_MSG_870
  eng "%s"
  chinese "%s"

ER_IB_MSG_871
  eng "%s"
  chinese "%s"

ER_IB_MSG_872
  eng "%s"
  chinese "%s"

ER_IB_MSG_873
  eng "%s"
  chinese "%s"

ER_IB_MSG_874
  eng "%s"
  chinese "%s"

ER_IB_MSG_875
  eng "%s"
  chinese "%s"

ER_IB_MSG_876
  eng "%s"
  chinese "%s"

ER_IB_MSG_877
  eng "%s"
  chinese "%s"

ER_IB_MSG_878
  eng "%s"
  chinese "%s"

ER_IB_MSG_879
  eng "%s"
  chinese "%s"

ER_IB_MSG_880
  eng "%s"
  chinese "%s"

ER_IB_MSG_881
  eng "%s"
  chinese "%s"

ER_IB_MSG_882
  eng "%s"
  chinese "%s"

ER_IB_MSG_883
  eng "%s"
  chinese "%s"

ER_IB_MSG_884
  eng "%s"
  chinese "%s"

ER_IB_MSG_885
  eng "%s"
  chinese "%s"

ER_IB_MSG_886
  eng "%s"
  chinese "%s"

ER_IB_MSG_887
  eng "%s"
  chinese "%s"

ER_IB_MSG_888
  eng "%s"
  chinese "%s"

ER_IB_MSG_889
  eng "%s"
  chinese "%s"

ER_IB_MSG_890
  eng "%s"
  chinese "%s"

ER_IB_MSG_891
  eng "%s"
  chinese "%s"

ER_IB_MSG_892
  eng "%s"
  chinese "%s"

ER_IB_MSG_893
  eng "%s"
  chinese "%s"

ER_IB_MSG_894
  eng "%s"
  chinese "%s"

ER_IB_MSG_895
  eng "%s"
  chinese "%s"

ER_IB_MSG_896
  eng "%s"
  chinese "%s"

ER_IB_MSG_897
  eng "%s"
  chinese "%s"

ER_IB_MSG_898
  eng "%s"
  chinese "%s"

ER_IB_MSG_899
  eng "%s"
  chinese "%s"

ER_IB_MSG_900
  eng "%s"
  chinese "%s"

ER_IB_MSG_901
  eng "%s"
  chinese "%s"

ER_IB_MSG_902
  eng "%s"
  chinese "%s"

ER_IB_MSG_903
  eng "%s"
  chinese "%s"

ER_IB_MSG_904
  eng "%s"
  chinese "%s"

ER_IB_MSG_905
  eng "%s"
  chinese "%s"

ER_IB_MSG_906
  eng "%s"
  chinese "%s"

ER_IB_MSG_907
  eng "%s"
  chinese "%s"

ER_IB_MSG_908
  eng "%s"
  chinese "%s"

ER_IB_MSG_909
  eng "%s"
  chinese "%s"

ER_IB_MSG_910
  eng "%s"
  chinese "%s"

ER_IB_MSG_911
  eng "%s"
  chinese "%s"

ER_IB_MSG_912
  eng "%s"
  chinese "%s"

ER_IB_MSG_913
  eng "%s"
  chinese "%s"

ER_IB_MSG_914
  eng "%s"
  chinese "%s"

ER_IB_MSG_915
  eng "%s"
  chinese "%s"

ER_IB_MSG_916
  eng "%s"
  chinese "%s"

ER_IB_MSG_917
  eng "%s"
  chinese "%s"

ER_IB_MSG_918
  eng "%s"
  chinese "%s"

ER_IB_MSG_919
  eng "%s"
  chinese "%s"

ER_IB_MSG_920
  eng "%s"
  chinese "%s"

ER_IB_MSG_921
  eng "%s"
  chinese "%s"

ER_IB_MSG_922
  eng "%s"
  chinese "%s"

ER_IB_MSG_923
  eng "%s"
  chinese "%s"

ER_IB_MSG_924
  eng "%s"
  chinese "%s"

ER_IB_MSG_925
  eng "%s"
  chinese "%s"

ER_IB_MSG_926
  eng "%s"
  chinese "%s"

ER_IB_MSG_927
  eng "%s"
  chinese "%s"

ER_IB_MSG_928
  eng "%s"
  chinese "%s"

ER_IB_MSG_929
  eng "%s"
  chinese "%s"

ER_IB_MSG_930
  eng "%s"
  chinese "%s"

ER_IB_MSG_931
  eng "%s"
  chinese "%s"

ER_IB_MSG_932
  eng "%s"
  chinese "%s"

ER_IB_MSG_933
  eng "%s"
  chinese "%s"

ER_IB_MSG_934
  eng "%s"
  chinese "%s"

ER_IB_MSG_935
  eng "%s"
  chinese "%s"

ER_IB_MSG_936
  eng "%s"
  chinese "%s"

ER_IB_MSG_937
  eng "%s"
  chinese "%s"

ER_IB_MSG_938
  eng "%s"
  chinese "%s"

ER_IB_MSG_939
  eng "%s"
  chinese "%s"

ER_IB_MSG_940
  eng "%s"
  chinese "%s"

ER_IB_MSG_941
  eng "%s"
  chinese "%s"

ER_IB_MSG_942
  eng "%s"
  chinese "%s"

ER_IB_MSG_943
  eng "%s"
  chinese "%s"

ER_IB_MSG_944
  eng "%s"
  chinese "%s"

ER_IB_MSG_945
  eng "%s"
  chinese "%s"

ER_IB_MSG_946
  eng "%s"
  chinese "%s"

ER_IB_IMPORT_INDEX_METADATA_READ_FAILED
  eng "IO Error: %s"

ER_IB_MSG_948
  eng "%s"
  chinese "%s"

ER_IB_MSG_949
  eng "%s"
  chinese "%s"

ER_IB_MSG_950
  eng "%s"
  chinese "%s"

ER_IB_MSG_951
  eng "%s"
  chinese "%s"

ER_IB_MSG_952
  eng "%s"
  chinese "%s"

ER_IB_MSG_953
  eng "%s"
  chinese "%s"

ER_IB_MSG_954
  eng "%s"
  chinese "%s"

ER_IB_MSG_955
  eng "%s"
  chinese "%s"

ER_IB_MSG_956
  eng "%s"
  chinese "%s"

ER_IB_MSG_957
  eng "%s"
  chinese "%s"

ER_IB_MSG_958
  eng "%s"
  chinese "%s"

ER_IB_MSG_959
  eng "%s"
  chinese "%s"

ER_IB_MSG_960
  eng "%s"
  chinese "%s"

ER_IB_MSG_961
  eng "%s"
  chinese "%s"

ER_IB_MSG_962
  eng "%s"
  chinese "%s"

ER_IB_MSG_963
  eng "%s"
  chinese "%s"

ER_IB_MSG_964
  eng "%s"
  chinese "%s"

ER_IB_MSG_965
  eng "%s"
  chinese "%s"

ER_IB_MSG_966
  eng "%s"
  chinese "%s"

ER_IB_MSG_967
  eng "%s"
  chinese "%s"

ER_IB_MSG_968
  eng "%s"
  chinese "%s"

ER_IB_MSG_969
  eng "%s"
  chinese "%s"

ER_IB_MSG_970
  eng "%s"
  chinese "%s"

ER_IB_MSG_971
  eng "%s"
  chinese "%s"

ER_IB_MSG_972
  eng "%s"
  chinese "%s"

ER_IB_MSG_973
  eng "%s"
  chinese "%s"

ER_IB_MSG_974
  eng "%s"
  chinese "%s"

ER_IB_MSG_975
  eng "%s"
  chinese "%s"

ER_IB_MSG_976
  eng "%s"
  chinese "%s"

ER_IB_MSG_977
  eng "%s"
  chinese "%s"

ER_IB_MSG_978
  eng "%s"
  chinese "%s"

ER_IB_MSG_979
  eng "%s"
  chinese "%s"

ER_IB_MSG_980
  eng "%s"
  chinese "%s"

ER_IB_MSG_981
  eng "%s"
  chinese "%s"

ER_IB_MSG_982
  eng "%s"
  chinese "%s"

ER_IB_MSG_983
  eng "%s"
  chinese "%s"

ER_IB_MSG_984
  eng "%s"
  chinese "%s"

ER_IB_MSG_985
  eng "%s"
  chinese "%s"

ER_IB_MSG_986
  eng "%s"
  chinese "%s"

ER_IB_MSG_987
  eng "%s"
  chinese "%s"

ER_IB_MSG_988
  eng "%s"
  chinese "%s"

ER_IB_MSG_989
  eng "%s"
  chinese "%s"

ER_IB_MSG_990
  eng "%s"
  chinese "%s"

ER_IB_MSG_991
  eng "%s"
  chinese "%s"

ER_IB_MSG_992
  eng "%s"
  chinese "%s"

ER_IB_MSG_993
  eng "%s"
  chinese "%s"

ER_IB_MSG_994
  eng "%s"
  chinese "%s"

ER_IB_MSG_995
  eng "%s"
  chinese "%s"

ER_IB_MSG_996
  eng "%s"
  chinese "%s"

ER_IB_MSG_997
  eng "%s"
  chinese "%s"

ER_IB_MSG_998
  eng "%s"
  chinese "%s"

ER_IB_MSG_999
  eng "%s"
  chinese "%s"

ER_IB_MSG_1000
  eng "%s"
  chinese "%s"

ER_IB_MSG_1001
  eng "%s"
  chinese "%s"

ER_IB_MSG_1002
  eng "%s"
  chinese "%s"

ER_IB_MSG_1003
  eng "%s"
  chinese "%s"

ER_IB_MSG_1004
  eng "%s"
  chinese "%s"

ER_IB_MSG_1005
  eng "%s"
  chinese "%s"

ER_IB_MSG_1006
  eng "%s"
  chinese "%s"

ER_IB_MSG_1007
  eng "%s"
  chinese "%s"

ER_IB_MSG_1008
  eng "%s"
  chinese "%s"

ER_IB_MSG_1009
  eng "%s"
  chinese "%s"

ER_IB_MSG_1010
  eng "%s"
  chinese "%s"

ER_IB_MSG_1011
  eng "%s"
  chinese "%s"

ER_IB_MSG_1012
  eng "%s"
  chinese "%s"

ER_IB_MSG_1013
  eng "%s"
  chinese "%s"

ER_IB_IMPORT_START_CFG_NAME
  eng "Writing table metadata to '%s'"

ER_IB_MSG_1015
  eng "%s"
  chinese "%s"

ER_IB_MSG_1016
  eng "%s"
  chinese "%s"

ER_IB_MSG_1017
  eng "%s"
  chinese "%s"

ER_IB_MSG_1018
  eng "%s"
  chinese "%s"

ER_IB_MSG_1019
  eng "%s"
  chinese "%s"

ER_IB_MSG_1020
  eng "%s"
  chinese "%s"

ER_IB_MSG_1021
  eng "%s"
  chinese "%s"

ER_IB_MSG_1022
  eng "%s"
  chinese "%s"

ER_IB_MSG_1023
  eng "%s"
  chinese "%s"

ER_IB_MSG_1024
  eng "%s"
  chinese "%s"

ER_IB_MSG_1025
  eng "%s"
  chinese "%s"

ER_IB_MSG_1026
  eng "%s"
  chinese "%s"

ER_IB_MSG_1027
  eng "%s"
  chinese "%s"

ER_IB_MSG_1028
  eng "%s"
  chinese "%s"

ER_IB_MSG_1029
  eng "%s"
  chinese "%s"

ER_IB_MSG_1030
  eng "%s"
  chinese "%s"

ER_IB_MSG_1031
  eng "%s"
  chinese "%s"

ER_IB_MSG_1032
  eng "%s"
  chinese "%s"

ER_IB_MSG_1033
  eng "%s"
  chinese "%s"

ER_IB_MSG_1034
  eng "%s"
  chinese "%s"

ER_IB_MSG_1035
  eng "%s"
  chinese "%s"

ER_IB_MSG_1036
  eng "%s"
  chinese "%s"

ER_IB_MSG_1037
  eng "%s"
  chinese "%s"

ER_IB_MSG_1038
  eng "%s"
  chinese "%s"

ER_IB_MSG_1039
  eng "%s"
  chinese "%s"

ER_IB_MSG_1040
  eng "%s"
  chinese "%s"

ER_IB_MSG_1041
  eng "%s"
  chinese "%s"

ER_IB_MSG_1042
  eng "%s"
  chinese "%s"

ER_IB_MSG_1043
  eng "%s"
  chinese "%s"

ER_IB_MSG_1044
  eng "%s"
  chinese "%s"

ER_IB_MSG_1045
  eng "%s"
  chinese "%s"

ER_IB_MSG_1046
  eng "Old log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.com"
  chinese "旧日志序列号%llu大于新日志序列号%llu。请向 http://bugs.mysql.com 提交错误报告"

ER_IB_MSG_1047
  eng "Semaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung."
  chinese "信号量等待时间已超过%llu秒。我们故意使服务器崩溃,因为它似乎已挂起。"

ER_IB_MSG_1048
  eng "Waiting for %llu table(s) to be dropped"
  chinese "正在等待删除%llu个表"

ER_IB_MSG_1049
  eng "Waiting for change buffer merge to complete number of bytes of change buffer just merged: %llu"
  chinese "正在等待更改缓冲区合并以完成刚合并的更改缓冲区的字节数:%llu"

OBSOLETE_ER_IB_MSG_1050
  eng "Can't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0."
  chinese "无法将撤消表空间设置为加密,因为--Innodb_undo_Tablespaces=0。"

ER_IB_MSG_1051
  eng "Can't set undo tablespace(s) to be encrypted in read-only-mode."
  chinese "无法将撤消表空间设置为在只读模式下加密。"

ER_IB_MSG_1052
  eng "Can't set undo tablespace '%s' to be encrypted."
  chinese "无法将撤消表空间'%s'设置为加密。"

ER_IB_MSG_1053
  eng "Can't set undo tablespace '%s' to be encrypted. Failed to write header page."
  chinese "无法将撤消表空间'%s'设置为加密。写入标题页失败。"

ER_IB_MSG_1054
  eng "Can't set undo tablespace '%s' to be encrypted. Error %d - %s"
  chinese "无法将撤消表空间'%s'设置为加密。错误%d-%s"

ER_IB_MSG_1055
  eng "Encryption is enabled for undo tablespace '%s'."
  chinese "已为撤消表空间'%s'启用加密。"

ER_IB_MSG_1056
  eng "Can't rotate encryption on undo tablespace '%s'."
  chinese "无法在撤消表空间'%s'上轮换加密。"

ER_IB_MSG_1057
  eng "Encryption is enabled for undo tablespace '%s'."
  chinese "已为撤消表空间'%s'启用加密。"

ER_IB_MSG_1058
  eng "os_file_get_status() failed on '%s'. Can't determine file permissions."
  chinese "OS_FILE_GET_STATUS()在'%s'上失败。无法确定文件权限。"

ER_IB_MSG_1059
  eng "%s can't be opened in %s mode."
  chinese "%s无法在%s模式下打开。"

ER_IB_MSG_1060
  eng "'%s' not a regular file."
  chinese "'%s'不是常规文件。"

ER_IB_MSG_LOG_FILE_OS_CREATE_FAILED
  eng "Cannot create %s"
  chinese "无法创建%s"

ER_IB_MSG_FILE_RESIZE
  eng "Setting file %s size to %llu MB. Progress : %u%%"

ER_IB_MSG_LOG_FILE_RESIZE_FAILED
  eng "Cannot resize redo log file %s to %llu MB (%s)"
  chinese "无法将重做日志文件%s的大小调整为%llu MB(%s)"

ER_IB_MSG_LOG_FILES_CREATE_AND_READ_ONLY_MODE
  eng "Cannot create redo log files in read-only mode (--innodb-read-only)."
  chinese "无法以只读模式(--Innodb-Read-Only)创建重做日志文件。"

ER_IB_MSG_1065
  eng "Redo log encryption is enabled, but the keyring is not loaded."
  chinese "重做日志加密已启用,但未加载密钥环。"

ER_IB_MSG_LOG_FILE_PREPARE_ON_CREATE_FAILED
  eng "Failed to create redo log file %s (error: %d) for start LSN %llu"
  chinese "无法创建重做日志文件%s(错误:%d)为启动LSN %llu"

OBSOLETE_ER_IB_MSG_1067
  eng "Renaming log file %s to %s"
  chinese "将日志文件%s重命名为%s"

ER_IB_MSG_LOG_FILES_INITIALIZED
  eng "New redo log files created, LSN=%llu"
  chinese "已创建新的重做日志文件,lsn=%llu"

ER_IB_MSG_LOG_FILE_OPEN_FAILED
  eng "Unable to open '%s' (error: %d)."
  chinese "无法打开'%s'(错误:%d)。"

ER_IB_MSG_1070
  eng "Cannot create construction log file '%s' for undo tablespace '%s'."
  chinese "无法为撤消表空间'%s'创建构造日志文件'%s'。"

ER_IB_MSG_1071
  eng "Creating UNDO Tablespace %s"
  chinese "正在创建撤消表空间%s"

ER_IB_MSG_1072
  eng "Setting file %s size to %llu MB"
  chinese "将文件%s大小设置为%llu MB"

ER_IB_MSG_1073
  eng "Physically writing the file full"
  chinese "物理写入文件已满"

ER_IB_MSG_1074
  eng "Error in creating %s: probably out of disk space"
  chinese "创建%s时出错:可能磁盘空间不足"

ER_IB_MSG_1075
  eng "Can't set encryption metadata for space %s"
  chinese "无法为空间%s设置加密元数据"

ER_IB_MSG_1076
  eng "Cannot read first page of '%s' - %s"
  chinese "无法读取'%s'的第一页-%s"

ER_IB_MSG_1077
  eng "Undo tablespace number %lu was being truncated when mysqld quit."
  chinese "Undo表空间编号%lu在mysqld退出时被截断。"

ER_IB_MSG_1078
  eng "Cannot recover a truncated undo tablespace in read-only mode"
  chinese "无法在只读模式下恢复被截断的还原表空间"

ER_IB_MSG_1079
  eng "Reconstructing undo tablespace number %lu."
  chinese "正在重新构造撤消表空间号%lu。"

ER_IB_MSG_1080
  eng "Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?"
  chinese "无法创建%s,因为%s已使用空间ID=%lu！您更改Innodb_undo_目录了吗？"

ER_IB_MSG_1081
  eng "UNDO tablespace %s must be %s"
  chinese "撤消表空间%s必须是%s"

ER_IB_MSG_1082
  eng "Error creating file for %s"
  chinese "为%s创建文件时出错"

ER_IB_MSG_1083
  eng "Error reading encryption for %s"
  chinese "读取%s的加密时出错"

ER_IB_MSG_CANNOT_OPEN_57_UNDO
  eng "Unable to open undo tablespace number %lu"
  chinese "无法打开撤消表空间号%lu"

ER_IB_MSG_1085
  eng "Opened %llu existing undo tablespaces."
  chinese "已打开%llu个现有的撤消表空间。"

ER_IB_MSG_1086
  eng "Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces."
  chinese "由于已设置Innodb_%s,因此无法创建撤消表空间。正在使用%llu个现有的撤消表空间。"

ER_IB_MSG_1087
  eng "Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found."
  chinese "无法继续在%s模式下启动InnoDB,因为找不到现有的撤消表空间。"

ER_IB_MSG_1088
  eng "Could not create undo tablespace '%s'."
  chinese "无法创建撤消表空间'%s'。"

ER_IB_MSG_1089
  eng "Error %d - %s - opening newly created undo tablespace '%s'."
  chinese "错误%d-%s-正在打开新创建的撤消表空间'%s'。"

ER_IB_MSG_1090
  eng "Created %llu undo tablespaces."
  chinese "已创建%llu个撤消表空间。"

ER_IB_MSG_1091
  eng "Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctly"
  chinese "无法创建加密的撤消表空间号%lu.请检查密钥环是否已正确初始化"

ER_IB_MSG_1092
  eng "Encryption is enabled for undo tablespace number %lu."
  chinese "为撤消表空间编号%lu启用了加密。"

ER_IB_MSG_1093
  eng "Unable to initialize the header page in undo tablespace number %lu."
  chinese "无法初始化撤消表空间%lu中的标题页。"

ER_IB_MSG_1094
  eng "Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions."
  chinese "无法删除旧的撤消表空间,因为它们包含XA准备事务的撤消日志。"

ER_IB_MSG_1095
  eng "Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces."
  chinese "将SYSTEM表空间中跟踪的%zu个现有还原表空间升级为%lu个新的独立还原表空间。"

ER_IB_MSG_1096
  eng "Deleting %llu new independent undo tablespaces that we just created."
  chinese "正在删除我们刚刚创建的%llu个新的独立撤消表空间。"

ER_IB_MSG_1097
  eng "Waiting for purge to start"
  chinese "等待清洗开始"

ER_IB_MSG_1098
  eng "Creating shared tablespace for temporary tables"
  chinese "为临时表创建共享表空间"

ER_IB_MSG_1099
  eng "The %s data file must be writable!"
  chinese "%s数据文件必须是可写的！"

ER_IB_MSG_1100
  eng "Could not create the shared %s."
  chinese "无法创建共享%s。"

ER_IB_MSG_1101
  eng "Unable to create the shared %s."
  chinese "无法创建共享%s。"

ER_IB_MSG_1102
  eng "The %s data file cannot be re-opened after check_file_spec() succeeded!"
  chinese "CHECK_FILE_SPEC()成功后,无法重新打开%s数据文件！"

ER_IB_MSG_1103
  eng "%d threads created by InnoDB had not exited at shutdown!"
  chinese "InnoDB创建的%d个线程在关闭时未退出！"

ER_IB_MSG_1104
  eng "InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again."
  chinese "InnoDB数据库创建已中止%s,错误为%s。在尝试重新启动之前,您可能需要删除ibdata1文件。"

ER_IB_MSG_1105
  eng "Plugin initialization aborted %swith error %s."
  chinese "插件初始化已中止%s,错误为%s。"

ER_IB_MSG_BUF_PENDING_IO
  eng "Waiting for %zu buffer page I/Os to complete."
  chinese "正在等待%zu缓冲区页面I/O完成。"

ER_IB_MSG_1107
  eng "PUNCH HOLE support available"
  chinese "提供冲孔支持"

ER_IB_MSG_1108
  eng "PUNCH HOLE support not available"
  chinese "冲孔支持不可用"

ER_IB_MSG_1109
  eng "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."
  chinese "InnoDB的ulint大小为%zu,而void*的大小为%zu。大小应该相同,以便在64位平台上可以分配超过4 GB的内存。"

ER_IB_MSG_1110
  eng "Database upgrade cannot be accomplished in read-only mode."
  chinese "无法在只读模式下完成数据库升级。"

ER_IB_MSG_1111
  eng "Database upgrade cannot be accomplished with innodb_force_recovery > 0"
  chinese "无法在Innodb_force_Recovery>0的情况下完成数据库升级"

ER_IB_MSG_1112
  eng "%s"
  chinese "%s"

ER_IB_MSG_1113
  eng "%s"
  chinese "%s"

ER_IB_MSG_1114
  eng "%s"
  chinese "%s"

ER_IB_MSG_1115
  eng "%s"
  chinese "%s"

ER_IB_MSG_1116
  eng "%s"
  chinese "%s"

ER_IB_MSG_1117
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_1118
  eng "%s"
  chinese "%s"

ER_IB_MSG_1119
  eng "%s"
  chinese "%s"

ER_IB_MSG_1120
  eng "%s"
  chinese "%s"

ER_IB_MSG_1121
  eng "%s"
  chinese "%s"

ER_IB_MSG_1122
  eng "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."
  chinese "MySQL在此体系结构上是在没有内存屏障功能的情况下构建的,这可能允许在高线程并发性下出现mutex/rw_lock冲突。这可能会导致挂起。"

ER_IB_MSG_1123
  eng "Compressed tables use zlib %s"
  chinese "压缩的表使用zlib %s"

ER_IB_MSG_1124
  eng "%s"
  chinese "%s"

ER_IB_MSG_1125
  eng "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."
  chinese "在进程生存期内第二次调用Startup。在MySQL Embedded Server库中,不能在进程生存期内多次调用server_init()。"

ER_IB_MSG_1126
  eng "%s"
  chinese "%s"

ER_IB_MSG_1127
  eng "Unable to create monitor file %s: %s"
  chinese "无法创建监视文件%s:%s"

ER_IB_MSG_1128
  eng "Disabling background ibuf IO read threads."
  chinese "正在禁用后台IBUF IO写入线程。"

ER_IB_MSG_1129
  eng "Cannot initialize AIO sub-system"
  chinese "无法初始化AIO子系统"

ER_IB_MSG_1130
  eng "Initializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c "

ER_IB_MSG_1131
  eng "Cannot allocate memory for the buffer pool"
  chinese "无法为缓冲池分配内存"

ER_IB_MSG_1132
  eng "Completed initialization of buffer pool"
  chinese "已完成缓冲池的初始化"

ER_IB_MSG_1133
  eng "Small buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up."
  chinese "由于缓冲池大小较小(%llum),如果缓冲池已满,则flst_valify()调试函数可能会导致死锁。"

ER_IB_MSG_1134
  eng "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!"
  chinese "无法打开或创建SYSTEM表空间。如果您尝试将新的数据文件添加到SYSTEM表空间,但在这里失败了,您现在应该将my.cnf中的Innodb_data_file_path编辑回原来的状态,并删除在这次失败的尝试中创建的新ibdata文件InnoDB。InnoDB只写满零的那些文件,但还没有以任何方式使用它们。但请注意:不要删除包含宝贵数据的旧数据文件！"

ER_IB_MSG_DATA_DIRECTORY_NOT_INITIALIZED_OR_CORRUPTED
  eng "Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files."
  chinese "无法创建重做日志文件,因为数据文件已损坏或数据库在创建数据文件后没有完全关闭。"

ER_IB_MSG_LOG_FILES_INVALID_SET
  eng "Only one redo log file found"
  chinese "只找到一个重做日志文件"

ER_IB_MSG_LOG_FILE_SIZE_INVALID
  eng "The redo log file %s size %llu is not a multiple of innodb_page_size"
  chinese "重做日志文件%s大小%llu不是Innodb_Page_Size的倍数"

ER_IB_MSG_LOG_FILES_DIFFERENT_SIZES
  eng "The redo log file %s is of different size %llu bytes than other log files %llu bytes!"
  chinese "重做日志文件%s的大小%llu字节与其他日志文件的大小%llu字节不同！"

ER_IB_MSG_1139
  eng "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)"
  chinese "使用--Innodb-directories查找表空间文件。如果失败,则使用--Innodb-force-Recovery=1忽略它并永久丢失对丢失的表空间所做的所有更改"

ER_IB_MSG_RECOVERY_CORRUPT
  eng "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!"
  chinese "重做日志文件可能已损坏,可能是日志扫描或解析在恢复过程中进行得不够深入。请对InnoDB表运行CHECK TABLE以检查它们是否正常！从备份恢复InnoDB数据库可能是最安全的！"

OBSOLETE_ER_IB_MSG_LOG_FILES_RESIZE_ON_START_IN_READ_ONLY_MODE
  eng "Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only."
  chinese "无法在只读模式下调整重做日志文件的大小。请提供--Innodb_redo_log_Capacity>=%lluMB或在不使用--Innodb-Read-Only的情况下启动。"

ER_IB_MSG_1142
  eng "Cannot open DD tablespace."
  chinese "无法打开DD表空间。"

ER_IB_MSG_LOG_FILES_REWRITING
  eng "Starting to delete and rewrite redo log files."
  chinese "开始删除和重写重做日志文件。"

ER_IB_MSG_1144
  eng "Undo from 5.7 found. It will be purged"
  chinese "已找到5.7中的撤消。它将被清除"

ER_IB_MSG_1145
  eng "%s"
  chinese "%s"

ER_IB_MSG_1146
  eng "%s"
  chinese "%s"

ER_IB_MSG_1147
  eng "Tablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pages"
  chinese "标题中存储的表空间大小为%lu页,但数据文件大小之和为%lu页"

ER_IB_MSG_1148
  eng "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."
  chinese "无法启动InnoDB。缺少SYSTEM表空间的尾部。您是否以不正确的方式编辑了my.cnf中的Innodb_data_file_path,从中删除了ibdata文件？如果您正在尝试恢复严重损坏的数据库,可以在my.cnf中设置Innodb_force_Recovery=1以强制启动。"

ER_IB_MSG_1149
  eng "Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pages"
  chinese "标题中存储的表空间大小为%lu页,但数据文件大小之和仅为%lu页"

ER_IB_MSG_1150
  eng "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."
  chinese "无法启动InnoDB。缺少SYSTEM表空间的尾部。您是否以InnoDB:不当的方式编辑了my.cnf中的Innodb_data_file_path,从那里删除了ibdata文件？您可以在my.cnf中设置Innodb_force_Recovery=1,以强制InnoDB:如果您正在尝试恢复严重损坏的数据库,则会启动InnoDB。"

ER_IB_MSG_1151
  eng "%s started; log sequence number %llu"
  chinese "%s已启动；日志序列号%llu"

ER_IB_MSG_1152
  eng "Waiting for purge to complete"
  chinese "正在等待清除完成"

OBSOLETE_ER_IB_MSG_1153
  eng "Waiting for dict_stats_thread to exit"
  chinese "正在等待DICT_STATS_THREAD退出"

ER_IB_MSG_1154
  eng "Query counter shows %lld queries still inside InnoDB at shutdown"
  chinese "查询计数器显示%lld个查询在关闭时仍在InnoDB内"

ER_IB_MSG_1155
  eng "Shutdown completed; log sequence number %llu"
  chinese "关闭已完成；日志序列号%llu"

ER_IB_MSG_1156
  eng "Cannot continue operation."
  chinese "无法继续操作。"

ER_IB_MSG_1157
  eng "%s"
  chinese "%s"

ER_IB_MSG_1158
  eng "%s"
  chinese "%s"

ER_IB_MSG_1159
  eng "%s"
  chinese "%s"

ER_IB_MSG_1160
  eng "%s"
  chinese "%s"

ER_IB_MSG_1161
  eng "%s"
  chinese "%s"

ER_IB_MSG_1162
  eng "%s"
  chinese "%s"

ER_IB_MSG_1163
  eng "%s"
  chinese "%s"

ER_IB_MSG_1164
  eng "%s"
  chinese "%s"

ER_IB_MSG_1165
  eng "%s"
  chinese "%s"

ER_IB_MSG_UNDO_TRUNCATE_FAIL_TO_READ_LOG_FILE
  eng "Unable to read the existing undo truncate log file '%s'. The error is %s"
  chinese "无法读取现有的撤消截断日志文件'%s'。错误为%s"

ER_IB_MSG_UNDO_MARKED_FOR_TRUNCATE
  eng "Undo tablespace %s is marked for truncate"
  chinese "撤消表空间%s被标记为截断"

OBSOLETE_ER_IB_MSG_UNDO_INJECT_BEFORE_MDL
  eng "%s"
  chinese "%s"

ER_IB_MSG_UNDO_TRUNCATE_START
  eng "Truncating UNDO tablespace %s"
  chinese "正在截断还原表空间%s"

OBSOLETE_ER_IB_MSG_UNDO_INJECT_BEFORE_DDL_LOG_START
  eng "%s"
  chinese "%s"

ER_IB_MSG_UNDO_TRUNCATE_DELAY_BY_LOG_CREATE
  eng "Cannot create truncate log for undo tablespace '%s'."
  chinese "无法为撤消表空间'%s'创建截断日志。"

OBSOLETE_ER_IB_MSG_UNDO_INJECT_BEFORE_TRUNCATE
  eng "%s"
  chinese "%s"

ER_IB_MSG_UNDO_TRUNCATE_DELAY_BY_FAILURE
  eng "Failed to truncate undo tablespace '%s'."
  chinese "无法截断撤消表空间'%s'。"

OBSOLETE_ER_IB_MSG_UNDO_INJECT_BEFORE_STATE_UPDATE
  eng "%s"
  chinese "%s"

ER_IB_MSG_UNDO_TRUNCATE_COMPLETE
  eng "Completed truncate of undo tablespace %s."
  chinese "已完成对撤消表空间%s的截断。"

OBSOLETE_ER_IB_MSG_UNDO_INJECT_TRUNCATE_DONE
  eng "%s"
  chinese "%s"

ER_IB_MSG_1177
  eng "%s"
  chinese "%s"

ER_IB_MSG_1178
  eng "%s"
  chinese "%s"

ER_IB_MSG_1179
  eng "%s"
  chinese "%s"

ER_IB_MSG_1180
  eng "%s"
  chinese "%s"

ER_IB_MSG_1181
  eng "%s"
  chinese "%s"

ER_IB_MSG_1182
  eng "%s"
  chinese "%s"

ER_IB_MSG_1183
  eng "%s"
  chinese "%s"

ER_IB_ERR_ACCESSING_OUT_OF_BOUND_FIELD_IN_INDEX
   eng "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."

ER_IB_MSG_1185
  eng "%s"
  chinese "%s"

ER_IB_MSG_1186
  eng "%s"
  chinese "%s"

ER_IB_MSG_1187
  eng "%s"
  chinese "%s"

ER_IB_MSG_1188
  eng "%s"
  chinese "%s"

ER_IB_MSG_1189
  eng "%s"
  chinese "%s"

ER_IB_MSG_TRX_RECOVERY_ROLLBACK_COMPLETED
  eng "Rollback of non-prepared transactions completed"
  chinese "已完成未准备事务的回滚"

ER_IB_MSG_1191
  eng "%s"
  chinese "%s"

ER_IB_MSG_1192
  eng "%s"
  chinese "%s"

ER_IB_MSG_1193
  eng "%s"
  chinese "%s"

ER_IB_MSG_1194
  eng "%s"
  chinese "%s"

ER_IB_MSG_1195
  eng "%s"
  chinese "%s"

ER_IB_MSG_1196
  eng "%s"
  chinese "%s"

ER_IB_MSG_1197
  eng "%s"
  chinese "%s"

ER_IB_MSG_1198
  eng "%s"
  chinese "%s"

ER_IB_MSG_1199
  eng "%s"
  chinese "%s"

ER_IB_MSG_1200
  eng "%s"
  chinese "%s"

ER_IB_MSG_1201
  eng "%s"
  chinese "%s"

ER_IB_MSG_1202
  eng "%s"
  chinese "%s"

ER_IB_MSG_1203
  eng "%s"
  chinese "%s"

ER_IB_MSG_1204
  eng "%s"
  chinese "%s"

ER_IB_MSG_1205
  eng "%s"
  chinese "%s"

ER_IB_MSG_1206
  eng "%s"
  chinese "%s"

ER_IB_MSG_1207
  eng "%s"
  chinese "%s"

ER_IB_MSG_1208
  eng "%s"
  chinese "%s"

ER_IB_MSG_1209
  eng "%s"
  chinese "%s"

ER_IB_MSG_1210
  eng "%s"
  chinese "%s"

ER_IB_MSG_1211
  eng "Blocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back."
  chinese "阻止的高优先级事务(ID%llu,线程ID%s)通过回滚终止了正在阻止的事务(ID%llu-%s)。"

ER_IB_MSG_1212
  eng "%s"
  chinese "%s"

ER_IB_MSG_1213
  eng "gettimeofday() failed: %s"
  chinese "gettimeofday()失败:%s"

ER_IB_MSG_1214
  eng "Can't create UNDO tablespace %s %s"
  chinese "无法创建撤消表空间%s %s"

ER_IB_MSG_1215
  eng "%s"
  chinese "%s"

ER_IB_MSG_LOG_FILES_RESIZE_ON_START
  eng "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."
  chinese "正在将重做日志从%llum同步调整为%llum(lsn=%llu)。如果这花费的时间太长,请考虑使用Large--Innodb_REDO_LOG_CAPTION启动服务器,并使用SET联机调整重做日志的大小。"

ER_IB_MSG_1217
  eng "%s"
  chinese "%s"

ER_IB_MSG_1218
  eng "%s"
  chinese "%s"

ER_IB_MSG_1219
  eng "%s"
  chinese "%s"

ER_IB_MSG_1220
  eng "%s"
  chinese "%s"

ER_IB_MSG_1221
  eng "%s"
  chinese "%s"

ER_IB_MSG_1222
  eng "%s"
  chinese "%s"

ER_IB_MSG_1223
  eng "%s"
  chinese "%s"

ER_IB_MSG_1224
  eng "%s"
  chinese "%s"

ER_IB_MSG_1225
  eng "%s"
  chinese "%s"

ER_IB_MSG_1226
  eng "%s"
  chinese "%s"

ER_IB_MSG_1227
  eng "%s"
  chinese "%s"

ER_IB_MSG_1228
  eng "%s"
  chinese "%s"

ER_IB_MSG_1229
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_1230
  eng "%s"
  chinese "%s"

ER_IB_MSG_1231
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_1232
  eng "%s"
  chinese "%s"

ER_IB_MSG_1233
  eng "%s"
  chinese "%s"

ER_IB_MSG_LOG_WRITER_OUT_OF_SPACE
  eng "Out of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity."
  chinese "重做日志中的空间不足。检查点lsn:%llu。请考虑增加Innodb_redo_log_Capacity。"

ER_IB_MSG_1235
  eng "%s"
  chinese "%s"

ER_IB_MSG_LOG_WRITER_ABORTS_LOG_ARCHIVER
  eng "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."
  chinese "日志编写器等待重做存档程序前进的时间太长(1秒)。有未存档的:%llu字节。存档程序LSN:%llu。已中止重做存档程序。请考虑增加Innodb_redo_log_Capacity。"

ER_IB_MSG_LOG_WRITER_WAITING_FOR_ARCHIVER
  eng "Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity."
  chinese "日志编写器正在等待重做存档程序跟踪未存档的:%llu字节。存档程序LSN:%llu。请考虑增加Innodb_redo_log_Capacity。"

ER_IB_MSG_1238
  eng "%s"
  chinese "%s"

ER_IB_MSG_1239
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_1240
  eng "%s"
  chinese "%s"

ER_IB_MSG_1241
  eng "%s"
  chinese "%s"

ER_IB_MSG_LOG_FILES_CANNOT_ENCRYPT_IN_READ_ONLY
  eng "Can't set redo log files to be encrypted in read-only mode."
  chinese "无法将重做日志文件设置为以只读模式加密。"

ER_IB_MSG_LOG_FILES_ENCRYPTION_INIT_FAILED
  eng "Can't set redo log files to be encrypted."
  chinese "无法将重做日志文件设置为加密。"

OBSOLETE_ER_IB_MSG_1244
  eng "Can't set redo log tablespace to be encrypted."
  chinese "无法将重做日志表空间设置为加密。"

ER_IB_MSG_1245
  eng "Redo log encryption is enabled."
  chinese "已启用重做日志加密。"

ER_IB_MSG_1246
  eng "Waiting for archiver to finish archiving page and log"
  chinese "正在等待存档程序完成存档页面和日志"

ER_IB_MSG_1247
  eng "Starting shutdown..."
  chinese "正在开始关机..."

ER_IB_MSG_1248
  eng "Waiting for %s to exit."
  chinese "正在等待%s退出。"

ER_IB_MSG_1249
  eng "Waiting for rollback of %zu recovered transactions, before shutdown."
  chinese "正在等待回滚%zu恢复的事务,然后关闭。"

ER_IB_MSG_1250
  eng "Waiting for master thread to be suspended."
  chinese "正在等待挂起主线程。"

ER_IB_MSG_1251
  eng "Waiting for page_cleaner to finish flushing of buffer pool."
  chinese "正在等待PAGE_CLENER完成缓冲池刷新。"

ER_IB_MSG_BUF_PENDING_IO_ON_SHUTDOWN
  eng "Shutdown is waiting for %zu buffer page I/Os to complete."
  chinese "关闭正在等待%zu缓冲区页面I/O完成。"

ER_IB_MSG_1253
  eng "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!"
  chinese "MySQL已请求快速关闭,而无需将InnoDB缓冲池刷新到数据文件。在下一次mysqld启动时,InnoDB将执行崩溃恢复！"

OBSOLETE_ER_IB_MSG_1254
  eng "%s"
  chinese "%s"

ER_IB_MSG_1255
  eng "%s"
  chinese "%s"

ER_IB_MSG_1256
  eng "%s"
  chinese "%s"

ER_IB_MSG_1257
  eng "%s"
  chinese "%s"

ER_IB_MSG_1258
  eng "%s"
  chinese "%s"

ER_IB_MSG_1259
  eng "%s"
  chinese "%s"

ER_IB_MSG_1260
  eng "%s"
  chinese "%s"

ER_IB_MSG_1261
  eng "%s"
  chinese "%s"

ER_IB_MSG_1262
  eng "%s"
  chinese "%s"

ER_IB_MSG_1263
  eng "%s"
  chinese "%s"

ER_IB_MSG_LOG_FILE_HEADER_INVALID_CHECKSUM
  eng "Invalid redo log header checksum."
  chinese "无效的重做日志头校验和。"

ER_IB_MSG_LOG_FORMAT_BEFORE_5_7_9
  eng "Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9"
  chinese "不支持重做日志格式(v%lu)。重做日志是在MySQL 5.7.9之前创建的"

ER_IB_MSG_1266
  eng "%s"
  chinese "%s"

ER_IB_MSG_LOG_PARAMS_CONCURRENCY_MARGIN_UNSAFE
  eng "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"
  chinese "无法继续操作。Innodb_REDO_LOG_CAPTIONCE=%llu对于InnodB_THREAD_CONTURRENT=%lu太小。重做容量应>=%lluM。若要运行mysqld,请将INNODB_THREAD_CONTURRENY设置为较小的值或增加InnodB_REDO_LOG_CAPTABILITY。%s"

ER_IB_MSG_1268
  eng "%s"
  chinese "%s"

ER_IB_MSG_1269
  eng "%s"
  chinese "%s"

ER_IB_MSG_THREAD_CONCURRENCY_CHANGED
  eng "User has set innodb_thread_concurrency to %lu."
  chinese "用户已将INNODB_THREAD_CONTURRENY设置为%lu。"

ER_RPL_REPLICA_SQL_THREAD_STOP_CMD_EXEC_TIMEOUT
  eng "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."
  chinese "停止从属命令执行未完成:从SQL线程收到停止信号,线程忙,一旦当前任务完成,SQL线程将停止。"

ER_RPL_REPLICA_IO_THREAD_STOP_CMD_EXEC_TIMEOUT
  eng "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."
  chinese "停止从属命令执行未完成:从属IO线程收到停止信号,线程忙,IO线程将在当前任务完成后停止。"

ER_RPL_GTID_UNSAFE_STMT_ON_NON_TRANS_TABLE
  eng "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."
  chinese "语句违反GTID一致性:对非事务性表的更新只能在自动提交的语句或单语句事务中完成,并且永远不能在与事务性表更新相同的语句中进行。"

ER_RPL_GTID_UNSAFE_STMT_CREATE_SELECT
  eng "Statement violates GTID consistency: CREATE TABLE ... SELECT."
  chinese "语句违反GTID一致性:CREATE TABLE...SELECT。"

OBSOLETE_ER_RPL_GTID_UNSAFE_STMT_ON_TEMPORARY_TABLE
  eng "Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions."
  chinese "语句违反GTID一致性:CREATE TEMPORARY TABLE和DROP TEMPORARY TABLE只能在事务上下文之外执行。函数或触发器中也不允许使用这些语句,因为函数和触发器也被视为多语句事务。"

ER_BINLOG_ROW_VALUE_OPTION_IGNORED
  eng "When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log."
  chinese "当为%.192s时,选项binlog_row_Value_Options=%.192s将被忽略,并且更新将以完整格式写入二进制日志。"

OBSOLETE_ER_BINLOG_USE_V1_ROW_EVENTS_IGNORED
  eng "When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log."
  chinese "当%.192s时,选项LOG_BIN_USE_v1_ROW_EVENTS=1将被忽略,行事件将以新格式写入二进制日志。"

ER_BINLOG_ROW_VALUE_OPTION_USED_ONLY_FOR_AFTER_IMAGES
  eng "When %.192s, the option binlog_row_value_options=%.192s 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%%."

ER_CONNECTION_ABORTED
  eng "Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s)."
  chinese "已中止与数据库的连接%u:'%-.192s'用户:'%-.48s'主机:'%-.255s'(%-.64s)。"

ER_NORMAL_SERVER_SHUTDOWN
  eng "%s: Normal shutdown."
  chinese "%s:正常关闭。"

ER_KEYRING_MIGRATE_FAILED
  eng "Can not perform keyring migration : %s."
  chinese "无法执行密钥环迁移:%s。"

ER_GRP_RPL_LOWER_CASE_TABLE_NAMES_DIFF_FROM_GRP
  eng "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."
  chinese "该成员配置的LOWER_CASE_TABLE_NAMES选项值'%u'与组'%u'不同。该成员现在将退出该组。如果成员上存在现有数据,如果它是用与该组不同的LOWER_CASE_TABLE_NAME值创建的,则可能与该组不兼容。"

ER_OOM_SAVE_GTIDS
  eng "An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed table"
  chinese "将上一个二进制日志中的GTID集保存到mysql.gtid_Executed表中时出现内存不足错误"

ER_LCTN_NOT_FOUND
  eng "The lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'."
  chinese "找不到数据字典的LOWER_CASE_TABLE_NAMES设置。请使用LOWER_CASE_TABLE_NAMES='%u'启动服务器。"

OBSOLETE_ER_REGEXP_INVALID_CAPTURE_GROUP_NAME
  eng "A capture group has an invalid name."
  chinese "捕获组的名称无效。"

ER_COMPONENT_FILTER_WRONG_VALUE
  eng "Variable '%-.64s' can't be set to the value of '%-.200s'"
  chinese "变量'%-.64s'不能设置为'%-.200s'的值"

ER_XPLUGIN_FAILED_TO_STOP_SERVICES
  eng "Stopping services failed with error \"%s\""
  chinese "停止服务失败,出现错误\"%s\""

ER_INCONSISTENT_ERROR
  eng "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'"
  chinese "查询在主服务器和从服务器上造成了不同的错误。主服务器上的错误:消息(格式)='%s',错误代码=%d；从服务器上的错误:实际消息='%s',错误代码=%d。默认数据库:'%s'。查询:'%s'"

ER_SERVER_SOURCE_FATAL_ERROR_READING_BINLOG
  eng "Got fatal error %d from source when reading data from binary log: '%-.512s'"
  chinese "从二进制日志中读取数据时,从主机获取致命错误%d:'%-.512s'"

ER_NETWORK_READ_EVENT_CHECKSUM_FAILURE
  eng "Replication event checksum verification failed while reading from network."
  chinese "从网络读取时,复制事件校验和验证失败。"

ER_REPLICA_CREATE_EVENT_FAILURE
  eng "Failed to create %s"
  chinese "无法创建%s"

ER_REPLICA_FATAL_ERROR
  eng "Fatal error: %s"
  chinese "致命错误:%s"

ER_REPLICA_HEARTBEAT_FAILURE
  eng "Unexpected source's heartbeat data: %s"
  chinese "未知的主机心跳数据:%s"

ER_REPLICA_INCIDENT
  eng "The incident %s occurred on the source. Message: %s"
  chinese "事件%s发生在主服务器上。消息:%s"

ER_REPLICA_SOURCE_COM_FAILURE
  eng "Source command %s failed: %s"
  chinese "主命令%s失败:%s"

ER_REPLICA_RELAY_LOG_READ_FAILURE
  eng "Relay log read failure: %s"
  chinese "中继日志读取失败:%s"

ER_REPLICA_RELAY_LOG_WRITE_FAILURE
  eng "Relay log write failure: %s"
  chinese "中继日志写入失败:%s"

ER_SERVER_REPLICA_CM_INIT_REPOSITORY
  eng "Replica failed to initialize connection metadata structure from the repository"
  chinese "Replica无法从存储库中初始化主信息结构"

ER_SERVER_REPLICA_AM_INIT_REPOSITORY
  eng "Replica failed to initialize applier metadata structure from the repository"
  chinese "Replica无法从存储库中初始化中继日志信息结构"

ER_SERVER_NET_PACKET_TOO_LARGE
  eng "Got a packet bigger than 'max_allowed_packet' bytes"
  chinese "收到大于'max_Allowed_Packet'字节的数据包"

ER_SERVER_NO_SYSTEM_TABLE_ACCESS
  eng "Access to %.64s '%.64s.%.64s' is rejected."
  chinese "拒绝访问%.64s'%.64s.%.64s'。"

OBSOLETE_ER_SERVER_UNKNOWN_ERROR
  eng "Unknown error"
  chinese "未知错误"

ER_SERVER_UNKNOWN_SYSTEM_VARIABLE
  eng "Unknown system variable '%-.64s'"
  chinese "未知系统变量'%-.64s'"

ER_SERVER_NO_SESSION_TO_SEND_TO
  eng "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"
  chinese "由于没有附加客户端会话,无法将发送给客户端的消息发送到那里。因此,我们改为将信息发送到错误日志:my-%06d-%s"

ER_SERVER_NEW_ABORTING_CONNECTION 08S01
  eng "Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)"
  chinese "已中止与数据库的连接%u:'%-.192s'用户:'%-.48s'主机:'%-.255s'(%-.64s；诊断区域:My-%06d-%-.64s)"

ER_SERVER_OUT_OF_SORTMEMORY
  eng "Out of sort memory, consider increasing server sort buffer size!"
  chinese "排序内存不足,请考虑增加服务器排序缓冲区大小！"

ER_SERVER_RECORD_FILE_FULL
  eng "The table '%-.192s' is full!"
  chinese "表'%-.192s'已满！"

ER_SERVER_DISK_FULL_NOWAIT
  eng "Create table/tablespace '%-.192s' failed, as disk is full."
  chinese "由于磁盘已满,创建表/表空间'%-.192s'失败。"

ER_SERVER_HANDLER_ERROR
  eng "Handler reported error %d - %s"
  chinese "处理程序报告错误%d-%s"

ER_SERVER_NOT_FORM_FILE
  eng "Incorrect information in file: '%-.200s'"
  chinese "文件中的信息不正确:'%-.200s'"

ER_SERVER_CANT_OPEN_FILE
  eng "Can't open file: '%-.200s' (OS errno: %d - %s)"
  chinese "无法打开文件:'%-.200s'(操作系统错误号:%d - %s)"

ER_SERVER_FILE_NOT_FOUND
  eng "Can't find file: '%-.200s' (OS errno: %d - %s)"
  chinese "找不到文件:'%-.200s'(操作系统错误号:%d - %s)"

ER_SERVER_FILE_USED
  eng "'%-.192s' is locked against change (OS errno: %d - %s)"
  chinese "'%-.192s'已锁定,不能更改(操作系统错误号:%d - %s)"

ER_SERVER_CANNOT_LOAD_FROM_TABLE_V2
  eng "Cannot load from %s.%s. The table is probably corrupted!"
  chinese "无法从%s.%s加载。该表可能已损坏！"

ER_ERROR_INFO_FROM_DA
  eng "Error in diagnostics area: MY-%06d - %s"
  chinese "诊断区域出错:My-%06d-%s"

ER_SERVER_TABLE_CHECK_FAILED
  eng "Incorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'."
  chinese "表%s.%s的定义不正确:需要列'%s'位置%d处,但找到了'%s'。"

ER_SERVER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE_V2
  eng "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."
  chinese "%s.%s的列计数错误。预期为%d,找到了%d。使用MySQL%d创建,现在正在运行%d。请执行MySQL升级过程。"

ER_SERVER_COL_COUNT_DOESNT_MATCH_CORRUPTED_V2
  eng "Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted."
  chinese "%s.%s的列计数错误。预期为%d,找到了%d。该表可能已损坏。"

ER_SERVER_ACL_TABLE_ERROR
  eng ""
  chinese ""

ER_SERVER_REPLICA_INIT_QUERY_FAILED
  eng "Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'"
  chinese "从SQL线程已中止。无法执行init_replica查询,my-%06d-'%s'"

ER_SERVER_REPLICA_CONVERSION_FAILED
  eng "Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'"
  chinese "无法将列%d的表'%-.192s.%-.192s'从类型'%-.32s'转换为类型'%-.32s'"

ER_SERVER_REPLICA_IGNORED_TABLE
  eng "Replica SQL thread ignored the query because of replicate-*-table rules"
  chinese "由于复制-*-表规则,从SQL线程忽略了该查询"

ER_CANT_REPLICATE_ANONYMOUS_WITH_AUTO_POSITION
  eng "Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld."
  chinese "当AUTO_POSITION=1,文件%.400s,位置%lld时,无法复制匿名事务。"

ER_CANT_REPLICATE_ANONYMOUS_WITH_GTID_MODE_ON
  eng "Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld."
  chinese "当@@GLOBAL.GTID_MODE=ON时,无法在文件%.400s的位置%lld复制匿名事务。"

ER_CANT_REPLICATE_GTID_WITH_GTID_MODE_OFF
  eng "Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld."
  chinese "当@@GLOBAL.GTID_MODE=OFF时,无法在文件%.400s的位置%lld复制GTID-TRANSACTION。"

# This entry is intended for testing (for instance, the server-log test
# component throws this, and has the built-in filtering engine select these)
# as it is disjunct from all error-codes used in real operation. Message is
# kept intentionally short to despam resulting output files.
ER_SERVER_TEST_MESSAGE
  eng "Simulated error"
  chinese "模拟误差"

ER_AUDIT_LOG_JSON_FILTER_PARSING_ERROR
  eng "%s"
  chinese "%s"

ER_AUDIT_LOG_JSON_FILTERING_NOT_ENABLED
  eng "Audit Log filtering has not been installed."
  chinese "尚未安装审核日志筛选。"

ER_PLUGIN_FAILED_TO_OPEN_TABLES
  eng "Failed to open the %s filter tables."
  chinese "无法打开%s筛选表。"

ER_PLUGIN_FAILED_TO_OPEN_TABLE
  eng "Failed to open '%s.%s' %s table."
  chinese "无法打开'%s.%s'%s表。"

ER_AUDIT_LOG_JSON_FILTER_NAME_CANNOT_BE_EMPTY
  eng "Filter name cannot be empty."
  chinese "过滤器名称不能为空。"

ER_AUDIT_LOG_USER_NAME_INVALID_CHARACTER
  eng "Invalid character in the user name."
  chinese "用户名中的字符无效。"

ER_AUDIT_LOG_UDF_INSUFFICIENT_PRIVILEGE
  eng "Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operation"
  chinese "忽略'%s'@'%s'的请求。需要SUPER或AUDIT_ADMIN来执行操作"

ER_AUDIT_LOG_NO_KEYRING_PLUGIN_INSTALLED
  eng "No keyring installed."
  chinese "未安装钥匙环。"

ER_AUDIT_LOG_HOST_NAME_INVALID_CHARACTER
  eng "Invalid character in the host name."
  chinese "主机名中的字符无效。"

ER_AUDIT_LOG_ENCRYPTION_PASSWORD_HAS_NOT_BEEN_SET
  eng "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."
  chinese "尚未设置审核日志加密密码；它将自动生成。使用AUDIT_LOG_ENCRYPTION_PASSWORD_GET获取密码,或使用AUDIT_LOG_ENCRYPTION_PASSWORD_SET设置新密码。"

ER_AUDIT_LOG_COULD_NOT_CREATE_AES_KEY
  eng "Could not create AES key. OpenSSL's EVP_BytesToKey function failed."
  chinese "无法创建AES密钥。OpenSSL的EVP_BytesToKey函数失败。"

ER_AUDIT_LOG_ENCRYPTION_PASSWORD_CANNOT_BE_FETCHED
  eng "Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption."
  chinese "无法从密钥环获取审核日志加密密码。目前使用的密码用于加密。"

ER_COULD_NOT_REINITIALIZE_AUDIT_LOG_FILTERS
  eng "Could not reinitialize audit log filters."
  chinese "无法重新初始化审核日志筛选器。"

ER_AUDIT_LOG_JSON_USER_NAME_CANNOT_BE_EMPTY
  eng "User cannot be empty."
  chinese "用户不能为空。"

ER_AUDIT_LOG_USER_FIRST_CHARACTER_MUST_BE_ALPHANUMERIC
  eng "First character of the user name must be alphanumeric."
  chinese "用户名的第一个字符必须是字母数字。"

ER_AUDIT_LOG_JSON_FILTER_DOES_NOT_EXIST
  eng "Specified filter has not been found."
  chinese "未找到指定的筛选器。"

OBSOLETE_ER_IB_MSG_1271
  eng "Cannot upgrade server earlier than 5.7 to 8.0"
  chinese "无法将5.7版之前的服务器升级到8.0版"

ER_STARTING_INIT
  eng "%s (mysqld %s) initializing of server in progress as process %lu"
  chinese "%s(mysqld%s)正在初始化服务器,进程为%lu"

ER_ENDING_INIT
  eng "%s (mysqld %s) initializing of server has completed"
  chinese "服务器的%s(mysqld%s)初始化已完成"

ER_IB_MSG_1272
  eng "Cannot boot server version %lu on data directory built by version %llu. Downgrade is not supported"
  chinese "无法启动服务器版本%lu在由版本%llu构建的数据目录上。不支持降级"

ER_SERVER_SHUTDOWN_INFO
  eng "Received SHUTDOWN from user %s. Shutting down mysqld (Version: %s)."
  chinese "收到来自用户%s的关闭。正在关闭mysqld(版本:%s)。"

ER_GRP_RPL_PLUGIN_ABORT
  eng "The plugin encountered a critical error and will abort: %s"
  chinese "插件遇到严重错误,将中止:%s"

OBSOLETE_ER_REGEXP_INVALID_FLAG
  eng "Invalid match mode flag in regular expression."
  chinese "正则表达式中的匹配模式标志无效。"

OBSOLETE_ER_XA_REPLICATION_FILTERS
  eng "The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica."
  chinese "不支持将复制筛选器与XA事务一起使用,这可能会导致复制从属服务器处于未定义的状态。"

OBSOLETE_ER_UPDATE_GTID_PURGED_WITH_GR
  eng "Cannot update GTID_PURGED with the Group Replication plugin running"
  chinese "无法在组复制插件运行时更新GTID_PURGED"

ER_AUDIT_LOG_TABLE_DEFINITION_NOT_UPDATED
  eng "'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure."
  chinese "'%s.%s'表定义尚未升级；请执行MySQL升级过程。"

ER_DD_INITIALIZE_SQL_ERROR
  eng "Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'."
  chinese "执行服务器端SQL语句'%s'失败,错误代码=%d,错误消息='%s'。"

ER_NO_PATH_FOR_SHARED_LIBRARY
  eng "No paths allowed for shared library."
  chinese "共享库不允许路径。"

ER_UDF_ALREADY_EXISTS
  eng "Function '%-.192s' already exists."
  chinese "函数'%-.192s'已存在。"

ER_SET_EVENT_FAILED
  eng "Got Error: %ld from SetEvent."
  chinese "从SetEvent获取错误:%ld。"

ER_FAILED_TO_ALLOCATE_SSL_BIO
  eng "Error allocating SSL BIO."
  chinese "分配SSLBIO时出错。"

ER_IB_MSG_1273
  eng "%s"
  chinese "%s"

ER_PID_FILEPATH_LOCATIONS_INACCESSIBLE
  eng "One or several locations were inaccessible while checking PID filepath."
  chinese "检查PID文件路径时,无法访问一个或多个位置。"

ER_UNKNOWN_VARIABLE_IN_PERSISTED_CONFIG_FILE
  eng "Currently unknown variable '%s' was read from the persisted config file."
  chinese "当前从持久化配置文件中读取了未知变量'%s'。"

ER_FAILED_TO_HANDLE_DEFAULTS_FILE
  eng "Fatal error in defaults handling. Program aborted!"
  chinese "默认处理中出现致命错误。程序已中止！"

ER_DUPLICATE_SYS_VAR
  eng "Duplicate variable name '%s'."
  chinese "变量名'%s'重复。"

ER_FAILED_TO_INIT_SYS_VAR
  eng "Failed to initialize system variables."
  chinese "无法初始化系统变量。"

ER_SYS_VAR_NOT_FOUND
  eng "Variable name '%s' not found."
  chinese "找不到变量名'%s'。"

ER_IB_MSG_1274
  eng "Some (%d) threads are still active"
  chinese "某些(%d)线程仍处于活动状态"

ER_IB_MSG_1275
  eng "%s"
  chinese "%s"

# Unused since MySQL 8.0.15
OBSOLETE_ER_TARGET_TS_UNENCRYPTED
  eng "Source tablespace is encrypted but target tablespace is not."
  chinese "源表空间已加密,但目标表空间未加密。"

ER_IB_MSG_WAIT_FOR_ENCRYPT_THREAD
  eng "Waiting for tablespace_alter_encrypt_thread to exit"
  chinese "正在等待TABLESPACE_ALTER_ENCRYPT_THREAD退出"

ER_IB_MSG_1277
  eng "%s"
  chinese "%s"

ER_IB_MSG_NO_ENCRYPT_PROGRESS_FOUND
  eng "%s"
  chinese "%s"

ER_IB_MSG_RESUME_OP_FOR_SPACE
  eng "%s"
  chinese "%s"

ER_IB_MSG_1280
  eng "%s"
  chinese "%s"

ER_IB_MSG_1281
  eng "%s"
  chinese "%s"

ER_IB_MSG_1282
  eng "%s"
  chinese "%s"

ER_IB_MSG_1283
  eng "%s"
  chinese "%s"

ER_IB_MSG_1284
  eng "%s"
  chinese "%s"

ER_CANT_SET_ERROR_SUPPRESSION_LIST_FROM_COMMAND_LINE
  eng "%s: Could not add suppression rule for code \"%s\". Rule-set may be full, or code may not correspond to an error-log message."
  chinese "%s:无法为代码\"%s\"添加抑制规则。规则集可能已满,或者代码可能与错误日志消息不对应。"

ER_INVALID_VALUE_OF_BIND_ADDRESSES
  eng "Invalid value for command line option bind-addresses: '%s'"
  chinese "命令行选项绑定地址的值无效:'%s'"

ER_RELAY_LOG_SPACE_LIMIT_DISABLED
  eng "Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled."
  chinese "忽略@@lobal.Relay_LOG_SPACE_LIMIT选项,因为已禁用@@GLOBAL.Relay_LOG_PURGE。"

ER_GRP_RPL_ERROR_GTID_SET_EXTRACTION
  eng "Error when extracting GTID execution information: %s"
  chinese "提取GTID执行信息时出错:%s"

ER_GRP_RPL_MISSING_GRP_RPL_ACTION_COORDINATOR
  eng "Message received without a proper group coordinator module."
  chinese "在没有正确的组协调器模块的情况下收到消息。"

ER_GRP_RPL_JOIN_WHEN_GROUP_ACTION_RUNNING
  eng "A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'."
  chinese "当组配置操作%s正在运行时，成员无法加入该组，该操作由%s启动。"

ER_GRP_RPL_JOINER_EXIT_WHEN_GROUP_ACTION_RUNNING
  eng "A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group."
  chinese "当组配置操作%s正在运行时，成员正在加入该组。该操作由%s启动。该成员现在将离开该组"

ER_GRP_RPL_CHANNEL_THREAD_WHEN_GROUP_ACTION_RUNNING
  eng "Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'."
  chinese "当组复制正在运行组配置操作时，无法启动从属%s,频道%s。当组配置操作%s正在运行，该操作由%s启动。"

ER_GRP_RPL_APPOINTED_PRIMARY_NOT_PRESENT
  eng "A primary election was invoked but the requested primary member is not in the group. Request ignored."
  chinese "已调用主要选举,但请求的主要成员不在组中。请求被忽略。"

ER_GRP_RPL_ERROR_ON_MESSAGE_SENDING
  eng "Error while sending message. Context: %s"
  chinese "发送消息时出错。上下文:%s"

ER_GRP_RPL_CONFIGURATION_ACTION_ERROR
  eng "Error while executing a group configuration operation: %s"
  chinese "执行组配置操作时出错:%s"

ER_GRP_RPL_CONFIGURATION_ACTION_LOCAL_TERMINATION
  eng "Configuration operation '%s' terminated. %s"
  chinese "配置操作'%s'已终止。%s"

ER_GRP_RPL_CONFIGURATION_ACTION_START
  eng "Starting group operation local execution: %s"
  chinese "正在启动组操作本地执行:%s"

ER_GRP_RPL_CONFIGURATION_ACTION_END
  eng "Termination of group operation local execution: %s"
  chinese "终止组操作本地执行:%s"

ER_GRP_RPL_CONFIGURATION_ACTION_KILLED_ERROR
  eng "A configuration change was killed in this member. The member will now leave the group as its configuration may have diverged."
  chinese "此成员中的配置更改被终止。该成员现在将离开该组,因为它的配置可能已偏离。"

ER_GRP_RPL_PRIMARY_ELECTION_PROCESS_ERROR
  eng "There was an issue on the primary election process: %s The member will now leave the group."
  chinese "初选过程中出现问题:%s该成员现在将离开该组。"

ER_GRP_RPL_PRIMARY_ELECTION_STOP_ERROR
  eng "There was an issue when stopping a previous election process: %s"
  chinese "停止以前的选举进程时出现问题:%s"

ER_GRP_RPL_NO_STAGE_SERVICE
  eng "It was not possible to initialize stage logging for this task. The operation will still run without stage tracking."
  chinese "无法为此任务初始化阶段日志记录。该操作仍将在没有阶段跟踪的情况下运行。"

ER_GRP_RPL_UDF_REGISTER_ERROR
  eng "Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove it"
  chinese "无法执行组复制UDF功能的安装:%s。请检查该功能是否已存在,如果存在,请尝试将其删除"

ER_GRP_RPL_UDF_UNREGISTER_ERROR
  eng "Could not uninstall Group Replication UDF functions. Try to remove them manually if present."
  chinese "无法卸载组复制UDF功能。如果存在,请尝试手动删除它们。"

ER_GRP_RPL_UDF_REGISTER_SERVICE_ERROR
  eng "Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the plugin"
  chinese "无法执行组复制UDF功能的安装。请检查日志中的其他错误并尝试重新安装插件"

ER_GRP_RPL_SERVER_UDF_ERROR
  eng "The function '%s' failed. %s"
  chinese "函数'%s'失败。%s"

OBSOLETE_ER_CURRENT_PASSWORD_NOT_REQUIRED
  eng "Do not specify the current password while changing it for other users."
  chinese "请不要在为其他用户更改密码时指定当前密码。"

OBSOLETE_ER_INCORRECT_CURRENT_PASSWORD
  eng "Incorrect current password. Specify the correct password which has to be replaced."
  chinese "当前密码不正确。请指定必须替换的正确密码。"

OBSOLETE_ER_MISSING_CURRENT_PASSWORD
  eng "Current password needs to be specified in the REPLACE clause in order to change it."
  chinese "需要在REPLACE子句中指定当前密码才能更改它。"

ER_SERVER_WRONG_VALUE_FOR_VAR
  eng "Variable '%-.64s' can't be set to the value of '%-.200s'"
  chinese "变量'%-.64s'不能设置为'%-.200s'的值"

ER_COULD_NOT_CREATE_WINDOWS_REGISTRY_KEY
  eng "%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident."
  chinese "%s无法为%s创建新的Windows注册表项%s；继续使用以前的标识。"

ER_SERVER_GTID_UNSAFE_CREATE_DROP_TEMP_TABLE_IN_TRX_IN_SBR
  eng "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."
  chinese "语句违反GTID一致性:当@@ession.binlog_Format=STATEMENT时,在事务或事务上下文中的过程内不允许CREATE TEMPORARY TABLE和DROP TEMPORARY TABLE。"

OBSOLETE_ER_SECONDARY_ENGINE
  eng "Secondary engine operation failed. %s."
  chinese "辅助引擎操作失败。%s。"

OBSOLETE_ER_SECONDARY_ENGINE_DDL
  eng "DDLs on a table with a secondary engine defined are not allowed."
  chinese "不允许在定义了辅助引擎的表上使用DDL。"

OBSOLETE_ER_NO_SESSION_TEMP
  eng "Unable to allocate temporary tablespace for this session"
  chinese "无法为此会话分配临时表空间"

ER_XPLUGIN_FAILED_TO_SWITCH_SECURITY_CTX
  eng "Unable to switch security context to user: %s"
  chinese "无法将安全上下文切换到用户:%s"

ER_RPL_GTID_UNSAFE_ALTER_ADD_COL_WITH_DEFAULT_EXPRESSION
  eng "Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT."
  chinese "语句违反GTID一致性:ALTER TABLE...ADD COLUMN..,表达式为默认值。"

ER_UPGRADE_PARSE_ERROR
  eng "Error in parsing %s '%s'.'%s' during upgrade. %s"
  chinese "分析%s'%s'时出错。升级期间'%s'。%s"

ER_DATA_DIRECTORY_UNUSABLE
  eng "The designated data directory %s is unusable. You can remove all files that the server added to it."
  chinese "指定的数据目录%s不可用。您可以删除服务器添加到其中的所有文件。"
  bgn "Зададената папка за базата %s е неизползваема. Можете да изтриете файловете които сървъра добави в нея."

ER_LDAP_AUTH_USER_GROUP_SEARCH_ROOT_BIND
  eng "Group search rebinding via root DN: %s "
  chinese "通过根目录DN重新绑定组搜索:%s"

ER_PLUGIN_INSTALL_ERROR
  eng "Error installing plugin '%s': %s"
  chinese "安装插件'%s'时出错:%s"

ER_PLUGIN_UNINSTALL_ERROR
  eng "Error uninstalling plugin '%s': %s"
  chinese "卸载插件'%s'时出错:%s"

ER_SHARED_TABLESPACE_USED_BY_PARTITIONED_TABLE
  eng "Partitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade."
  chinese "不允许分区表'%s'使用共享表空间'%s'。请在升级前将所有分区移动到逐个表文件的表空间。"

ER_UNKNOWN_TABLESPACE_TYPE
  eng "Cannot determine the type of the tablespace named '%s'."
  chinese "无法确定名为'%s'的表空间的类型。"

ER_WARN_DEPRECATED_UTF8_ALIAS_OPTION
  eng "%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."
  chinese "%s:'UTF8'当前是字符集UTF8MB3的别名,但在将来的版本中将是UTF8MB4的别名。请考虑使用UTF8MB4以明确表示。"

ER_WARN_DEPRECATED_UTF8MB3_CHARSET_OPTION
  eng "%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead."
  chinese "%s:字符集UTF8MB3已弃用,将在将来的版本中删除。请考虑改用UTF8MB4。"

ER_WARN_DEPRECATED_UTF8MB3_COLLATION_OPTION
  eng "%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead."
  chinese "%s:'%-.64s'是不推荐使用的字符集UTF8MB3的排序规则。请考虑改用具有适当排序规则的UTF8MB4。"

ER_SSL_MEMORY_INSTRUMENTATION_INIT_FAILED
  eng "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."
  chinese "SSL库函数%s失败。这通常是由已在使用的SSL库引起的。因此,将不检测SSL内存分配。"
  bgn "Функцията от SSL библиотеката %s върна грешка. Това обикновено е защото SSL библиотеката вече е била използвана. Заради това SSL паметта няма да се инструментира."

ER_IB_MSG_MADV_DONTDUMP_UNSUPPORTED
  eng "Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platform"
  chinese "禁用@@CORE_FILE,因为@@INNODB_BUFFER_POOL_IN_CORE_FILE已禁用,但此平台不支持MADV_DONTDUMP"

ER_IB_MSG_MADVISE_FAILED
  eng "Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %s"
  chinese "正在禁用@@core_file,因为已禁用@@Innodb_Buffer_Pool_in_core_file,但mise(%p,%zu,%s)失败,返回%s"

OBSOLETE_ER_COLUMN_CHANGE_SIZE
  eng "Could not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes."
  chinese "未能更改表'%s'的列'%s'。索引'%s'的结果大小将超过最大键长度%d字节。"

ER_WARN_REMOVED_SQL_MODE
  eng "sql_mode=0x%08x has been removed and will be ignored"
  chinese "SQL_MODE=0x%08x已被删除,将被忽略"

ER_IB_MSG_FAILED_TO_ALLOCATE_WAIT
  eng "Failed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource."
  chinese "无法为大小为%zu字节的池分配内存。线程将等待%zu秒来释放资源。"

OBSOLETE_ER_IB_MSG_NUM_POOLS
  eng "Number of pools: %zu"
  chinese "池数:%zu"

ER_IB_MSG_USING_UNDO_SPACE
  eng "Using undo tablespace '%s'."
  chinese "使用撤消表空间'%s'。"

ER_IB_MSG_FAIL_TO_SAVE_SPACE_STATE
  eng "%s Unable to save the current state of tablespace '%s' to the data dictionary"
  chinese "%s无法将表空间'%s'的当前状态保存到数据字典"

ER_IB_MSG_MAX_UNDO_SPACES_REACHED
  eng "Cannot create undo tablespace %s at %s because %d undo tablespaces already exist."
  chinese "无法在%s处创建撤消表空间%s,因为已存在%d个撤消表空间。"

ER_IB_MSG_ERROR_OPENING_NEW_UNDO_SPACE
  eng "Error %d opening newly created undo tablespace %s."
  chinese "错误%d打开新创建的撤消表空间%s。"

ER_IB_MSG_FAILED_SDI_Z_BUF_ERROR
  eng "SDI Compression failed, Z_BUF_ERROR"
  chinese "SDI压缩失败,Z_BUF_ERROR"

ER_IB_MSG_FAILED_SDI_Z_MEM_ERROR
  eng "SDI Compression failed, Z_MEM_ERROR"
  chinese "SDI压缩失败,Z_MEM_ERROR"

ER_IB_MSG_SDI_Z_STREAM_ERROR
  eng "SDI Compression failed, Z_STREAM_ERROR"
  chinese "SDI压缩失败,Z_STREAM_ERROR"

ER_IB_MSG_SDI_Z_UNKNOWN_ERROR
  eng "%s"
  chinese "%s"

ER_IB_MSG_FOUND_WRONG_UNDO_SPACE
  eng "Expected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?"
  chinese "期望找到撤消表空间'%s'为空间ID=%lu,但找到的却是'%s'！您更改innodb_undo_directory了吗？"

ER_IB_MSG_NOT_END_WITH_IBU
  eng "Cannot use %s as an undo tablespace because it does not end with '.ibu'."
  chinese "不能将%s用作撤消表空间,因为它不以'.ibu'结尾。"

OBSOLETE_ER_IB_MSG_UNDO_TRUNCATE_EMPTY_FILE
  eng "ib_undo_trunc_empty_file"
  chinese "ib_undo_trunc_empty_file"

OBSOLETE_ER_IB_MSG_UNDO_INJECT_BEFORE_DD_UPDATE
  eng "ib_undo_trunc_before_dd_update"
  chinese "ib_undo_trunc_before_dd_update"

OBSOLETE_ER_IB_MSG_UNDO_INJECT_BEFORE_UNDO_LOGGING
  eng "ib_undo_trunc_before_done_logging"
  chinese "ib_undo_trunc_before_done_logging"

OBSOLETE_ER_IB_MSG_UNDO_INJECT_BEFORE_RSEG
  eng "ib_undo_trunc_before_rsegs"
  chinese "ib_undo_trunc_before_rsegs"

ER_IB_MSG_FAILED_TO_FINISH_TRUNCATE
  eng "%s Failed to finish truncating Undo Tablespace '%s'"
  chinese "%s无法完成对撤消表空间'%s'的截断"

ER_IB_MSG_DEPRECATED_INNODB_UNDO_TABLESPACES
  eng "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."
  chinese "INNODB_UNDO_TABLESPACES设置已弃用,不再使用。InnoDB始终首先创建2个撤消表空间。如果需要更多,请使用CREATE UNDO TABLESPACE。"

ER_IB_MSG_WRONG_TABLESPACE_DIR
  eng "The directory for tablespace %s does not exist or is incorrect."
  chinese "表空间%s的目录不存在或不正确。"

ER_IB_MSG_LOCK_FREE_HASH_USAGE_STATS
  eng "%s"
  chinese "%s"

ER_CLONE_DONOR_TRACE
  eng "Clone donor reported : %.512s."
  chinese "克隆捐赠者报告:%.512s。"

ER_CLONE_PROTOCOL_TRACE
  eng "Clone received unexpected response from donor : %.512s."
  chinese "克隆收到来自供方的意外响应:%.512s。"

ER_CLONE_CLIENT_TRACE
  eng "Client: %.512s."
  chinese "客户端:%.512s。"

ER_CLONE_SERVER_TRACE
  eng "Server: %.512s."
  chinese "服务器:%.512s。"

ER_THREAD_POOL_PFS_TABLES_INIT_FAILED
  eng "Failed to initialize the performance schema tables service."
  chinese "无法初始化性能架构表服务。"

ER_THREAD_POOL_PFS_TABLES_ADD_FAILED
  eng "Failed to add thread pool performance schema tables."
  chinese "无法初始化性能架构表服务。"

ER_CANT_SET_DATA_DIR
  eng "Failed to set datadir to \'%-.200s\' (OS errno: %d - %s)"
  chinese "无法将数据目录设置为\'%-.200s\'(操作系统错误号:%d - %s)"

ER_INNODB_INVALID_INNODB_UNDO_DIRECTORY_LOCATION
  eng "The innodb_undo_directory is not allowed to be an ancestor of the datadir."
  chinese "innodb_undo_directory不允许成为数据目录的祖先。"

ER_SERVER_RPL_ENCRYPTION_FAILED_TO_FETCH_KEY
  eng "Failed to fetch key from keyring, please check if keyring is loaded."
  chinese "无法从密钥环获取密钥,请检查是否加载了密钥环。"

ER_SERVER_RPL_ENCRYPTION_KEY_NOT_FOUND
  eng "Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully."
  chinese "找不到密钥环中的密钥,如果密钥环加载和初始化成功,请查看服务器日志。"

ER_SERVER_RPL_ENCRYPTION_KEYRING_INVALID_KEY
  eng "Fetched an invalid key from keyring."
  chinese "从密钥环获取了无效的密钥。"

ER_SERVER_RPL_ENCRYPTION_HEADER_ERROR
  eng "Error reading a replication log encryption header: %s."
  chinese "读取复制日志加密头时出错:%s。"

ER_SERVER_RPL_ENCRYPTION_FAILED_TO_ROTATE_LOGS
  eng "Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually."
  chinese "更改binlog加密设置后,无法轮换某些日志。请解决此问题并手动轮换日志。"

ER_SERVER_RPL_ENCRYPTION_KEY_EXISTS_UNEXPECTED
  eng "Key %s exists unexpected."
  chinese "密钥%s意外存在。"

ER_SERVER_RPL_ENCRYPTION_FAILED_TO_GENERATE_KEY
  eng "Failed to generate key, please check if keyring is loaded."
  chinese "生成密钥失败,请检查是否加载了密钥环。"

ER_SERVER_RPL_ENCRYPTION_FAILED_TO_STORE_KEY
  eng "Failed to store key, please check if keyring is loaded."
  chinese "存储密钥失败,请检查是否加载了密钥环。"

ER_SERVER_RPL_ENCRYPTION_FAILED_TO_REMOVE_KEY
  eng "Failed to remove key, please check if keyring is loaded."
  chinese "删除密钥失败,请检查是否加载了密钥环。"

ER_SERVER_RPL_ENCRYPTION_MASTER_KEY_RECOVERY_FAILED
  eng "Unable to recover binlog encryption master key, please check if keyring is loaded."
  chinese "无法恢复binlog加密主密钥,请检查是否加载了密钥环。"

ER_SERVER_RPL_ENCRYPTION_UNABLE_TO_INITIALIZE
  eng "Failed to initialize binlog encryption, please check if keyring is loaded."
  chinese "无法初始化binlog加密,请检查是否加载了密钥环。"

ER_SERVER_RPL_ENCRYPTION_UNABLE_TO_ROTATE_MASTER_KEY_AT_STARTUP
  eng "Failed to rotate binlog encryption master key at startup, please check if keyring is loaded."
  chinese "启动时无法轮换binlog加密主密钥,请检查是否加载了密钥环。"

ER_SERVER_RPL_ENCRYPTION_IGNORE_ROTATE_MASTER_KEY_AT_STARTUP
  eng "Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled."
  chinese "忽略binlog_rotate_encryption_master_key_at_startup,因为禁用了BINLOG_ENCRYPTION选项。"

ER_INVALID_ADMIN_ADDRESS
  eng "Invalid value for command line option admin-address: '%s'"
  chinese "命令行选项admin-Address的值无效:'%s'"

ER_SERVER_STARTUP_ADMIN_INTERFACE
  eng "Admin interface ready for connections, address: '%s'  port: %d"
  chinese "管理接口已准备好连接,地址:'%s',端口:%d"

ER_CANT_CREATE_ADMIN_THREAD
  eng "Can't create thread to handle admin connections (errno= %d)"
  chinese "无法创建线程来处理管理员连接(错误号=%d)"

ER_WARNING_RETAIN_CURRENT_PASSWORD_CLAUSE_VOID
  eng "RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords."
  chinese "忽略用户'%s'@'%s'的保留当前密码,因为其身份验证插件%s不支持多个密码。"

ER_WARNING_DISCARD_OLD_PASSWORD_CLAUSE_VOID
  eng "DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords."
  chinese "丢弃用户'%s'@'%s'忽略的旧密码,因为其身份验证插件%s不支持多个密码。"

OBSOLETE_ER_SECOND_PASSWORD_CANNOT_BE_EMPTY
  eng "Empty password can not be retained as second password for user '%s'@'%s'."
  chinese "空密码不能保留为用户'%s'@'%s'的第二个密码。"

OBSOLETE_ER_PASSWORD_CANNOT_BE_RETAINED_ON_PLUGIN_CHANGE
  eng "Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed."
  chinese "无法为用户'%s'@'%s'保留当前密码,因为正在更改身份验证插件。"

OBSOLETE_ER_CURRENT_PASSWORD_CANNOT_BE_RETAINED
  eng "Current password can not be retained for user '%s'@'%s' because new password is empty."
  chinese "无法为用户'%s'@'%s'保留当前密码,因为新密码为空。"

ER_WARNING_AUTHCACHE_INVALID_USER_ATTRIBUTES
  eng "Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user."
  chinese "无法从用户'%s@%s'的mysql.user表中读取和处理USER_ATTRIBUTES列的值；忽略USER。"

ER_MYSQL_NATIVE_PASSWORD_SECOND_PASSWORD_USED_INFORMATION
  eng "Second password was used for login by user: '%s'@'%s'."
  chinese "用户使用第二个密码登录:'%s'@'%s'。"

ER_SHA256_PASSWORD_SECOND_PASSWORD_USED_INFORMATION
  eng "Second password was used for login by user: '%s'@'%s'."
  chinese "用户使用第二个密码登录:'%s'@'%s'。"

ER_CACHING_SHA2_PASSWORD_SECOND_PASSWORD_USED_INFORMATION
  eng "Second password was used for login by user: '%s'@'%s'."
  chinese "用户使用第二个密码登录:'%s'@'%s'。"

ER_GRP_RPL_SEND_TRX_PREPARED_MESSAGE_FAILED
  eng "Error sending transaction '%s:%lld' prepared message from session '%u'."
  chinese "发送事务'%s:%lld'从会话'%u'准备好的消息时出错。"

ER_GRP_RPL_RELEASE_COMMIT_AFTER_GROUP_PREPARE_FAILED
  eng "Error releasing transaction '%s:%lld' for commit on session '%u' after being prepared on all group members."
  chinese "在所有组成员上做好准备后,释放事务'%s:%lld'以便在会话'%u'上提交时出错。"

ER_GRP_RPL_TRX_ALREADY_EXISTS_ON_TCM_ON_AFTER_CERTIFICATION
  eng "Transaction '%s:%lld' already exists on Group Replication consistency manager while being registered after conflict detection."
  chinese "在冲突检测后注册时,组复制一致性管理器上已存在事务'%s:%lld'。"

ER_GRP_RPL_FAILED_TO_INSERT_TRX_ON_TCM_ON_AFTER_CERTIFICATION
  eng "Error registering transaction '%s:%lld' on Group Replication consistency manager after conflict detection."
  chinese "在检测到冲突后,在组复制一致性管理器上注册事务'%s:%lld'时出错。"

ER_GRP_RPL_REGISTER_TRX_TO_WAIT_FOR_GROUP_PREPARE_FAILED
  eng "Error registering transaction '%s:%lld' from session '%u' to wait for being prepared on all group members."
  chinese "注册事务'%s:%lld'(来自会话'%u')以等待在所有组成员上准备时出错。"

ER_GRP_RPL_TRX_WAIT_FOR_GROUP_PREPARE_FAILED
  eng "Error on transaction '%s:%lld' from session '%u' while waiting for being prepared on all group members."
  chinese "等待准备所有组成员时,事务'%s:%lld'(会话'%u'中的)出错。"

ER_GRP_RPL_TRX_DOES_NOT_EXIST_ON_TCM_ON_HANDLE_REMOTE_PREPARE
  eng "Transaction '%s:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare."
  chinese "在接收远程事务准备时,组复制一致性管理器上不存在事务'%s:%lld'。"

ER_GRP_RPL_RELEASE_BEGIN_TRX_AFTER_DEPENDENCIES_COMMIT_FAILED
  eng "Error releasing transaction '%s:%lld' for execution on session '%u' after its dependencies did complete commit."
  chinese "在其依赖项完成提交后,释放事务'%s:%lld'以在会话'%u'上执行时出错。"

ER_GRP_RPL_REGISTER_TRX_TO_WAIT_FOR_DEPENDENCIES_FAILED
  eng "Error registering transaction from session '%u' to wait for its dependencies to complete commit."
  chinese "注册会话'%u'中的事务以等待其依赖项完成提交时出错。"

ER_GRP_RPL_WAIT_FOR_DEPENDENCIES_FAILED
  eng "Error on session '%u' while waiting for its dependencies to complete commit."
  chinese "等待会话'%u'的依赖项完成提交时,会话出错。"

ER_GRP_RPL_REGISTER_TRX_TO_WAIT_FOR_SYNC_BEFORE_EXECUTION_FAILED
  eng "Error registering transaction from session '%u' to wait for sync before execution."
  chinese "注册会话'%u'中的事务以在执行前等待同步时出错。"

ER_GRP_RPL_SEND_TRX_SYNC_BEFORE_EXECUTION_FAILED
  eng "Error sending sync before execution message from session '%u'."
  chinese "从会话'%u'发送执行前同步消息时出错。"

ER_GRP_RPL_TRX_WAIT_FOR_SYNC_BEFORE_EXECUTION_FAILED
  eng "Error on transaction from session '%u' while waiting for sync before execution."
  chinese "在执行前等待同步时,会话'%u'中的事务出错。"

ER_GRP_RPL_RELEASE_BEGIN_TRX_AFTER_WAIT_FOR_SYNC_BEFORE_EXEC
  eng "Error releasing transaction for execution on session '%u' after wait for sync before execution."
  chinese "在执行前等待同步之后,释放要在会话'%u'上执行的事务时出错。"

ER_GRP_RPL_TRX_WAIT_FOR_GROUP_GTID_EXECUTED
  eng "Error waiting for group executed transactions commit on session '%u'."
  chinese "等待在会话'%u'上提交组执行的事务时出错。"

OBSOLETE_ER_UNIT_NOT_FOUND SU001
  eng "There's no unit of measure named '%s'."
  chinese "没有名为'%s'的度量单位。"

OBSOLETE_ER_GEOMETRY_IN_UNKNOWN_LENGTH_UNIT SU001
  eng "The function %s uses %s as a unit, but was passed geometry without units (\"SRID 0\"). Conversion is not possible."
  chinese "函数%s使用%s作为单位,但传递的几何图形没有单位(\"SRID 0\")。无法进行转换。"

ER_WARN_PROPERTY_STRING_PARSE_FAILED
  eng "Could not parse key-value pairs in property string '%s'"
  chinese "无法分析属性字符串'%s'中的键-值对"

ER_INVALID_PROPERTY_KEY
  eng "Property key '%s' is invalid."
  chinese "属性键'%s'无效。"

ER_GRP_RPL_GTID_SET_EXTRACT_ERROR_DURING_RECOVERY
  eng "Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery."
  chinese "提取GROUP_REPLICATION_APPLIER通道收到的事务集时出错。无法确保执行在恢复期间收到的组事务。"

ER_SERVER_RPL_ENCRYPTION_FAILED_TO_ENCRYPT
  eng "Failed to encrypt content to write into binlog file: %s."
  chinese "无法加密内容以写入binlog文件:%s。"

ER_CANNOT_GET_SERVER_VERSION_FROM_TABLESPACE_HEADER
  eng "Cannot get the server version number from the dictionary tablespace header."
  chinese "无法从字典表空间标题中获取服务器版本号。"

ER_CANNOT_SET_SERVER_VERSION_IN_TABLESPACE_HEADER
  eng "Cannot set the server version number in the dictionary tablespace header."
  chinese "无法在字典表空间标题中设置服务器版本号。"

ER_SERVER_UPGRADE_VERSION_NOT_SUPPORTED
  eng "Upgrading the server from server version '%u' is not supported."
  chinese "不支持从服务器版本'%u'升级服务器。"

ER_SERVER_UPGRADE_FROM_VERSION
  eng "MySQL server upgrading from version '%u' to '%u'."
  chinese "MySQL服务器从版本'%u'升级到'%u'。"

ER_GRP_RPL_ERROR_ON_CERT_DB_INSTALL
  eng "The certification information could not be set in this server: '%s'"
  chinese "无法在此服务器中设置证书信息:'%s'"

ER_GRP_RPL_FORCE_MEMBERS_WHEN_LEAVING
  eng "A request to force a new group membership was issued when the member is leaving the group."
  chinese "当成员离开组时,发出了强制新组成员身份的请求。"

ER_TRG_WRONG_ORDER
  eng "Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table."
  chinese "触发器%s.%s(表%s.%s的)的列出顺序错误。请删除并重新创建该表的所有触发器。"

OBSOLETE_ER_SECONDARY_ENGINE_PLUGIN
  eng "%s"
  chinese "%s"

ER_LDAP_AUTH_GRP_SEARCH_NOT_SPECIAL_HDL
  eng "Special handling for group search, {GA} not found"
  chinese "组搜索的特殊处理,{GA}未找到"

ER_LDAP_AUTH_GRP_USER_OBJECT_HAS_GROUP_INFO
  eng "User group retrieval: User object has group information"
  chinese "用户组检索:用户对象具有组信息"

ER_LDAP_AUTH_GRP_INFO_FOUND_IN_MANY_OBJECTS
  eng "Group information found in multiple user objects. Search filter configuration is incorrect."
  chinese "在多个用户对象中找到组信息。搜索筛选器配置不正确。"

ER_LDAP_AUTH_GRP_INCORRECT_ATTRIBUTE
  eng "User group retrieval: no group attribute found. Incorrect group search attribute. "
  chinese "用户组检索:未找到组属性。组搜索属性不正确。"

ER_LDAP_AUTH_GRP_NULL_ATTRIBUTE_VALUE
  eng "User group retrieval: Group attribute values is NULL. "
  chinese "用户组检索:组属性值为空。"

ER_LDAP_AUTH_GRP_DN_PARSING_FAILED
  eng "User group retrieval: parsing DN failed. "
  chinese "用户组检索:解析DN失败。"

ER_LDAP_AUTH_GRP_OBJECT_HAS_USER_INFO
  eng "User group retrieval: Group object has user information"
  chinese "用户组检索:组对象具有用户信息"

ER_LDAP_AUTH_LDAPS
  eng "Reserved port for ldaps using ldaps"
  chinese "为使用ldap的ldap保留端口"

ER_LDAP_MAPPING_GET_USER_PROXY
  eng "Get user proxy"
  chinese "获取用户代理"

ER_LDAP_MAPPING_USER_DONT_BELONG_GROUP
  eng "Get user proxy: User doesn't belongs to any group, user name will be treated as authenticated user."
  chinese "获取用户代理:用户不属于任何组,用户名将被视为经过身份验证的用户。"

ER_LDAP_MAPPING_INFO
  eng "Get user proxy: configured mapping info: %s"
  chinese "获取用户代理:配置的映射信息:%s"

ER_LDAP_MAPPING_EMPTY_MAPPING
  eng "Get user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user."
  chinese "获取用户代理:用户没有组映射信息,第一个ldap组将被视为经过身份验证的用户。"

ER_LDAP_MAPPING_PROCESS_MAPPING
  eng "Process group proxy mapping"
  chinese "进程组代理映射"

ER_LDAP_MAPPING_CHECK_DELIMI_QUOTE
  eng "Check delimiter after quote"
  chinese "检查引号后的分隔符"

ER_LDAP_MAPPING_PROCESS_DELIMITER
  eng "Processing delimiter"
  chinese "处理分隔符"

ER_LDAP_MAPPING_PROCESS_DELIMITER_EQUAL_NOT_FOUND
  eng "Processing delimiter, separator = not found, resetting position"
  chinese "处理分隔符,分隔符=未找到,正在重置位置"

ER_LDAP_MAPPING_PROCESS_DELIMITER_TRY_COMMA
  eng "Processing delimiter, failed to get data for = separator try for separator ,."
  chinese "正在处理分隔符,无法为=分隔符尝试分隔符获取数据。"

ER_LDAP_MAPPING_PROCESS_DELIMITER_COMMA_NOT_FOUND
  eng "Processing delimiter, separator , not found, resetting position"
  chinese "处理分隔符、分隔符、未找到、重置位置"

ER_LDAP_MAPPING_NO_SEPEARATOR_END_OF_GROUP
  eng "Processing delimiter: No mapping separator is found, end of group information"
  chinese "处理分隔符:找不到映射分隔符,组信息结束"

ER_LDAP_MAPPING_GETTING_NEXT_MAPPING
  eng "Getting next mapping information"
  chinese "获取下一个映射信息"

ER_LDAP_MAPPING_PARSING_CURRENT_STATE
  eng "Parsing mapping, current state: %d  delimiter char: %c "

ER_LDAP_MAPPING_PARSING_MAPPING_INFO
  eng "Parsing mapping info, LDAP group: %s MySQL proxy: %s"
  chinese "正在分析映射信息,ldap组:%s MySQL代理:%s"

ER_LDAP_MAPPING_PARSING_ERROR
  eng "Mapping parsing error"
  chinese "映射解析错误"

ER_LDAP_MAPPING_TRIMMING_SPACES
  eng "Trimming left spaces"
  chinese "修剪左边的空格"

ER_LDAP_MAPPING_IS_QUOTE
  eng "Checking if current characters is quote"
  chinese "检查当前字符是否为引号"

ER_LDAP_MAPPING_NON_DESIRED_STATE
  eng "Not desired state or un-defined states."
  chinese "不是所需状态或未定义的状态。"

ER_INVALID_NAMED_PIPE_FULL_ACCESS_GROUP
  eng "Invalid value for named_pipe_full_access_group."
  chinese "NAMED_PIPE_FULL_ACCESS_GROUP的值无效。"

# This error is not supposed to be reported to the users. It is only
# meant for internal use to signal that a statement should be
# reprepared for a secondary storage engine. The error should be
# caught and handled by the server.
ER_PREPARE_FOR_SECONDARY_ENGINE
  eng "Retry the statement using a secondary storage engine."
  chinese "使用辅助存储引擎重试该语句。"

ER_SERVER_WARN_DEPRECATED
  eng "'%s' is deprecated and will be removed in a future release. Please use %s instead"
  chinese "'%s'已弃用,将在将来的版本中删除。请改用%s"
ER_AUTH_ID_WITH_SYSTEM_USER_PRIV_IN_MANDATORY_ROLES
  eng "Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege."
  chinese "无法设置MANDIAL_ROLES:AuthID`%.64s`@`%.64s`具有'%s'权限。"

ER_SERVER_BINLOG_MASTER_KEY_RECOVERY_OUT_OF_COMBINATION
  eng "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."
  chinese "无法恢复二进制日志主密钥,new_master_key_seqno=%u、master_key_seqno=%u和old_master_key_seqno=%u的组合错误。"

ER_SERVER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_CLEANUP_AUX_KEY
  eng "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."
  chinese "无法从密钥环中删除辅助二进制日志加密密钥,请检查是否加载了密钥环。二进制日志主密钥轮换过程的清理未按预期完成,清理将在服务器重新启动或下一次执行'ALTER INSTANCE ROTATE BINLOG MASTER KEY'时进行。"

OBSOLETE_ER_CANNOT_GRANT_SYSTEM_PRIV_TO_MANDATORY_ROLE
  eng "AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege."
  chinese "AuthID`%.64s`@`%.64s`被设置为MANDIRED_ROLES。无法授予'%s'特权。"

OBSOLETE_ER_PARTIAL_REVOKE_AND_DB_GRANT_BOTH_EXISTS
  eng "'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted."
  chinese "'%s'(数据库'%s')权限同时作为Partial Revke和mysql.db存在。这可能意味着'MySQL'架构已损坏。"

OBSOLETE_ER_DB_ACCESS_DENIED
  eng "Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'."
  chinese "授权ID`%.64s`@`%.64s`对数据库'%-.192s'的访问被拒绝。"

OBSOLETE_ER_PARTIAL_REVOKES_EXIST
  eng "At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON."
  chinese "数据库上至少存在一个部分撤消。必须将系统变量'@@PARTIAL_REVOKES'设置为ON。"

ER_TURNING_ON_PARTIAL_REVOKES
  eng "At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'."
  chinese "数据库上至少存在一个部分撤消。正在打开系统变量'@@PARTIAL_REVOKS'。"

ER_WARN_PARTIAL_REVOKE_AND_DB_GRANT
  eng "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."
  chinese "对于用户'%s'@'%s',通过mysql.db为数据库'%s'授予的一个或多个权限与部分撤销冲突。这可能意味着'MySQL'架构已损坏。"

ER_WARN_INCORRECT_PRIVILEGE_FOR_DB_RESTRICTIONS
  eng "For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges."
  chinese "对于用户%s,忽略了对数据库'%s'的权限'%s'的限制,因为这些权限不是有效的数据库权限。"

ER_WARN_INVALID_DB_RESTRICTIONS
  eng "For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted."
  chinese "对于用户%s,忽略对数据库'%s'的权限'%s'的限制,因为未授予相应的全局权限。"

ER_GRP_RPL_INVALID_COMMUNICATION_PROTOCOL
  eng "'%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"
  chinese "'%s'是group_replication_communication_protocol_join,的无效值,请使用5.7.14和此服务器版本之间的MySQL值"

ER_GRP_RPL_STARTED_AUTO_REJOIN
  eng "Started auto-rejoin procedure attempt %lu of %lu"
  chinese "已启动自动重新加入过程尝试%lu次,共%lu次"

ER_GRP_RPL_TIMEOUT_RECEIVED_VC_ON_REJOIN
  eng "Timeout while waiting for a view change event during the auto-rejoin procedure"
  chinese "在自动重新加入过程中等待视图更改事件时超时"

ER_GRP_RPL_FINISHED_AUTO_REJOIN
  eng "Auto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group."
  chinese "已完成自动重新加入过程尝试%lu次,共%lu次。成员%s能够加入该组。"

ER_GRP_RPL_DEFAULT_TABLE_ENCRYPTION_DIFF_FROM_GRP
  eng "The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group."
  chinese "成员配置的DEFAULT_TABLE_ENCRYPTION选项的值'%d'与组'%d'不同。该成员现在将退出该组。"

ER_SERVER_UPGRADE_OFF
  eng "Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'."
  chinese "服务器正在关闭,因为需要升级,但命令行选项'--Upgrade=None'禁止升级。"

ER_SERVER_UPGRADE_SKIP
  eng "Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'."
  chinese "服务器升级是必需的,但命令行选项'--Upgrade=Minimal'跳过了。"

ER_SERVER_UPGRADE_PENDING
  eng "Server upgrade started with version %d, but server upgrade of version %d is still pending."
  chinese "服务器升级已从版本%d开始,但版本%d的服务器升级仍处于挂起状态。"

ER_SERVER_UPGRADE_FAILED
  eng "Failed to upgrade server."
  chinese "升级服务器失败。"

ER_SERVER_UPGRADE_STATUS
  eng "Server upgrade from '%d' to '%d' %s."
  chinese "服务器从'%d'升级到'%d'%s。"

ER_SERVER_UPGRADE_REPAIR_REQUIRED
  eng "Table '%s' requires repair."
  chinese "表'%s'需要修复。"

ER_SERVER_UPGRADE_REPAIR_STATUS
  eng "Table '%s' repair %s."
  chinese "表'%s'修复%s。"

ER_SERVER_UPGRADE_INFO_FILE
  eng "Could not open server upgrade info file '%s' for writing. Please make sure the file is writable."
  chinese "无法打开服务器升级信息文件'%s'进行写入。请确保该文件可写。"

ER_SERVER_UPGRADE_SYS_SCHEMA
  eng "Upgrading the sys schema."
  chinese "升级sys架构。"

ER_SERVER_UPGRADE_MYSQL_TABLES
  eng "Running queries to upgrade MySQL server."
  chinese "运行查询以升级MySQL服务器。"

ER_SERVER_UPGRADE_SYSTEM_TABLES
  eng "Upgrading system table data."
  chinese "升级系统表数据。"

ER_SERVER_UPGRADE_EMPTY_SYS
  eng "Found empty sys database. Installing the sys schema."
  chinese "找到空的sys数据库。正在安装sys架构。"

ER_SERVER_UPGRADE_NO_SYS_VERSION
  eng "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."
  chinese "存在没有sys.version视图的sys架构。如果您有用户创建的sys架构,则必须重命名此架构才能成功升级。"

ER_SERVER_UPGRADE_SYS_VERSION_EMPTY
  eng "A sys schema exists with a sys.version view, but it returns no results."
  chinese "存在具有sys.Version视图的sys架构,但它不返回任何结果。"

ER_SERVER_UPGRADE_SYS_SCHEMA_OUTDATED
  eng "Found outdated sys schema version %s."
  chinese "发现过期的sys架构版本%s。"

ER_SERVER_UPGRADE_SYS_SCHEMA_UP_TO_DATE
  eng "The sys schema is already up to date (version %s)."
  chinese "系统架构已是最新的(版本%s)。"

ER_SERVER_UPGRADE_SYS_SCHEMA_OBJECT_COUNT
  eng "Found %d sys %s, but expected %d. Re-installing the sys schema."
  chinese "找到%d个系统%s,但需要%d。请重新安装系统架构。"

ER_SERVER_UPGRADE_CHECKING_DB
  eng "Checking '%s' schema."
  chinese "正在检查'%s'架构。"

ER_IB_MSG_DDL_LOG_DELETE_BY_ID_TMCT
  eng "Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments."
  chinese "清除DDL日志时并发事务太多。请增加回滚段的数量。"

ER_IB_MSG_POST_RECOVER_DDL_LOG_RECOVER
  eng "Error in DDL Log recovery during Post-Recovery processing."
  chinese "恢复后处理期间DDL日志恢复出错。"

ER_IB_MSG_POST_RECOVER_POST_TS_ENCRYPT
  eng "Error in Post-Tablespace-Encryption during Post-Recovery processing."
  chinese "恢复后处理期间表空间加密后出错。"

ER_IB_MSG_DDL_LOG_FAIL_POST_DDL
  eng "Error in DLL Log cleanup during Post-DDL processing."
  chinese "在后期DDL处理过程中,DLL日志清理出错。"

ER_SERVER_BINLOG_UNSAFE_SYSTEM_FUNCTION
  eng "'%s' statement is unsafe because it uses a system function that may return a different value on the replica."
  chinese "'%s'语句不安全,因为它使用的系统函数可能会在从属服务器上返回不同的值。"

ER_SERVER_UPGRADE_HELP_TABLE_STATUS
  eng "Upgrade of help tables %s."
  chinese "升级帮助表%s。"

OBSOLETE_ER_GRP_RPL_SRV_GTID_WAIT_ERROR
  eng "Error when waiting for the server to execute local transactions in order assure the group change proper logging"
  chinese "等待服务器执行本地事务以确保组更改正确记录时出错"

OBSOLETE_ER_GRP_DELAYED_VCLE_LOGGING
  eng "Unable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process."
  chinese "无法在日志中的摘要位置记录组更改视图日志事件。但这不会影响组复制恢复过程或整个插件过程。"

OBSOLETE_ER_CANNOT_GRANT_ROLES_TO_ANONYMOUS_USER
  eng "Cannot grant roles to an anonymous user."
  chinese "无法将角色授予匿名用户。"

ER_BINLOG_UNABLE_TO_ROTATE_GTID_TABLE_READONLY
  eng "Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %s"
  chinese "无法创建新的binlog文件:无法打开表`mysql.gtid_ecuted`。%s"

ER_NETWORK_NAMESPACES_NOT_SUPPORTED
  eng "Network Namespaces is not supported on this platform"
  chinese "此平台不支持网络命名空间"

ER_UNKNOWN_NETWORK_NAMESPACE
  eng "Unknown network namespace '%s'"
  chinese "未知的网络命名空间'%s'"

ER_NETWORK_NAMESPACE_NOT_ALLOWED_FOR_WILDCARD_ADDRESS
  eng "Network namespace not allowed for wildcard interface address"
  chinese "通配符接口地址不允许使用网络命名空间"

ER_SETNS_FAILED
  eng "setns() failed with error '%s'"
  chinese "setns()失败,错误为'%s'"

ER_WILDCARD_NOT_ALLOWED_FOR_MULTIADDRESS_BIND
  eng "Wildcard address value not allowed for multivalued bind address"
  chinese "多值绑定地址不允许通配符地址值"

ER_NETWORK_NAMESPACE_FILE_PATH_TOO_LONG
  eng "The path to a special network namespace file is too long. (got %u > max %u)"
  chinese "特殊网络命名空间文件的路径太长。(已获取%u>最大%u)"

ER_IB_MSG_TOO_LONG_PATH
  eng "Cannot create tablespace '%s'. The filepath is too long for this OS."
  chinese "无法创建表空间'%s'。文件路径对于此操作系统太长。"

ER_IB_RECV_FIRST_REC_GROUP_INVALID
  eng "The last block of redo had corrupted first_rec_group and became fixed (%u -> %u)."
  chinese "最后一个重做块已损坏first_rec_group并已修复(%u->%u)。"

ER_DD_UPGRADE_COMPLETED
  eng "Data dictionary upgrade from version '%u' to '%u' completed."
  chinese "已完成从版本'%u'到'%u'的数据字典升级。"

OBSOLETE_ER_SSL_SERVER_CERT_VERIFY_FAILED
  eng "Server SSL certificate doesn't verify: %s"
  chinese "服务器SSL证书未验证:%s"

ER_PERSIST_OPTION_USER_TRUNCATED
  eng "Truncated a user name for %s that was too long while reading the persisted variables file"
  chinese "已截断%s的用户名,该用户名在读取持久变量文件时太长"

ER_PERSIST_OPTION_HOST_TRUNCATED
  eng "Truncated a host name for %s that was too long while reading the persisted variables file"
  chinese "读取持久化变量文件时,%s的主机名太长,已将其截断"

ER_NET_WAIT_ERROR
  eng "The wait_timeout period was exceeded, the idle time since last command was too long."
  chinese "已超过WAIT_TIMEOUT期限,自上次命令以来的空闲时间太长。"

ER_IB_MSG_1285
  eng "'%s' found not encrypted while '%s' is ON. Trying to encrypt it now."
  chinese "发现'%s'未加密,打开'%s'时。正在尝试加密。"

ER_IB_MSG_CLOCK_MONOTONIC_UNSUPPORTED
  eng "CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !"
  chinese "不支持CLOCK_MONTOTONIC,因此不要在MySQL运行时更改系统时间！"

ER_IB_MSG_CLOCK_GETTIME_FAILED
  eng "clock_gettime() failed: %s"
  chinese "Clock_gettime()失败:%s"

ER_PLUGIN_NOT_EARLY_DUP
  eng "Plugin '%s' is not to be used as an \"early\" plugin. Don't add it to --early-plugin-load, keyring migration etc."
  chinese "插件'%s'不能用作'早期'插件。不要将其添加到--早期插件加载、密钥环迁移等。"
  bgn "Приставката '%s' не може да се използва като ранна приставка. Не я добавайте в --early-plugin-load и т.н."

ER_PLUGIN_NO_INSTALL_DUP
  eng "Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it."
  chinese "插件'%s'被标记为不可动态安装。您必须停止服务器才能安装它。"

# When using this error message, use the ER_WARN_DEPRECATED_SYNTAX error
# code.
OBSOLETE_ER_WARN_DEPRECATED_SQL_CALC_FOUND_ROWS
  eng "SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead."
  chinese "SQL_CALC_FOUND_ROWS已弃用,将在将来的版本中删除。请考虑改用两个单独的查询。"

# When using this error message, use the ER_WARN_DEPRECATED_SYNTAX error
# code.
OBSOLETE_ER_WARN_DEPRECATED_FOUND_ROWS
  eng "FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead."
  chinese "FOUND_ROWS()已弃用,将在将来的版本中删除。请考虑改用COUNT(*)。"

ER_BINLOG_UNSAFE_DEFAULT_EXPRESSION_IN_SUBSTATEMENT
  eng "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."
  chinese "该语句是不安全的,因为它调用触发器或存储函数来修改表,而该表具有默认表达式的列,该默认表达式可能会在从属数据库上返回不同的值。"

ER_GRP_RPL_MEMBER_VER_READ_COMPATIBLE
  eng "Member version is read compatible with the group."
  chinese "成员版本与组的读取兼容。"

ER_LOCK_ORDER_INIT_FAILED
  eng "Lock order disabled (reason: init failed)."
  chinese "锁定顺序已禁用(原因:init失败)。"

ER_AUDIT_LOG_KEYRING_ID_TIMESTAMP_VALUE_IS_INVALID
  eng "Keyring ID timestamp value is invalid: '%s'"
  chinese "密钥环ID时间戳值无效:'%s'"

ER_AUDIT_LOG_FILE_NAME_TIMESTAMP_VALUE_IS_MISSING_OR_INVALID
  eng "Cannot process audit log file. File name timestamp value is missing or invalid: '%s'"
  chinese "无法处理审核日志文件。缺少文件名时间戳值或该值无效:'%s'"

ER_AUDIT_LOG_FILE_NAME_DOES_NOT_HAVE_REQUIRED_FORMAT
  eng "Cannot process audit log file. File name does not have required format: '%s'"
  chinese "无法处理审核日志文件。文件名没有所需的格式:'%s'"

ER_AUDIT_LOG_FILE_NAME_KEYRING_ID_VALUE_IS_MISSING
  eng "Cannot process audit log file. File name keyring ID value is missing: '%s'"
  chinese "无法处理审核日志文件。缺少文件名密钥环ID值:'%s'"

ER_AUDIT_LOG_FILE_HAS_BEEN_SUCCESSFULLY_PROCESSED
  eng "Audit log file has been successfully processed: '%s'"
  chinese "已成功处理审核日志文件:'%s'"

ER_AUDIT_LOG_COULD_NOT_OPEN_FILE_FOR_READING
  eng "Could not open audit log file for reading: '%s'"
  chinese "无法打开审核日志文件进行读取:'%s'"

ER_AUDIT_LOG_INVALID_FILE_CONTENT
  eng "Invalid audit log file content: '%s'"
  chinese "无效的审核日志文件内容:'%s'"

ER_AUDIT_LOG_CANNOT_READ_PASSWORD
  eng "Cannot read password: '%.32s'."
  chinese "无法读取密码:'%.32s'。"

ER_AUDIT_LOG_CANNOT_STORE_PASSWORD
  eng "Cannot store password: '%.32s'."
  chinese "无法存储密码:'%.32s'。"

ER_AUDIT_LOG_CANNOT_REMOVE_PASSWORD
  eng "Cannot remove password: '%.32s'."
  chinese "无法删除密码:'%.32s'。"

ER_AUDIT_LOG_PASSWORD_HAS_BEEN_COPIED
  eng "'audit_log' password has been copied into '%.32s' and will be removed with first purged password."
  chinese "'AUDIT_LOG'密码已复制到'%.32s'中,并将与第一个清除的密码一起删除。"

OBSOLETE_ER_AUDIT_LOG_INSUFFICIENT_PRIVILEGE
  eng "Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'"
  chinese "忽略'%.64s'@'%.64s'的请求。执行操作所需的角色:'%.32s'"

OBSOLETE_ER_WRONG_MVI_VALUE
  eng "Can't store an array or an object in a scalar key part of the index '%.192s'"
  chinese "无法在索引'%.192s'的标量键部分存储数组或对象"

OBSOLETE_ER_WARN_FUNC_INDEX_NOT_APPLICABLE
  eng "Cannot use functional index '%-.64s' due to type or collation conversion"
  chinese "由于类型或归类转换,无法使用函数索引'%-.64s'"

OBSOLETE_ER_EXCEEDED_MV_KEYS_NUM
  eng "Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)"
  chinese "多值索引'%-.64s'的超过%u个值的每条记录的最大值数"

OBSOLETE_ER_EXCEEDED_MV_KEYS_SPACE
  eng "Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes"
  chinese "多值索引'%-.64s'的超过%u字节的每条记录的最大值总长度"

OBSOLETE_ER_FUNCTIONAL_INDEX_DATA_IS_TOO_LONG 22001
  eng "Data too long for functional index '%-.64s'"
  chinese "函数索引'%-.64s'的数据太长"

OBSOLETE_ER_INVALID_JSON_VALUE_FOR_FUNC_INDEX 22018
  eng "Invalid JSON value for CAST for functional index '%-.64s'"
  chinese "函数索引'%-.64s'的强制转换的JSON值无效"

OBSOLETE_ER_JSON_VALUE_OUT_OF_RANGE_FOR_FUNC_INDEX 22003
  eng "Out of range JSON value for CAST for functional index '%-.64s'"
  chinese "函数索引'%-.64s'的强制转换JSON值超出范围"

ER_LDAP_EMPTY_USERDN_PASSWORD
  eng "Empty user dn or password is not allowed, not attempting LDAP bind."
  chinese "不允许空的用户DN或密码,不尝试进行LDAP绑定。"

OBSOLETE_ER_GROUPING_ON_TIMESTAMP_IN_DST
  eng "Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query."
  chinese "对于具有DST的时区,按时间分组是不确定的。请考虑为此查询切换到UTC。"

ER_ACL_WRONG_OR_MISSING_ACL_TABLES_LOG
  eng "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."
  chinese "ACL表的当前布局不符合服务器的预期布局。它们可能已更改、丢失或未从以前的版本升级。但是,仍将尽最大努力从这些表中读取数据。"

ER_LOCK_ORDER_FAILED_WRITE_FILE
  eng "LOCK_ORDER: Failed to write to file <%s>."
  chinese "lock_order:无法写入文件<%s>。"

ER_LOCK_ORDER_FAILED_READ_FILE
  eng "LOCK_ORDER: Failed to read from file <%s>."
  chinese "LOCK_ORDER:无法从文件<%s>读取。"

ER_LOCK_ORDER_MESSAGE
  eng "LOCK_ORDER message: %s"
  chinese "LOCK_ORDER消息:%s"

ER_LOCK_ORDER_DEPENDENCIES_SYNTAX
  eng "Lock order dependencies file <%s> (%d:%d) - (%d:%d) : %s"
  chinese "锁定顺序依赖关系文件<%s>(%d:%d)-(%d:%d):%s"

ER_LOCK_ORDER_SCANNER_SYNTAX
  eng "Lock order scanner: (%d:%d) - (%d:%d) : %s"
  chinese "锁定顺序扫描程序:(%d:%d)-(%d:%d):%s"

ER_DATA_DIRECTORY_UNUSABLE_DELETABLE
  eng "The newly created data directory %s by --initialize is unusable. You can remove it."
  chinese "由--INITIALIZE新建的数据目录%s不可用。您可以将其删除。"
  bgn "Новосъздадената от --initialize папка за базата %s е неизползваема. Можете да я изтриете."

ER_IB_MSG_BTREE_LEVEL_LIMIT_EXCEEDED
  eng "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."
  chinese "为索引%s创建的B树级别数已超过允许的限制。如果正在使用调试选项Innodb_Limit_乐观_INSERT_DEBUG,请尝试调整它以在页面中包含更多记录。"

ER_IB_CLONE_START_STOP
  eng "%s"
    chinese "%s"

ER_IB_CLONE_OPERATION
  eng "%s"
    chinese "%s"

ER_IB_CLONE_RESTART
  eng "%s"
    chinese "%s"

ER_IB_CLONE_USER_DATA
  eng "Clone removing all user data for provisioning: %s"
  chinese "克隆删除要设置的所有用户数据:%s"

ER_IB_CLONE_NON_INNODB_TABLE
  eng "Non innodb table: %s.%s is not cloned and is empty."
  chinese "非Innodb表:%s.%s未克隆且为空。"

ER_CLONE_SHUTDOWN_TRACE
  eng "Clone shutting down server as RESTART failed. Please start server to complete clone operation."
  chinese "由于重新启动失败,克隆正在关闭服务器。请启动服务器以完成克隆操作。"

ER_GRP_RPL_GTID_PURGED_EXTRACT_ERROR
  eng "Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete."
  chinese "提取此成员GTID清除集时出错。对组联结器进行的操作和检查可能不完整。"

ER_GRP_RPL_CLONE_PROCESS_PREPARE_ERROR
  eng "There was an issue when configuring the remote cloning process: %s"
  chinese "配置远程克隆进程时出现问题:%s"

ER_GRP_RPL_CLONE_PROCESS_EXEC_ERROR
  eng "There was an issue when cloning from another server: %s"
  chinese "从另一台服务器克隆时出现问题:%s"

ER_GRP_RPL_RECOVERY_EVAL_ERROR
  eng "There was an issue when trying to evaluate the best distributed recovery strategy while joining.%s"
  chinese "尝试在加入时评估最佳分布式恢复策略时出现问题。%s"

ER_GRP_RPL_NO_POSSIBLE_RECOVERY
  eng "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."
  chinese "不存在有效成员或联机成员,无法从组中获取丢失的数据。对于克隆,请检查是否存在相同版本且安装了克隆插件的捐赠者。对于增量恢复,请检查是否有未从二进制日志中清除所需数据的捐赠者。"

ER_GRP_RPL_CANT_KILL_THREAD
  eng "The group replication plugin could not kill the plugin routine for %s. %s"
  chinese "组复制插件无法终止%s的插件例程。%s"

ER_GRP_RPL_RECOVERY_STRAT_CLONE_THRESHOLD
  eng "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."
  chinese "此成员将使用克隆启动分布式恢复。这是因为丢失的事务数高于配置的阈值%llu。"

ER_GRP_RPL_RECOVERY_STRAT_CLONE_PURGED
  eng "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."
  chinese "此成员将使用克隆启动分布式恢复。这是因为没有联机成员在其二进制日志中具有要恢复的丢失数据。"

ER_GRP_RPL_RECOVERY_STRAT_CHOICE
  eng "Distributed recovery will transfer data using: %s"
  chinese "分布式恢复将使用%s传输数据"

ER_GRP_RPL_RECOVERY_STRAT_FALLBACK
  eng "Due to some issue on the previous step distributed recovery is now executing: %s"
  chinese "由于上一步的一些问题,分布式恢复现在正在执行:%s"

ER_GRP_RPL_RECOVERY_STRAT_NO_FALLBACK
  eng "Due to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group."
  chinese "由于出现严重克隆错误或缺少捐赠者,无法执行分布式恢复。该成员现在将离开该组。"

ER_GRP_RPL_REPLICA_THREAD_ERROR_ON_CLONE
  eng "The '%s' thread of channel '%s' will error out as the server will attempt to clone another server"
  chinese "通道'%s'的'%s'线程将出错,因为服务器将尝试克隆另一台服务器"

ER_UNKNOWN_TABLE_IN_UPGRADE
  eng "Unknown table '%-.129s'"
  chinese "未知表'%-.129s'"

ER_IDENT_CAUSES_TOO_LONG_PATH_IN_UPGRADE
  eng "Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'."
  chinese "对象的长数据库名称和标识符导致路径长度超过%d个字符。路径:'%s'。"

ER_XA_CANT_CREATE_MDL_BACKUP
  eng "XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect."
  chinese "XA:在客户端断开连接期间,无法对准备好的XA事务进行MDL锁定备份。"

ER_AUDIT_LOG_SUPER_PRIVILEGE_REQUIRED
  eng "SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user."
  chinese "'%s'@'%s'用户需要超级特权或AUDIT_ADMIN角色。"

ER_AUDIT_LOG_UDF_INVALID_ARGUMENT_TYPE
  eng "Invalid argument type"
  chinese "参数类型无效"

ER_AUDIT_LOG_UDF_INVALID_ARGUMENT_COUNT
  eng "Invalid argument count"
  chinese "参数计数无效"

ER_AUDIT_LOG_HAS_NOT_BEEN_INSTALLED
  eng "audit_log plugin has not been installed using INSTALL PLUGIN syntax."
  chinese "尚未使用安装插件语法安装AUDIT_LOG插件。"

ER_AUDIT_LOG_UDF_READ_INVALID_MAX_ARRAY_LENGTH_ARG_TYPE
  eng "Invalid \"max_array_length\" argument type."
  chinese "无效的\"max_array_length\"参数类型。"

ER_LOG_CANNOT_WRITE_EXTENDED
  eng "Failed to write to %s: %s (%s)"
  chinese "无法写入%s:%s(%s)"

OBSOLETE_ER_UPGRADE_WITH_PARTITIONED_TABLES_REJECTED
  eng "Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information."
  chinese "在区分大小写的文件系统上从具有分区表和LOWER_CASE_TABLE_NAMES==1的服务器版本%d升级可能会导致问题,因此禁止升级。如果仍要升级,请使用命令行选项'UPGRADE=FORCE'重新启动新的服务器版本。升级完成后,请对每个分区表执行'RENAME TABLE<PART_TABLE_NAME>to<new_TABLE_NAME>；RENAME TABLE<NEW_TABLE_NAME>；'。有关详细信息,请参阅文档。"

ER_KEYRING_AWS_INCORRECT_PROXY
  eng "Incorrect environment variable %s, invalid port: %s"
  chinese "环境变量%s不正确,端口无效:%s"

ER_GRP_RPL_SERVER_SET_TO_OFFLINE_MODE_DUE_TO_ERRORS
  eng "The server was automatically set into offline mode after an error was detected."
  chinese "检测到错误后,服务器自动设置为脱机模式。"

ER_GRP_RPL_MESSAGE_SERVICE_FATAL_ERROR
  eng "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."
  chinese "通过组复制邮件传递服务发送的邮件未成功传递。服务器现在将离开该组。请尝试将服务器添加回该组并检查问题是否仍然存在,或检查日志中以前的邮件以寻找可能是问题的线索。"

ER_WARN_WRONG_COMPRESSION_ALGORITHM_LOG
  eng "Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression)."
  chinese "在存储库中找到通道'%.192s'的SOURCE_COMPRESSION_ALGRATIONS'%.192s'无效。正在重置为'UNCOMPRESSED'(无压缩)。"

ER_WARN_WRONG_COMPRESSION_LEVEL_LOG
  eng "Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u."
  chinese "在存储库中为频道'%.192s'找到无效的SOURCE_ZSTD_COMPRESSION_LEVEL。正在重置为%u。"

ER_PROTOCOL_COMPRESSION_RESET_LOG
  eng "Option --protocol-compression-algorithms is reset to default value."
  chinese "选项--PROTOCOL-COMPRESSION-ALGULTS重置为默认值。"

ER_XPLUGIN_COMPRESSION_ERROR
  eng "Fatal error while compressing outgoing data - %s"
  chinese "压缩传出数据时出现致命错误-%s"

ER_MYSQLBACKUP_MSG
  eng "%s"
  chinese "%s"

ER_WARN_UNKNOWN_KEYRING_AWS_REGION
  eng "Unknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail."
  chinese "未知的KEYRING_AWS_REGION'%.192s'。连接到AWS KMS可能会失败。"

ER_WARN_LOG_PRIVILEGE_CHECKS_USER_DOES_NOT_EXIST
  eng "PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads."
  chinese "复制通道'%.192s'的PRIVITICATION_CHECKS_USER已设置为`%.64s`@`%.255s`,但这不是现有用户。请在启动复制线程之前更正此错误。"

ER_WARN_LOG_PRIVILEGE_CHECKS_USER_CORRUPT
  eng "Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration."
  chinese "在通道'%.192s'的复制配置存储库中找到无效的、已损坏的PRIVICATION_CHECKS_USER。请使用CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER更正配置。"

ER_WARN_LOG_PRIVILEGE_CHECKS_USER_NEEDS_RPL_APPLIER_PRIV
  eng "PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads."
  chinese "复制通道'%.192s'的PRIVITICATION_CHECKS_USER已设置为`%.64s`@`%.255s`,但此用户没有REPLICATION_APPLIER权限。请在启动复制线程之前更正此问题。"

ER_OBSOLETE_FILE_PRIVILEGE_FOR_REPLICATION_CHECKS
  eng "The PRIVILEGE_CHECKS_USER for channel '%.192s' 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."
  chinese "通道'%.192s'的PRIVILEGE_CHECKS_USER需要FILE特权才能执行以语句格式复制的LOAD DATA INFILE语句。请考虑在MASTER上使用BINLOG_FORMAT=ROW。如果复制的事件是可信的,请通过将FILE临时授予PRIVILEGE_CHECKS_USER来从失败中恢复。"

ER_RPL_REPLICA_SQL_THREAD_STARTING_WITH_PRIVILEGE_CHECKS
  eng "Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512s"
  chinese "从属SQL线程%s已初始化,正在开始复制日志'%s'中的位置%s,中继日志'%s'位置:%s,用户:'%.64s'@'%.255s',角色:%.512s"

ER_AUDIT_LOG_CANNOT_GENERATE_PASSWORD
  eng "Cannot generate password: '%.32s'"
  chinese "无法生成密码:'%.32s'"

ER_INIT_FAILED_TO_GENERATE_ROOT_PASSWORD
  eng "Failed to generate a random password for root. Probabably not enough enthropy."
  chinese "无法为超级用户生成随机密码。可能是加密不够。"

ER_PLUGIN_LOAD_OPTIONS_IGNORED
  eng "Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure)."
  chinese "忽略--plugin-Load[_Add]列表,因为服务器正在使用--initialize(-insecure)运行。"

ER_WARN_AUTH_ID_WITH_SYSTEM_USER_PRIV_IN_MANDATORY_ROLES
  eng "Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored."
  chinese "无法设置MANDIAND_ROLES:AuthID`%.64s`@`%.64s`具有'%s'权限。在MANDIAND_ROLES中设置的AuthID将被忽略。"

ER_IB_MSG_SKIP_HIDDEN_DIR
  eng "Directory '%s' will not be scanned because it is a hidden directory."
  chinese "目录'%s'将不会被扫描,因为它是一个隐藏目录。"

ER_WARN_RPL_RECOVERY_NO_ROTATE_EVENT_FROM_SOURCE_EOF
  eng "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."
  chinese "服务器找不到来自主服务器的轮换事件来初始化通道'%s'的中继日志恢复。正在跳过该通道的中继日志恢复。"

ER_IB_LOB_ROLLBACK_INDEX_LEN
  eng "Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)"
  chinese "正在回滚事务%llu撤消编号%llu的LOB:当前索引长度%llu。(迭代%llu)"

ER_CANT_PROCESS_EXPRESSION_FOR_GENERATED_COLUMN_TO_DD
  eng "Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64s"
  chinese "处理(可能已弃用)表达式或函数'%.128s'时为生成的列%.64s.%.64s.%.64s出错"

ER_RPL_REPLICA_QUEUE_EVENT_FAILED_INVALID_NON_ROW_FORMAT
  eng "The queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found."
  chinese "通道'%s'的队列事件失败,因为根据REQUIRED_ROW_FORMAT找到了无效事件。"

ER_OBSOLETE_REQUIRE_ROW_FORMAT_VIOLATION
  eng "The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found."
  chinese "由于找到了根据REQUIRED_ROW_FORMAT的无效事件,通道'%s'的中继事件应用失败。"

ER_LOG_PRIV_CHECKS_REQUIRE_ROW_FORMAT_NOT_SET
  eng "PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d."
  chinese "否则无法将复制通道'%.192s'的PRIVICATION_CHECKS_USER设置为`%.64s`@`%.255s`除非REQUIRED_ROW_FORMAT也设置为%d。"

ER_RPL_REPLICA_SQL_THREAD_DETECTED_UNEXPECTED_EVENT_SEQUENCE
  eng "An unexpected event sequence was detected by the SQL thread while applying an event."
  chinese "应用事件时,SQL线程检测到意外事件序列。"

ER_IB_MSG_UPGRADE_PARTITION_FILE
  eng "Updating partition file name '%s' to '%s' and all other partition files during upgrade"
  chinese "在升级过程中将分区文件名'%s'更新为'%s'以及所有其他分区文件"

ER_IB_MSG_DOWNGRADE_PARTITION_FILE
  eng "Updating partition file name '%s' to '%s' and all other partition files during downgrade"
  chinese "在降级过程中将分区文件名'%s'更新为'%s'以及所有其他分区文件"

ER_IB_MSG_UPGRADE_PARTITION_FILE_IMPORT
  eng "Updating partition file name '%s' to '%s' for import"
  chinese "正在将分区文件名'%s'更新为'%s'以进行导入"

ER_IB_WARN_OPEN_PARTITION_FILE
  eng "Unable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths"
  chinese "无法打开新名称为'%s'的分区文件。请检查是否将Innodb_DIRECTORIES设置为包括所有外部文件路径"

ER_IB_MSG_FIL_STATE_MOVED_CORRECTED
  eng "%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'"
  chinese "%s DD ID:%llu-分区表空间%u,名称'%s'已更正为'%s'"

ER_IB_MSG_FIL_STATE_MOVED_CHANGED_PATH
  eng "%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'"
  chinese "%s DD ID:%llu-表空间%u,名称'%s','%s'已移动到'%s'"

ER_IB_MSG_FIL_STATE_MOVED_CHANGED_NAME
  eng "%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'"
  chinese "%s DD ID:%llu-分区表空间%u,名称'%s','%s'更新为'%s'"

ER_IB_MSG_FIL_STATE_MOVED_TOO_MANY
  eng "%s Too many files have been moved, disabling logging of detailed messages"
  chinese "%s移动的文件太多,无法记录详细消息"

ER_GR_ELECTED_PRIMARY_GTID_INFORMATION
  eng "Elected primary member %s: %s"
  chinese "当选的主要成员%s:%s"

ER_SCHEMA_NAME_IN_UPPER_CASE_NOT_ALLOWED
  eng "Schema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1."
  chinese "当LOWER_CASE_TABLE_NAMES=1时,不允许架构名称'%s'包含大写字符。"

ER_TABLE_NAME_IN_UPPER_CASE_NOT_ALLOWED
  eng "Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1."
  chinese "当LOWER_CASE_TABLE_NAMES=1时,不允许包含大写字符的表名'%s.%s'。"

ER_SCHEMA_NAME_IN_UPPER_CASE_NOT_ALLOWED_FOR_FK
  eng "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."
  chinese "当LOWER_CASE_TABLE_NAMES=1时,不允许包含大写字符的架构名称'%s'由外键'%s'(表'%s.%s'中的)使用。"

ER_TABLE_NAME_IN_UPPER_CASE_NOT_ALLOWED_FOR_FK
  eng "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."
  chinese "当LOWER_CASE_TABLE_NAMES=1时,不允许包含大写字符的表名'%s.%s'由外键'%s'(表'%s.%s'中的)使用。"

ER_IB_MSG_DICT_PARTITION_NOT_FOUND
  eng "Table Partition: %s is not found in InnoDB dictionary"
  chinese "在InnoDB词典中找不到表分区:%s"

ER_ACCESS_DENIED_FOR_USER_ACCOUNT_BLOCKED_BY_PASSWORD_LOCK
  eng "Access denied for user '%-.48s'@'%-.64s'. 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."
  chinese "用户'%-.48s'@'%-.64s'的访问被拒绝。帐户被阻止%s天(剩余%s天)由于连续%u次登录失败。请使用刷新权限或更改用户来重置。"

ER_INNODB_OUT_OF_RESOURCES
  eng "%s"
  chinese "%s"

OBSOLETE_ER_DD_UPGRADE_FOUND_PREPARED_XA_TRANSACTION
  eng "Upgrade cannot proceed due to an existing prepared XA transaction."
  chinese "由于现有的已准备好的XA事务,升级无法继续。"

ER_MIGRATE_TABLE_TO_DD_OOM
  eng "Could not allocate memory for key_info when migrating table %s.%s"
  chinese "迁移表%s.%s时,无法为KEY_INFO分配内存。"

ER_RPL_RELAY_LOG_RECOVERY_INFO_AFTER_CLONE
  eng "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'"
  chinese "克隆操作后找到通道'%s'的中继日志信息。将执行中继日志恢复以调整此新服务器的位置和文件信息。如果自动过程失败,请通过'更改主服务器到'来调整位置"

ER_IB_MSG_57_UNDO_SPACE_DELETE_FAIL
  eng "Failed to delete 5.7 undo tablespace: %s during upgrade"
  chinese "升级期间无法删除5.7还原表空间:%s"

ER_IB_MSG_DBLWR_1285
  eng "Empty doublewrite file: %s"
  chinese "空的双重写入文件:%s"

ER_IB_MSG_DBLWR_1286
  eng "Using '%s' for doublewrite"
  chinese "使用'%s'进行双重写入"

ER_IB_MSG_DBLWR_1287
  eng  "Error reading doublewrite buffer from the system tablespace"
  chinese "从SYSTEM表空间读取双写缓冲区时出错"

ER_IB_MSG_DBLWR_1288
  eng "Cannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation."
  chinese "无法创建双写缓冲区:您必须增加缓冲池大小。无法继续操作。"

ER_IB_MSG_DBLWR_1290
  eng "The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6"
  chinese "双重写入文件中的页面已损坏。无法继续操作。您可以尝试使用Innodb_force_Recovery=6恢复数据库。"

ER_IB_MSG_BAD_DBLWR_FILE_NAME
  eng "The doublewrite filename '%s' is incorrect."
  chinese "双重写入文件名'%s'不正确。"

OBSOLETE_ER_IB_MSG_DBLWR_1292
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1293
  eng "Doublewrite file create failed: %s"
  chinese "双重写入文件创建失败:%s"

ER_IB_MSG_DBLWR_1294
  eng "DBLWRThread: pthread_setaffinity() failed!"
  chinese "DBLWRThread:pthline_setapherity()失败！"

ER_IB_MSG_DBLWR_1295
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1296
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1297
  eng "Doublewrite file read failed: %s"
  chinese "双重写入文件读取失败:%s"

ER_IB_MSG_DBLWR_1298
  eng "Dump of the data file page:"
  chinese "转储数据文件页:"

ER_IB_MSG_DBLWR_1300
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1301
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1304
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1305
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1306
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1307
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1308
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1309
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1310
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1311
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1312
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1313
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1314
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1315
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1316
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1317
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1318
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_LOAD_WRONG_SIZE
  eng "Doublewrite load file %s size %llu is not a multiple of the configured page size %zu"
  chinese "双重写入加载文件%s大小%llu不是配置的页面大小%zu的倍数"

ER_IB_MSG_DBLWR_1320
  eng "Doublewrite file %s truncate failed"
  chinese "双重写入文件%s截断失败"

ER_IB_MSG_DBLWR_1321
  eng "Doublewrite file %s failed to writ zeros"
  chinese "双重写入文件%s写入零失败"

ER_IB_MSG_DBLWR_OPEN_OR_CREATE_WRONG_SIZE
  eng "Doublewrite open or create file %s size %llu is not a multiple of the configured page size %zu"
  chinese "双重写入创建文件%s大小%llu不是配置的页面大小%zu的倍数"

ER_IB_MSG_DBLWR_1323
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1324
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1325
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1326
  eng "%s"
  chinese "%s"

ER_IB_MSG_DBLWR_1327
  eng "%s"
  chinese "%s"

ER_IB_MSG_GTID_FLUSH_AT_SHUTDOWN
  eng "Could not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts."
  chinese "在缓慢关机期间无法刷新所有GTID。将在服务器重新启动时恢复GTID。"

ER_IB_MSG_57_STAT_SPACE_DELETE_FAIL
  eng "Failed to delete 5.7 stat tablespace: %s during upgrade"
  chinese "升级期间无法删除5.7状态表空间:%s"

ER_NDBINFO_UPGRADING_SCHEMA
  eng "Installing ndbinfo schema version %s"
  chinese "正在安装nDBINFO架构版本%s"

ER_NDBINFO_NOT_UPGRADING_SCHEMA
  eng "Installed ndbinfo schema is current. Not upgrading."
  chinese "已安装的nDBINFO架构是最新的。未升级。"

ER_NDBINFO_UPGRADING_SCHEMA_FAIL
  eng "Failed to upgrade ndbinfo schema."
  chinese "无法升级ndbinfo架构。"

OBSOLETE_ER_IB_MSG_CREATE_LOG_FILE
  eng "%s"
  chinese "%s"

ER_IB_MSG_INNODB_START_INITIALIZE
  eng "InnoDB initialization has started."
  chinese "InnoDB初始化已开始。"

ER_IB_MSG_INNODB_END_INITIALIZE
  eng "InnoDB initialization has ended."
  chinese "InnoDB初始化已结束。"

ER_IB_MSG_PAGE_ARCH_NO_RESET_POINTS
  eng "Could not find appropriate reset points."
  chinese "找不到适当的重置点。"

ER_IB_WRN_PAGE_ARCH_FLUSH_DATA
  eng "Unable to flush. Page archiving data may be corrupt in case of a crash."
  chinese "无法刷新。在崩溃的情况下,页面存档数据可能已损坏。"

ER_IB_ERR_PAGE_ARCH_INVALID_DOUBLE_WRITE_BUF
  eng "Page archiver's doublewrite buffer for %ld is not valid."
  chinese "%ld 的页面存档器的双重写入缓冲区无效。"

ER_IB_ERR_PAGE_ARCH_RECOVERY_FAILED
  eng "Page archiver system's recovery failed."
  chinese "页面存档程序系统的恢复失败。"

ER_IB_ERR_PAGE_ARCH_INVALID_FORMAT
  eng "Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*."
  chinese "无效的存档文件名格式。存档文件的格式应为%s+[0-9]*。"

ER_INVALID_XPLUGIN_SOCKET_SAME_AS_SERVER
  eng "X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket"
  chinese "X Plugins Unix Socket必须使用与MySQL服务器不同的文件。X Plugins将无法通过Unix Socket访问"

ER_INNODB_UNABLE_TO_ACQUIRE_DD_OBJECT
  eng "%s"
  chinese "%s"

OBSOLETE_ER_WARN_LOG_DEPRECATED_PARTITION_PREFIX_KEY
  eng "Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release."
  chinese "分区函数忽略了列'%.64s.%.64s.%.64s'具有前缀关键字部分'%.64s(%u)'的。不建议在PARTITION BY KEY()子句中使用带前缀的列,并将在将来的版本中删除这些列。"

ER_IB_MSG_UNDO_TRUNCATE_TOO_OFTEN
  eng "Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size."
  chinese "撤消截断发生得太频繁。请考虑增加--Innodb-max-Undo-log-Size。"

ER_GRP_RPL_IS_STARTING
  eng "Plugin 'group_replication' is starting."
  chinese "插件'GROUP_REPLICATION'正在启动。"

ER_IB_MSG_INVALID_LOCATION_FOR_TABLESPACE
  eng "Cannot create tablespace %s because the directory is not a valid location. %s"
  chinese "无法创建表空间%s,因为该目录不是有效位置。%s"

ER_IB_MSG_INVALID_LOCATION_WRONG_DB
  eng "Scanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema."
  chinese "无法打开扫描的文件'%s'(表空间'%s'的),因为它不在以架构命名的子目录中。"

ER_IB_MSG_CANNOT_FIND_DD_UNDO_SPACE
  eng "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."
  chinese "找不到撤消表空间%s(如数据字典所示,文件名为'%s'的)。您是否移动或删除了此表空间？其中的任何撤消日志都无法使用。"

ER_GRP_RPL_RECOVERY_ENDPOINT_FORMAT
  eng "Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)."
  chinese "恢复套接字终结点'%s'的输入值无效。请提供以逗号分隔的有效终结点列表(IP:port)。"

ER_GRP_RPL_RECOVERY_ENDPOINT_INVALID
  eng "The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints."
  chinese "服务器没有侦听终结点'%s'。只有服务器正在侦听的终结点才是有效的恢复终结点。"

ER_GRP_RPL_RECOVERY_ENDPOINT_INVALID_DONOR_ENDPOINT
  eng "Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped."
  chinese "从提供方接收到无效的恢复终结点配置。此成员不是有效的恢复提供方,因此将跳过它。"

ER_GRP_RPL_RECOVERY_ENDPOINT_INTERFACES_IPS
  eng "Failed to retrieve IP addresses from enabled host network interfaces."
  chinese "无法从启用的主机网络接口检索IP地址。"

ER_WARN_TLS_CHANNEL_INITIALIZATION_ERROR
  eng "Failed to initialize TLS for channel: %s. See below for the description of exact issue."
  chinese "无法初始化通道%s的TLS。有关确切问题的说明,请参阅下面的内容。"

ER_XPLUGIN_FAILED_TO_VALIDATE_ADDRESS
  eng "Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value."
  chinese "设置为`Mysqlx_BIND_Address`的值'%s'的验证失败:%s。正在跳过此值。"

ER_XPLUGIN_FAILED_TO_BIND_INTERFACE_ADDRESS
  eng "Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value."
  chinese "值'%s'设置为`Mysqlx_BIND_Address`,X插件无法绑定到它。正在跳过此值。"

ER_IB_ERR_RECOVERY_REDO_DISABLED
  eng "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"
  chinese "禁用InnoDB重做日志记录时服务器被关闭。数据文件可能已损坏。您可以尝试使用Innodb_force_Recovery=6重新启动数据库"

ER_IB_WRN_FAST_SHUTDOWN_REDO_DISABLED
  eng "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."
  chinese "InnoDB无法执行冷关闭'Innodb_fast_Shutdown=2',并在禁用重做日志记录时强制执行'Innodb_fast_Shutdown=1'。InnoDB将刷新所有脏页以确保物理数据一致性。"

ER_IB_WRN_REDO_DISABLED
  eng "InnoDB redo logging is disabled. All data could be lost in case of a server crash."
  chinese "InnoDB重做日志记录已禁用。如果服务器崩溃,所有数据可能会丢失。"

ER_IB_WRN_REDO_ENABLED
  eng "InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash."
  chinese "InnoDB重做日志记录已启用。数据现在是安全的,可以在服务器崩溃的情况下恢复。"

ER_TLS_CONFIGURED_FOR_CHANNEL
  eng "Channel %s configured to support TLS. Encrypted connections are now supported for this channel."
  chinese "通道%s配置为支持TLS。此通道现在支持加密连接。"

ER_TLS_CONFIGURATION_REUSED
  eng "No TLS configuration was given for channel %s; re-using TLS configuration of channel %s."
  chinese "没有为通道%s提供TLS配置；正在重新使用通道%s的TLS配置。"

ER_IB_TABLESPACE_PATH_VALIDATION_SKIPPED
  eng "Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!"
  chinese "正在跳过InnoDB表空间路径验证。将不会检测到手动移动的表空间文件！"

ER_IB_CANNOT_UPGRADE_WITH_DISCARDED_TABLESPACES
  eng "Upgrade failed because database contains discarded tablespaces."
  chinese "升级失败,因为数据库包含丢弃的表空间。"

ER_USERNAME_TRUNKATED
  eng "The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated."
  chinese "用户名'%s'超过了允许的最大字符数%d,已被中继。"

ER_HOSTNAME_TRUNKATED
  eng "The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated."
  chinese "主机名'%s'超过了允许的最大字符数%d,已被中继。"

ER_IB_MSG_TRX_RECOVERY_ROLLBACK_NOT_COMPLETED
  eng "Rollback of non-prepared transactions not completed, due to fast shutdown"
  chinese "由于快速关闭,未准备事务的回滚未完成"

ER_AUTHCACHE_ROLE_EDGES_IGNORED_EMPTY_NAME
  eng "Found an entry in the 'role_edges' table with empty authorization ID; Skipped"
  chinese "在'ROLE_EDGES'表中找到一个授权ID为空的条目；已跳过"

ER_AUTHCACHE_ROLE_EDGES_UNKNOWN_AUTHORIZATION_ID
  eng "Found an entry in the 'role_edges' table with unknown authorization ID '%s'; Skipped"
  chinese "在'ROLE_EDGES'表中找到一个具有未知授权ID'%s'的条目；已跳过"

ER_AUTHCACHE_DEFAULT_ROLES_IGNORED_EMPTY_NAME
  eng "Found an entry in the 'default_roles' table with empty authorization ID; Skipped"
  chinese "在'DEFAULT_ROLES'表中找到一个授权ID为空的条目；已跳过"

ER_AUTHCACHE_DEFAULT_ROLES_UNKNOWN_AUTHORIZATION_ID
  eng "Found an entry in the 'default_roles' table with unknown authorization ID '%s'; Skipped"
  chinese "在'DEFAULT_ROLES'表中找到一个具有未知授权ID'%s'的条目；已跳过"

ER_IB_ERR_DDL_LOG_INSERT_FAILURE
  eng "Couldn't insert entry in ddl log for ddl."
  chinese "无法在DDL日志中为DDL插入条目。"

ER_IB_LOCK_VALIDATE_LATCH_ORDER_VIOLATION
  eng "%s"
  chinese "%s"

ER_IB_RELOCK_LATCH_ORDER_VIOLATION
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_1352
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_1353
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_1354
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_1355
  eng "%s"
  chinese "%s"

OBSOLETE_ER_IB_MSG_1356
  eng "%s"
  chinese "%s"

ER_IB_MSG_1357
  eng "%s"
  chinese "%s"

ER_IB_MSG_1358
  eng "%s"
  chinese "%s"

ER_IB_MSG_1359
  eng "%s"
  chinese "%s"

ER_IB_FAILED_TO_DELETE_TABLESPACE_FILE
  eng "%s"
  chinese "%s"

ER_IB_UNABLE_TO_EXPAND_TEMPORARY_TABLESPACE_POOL
  eng "%s"
  chinese "%s"

ER_IB_TMP_TABLESPACE_CANNOT_CREATE_DIRECTORY
  eng "%s"
  chinese "%s"

ER_IB_MSG_SCANNING_TEMP_TABLESPACE_DIR
  eng "%s"
  chinese "%s"

ER_IB_ERR_TEMP_TABLESPACE_DIR_DOESNT_EXIST
  eng "%s"
  chinese "%s"

ER_IB_ERR_TEMP_TABLESPACE_DIR_EMPTY
  eng "%s"
  chinese "%s"

ER_IB_ERR_TEMP_TABLESPACE_DIR_CONTAINS_SEMICOLON
  eng "%s"
  chinese "%s"

ER_IB_ERR_TEMP_TABLESPACE_DIR_SUBDIR_OF_DATADIR
  eng "%s"
  chinese "%s"

ER_IB_ERR_SCHED_SETAFFNINITY_FAILED
  eng "%s"
  chinese "%s"

ER_IB_ERR_UNKNOWN_PAGE_FETCH_MODE
  eng "%s"
  chinese "%s"

ER_IB_ERR_LOG_PARSING_BUFFER_OVERFLOW
  eng "%s"
  chinese "%s"

ER_IB_ERR_NOT_ENOUGH_MEMORY_FOR_PARSE_BUFFER
  eng "%s"
  chinese "%s"

ER_IB_MSG_1372
  eng "%s"
  chinese "%s"

ER_IB_MSG_1373
  eng "%s"
  chinese "%s"

ER_IB_MSG_1374
  eng "%s"
  chinese "%s"

ER_IB_MSG_1375
  eng "%s"
  chinese "%s"

ER_IB_ERR_ZLIB_UNCOMPRESS_FAILED
  eng "%s"
  chinese "%s"

ER_IB_ERR_ZLIB_BUF_ERROR
  eng "%s"
  chinese "%s"

ER_IB_ERR_ZLIB_MEM_ERROR
  eng "%s"
  chinese "%s"

ER_IB_ERR_ZLIB_DATA_ERROR
  eng "%s"
  chinese "%s"

ER_IB_ERR_ZLIB_UNKNOWN_ERROR
  eng "%s"
  chinese "%s"

ER_IB_MSG_1381
  eng "%s"
  chinese "%s"

ER_IB_ERR_INDEX_RECORDS_WRONG_ORDER
  eng "%s"
  chinese "%s"

ER_IB_ERR_INDEX_DUPLICATE_KEY
  eng "%s"
  chinese "%s"

ER_IB_ERR_FOUND_N_DUPLICATE_KEYS
  eng "%s"
  chinese "%s"

ER_IB_ERR_FOUND_N_RECORDS_WRONG_ORDER
  eng "%s"
  chinese "%s"

ER_IB_ERR_PARALLEL_READ_OOM
  eng "%s"
  chinese "%s"

ER_IB_MSG_UNDO_MARKED_ACTIVE
  eng "The state of undo tablespace %s is set to active implicitly."
  chinese "撤消表空间%s的状态已隐式设置为ACTIVE。"

ER_IB_MSG_UNDO_ALTERED_ACTIVE
  eng "The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE."
  chinese "ALTER TABLESPACE将撤消表空间%s的状态设置为'ACTIVE'。"

ER_IB_MSG_UNDO_ALTERED_INACTIVE
  eng "The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE."
  chinese "ALTER TABLESPACE将撤消表空间%s的状态设置为'Inactive'。"

ER_IB_MSG_UNDO_MARKED_EMPTY
  eng "The state of undo tablespace %s is set to 'empty'."
  chinese "撤消表空间%s的状态设置为'Empty'。"

ER_IB_MSG_UNDO_TRUNCATE_DELAY_BY_CLONE
  eng "Delaying truncate of undo tablespace %s due to clone activity."
  chinese "由于克隆活动,正在延迟撤消表空间%s的截断。"

ER_IB_MSG_UNDO_TRUNCATE_DELAY_BY_MDL
  eng "Delaying truncate of undo tablespace %s due to a metadata lock."
  chinese "由于元数据锁定,正在延迟还原表空间%s的截断。"

ER_IB_MSG_INJECT_CRASH
  eng "Injected debug crash point: %s"
  chinese "注入调试崩溃点:%s"

ER_IB_MSG_INJECT_FAILURE
  eng "Injected debug failure point: %s"
  chinese "插入调试故障点:%s"

ER_GRP_RPL_TIMEOUT_RECEIVED_VC_LEAVE_ON_REJOIN
  eng "Timeout while waiting for a view change event during the leave step before a auto-rejoin attempt."
  chinese "在尝试自动重新加入之前,在离开步骤期间等待视图更改事件时超时。"

ER_RPL_ASYNC_RECONNECT_FAIL_NO_SOURCE
  eng "Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s."
  chinese "无法自动重新连接到通道'%s'的另一个源,因为%s。要修复此问题,请执行%s操作。"

ER_UDF_REGISTER_SERVICE_ERROR
  eng "Could not execute the installation of UDF functions. Check for other errors in the log"
  chinese "无法执行UDF函数的安装。请检查日志中的其他错误"

ER_UDF_REGISTER_ERROR
  eng "Could not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it."
  chinese "无法执行UDF函数%s的安装。请检查该函数是否已存在,如果存在,请尝试将其删除。"

ER_UDF_UNREGISTER_ERROR
  eng "Could not uninstall UDF functions. Try to remove them manually if present."
  chinese "无法卸载UDF函数。如果存在,请尝试手动删除它们。"

ER_EMPTY_PRIVILEGE_NAME_IGNORED
  eng "An empty or illegal privilege identifier was ignored when global privileges were read from disk."
  chinese "从磁盘读取全局权限时,忽略了空的或非法的权限标识符。"

ER_IB_MSG_INCORRECT_SIZE
  eng "%s"
  chinese "%s"

ER_TMPDIR_PATH_TOO_LONG
  eng "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."
  chinese "对于此操作系统,tmpdir临时路径\"%s\"太长(>%zu)。这将不会为长度为%zu的临时文件名留下足够的空间。"

ER_ERROR_LOG_DESTINATION_NOT_A_FILE
  eng "Error-log destination \"%s\" is not a file. Can not restore error log messages from previous run."
  chinese "错误-日志目标\"%s\"不是文件。无法还原上次运行的错误日志消息。"

ER_NO_ERROR_LOG_PARSER_CONFIGURED
  eng "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."
  chinese "使用--LOG-ERROR-SERVICES=...选择的日志接收器都不提供日志解析器。服务器将无法在PERFORMANCE_SCHEA.ERROR_LOG中提供以前运行的错误日志。"

ER_UPGRADE_NONEXISTENT_SCHEMA
  eng "The schema \"%.64s\" referenced by %.16s \"%.128s\" does not exist. Please clean up any orphan %.16s before upgrading."
  chinese "架构\"%.64s\"(%.16s\"%.128s\"引用的)不存在。请在升级前清除所有孤立的%.16s。"

ER_IB_MSG_CREATED_UNDO_SPACE
  eng "Created undo tablespace '%s'."
  chinese "已创建撤消表空间'%s'。"

ER_IB_MSG_DROPPED_UNDO_SPACE
  eng "Dropped undo tablespace '%s'."
  chinese "已删除撤消表空间'%s'。"

ER_IB_MSG_MASTER_KEY_ROTATED
  eng "The InnoDB Encryption Master Key has been rotated in %d tablespaces."
  chinese "InnoDB加密主密钥已在%d个表空间中轮换。"

ER_IB_DBLWR_DECOMPRESS_FAILED
  eng "Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted."
  chinese "无法解压缩DBLWR页(错误=%d)。原始大小为%d。报告dblwr页已损坏。"

ER_IB_DBLWR_DECRYPT_FAILED
  eng "Decrypting a page in doublewrite file failed: %s."
  chinese "解密双重写入文件中的页面失败:%s。"

ER_IB_DBLWR_KEY_MISSING
  eng "Encryption key missing: %s."
  chinese "缺少加密密钥:%s。"

ER_INNODB_IO_WRITE_ERROR_RETRYING
  eng "I/O error while writing to file: %s. Retrying ..."
  chinese "写入文件时出现I/O错误:%s。正在重试..."

ER_INNODB_IO_WRITE_FAILED
  eng "Failed to write data to file: %s"
  chinese "无法将数据写入文件:%s"

ER_LOG_COMPONENT_CANNOT_INIT
  eng "Log component %s failed to initialize."
  chinese "日志组件%s初始化失败。"

ER_RPL_ASYNC_CHANNEL_CANT_CONNECT
  eng "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."
  chinese "监视器IO线程无法连接到(主机:%s端口:%u网络命名空间:%s)的通道'%s'的源,因此它将尝试连接到另一个源。"

ER_RPL_ASYNC_SENDER_ADDED
  eng  "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."
  chinese "(主机:%s端口:%u网络名称空间:%s)的通道'%s'的源已加入组(GROUP_NAME:%s),因此将其条目添加到REPLICATION_ASNCHRONCE_CONNECTION_FAILOVER表中。"

ER_RPL_ASYNC_SENDER_REMOVED
  eng "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."
  chinese "(主机:%s端口:%u网络名称空间:%s)的通道'%s'的源已离开组(GROUP_NAME:%s),因此已从REPLICATION_ASNCHRON_CONNECTION_FAILOVER表中删除其条目。"

ER_RPL_ASYNC_CHANNEL_STOPPED_QUORUM_LOST
  eng "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."
  chinese "监视器IO线程检测到源(主机:%s端口:%u网络命名空间:%s)不属于组多数,因此通道'%s'将尝试连接到另一个源。"

ER_RPL_ASYNC_CHANNEL_CANT_CONNECT_NO_QUORUM
  eng "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."
  chinese "IO线程检测到源(主机:%s端口:%u网络命名空间:%s)不属于组多数,因此通道'%s'将尝试连接到另一个源。"

OBSOLETE_ER_RPL_ASYNC_EXECUTING_QUERY
  eng "%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'."
  chinese "%s的源(主机:%s端口:%u网络命名空间:%s)在通道'%s'上。"

ER_RPL_REPLICA_MONITOR_IO_THREAD_EXITING
  eng "Replica Monitor IO thread exiting."
  chinese "正在退出副本监视器IO线程。"

ER_RPL_ASYNC_MANAGED_NAME_REMOVED
  eng "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."
  chinese "(GROUP_NAME:%s)的通道'%s'的组已被删除,因此已从replication_asynchronous_connection_failover_managed中删除其条目,并从REPLICATION_ASNCHRONCE_CONNECTION_FAILOVER表中删除所有组成员。"

ER_RPL_ASYNC_MANAGED_NAME_ADDED
  eng "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."
  chinese "(GROUP_NAME:%s)已添加通道'%s'的组,因此将其在replication_asynchronous_connection_failover_managed和SOURCE中的条目添加到REPLICATION_ASNCHRONCE_CONNECTION_FAILOVER表中。"

ER_RPL_ASYNC_READ_FAILOVER_TABLE
  eng "Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table."
  chinese "从REPLICATION_ASNCHRONCE_CONNECTION_FAILOVER表中读取通道'%s'的故障切换源时出错。"

ER_RPL_REPLICA_MONITOR_IO_THREAD_RECONNECT_CHANNEL
  eng "Error %s the channel '%s', the operation will be automatically retried."
  chinese "错误%s通道'%s',该操作将自动重试。"

ER_REPLICA_ANON_TO_GTID_IS_LOCAL_OR_UUID_AND_GTID_MODE_NOT_ON
  eng "Replication channel '%.192s' 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'."
  chinese "复制通道'%.192s'配置了ASSIGN_GTID_TO_ANNOWARY_TRANSACTIONS='%s',当GTID_MODE<>打开时,这是无效的。如果您打算在任何地方使用GTID_MODE=ON,请更改为ASSIGN_GTID_TO_ANNOWARY_TRANSACTIONS=OFF并使用在线启用GTID的过程(请参阅文档)。如果您打算在此复制副本上使用GTID,但无法在源上启用GTID,请启用GTID_MODE=ON,并保留ASSIGN_GTID_TO_ANNOWARY_TRANSACTIONS=LOCAL|<uuid>。如果您打算在复制拓扑中根本不使用GTID,请更改为ASSIGN_GTID_TO_ANNOWARY_TRANSACTIONS=OFF,并保留GTID_MODE='%s'。"

ER_REPLICA_ANONYMOUS_TO_GTID_UUID_SAME_AS_GROUP_NAME
  eng "Replication channel '%.192s' 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."
  chinese "复制通道'%.192s'配置了ASSIGN_GTID_TO_ANNOWARY_TRANSACTIONS='%s',它等于GROUP_REPLICATION_GROUP_NAME。若要解决此问题,请更改GROUP_REPLICATION_GROUP_NAME或使用ASSIGN_GTID_TO_ANONYONY_TRANSACTIONS的其他值。"

ER_GRP_RPL_GRP_NAME_IS_SAME_AS_ANONYMOUS_TO_GTID_UUID
  eng "The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channel"
  chinese "GROUP_REPLICATION_GROUP_NAME'%s'与服务器通道中ASSIGN_GTID_TO_ANNOWARY_TRANSACTIONS的UUID值相同"

ER_WARN_GTID_THRESHOLD_BREACH
  eng "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."
  chinese "GTID号的整数部分太高。建议使用新的SERVER_UUID重新启动服务器,以防止其达到最大值2^63-1,这将使其无法写入二进制日志并调用binlog_error_action指定的行为。"

ER_HEALTH_INFO
  eng "%s"
  chinese "%s"

ER_HEALTH_WARNING
  eng "%s"
  chinese "%s"

ER_HEALTH_ERROR
  eng "%s"
  chinese "%s"

ER_HEALTH_WARNING_DISK_USAGE_LEVEL_1
  eng "%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"
  chinese "%s:警告级别1(%llu MiB):装入点='%s',可用=%llu MiB,总数=%llu MiB,已用=%.2f%%,下限=%llu MiB,关键级别=%llu MiB"

ER_HEALTH_WARNING_DISK_USAGE_LEVEL_2
  eng "%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"
  chinese "%s:警告级别2(%llu MiB):装入点='%s',可用=%llu MiB,总数=%llu MiB,已用=%.2f%%,下限=%llu MiB,关键级别=%llu MiB"

ER_HEALTH_WARNING_DISK_USAGE_LEVEL_3
  eng "%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"
  chinese "%s:警告级别3(%llu MiB):装入点='%s',可用=%llu MiB,总数=%llu MiB,已用=%.2f%%,下限=%llu MiB,关键级别=%llu MiB"

ER_IB_INNODB_TBSP_OUT_OF_SPACE
  eng "InnoDB: Size of tablespace %s is more than the maximum size allowed."
  chinese "InnoDB:表空间%s的大小超过了允许的最大大小。"

ER_GRP_RPL_APPLIER_CHANNEL_STILL_RUNNING
  eng "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."
  chinese "GROUP_REPLICATION_APPLIER通道仍在运行,很可能它正在等待阻止通道停止的数据库/表锁。请检查数据库/表锁,包括由备份工具创建的锁。"

ER_RPL_ASYNC_RECONNECT_GTID_MODE_OFF_CHANNEL
  eng "Detected misconfiguration: replication channel \'%.192s\' 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 \'%.192s\', or change GTID_MODE to value ON, before starting the replica receiver thread."
  chinese "检测到配置错误:复制通道\'%.192s\'配置为SOURCE_CONNECTION_AUTO_FAILOVER=1,但服务器是使用--GTID-MODE=ON以外的值启动的。在启动副本接收器线程之前,请使用Change REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER=0为通道\'%.192s\'重新配置复制,或将GTID_MODE更改为值ON。"

ER_FIREWALL_SERVICES_NOT_ACQUIRED
  eng "Could not acquire required component services."
  chinese "无法获取所需的组件服务。"

ER_FIREWALL_UDF_REGISTER_FAILED
  eng "Automatic registration of function(s) failed."
  chinese "自动注册函数失败。"

ER_FIREWALL_PFS_TABLE_REGISTER_FAILED
  eng "Automatic registration of Performance schema table(s) failed."
  chinese "自动注册性能架构表失败。"

ER_IB_MSG_STATS_SAMPLING_TOO_LARGE
  eng "%s"
  chinese "%s"

ER_AUDIT_LOG_FILE_PRUNE_FAILED
  eng "Failed to auto-prune file '%s', Error (%d): %s"
  chinese "无法自动清理文件'%s',错误(%d):%s"

ER_AUDIT_LOG_FILE_AUTO_PRUNED
  eng "File '%s' auto-pruned"
  chinese "文件'%s'已自动修剪"

ER_COMPONENTS_INFRASTRUCTURE_MANIFEST_INIT
  eng "Received an error while processing components from manifest file: %s"
  chinese "处理清单文件中的组件时收到错误:%s"

ER_COMPONENTS_INFRASTRUCTURE_MANIFEST_DEINIT
  eng "Received an error while unloading components read from manifest file: %s"
  chinese "卸载从清单文件读取的组件时收到错误:%s"

ER_WARN_COMPONENTS_INFRASTRUCTURE_MANIFEST_NOT_RO
  eng "Manifest file '%s' is not read-only. For better security, please make sure that the file is read-only."
  chinese "清单文件'%s'不是只读的。为了更好的安全性,请确保该文件为只读。"

ER_WARN_NO_KEYRING_COMPONENT_SERVICE_FOUND
  eng "No suitable '%s' service implementation found to fulfill the request."
  chinese "找不到合适的'%s'服务实现来满足请求。"

ER_NOTE_KEYRING_COMPONENT_INITIALIZED
  eng "Keyring component initialized successfully."
  chinese "Keyring组件已成功初始化。"

ER_KEYRING_COMPONENT_NOT_INITIALIZED
  eng "The component is not initialized properly. Error: %s. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component."
  chinese "组件未正确初始化。错误信息：%s。请确保配置正确并使用ALTER INSTANCE RELOAD KEYRING重新初始化组件。"

ER_KEYRING_COMPONENT_EXCEPTION
  eng "Keyring component encountered an exception while executing : '%s' API of service: '%s'"
  chinese "Keyring组件在执行时遇到异常:'%s'服务的API:'%s'"

ER_KEYRING_COMPONENT_MEMORY_ALLOCATION_ERROR
  eng "Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'"
  chinese "执行时无法为'%s'分配内存:'%s'服务的API:'%s'"

ER_NOTE_KEYRING_COMPONENT_AES_INVALID_MODE_BLOCK_SIZE
  eng "Empty or 0 values for AES encryption mode and/or block size are not permitted."
  chinese "不允许AES加密模式和/或块大小的值为空或0。"

ER_NOTE_KEYRING_COMPONENT_AES_DATA_IDENTIFIER_EMPTY
  eng "A valid data identifier is required in order to fetch the key required for the AES operation."
  chinese "需要有效的数据标识符才能获取AES操作所需的密钥。"

ER_NOTE_KEYRING_COMPONENT_AES_INVALID_KEY
  eng "Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES."
  chinese "由数据ID'%s'和身份验证ID'%s'标识的密钥不是AES类型。"

ER_NOTE_KEYRING_COMPONENT_AES_OPERATION_ERROR
  eng "Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'."
  chinese "遇到错误:'%s'执行KEYRING_AES服务的'%s'API时。密钥详细信息是数据ID:'%s'和身份验证ID:'%s'。"

ER_NOTE_KEYRING_COMPONENT_READ_DATA_NOT_FOUND
  eng "Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'."
  chinese "找不到与数据ID:'%s'、身份验证ID:'%s'对应的数据。"

ER_NOTE_KEYRING_COMPONENT_WRITE_MAXIMUM_DATA_LENGTH
  eng "Maximum permissible size of data is '%zu' bits"
  chinese "允许的最大数据大小为'%zu'位"

ER_NOTE_KEYRING_COMPONENT_STORE_FAILED
  eng "Error writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error."
  chinese "为数据ID:'%s',身份验证ID:'%s'写入数据时出错。数据已存在,且具有相同的标识符,或者密钥环后端遇到错误。"

ER_NOTE_KEYRING_COMPONENT_REMOVE_FAILED
  eng "Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error."
  chinese "删除数据ID:'%s'、身份验证ID:'%s'的数据时出错。数据不存在,具有相同的标识符,或者密钥环后端遇到错误。"

ER_NOTE_KEYRING_COMPONENT_GENERATE_FAILED
  eng "Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error."
  chinese "为数据ID:'%s',身份验证ID:'%s'生成数据时出错。数据已存在,且具有相同的标识符,或者密钥环后端遇到错误。"

ER_NOTE_KEYRING_COMPONENT_KEYS_METADATA_ITERATOR_FETCH_FAILED
  eng "Failed to get metadata from current keys metadata iterator position."
  chinese "无法从当前关键字元数据迭代器位置获取元数据。"

ER_NOTE_KEYRING_COMPONENT_METADATA_ITERATOR_INVALID_OUT_PARAM
  eng "Key and value length parameters must not be null."
  chinese "键和值长度参数不能为空。"

ER_IB_WRN_FAILED_TO_ACQUIRE_SERVICE
  eng "Innodb could not acquire service : %s"
  chinese "Innodb无法获取服务:%s"

ER_IB_WRN_OLD_GEOMETRY_TYPE
  eng "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."
  chinese "类型为GEOMETRY的列%s是旧的(5.6)格式,将来可能会弃用。若要将格式更改为最新格式,请考虑在升级后重新生成表。"

ER_NET_WAIT_ERROR2
  eng "'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long."
  chinese "'WAIT_TIMEOUT'时间段%s已被超过%s。自上次命令以来的空闲时间太长。"

ER_GRP_RPL_MEMBER_ACTION_TRIGGERED
  eng "The member action \"%s\" for event \"%s\" with priority \"%u\" will be run."
  chinese "成员操作\"%s\"(事件\"%s\"的,优先级为\"%u\")将运行。"

ER_GRP_RPL_MEMBER_ACTION_FAILURE_IGNORE
  eng "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."
  chinese "成员操作\"%s\"(事件\"%s\"的,优先级为\"%u\")失败,按照指示忽略此错误。请查看错误日志中以前的消息,了解可能导致此失败的原因。"

ER_GRP_RPL_MEMBER_ACTION_FAILURE
  eng "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."
  chinese "成员操作\"%s\"(事件\"%s\"的,优先级为\"%u\")失败。请查看错误日志中以前的消息,以获取有关可能导致此失败的原因的提示。"

ER_GRP_RPL_MEMBER_ACTION_PARSE_ON_RECEIVE
  eng "Unable to parse the member actions configuration sent by the primary."
  chinese "无法解析主服务器发送的成员操作配置。"

ER_GRP_RPL_MEMBER_ACTION_UPDATE_ACTIONS
  eng "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'."
  chinese "无法使用主服务器发送的成员操作配置来更新成员操作配置。请检查表'mySQL.Replication_GROUP_MEMBER_ACTIONS'和'mysql.replication_group_configuration_version'."

ER_GRP_RPL_MEMBER_ACTION_GET_EXCHANGEABLE_DATA
  eng "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'."
  chinese "在更改组成员身份的过程中无法读取成员操作配置。请检查表'mySQL.Replication_GROUP_MEMBER_ACTIONS'和'mysql.replication_group_configuration_version'."

ER_GRP_RPL_MEMBER_ACTION_DEFAULT_CONFIGURATION
  eng "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."
  chinese "此成员加入了一个所有成员都不支持成员操作的组,因此它确实将其成员配置重置为默认配置。"

ER_GRP_RPL_MEMBER_ACTION_UNABLE_TO_SET_DEFAULT_CONFIGURATION
  eng "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'."
  chinese "无法将成员联接上的默认配置重置为成员操作。请检查表'mySQL.Replication_GROUP_MEMBER_ACTIONS'和'mysql.replication_group_configuration_version'."

ER_GRP_RPL_MEMBER_ACTION_PARSE_ON_MEMBER_JOIN
  eng "Unable to parse the member actions configuration sent by the group on member join."
  chinese "无法分析组在成员加入时发送的成员操作配置。"

ER_GRP_RPL_MEMBER_ACTION_UPDATE_ACTIONS_ON_MEMBER_JOIN
  eng "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'."
  chinese "无法更新成员联接上的成员操作配置。请检查表'mySQL.Replication_GROUP_MEMBER_ACTIONS'和'mysql.replication_group_configuration_version'."

ER_GRP_RPL_MEMBER_ACTION_INVALID_ACTIONS_ON_MEMBER_JOIN
  eng "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."
  chinese "组成员无法发送其成员操作配置。请检查所有成员上的表'mySQL.Replication_GROUP_MEMBER_ACTIONS'和'mysql.replication_group_configuration_version'。"

ER_GRP_RPL_MEMBER_ACTION_ENABLED
  eng "Member action enabled: \"%s\", type: \"%s\", event: \"%s\", priority: \"%u\", error_handling: \"%s\"."
  chinese "成员操作已启用:\"%s\",类型:\"%s\",事件:\"%s\",优先级:\"%u\",错误处理:\"%s\"。"

ER_GRP_RPL_MEMBER_ACTION_DISABLED
  eng "Member action disabled: \"%s\", type: \"%s\", event: \"%s\", priority: \"%u\", error_handling: \"%s\"."
  chinese "成员操作已禁用:\"%s\",类型:\"%s\",事件:\"%s\",优先级:\"%u\",错误处理:\"%s\"。"

ER_GRP_RPL_MEMBER_ACTIONS_RESET
  eng "Member actions configuration was reset."
  chinese "成员操作配置已重置。"

OBSOLETE_ER_DEPRECATED_TLS_VERSION_SESSION
  eng "Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`"
  chinese "接受已弃用协议'%s'的帐户'%s'@`%s'(来自主机`%s')的连接。客户端提供了用户名'%s'"

OBSOLETE_ER_WARN_DEPRECATED_TLS_VERSION_FOR_CHANNEL
  eng "A deprecated TLS version %s is enabled for channel %s"
  chinese "已启用了已弃用的TLS版本%s(为通道%s)"

ER_FIREWALL_DEPRECATED_USER_PROFILE
  eng "User profile \'%s\' loaded. Firewall user profiles are deprecated, consider migrating to group profiles."
  chinese "已加载用户配置文件\'%s\'。防火墙用户配置文件已弃用,请考虑迁移到组配置文件。"

ER_GRP_RPL_VIEW_CHANGE_UUID_INVALID
  eng "Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID."
  chinese "GROUP_REPLICATION_VIEW_CHANGE_UUID'%s'的输入值无效。请提供有效的UUID。"

ER_GRP_RPL_VIEW_CHANGE_UUID_SAME_AS_GROUP_NAME
  eng "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."
  chinese "变量'GROUP_REPLICATION_VIEW_CHANGE_UUID'不能设置为值'%s'。如果要将UUID'GROUP_REPLICATION_GROUP_NAME'用于VIEW_CHANGE_LOG_EVENTS的UUID,请将'GROUP_REPLICATION_VIEW_CHANGE_UUID'设置为AUTOMATIC。"

ER_GRP_RPL_GROUP_NAME_SAME_AS_VIEW_CHANGE_UUID
  eng "group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATIC"
  chinese "GROUP_REPLICATION_GROUP_NAME'%s',与GROUP_REPLICATION_VIEW_CHANGE_UUID相同。请将GROUP_REPLICATION_VIEW_CHANGE_UUID更改为AUTOMATIC"

ER_GRP_RPL_VIEW_CHANGE_UUID_IS_SAME_AS_ANONYMOUS_TO_GTID_UUID
  eng "The group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channel"
  chinese "GROUP_REPLICATION_VIEW_CHANGE_UUID '%s'与服务器通道中ASSIGN_GTID_TO_ANNOWARY_TRANSACTIONS的UUID值相同"

ER_GRP_RPL_GRP_VIEW_CHANGE_UUID_IS_INCOMPATIBLE_WITH_SERVER_UUID
  eng "group_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s."
  chinese "GROUP_REPLICATION_VIEW_CHANGE_UUID与GROUP不兼容。GROUP_REPLICATION_VIEW_CHANGE_UUID%s与SERVER_UUID %s匹配。"

ER_GRP_RPL_VIEW_CHANGE_UUID_DIFF_FROM_GRP
  eng "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."
  chinese "该成员配置了GROUP_REPLICATION_VIEW_CHANGE_UUID选项值'%s',该值与组'%s'不同。该成员现在将退出该组。"

ER_WARN_REPLICA_ANONYMOUS_TO_GTID_UUID_SAME_AS_VIEW_CHANGE_UUID
  eng "Replication channel '%.192s' 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."
  chinese "复制通道'%.192s'配置了ASSIGN_GTID_TO_ANNOWARY_TRANSACTIONS='%s',它等于GROUP_REPLICATION_VIEW_CHANGE_UUID。若要解决此问题,请更改GROUP_REPLICATION_VIEW_CHANGE_UUID,或为ASSIGN_GTID_TO_ANONOWARY_TRANSACTIONS使用不同的值。"

ER_GRP_RPL_FAILED_TO_PARSE_THE_VIEW_CHANGE_UUID
  eng "Unable to parse the group_replication_view_change_uuid."
  chinese "无法分析GROUP_REPLICATION_VIEW_CHANGE_UUID。"

ER_GRP_RPL_FAILED_TO_GENERATE_SIDNO_FOR_VIEW_CHANGE_UUID
  eng "Unable to generate sidno for group_replication_view_change_uuid."
  chinese "无法为GROUP_REPLICATION_VIEW_CHANGE_UUID生成SIDNO。"

ER_GRP_RPL_VIEW_CHANGE_UUID_PARSE_ERROR
  eng "Unable to parse the group_replication_view_change_uuid during the Certification module initialization."
  chinese "无法在证书模块初始化期间分析GROUP_REPLICATION_VIEW_CHANGE_UUID。"

ER_GRP_RPL_UPDATE_GRPGTID_VIEW_CHANGE_UUID_EXECUTED_ERROR
  eng "Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization."
  chinese "在证书模块初始化过程中,使用VIEW CHANGE UUID更新GROUP_GTID_EXECUTE GTID集时出错。"

ER_GRP_RPL_ADD_VIEW_CHANGE_UUID_TO_GRP_SID_MAP_ERROR
  eng "Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization."
  chinese "在证书模块初始化期间,无法在group_gtid_sid_map中添加GROUP_REPLICATION_VIEW_CHANGE_UUID SIDNO。"

ER_GRP_RPL_DONOR_VIEW_CHANGE_UUID_TRANS_INFO_ERROR
  eng "Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error."
  chinese "初始化冲突检测组件时,无法处理原服务器的视图更改UUID事务信息。可能是内存不足错误。"

ER_WARN_GRP_RPL_VIEW_CHANGE_UUID_FAIL_GET_VARIABLE
  eng "Unable to retrieve group_replication_view_change_uuid during server checks on replication operations."
  chinese "在服务器检查复制操作期间,无法检索GROUP_REPLICATION_VIEW_CHANGE_UUID。"

ER_WARN_ADUIT_LOG_MAX_SIZE_AND_PRUNE_SECONDS_LOG
  eng "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"
  chinese "AUDIT_LOG_MAX_SIZE和AUDIT_LOG_PRUNE_Second均设置为非零。AUDIT_LOG_MAX_SIZE优先,而AUDIT_LOG_PRUNE_SECONDS被忽略"

ER_WARN_ADUIT_LOG_MAX_SIZE_CLOSE_TO_ROTATE_ON_SIZE_LOG
  eng "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."
  chinese "AUDIT_LOG_ROTATE_ON_SIZE对于提供的AUDIT_LOG_MAX_SIZE的值不够精细。应至少小%d倍。"

ER_PLUGIN_INVALID_TABLE_DEFINITION
  eng "Invalid table definition for '%s.%s'."
  chinese "'%s.%s'的表定义无效。"

ER_AUTH_KERBEROS_LOGGER_GENERIC_MSG
  eng "%s"
  chinese "%s"

ER_INSTALL_PLUGIN_CONFLICT_LOG
  eng "Cannot install the %.192s plugin when the %.192s plugin is installed."
  chinese "安装%.192s插件时,无法安装%.192s插件。"

ER_DEPRECATED_PERSISTED_VARIABLE_WITH_ALIAS
  eng "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."
  chinese "变量%s已重命名为%s,旧名称已弃用。在保留的变量文件中只找到旧名称。下次保存该文件时,这两个名称都将被存储。发出任何Set Persistent命令以保存该文件,消除此警告,并为将来版本中删除变量时的保留配置做好准备。"

ER_LOG_COMPONENT_FLUSH_FAILED
  eng "%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."
  chinese "%d个错误日志记录组件刷新失败。对于基于文件的日志,当日志文件的路径或权限已更改时,可能会发生这种情况。刷新基于文件的日志失败可能会影响日志轮换。"

ER_IB_MSG_REENCRYPTED_TABLESPACE_KEY
  eng "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."
  chinese "%s的表空间密钥已使用最新的InnoDB主密钥重新加密。但是,我们建议您重建表以获得更好的安全性。"

ER_IB_MSG_REENCRYPTED_GENERAL_TABLESPACE_KEY
  eng "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."
  chinese "%s的表空间密钥已使用最新的InnoDB主密钥重新加密。但是,我们建议您重新加密表空间以提高安全性。"

ER_IB_ERR_PAGE_ARCH_DBLWR_INIT_FAILED
  eng "Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information."
  chinese "页面存档程序的双重写入缓冲区初始化失败。页面跟踪有丢失跟踪信息的风险。"

ER_IB_MSG_RECOVERY_NO_SPACE_IN_REDO_LOG__SKIP_IBUF_MERGES
  eng "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."
  chinese "恢复期间重做日志中没有足够的可用空间来执行挂起的IBUF合并。请使用--Innodb-force-Recovery=4重试启动MySQL。"

ER_IB_MSG_RECOVERY_NO_SPACE_IN_REDO_LOG__UNEXPECTED
  eng "There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6)."
  chinese "在恢复、从备份恢复(或使用--Innodb-force-Recovery=6重试)期间,重做日志中没有足够的可用空间。"

ER_WARN_AUDIT_LOG_FORMAT_UNIX_TIMESTAMP_ONLY_WHEN_JSON_LOG
  eng "audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON."
  chinese "AUDIT_LOG_FORMAT_UNIX_TIMESTAMP仅在AUDIT_LOG_FORMAT=JSON时适用。"

# This error is not supposed to be reported to the users. It is only
# meant for internal use to signal that a statement should be
# reprepared for the primary storage engine, without transformations.
# The error should be caught and handled by the server.
ER_PREPARE_FOR_PRIMARY_ENGINE
  eng "Retry the statement using the primary storage engine."
  chinese "使用主存储引擎重试该语句。"

ER_IB_MSG_PAR_RSEG_INIT_COMPLETE_MSG
  eng "Parallel initialization of rseg complete"
  chinese "rseg的并行初始化完成"

ER_IB_MSG_PAR_RSEG_INIT_TIME_MSG
  eng "Time taken to initialize rseg using %u thread: %u ms."
  chinese "使用%u线程初始化rseg所用的时间:%u毫秒。"

ER_DDL_MSG_1
  eng "DDL failed to create a thread to load an index, fall back to single thread"
  chinese "DDL无法创建用于加载索引的线程,请回退到单个线程"

ER_MTR_MSG_1
  eng "Debug_check_no_latching failed, slot->type=%d"
  chinese "DEBUG_CHECK_NO_LATCHING失败,slot->type=%d"

ER_GRP_RPL_MYSQL_NETWORK_PROVIDER_CLIENT_ERROR_CONN_ERR
  eng "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."
  chinese "未能在组复制中建立MySQL客户端连接。建立连接时出错。请参阅手册以确保您正确配置了组复制以使用MySQL协议连接。"

ER_GRP_RPL_MYSQL_NETWORK_PROVIDER_CLIENT_ERROR_COMMAND_ERR
  eng "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."
  chinese "未能在组复制中建立MySQL客户端连接。发送连接委派命令时出错。请参阅手册以确保您正确配置了组复制以使用MySQL协议连接。"

ER_GRP_RPL_FAILOVER_CONF_GET_EXCHANGEABLE_DATA
  eng "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'."
  chinese "在更改组成员身份期间无法读取复制故障转移通道配置。请检查表'mysql.replication_asynchronous_connection_failover','mysql.replication_asynchronous_connection_failover_managed'和'mysql.replication_group_configuration_version'."

ER_GRP_RPL_FAILOVER_CONF_DEFAULT_CONFIGURATION
  eng "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."
  chinese "此成员加入的组中的所有成员都不支持组复制上的复制故障切换通道集成,因此它确实将其复制故障切换通道配置重置为默认配置。"

ER_GRP_RPL_FAILOVER_CONF_UNABLE_TO_SET_DEFAULT_CONFIGURATION
  eng "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'."
  chinese "无法在成员加入时重置到复制故障转移通道默认配置。请检查表'mysql.replication_asynchronous_connection_failover','mysql.replication_asynchronous_connection_failover_managed'和'mysql.replication_group_configuration_version'."

ER_GRP_RPL_FAILOVER_CONF_PARSE_ON_MEMBER_JOIN
  eng "Unable to parse the replication failover channels configuration sent by the group on member join."
  chinese "无法分析组在成员加入时发送的复制故障转移通道配置。"

ER_GRP_RPL_FAILOVER_CONF_CHANNEL_DOES_NOT_EXIST
  eng "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."
  chinese "无法在不存在或配置错误的复制通道'%s'上设置SOURCE_CONNECTION_AUTO_FAILOVER,请创建该通道并将服务器重新加入该组。"

ER_GRP_RPL_FAILOVER_REGISTER_MESSAGE_LISTENER_SERVICE
  eng "Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'."
  chinese "无法将侦听器'replication_asynchronous_connection_failover_configuration'注册到服务'GROUP_REPLICATION_MESSAGE_SERVICE_RECV'。"

ER_GRP_RPL_FAILOVER_PRIMARY_WITHOUT_MAJORITY
  eng "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."
  chinese "此服务器无法访问组中的大多数成员。此服务器将跳过复制故障转移通道处理,直到此服务器返回到组多数。"

ER_GRP_RPL_FAILOVER_PRIMARY_BACK_TO_MAJORITY
  eng "This server is back to the group majority. Replication failover channels handling is resumed."
  chinese "此服务器已返回到组多数。复制故障转移通道处理已恢复。"

ER_RPL_INCREMENTING_MEMBER_ACTION_VERSION
  eng "Error incrementing member action configuration version for %s.%s table."
  chinese "递增%s.%s表的成员操作配置版本时出错。"

ER_GRP_RPL_REPLICA_THREAD_ERROR_ON_SECONDARY_MEMBER
  eng "The '%s' thread of channel '%s' will error out as this server is a group secondary."
  chinese "'%s'线程(通道'%s'的)将出错,因为此服务器是组辅助服务器。"

ER_IB_MSG_CLONE_DDL_NTFN
  eng "Clone DDL Notification: %s"
  chinese "DDL克隆通知:%s"

ER_IB_MSG_CLONE_DDL_APPLY
  eng "Clone DDL APPLY: %s"
  chinese "应用克隆DDL:%s"

ER_IB_MSG_CLONE_DDL_INVALIDATE
  eng "Clone DDL Invalidate : %s"
  chinese "克隆DDL无效:%s"

ER_IB_MSG_UNDO_ENCRYPTION_INFO_LOADED
  eng "Encryption key is loaded for undo tablespace '%s'."
  chinese "已为撤消表空间'%s'加载加密密钥。"

ER_IB_WRN_ENCRYPTION_INFO_SIZE_MISMATCH
  eng "Ignoring encryption INFO size in redo log: %zu, expected: %zu"
  chinese "忽略重做日志中的加密信息大小:%zu,预期:%zu"

ER_INVALID_AUTHENTICATION_POLICY
  eng "Option --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid."
  chinese "选项--authentication-policy设置为无效值。请检查指定的身份验证插件是否有效。"

ER_AUTHENTICATION_PLUGIN_REGISTRATION_FAILED
  eng "Signature verification failed during registration."
  chinese "注册过程中签名验证失败。"

ER_AUTHENTICATION_PLUGIN_REGISTRATION_INSUFFICIENT_BUFFER
  eng "Buffer too small to hold registration challenge response."
  chinese "缓冲区太小,无法保存注册质询响应。"

ER_AUTHENTICATION_PLUGIN_AUTH_DATA_CORRUPT
  eng "FIDO device authenticator data corrupt."
  chinese "FIDO设备验证器数据损坏。"

ER_AUTHENTICATION_PLUGIN_SIGNATURE_CORRUPT
  eng "FIDO device signature corrupt."
  chinese "FIDO设备签名损坏。"

ER_AUTHENTICATION_PLUGIN_VERIFY_SIGNATURE_FAILED
  eng "Signature verification failed during authentication."
  chinese "身份验证过程中签名验证失败。"

ER_AUTHENTICATION_PLUGIN_OOM
  eng "Out of memory."
  chinese "内存不足。"

ER_AUTHENTICATION_PLUGIN_LOG
  eng "Can't initialize logging service."
  chinese "无法初始化日志记录服务。"

ER_WARN_REPLICA_GTID_ONLY_AND_GTID_MODE_NOT_ON
  eng "Replication channel '%.192s' 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."
  chinese "复制通道'%.192s'配置为GTID_ONLY=1,当GTID_MODE<>打开时无效。如果要在复制拓扑中禁用GTID,请将GTID_ONLY更改为0。"

ER_WARN_L_DISABLE_GTID_ONLY_WITH_SOURCE_AUTO_POS_INVALID_POS
  eng "The replication positions relative to the source may be out-of-date on channel '%.192s', 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."
  chinese "由于使用了GTID_ONLY=1,通道'%.192s'上相对于源的复制位置可能已过期。在某些情况下,仍可使用过期的位置,因此,为了更新它们,我们建议您开始复制以接收并应用至少一个事务,这会将位置设置为有效值。"

ER_RPL_CANNOT_OPEN_RELAY_LOG
  eng "Could not open relay log: %s"
  chinese "无法打开中继日志:%s"

ER_AUTHENTICATION_OCI_PLUGIN_NOT_INITIALIZED
  eng "Authentication plugin not initialized."
  chinese "身份验证插件未初始化。"

ER_AUTHENTICATION_OCI_PRIVATE_KEY_ERROR
  eng "Cannot use the generated private key file."
  chinese "无法使用生成的私钥文件。"

ER_AUTHENTICATION_OCI_DOWNLOAD_PUBLIC_KEY
  eng "Unavailable public key with fingerprint %s for user %s in tenancy %s ."
  chinese "指纹%s(用户%s的,租户%s中的)的公钥不可用。"

ER_AUTHENTICATION_OCI_IMDS
  eng "Cannot obtain the OCI configuration from the IMDS service."
  chinese "无法从IMDS服务获取OCI配置。"

ER_AUTHENTICATION_OCI_IAM
  eng "Cannot initialize the IAM service."
  chinese "无法初始化IAM服务。"

ER_AUTHENTICATION_OCI_INVALID_AUTHENTICATION_STRING
  eng "Invalid authentication string details for user: `%s`@`%s`."
  chinese "用户`%s`@`%s`的身份验证字符串详细信息无效。"

ER_AUTHENTICATION_OCI_NO_MATCHING_GROUPS
  eng "None of the groups returned by IAM matches any of the entries from authentication string."
  chinese "IAM返回的组与身份验证字符串中的任何条目都不匹配。"

ER_AUTHENTICATION_OCI_NO_GROUPS_FOUND
  eng "User is not part of any groups. However, account is configured to use group mapping."
  chinese "用户不属于任何组。但是,帐户配置为使用组映射。"

ER_AUTHENTICATION_OCI_NONCE
  eng "Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s ."

ER_HEALTH_WARNING_MEMORY_USAGE_LEVEL_1
  eng "%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB"
  chinese "%s: 警告级别1 (%llu MiB): 可用=%llu MiB, 总计=%llu MiB, 已用=%.2f%%, mysqld=%llu MiB"

ER_HEALTH_WARNING_MEMORY_USAGE_LEVEL_2
  eng "%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB"
  chinese "%s: 警告级别2 (%llu MiB): 可用=%llu MiB, 总计=%llu MiB, 已用=%.2f%%, mysqld=%llu MiB"

ER_HEALTH_WARNING_MEMORY_USAGE_LEVEL_3
  eng "%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB"
  chinese "%s: 警告级别3 (%llu MiB): 可用=%llu MiB, 总计=%llu MiB, 已用=%.2f%%, mysqld=%llu MiB"

ER_GRP_RPL_SET_SINGLE_CONSENSUS_LEADER
  eng "The member %s:%u, with UUID: %s, was set as the single preferred consensus leader."
  chinese "成员%s:%u(UUID为%s的)被设置为单个首选共识领袖。"

ER_GRP_RPL_ERROR_SET_SINGLE_CONSENSUS_LEADER
  eng "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."
  chinese "尝试将成员%s:%u(uuid:%s)设置为单个首选共识领导者时出错。请查询performance_schema.replication_group_communication_information表以查看操作是否生效,即首选共识领导者是否与当前主要成员匹配。如果不是,请考虑选择其他主要成员重试。请检查错误日志和gcs_DEBUG_TRACE以了解可能有助于了解出错原因的详细信息。"

ER_GRP_RPL_SET_MULTI_CONSENSUS_LEADER
  eng "All members were set as consensus leaders."
  chinese "所有成员都被设定为共识领袖。"

ER_GRP_RPL_ERROR_SET_MULTI_CONSENSUS_LEADER
  eng "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."
  chinese "尝试将所有成员设置为共识领导者时出错。请查询performance_schema.replication_group_communication_information表以查看操作是否生效,即共识领导者是否与所有成员匹配。如果不是,请考虑将组通信协议重置为版本低于8.0.22,或切换到单主要模式,然后再切换回多主要模式,以重试。请检查错误日志和gcs_DEBUG_TRACE以了解可能有助于了解出错原因的详细信息。"

ER_GRP_RPL_PAXOS_SINGLE_LEADER_DIFF_FROM_GRP
  eng "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."
  chinese "此成员配置了GROUP_REPLICATION_PAXOS_SINGLE_LEADER选项值'%d',该值与组的值('%d')不同。此成员现在将退出该组。"

ER_MFA_USER_ATTRIBUTES_CORRUPT
  eng "Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. \"%s\"."
  chinese "mysql.user表的USER_ATTRIBUTES列中的多因素身份验证方法无效和/或已损坏。\"%s\"。"

ER_MFA_PLUGIN_NOT_LOADED
  eng "Plugin \'%-.192s\' is not loaded; Ignoring user"
  chinese "未加载插件\'%-.192s\'；忽略用户"

ER_WARN_DEPRECATED_CHARSET_OPTION
  eng "%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead."
  chinese "%s:字符集%s已弃用,将在将来的版本中删除。请考虑改用%s。"

ER_WARN_DEPRECATED_COLLATION_OPTION
  eng "%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead."
  chinese "%s:'%-.64s'是不推荐使用的字符集%s的排序规则。请考虑改用具有适当排序规则的%s。"

ER_REGEXP_MISSING_ICU_DATADIR
  eng "Missing data directory for ICU regular expressions: %s."
  chinese "缺少ICU正则表达式的数据目录:%s。"

ER_IB_WARN_MANY_NON_LRU_FILES_OPENED
  eng "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."

ER_IB_MSG_TRYING_TO_OPEN_FILE_FOR_LONG_TIME
  eng "Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher."
  chinese "尝试打开文件的时间为%lld秒。配置仅允许%zu个打开的文件。请考虑将Innobase_OPEN_FILES设置得更高。"

ER_GLOBAL_CONN_LIMIT
  eng "Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes."
  chinese "连接已关闭。已超过全局连接内存限制%llu字节。已使用%llu字节。"

ER_CONN_LIMIT
  eng "Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes."
  chinese "连接已关闭。已超过连接内存限制%llu字节。已使用%llu字节。"

ER_WARN_AUDIT_LOG_DISABLED
  eng "Audit Log is disabled. Enable it with audit_log_disable = false."
  chinese "审核日志已禁用。请使用AUDIT_LOG_DISABLE=FALSE启用它。"

ER_INVALID_TLS_VERSION
  eng "Option --tls-version or --admin-tls-version is set to an invalid value %s."
  chinese "选项--tls-version 或--admin-tls-version 设置为无效值%s。"

ER_RPL_RELAY_LOG_RECOVERY_GTID_ONLY
  eng "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."
  chinese "GTID_ONLY=1的通道上的中继日志恢复。该通道将切换到新的中继日志,并且GTID协议将用于复制未应用的事务。"

ER_KEYRING_OKV_STANDBY_SERVER_COUNT_EXCEEDED
  eng "Number of STANDBY_SERVER values exceeded maximum limit of 64."
  chinese "STANDBY_SERVER值的数量超过了64个的最大限制。"

ER_WARN_MIGRATION_EMPTY_SOURCE_KEYRING
  eng "Source keyring does not have any keys to migrate."
  chinese "源密钥环没有任何要迁移的密钥。"

ER_WARN_CANNOT_PERSIST_SENSITIVE_VARIABLES
  eng "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."
  chinese "无法持久化敏感系统变量,因为密钥环组件支持不可用,并且Persistent_Sensitive_Variables_in_PLEMPText设置为OFF。请确保密钥环服务处于活动状态并且所需的密钥可用。"

ER_CANNOT_INTERPRET_PERSISTED_SENSITIVE_VARIABLES
  eng "Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available."
  chinese "无法解释持久的敏感系统变量。请确保密钥环服务处于活动状态并且所需的密钥可用。"

ER_PERSISTED_VARIABLES_KEYRING_SUPPORT_REQUIRED
  eng "Keyring has to be loaded through manifest file in order to support secure storage for persisted variables"
  chinese "必须通过清单文件加载密钥环,才能支持持久变量的安全存储"

ER_PERSISTED_VARIABLES_MASTER_KEY_NOT_FOUND
  eng "Could not find master key %s in keyring"
  chinese "在密钥环中找不到主密钥%s"

ER_PERSISTED_VARIABLES_MASTER_KEY_CANNOT_BE_GENERATED
  eng "A new master key %s could not be generated"
  chinese "无法生成新的主密钥%s"

ER_PERSISTED_VARIABLES_ENCRYPTION_FAILED
  eng "Failed to encrypt %s using %s"
  chinese "无法加密%s使用%s"

ER_PERSISTED_VARIABLES_DECRYPTION_FAILED
  eng "Failed to decrypt %s using %s"
  chinese "无法解密%s使用%s"

ER_PERSISTED_VARIABLES_LACK_KEYRING_SUPPORT
  eng "Persisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file."
  chinese "以加密形式保存敏感变量需要通过清单文件加载密钥环组件。"

ER_MY_MALLOC_USING_JEMALLOC
  eng "Using jemalloc.dll for my_malloc and ut::malloc etc."
  chinese "对my_Malloc和ut::Malloc等使用jemalloc.dll。"

ER_MY_MALLOC_USING_STD_MALLOC
  eng "%s."
  chinese "%s."

ER_MY_MALLOC_LOADLIBRARY_FAILED
  eng "%s."
  chinese "%s."

ER_MY_MALLOC_GETPROCADDRESS_FAILED
  eng "%s."
  chinese "%s."

ER_ACCOUNT_WITH_EXPIRED_PASSWORD
  eng "Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator."
  chinese "帐户'%-.48s'@'%-.64s'的密码已过期。若要登录,请使用支持过期密码的客户端进行更改,或将更改请求发送给管理员。"

ER_THREAD_POOL_PLUGIN_STARTED
  eng "Thread pool plugin started successfully with parameters: %s"
  chinese "线程池插件已成功启动,参数为:%s"

ER_THREAD_POOL_DEDICATED_LISTENERS_INVALID
  eng "thread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0"
  chinese "除非THREAD_POOL_MAX_TRANSACTIONS_LIMIT>0,否则无法设置THREAD_POOL_DIRECTED_LISTENERS"

ER_IB_DBLWR_BYTES_INFO
  eng "%s"
  chinese "%s"

ER_IB_RDBLWR_BYTES_INFO
  eng "%s"
  chinese "%s"

ER_IB_MSG_LOG_FILE_IS_EMPTY
  eng "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."
  chinese "重做日志文件%s为空,这表明它不是由InnoDB生成的或已损坏。请还原正确的文件或尝试在不使用重做文件的情况下以只读模式恢复,方法是提供--Innodb-force-Recovery=6。"

ER_IB_MSG_LOG_FILE_TOO_SMALL
  eng "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."
  chinese "重做日志文件%s小于%llu字节,这表明它不是由InnoDB生成的或已损坏。请还原正确的文件。"

ER_IB_MSG_LOG_FILE_TOO_BIG
  eng "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."
  chinese "重做日志文件%s大于%llu字节,这表明它不是由InnoDB生成的或已损坏。请还原正确的文件。"

ER_IB_MSG_LOG_FILE_HEADER_READ_FAILED
  eng "Failed to read header of the redo log file %s"
  chinese "无法读取重做日志文件%s的头"

ER_IB_MSG_LOG_INIT_DIR_NOT_EMPTY_WONT_INITIALIZE
  eng "--initialize specified but the redo log directory %s has redo log files inside. Aborting."
  chinese "--指定了初始化,但重做日志目录%s中有重做日志文件。正在中止。"

ER_IB_MSG_LOG_INIT_DIR_LIST_FAILED
  eng "Failed to list redo log files in the redo log directory %s"
  chinese "无法列出重做日志目录%s中的重做日志文件"

ER_IB_MSG_LOG_INIT_DIR_MISSING_SUBDIR
  eng "Neither found %s subdirectory, nor %s* files in %s"
  chinese "未找到%s子目录,也未找到%s*文件(在%s中)"

ER_IB_MSG_LOG_FILES_CREATED_BY_CLONE_AND_READ_ONLY_MODE
  eng "Cannot restore cloned data directory, InnoDB running in read-only mode!"
  chinese "无法恢复克隆的数据目录,InnoDB正在以只读模式运行！"

ER_IB_MSG_LOG_WRITER_WRITE_FAILED
  eng "Error %d encountered when writing to the redo log file: %s."
  chinese "写入重做日志文件时遇到错误%d:%s。"

ER_IB_MSG_LOG_WRITER_WAIT_ON_NEW_LOG_FILE
  eng "Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity."
  chinese "重做日志编写器正在等待新的重做日志文件。请考虑增加Innodb_REDO_LOG_CAPTABLE。"

ER_IB_MSG_RECOVERY_CHECKPOINT_OUTSIDE_LOG_FILE
  eng "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."
  chinese "找到检查点LSN %llu 在重做日志文件%s中,但该文件表示LSN值范围[%llu,%llu),因此该文件已损坏。"

ER_IB_MSG_LOG_WRITER_ENTERED_EXTRA_MARGIN
  eng "Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity."
  chinese "重做日志的可用空间不足,正在暂停用户线程...请考虑增加Innodb_redo_log_Capacity。"

ER_IB_MSG_LOG_WRITER_EXITED_EXTRA_MARGIN
  eng "Redo log reclaimed some free space, resuming user threads."
  chinese "重做日志回收了一些可用空间,恢复了用户线程。"

ER_IB_MSG_LOG_PARAMS_FILE_SIZE_UNUSED
  eng "Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead."
  chinese "已忽略不推荐使用的配置参数Innodb_LOG_FILE_SIZE。改为使用InnodB_REDO_LOG_CAPTABLE。"

ER_IB_MSG_LOG_PARAMS_N_FILES_UNUSED
  eng "Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead."
  chinese "已忽略不推荐使用的配置参数Innodb_LOG_FILES_IN_GROUP。改为使用InnodB_REDO_LOG_CAPTABLITY。"

ER_IB_MSG_LOG_UPGRADE_FORCED_RECV
  eng "Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0."
  chinese "当Innodb-force-Recovery>0时,无法升级重做日志文件的格式(v%lu)。"

ER_IB_MSG_LOG_UPGRADE_IN_READ_ONLY_MODE
  eng "Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only)."
  chinese "无法以只读模式(--Innodb-Read-Only)升级重做日志文件的格式(v%lu)。"

ER_IB_MSG_LOG_UPGRADE_CLONED_DB
  eng "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)."
  chinese "无法升级克隆数据目录上的重做日志文件格式(v%lu)。请使用较旧版本的MySQL-Recover并关闭(使用Innodb-fast-Shutdown<2)。"

ER_IB_MSG_LOG_UPGRADE_UNINITIALIZED_FILES
  eng "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)."
  chinese "无法升级重做日志文件的格式(v%lu),因为它们被标记为未初始化。请使用较旧版本的MySQL-Recover并关闭(使用Innodb-fast-Shutdown<2)。"

ER_IB_MSG_LOG_UPGRADE_CORRUPTION__UNEXPECTED
  eng "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)."
  chinese "当重做日志损坏时,无法升级重做日志文件的格式(v%lu)。请使用较旧版本的MySQL-Recover和Shutdown(Innodb-fast-Shutdown<2)。"

OBSOLETE_ER_IB_MSG_LOG_UPGRADE_NON_PERSISTED_DD_METADATA
  eng "Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2)."
  chinese "当重做中存在非持久化的DD元数据时,无法升级重做日志文件的格式(v%lu)。请使用较旧版本的MySQL-Recover and Shutdown(Innodb-fast-Shutdown<2)。"

OBSOLETE_ER_IB_MSG_LOG_UPGRADE_FLUSH_FAILED__UNEXPECTED
  eng "Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2)."
  chinese "无法升级重做日志文件的格式(v%lu),因为InnoDB未能达到重做日志逻辑为空的状态。请使用较旧版本的MySQL-Recover并关闭(Innodb-fast-Shutdown<2)。"

OBSOLETE_ER_IB_MSG_LOG_FILES_RESIZE_ON_START_FAILED__UNEXPECTED
  eng "Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2)."
  chinese "无法同步调整重做日志的大小,因为InnoDB未能达到重做日志逻辑为空的状态。请使用较旧版本的MySQL-Recover并关闭(Innodb-fast-Shutdown<2)。"

ER_IB_MSG_LOG_FILE_FOREIGN_UUID
  eng "The redo log file %s comes from other data directory than redo log file %s."
  chinese "重做日志文件%s来自重做日志文件%s以外的其他数据目录。"

ER_IB_MSG_LOG_FILE_INVALID_START_LSN
  eng "The redo log file %s has invalid start_lsn %llu."
  chinese "重做日志文件%s具有无效的START_LSN %llu。"

ER_IB_MSG_LOG_FILE_INVALID_LSN_RANGES
  eng "The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file)."
  chinese "重做日志文件%s具有START_LSN %llu,但需要%llu(上一个重做日志文件的END_LSN)。"

ER_IB_MSG_LOG_FILE_MISSING_FOR_ID
  eng "Missing redo log file %s (with start_lsn = %llu)."
  chinese "缺少重做日志文件%s(START_LSN=%llu)。"

ER_IB_MSG_LOG_CHECKPOINT_FOUND
  eng "The latest found checkpoint is at lsn = %llu in redo log file %s."
  chinese "最新找到的检查点位于LSN=%llu(在重做日志文件%s中)。"

ER_IB_MSG_LOG_FILES_CAPACITY_CHANGED
  eng "User has set innodb_redo_log_capacity to %lluM."
  chinese "用户已将Innodb_redo_log_Capacity设置为%lluM。"

ER_IB_MSG_LOG_FILES_RESIZE_REQUESTED
  eng "Redo log has been requested to resize from %lluM to %lluM."
  chinese "已请求重做日志将大小从%llum调整为%llum。"

ER_IB_MSG_LOG_FILES_RESIZE_CANCELLED
  eng "Redo log resize has been cancelled."
  chinese "重做日志大小调整已取消。"

ER_IB_MSG_LOG_FILES_RESIZE_FINISHED
  eng "Redo log has been resized to %lluM."
  chinese "重做日志已调整到%lluM。"

ER_IB_MSG_LOG_FILES_UPGRADE
  eng "Upgrading redo log: %lluM, LSN=%llu."
  chinese "升级重做日志:%llum,LSN=%llu。"

ER_IB_MSG_LOG_FILE_MARK_CURRENT_AS_INCOMPLETE
  eng "Marked the current redo log file %s as incomplete."
  chinese "将当前重做日志文件%s标记为不完整。"

ER_IB_MSG_LOG_FILE_REMOVE_FAILED
  eng "Failed to remove redo log file %s."
  chinese "无法删除重做日志文件%s。"

ER_IB_MSG_LOG_FILE_RENAME_ON_CREATE_FAILED
  eng "Failed to rename %s when creating redo log file %s (error: %d)"
  chinese "无法重命名%s,当创建重做日志文件%s时(错误:%d)"

ER_IB_MSG_LOG_FILES_CREATED_BY_UNKNOWN_CREATOR
  eng "Redo log files created by unknown creator %s."
  chinese "由未知创建者%s创建的重做日志文件。"

ER_IB_MSG_LOG_FILES_FOUND_MISSING
  eng "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."
  chinese "已找到现有重做日志文件,但至少缺少一个重做日志文件。恢复是否可以达到物理一致状态尚不清楚。请考虑从备份还原或提供--Innodb-force-Recovery>0。"

ER_IB_MSG_LOG_FILE_FORMAT_TOO_NEW
  eng "Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo."
  chinese "找到重做日志文件%s,该文件的格式为(v%lu)并且存储在#Innodb_REDO之外。"

ER_IB_MSG_LOG_FILE_FORMAT_TOO_OLD
  eng "Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo."
  chinese "找到重做日志文件%s,该文件的格式为(v%lu)并存储在#Innodb_REDO中。"

ER_IB_MSG_LOG_FILE_DIFFERENT_FORMATS
  eng "Found redo log files with different formats: %s has format v%lu, %s has format v%lu."
  chinese "找到不同格式的重做日志文件:%s的格式为v%lu,%s的格式为v%lu。"

ER_IB_MSG_LOG_PRE_8_0_30_MISSING_FILE0
  eng "Missing ib_logfile0 in the directory %s."
  chinese "目录%s中缺少ib_logfile0。"

ER_IB_MSG_LOG_PFS_ACQUIRE_SERVICES_FAILED
  eng "Failed to initialize services required to handle redo log PFS tables."
  chinese "无法初始化处理重做日志PFS表所需的服务。"

ER_IB_MSG_LOG_PFS_CREATE_TABLES_FAILED
  eng "Failed to create redo log PFS tables."
  chinese "无法创建重做日志PFS表。"

ER_IB_MSG_LOG_FILE_TRUNCATE
  eng "Truncating redo log file %s..."
  chinese "正在截断重做日志文件%s..."

ER_IB_MSG_LOG_FILE_UNUSED_RESIZE_FAILED
  eng "Failed to resize unused redo log file %s to %llu MB (%s)."
  chinese "无法将未使用的重做日志文件%s调整为%llu MB(%s)。"

ER_IB_MSG_LOG_FILE_UNUSED_REMOVE_FAILED
  eng "Failed to remove unused redo log file %s."
  chinese "无法删除未使用的重做日志文件%s。"

ER_IB_MSG_LOG_FILE_UNUSED_RENAME_FAILED
  eng "Failed to rename unused redo log file %s to %s."
  chinese "无法将未使用的重做日志文件%s重命名为%s。"

ER_IB_MSG_LOG_FILE_UNUSED_MARK_AS_IN_USE_FAILED
  eng "Failed to mark unused redo log file %s as in use (by renaming to %s)."
  chinese "无法将未使用的重做日志文件%s标记为正在使用(通过重命名为%s)。"

ER_IB_MSG_LOG_FILE_MARK_AS_UNUSED_FAILED
  eng "Failed to mark redo log file %s as unused (by renaming to %s)."
  chinese "无法将重做日志文件%s标记为未使用(通过重命名为%s)。"

ER_IB_MSG_LOG_PARAMS_DEDICATED_SERVER_IGNORED
  eng "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."
  chinese "由于已显式指定Innodb_redo_log_set或Innodb_log_files_in_group,因此将忽略Innodb_redo_log_Capacity选项Innodb_Dedued_SERVER。重做日志容量:%llum。"

ER_IB_MSG_LOG_PARAMS_LEGACY_USAGE
  eng "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."
  chinese "已使用不推荐使用的配置参数Innodb_log_file_SIZE和/或Innodb_LOG_FILES_IN_GROUP来计算Innodb_redo_log_Capacity=%llu。请改用Innodb_redo_log_Capacity。"

ER_GRP_RPL_FAILED_TO_LOG_VIEW_CHANGE
  eng "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."
  chinese "此成员无法将VIEW_CHANGE_LOG_EVENT记录到二进制日志中,因此将离开该组。请检查是否有可用的磁盘空间,然后将该成员重新添加到该组中。"

ER_BINLOG_CRASH_RECOVERY_MALFORMED_LOG
  eng "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."
  chinese "二进制日志文件'%s'(从位置%llu和%llu之间的)恢复时发现无效的事件序列:%s。恢复进程提前停止,没有恢复任何事务。副作用可能是二进制日志和存储引擎之间处于不一致状态的事务,或者存储引擎保持在准备状态(可能持有锁)的事务。修复二进制日志的问题,或者在服务器恢复期间禁用二进制日志,以释放可能获取的锁定。请注意,禁用二进制日志可能会导致已确认为成功连接到客户端的事务丢失,并且可能已复制到拓扑中的其他服务器。"

ER_BINLOG_CRASH_RECOVERY_ERROR_RETURNED_SE
  eng "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."
  chinese "存储引擎无法恢复一个或多个事务。恢复进程已提前停止,请检查以前的消息以了解有关失败事务的详细信息。副作用可能是二进制日志和存储引擎之间的事务处于不一致状态,或者存储引擎将事务保持在准备状态(可能处于锁定状态)。修复存储引擎的问题(内存不足、没有磁盘空间等),或者要释放XA事务可能获取的锁定,请在服务器恢复期间禁用二进制日志,并检查存储引擎和二进制日志文件之间的一致性。"

ER_BINLOG_CRASH_RECOVERY_ENGINE_RESULTS
  eng "Crash recovery finished in %s engine. %s"
  chinese "已在%s引擎中完成崩溃恢复。%s"

ER_BINLOG_CRASH_RECOVERY_COMMIT_FAILED
  eng "Failed to commit %s in %s, with failure code %s."
  chinese "无法提交%s在%s中,失败代码为%s。"

ER_BINLOG_CRASH_RECOVERY_ROLLBACK_FAILED
  eng "Failed to rollback %s in %s, with failure code %s."
  chinese "无法回滚%s在%s中,失败代码为%s。"

ER_BINLOG_CRASH_RECOVERY_PREPARE_FAILED
  eng "Failed to prepare %s in %s, with failure code %s."
  chinese "无法准备%s在%s中,失败代码为%s。"
ER_COMPONENT_EE_SYS_VAR_REGISTRATION_FAILURE
  eng "Cannot register variable '%s'. Please check if it is not already registered by another component."
  chinese "无法注册变量'%s'。请检查它是否尚未由其他组件注册。"

ER_COMPONENT_EE_SYS_VAR_DEREGISTRATION_FAILURE
  eng "Cannot unregister variable '%s'. Please check if it was registered properly in the first place."
  chinese "无法注销变量'%s'。请首先检查它是否已正确注册。"

ER_COMPONENT_EE_FUNCTION_REGISTRATION_FAILURE
  eng "Cannot register function '%s'. Please check if it is not already registered."
  chinese "无法注册函数'%s'。请检查它是否尚未注册。"

ER_COMPONENT_EE_FUNCTION_DEREGISTRATION_FAILURE
  eng "Cannot unregister function '%s'. Please check if it was registered properly in the first place."
  chinese "无法注销函数'%s'。请首先检查它是否已正确注册。"

ER_COMPONENT_EE_FUNCTION_INVALID_ARGUMENTS
  eng "Invalid arguments to function '%s'. Expected values: %s."
  chinese "函数'%s'的参数无效。期望值:%s。"

ER_COMPONENT_EE_FUNCTION_INVALID_ALGORITHM
  eng "Invalid algorithm value '%.20s' in function %s."
  chinese "算法值'%.20s'无效函数%s中的。"

ER_COMPONENT_EE_FUNCTION_KEY_LENGTH_OUT_OF_RANGE
  eng "Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d]."
  chinese "密钥长度'%d'无效函数'%s'对于算法为'%.20s'的。请提供一个介于[%d,%d]之间的值。"

ER_COMPONENT_EE_FUNCTION_PRIVATE_KEY_GENERATION_FAILURE
  eng "Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message."
  chinese "无法生成长度为'%d'的私钥使用算法'%.20s'函数'%s'中的。有关该错误的更多详细信息将在此消息之前记录。"

ER_COMPONENT_EE_FUNCTION_PUBLIC_KEY_GENERATION_FAILURE
  eng "Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message."
  chinese "无法使用算法'%.20s'为函数'%s'中的给定私钥生成公钥。有关该错误的更多详细信息将在此消息之前记录。"

ER_COMPONENT_EE_DATA_LENGTH_OUT_OF_RAGE
  eng "Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes)."
  chinese "生成长度为'%d'的私钥函数'%s'中的使用算法'%.20s'。给定私钥的最大支持数据长度为%d(字节)。"

ER_COMPONENT_EE_DATA_ENCRYPTION_ERROR
  eng "Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message."
  chinese "无法加密函数'%s'中的数据,使用算法'%.20s'。数据长度为'%d'字节。有关该错误的更多详细信息将在此消息之前记录。"

ER_COMPONENT_EE_DATA_DECRYPTION_ERROR
  eng "Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message."
  chinese "无法解密函数'%s'中的数据,使用算法'%.20s'。数据长度为'%d'字节。有关该错误的更多详细信息将在此消息之前记录。"

ER_COMPONENT_EE_DATA_SIGN_ERROR
  eng "Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message."
  chinese "无法标记函数'%s'中的数据,使用算法'%.20s'和消息型'%.20s'。有关该错误的更多详细信息将在此消息之前记录。"

ER_COMPONENT_EE_OPENSSL_ERROR
  eng "Received OpenSSL error in function '%s' for algorithm '%s': '%s'"
  chinese "收到OpenSSL错误(函数'%s'中使用算法'%s'):'%s'"

ER_COMPONENT_EE_INSUFFICIENT_LENGTH
  eng "In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'."
  chinese "在函数'%s'(算法为'%s')中:输出缓冲区长度'%zu'不足。需要的长度为'%zu'。"

ER_SYSTEMD_NOTIFY_DEBUG
  eng "%s%s"
  chinese "%s%s"

ER_TMP_SESSION_FOR_VAR
  eng "Setting session values for system variables only makes sense in a user session (failed to set '%.256s')."
  chinese "设置系统变量的会话值仅在用户会话中有意义(设置'%.256s'失败)。"

ER_BUILD_ID
  eng "BuildID[sha1]=%s"
  chinese "BuildID[sha1]=%s"

ER_THREAD_POOL_CANNOT_REGISTER_DYNAMIC_PRIVILEGE
  eng "Failed to register dynamic privilege %s."
  chinese "注册动态特权%s失败。"

ER_IB_MSG_LOG_WRITER_WAIT_ON_CONSUMER
  eng "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."
  chinese "重做日志的%s编写器正在等待当前正在读取LSN=%llu重做日志使用者阻止回收重做日志的后续部分。请考虑增加Innodb_REDO_LOG_CAPTABLE。"

ER_CONDITIONAL_DEBUG
  eng "%s"
  chinese "%s"

ER_IB_MSG_PARSE_OLD_REDO_INDEX_VERSION
  eng "Recovery: Generating index information for INSTANT DDL Table in 8.0.29 format"
  chinese "恢复:为8.0.29格式的即时DDL表生成索引信息"

OBSOLETE_ER_RES_GRP_FAILED_TO_SWITCH_RESOURCE_GROUP
  eng "Failed to switch resource group. %s"
  chinese "无法切换资源组。%s"

OBSOLETE_ER_RES_GRP_SWITCH_FAILED_COULD_NOT_ACQUIRE_GLOBAL_LOCK
  eng "Failed to switch resource group. Could not acquire resource groups global lock."
  chinese "切换资源组失败。无法获取资源组全局锁。"

OBSOLETE_ER_RES_GRP_SWITCH_FAILED_COULD_NOT_ACQUIRE_LOCK
  eng "Failed to switch resource group. Could not acquire lock on resource group %s."
  chinese "切换资源组失败。无法获取资源组%s上的锁。"

OBSOLETE_ER_RES_GRP_SWITCH_FAILED_UNABLE_TO_APPLY_RES_GRP
  eng "Failed to switch resource group. Unable to apply resource group controller %s."
  chinese "切换资源组失败。无法应用资源组控制器%s。"

ER_IB_MSG_CLEAR_INSTANT_DROP_COLUMN_METADATA
  eng "Failed to clear instant drop column metadata for table %s"
  chinese "无法清除表%s的即时删除列元数据"

ER_COMPONENT_KEYRING_OCI_OPEN_KEY_FILE
  eng "Cannot open signing key file %s."
  chinese "无法打开签名密钥文件%s。"

ER_COMPONENT_KEYRING_OCI_CREATE_PRIVATE_KEY
  eng "Out of memory! Cannot create private key."
  chinese "内存不足！无法创建私钥。"

ER_COMPONENT_KEYRING_OCI_READ_KEY_FILE
  eng "Cannot read signing key file %s."
  chinese "无法读取签名密钥文件%s。"

ER_NOTE_COMPONENT_KEYRING_OCI_MISSING_NAME_OR_TYPE
  eng "Incomplete key: missing Name/Type for the Key: %s."
  chinese "密钥不完整:缺少密钥的名称/类型:%s。"

ER_WARN_COMPONENT_KEYRING_OCI_DUPLICATE_KEY
  eng "Duplicate key found in keyring with Name: %s and Owner: %s."
  chinese "在名称为%s、所有者为%s的密钥环中发现重复密钥。"

ER_KEYRING_OCI_PARSE_JSON
  eng "Error parsing JSON response %s."
  chinese "解析JSON响应%s时出错。"

ER_KEYRING_OCI_INVALID_JSON
  eng "Invalid JSON response!"
  chinese "无效的JSON响应！"

ER_KEYRING_OCI_HTTP_REQUEST
  eng "HTTP request failed with error: '%s'"
  chinese "HTTP请求失败，错误为:'%s'"

ER_THREAD_POOL_SYSVAR_CHANGE
  eng "Variable thread_pool.%s was updated: %s"
  chinese "变量THREAD_POOL.%s已更新:%s"

ER_STACK_BACKTRACE
  eng "%s"
  chinese "%s"

ER_IB_MSG_BUF_POOL_RESIZE_COMPLETE_CUR_CODE
  eng "Status code %u: Completed"
  chinese "状态代码%u:已完成"

ER_IB_MSG_BUF_POOL_RESIZE_PROGRESS_UPDATE
  eng "Status code %u: %u%% complete"

ER_IB_MSG_BUF_POOL_RESIZE_CODE_STATUS
  eng "Status code %u: %s"
  chinese "状态代码%u:%s"

ER_THREAD_POOL_QUERY_THREADS_PER_GROUP_INVALID
  eng "Invalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u."
  chinese "设置为THREAD_POOL_QUERY_THREADS_PER_GROUP的值无效。有效值范围为%u-%u。"

ER_THREAD_POOL_QUERY_THRS_PER_GRP_EXCEEDS_TXN_THR_LIMIT
  eng "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"
  chinese "查询线程计数(%u)超过了每个组的事务线程限制(%u)。请使用小于或等于每组最大事务线程限制的每组查询线程数"

ER_IB_MSG_INVALID_PAGE_TYPE
  eng "Found page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lu"
  chinese "发现页面类型不匹配。预期为%u，在页面中找到%u:space_id=%lu页面编号=%lu"

ER_IB_PARALLEL_READER_WORKER_INFO
  eng "preader: thread_id=%zu, n_threads=%zu, n_ctx=%zu, one_range_per_thread=%s, n_index=%zu, index_list=%s, err=%zu"

ER_IB_BULK_LOAD_SUBTREE_INFO
  eng "bulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zu"
  chinese "批量加载:space_id=%zu，表=%s，索引=%s，高度=%zu，n_extents=%zu，n_ages=%zu"

ER_IB_BULK_FLUSHER_INFO
  eng "bulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu"
  chinese "批量刷新:睡眠计数=%zu，睡眠持续时间=%zu毫秒，总睡眠=%zu毫秒，页面刷新=%zu"

ER_IB_BUFFER_POOL_OVERUSE
  eng "%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."
  chinese "%s:超过67的缓冲池(CURR_SIZE=%zu MB)被锁堆或自适应哈希索引或BUF_BLOCK_MEMORY页占用。检查您的事务是否没有设置太多行锁。也许你应该把缓冲池做得更大?.启动InnoDB显示器以打印诊断信息。"

ER_IB_BUFFER_POOL_FULL
  eng "%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!"
  chinese "%s:超过95的缓冲池(CURR_SIZE=%zu MB)被锁堆或自适应哈希索引或BUF_BLOCK_MEMORY页占用。检查您的事务是否没有设置太多行锁。也许你应该把缓冲池做得更大？我们故意生成一个seg错误，以便在Linux上打印堆栈跟踪！"

ER_IB_DUPLICATE_KEY
  eng "%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)"
  chinese "%s:表=%s，索引=%s，n_uniq=%zu，n_field=%zu，lhs=(%s)，rhs=(%s)"

ER_REPLICATION_INCOMPATIBLE_TABLE_WITH_GIPK
  eng "Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', 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."
  chinese "无法应用具有%d列的行事件，该事件源自%s版的表'%-.192s.%-.192s'的服务器，该表有%d列，其中一列是生成的隐式主键。当源服务器早于8.0.30，副本表具有生成的隐式主键，并且列计数存在差异(不计算副本生成的隐式主键)时不支持复制。对齐源和复制副本上的表架构，然后重新启动复制。"

ER_BULK_EXECUTOR_INFO
  eng "Bulk executor: %s"
  chinese "批量执行程序:%s"

ER_BULK_LOADER_INFO
  eng "Bulk loader: %s"
  chinese "批量加载程序:%s"

ER_BULK_LOADER_FILE_CONTAINS_LESS_LINES_THAN_IGNORE_CLAUSE_LOG
  eng "The first file being loaded contained less lines than the ignore clause"
  chinese "要装载的第一个文件包含的行数少于IGNORE子句"

ER_BULK_READER_INFO
  eng "Bulk reader: %s"
  chinese "批量读取器:%s"

ER_BULK_READER_LIBCURL_INIT_FAILED_LOG
  eng "Bulk reader failed to initialize libcurl"
  chinese "批量读取器无法初始化libcurl"

ER_BULK_READER_LIBCURL_ERROR_LOG
  eng "Bulk reader got libcurl error: %s"
  chinese "批量读取器获取libcurl错误:%s"

ER_BULK_READER_SERVER_ERROR_LOG
  eng "Bulk reader got error response from server: %ld"
  chinese "批量读取器从服务器获得错误响应:%ld"

ER_BULK_READER_COMMUNICATION_ERROR_LOG
  eng "Bulk reader got error in communication with source server, check the error log for additional details"
  chinese "批量读取器在与源服务器通信时出错，有关其他详细信息，请查看错误日志"

ER_BULK_PARSER_MISSING_ENCLOSED_BY_LOG
  eng "Missing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input."
  chinese "第%ld行中，在文件'%s'，缺少封闭式字符。可选地添加到INCLUTED BY子句以允许此输入。"

ER_BULK_PARSER_ROW_BUFFER_MAX_TOTAL_COLS_EXCEEDED_LOG
  eng "The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'."
  chinese "分析需要缓冲的输入列数超过了文件%s的预定义缓冲区最大大小。"

ER_BULK_PARSER_COPY_BUFFER_SIZE_EXCEEDED_LOG
  eng "The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'."
  chinese "由于转义字符而需要复制的列数据超出了文件'%s'的内部复制缓冲区的大小。"

ER_BULK_PARSER_UNEXPECTED_END_OF_INPUT_LOG
  eng "Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing."
  chinese "第%ld行中，在文件'%s'，发现意外的输入结尾。缺少某些列的数据。"

ER_BULK_PARSER_UNEXPECTED_ROW_TERMINATOR_LOG
  eng "Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing."
  chinese "第%ld行中，在文件'%s'，发现意外的行终止符。缺少某些列的数据。"

ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_ENDING_ENCLOSED_BY_LOG
  eng "Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'."
  chinese "第%ld行中，在文件'%s'，发现结尾由字符括起的意外字符。"

ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_NULL_ESCAPE_LOG
  eng "Unexpected characters after NULL escape (\\N) found at row %ld in file '%s'."
  chinese "第%ld行中，在文件'%s'，在NULL转义(\\N)后发现意外字符。"

ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_COLUMN_TERMINATOR_LOG
  eng "Unexpected characters after column terminator found at row %ld in file '%s'."
  chinese "第%ld行中，在文件'%s'的在列终止符之后发现了意外字符。"

ER_BULK_PARSER_INCOMPLETE_ESCAPE_SEQUENCE_LOG
  eng "Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence."
  chinese "第%ld行在文件'%s'中发现意外的输入结尾，导致不完整的转义序列。"

ER_LOAD_BULK_DATA_WRONG_VALUE_FOR_FIELD_LOG
  eng "Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'"
  chinese "错误的%-.32s值:'%-.128s'中%-.192s第%ld行的列'%-.192s'文件"

ER_LOAD_BULK_DATA_WARN_NULL_TO_NOTNULL_LOG
  eng "NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'"
  chinese "提供给非空列%s的空值在%ld行在文件%-.192s中"

ER_IB_BULK_LOAD_THREAD_FAIL
   eng "%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s"
   chinese "%s:加载大容量数据线程失败(错误=%lu)，表=%s，索引=%s"

ER_IB_BULK_LOAD_MERGE_FAIL
   eng "%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%s"
   chinese "%s:无法在加载批量数据时合并子树，表=%s，索引=%s，详细信息=%s"

ER_IB_LOAD_BULK_CONCURRENCY_REDUCED
   eng "LOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s."
   chinese "加载大容量数据:缓冲池大小为%zu。正在将并发性从%zu降低到%zu。表=%s。"

ER_PLUGIN_EXCEPTION_OPERATION_FAILED
   eng "C++ Exception caught while %s the %s plugin: [%s]"
   chinese "%s时捕获到C++异常%s插件:[%s]"

ER_REQUIRE_TABLE_PRIMARY_KEY_CHECK_GENERATE_WITH_GR_IN_REPO
   eng "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."
   chinese "复制配置似乎已损坏。在组复制通道'%s'上，不允许将REQUIRED_TABLE_PRIMARY_KEY_CHECK设置为'GENERATE'。运行Reset Replica All以重置它。"

ER_CHECK_TABLE_INSTANT_VERSION_BIT_SET
   eng "Record has both instant and version bit set."
   chinese "记录同时设置了即时位和版本位。"

ER_GRP_RPL_PAXOS_SINGLE_LEADER_DIFF_FROM_OLD_GRP
  eng "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."
  chinese "此成员配置了GROUP_REPLICATION_PAXOS_SINGLE_LEADER选项值1，并且它正在尝试加入通信协议版本低于8.0.27的组。要加入该组，GROUP_REPLICATION_PAXOS_SINGLE_LEADER值必须配置为值0。此成员现在将退出群。"

ER_IB_WRN_IGNORE_REDO_LOG_CAPACITY
  eng "Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files."
  chinese "已忽略Innodb只读模式下的Innodb-redo-log-acity选项。服务器正在使用活动重做日志文件。"

ER_IB_PRIMARY_KEY_IS_INSTANT
  eng "Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging"
  chinese "获取行日志记录的主键时，意外添加/删除列:'%s'，位置为%lu(表'%s'，索引'%s')"

ER_THREAD_POOL_IDLE_CONNECTION_CLOSED
   eng "%s"
   chinese "%s"

ER_IB_HIDDEN_NAME_CONFLICT
   eng "Column name %s and internally generated INSTANT DROP column name %s is causing a conflict."
   chinese "列名%s和内部生成的即时删除列名%s导致冲突。"

ER_IB_DICT_INVALID_COLUMN_POSITION
   eng "Field number: %llu too large, Total fields in Record: %zu."
   chinese "字段号:%llu太大，记录中的总字段数:%zu。"

ER_IB_DICT_LOG_TABLE_INFO
   eng "%s"
   chinese "%s"

ER_RPL_ASYNC_NEXT_FAILOVER_CHANNEL_SELECTED
  eng "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'"

ER_RPL_REPLICA_SOURCE_UUID_HAS_NOT_CHANGED
  eng "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."

ER_RPL_REPLICA_SOURCE_UUID_HAS_CHANGED_HOST_PORT_UNCHANGED
  eng "The server_uuid for source server \'%s:%d\' has changed from %s to %s. This should not happen unless you have changed it manually."

ER_RPL_REPLICA_SOURCE_UUID_HOST_PORT_HAS_CHANGED
  eng "The source server has changed from \'%s:%d\' with server_uuid %s, to \'%s:%d\' with server_uuid %s."

ER_RPL_REPLICA_CONNECTED_TO_SOURCE_RPL_STARTED_FILE_BASED
  eng "Replica receiver thread%s: connected to source \'%s@%s:%d\' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'."

ER_RPL_REPLICA_CONNECTED_TO_SOURCE_RPL_STARTED_GTID_BASED
  eng "Replica receiver thread%s: connected to source \'%s@%s:%d\' with server_uuid=%s, server_id=%d. Starting GTID-based replication."

ER_IB_INDEX_LOADER_DONE
   eng "Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu."
   chinese "Loader::Build_All():已完成生成%zu索引为old_table=%s、new_table=%s，错误=%zu。"

ER_IB_INDEX_BUILDER_DONE
   eng "Builder::finish(): Completed building index=%s of table=%s, err=%zu."
   chinese "Builder::Finish():已完成的生成索引=%s，表=%s，错误=%zu。"

ER_CANT_PARSE_CPU_STRING
  eng "Cannot parse cpu string '%s'."

ER_LIBNUMA_TEST_FAIL
  eng "libnuma test fail."

ER_NUMA_AVAILABLE_TEST_FAIL
  eng "numa_available test fail."

ER_CANNOT_SET_THREAD_SCHED_AFFINIFY
  eng "Cannot set thread %s sched affinity."

ER_CANNOT_UNSET_THREAD_SCHED_AFFINIFY
  eng "Cannot unset thread %s sched affinity."

ER_CANNOT_REGISTER_THREAD_TO_SCHED_AFFINIFY_MANAGER
  eng "Cannot register thread %s sched affinity manager."

ER_CANNOT_UNREGISTER_THREAD_FROM_SCHED_AFFINIFY_MANAGER
  eng "Cannot unregister thread %s sched affinity manager."

ER_USE_DUMMY_SCHED_AFFINITY_MANAGER
  eng "use dummy sched_affinity_manager."

ER_SCHED_AFFINITY_THREAD_PROCESS_CONFLICT
  eng "Found sched affinity conflict between threads and process."

ER_SCHED_AFFINITY_FOREGROUND_BACKGROUND_CONFLICT
  eng "Found sched affinity conflict between foreground threads and background threads."

ER_CANNOT_CREATE_SCHED_AFFINITY_MANAGER
  eng "Cannot create sched affinity manager."

ER_SET_FALLBACK_MODE
  eng "sched_affinity_manager is set to fallback mode."

ER_FALLBACK_DELEGATE_SCHED_AFFINITY_MANAGER_IS_CALLED
  eng "sched_affinity_manager is in fallback mode. A fallback version of sched_affinity_manager is called, which does nothing."

ER_WARN_DEPRECATED_USER_DEFINED_COLLATIONS_OPTION
   eng "%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."

ER_IB_INDEX_BUILDER_INIT
   eng "Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes."

ER_IB_SELECT_COUNT_STAR
   eng "SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu."

ER_IB_INDEX_LOG_VERSION_MISMATCH
   eng "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."

ER_WARN_COMPONENTS_INFRASTRUCTURE_MANIFEST_MULTIPLE_KEYRING
   eng "Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time."

ER_GRP_RPL_HAS_STARTED
  eng "Plugin 'group_replication' has been started."

ER_CHECK_TABLE_MIN_REC_FLAG_SET
   eng "Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'."

ER_CHECK_TABLE_MIN_REC_FLAG_NOT_SET
   eng "Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'."

ER_NOTE_COMPONENT_SLOT_REGISTRATION_SUCCESS
  eng "Successfully registered slot '%d' for component '%s'."

ER_NOTE_COMPONENT_SLOT_DEREGISTRATION_SUCCESS
  eng "Successfully de-registered slot '%d' from component '%s'."

ER_WARN_CANNOT_FREE_COMPONENT_DATA_DEALLOCATION_FAILED
  eng "Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources."

ER_IB_RESURRECT_TRX_INSERT
  eng "Transaction ID: %lu found for resurrecting inserts"

ER_IB_RESURRECT_TRX_UPDATE
  eng "Transaction ID: %lu found for resurrecting updates"

ER_IB_RESURRECT_IDENTIFY_TABLE_TO_LOCK
  eng "Identified table ID: %lu to acquire lock"

ER_IB_RESURRECT_ACQUIRE_TABLE_LOCK
  eng "Acquired lock on table ID: %lu, name: %s"

ER_IB_RESURRECT_RECORD_PROGRESS
  eng "Records read: %lu - Pages read: %lu"

ER_IB_RESURRECT_RECORD_COMPLETE
  eng "Total records resurrected: %lu - Total pages read: %lu - Total tables acquired: %lu"

ER_IB_RESURRECT_TRX_INSERT_COMPLETE
  eng "Resurrected %lu transactions doing inserts."

ER_IB_RESURRECT_TRX_UPDATE_COMPLETE
  eng "Resurrected %lu transactions doing updates."

ER_AUTHENTICATION_OCI_INVALID_TOKEN
  eng "Invalid security token provided by '%s' for '%s'@'%s': %s."

ER_AUTHENTICATION_OCI_TOKEN_DETAILS_MISMATCH
  eng "Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'."

ER_AUTHENTICATION_OCI_TOKEN_NOT_VERIFIED
  eng "Verification failed for security token provided by '%s' for '%s'@'%s' : %s."

ER_AUTHENTICATION_OCI_DOWNLOAD_IDDP_PUBLIC_KEY
  eng "Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid."

OBSOLETE_ER_AUTHENTICATION_OCI_NO_MATCHING_GROUPS_IN_TOKEN
  eng "None of the groups extracted from security token matches any of the entries from authentication string."

ER_SYS_VAR_REGISTRATION
  eng "Cannot register variable '%s'. Please check if it is not already registered by another component."

ER_SYS_VAR_DEREGISTRATION
  eng "Cannot unregister variable '%s'. Please check if it was registered properly in the first place."

ER_UDF_REGISTRATION
  eng "Cannot register function '%s'. Please check if it is not already registered by another component."

ER_UDF_DEREGISTRATION
  eng "Cannot unregister function '%s'. Please check if it was registered properly in the first place."

ER_PRIVILEGE_REGISTRATION
  eng "Cannot register privilege '%s'. Please check if it is not already registered."

ER_PRIVILEGE_DEREGISTRATION
  eng "Cannot unregister privilege '%s'. Please check if it was registered properly in the first place."

ER_UDF_EXEC_FAILURE
  eng "Error while executing UDF %s."

ER_UDF_EXEC_FAILURE_REASON
  eng "Error while executing UDF %s: %s."

ER_COMPONENT_SERVICE_CALL
  eng "%s failed."

ER_COMPONENT_SERVICE_CALL_RESULT
  eng "%s failed with %u."

ER_COMPONENT_LOCK
  eng "Lock failed at %s : %u."

ER_COMPONENT_UNLOCK
  eng "Lock from %s : %u failed to unlock."

ER_COMPONENT_MASKING_OTHER_ERROR
  eng "Masking component error: '%s'."

ER_COMPONENT_MASKING_ABI
  eng "%s failed."

ER_COMPONENT_MASKING_ABI_REASON
  eng "%s failed because %s."

ER_COMPONENT_MASKING_RANDOM_CREATE
  eng "Creation of random context failed."

ER_COMPONENT_MASKING_RANDOM_CREATE_REASON
  eng "Creation of random context failed because %s."

ER_COMPONENT_MASKING_CANNOT_ACCESS_TABLE
  eng "Cannot access %s.%s table."

ER_REDUCED_DBLWR_FILE_CORRUPTED
  eng "Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted."

ER_REDUCED_DBLWR_PAGE_FOUND
  eng "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."

ER_CONN_INIT_CONNECT_IGNORED_MFA
  eng "init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxing"

ER_SECONDARY_ENGINE_DDL_FAILED
  eng "Execution of alter table %s %s failed because %s."

ER_THREAD_POOL_CONNECTION_REPORT
   eng "TP conn (port: managed(delta), active, opened, closed, added, dropped): %s"

ER_WARN_SCHEDULED_TASK_RUN_FAILED
   eng "Scheduled run of task %s failed"

ER_AUDIT_LOG_INVALID_FLUSH_INTERVAL_VALUE
   eng "Invalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %d"

ER_LOG_CANNOT_PURGE_BINLOG_WITH_BACKUP_LOCK
  eng "Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock."

ER_CONVERT_MULTI_VALUE
   eng "Multi-values cannot be converted to MySQL format: %s"

ER_IB_DDL_CONVERT_HEAP_NOT_FOUND
  eng "Heap required to convert columns is not present."

ER_SERVER_DOWNGRADE_FROM_VERSION
  eng "MySQL server downgrading from version '%u' to '%u'."

ER_BEYOND_SERVER_DOWNGRADE_THRESHOLD
  eng "Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u."

ER_BEYOND_SERVER_UPGRADE_THRESHOLD
  eng "Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u."

ER_INVALID_SERVER_UPGRADE_NOT_LTS
  eng "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."

ER_INVALID_SERVER_DOWNGRADE_NOT_PATCH
  eng "Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases."

ER_FAILED_GET_DD_PROPERTY
  eng "Failed to get the data dictionary property %s."

ER_FAILED_SET_DD_PROPERTY
  eng "Failed to set the data dictionary property %s."

ER_SERVER_DOWNGRADE_STATUS
  eng "Server downgrade from '%d' to '%d' %s."

ER_INFORMATION_SCHEMA_VERSION_CHANGE
  eng "%s information schema from version %u to %u."

ER_PERFORMANCE_SCHEMA_VERSION_CHANGE
  eng "%s performance schema from version %u to %u."

ER_WARN_DEPRECATED_OR_BLOCKED_CIPHER
   eng "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."

ER_IB_MSG_DDL_FAIL_NO_BUILDER
  eng "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'."

ER_GRP_RPL_MEMBER_INFO_DOES_NOT_EXIST
  eng "Member identified %s: '%s' does not exist on Group Replication membership during %s."

ER_USAGE_DEPRECATION_COUNTER
  eng "Deprecated '%s' used %s times, last time used '%s'."

ER_WAITING_FOR_NO_CONNECTIONS
  eng "Waiting for %u connections to be closed."

ER_WAITING_FOR_NO_THDS
  eng "Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions."

ER_IB_INDEX_PART_TOO_LONG
  eng "Index %s of %s.%s exceeds limit of %lu bytes per column."

# The following 4 messages were incorrectly up-merged from 8.0.
# They now live in the 8.1+ range. This decision was taken as
# we now had the 4 messages in different ranges in 8.0 vis-a-vis
# all higher versions, which means that once 8.0 becomes unsupported,
# only one error number remains for each of these messages (namely
# the one in the 8.1+ range). That in itself requires nothing else
# (outside this explanatory message, anyway). We do however block
# the 8.0 error-numbers of these messages in 8.1+ as OBSOLETE so
# that if further messages are upmerged from 8.0, they are not
# assigned the numbers in the 8.0 range of 8.1+ where the messages
# from the initial broken merge should have been, as that would lead
# to another batch of symbols that have different numbers in 8.0 and
# 8.1+. This is less complicated than it sounds. :)

OBSOLETE_ER_DD_UPDATE_DATADIR_FLAG_FAIL
  eng "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"

OBSOLETE_ER_IB_MSG_FIL_STATE_MOVED_PREV_OR_HAS_DATADIR
  eng "%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory. It is either moved or is created with 'DATA DIRECTORY'"

OBSOLETE_ER_RPL_KILL_OLD_DUMP_THREAD_ENCOUNTERED
  eng "Upon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected."

OBSOLETE_ER_RPL_MTA_ALLOW_COMMIT_OUT_OF_ORDER
  eng "The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order."

#
# End of 8.0 error messages intended to be written to the server error log.
#


#
# Start of 8.1+ error messages intended to be written to the server error log.
# Append 8.0 error log messages to the end of the _previous_ section.
# Messages intended to be sent to _clients_ go in messages_to_clients.txt!
#

start-error-number 15000

ER_LANGUAGE_COMPONENT_INFO
  eng "%s"

ER_LANGUAGE_COMPONENT_WARNING
  eng "%s"

ER_LANGUAGE_COMPONENT_ERROR
  eng "%s"

ER_IB_BULK_FLUSHER_PUNCH_HOLE
  eng "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"

ER_GRP_RPL_CONN_KILLED
   eng "%s as the client session was killed."

ER_WARN_CANT_OPEN_CERTIFICATE
  eng "Cannot open certificate %s. Please check the cerificate"

ER_FAILED_TO_VALIDATE_CERTIFICATES_SERVER_EXIT
  eng "Certificate validation has failed. Stopping the server as tls-certificates-enforced-validation is enabled"

ER_WARN_CA_CERT_VERIFY_FAILED
  eng "CA certificate/certficates is invalid. Please check logs for more details."

ER_WARN_FAILED_TO_SETUP_TLS
  eng "Internal TLS error %s:%s:%d:%s"

ER_TLS_LIBRARY_ERROR_INTERNAL
  eng "Failed to set up TLS. Check logs for details"

ER_SERVER_CERT_VERIFY_FAILED
  eng "Server certificate %s verification has failed. Check logs for more details"

ER_WARN_CERTIFICATE_ERROR_STRING
  eng "Failed to validate certificate %s because %s"

ER_TELEMETRY_INFO
  eng "%s"

ER_TELEMETRY_WARNING
  eng "%s"

ER_TELEMETRY_ERROR
  eng "%s"

ER_SRV_START
  eng "MySQL Server - start."

ER_SRV_END
  eng "MySQL Server - end."

ER_SRV_INIT_START
  eng "MySQL Server Initialization - start."

ER_SRV_INIT_END
  eng "MySQL Server Initialization - end."

ER_PLUGINS_SHUTDOWN_START
  eng "MySQL Server: Plugins Shutdown - start."

ER_PLUGINS_SHUTDOWN_END
  eng "MySQL Server: Plugins Shutdown - end."

ER_COMPONENTS_INFRASTRUCTURE_SHUTDOWN_START
  eng "MySQL Server: Components Shutdown - start."

ER_COMPONENTS_INFRASTRUCTURE_SHUTDOWN_END
  eng "MySQL Server: Components Shutdown - end (with return value = %d)."

ER_CONNECTIONS_SHUTDOWN_START
  eng "MySQL Server: Closing Connections - start."

ER_CONNECTIONS_SHUTDOWN_END
  eng "MySQL Server: Closing Connections - end."

ER_THREAD_STILL_ALIVE
  eng "Waiting for forceful disconnection of Thread (ID %ld) to end."

ER_NUM_THREADS_STILL_ALIVE
  eng "Waiting for forceful disconnection of %ld thread(s) to end."

ER_GRP_RPL_MYSQL_NETWORK_PROVIDER_SERVER_ERROR_COMMAND_ERR
   eng "Failed to accept a MySQL connection for Group Replication. %s. Please retry."

ER_COMPONENT_KEYRING_OCI_INVALID_CONFIG_VAR
   eng "Invalid value of argument %s (%s)."

ER_WARN_OPTION_RESET_AND_IGNORED_DURING_INITIALIZE
   eng "Ignoring a non-default value for %s during --initialize."

ER_FIREWALL_SCHEDULER_REGISTER_FAILED
  eng "Automatic registration of the scheduler failed."

ER_FIREWALL_INVALID_RELOAD_INTERVAL_VALUE
  eng "Invalid reload interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %d."

ER_WARN_DEPRECATED_DYNAMIC_PRIV_FOR_USER
   eng "'%s' (granted to '%s@%s') is deprecated and will be removed in a future release."

ER_BULK_MULTI_READER_INFO
  eng "Bulk Multi Reader: %s"

ER_BULK_MERGE_LOADER_INFO
  eng "Bulk Merge Loader: %s"

ER_BULK_SORTING_LOADER_INFO
  eng "Bulk Sorting Loader: %s"

ER_BULK_WRITER_INFO
  eng "Bulk Writer: %s"

ER_BULK_WRITER_LIBCURL_INIT_FAILED_LOG
  eng "Bulk writer failed to initialize libcurl"

ER_BULK_WRITER_LIBCURL_ERROR_LOG
  eng "Bulk writer got libcurl error: %s"

ER_IB_WRONG_PAGE_ID
  eng "Detected wrong page_id: buf_block_t[space_id=%zu, page_no=%zu], buf_frame_t[space_id=%zu, page_no=%zu], file=%s"

ER_IB_FIXED_PAGE_ID
  eng "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"

ER_IB_WRONG_PAGEID_AFTER_SYNC_READ
  eng "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"

ER_IB_SYNC_READ_FAILED
  eng "Sync read to fix wrong page_id failed: buf_block_t[space_id=%zu, page_no=%zu], file=%s, err=%zu, retry=%zu"

ER_START_REPLICA_CHANNEL_INVALID_CONFIGURATION_LOG
  eng "Cannot start replication channel '%s' because %s."

ER_GROUP_REPLICATION_CERTIFIER_MESSAGE_LARGE
  eng "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."

ER_GROUP_REPLICATION_METADATA_SENDER_IS_REMOTE
  eng "The member %s:%u will be the one sending the recovery metadata message."

ER_GROUP_REPLICATION_METADATA_SENDER
  eng "This member %s:%u will be the one sending the recovery metadata message."

ER_GROUP_REPLICATION_ERROR_COMPRESS_INITIALIZE
  eng "Error initializing the %s compression context. Data cannot be compressed."

ER_GROUP_REPLICATION_COMPRESS_PROCESS
  eng "Error while compressing data using %s compression. Data cannot be decompressed."

ER_GROUP_REPLICATION_UNKOWN_COMPRESSION_TYPE
  eng "Error unknown Compression Library requested."

ER_GROUP_REPLICATION_COMPRESS_EXCEEDS_MAX_SIZE
  eng "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."

ER_GROUP_REPLICATION_COMPRESS_OUT_OF_MEMORY
  eng "Error while compressing data using %s compression. The operation could not be performed as memory allocation failed."

ER_GROUP_REPLICATION_ERROR_DECOMPRESS_INITIALIZE
  eng "Error initializing the %s decompression context. Data cannot be decompressed."

ER_GROUP_REPLICATION_DECOMPRESS_EXCEEDS_MAX_SIZE
  eng "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."

ER_GROUP_REPLICATION_DECOMPRESS_OUT_OF_MEMORY
  eng "Error while decompressing data using %s compression. The operation could not be performed as memory allocation failed."

ER_GROUP_REPLICATION_DECOMPRESS_TRUNCATED
  eng "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."

ER_GROUP_REPLICATION_DECOMPRESS_CORRUPTED
  eng "Error while decompressing data using %s compression. The operation could not be performed as the compression library reported an error."

ER_GROUP_REPLICATION_DECOMPRESS_END
  eng "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."

ER_GROUP_REPLICATION_DECOMPRESS_PROCESS
  eng "Error while decompressing data using %s compression. Data cannot be decompressed."

ER_GRP_RPL_VCLE_NOT_BEING_LOGGED
  eng "View_change_log_event will not be logged further on the binary log, as all members of the group are 8.3.0 or greater."

ER_GROUP_REPLICATION_METADATA_PROTOBUF_PARSING
  eng "Error while parsing serialzed Certification_info from received Recovery Metadata to Protobuf format using Protobuf library."

ER_GROUP_REPLICATION_PROTOBUF_SERIALIZING_ERROR
  eng "Error while serializing % data using Protobuf library."

ER_GROUP_REPLICATION_ERROR_RECEIVED_WAITING_METADATA
  eng "Error received while the Recovery thread was waiting for the Recovery Metadata. The Recovery will be terminated."

ER_GROUP_REPLICATION_TIMEOUT_ERROR_FETCHING_METADATA
  eng "Error fetching AFTER_GTIDS from Recovery Metadata by Recovery thread. The Recovery thread timeout after waiting for %d seconds. The Recovery will be terminated."

ER_GROUP_REPLICATION_METADATA_PAYLOAD_EMPTY
  eng "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."

ER_GROUP_REPLICATION_METADATA_MESSAGE_PAYLOAD_EMPTY
  eng "The %s payload type of the received Recovery Metadata Message is empty."

ER_GROUP_REPLICATION_METADATA_READ_GTID_EXECUTED
  eng "Error reading gtid_executed from the received Recovery Metadata Message."

ER_GROUP_REPLICATION_METADATA_PAYLOAD_DECODING
  eng "Error while decoding the received Recovery Metadata Message."

ER_GROUP_REPLICATION_METADATA_SEND_ERROR
  eng "The group was unable to send the Recovery Metadata to a joining member."

ER_GROUP_REPLICATION_METADATA_SAVE_RECOVERY_COPY
  eng "Error while saving copy of Recovery Metadata Message."

ER_GROUP_REPLICATION_METADATA_CERT_INFO_ERROR_PROCESSING
  eng "Error while processing received Certification Information from the Recovery Metadata Message."

ER_GROUP_REPLICATION_METADATA_CERT_INFO_PACKET_EMPTY
  eng "Error Certification Information packet from the received Recovery Metadata Message is empty."

ER_GROUP_REPLICATION_METADATA_ERROR_ON_SEND_ERROR_MESSAGE
  eng "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."

ER_GROUP_REPLICATION_METADATA_SET_IN_RECOVERY_FAILED
  eng "Error when transferring Recovery Metadata Message to Recovery. The joining member will leave the group."

ER_GROUP_REPLICATION_CERTIFICATION_MODULE_FAILURE
  eng "Error Certification module wasn't properly initialized."

ER_GROUP_REPLICATION_METADATA_INITIALIZATION_FAILURE
  eng "Error Recovery Metadata Message module wasn't properly initialized."

ER_GROUP_REPLICATION_METADATA_MEMORY_ALLOC
  eng "Error while %s. The operation could not be performed as memory allocation failed."

ER_GROUP_REPLICATION_RECOVERY_SKIPPED_GTID_PRESENT
  eng "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."

ER_GROUP_REPLICATION_RECOVERY_FETCHING_GTID_EXECUTED_SET
  eng "Error in Group Replication Recovery while getting member's global GTID executed set."

ER_GROUP_REPLICATION_RECOVERY_ERROR_ADD_GTID_EXECUTED
  eng "Error in Group Replication Recovery while adding GTIDs in string format to Gtid_set."

ER_GROUP_REPLICATION_RECOVERY_METADATA_SENDER_NOT_FOUND
  eng "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."

ER_GROUP_REPLICATION_METADATA_CERT_INFO_PACKET_COUNT_ERROR
  eng "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."

ER_GROUP_REPLICATION_METADATA_CERT_INFO_ENCODING_ERROR
  eng "Error while encoding Certification Information for the Recovery Metadata Message."

ER_GROUP_REPLICATION_METADATA_NO_VALID_DONOR
  eng "There are no valid recovery metadata donors. The joining member will leave the group."

ER_GROUP_REPLICATION_NO_CERTIFICATION_DONOR_AVAILABLE
  eng "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."

ER_GROUP_REPLICATION_RECOVERY_STOPPED_GTID_PRESENT
  eng "The group replication recovery is complete, joiner gtid executed set has all the transactions of the donor's gtid set %s."

ER_RPL_ASYNC_CHECK_CONNECTION_ERROR
  eng "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'."

ER_RPL_ASYNC_MONITOR_IO_THD_FETCH_GROUP_MAJORITY_ERROR
  eng "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'."

ER_RPL_ASYNC_REPLICA_IO_THD_FETCH_GROUP_MAJORITY_ERROR
  eng "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'."

ER_RPL_ASYNC_GET_GROUP_MEMBERSHIP_DETAILS_ERROR
  eng "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'."

ER_IB_ERR_CORRUPT_TABLESPACE_UNRECOVERABLE
  eng "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!"

ER_IB_BULK_LOAD_STATS_WARN
  eng "%s: Failed to save statistics for table=%s err=%zu"

ER_COMPONENT_MASKING_INVALID_FLUSH_INTERVAL_VALUE
   eng "Invalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %d."

ER_COMPONENT_MASKING_VAR_REGISTRATION_FAILURE
  eng "Cannot register variable '%s'.'%s'."

ER_COMPONENT_MASKING_NOTIFICATION_REGISTRATION_FAILURE
  eng "Masking component failed to register notification service. Periodical masking dictionaries flush will not work."

ER_GRP_RPL_MSG_DECODING_FAILED
  eng "Failed to decode Group Replication message: %s. Reason : %s"

ER_GRP_RPL_APPLIER_ERROR_PACKET_RECEIVED
  eng "The Applier process of Group Replication found an error and was requested to stop: %s"

ER_LANGUAGE_COMPONENT_INSTALL_ERROR
  eng "Cannot install the component."

ER_WARN_LANGUAGE_COMPONENT_CANNOT_UNINSTALL
  eng "Cannot uninstall the language component: %s."

ER_LANGUAGE_COMPONENT_SERVER_ERROR
  eng "Calling component service: %s."

ER_LANGUAGE_COMPONENT_INTERNAL_ERROR
  eng "Internal error while %s."

ER_LANGUAGE_COMPONENT_VM_API_FUNCTION_ERROR
  eng "Internal VM API function failed: %s."

ER_LANGUAGE_COMPONENT_VM_INTERNAL_ERROR
  eng "Internal VM error while %s."

ER_WARN_LANGUAGE_COMPONENT_RESOURCE_LIMIT
  eng "The resource limit has been exceeded. Details: %s."

ER_BLOCKED_CIPHER
   eng "Value for option '%s' contains cipher '%s' that is blocked. Please refer to the documentation for allowed ciphers."

ER_KEYRING_COMPONENT_KEYRING_FILE_NAME_EMPTY
   eng "Keyring file path is empty in configuration file."

ER_KEYRING_COMPONENT_KEYRING_FILE_READ_FAILED
   eng "Failed to read keyring file: %s."

ER_KEYRING_COMPONENT_KEYRING_FILE_DECRYPT_FAILED
   eng "Failed to decrypt keyring file: %s."

ER_KEYRING_COMPONENT_KEYRING_FILE_INVALID_FORMAT
   eng "The keyring file content is not in a valid JSON format."

ER_KEYRING_COMPONENT_KEYRING_FILE_JSON_EXTRACT_FAILED
   eng "Failed to extract a valid JSON data from keyring file."

ER_KEYRING_COMPONENT_KEYRING_FILE_KEY_EXTRACT_FAILED
   eng "Failed to extract key from keyring file JSON data."

ER_NOTE_KEYRING_COMPONENT_NOT_INITIALIZED
   eng "Keyring component is not initialized."

ER_NOTE_KEYRING_COMPONENT_EMPTY_DATA_ID
   eng "Provided Data ID is empty."

ER_NOTE_KEYRING_COMPONENT_KEYS_METADATA_ITERATOR_INIT_FAILED
  eng "Failed to initialize metadata iterator."

ER_NOTE_KEYRING_COMPONENT_KEY_READ_ITERATOR_INIT_FAILED
  eng "Failed to initialize key reader iterator."

ER_NOTE_KEYRING_COMPONENT_KEY_READ_ITERATOR_FETCH_FAILED
  eng "Failed to read key from key reader iterator."

ER_BACKGROUND_HISTOGRAM_UPDATE
  eng "%*s"

ER_IB_MSG_SUBMIT_DETAILED_BUG_REPORT
  eng "Submit a detailed bug report to http://bugs.mysql.com"

ER_AUTO_INCREMENT_NOT_SUPPORTED_FOR_FLOAT_DOUBLE
  eng "AUTO_INCREMENT is not supported with DOUBLE/FLOAT field. Please consider fixing (Schema:%s, Table:%s, Column:%s)."

ER_SERVER_DOWNGRADE_SYS_SCHEMA
  eng "Downgrading the sys schema."

ER_SERVER_DOWNGRADE_HELP_TABLE_STATUS
  eng "Downgrade of help tables %s."

ER_KEYRING_MIGRATE_SKIPPED_KEY
  eng "Could not find data pointed by data_id: %s, auth_id: %s. Skipping."

ER_KEYRING_MIGRATE_MEMORY_DEALLOCATION_FAILED
  eng "Failed to deallocate reader_object."

ER_LOG_CLIENT_INTERACTION_TIMEOUT
  eng "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."

ER_GRP_RPL_PREEMPTIVE_GARBAGE_COLLECTION_DIFF_FROM_GRP
  eng "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."

ER_IB_LONG_ROLLBACK_FULL
  eng "Still rolling back transaction %llu; %llu undo records rolled back out of %llu total (%lu%% complete). Transaction info: last state: %s"

ER_IB_LONG_ROLLBACK
  eng "Still rolling back transaction %llu; %llu undo records rolled back out of %llu total (%lu%% complete)."

ER_INVALID_FILE_FORMAT
  eng "Invalid format of file '%s'."

ER_LOG_SANITIZATION
  eng "Relay log sanitization: %s"

ER_WARN_LOG_DEPRECATED_NON_STANDARD_KEY
  eng "Foreign key '%.64s' on table '%.64s'.'%.64s' refers to non-unique key or partial key. This is deprecated and will be removed in a future release."

ER_THREAD_POOL_MTL_DISABLE
  eng "Disabling MTL in thread group %u since it has %u (=MTL per group) long running transactions."

ER_THREAD_POOL_MTL_REENABLE
  eng "Re-enabling MTL in thread group %u since it is down to %u long running transactions."

ER_LOG_PARTITION_PREFIX_KEY_NOT_SUPPORTED
  eng "Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' in the PARTITION BY KEY() clause is not supported."

ER_LDAP_AUTH_INFO_USER_MAP
  eng "Login user: %s@%s (external: %s) authenticated as: %s"

ER_ACCESS_DENIED_NO_PROXY_GRANT_WITH_NAME
  eng "Access denied for user '%s'@'%s', missing proxy privilege to '%s'."

ER_ACCESS_DENIED_NO_PROXY_WITH_NAME
  eng "Access denied for user '%s'@'%s', proxied user '%s' doesn't exist."

ER_GRP_RPL_RECOVERY_WAIT_APPLIER_BACKLOG_START
  eng "Distributed recovery will wait until the transactions '%s' contained on the 'group_replication_applier' channel are applied."

ER_GRP_RPL_RECOVERY_WAIT_APPLIER_BACKLOG_FINISH
  eng "Distributed recovery finished applying the transactions '%s' contained on the 'group_replication_applier' channel."

ER_BULK_READER_ZSTD_ERROR_LOG
  eng "ZSTD decompression failed: %s"

ER_SECONDARY_ENGINE_DDL_TRACK_PROGRESS
  eng "%s"

ER_IB_MSG_INNODB_FLUSH_METHOD
  eng "Using innodb_flush_method=%s"

ER_BULK_SCANNER_INFO
  eng "Bulk Scanner: %s"

ER_LOG_DEPRECATE_NON_COMPOSABLE_MULTIPLE_ENGINE
  eng "Combining the storage engines %.64s and %.64s is deprecated, but the statement or transaction updates both the %.64s table %.64s.%.64s and the %.64s table %.64s.%.64s."

ER_DD_UPDATE_DATADIR_FLAG_FAIL
  eng "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_IB_MSG_FIL_STATE_MOVED_PREV
  eng "%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORY"

ER_RPL_KILL_OLD_DUMP_THREAD_ENCOUNTERED
  eng "Upon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected."

ER_RPL_MTA_ALLOW_COMMIT_OUT_OF_ORDER
  eng "The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order."

ER_NUMA_INTERFACE_FAILED
  eng "numa_available test success, but interface %s failed, reinstall libnuma or set sched_affinity_enabled=OFF."

# DO NOT add server-to-client messages here;
# they go in messages_to_clients.txt
# in the same directory as this file.
#
# This file is for messages intended for the error log only.
#
# See the FAQ in errmsg_readme.txt in the
# same directory as this file for more
# information.


#
# End of 8.1, 8.2, 8.3, 8.4 error messages intended to be written to the server error log.
#

#
# Start of Percona Server 8.0 server error log messages
#
start-error-number 48000

ER_RPL_FAILED_TO_RECREATE_CACHE_FOR_INFO_FILE
  eng "Failed to recreate a cache on info file (file '%s')"
  chinese "无法在信息文件(文件‘%s’)上重新创建缓存"

ER_XB_MSG_0
  eng "%s"
  chinese "%s"

ER_XB_MSG_1
  eng "%s"
  chinese "%s"

ER_COMPRESSION_DICTIONARY_NO_CREATE
  eng "Cannot create compression dictionary tables in %s%sread-only mode."
  chinese "无法在%s%s只读模式下创建压缩字典表。"

ER_XB_UNUSED_1
  eng "%s"
  chinese "%s"

ER_XB_UNUSED_2
  eng "%s"
  chinese "%s"

ER_XB_MSG_4
  eng "Table %s is encrypted but decryption failed. Seems that the encryption key fetched from keyring is not the correct one. Are you using the correct keyring?"
  chinese "表%s已加密，但解密失败。从KEYRING获取的加密密钥似乎不正确。你用的钥匙扣对了吗？"

ER_XB_MSG_5
  eng "Tablespace id %u in file %s is encrypted but keyring or used key_id %u is not available. Can't continue reading table. Please provide the correct keyring."
  chinese "表空间ID%u(在文件%s中)已加密，但KEYRING或USED KEY_ID%u不可用。无法继续读表。请提供正确的钥匙扣。"

ER_XB_MSG_WAIT_FOR_KEYRING_ENCRYPT_THREAD
  eng "Waiting for keyring encryption threads to exit"
  chinese "正在等待密钥环加密线程退出"

ER_XB_UNUSED_3
  eng "%s"
  chinese "%s"

ER_XB_MSG_6
  eng "Key rotation of encrypted session temporary tablespace %s failed"
  chinese "加密会话临时表空间%s的密钥循环失败"

ER_XB_UNUSED_4
  eng "%s"
  chinese "%s"

ER_UPGRADE_KEYRING_UNSUPPORTED_VERSION_ENCRYPTION
  eng "Upgrade is not possible as there are tables that are KERYING encrypted. KEYRING encryption is still experimental feature in the version you are upgrading from. To upgrade please decrypt the tables encrypted with KEYRING encryption."
  chinese "无法升级，因为有KERYING加密的表。密钥环加密在您要升级的版本中仍然是实验性的功能。若要升级，请解密使用密钥环加密的表。"

ER_REDO_ENCRYPTION_CANT_BE_CHANGED
  eng "Redo log encryption mode can't be switched without stopping the server and recreating the redo logs. Current mode is %s, requested %s."
  chinese "如果不停止服务器并重新创建重做日志，则无法切换重做日志加密模式。当前模式为%s，请求%s。"

ER_REDO_ENCRYPTION_CANT_GENERATE_KEY
  eng "Redo log key generation failed."
  chinese "重做日志密钥生成失败。"

ER_REDO_ENCRYPTION_FAILED
  eng "Failed to encrypt redo log tablespace."
  chinese "无法加密重做日志表空间。"

ER_REDO_ENCRYPTION_CANT_LOAD_KEY_VERSION
  eng "Failed to load redo key version %u"
  chinese "无法加载重做密钥版本%u"

ER_REDO_ENCRYPTION_CANT_FETCH_KEY
  eng "Couldn't fetch newly generated redo key."
  chinese "无法获取新生成的重做密钥。"

ER_REDO_ENCRYPTION_CANT_PARSE_KEY
  eng "Couldn't parse system key: %s"
  chinese "无法解析系统密钥:%s"

ER_REDO_ENCRYPTION_KEYRING
  eng "Redo log cannot be encrypted if the keyring is not loaded."
  chinese "如果未加载密钥环，则无法加密重做日志。"

ER_UNDO_NO_KEYRING
  eng "Undo log can't be encrypted if the keyring is not loaded."
  chinese "如果未加载密钥环，则无法加密撤消日志。"

ER_REDO_ENCRYPTION_CANT_FETCH_DEFAULT_KEY
  eng "Couldn't fetch default percona_redo key. Please check if keyring is operational."
  chinese "无法获取默认的Percona_Redo密钥。请检查密钥环是否工作正常。"

ER_REDO_ENCRYPTION_CANT_UPGRADE_OLD_VERSION
  eng "Upgrade cannot continue as redo is encrypted with old, experimental version of KEYRING encryption. Please perform slow shutdown and remove old redo log files before upgrading."
  chinese "升级无法继续，因为重做是用旧的、实验性的密钥环加密版本加密的。请在升级前执行缓慢关闭并删除旧的重做日志文件。"

ER_TABLESPACE_ENCRYPTION_MISSING_KEY_VERSIONS
  eng "Tablespace id %u in file %s is encrypted. Although server managed to find key_id=%u in keyring to decrypt it, some versions of this key, that are needed to decrypt this space, are missing. Maybe you are using an old keyring? Can't continue reading table. Please provide the correct keyring."
  chinese "表空间ID%u文件%s中的已加密。虽然服务器设法在KEYRING中找到key_id=%u进行解密，但缺少解密此空间所需的此密钥的某些版本。可能您正在使用旧的KEYRING？无法继续读取表。请提供正确的KEYRING。"

ER_TABLESPACE_ENCRYPTION_CORRUPTED_KEYS
  eng "Tablespace id %u in file %s is encrypted. Although server managed to find all needed versions of key_id=%u in keyring to decrypt it, the provided versions are either incorrect or corrupted. Can't continue reading table. Please provide the correct keyring."
  chinese "表空间ID%u(在文件%s中)已加密。尽管服务器设法在KEYRING中找到了所有所需的key_id=%u版本进行解密，但提供的版本不正确或已损坏。无法继续读取表。请提供正确的KEYRING。"

ER_REDO_TABLESPACE_ENCRYPTION_MISSING_KEY
  eng "Tablespace id %u is encrypted but keyring or used key_id %u is not available. Can't continue reading table. Please provide the correct keyring."
  chinese "表空间ID%u已加密，但密钥环或使用的key_id%u不可用。无法继续读取表。请提供正确的密钥环。"

ER_REDO_TABLESPACE_ENCRYPTION_MISSING_KEY_VERSIONS
  eng "Tablespace id %u is encrypted. Although server managed to find key_id=%u in keyring to decrypt it, some versions of this key, that are needed to decrypt this space, are missing. Maybe you are using an old keyring? Can't continue reading table. Please provide the correct keyring."
  chinese "表空间ID%u已加密。尽管服务器设法在密钥环中找到key_id=%u进行解密，但解密此空间所需的此密钥的某些版本已丢失。可能您使用的是旧的密钥环？无法继续读取表。请提供正确的密钥环。"

ER_REDO_TABLESPACE_ENCRYPTION_CORRUPTED_KEYS
  eng "Tablespace id %u is encrypted. Although server managed to find all needed versions of key_id=%u in keyring to decrypt it, the provided versions are either incorrect or corrupted. Can't continue reading table. Please provide the correct keyring."
  chinese "表空间ID%u已加密。尽管服务器设法在密钥环中找到了所有需要的key_id=%u版本来解密它，但提供的版本不正确或已损坏。无法继续读表。请提供正确的钥匙圈。"

ER_IB_MSG_UNDO_TRUNCATE_DELAY_BY_LTFB
  eng "Delaying truncate of undo tablespace %s due to lock tables for backup."
  chinese "由于锁定要备份的表，正在延迟对撤消表空间%s的截断。"

ER_XPLUGIN_SSL_RELOAD_REGISTER_FAILED
  eng "X plugin failed to register SSL reload callback. ALTER INSTANCE RELOAD TLS will have no effect on the plugin."
  chinese "X插件无法注册SSL重新加载回调。ALTER INSTANCE RELOAD TLS不会对插件产生影响。"

ER_KEYRING_COMPONENT_NO_CONFIG
  eng "Keyring configuration doesn't exists: %s"
  chinese "密钥环配置不存在:%s"

ER_KEYRING_COMPONENT_CONFIG_PARSE_FAILED
  eng "Keyring configuration JSON parse error: %s (%lu)"
  chinese "密钥环配置JSON解析错误: %s (%lu)"

ER_PERCONA_UNSUPPORTED_ENGINE 
  eng "Table '%s.%s' requires the '%s' storage engine, which was removed in Percona Server 8.0.28"
  chinese "表‘%s.%s’需要‘%s’存储引擎，该引擎已在Percona Server 8.0.28中删除"

ER_SEC_LOG_PATH_NULL
  eng "--%s is set to NULL. Dynamic log files can be saved anywhere, possibly overwriting other files."
  chinese "--%s设置为空。动态日志文件可以保存在任何位置，可能会覆盖其他文件。"

ER_KEYRING_COMPONENT_KMS_ERROR
  eng "KMS communication error: %s"
  chinese "KMS通信错误:%s"

ER_XB_MSG_DOWNGRADING_LOG_FILE
  eng "Upgrade failed, recreating redo logs with previous version"
  chinese "升级失败，正在使用以前的版本重新创建重做日志"

ER_RPL_ENABLE_EVENT_ADD_WILD_PATTERN_FAILED
  eng "Could not add event rule '%s' to --replica-enable-event. %s"
  chinese "无法将事件规则‘%s’添加到复制副本启用事件。%s"

ER_GRP_RPL_FLOW_CONTROL_TIMEOUT
  eng "Flow control auto evict timeout reached. The server will now leave the group."
  chinese "已达到流控制自动逐出超时。服务器现在将离开该组。"

ER_PERCONA_IGNORE_TMP_TABLE_SIZE
  eng "Tmp_table_size is set below 1MiB. The TEMPTABLE engine requires at least 1MiB table size, and will use that value instead. Please increase the limit to silence this warning."

ER_CONN_CONTROL_FAILED_CONN_THRESHOLD_REACHED
  eng "Failing connection attempts threshold reached for %s"

ER_CONN_CONTROL_FAILED_CONN_THRESHOLD_REACHED_WITH_WARN
  eng "Failing connection attempts threshold reached for %s, further messages will be suppressed for next %llu seconds"

ER_CONN_CONTROL_DELAYED_CONN_STATS
  eng "Delayed %llu connection attempts during last %llu seconds"

ER_LOG_NAME_NOT_MATCHING_SEC_LOG_PATH
  eng "The --secure-file-path is configured, %s must be set accordingly."

ER_AUDIT_INIT_STARTED
  eng "Initializing Audit Event Filter..."

ER_AUDIT_DEINIT_DONE
  eng "Uninstalled Audit Event Filter"

ER_AUDIT_INIT_ENCRYPTION_PASSWORD_FAILURE
  eng "Failed to check/generate encryption password"

ER_AUDIT_INIT_PRIV_FAILURE
  eng "Failed to init AUDIT_ABORT_EXEMPT privilege"

ER_AUDIT_INIT_UDF_CREATE_FAILURE
  eng "Failed to create UDFs handler instance"

ER_AUDIT_INIT_UDF_INIT_FAILURE
  eng "Failed to init UDFs"

ER_AUDIT_INIT_FILTERS_INIT_FAILURE
  eng "Failed to create audit rule registry instance"

ER_AUDIT_INIT_FORMATTER_INIT_FAILURE
  eng "Failed to init record formatter"

ER_AUDIT_INIT_WRITER_INIT_FAILURE
  eng "Failed to init log writer"

ER_AUDIT_INIT_WRITER_OPEN_FAILURE
  eng "Cannot open log writer, error: %s"

ER_AUDIT_INIT_READER_INIT_FAILURE
  eng "Failed to create log reader instance"

ER_AUDIT_INIT_FAILURE
  eng "Failed to init component"

ER_AUDIT_INIT_DISABLED_WARN
  eng "Audit Log Filter is disabled. Enable it with audit_log_filter.disable = false."

ER_AUDIT_REMOVE_FILTER_UDF_NAME_CHECK_FAIL
  eng "Failed to check filtering rule name existence"

ER_AUDIT_REMOVE_FILTER_UDF_REMOVE_USER_FAIL
  eng "Failed to remove filter '%s' from users table"

ER_AUDIT_REMOVE_FILTER_UDF_REMOVE_FILTER_FAIL
  eng "Failed to remove filter '%s'"

ER_AUDIT_SET_USER_UDF_NAME_CHECK_FAIL
  eng "Failed to check filtering rule name existence"

ER_AUDIT_SET_USER_UDF_UNKNOWN_NAME
  eng "Unknown filtering rule name '%s'"

ER_AUDIT_SET_USER_UDF_FAIL
  eng "Failed to set '%s' filtering rule for user '%s@%s'"

ER_AUDIT_REMOVE_USER_UDF_FAIL
  eng "Failed to remove filter for user '%s@%s' from users table"

ER_AUDIT_LOG_ROTATE_UDF_FAIL
  eng "Log rotation failed: '%s'"

ER_AUDIT_STATUS_VAR_REGISTER_FAILURE
  eng "Failed to register status variables"

ER_AUDIT_STATUS_VAR_UNREGISTER_FAILURE
  eng "Failed to unregister status variables"

ER_AUDIT_SYS_VAR_REGISTER_FAILURE
  eng "Failed to register %s.%s system variable"

ER_AUDIT_SYS_VAR_UNREGISTER_FAILURE
  eng "Failed to unregister %s.%s system variable"

ER_AUDIT_SYS_VAR_SOURCE_CHECK_FAILURE
  eng "Failed to check %s variable source"

ER_AUDIT_PARSE_DEFAULT_LOG_ACTION_BAD_LOG_TYPE
  eng "Wrong JSON filter '%s' format, the 'log' member must be of type bool"

ER_AUDIT_PARSE_EVENT_CLASS_BAD_CLASS_LIST_TYPE
  eng "Wrong JSON filter '%s' format, 'class' array element must be of object type"

ER_AUDIT_PARSE_EVENT_CLASS_BAD_CLASS_TYPE
  eng "Wrong JSON filter '%s' format, 'class' must be an object or an array"

ER_AUDIT_PARSE_EVENT_CLASS_NO_CLASS_NAME
  eng "Wrong JSON filter '%s' format, no name provided for event class"

ER_AUDIT_PARSE_EVENT_CLASS_BAD_ABORT_DEF
  eng "Wrong JSON filter '%s' format, 'abort' condition should be set for subclass only"

ER_AUDIT_PARSE_EVENT_CLASS_BAD_LOG_TYPE
  eng "Wrong JSON filter '%s' format, 'log' must be of bool type"

ER_AUDIT_PARSE_EVENT_CLASS_BAD_PRINT_DEF
  eng "Wrong JSON filter '%s' format, failed to parse 'print' replacement rule"

ER_AUDIT_PARSE_EVENT_CLASS_UNEXPECTED_PRINT_DEF
  eng "Wrong JSON filter '%s' format, replacement rule not expected for event class"

ER_AUDIT_PARSE_EVENT_CLASS_UNEXPECTED_EVENT_DEF
  eng "Wrong JSON filter '%s' format, there must be no 'event' in case class names provided as an array of strings"

ER_AUDIT_PARSE_EVENT_CLASS_BAD_EVENT_NAME_FOR_LIST
  eng "Wrong JSON filter '%s' format, event class name within an array should be of a string type"

ER_AUDIT_PARSE_EVENT_CLASS_BAD_EVENT_NAME_TYPE
  eng "Wrong JSON filter '%s' format, event class name type must be either string or an array of strings"

ER_AUDIT_PARSE_EVENT_SUBCLASS_BAD_SUBCLASS_LIST_TYPE
  eng "Wrong JSON filter '%s' format, 'event' array element must be of object type"

ER_AUDIT_PARSE_EVENT_SUBCLASS_BAD_SUBCLASS_TYPE
  eng "Wrong JSON filter '%s' format, type of 'event' must be either an object or an array of objects"

ER_AUDIT_PARSE_ACTION_BAD_ABORT_TYPE
  eng "Wrong JSON filter '%s' format, 'abort' must be of bool or object type"

ER_AUDIT_PARSE_ACTION_BAD_REPLACE
  eng "Event field '%s' cannot be replaced"

ER_AUDIT_PARSE_CONDITION_TYPE_UNEXPECTED_COND_FORMAT
  eng "Wrong JSON filter '%s' format, there must be only one condition specified for 'log' field"

ER_AUDIT_PARSE_CONDITION_TYPE_BAD_COND_TYPE
  eng "Wrong JSON filter '%s' format, the 'log' condition name must be of string type"

ER_AUDIT_PARSE_CONDITION_TYPE_UNEXPECTED_COND_NAME
  eng "Wrong JSON filter '%s' format, unknown 'log' condition name '%s'"

ER_AUDIT_PARSE_CONDITION_BAD_FIELD_TYPE
  eng "Wrong JSON filter '%s' format, condition definition 'field' must be of object type"

ER_AUDIT_PARSE_CONDITION_BAD_FIELD_NAME_AND_VALUE
  eng "Wrong JSON filter '%s' format, event field definition 'field' must have field 'name' and 'value' provided as strings"

ER_AUDIT_PARSE_CONDITION_BAD_AND_COND_TYPE
  eng "Wrong JSON filter '%s' format, condition definition 'and' must be of array type"

ER_AUDIT_PARSE_CONDITION_BAD_AND_COND_FORMAT
  eng "Wrong JSON filter '%s' format, a member of 'and' condition must be of object type"

ER_AUDIT_PARSE_CONDITION_BAD_AND_COND_OPERANDS
  eng "Wrong JSON filter '%s' format, there should be at least two fields provided for 'and' condition"

ER_AUDIT_PARSE_CONDITION_BAD_OR_COND_TYPE
  eng "Wrong JSON filter '%s' format, condition definition 'or' must be of array type"

ER_AUDIT_PARSE_CONDITION_BAD_OR_COND_FORMAT
  eng "Wrong JSON filter '%s' format, a member of 'or' condition must be of object type"

ER_AUDIT_PARSE_CONDITION_BAD_OR_COND_OPERANDS
  eng "Wrong JSON filter '%s' format, there should be at least two fields provided for 'or' condition"

ER_AUDIT_PARSE_CONDITION_BAD_NOT_COND_TYPE
  eng "Wrong JSON filter '%s' format, condition definition 'not' must be of object type"

ER_AUDIT_PARSE_CONDITION_BAD_VARIABLE_COND_TYPE
  eng "Wrong JSON filter '%s' format, condition definition 'variable' must be of object type"

ER_AUDIT_PARSE_CONDITION_BAD_VARIABLE_NAME_AND_VALUE
  eng "Wrong JSON filter '%s' format, event field definition 'variable' must have field 'name' and 'value' provided as strings"

ER_AUDIT_PARSE_FUNCTION_NOT_OBJECT
  eng "Wrong JSON filter '%s' format, 'function' must be of object type"

ER_AUDIT_PARSE_FUNCTION_NO_FUNCTION_NAME
  eng "Wrong JSON filter '%s' format, missing 'function' name or not a string"

ER_AUDIT_PARSE_FUNCTION_UNKNOWN_FUNCTION_NAME
  eng "Wrong JSON filter '%s' format, unknown function name '%s'"

ER_AUDIT_PARSE_FUNCTION_BAD_ARGS_FORMAT
  eng "Wrong JSON filter '%s' format, wrong function args format provided"

ER_AUDIT_PARSE_FUNCTION_BAD_ARGS
  eng "Wrong JSON filter '%s' format, invalid arguments for '%s' function"

ER_AUDIT_PARSE_NO_SUBCLASS_NAME
  eng "Wrong JSON filter '%s' format, no name provided for event subclass"

ER_AUDIT_PARSE_BAD_SUBCLASS_NAME_TYPE
  eng "Wrong JSON filter '%s' format, event subclass name within an array should be of a string type"

ER_AUDIT_PARSE_BAD_SUBCLASS_NAME_LIST_TYPE
  eng "Wrong JSON filter '%s' format, event subclass name type must be either string or an array of strings"

ER_AUDIT_PARSE_CONDITION_DUPLICATED
  eng "Wrong JSON filter '%s' format, there must be only one condition provided, 'log' or 'abort'"

ER_AUDIT_PARSE_UNKNOWN_TAG
  eng "Wrong JSON filter '%s' format, unknown tag '%s'"

ER_AUDIT_PARSE_BAD_ACTION_FORMAT
  eng "Wrong JSON filter '%s' format, bad format for '%s' action"

ER_AUDIT_PARSE_BAD_REPLACEMENT_RULE
  eng "Wrong JSON filter '%s' format, failed to parse 'filter' replacement rule"

ER_AUDIT_UDF_INTERNAL_ERROR
  eng "ERROR: Internal error"

ER_AUDIT_UDF_SET_FILTER_BAD_DEFINITION
  eng "Wrong argument: incorrect rule definition '%s'"

ER_AUDIT_UDF_SET_FILTER_UNIQUE_CHECK_FAIL
  eng "Failed to check filtering rule name existence"

ER_AUDIT_UDF_SET_FILTER_NAME_EXISTS
  eng "Filtering rule with the name '%s' already exists"

ER_AUDIT_UDF_SET_FILTER_FAILURE
  eng "Failed to insert filtering rule '%s', '%s'"

ER_AUDIT_REPLACE_FIELD_UNEXPECTED_EVENT_TYPE
  eng "Unexpected event type for replace_field action"

ER_SSL_FIPS_MODE_ENABLED
  eng "A FIPS-approved version of the OpenSSL cryptographic library has been detected in the operating system with a properly configured FIPS module available for loading. Percona Server for MySQL will load this module and run in FIPS mode."

#
# End of Percona Server 8.0 server error log messages
#

#
# Start of GreatSQL 8.0 server error log messages
#
start-error-number 49500

ER_GRP_RPL_MULTI_PRIM_MODE_NOT_ALLOWED_WITH_FAST_MODE
  eng "It is not allowed to run multiple primary mode with 'group_replication_single_primary_fast_mode' enabled."
  chinese "不允许在启用了‘GROUP_REPLICATION_SINGLE_PRIMARY_FAST_MODE’的情况下运行多个主模式。"

ER_GRP_RPL_FAST_MODE_NOT_COMPATIBLE
  eng "The member is configured with a single_primary_fast_mode option value '%d' not compatible from the group '%d'. The member will now exit the group."
  chinese "该成员配置的SINGLE_PRIMARY_FAST_MODE选项的值'%d'与组'%d'不兼容。该成员现在将退出该组。"

ER_GRP_RPL_CERTIFY_GET_NEXT_GTID
  eng "Getting group next available gtid is failed."
  chinese "获取组下一个可用GTID失败。"

ER_GRP_RPL_CERTIFY_IS_INITIALIZED
  eng "Certify initializing is failed."
  chinese "认证初始化失败。"

ER_GRP_RPL_ARBITRATOR_IS_INITIALIZED
  eng "A primary node with the arbitrator role is not allowed"
  chinese "不允许具有仲裁者角色的主节点"

ER_GRP_RPL_ZONE_ID_SYNC_MODE_NOT_COMPATIBLE
  eng "The member is configured with a zone_id_sync_mode option value '%d' not compatible from the group '%d'. The member will now exit the group."
  chinese "该成员配置的zone_id_sync_mode值'%d'与组'%d'不兼容。该成员现在将退出该组。"

ER_GRP_RPL_PRIMARY_ELECTION_MODE_NOT_COMPATIBLE
  eng "The member is configured with a primary_election_mode option value '%s' not compatible from the group '%s'. The member will now exit the group."
  chinese "该成员配置的PRIMARY_SELECTION_MODE选项值‘%s’与组‘%s’不兼容。该成员现在将退出该组。"

ER_GRP_RPL_FAILED_SHUTDOWN_WITH_SUPER_READ_ONLY_ERROR
  eng "Failed to shutdown plugin group_replication when enable super_read_only error, the member will be STATE_ERROR."
  chinese "启用SUPER_READ_ONLY错误时，无法关闭插件GROUP_REPLICATION，成员将为STATE_ERROR。"

ER_X509_NEEDS_ECC_PRIVKEY
  eng "Could not generate ECC private key required for X.509 certificate."

ER_CLONE_APPLY_FILE_ERROR
  eng "Failed to restore increment clone data: %s"
  chinese "恢复增量的克隆数据失败：%s"

ER_CLONE_APPLY_FILE
  eng "Restore increment clone data: %s"
  chinese "恢复增量的克隆数据：%s"

ER_DATA_MASKING
  eng "data mask :%s"
  chinese "数据脱敏:%s"

ER_SYNONYM_ERROR_CREATING_QUERY_TO_WRITE_TO_BINLOG
  eng "Synonym Error: An error occurred while creating query string, before writing it into binary log."

ER_AUTHCACHE_MAC_INIT_SUBSYSTEM
  eng "Fatal: can't initialize mac subsystem - '%s'"
  chinese "致命:无法初始化Mac子系统-'%s'"

ER_AUTHCACHE_CANT_OPEN_AND_LOCK_MAC_TABLES
  eng "Fatal error: Can't open and lock mac tables: %s"
  chinese "致命错误:无法打开和锁定Mac表:%s"


################################################################################
# Error numbers 50000 to 51999 are reserved. Please do not use them for
reserved-error-section 50000 51999


# DO NOT append error messages here at the end.
#
#   If you came here to add a message, please read the FAQ in
#   errmsg_readme.txt to see where it should go.
#
#   Messages the server sends to the error log and messages
#   the server sends to its clients go to different places.
#   Messages for different server versions go to different places.
#   Messages that are built into the client library (libmysql/C-API)
#   go into yet a different place.
