10000 to 12000

This range includes error codes related to OBProxy, OBSharding, OBKV, and the client.

ERROR 10500 (HY000): incorrect route for obkv global index, client router should refresh.

• OceanBase error code: 10500

• Cause: The route for the OBKV global index is incorrect. The client router needs to be refreshed.

• Solution: Please verify your client connection and routing information.

ERROR 10501 (HY000): TTL feature is not enabled

• OceanBase error code: 10501

• Cause: The TTL feature is not enabled.

• Solution: Ensure that the TTL feature is correctly enabled.

ERROR 10502 (HY000): TTL column '%.*s' not exists

• OceanBase error code: 10502

• Cause: The specified TTL column does not exist.

• Solution: Please verify whether the specified TTL column exists in the database table.

ERROR 10503 (HY000): Column type of '%.*s' is not supported for TTL definition

• OceanBase error code: 10503

• Cause: The specified column type is not supported for TTL definition.

• Solution: Verify whether the specified column type is supported for TTL definition.

ERROR 10504 (HY000): TTL command is not allowed, current TTL status is '%s'

• OceanBase error code: 10504

• Cause: The TTL command is not allowed because the current TTL status is a specific value.

• Solution: Check whether the current status is as expected and switch the status by using an appropriate TTL command.

ERROR 10505 (HY000): No TTL task is running, please try trigger a new TTL task

• OceanBase error code: 10505

• Cause: No TTL task is running. You need to try triggering a new one.

ERROR 10506 (HY000): Cannot execute TTL task during tenant is restore

• OceanBase error code: 10506

• Cause: TTL tasks cannot be executed during tenant restore.

ERROR 10507 (HY000): Time to live of hbase table must be greater than 0

• OceanBase error code: 10507

• Cause: The Time To Live (TTL) of an HBase table must be greater than 0.

• Solution: Check the KV_ATTRIBUTES attribute of the current table to ensure that the defined TimeToLive is greater than 0.

ERROR 10508 (HY000): MaxVersions of hbase table must be greater than 0

• OceanBase error code: 10508

• Cause: The MaxVersions value of an HBase table must be greater than 0.

• Solution: Check the KV_ATTRIBUTES attribute of the current table to ensure that the defined MaxVersions value is greater than 0.

ERROR 10509 (HY000): Access denied, credential '%.*s' not match '%.*s'

• OceanBase error code: 10509

• Cause: Access is denied because the credentials '%.*s' do not match '%.*s'.

• Solution: Enter the correct credentials again. Ensure the username and password are correct and no errors were made in the input.

ERROR 10510 (HY000): Rowkey column count not match, schema rowkey count is '%ld', input rowkey count is '%ld'

• OceanBase error code: 10510

• Cause: The number of columns in the rowkey does not match the number of columns in the database table during the operation.

• Solution: Make sure that the number of row key columns during operation is consistent with the actual number of row key columns in the table.

ERROR 10511 (HY000): Column type for '%.*s' not match, schema column type is '%.*s', input column type is '%.*s'

• OceanBase error code: 10511

• Cause: The input column type does not match the column type of the database table. This may cause data conversion errors or prevent the operation from being executed correctly.

• Solution: Ensure that the input column type matches the column type of the table during the operation.

ERROR 10512 (HY000): Collation type for '%.*s' not match, schema collation type is '%.*s', input collation type is '%.*s'

• OceanBase error code: 10512

• Cause: The collation types do not match.

• Solution: Ensure that the input collation type matches the table's collation type during the operation.

ERROR 10513 (HY000): Scan range missing, input scan range cell count is '%ld', which should equal to rowkey count '%ld'

• OceanBase error code: 10513

• Cause: The number of columns in the scan range does not match the number of primary key columns in the table during a scan operation.

• Solution: Ensure that the number of columns in the scan range equals the number of primary key columns during the scan operation.

ERROR 10515 (HY000): Redis protocol parse error, the input redis string is: '%.*s'

• OceanBase error code: 10515

• Cause: Redis protocol parsing error.

• Solution: The client may have sent a custom Redis command that is not supported by OceanBase Database, or the command format is incorrect.

