This topic describes the OCP error codes and their meaning.
Error code |
Error message |
|---|---|
| 1001 | You must specify a valid value for {0}. Please check and try again. |
| 1002 | No record of the specified type {0} exists. Parameter: {1}. Please check and try again. |
| 1003 | The request is invalid. Cause: {0}. |
| 1004 | The request timed out. Please try again. |
| 1005 | An error occurred while processing the request. Please try again. |
| 1006 | A resource with the specified name already exists. Type: {0}. Parameter: {1}. Please specify another name and try again. |
| 1007 | The unit {0} is not supported. |
| 1008 | The method is not supported. |
| 1010 | The specified start or end time is invalid. Please specify another value and try again. |
| 1011 | The sort field {0} is not supported. |
| 1012 | The configuration item {0} does not exist. |
| 1013 | You must specify both the start time and end time or leave them both empty. Please check and try again. |
| 1113 | Failed to retrieve the next value in the sequence. |
| 1114 | An error occurred while attempting to perform concurrency protection in a multi-node OCP server cluster. Error: {0}. Please try again later. |
| 1115 | An unexpected error occurred. |
| 1116 | The specified object does not exist. |
| 1117 | The number of specified parameters is invalid. You can specify {0} to {1} parameters. |
| 1118 | The specified time range is too long. Please reduce the time range and try again. |
| 1200 | An I/O exception was thrown while executing an RPC call. Server: {0}. Port: {1}. |
| 1201 | An error occurred while executing an RPC call. Server: {0}. Port: {1}. Command: {2}. Code: {3}. Result: {4}. |
| 1500 | An error occurred while operating on OceanBase Database. Error: {0}. |
| 1999 | An unknown error occurred. Cause: {0}. Error: {1}. Please contact the administrator. |
| 3000 | You are not logged on or a logon error occurred. Please log on and try again. |
| 3001 | The current account is blocked. Please contact the administrator. |
| 3002 | The current logon account has expired. Contact the administrator. |
| 3003 | The current account is locked. Please contact the administrator. |
| 3004 | The username or password you entered is invalid. Please try again. You can retry {0} more times. |
| 3005 | Your password has expired. Please contact the administrator to reset the password. |
| 3006 | The username or password you entered is invalid. Please try again. You can retry {0} more times. |
| 3007 | The current account is not allowed to log on. Please contact the administrator. |
| 3008 | The specified username {0} is invalid. It must be 4 to 48 characters in length, start with a lowercase letter, and can contain lowercase letters, digits, underscores (_), and periods (.). |
| 3009 | The specified password is invalid. It must be 8 to 32 characters in length and contain at least two digits, two uppercase letters, two lowercase letters, and two special characters. Special characters include . _ + @ # $ % |
| 3010 | This operation requires the password of the user {2} in the {1} tenant of the {0} cluster. Please add it to the password box first. |
| 3011 | The specified password does not match the password of the account. Please check and try again. |
| 3012 | The format of the specified password ID is invalid. |
| 3013 | The password with an ID of {0} does not exist in the password box. |
| 3014 | Requests sent from the IP address {0} are restricted. Please try again later. |
| 3015 | The password of the user {2} in the {1} tenant of the {0} cluster is unavailable in the password box. |
| 3016 | The role name is invalid. The name must be 2 to 32 characters in length, and can contain letters, digits, and underscores (_). It must start with a letter and end with a letter or a digit. |
| 3100 | You are not authorized to perform the corresponding operations. Contact the administrator. |
| 3101 | You must specify the expression of the permission. Please check the permission settings and try again. |
| 3102 | The specified permission expression {0} is invalid. Please check the permission settings and try again. |
| 3103 | The system default role {0} cannot be deleted. |
| 3104 | The system default account {0} cannot be deleted. |
| 3105 | The username {0} is a keyword reserved by the system. Please specify another name and try again. Avoid words such as admin, sys, dba, and proxy. |
| 3016 | You cannot change the role of a user specified by the system. Username: {0}. |
| 3200 | The throttling strategy type {0} is not supported. |
| 3201 | The throttling resource {0} is not supported. |
| 3202 | The throttling object type {0} is not supported. |
| 3203 | The fixed window is not supported. Time unit: {0}. Time length: {1}. Window length: {2} seconds. |
| 3204 | The value {0} specified for the maximum number of throttling operations is invalid. |
| 3205 | You must specify the type of the throttling object. |
| 3206 | You must specify the ID of the throttling object. |
| 3207 | The specified throttling strategy creation parameter {0} is invalid. |
| 4001 | The {0} task does not exist. |
| 4002 | The dag {0} does not exist. |
| 4003 | A loop is found. |
| 4004 | A task context error occurred. |
| 4005 | Failed to run the {0} command on the host {1}. |
| 4006 | Failed to save the file {0} on the host {1}. |
| 4007 | The operation is not allowed because the {0} task is in the {1} state. |
| 4008 | The scheduled task {0} does not exist. |
| 6000 | Bad request. An error occurred while validating the parameter {0}. Please modify the parameter and try again. |
| 6001 | An alert service error occurred. Please contact the administrator. |
| 6002 | You (user ID: {0}) are not authorized to perform this operation. Please check your permissions and try again. |
| 6003 | You are not authorized to change the configurations of other users. Please check your permissions and try again. |
| 6004 | You are not authorized to read all clusters. Please check your permissions and try again. |
| 6005 | The alert group {0} is referenced in a subscription configuration. Please try again when it is no longer referenced by a subscription configuration. |
| 6006 | The alert rule (ID: {0}) is referenced by an alert group. Please try again when it is no longer referenced by an alert group. |
| 6007 | You cannot delete a system built-in alert. |
| 6008 | You cannot delete a default channel. |
| 6009 | The specified alert rule does not exist. Alert rule type: {0}. Please check. |
| 6010 | The specified alert group (ID: {0}) does not exist. Please check. |
| 6011 | The specified alert blocking configuration (ID: {0}) does not exist. Please check. |
| 6012 | The specified user (ID: {0}) does not exist. Please check. |
| 6013 | The specified alert (ID: {0}) does not exist. Please check. |
| 6014 | The alert indicator referenced by the alert rule {0} does not exist. Please check again. |
| 6015 | The specified alert rule expression is invalid. Please edit the expression and try again. |
| 6016 | An alert item (ID: {0}) with the same name already exists. Please change the name and try again. |
| 6017 | You cannot delete a system built-in alert group. |
| 6018 | A circular reference to the variable {0} exists in the template. Please modify the configuration template. |
| 6019 | The reference to the variable {1} in the template {0} is invalid. Please modify the configuration template. |
| 6020 | The alert is configured to last for {0}, which is less than the evaluation interval of {1}. Please make sure that the alert lasts longer than the evaluation interval. |
| 6021 | The alert blocking condition {0} is invalid. Please modify the condition and try again. |
| 6022 | When you replicate an alert group, you must specify a different name for the replica alert group. Please check and try again. |
| 6023 | You must specify the recipient address. |
| 6024 | The recipient address {0} is unavailable. Please check and try again. |
| 6025 | You must specify the recipient. |
| 6026 | The specified recipient address {0} is invalid. Please check and try again. |
| 6027 | The specified channel does not exist. Please check. |
| 6028 | The channel (ID: {0}) is referenced by a subscription (ID: {1}). Please first make sure that the channel is no longer referenced by a subscription, and then try again. |
| 6029 | You must enter the content of the script. |
| 6030 | You must specify a program in the shebang line of the script. Please check. |
| 6031 | The script {0} is not supported. Only Python or bash scripts are supported. |
| 6032 | You must specify the script file name. |
| 6033 | The format of the specified script file name {0} is invalid. It can only contain letters, digits, periods (.), and underscores (_). Please change the name and try again. |
| 6034 | The specified script file does not exist. Please upload the script to the /home/admin directory of OCP. |
| 6035 | The specified script file name ({0}) is a path, not a file. Please check and try again. |
| 6036 | An error occurred while reading the script file. Please check the access permission of the file. |
| 6037 | You must specify a channel for the notification. |
| 6038 | The proxy format {0} of the notification channel is invalid. Please check and try again. |
| 6039 | An error occurred while sending the notification. Please try again later. |
| 6040 | The format of the notification channel header {0} is invalid. Please check and try again. |
| 6041 | The notification channel does not support the method {0}. Please contact the administrator. |
| 6042 | The channel is not available. Please contact the administrator. |
| 6043 | Failed to update the notification {0}. Please try again later. |
| 6044 | Failed to send the test message. Error: {0}. |
| 6045 | The format of the URL is invalid ({0}). Please edit it and try again. |
| 6046 | Failed to get the task. Please check and try again. |
| 6047 | Failed to generate the alert event (ID: {0}). Please contact the administrator. |
| 6048 | Failed to create the alert group {0}. Please contact the administrator. |
| 6049 | Failed to create the alert blocking rule. Alert blocking ID: {0}. Contact the administrator. |
| 6050 | The specified alert channel name {0} already exists. |
| 6051 | You must specify the alert channel name. |
| 6052 | The specified alert channel name {0} is invalid. It cannot start or end with a space. |
| 6053 | The specified alert group name {0} already exists. |
| 6054 | You must specify the name. |
| 6055 | The specified name {0} is invalid. It cannot start or end with a space. |
| 7000 | The specified resource {0}:{1} contains one or more child resources. Please remove the child resources and try again. |
| 7001 | The specified host <{0}:{1}> already exists. Please change it and try again. |
| 7002 | Failed to connect to the target host {0}@{1}:{2} through SSH. Cause:{3}. Please modify the connection information and try again. |
| 7004 | The host {0} is offline or in use. Please release the host and try again after its status returns to {1}. |
| 7005 | The host <{0}:{1}> does not exist. |
| 7006 | The status of the host {0} does not support this operation. |
| 7007 | The IDC of the host {0} does not match that of the OBServer. |
| 7008 | The IDC of the host {0} does not match that of the target zone. |
| 7009 | The region of the host {0} does not match that of the target OBServer. |
| 7010 | You cannot deploy more than one {1} service of the same type on the host {0}. Please select another host and try again. |
| 7011 | You cannot deploy more than one {1} service on the container-type host {0}. Please select another host and try again. |
| 7012 | Agent service is already deployed on the host {0}. Please uninstall it and try again. |
| 7013 | The host with the IP address of <{0}> does not exist. |
| 7014 | The host with the IP address of <{0}> is not unique. |
| 7015 | Failed to connect to the host through SSH. Please check the IP address, credentials, and port that you entered. IP address of failed host: [{0}]. |
| 7016 | Failed to get the credentials for the host {0}. Please check if the credentials exist. |
| 7017 | The hosts that you selected are not running on the same operating system. Please select again. |
| 7018 | The hosts that you selected are not running on the same architecture. Please select again. |
| 7019 | The OCP Agent status of the host {0} does not support this operation. |
| 7020 | The network latency is too high for the SSH connection. Latency: {0} ms. Maximum allowed latency: {1} ms. |
| 7021 | The time difference between OCP and the host is too large. Host time: {0}. OCP time: {1}. Maximum allowed time difference: {2} ms. |
| 7022 | The specified IP address does not match the host IP address. Specified IP address: {0}. Host IP address: {1}. |
| 7023 | You must specify the OCP Agent dependency [{0}] for the host. |
| 7024 | The returned result of the SSH command does not match the expectation. Please check if the SSH command has returned other results to the console. |
| 7500 | The file {0}:{1} does not exist. |
| 7501 | The file block {0}:{1} does not exist. |
| 7502 | A file of the type {0} and the name {1} already exists. |
| 7503 | An error occurred while validating the file extension. File extension: {0}. Expected extension: {1}. |
| 7504 | An error occurred while validating the file type. File type: {0}. Expected type: {1}. |
| 7505 | Timed out while waiting for another request to complete handling the file. Please try again. |
| 7506 | An error occurred while parsing the software package. Please check the file type. |
| 7507 | The operation failed because the software package is in use. |
| 7508 | The format of the storage space is invalid. It must be 3 to 63 characters in length, start and end with a lowercase letter or a digit, and consist of lowercase letters, digits, and dashes (-). |
| 7509 | The storage space {0} does not exist. |
| 7510 | The storage space name already exists. |
| 7511 | The file {1} in storage space {0} is being uploaded. Please check the upload result later. |
| 7512 | A software package with a name of {0} already exists. |
| 7513 | The specified software package type is invalid. Software package type: {0}. Specified software package type: {1}. |
| 7514 | The software package {0} does not exist. |
| 8,000 | The user center is currently unavailable. Please try again later. |
| 8001 | You cannot delete content in the password box of other users. Parameter: {0}. |
| 8002 | An identical connection already exists. Please delete the old record and create the connection again. Parameter: {0}. |
| 8010 | An error occurred while validating the credentials. Cause: {0}. Please check whether the credentials can be used to connect to the target resource. |
| 8011 | Failed to decrypt the credential. Credential: {0}. Cause: {1}. Please check whether the same key is used for both encryption and decryption. For example, check whether the logon password of the OCP user has been manually changed. |
| 8012 | Failed to use the credential {0} to connect to the resource. Please check whether the credentials can be used to connect to the resource. |
| 8013 | Failed to use the SSH credential {0} to test the sudo permission. Please make sure that the user is granted the permission to run sudo commands and that NOPASSWD is enabled in '/etc/sudoers'. |
| 8014 | The SSH private key is not supported. Credential: {0}. Please verify the format of the private key and check whether the private key was generated by using an OpenSSL version earlier than 7.8. If not, add '-m PEM' to the keygen command to regenerate the private key. |
| 8500 | The {0} parameter is empty or invalid: {1}. You must use a complete URL that starts with http/https and contains the domain name and the port number. Please check the URL and try again. |
| 11001 | The specified cluster (ID: {0}) does not exist. |
| 11002 | The specified cluster (name: {0}) does not exist. |
| 11003 | The type of the specified cluster (ID: {0}) does not support this operation. |
| 11004 | The version of the specified cluster (ID: {0}) does not support this operation. Minimum supported version: {1}. |
| 11005 | The specified root server information is invalid. |
| 11007 | The current status of the {0} cluster does not support this operation. |
| 11008 | This operation is only supported when the {0} cluster is in the {1} state. |
| 11009 | The RootServer JSON {0} is invalid. |
| 11010 | No RootServer is found in the cluster with the ID of {0}. |
| 11011 | The specified password is incorrect. Please check whether the old password that you entered is correct. |
| 11012 | You must specify the password. |
| 11013 | You must specify the RPM package name. |
| 11014 | The cluster to be created already exists. |
| 11015 | This operation is not allowed because the cluster has a standby cluster. |
| 11016 | The config URL of the cluster does not belong to the current OCP. |
| 11017 | Failed to find the primary cluster of the {0} cluster. |
| 11018 | Multiple primary clusters exist in the {0} cluster. |
| 11019 | The server list of the {0} cluster is empty. |
| 11020 | The last O&M task of the cluster is not completed. |
| 11021 | The specified server is already deployed in a cluster. |
| 11022 | Hot standby is not enabled for the cluster. |
| 11023 | The specified cluster {0} does not satisfy the conditions for switching. |
| 11024 | |
| 11025 | The specified cluster {0} does not meet the conditions for switching. |
| 11026 | |
| 11030 | The specified number of servers does not match the number of servers to be added to the cluster. |
| 11031 | The specified IP address of the server does not match the IP address of the OBServer to be added to the cluster. |
| 11032 | Please first import the primary cluster, and then the standby clusters. |
| 11033 | The cluster to be imported already exists. |
| 11034 | You must specify the region information for the {0} zone in the cluster to be imported. |
| 11035 | You must specify the IDC information for the {0} zone in the cluster to be imported. |
| 11036 | You must specify the IDC information for the {0} zone in the cluster to be managed. |
| 11037 | The IDC {1} and region {2} of the {0} zone in the cluster to be managed do not match the IDC and region of OCP. |
| 11038 | The name {0} of the cluster to be managed is invalid. |
| 11039 | The cluster to be managed contains an invalid tenant name: {0}. |
| 11040 | The specified connection method is invalid. Valid values: proxy and direct. |
| 11041 | When the connection method is proxy, you must specify the cluster name. |
| 11042 | Cluster management precheck failed. Cause: {0}. |
| 11043 | OBServer precheck failed. |
| 11044 | You must specify the host information of the cluster to be managed. |
| 11045 | You must specify the host type of the cluster to be managed. |
| 11046 | You must specify the host type ID of the cluster to be managed. |
| 11047 | You must specify the host credentials ID of the cluster to be managed. |
| 11050 | The specified parameter {0} does not exist. |
| 11051 | The format of the value {1} of the {0} parameter is invalid. |
| 11052 | The effective scope of cluster parameters can be a cluster, zone, or server. The current value {0} is invalid. Please try again. |
| 11060 | The standby cluster (ID: {0}) cannot be updated because its synchronization status is not supported. |
| 11061 | You cannot upgrade a cluster earlier than version {0}. |
| 11062 | The target cluster version to be updated to is invalid. |
| 11063 | The path of updating from version {0} to {1} does not exist. |
| 11065 | You are not authorized to update the cluster {0}:{1}. |
| 11066 | You cannot update a primary/standby cluster earlier than version {0}. |
| 11070 | You cannot perform rolling restart by zone because it must as at least three zones in the {0} tenant. |
| 11100 | Failed to connect to the {0} cluster. Please check the username and password of the user {1} in the sys tenant in the password box, the whitelist settings for the sys tenant, and the network connectivity. |
| 11101 | Failed to connect to the {0} cluster. Please check the username and password for the user {1} in the sys tenant, the whitelist settings for the sys tenant, and the network connectivity. |
| 11102 | Failed to connect to the cluster {0}:{1} because no OBServer can be connected to. |
| 11201 | The major compaction version {1} does not exist for the cluster with an ID of {0}. |
| 11202 | Compaction query timed out. Please try again. |
| 11203 | The compaction statistics metric {0} is not supported. |
| 11204 | Failed to update the compaction parameters. Possible conflict requests may exist. Please check the update status several seconds later. |
| 11205 | You cannot start a compaction from a non-primary cluster. The cluster with an ID of {0} is a standby cluster. |
| 11501 | Failed to start OB-Agent on the host {0}. |
| 12001 | The format of the specified zone name is invalid. It must be 2 to 64 characters in length, start with a letter, and consist of letters, digits, and underscores (_). |
| 12002 | The {1} zone does not exist in the cluster with an ID of {0}. |
| 12003 | The {1} zone already exists in the cluster with an ID of {0}. |
| 12004 | The current status of the specified zone {0} does not support this operation. |
| 12005 | Failed to stop the {0} zone. |
| 12006 | The specified zone {0} cannot be deleted because it has one or more units. |
| 12007 | The last O&M task in the zone is not completed. |
| 12008 | A zone of the specified name already exists. |
| 12009 | A zone of the specified name already exists. |
| 13001 | The specified OBServer with an ID of {0} does not exist. |
| 13002 | The specified OBServer with an IP address of {0} and a port of {1} does not exist. |
| 13003 | The current status of the specified OBServer {0} does not support this operation. |
| 13004 | OBSbserver {0} did not exit. |
| 13005 | Failed to start OBSbserver {0}. |
| 13006 | The IP address of the target OBServer is invalid. |
| 13007 | The RPC port of the target OBServer is invalid. |
| 13008 | The SQL port of the target OBServer is invalid. |
| 13009 | The number of remaining servers cannot be less than the number of units in the {1} zone of the {0} tenant. |
| 13010 | OB-Agent {0} did not exit. |
| 13011 | You cannot delete the OBServer. Cause: {0}. |
| 13012 | The last O&M task on the OBServer is not completed. |
| 13013 | The OBServer with an IP address of {0} does not exist. |
| 13014 | The specified OBServer is not unique. IP address: {0}. |
| 13015 | Did not exit. |
| 15001 | The specified specification ID {0} does not exist. |
| 15002 | The specified specification name {0} does not exist. |
| 15003 | The format of the specified specification name is invalid. It must be 2 to 32 characters in length, start with a letter, and consist of letters, digits, and underscores (_). |
| 15004 | The specified specification name {0} already exists. |
| 15005 | The specified number of CPU cores is invalid. Minimum value: 0.5. |
| 15006 | The specified memory size is invalid. Minimum value: 1073741824. Unit: bytes. |
| 15007 | The specified disk size is invalid. Minimum value: 10737418240. Unit: bytes. |
| 15008 | The specified IOPS value is invalid. Minimum value: 128. |
| 15011 | The minimum number of CPU cores cannot be larger than the maximum number of CPU cores. |
| 15012 | The minimum memory size cannot be larger than the maximum memory size. |
| 15013 | You must specify the specification parameter on the modification page. |
| 15014 | You cannot modify specifications of the system type. |
| 15015 | You cannot delete specifications of the system type. |
| 15020 | The format of the specified tenant name is invalid. It must be 2 to 64 characters in length, start with a letter, and consist of letters, digits, and underscores (_). |
| 15021 | The {1} tenant already exists in the {0} cluster. |
| 15022 | The {1} tenant does not exist in the {0} cluster. |
| 15023 | The specified tenant (ID: {0}) does not exist. |
| 15024 | The specified tenant (ID: {0}) is already deleted. |
| 15025 | The current status of the specified tenant {0} does not support this operation. |
| 15026 | The specified tenant{0} cannot be deleted. |
| 15027 | You are not authorized to perform this operation on the specified tenant {0}. |
| 15028 | Failed to set password for the specified tenant (ID: {0}). |
| 15030 | The specified tenant mode is invalid. Valid values: MYSQL and ORACLE. |
| 15031 | The specified primary zone name must be less than 128 characters in length. |
| 15032 | The specified primary zone name is invalid. |
| 15033 | The length of the specified whitelist is invalid. The whitelist must be less than 65535 characters in length. |
| 15034 | The length of the specified password is invalid. The password must be less than 32 characters in length. |
| 15035 | The length of the description is invalid. The description must be less than 1024 characters in length. |
| 15036 | Minimum supported version in Oracle mode: {0}. Current version: {1}. |
| 15037 | The specified zone is incorrect. |
| 15038 | The specified collation is invalid. |
| 15039 | You must have at least one zone in the tenant. |
| 15040 | The specified zone {0} is invalid. |
| 15041 | The specified zone {0} does not exist. |
| 15042 | No resource pool is available in the specified zone: {0}. |
| 15043 | The specified unit {0) does not exist. |
| 15044 | The specified unit {0} cannot be deleted because it is the only resource unit in its zone. |
| 15045 | The number of specified units is invalid. |
| 15046 | The number of specified units cannot exceed the number of active servers in the zone. |
| 15050 | No server is available in the {0} tenant. |
| 15060 | The specified tenant parameter {0} does not exist. |
| 15061 | The specified tenant parameter {0} is read-only. |
| 15062 | Failed to get the old value of the specified tenant parameter {0}. |
| 15080 | The specified replica type is invalid. |
| 15082 | Failed to find the locality modification progress for the {0} tenant. |
| 15083 | The locality modification for the {0} tenant is not competed. |
| 15084 | The scale-in of the resource pool for the {0} tenant is not competed. |
| 15100 | Failed to connect to the {0} tenant. Please check the password for the root user in the password box and the whitelist settings for the sys tenant. |
| 15200 | The format of the specified database name is invalid. It must be 2 to 128 characters in length, start with a letter, and consist of letters, digits, and underscores (_). |
| 15201 | A database with the specified name {0} already exists. |
| 15202 | The specified database {0} does not exist. |
| 15203 | You must specify the input parameter for database modification. |
| 15204 | The database {0} does not support the operation. |
| 15205 | The specified collation is invalid. |
| 15206 | Oracle tenants do not support this operation. |
| 15250 | The format of the specified username is invalid. It must be 2 to 128 characters in length, start with a letter, and consist of letters, digits, and underscores (_). |
| 15251 | The specified username {0} already exists. |
| 15252 | The specified user {0} does not exist. |
| 15253 | User {0} is not authorized to perform this operation. |
| 15254 | Oracle tenants do not support this operation. |
| 15255 | The permission of the database {0} is invalid. |
| 20000 | OceanBase Database version {0} does not support backup and recovery. |
| 20001 | The configuration file {0} exists, but no backup component for version {1} of the {2} cluster is available. |
| 20002 | The installation directory {1} with an IP address of {1} already exists. Please check manually. |
| 20003 | You must first back up the scheduling settings for the {0} cluster. |
| 20004 | The specified parameter is invalid. |
| 20005 | You must specify the backup configuration in the component for version {0} of the {1} cluster. |
| 20006 | No {0} component suitable for the cluster is online. Please check. |
| 20007 | A baseline backup task already exists for the cluster or tenant. |
| 20008 | Failed to perform an immediate backup of the cluster. |
| 20009 | Failed to initiate data restoration. |
| 20010 | You must specify the URI in the backup configuration {0}. |
| 20011 | You must specify the endpoint in the backup configuration {0}. |
| 20012 | You must specify the AccessKey ID in the backup configuration {0}. |
| 20013 | You must specify the AccessKey Secret in the backup configuration {0}. |
| 20014 | The backup version number of the {0} tenant does not exist in the backup file. |
| 20015 | An error occurred while parsing the tenant information in the backup file. |
| 20016 | Failed to add a configuration file. |
| 20017 | The configuration cannot be deleted because it is used by the {0} component. |
| 20018 | The configuration name {0} already exists. |
| 20020 | The {0} component failed. |
| 20021 | An O&M task (TaskId:{0}) is already in progress on the host. Please initiate a new O&M task after this task is completed. |
| 20022 | The host is already used by the cluster or the backup and recovery module. |
| 20023 | Failed to update the host status. HostId: {0}. agentStatus: {1}. |
| 20024 | The specified backup and recovery parameter {0} does not exist. |
| 20025 | The format of the value {1} of the backup and recovery parameter {0} is invalid. |
| 20030 | Data backup is not started. |
| 20031 | Log backup is not started. |
| 20032 | The same cluster or tenants in the same cluster can have only one copy of scheduling settings. The configuration for the {1} tenant in the {0} cluster already exists. Please delete the existing configuration before specifying a new one. |
| 20033 | Failed to stop log backup. Error: {0}. |
| 20040 | Failed to create resource unit {0} during tenant recovery. {1}. |
| 20041 | The format of {0} in the pool list is invalid. Please check. |
| 20042 | The specified pool already exists in the pool list. Please change the pool name. |
| 20043 | The specified new tenant {0} is being recovered. Please check. |
| 20044 | The specified new tenant name {0} already exists. Please change the tenant name. |
| 20045 | Internal error. More than one matching recovery task exists. |
| 20046 | The task with an ID of {0} does not exist. |
| 20047 | The task {0} cannot be canceled because it is in the {1} state. Only failed tasks can be canceled. |
| 20048 | You cannot delete the restoration residual data of tasks that are not failed during data restoration. |
| 20050 | A primary/standby switchover may have occurred in the {0} cluster. You cannot back up the standby cluster {1}. Please back up the primary database {1} to a new backup directory. |
| 20060 | The format of the specified configuration name is invalid. It must be 2 to 32 characters in length, start with a letter, and consist of letters, digits, and underscores (_). |
| 20061 | The service configuration has been changed. 20062 error.backup.config.name.existed The specified name {0} already exists. Please specify another name. |
| 20063 | The specified storage configuration name or path already exists. Please specify another storage configuration name or path. |
| 20064 | Storage configuration test failed on {0}. Please make sure that the configuration can be accessed. |
| 20065 | The storage configuration name {0} already exists. Please specify another storage configuration name. |
| 20066 | No storage configuration exists. Please install a service and configure the storage. |
| 20067 | You must specify the {0} parameter. |
| 20070 | Service installation failed. |
| 20071 | Host operation failed. |
| 20072 | The backup service {0} is not operating properly and may affect the backup. Please check. |
| 20073 | No service is available to backup and recover the MetaDB {0}. Please install the service first. |
| 20074 | You must specify the {0} parameter. |
| 20075 | The service with an ID of {0} does not exist. |
| 20076 | The service named {0} does not exist. |
| 20077 | The service with a storage configuration of {0} does not exist. Please install the service first. |
| 20078 | The matching service {0} is not running. Please start it first. |
| 20079 | The service cannot be deleted because it has {0} nodes. Please first delete the backup and recovery program on the nodes. |
| 20080 | The status before the {2} operation on the host {1} of the service {0} does not meet the requirement. Expected status: {3}. Actual status: {4}. |
| 20081 | The service {0} cannot be deleted because it is used by the backup strategy of the cluster {1}. |
| 20082 | The configuration for the service is not changed. |
| 20083 | No configuration of the {1} type exists in the {0} service. |
| 20090 | The request parameter {0} is invalid. |
| 20091 | The request object {0} does not exist. |
| 20092 | Invalid SQL: {0}. |
| 20093 | The request parameter {0} in the SQL query is invalid. |
| 20100 | The {0} cluster (ID: {1}) already has a backup strategy. Please delete or edit the existing strategy. |
| 20101 | The {2} tenant (ID:{3}) in the {0} cluster (ID: {1}) already has a backup strategy If you continue, the new strategy will overwrite the existing backup strategy of the {2} tenant. |
| 20102 | The {2} tenant (ID:{3}) in the {0} cluster (ID: {1}) already has a backup strategy. Please delete or edit the existing strategy. |
| 20103 | The {2} tenant (ID:{3}) in the {0} cluster (ID: {1}) already has a backup strategy. If you have more than two tenants, we recommend that you use a cluster backup strategy. |
| 20104 | The {0} cluster (ID: {1}) already has a backup strategy. You do not need to create a tenant-level backup strategy. |
| 20105 | The format {1} of the scheduling duration {0} is invalid. Please check. |
| 20106 | The backup object {0} does not have a backup strategy. |
| 20107 | You must specify the backup object. Please check. |
| 20108 | The backup object {0} does not support the backup method {1}. |
| 20109 | You cannot test the storage configuration of a cluster that does not support physical backup if the cluster does not have a backup strategy. |
| 20110 | The logical backup method only supports full backup. |
| 20111 | During a physical backup, you must perform a full backup before you can perform an incremental backup. |
| 20112 | You cannot change the backup method in the backup strategy from physical backup to logical backup. |
| 20120 | An exception occurred while parsing the backup file. Content: {0}. |
| 20121 | Failed to parse the file name {0}. The number after the last slash in the file name must be an integer. |
| 20130 | An error occurred while retrieving the backup file. Failed to run the {1} command on the host {0}. |
| 20140 | This feature is not supported for physical backup. |
| 20141 | The OceanBase version {0} does not support the {1} backup method. |
| 20150 | Failed to set the backup path. Error: {0}. |
| 20151 | The cluster is being backed up to {0}. You cannot change the backup path to the new path {1}. |
| 21001 | The OBProxy cluster with an ID of {0} does not exist. |
| 21002 | The OBProxy server with an ID of {0} does not exist. |
| 21003 | The OBProxy server with an ID of {0} and a status of {1} does not exist. |
| 31100 | The specified property {0} in advanced search is invalid. |
| 31101 | The specified operator {0} in advanced search is invalid. |
| 31102 | The specified value {0} in advanced search is invalid. |
| 31103 | The specified UID {0} of the plan is invalid. |
| 31104 | The selected time range is larger than the maximum range of {0}. Please reduce the range and try again. |
| 31105 | The query timed out because the selected time range is too large. Please reduce the range and try again. |