ERROR 10516 (HY000): When invoking the Increment interface, only HBase cells with a length of 8 can be converted to int64_t. the current length of the HBase cell is '%d'

• OceanBase error code: 10516

• Cause: When using the Increment API in OBKV-HBase, the value of the cell to be incremented or decremented must be an 8-byte long type (Java long/int64) in big-endian format (Big-Endian, meaning the high-order byte is placed first and the low-order byte is placed last). If the value is not an 8-byte long, the operation fails. Common causes include:

  • The incremental data written by the client is not an 8-byte long, such as strings, text, int32, etc., instead of being encoded as a long type.
  • The column previously had non-8-byte data written via Put or Append (such as strings, variable-length binary, etc.), causing the current value type to not be long.

• Solution:

  • When the client writes incremental data, be sure to encode it as an 8-byte big-endian long (in Java, you can use org.apache.hadoop.hbase.util.Bytes.toBytes(long)).
  • If a cell already has data that is not a long, you can delete or overwrite it with a valid 8-byte long before performing an Increment operation.

ERROR 10518 (HY000): Check failed in %.*s"

• OceanBase error code: 10518

• Cause: When the rollbackWhenCheckFailed parameter of the OBKV checkAndInsertup interface is set to true, this error code is thrown if the check fails.

• Solution: This error indicates a check failure. Handle it accordingly based on your business requirements, such as ignoring it or performing other necessary processing.

ERROR 10519 (HY000): '%.*s' is not disabled

• OceanBase error code: 10519

• Cause: The current table status is not DISABLED, so you cannot use the enableTable() or deleteTable() interface of HBase Admin.

• Solution: Call the disableTable() interface of HBase Admin to set the table status to DISABLED, and then try again.

ERROR 10520 (HY000): '%.*s' is not enabled

• OceanBase error code: 10520

• Cause: The current table is not in the ENABLED state, so the table cannot be accessed.

• Solution: Call the enableTable() API of HBase Admin to set the table state to ENABLED, and then retry.

ERROR 10521 (HY000): namespace '%.*s' is not found

• OceanBase error code: 10521

• Cause: The specified HBase namespace does not exist.

• Solution: Create the corresponding HBase namespace in the OBKV-HBase database, and then retry.

ERROR 10522 (HY000): table '%.*s' already exists

• OceanBase error code: 10522

• Cause: The specified HBase table already exists.

• Solution: Verify whether the existing table meets your requirements. Otherwise, you can delete and recreate the HBase table you need.

ERROR 10523 (HY000): table '%.*s' not found

• OceanBase error code: 10523

• Cause: The specified HBase table does not exist.

• Solution: Create the corresponding HBase table.

ERROR 10650 (HY000): ODP process timeout

• OceanBase error code: 10650

• Cause: The ODP process execution timed out.

• Solution: Check whether the operation contains long-running steps, and increase the operation timeout.

ERROR 11014 (HY000): Can't find FULLTEXT index matching the column list

• OceanBase error code: 11014

• Cause: No full-text index matching the query columns was found.

• Solution: Verify whether the table has a full-text index and which columns it covers. Create a full-text index for the missing columns and make sure the query columns match the index columns.

ERROR 11015 (HY000): Can't update table '%s' while '%s' is being created.

• OceanBase error code: 11015

• Cause: The table cannot be updated while it is being created.

• Solution: Wait until the table creation completes, and then retry.

ERROR 11018 (HY000): Invalid external file: %s

• OceanBase error code: 11018

• SQLSTATE: HY000

• Cause: The specified external file cannot be read correctly.

• Solution:

  • Verify that the file exists, the file path is correct, and the current user has access permissions for the file.

  • Check whether the file format or encoding matches.

  • Check whether the file content is corrupted or has format errors.

ERROR 11020 (HY000): HDFS: could not open file on hdfs

• OceanBase error code: 11020

• Cause:

  • The file may not exist or you may not have permission to access it.

  • The file open mode does not match.

• Solution:

  • Verify that the file path is correct and the file actually exists on HDFS.

  • Check HDFS file permissions and make sure the current user has read or write permissions.

  • Verify that the HDFS namenode or datanode services are running properly.

ERROR 11021 (HY000): HDFS: error reading the file on hdfs

• OceanBase error code: 11021

• Cause: Failed to read the HDFS file.

• Solution:

  • Verify that the HDFS datanode nodes are running properly and the network connection is normal.

  • Check HDFS logs (HDFS-related logs, not on the OceanBase Database server) to see whether there are corrupt blocks or unavailable replicas.

ERROR 11032 (HY000): HDFS path message %s

• OceanBase error code: 11032

• Cause: The HDFS path message %s error usually occurs in the following scenarios:

  1. In an HDFS environment with Kerberos authentication enabled, when you access an HDFS external table, if you do not have sufficient permissions to access it, error -11032 occurs.

  2. If Kerberos authentication is configured correctly but you still see HDFS: path not found, the external table path specified in the CREATE EXTERNAL TABLE statement may be incorrect and points to a non-existent path.

  3. If external table access works initially but error 11032 occurs after querying for a while, a file under the HDFS path of the external table may have a corrupt block. That is, the HDFS DataNode reports that the data block is corrupted and cannot be accessed, which triggers this error.

• Solution:

  1. Verify that the Kerberos keytab and principal are valid and the corresponding user has access permissions for the HDFS cluster. Reconfigure external table permissions and set up Kerberos authentication.

  2. Verify that the corresponding HDFS path is correct and exists. Re-establish the HDFS path mapping for the external table.

  3. Report the issue to your operations team. After confirming the corrupt block situation, you can choose to repair the corrupt block or switch to another environment for further verification.

ERROR 11042 (HY000): HDFS: malformed uri

• OceanBase error code: 11042

• Cause:

  • The URI is missing the hdfs:// prefix.

  • The URI is missing the path part. That is, there is no /path after hdfs://authority.

• Solution:

  • Make sure the URI format is hdfs://<namenode>:<port>/<path>, which must include the complete scheme, authority, and path.

  • Check whether the spelling of the LOCATION field in the external table or backup configuration is correct.

ERROR 11043 (HY000): HDFS: invalid argument

• OceanBase error code: 11043

• Cause:

  • The HDFS URI format is incorrect.
  • The Kerberos authentication configuration is incorrect.
  • The HDFS client environment is not initialized or is invalid.
  • The HDFS connection parameters are invalid.
  • Failed to set HDFS configuration items.

• Solution:

  • Check whether the HDFS URI format is correct and whether the HDFS-related configuration is complete.
  • Verify that the files required for Kerberos authentication (keytab, krb5.conf, ticket cache) exist and the paths are correct.
  • Check the network connectivity of the HDFS cluster and make sure the namenode is accessible.
  • Check whether the key=value format of custom HDFS configuration items is correct and make sure there are no empty keys or values.

ERROR 11044 (HY000): HDFS: not implementation

• OceanBase error code: 11044

• Cause: You are attempting to use a feature that HDFS has not implemented. The current HDFS storage backend does not support pwrite and append write operations.

ERROR 11045 (HY000): HDFS error

• OceanBase error code: 11045

• Cause:

  • Duplicate access. An already opened file may be opened again.

  • Operations such as delete, mkdir, and list are attempted before HDFS successfully establishes a connection.

  • File deletion failed. The file may not exist or you may not have sufficient permissions.

  • Directory creation failed.

  • Write failed.

  • Flush failed.

• Solution:

  • Check HDFS file or directory permissions and make sure the current user has read, write, and delete permissions.

  • Verify that the target path exists and the format is correct.

  • Make sure the lifecycle management of HDFS components is correct to avoid duplicate access or operations before a connection is successfully established.

  • Check whether the HDFS cluster has sufficient disk space.

ERROR 11046 (HY000): Invalid path: %.*s

• OceanBase error code: 11046

• SQLSTATE: HY000

• Cause:

  • The column name or path entered in the DDL does not match the spelling or case of the column name in the file (Parquet, ORC, Arrow, etc. are usually case-sensitive).

  • The nested structure path is incorrect. For example, you need to access addr.city, but the DDL uses addr_city or address.city.

  • Under the same external table, some files are missing the column.

  • Format symbol issues. For example, extra spaces, quotes before or after the column name, or escape errors.

• Solution:

  • Verify that the data_access_path or EXTERNAL_FILE_COLUMN_PATTERN on external columns in the DDL statement actually exists in the file schema.

  • For nested types, use the actual hierarchical path separator in the file for an exact match.

  • If the schemas of files in different partitions are different, create separate external tables for the partitions with missing columns, or set a default value for the column to avoid directly mapping missing columns by path.

  • Modify the incorrect column definition and recreate the external table.

ERROR 11047 (HY000): Column type mismatch between the file and the table: FileColumnType=%s TableColumnType=%s

• OceanBase error code: 11047

• SQLSTATE: HY000

• Cause: The column type in the file does not match the table definition.

• Solution: Compare the file content with the table definition, identify the mismatched column types, and modify the table definition or file content.

ERROR 11049 (HY000): Exceed query memory limit (mem_limit=%ld, mem_hold=%ld), please check whether the query_memory_limit_percentage configuration item is reasonable.

• OceanBase error code: 11049

• Cause: The query memory exceeds the limit.

• Solution: Check the value of the query_memory_limit_percentage configuration item and make sure the setting is reasonable.

ERROR 11050 (HY000): Odps driver throw exception: ExceptionMsg=%s

• OceanBase error code: 11050

• Cause: An ODPS driver exception occurred.

• Solution:

  • Verify that the ODPS connection configuration is correct.

  • Check network connectivity and make sure the network connection is normal.

  • Verify that the ODPS table exists.

  • Check the ODPS table structure and permissions. Make sure the current user has Describe, Select, and project access permissions.

ERROR 11051 (HY000): Column type mismatch between the ODPS table and the OceanBase table: OdpsColumnType=%s TableColumnType=%s

• OceanBase error code: 11051

• Cause: The column data types of the ODPS table and the OceanBase external table definition do not match.

• Solution: Check the actual structure of the ODPS table and the definition of the OceanBase external table, identify the mismatched columns and types, and then modify the OceanBase external table definition.

ERROR 11052 (HY000): unexpected error for exteran odps table:%s

• OceanBase error code: 11052

• Cause:

  • Network or connection interruption during the query.

  • ODPS server exception.

  • Incorrect data format in the ODPS table.

  • Resource limits on ODPS or OceanBase Database.

• Solution:

  • Check network connectivity.

  • Check the ODPS service status.

  • Check the data format in the ODPS table for data encoding issues, unhandled special characters, or data corruption.

  • Check resource limits on ODPS or OceanBase Database, such as insufficient memory or computation limits.

ERROR 11053 (HY000): unexpected error for jni

• OceanBase error code: 11053

• Cause: A Java error exception occurred.

• Solution: Check the error exception log context to identify the root cause and resolve it.

ERROR 11054 (HY000): class could not be found during jni operation

• OceanBase error code: 11054

• Cause: A class does not exist or cannot be found.

• Solution: Check the current log to see which class cannot be found. Download and install the corresponding JAR package to the appropriate path, and restart OBServer.

ERROR 11055 (HY000): method could not be found during jni operation

• OceanBase error code: 11055

• Cause: A method in a class does not exist or cannot be found.

• Solution: Check the current log to see which method of which class cannot be found. The corresponding JAR package may be missing, or a version mismatch may have caused the method to be missing. Download the corresponding JAR package to the appropriate path and restart OBServer.

ERROR 11056 (HY000): jvm.so not found %s

• OceanBase error code: 11056

• Cause: When creating or accessing external tables such as HDFS or ODPS in OceanBase Database, this error is triggered because JVM environment initialization failed.

• Solution: Check whether the JVM runtime environment configuration is correct.

ERROR 11057 (HY000): JNI env could not delete ref

• OceanBase error code: 11057

• Cause: Failed to delete a reference in the Java environment.

• Solution: There may be a code logic error. This error does not exist in the current code logic because the corresponding logic has been removed. Contact technical support for assistance.

ERROR 11058 (HY000): cur java home path %s

• OceanBase error code: 11058

• Cause: The JAVA path is set incorrectly.

• Solution: Configure the correct JAVA path.

ERROR 11059 (HY000): JNI cound not ensure capacity

• OceanBase error code: 11059

• Cause: The maximum and minimum heap memory sizes set in ob_java_opts for Java startup are too small, or the machine does not have sufficient memory resources.

• Solution: Check the machine memory resources, the memory size set for the current Java process, and the ob_java_opts environment variable settings.

ERROR 11060 (HY000): field could not be found during jni operation

• OceanBase error code: 11060

• Cause: A field in a class does not exist.

• Solution: Update and replace the compatible JAR package. The JAR package is expected to have this field.

ERROR 11061 (HY000): object could not be found during jni operation

• OceanBase error code: 11061

• Cause: During the operation, a JNI-generated class object instance does not exist.

• Solution: There is a code logic issue that caused this problem. Contact technical support for assistance.

ERROR 11063 (HY000): missing format for external table

• OceanBase error code: 11063

• Cause: When creating an external table, the file format is not specified or no valid format configuration appears in the DDL statement.

• Solution:

  • Add a FORMAT clause in the CREATE EXTERNAL TABLE statement and specify a TYPE consistent with the actual file.

  • Verify that the TYPE is consistent with the actual file extension and content (for example, if the directory contains .parquet files, use PARQUET instead of CSV).

  • If you use CSV, add delimiter, encoding, and other parameters as needed to avoid query parsing exceptions after the table is created successfully.

ERROR 11064 (HY000): missing access path for external table

• OceanBase error code: 11064

• Cause: When creating an external table, the data access path is not specified. Usually, LOCATION is not configured, is empty, or is not correctly bound to a Location object.

• Solution:

  • Add LOCATION in the DDL statement to point to the directory or URL where external data is actually stored.

  • Make sure the path is accessible to the OceanBase cluster (configure network, authentication, mounting, object storage AK/SK, etc. according to your environment).

  • If you use a Location object, make sure the object has been created and the current user has read permissions before referencing it on the external table.

  • We recommend that you use a protocol prefix agreed upon with relevant personnel (such as file://, oss://, hdfs://, etc., depending on the version supported).

ERROR 11065 (HY000): fail to read orc file, message: %s

• OceanBase error code: 11065

• Cause: Failed to read the ORC file.

• Solution: Check the ORC file message: %s.

ERROR 11076 (HY000): The plugin's version is incompatible with current server

• OceanBase error code: 11076

• Cause: The plugin to be loaded is incompatible with the current observer process.

• Solution: Find a plugin compatible with the observer version on the node where the specific error occurred, upload it again, and retry the installation.

ERROR 11077 (HY000): Failed to open library

• OceanBase error code: 11077

• Cause: Failed to load the specified dynamic library plugin.

• Solution: Check whether the plugin dynamic library to be loaded exists in the plugin_dir directory under the observer execution path on all nodes, and make sure the plugin dynamic library has read and execute permissions and that the dependent glibc version is not higher than the local glibc version.

ERROR 11078 (HY000): Plugin internal error

• OceanBase error code: 11078

• Cause: An internal error occurred. This is a defensive error when processing plugin-related functions.

• Solution: This is an internal error code. Contact technical support for assistance.

ERROR 11079 (HY000): Can't create catalog '%.*s'; catalog exists

• OceanBase error code: 11079

• Cause: A catalog with the same name already exists.

• Solution: Use the IF NOT EXISTS keyword or delete the old catalog and then recreate it.

ERROR 11080 (HY000): Catalog '%.*s' doesn't exist

• OceanBase error code: 11080

• Cause: The catalog to be queried has been deleted.

• Solution: Create a new catalog.

ERROR 11081 (HY000): skip_header and parse_header cannot be used at the same time

• OceanBase error code: 11081

• Cause: PARSE_HEADER and SKIP_HEADER cannot be used at the same time because they conflict semantically.

• Solution: When specifying attributes related to external file formats, do not use PARSE_HEADER and SKIP_HEADER at the same time.

ERROR 11082 (HY000): DDL operations on the internal catalog are not allowed

• OceanBase error code: 11082

• Cause: DDL operations on the internal catalog are not allowed.

• Solution: Check the type of the catalog to be operated on.

ERROR 11083 (HY000): Command denied to user '%.*s'@'%.*s' for catalog '%.*s'

• OceanBase error code: 11083

• Cause: The user does not have operation permissions for the catalog.

• Solution: Check whether the user has permissions for the catalog and grant the user the corresponding catalog operation permissions.

ERROR 11085 (HY000): CCL rule '%.*s' already exists

• OceanBase error code: 11085

• Cause: When creating a CCL rule, a rule with the same name already exists.

• Solution: Use the IF NOT EXISTS keyword or delete the old rule and then recreate it.

ERROR 11086 (HY000): CCL rule '%.*s' doesn't exist

• OceanBase error code: 11086

• Cause: When modifying or deleting a CCL rule, the rule does not exist.

• Solution: Use the IF EXISTS keyword or verify that the rule name is correct.

ERROR 11087 (HY000): SQL reach max ccl rule %s, concurrent num %ld

• OceanBase error code: 11087

• Cause: The SQL concurrency has reached the upper limit of the CCL rule.

• Solution: Retry after the concurrency decreases, or increase the value of MAX_CONCURRENCY.

ERROR 11089 (HY000): Location is still in use

• OceanBase error code: 11089

• Cause: The Location object being accessed is still in use by external tables.

• Solution: Check all external tables that depend on this Location object, verify that the dependencies have been removed, and then retry the operation.

ERROR 11090 (HY000): Location access denied

• OceanBase error code: 11090

• Cause: The specified Location object cannot be accessed.

• Solution: Check the user's access permissions for the Location object. Use the GRANT READ ON LOCATION location_name TO user_name WITH GRANT OPTION; command to grant the user READ permissions.

ERROR 11091 (HY000): Can't create location '%.*s'; location exists

• OceanBase error code: 11091

• Cause: The specified Location object already exists and cannot be created.

• Solution: Check whether the specified Location object already exists. Add the OR REPLACE keyword to replace the original Location object definition with a new one, or create a new Location object.

ERROR 11092 (HY000): location '%.*s' doesn't exist

• OceanBase error code: 11092

• Cause: The specified Location object does not exist.

• Solution: Check whether the specified Location object exists and specify the correct Location object.

ERROR 11093 (HY000): OBLogService rpc execute failed

• OceanBase error code: 11093

• Cause: Log service RPC execution failed due to insufficient resources on the target node or a network failure.

• Solution: Use trace_id to locate the target node logs first, and resolve the issue by combining resource monitoring and parameter adjustments.

ERROR 11094 (HY000): Sensitive rule '%.*s' exists

• OceanBase error code: 11094

• Cause: A sensitive rule with the same name already exists. This usually occurs when adding a sensitive rule through a DDL statement and the new rule has the same name as an existing rule.

• Solution: Check whether the specified sensitive rule name already exists and specify a name that does not exist.

ERROR 11095 (HY000): Sensitive rule '%.*s' does not exist

• OceanBase error code: 11095

• Cause: No sensitive rule with the specified name exists. This usually occurs when deleting a sensitive rule through a DDL statement and specifying a rule name that does not exist.

• Solution: Check whether the entered sensitive rule name is correct and enter the correct sensitive rule name.

ERROR 11096 (HY000): Sensitive column %.*s(%.*s) exists

• OceanBase error code: 11096

• Cause: The column with the specified name is already a sensitive column. This usually occurs when adding or modifying a sensitive rule through a DDL statement and attempting to apply a sensitive rule to a column already covered by another sensitive rule.

• Solution: Check whether the specified column is a sensitive column and choose an appropriate column to add the sensitive rule.

ERROR 11097 (HY000): Sensitive column %.*s(%.*s) does not exist

• OceanBase error code: 11097

• Cause: No sensitive column with the specified name exists. This usually occurs when modifying a sensitive rule through a DDL statement and attempting to remove a column that is not a sensitive column.

• Solution: Check whether the specified sensitive column exists and enter the correct sensitive column name.

ERROR 11098 (HY000): %.*s command denied to user '%.*s'@'%.*s' for sensitive rule '%.*s'

• OceanBase error code: 11098

• Cause: The user does not have permission to execute the sensitive rule command '%.*s'. This usually occurs when a DML statement (such as INSERT, UPDATE, or REPLACE) accesses columns protected by sensitive rules.

• Solution: Check user permissions. Use the GRANT PLAINACCESS ON SENSITIVE RULE '%.*s' TO '%.*s'@'%.*s' command to grant the user appropriate plain-text access permissions.

ERROR 11099 (HY000): Invalid sensitive rule name '%.*s'

• OceanBase error code: 11099

• Cause: Invalid sensitive rule name.

• Solution: Check whether the specified sensitive rule name is correct and enter the correct sensitive rule name.

ERROR 11100 (HY000): kerberos execution error

• OceanBase error code: 11100

• Cause: Kerberos execution error, which may be caused by incorrect configuration or invalid key files.

• Solution: Check the Kerberos configuration file (such as krb5.conf) and key file paths, and make sure the permissions and content are correct.

ERROR 11101 (HY000): HMS execution error

• OceanBase error code: 11101

• Cause: HMS execution error, which may be caused by service unavailability or incorrect configuration.

• Solution: Verify the HMS service status, check whether connection parameters (such as address and port) are correct, and check HMS logs to troubleshoot the specific issue.

ERROR 11102 (HY000): HMS host: '%.*s' is invalid

• OceanBase error code: 11102

• Cause: The HMS host is invalid. The host address format may be invalid or cannot be resolved.

• Solution: Check the HMS IP address format and make sure the configuration is correct.

ERROR 11103 (HY000): HMS port: '%.*s' is invalid

• OceanBase error code: 11103

• Cause: The HMS port is invalid.

• Solution: Make sure the port number conforms to the specification and check whether firewall rules allow access to this port.

ERROR 11104 (HY000): HMS table location: '%.*s' is invalid

• OceanBase error code: 11104

• Cause: The HMS table storage path is invalid.

• Solution: Verify that the table path exists and make sure OceanBase Database has read/write permissions.

ERROR 11105 (HY000): HMS service: '%.*s' is invalid

• OceanBase error code: 11105

• Cause: The HMS service is invalid.

• Solution: Check whether the HMS service name matches the actual deployment and make sure the service has started properly.

ERROR 11106 (HY000): HMS service FQDN: '%.*s' is invalid

• OceanBase error code: 11106

• Cause: The HMS service FQDN format is incorrect or cannot be resolved.

• Solution: Verify the FQDN format and make sure DNS resolution works properly.

ERROR 11107 (HY000): HMS transport: '%.*s' is invalid

• OceanBase error code: 11107

• Cause: The HMS transport is invalid.

• Solution: Make sure the transport protocol is compatible with the HMS service.

ERROR 11108 (HY000): HMS metastore: '%.*s' is invalid

• OceanBase error code: 11108

• Cause: Invalid HMS metastore.

• Solution: Check the connection parameters of the HMS metadata database.

ERROR 11109 (HY000): HMS partition error

• OceanBase error code: 11109

• Cause: HMS partition operation failed, which may be caused by partition field type mismatch or data conflicts.

• Solution: Check the partition field definition and data content to make sure they comply with HMS metadata specifications.

ERROR 11110 (HY000): HMS database: '%.*s' not found

• OceanBase error code: 11110

• Cause: The requested HMS database does not exist.

• Solution: Make sure the database name is spelled correctly, or contact the administrator to create the target database.

ERROR 11111 (HY000): HMS table: '%.*s' not found

• OceanBase error code: 11111

• Cause: The requested HMS table does not exist.

• Solution: Check the table name spelling and database context, and make sure the table has been created correctly.

ERROR 11112 (HY000): This ai model endpoint '%.*s' not found in the tenant

• OceanBase error code: 11112

• Cause: The AI model endpoint name entered by the user does not exist.

• Solution: Query the DBA_OB_AI_MODEL_ENDPOINTS view to check whether a corresponding endpoint record exists. If not, use DBMS_AI_SERVICE.CREATE_AI_MODEL_ENDPOINT to create the corresponding endpoint record.

ERROR 11113 (HY000): This ai model endpoint '%.*s' is already exists

• OceanBase error code: 11113

• Cause: The AI model endpoint name entered by the user already exists.

• Solution: Use a different AI model endpoint name to create it.

ERROR 11114 (HY000): The param '%.*s' is empty or null

• OceanBase error code: 11114

• Cause: The parameter of the DBMS_AI_SERVICE subprogram specified by the user cannot be empty or NULL.

• Solution: Check whether the parameter of the DBMS_AI_SERVICE subprogram specified by the user is empty or NULL. Refer to the parameter descriptions in DBMS_AI_SERVICE subprogram overview.

ERROR 11115 (HY000): The param '%.*s' is invalid

• OceanBase error code: 11115

• Cause: The parameter name of the DBMS_AI_SERVICE subprogram specified by the user does not meet the requirements.

• Solution: Use a valid parameter name. Refer to the parameter descriptions in DBMS_AI_SERVICE subprogram overview.

ERROR 11116 (HY000): The value of param '%.*s' is invalid

• OceanBase error code: 11116

• Cause: The parameter value of the DBMS_AI_SERVICE subprogram specified by the user does not meet the requirements.

• Solution: Use a valid parameter value. Refer to the parameter descriptions in DBMS_AI_SERVICE subprogram overview.

ERROR 11117 (HY000): This type of param '%.*s' is invalid, should be %.*s

• OceanBase error code: 11117

• Cause: The parameter type of the DBMS_AI_SERVICE subprogram specified by the user does not meet the requirements.

• Solution: Use a valid parameter type. Refer to the parameter descriptions in DBMS_AI_SERVICE subprogram overview.

ERROR 11118 (HY000): This ai model '%.*s' not found in the tenant

• OceanBase error code: 11118

• Cause: The AI model specified by the user does not exist.

• Solution: Query the DBA_OB_AI_MODELS view to check whether a corresponding model record exists. If not, use DBMS_AI_SERVICE.CREATE_AI_MODEL to create the corresponding model record.

ERROR 11119 (HY000): This ai model '%.*s' is already exists

• OceanBase error code: 11119

• Cause: The AI model specified by the user already exists.

• Solution: Use a different AI model name to create it.

ERROR 11120 (HY000): Got error during COMMIT: %s

• OceanBase error code: 11120

• Compatible MySQL error code: 1180

• Cause: An error occurred during the commit phase of the transaction.

• Solution: The key to resolving this issue is to identify the root cause through detailed logs. After obtaining the specific error information, we recommend that you seek official technical support for the most accurate solution.

ERROR 11121 (HY000): Table snapshot '%.*s' does not exist

• OceanBase error code: 11121

• Cause: The table snapshot does not exist.

• Solution: Verify whether the snapshot exists. If it does not exist, recreate the required snapshot.

ERROR 11122 (HY000): Bad http request: %s

• OceanBase error code: 11122

• Cause: HTTP request error.

• Solution: Check whether the HTTP request parameters are correct.

ERROR 11123 (HY000): Unauthorized http request: %s

• OceanBase error code: 11123

• Cause: HTTP request authorization denied.

• Solution: Check whether the HTTP request authentication information is set correctly.

ERROR 11124 (HY000): Http request not found: %s

• OceanBase error code: 11124

• Cause: HTTP request not found.

• Solution: Check whether the requested resource exists.

ERROR 11125 (HY000): Http server error: %s

• OceanBase error code: 11125

• Cause: HTTP server error.

• Solution: Check the status of the HTTP service being accessed.

ERROR 11126 (HY000): unit '%.*s' not recognized

• OceanBase error code: 11126

• Cause: When calling a date truncation function (such as DATE_TRUNC or DATETRUNC), the time unit parameter passed in is not recognized.

• Solution: Check the first parameter of the date truncation function in your SQL statement and make sure it is spelled correctly and is a valid time unit keyword supported by OceanBase Database.

ERROR 11127 (HY000): Privilege not allowed for sensitive rules

• OceanBase error code: 11127

• Cause: An operation related to sensitive data rules was performed, but the permissions held are insufficient for this operation.

• Solution: Confirm the permissions required for the operation and grant the corresponding permissions.