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: Please 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 confirm 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: Please confirm 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 TTL task.
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 TTL of the HBase table must be greater than 0.
Solution: Check the
KV_ATTRIBUTESattribute 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 of the HBase table must be greater than 0.
Solution: Check the
KV_ATTRIBUTESattribute of the current table to ensure that the defined MaxVersions is greater than 0.
ERROR 10509 (HY000) : Access denied, credential '%.*s' not match '%.*s'
OceanBase error code: 10509
Cause: Access is denied. The credentials '%.*s' do not match '%.*s'.
Solution: Enter the correct credentials again, ensure the username and password are correct, and make sure no errors were entered.
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: Ensure that the number of columns in the rowkey matches the number of columns in the table during the operation.
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 collation type of the table 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 during the 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 AI 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 interface in OBKV-HBase, the value of a cell to be incremented or decremented must be an 8-byte long type (Java long/int64) in big-endian format (where the high-order byte precedes the low-order byte). If it is not an 8-byte long, the operation will fail. Common reasons include:
- The incremental data written by the client is not an 8-byte long, such as being written as a string, text, int32, etc., without being encoded as a long type.
- The column has previously been written with data other than 8 bytes using Put or Append (such as strings, variable-length binary, etc.), causing the current value type to be non-long.
Solution:
- When writing incremental data, the client must encode it as an 8-byte big-endian long (in Java, use org.apache.hadoop.hbase.util.Bytes.toBytes(long)).
- If a cell already contains data and is not a long, you can first delete or overwrite it with a valid 8-byte long before performing the 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.
ERROR 10519 (HY000) : '%.*s' is not disabled
OceanBase error code: 10519
Cause: The current table status is not DISABLED, so you cannot use the HBase Admin
enableTable()ordeleteTable()interface.Solution: Call the HBase Admin
disableTable()interface to set the table status to DISABLED, then try again.
ERROR 10520 (HY000) : '%.*s' is not enabled
OceanBase error code: 10520
Cause: The current table status is not ENABLED, so you cannot access the table.
Solution: Call the
enableTable()interface of HBase Admin to set the table status to available (ENABLED), and then try again.
ERROR 10521 (HY000) : namespace '%.*s' is not found
OceanBase error code: 10521
Cause: The specified HBase tablespace does not exist.
Solution: Create the corresponding HBase tablespace in the OBKV-HBase database, and then try again.
ERROR 10522 (HY000) : table '%.*s' already exists
OceanBase error code: 10522
Cause: The specified HBase table already exists.
Solution: Check whether the created table meets the requirements. If not, you can delete it and recreate the required HBase table.
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 operations, and increase the operation timeout period.
ERROR 11014 (HY000) : Can't find FULLTEXT index matching the column list
OceanBase error code: 11014
Cause: No full-text index was found that matches the query columns.
Solution: Check whether a full-text index exists on the table and which columns it covers. Then create a full-text index for the missing columns to ensure 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: A table cannot be updated during its creation.
Solution: Wait for the table creation to complete, and then try again.
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 a format error.
ERROR 11020 (HY000) : HDFS: could not open file on hdfs
OceanBase error code: 11020
Cause:
The file may not exist or you do not have permission.
The file opening mode does not match.
Solution:
Verify that the file path is correct and the file actually exists on HDFS.
Check the HDFS file permissions to ensure the current user has read or write permissions.
Verify that the HDFS namenode or datanode service is running normally.
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 node is running normally and the network connection is normal.
Check the HDFS logs (non-HDFS-related logs of OceanBase AI Database) to confirm whether there are any corrupt blocks or unavailable replicas.
ERROR 11032 (HY000) : HDFS path message %s
OceanBase error code: 11032
Cause: The HDFS path message %s error occurs, typically in the following scenarios:
In an HDFS environment with Kerberos authentication enabled, when accessing an external HDFS table, a -11032 error may occur if insufficient permissions prevent access.
If Kerberos authentication is correctly configured but the HDFS: path not found error still appears, it may be because the external table path specified in the external table creation statement is incorrect and points to a non-existent path.
External table access works normally initially, but after executing queries for a while, a 11032 error occurs. This may be because a bad block exists in a file under the corresponding external table path in HDFS. Specifically, the HDFS DataNode reports that this data block is faulty and inaccessible, triggering the error.
Solution:
Confirm that the Kerberos authentication keytab and principal are valid and that the corresponding user has access permissions to the HDFS cluster. Then, reconfigure the external table permissions and set up Kerberos authentication.
Confirm that the corresponding HDFS path is correct and exists. Re-establish the HDFS path mapping for the external table.
Report the issue to the customer's operations team. After confirming the bad block situation, you can choose to adjust the bad blocks or switch environments to continue 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, meaning there is no
/pathafterhdfs://authority.
Solution:
Ensure the URI format is
hdfs://<namenode>:<port>/<path>, which must include the complete scheme, authority, and path parts.Check whether the spelling of the
LOCATIONfield in the external table or backup configuration is correct.
ERROR 11043 (HY000) : HDFS: invalid argument
OceanBase error code: 11043
Cause:
- Incorrect HDFS URI format.
- Incorrect Kerberos authentication configuration.
- HDFS client environment not initialized or invalid.
- Invalid HDFS connection parameters.
- Failed to set HDFS parameters.
Solution:
- Check whether the HDFS URI format is correct and whether HDFS-related configurations are complete.
- Confirm that the files required for Kerberos authentication (keytab, krb5.conf, ticket cache) exist and have correct paths.
- Check the network connectivity of the HDFS cluster to ensure the namenode is accessible.
- Check whether the
key=valueformat of HDFS custom parameters is correct, ensuring no empty keys or values.
ERROR 11044 (HY000) : HDFS: not implementation
OceanBase error code: 11044
Cause: An attempt was made to use a feature that is not yet implemented in HDFS. 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, possibly attempting to open a file that is already open.
Attempting to perform operations such as delete, mkdir, or list before a connection to HDFS is successfully established.
File deletion failed, possibly due to the file not existing or insufficient permissions.
Directory creation failed.
Write failed.
Flush failed.
Solution:
Check the permissions on the HDFS file or directory to confirm whether the current user has read, write, and delete permissions.
Confirm that the target path exists and is correctly formatted.
Ensure proper lifecycle management of HDFS components to avoid duplicate access or operations performed before a connection is successfully established.
Check whether the disk space of the HDFS cluster is sufficient.
ERROR 11046 (HY000) : Invalid path: %.*s
OceanBase error code: 11046
SQLSTATE: HY000
Cause:
The column name or path entered in the DDL statement has a spelling or case inconsistency with the column name in the file (format such as Parquet, ORC, and Arrow are usually case-sensitive).
Incorrect nested structure path input. For example, the intended access path is
addr.city, but it is written asaddr_cityoraddress.cityin the DDL statement.The specified column is missing in some files under the same external table.
Format symbol issues. For example, extra spaces, quotes, or incorrect escape characters before or after the column name.
Solution:
Verify whether the
data_access_pathorEXTERNAL_FILE_COLUMN_PATTERNon external columns in the DDL statement actually exists in the file's schema.When using nested types, use the actual hierarchical path separator of the file for precise matching.
If the schemas of files from different partitions are different, create separate external tables for the columns that are missing, or set a default value for that column to avoid directly using path mapping for missing columns.
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 to identify the mismatched column type, and modify the table definition or the file content accordingly.
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_percentageparameter to confirm if the setting is reasonable.
ERROR 11050 (HY000) : Odps driver throw exception: ExceptionMsg=%s
OceanBase error code: 11050
Cause: An exception occurred in the ODPS driver.
Solution:
Verify that the ODPS connection configuration information is correct.
Check network connectivity to ensure the network connection is normal.
Verify that the ODPS table exists.
Check the ODPS table structure and permissions to confirm whether the current user has the Describe, Select, and project access privileges.
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 defined in the ODPS table and the OceanBase external table do not match.
Solution: Check the actual structure of the ODPS table against the definition of the OceanBase external table, identify the mismatched columns and types, and then modify the definition of the OceanBase external table.
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 limitations in ODPS or OceanBase AI Database.
Solution:
Check network connectivity.
Check the service status of ODPS.
Check the data format in the ODPS table for issues such as data encoding problems, unprocessed special characters, or data corruption.
Check for resource limitations in ODPS or OceanBase AI Database, such as insufficient memory or computational limits exceeded.
ERROR 11053 (HY000) : unexpected error for jni
OceanBase error code: 11053
Cause: A Java error or exception.
Solution: You need to examine the error exception log context to determine the root cause and resolve it.
ERROR 11054 (HY000) : class could not be found during jni operation
OceanBase error code: 11054
Cause: A certain class does not exist or cannot be found.
Solution: Identify which class cannot be found in the current log, download and install the corresponding JAR package to the appropriate path, and restart the OBServer.
ERROR 11055 (HY000) : method could not be found during jni operation
OceanBase error code: 11055
Cause: A method within a certain class does not exist or cannot be found.
Solution: Identify which class's method cannot be found in the current log. This may be due to the corresponding JAR package not existing, or a mismatch in version numbers causing the method to be lost. You need to download the corresponding JAR package, locate it in the proper path, and restart the OBServer.
ERROR 11056 (HY000) : jvm.so not found %s
OceanBase error code: 11056
Cause: An error occurred when creating or accessing an external table such as HDFS or ODPS in OceanBase AI Database, due to failed JVM environment initialization.
Solution: Check whether the JVM runtime environment is correctly configured.
ERROR 11057 (HY000) : JNI env could not delete ref
OceanBase error code: 11057
Cause: The Java environment failed to delete a reference.
Solution: There may be a code logic error. This error does not exist in the current code logic because the corresponding logic has been deleted. Contact technical personnel for assistance in troubleshooting.
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 specified in the
ob_java_optsparameters for Java startup are too small, or the server resources are insufficient.Solution: Check the server resources and memory, the memory size specified for the currently started Java process, and the environment variables set in
ob_java_opts.
ERROR 11060 (HY000) : field could not be found during jni operation
OceanBase error code: 11060
Cause: A certain attribute does not exist in a certain class.
Solution: Update and replace with a compatible JAR package that is expected to contain this attribute.
ERROR 11061 (HY000) : object could not be found during jni operation
OceanBase error code: 11061
Cause: During the operation, an instance of a class object generated by JNI does not exist.
Solution: There is a logic error in the code that causes this problem. Contact technical personnel for assistance in troubleshooting.
ERROR 11063 (HY000) : missing format for external table
OceanBase error code: 11063
Cause: The file format was not specified when creating the external table, or no valid format configuration appeared in the DDL statement.
Solution:
Add a
FORMATclause to theCREATE EXTERNAL TABLEstatement and specify aTYPEthat matches the actual file.Verify that the
TYPEmatches the actual file extension and content. For example, if the directory contains.parquetfiles, usePARQUETinstead ofCSV.If using
CSV, add parameters such as the delimiter and encoding as needed to avoid successful table creation but abnormal query parsing.
ERROR 11064 (HY000) : missing access path for external table
OceanBase error code: 11064
Cause: No data access path was specified when creating the external table. This is usually because the
LOCATIONclause is not configured, is empty, or has not been correctly bound to a Location object.Solution:
Add a
LOCATIONclause to the DDL statement, pointing to the directory or URL where the external data is stored.Ensure the path is accessible to the OceanBase AI Database cluster (network, authentication, mounting, object storage AK/SK, etc., must be configured according to the environment).
If using a Location object, first confirm that the object has been created and the current user has read permissions, then reference it in the external table.
It is recommended to use a protocol prefix agreed upon with relevant personnel for the path (such as
file://,hdfs://, etc., subject to the support of the current version).
ERROR 11065 (HY000) : fail to read orc file, message: %s
OceanBase error code: 11065
Cause: Unable 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 version of the observer at the specific error node, re-upload it, and try installing it again.
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_dirdirectory under the observer execution path of all nodes. Ensure the plugin dynamic library has read and execute permissions, and its dependency 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 during the processing of a plugin-related function.
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 EXISTSkeyword, 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: Recreate a new catalog.
ERROR 11081 (HY000) : skip_header and parse_header cannot be used at the same time
OceanBase error code: 11081
Cause:
PARSE_HEADERandSKIP_HEADERcannot be used simultaneously, as they are mutually exclusive.Solution: Do not use the
PARSE_HEADERandSKIP_HEADERparameters together when specifying properties related to the external file format.
ERROR 11082 (HY000) : DDL operations on the internal catalog are not allowed
OceanBase error code: 11082
Cause: DDL operations are not allowed on the Internal Catalog.
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 the permission to operate on the catalog.
Solution: Check whether the user has the permission to operate on the catalog, and grant the corresponding operation permission to the user.
ERROR 11085 (HY000) : CCL rule '%.*s' already exists
OceanBase error code: 11085
Cause: A CCL rule with the same name already exists when creating a new one.
Solution: Use the
IF NOT EXISTSkeyword, or delete the old rule before creating a new one.
ERROR 11086 (HY000) : CCL rule '%.*s' doesn't exist
OceanBase error code: 11086
Cause: The rule does not exist when modifying or deleting it.
Solution: Use the
IF EXISTSkeyword, or confirm whether the rule name is correct.
ERROR 11087 (HY000) : SQL reach max ccl rule %s, concurrent num %ld
OceanBase error code: 11087
Cause: The number of concurrent SQL statements has reached the upper limit specified by 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 accessed location object is being used by an external table.
Solution: Check all external tables that depend on this location object to confirm if the dependency has 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 this location object. Grant the
READprivilege to the user using the commandGRANT READ ON LOCATION location_name TO user_name WITH GRANT OPTION;.
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 if the specified location object already exists. To replace the existing definition, add the
OR REPLACEkeyword when defining the new location object. Alternatively, 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 already exists, and then specify a valid one.
ERROR 11093 (HY000) : OBLogService rpc execute failed
OceanBase error code: 11093
Cause: The log service RPC execution failed. This may be due to insufficient resources on the target node or a network failure.
Solution: First, locate the target node logs by using the
trace_id. Then, resolve the issue by checking the resource monitoring data and adjusting parameters.
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 new sensitive rule via a DDL statement, and the new rule's name duplicates an existing one.
Solution: Check whether the specified sensitive rule name already exists. If so, specify a unique name for the new rule.
ERROR 11095 (HY000) : Sensitive rule '%.*s' does not exist
OceanBase error code: 11095
Cause: The sensitive rule with the specified name does not exist. This typically occurs when deleting a sensitive rule using a DDL statement, and the specified rule name is invalid.
Solution: Check whether the specified sensitive rule name is correct, and enter the correct name again.
ERROR 11096 (HY000) : Sensitive column %.*s(%.*s) exists
OceanBase error code: 11096
Cause: The specified column is already a sensitive column. This typically occurs when adding or modifying a sensitive rule using a DDL statement, and you try to apply the sensitive rule to a column that is already covered by another sensitive rule.
Solution: Check whether the specified column is a sensitive column, and select an appropriate column to add the sensitive rule.
ERROR 11097 (HY000) : Sensitive column %.*s(%.*s) does not exist
OceanBase error code: 11097
Cause: The sensitive column with the specified name does not exist. This typically occurs when modifying a sensitive rule using a DDL statement, and you try to remove a column that is not a sensitive column.
Solution: Check whether the specified sensitive column exists, and enter the correct name again.
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 happens when a DML statement (for example,INSERT,UPDATE, orREPLACE) accesses a column protected by a sensitive rule.Solution: Check the user's permissions, and grant the appropriate explicit access permission to the user using the
GRANT PLAINACCESS ON SENSITIVE RULE '%.*s' TO '%.*s'@'%.*s'command.
ERROR 11099 (HY000) : Invalid sensitive rule name '%.*s'
OceanBase error code: 11099
Cause: The sensitive rule name is invalid.
Solution: Check whether the specified sensitive rule name is correct, and enter the correct name again.
ERROR 11100 (HY000) : kerberos execution error
OceanBase error code: 11100
Cause: A Kerberos execution error occurred, possibly due to configuration errors or an invalid key file.
Solution: Check the Kerberos configuration file (such as
krb5.conf) and the path of the key file to ensure the permissions and content are correct.
ERROR 11101 (HY000) : HMS execution error
OceanBase error code: 11101
Cause: HMS execution error, possibly caused by service unavailability or configuration errors.
Solution: Verify the HMS service status, check whether the connection parameters (such as address and port) are correct, and view the 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, possibly due to an invalid host address format or inability to resolve it.
Solution: Check the HMS IP address format to ensure correct configuration.
ERROR 11103 (HY000) : HMS port: '%.*s' is invalid
OceanBase error code: 11103
Cause: The HMS port is invalid.
Solution: Confirm that the port number complies with specifications 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 whether the table path exists and ensure OceanBase AI 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 confirm that the service has started normally.
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 ensure normal DNS resolution.
ERROR 11107 (HY000) : HMS transport: '%.*s' is invalid
OceanBase error code: 11107
Cause: HMS transmission is invalid.
Solution: Ensure the transmission 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: The HMS partition operation failed, possibly due to mismatched partition field types or data conflicts.
Solution: Check the partition field definitions and data content to ensure 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: Verify that 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 to ensure 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 confirm if there is a corresponding endpoint record. If not, you need to use 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: Create it using a different AI model endpoint name.
ERROR 11114 (HY000) : The param '%.*s' is empty or null
OceanBase error code: 11114
Cause: The parameter of the
DBMS_AI_SERVICEsubprogram specified by the user cannot be empty or NULL.Solution: Check whether the parameter of the
DBMS_AI_SERVICEsubprogram specified by the user is empty or NULL. For more information, see the parameter description in Overview of DBMS_AI_SERVICE.
ERROR 11115 (HY000) : The param '%.*s' is invalid
OceanBase error code: 11115
Cause: The parameter name of the
DBMS_AI_SERVICEsubprogram specified by the user does not meet the requirements.Solution: Use a valid parameter name. For more information, see the parameter description in Overview of DBMS_AI_SERVICE.
ERROR 11116 (HY000) : The value of param '%.*s' is invalid
OceanBase error code: 11116
Cause: The parameter value of the
DBMS_AI_SERVICEsubprogram specified by the user does not meet the requirements.Solution: Use a valid parameter value. For more information, see the parameter description in Overview of DBMS_AI_SERVICE.
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_SERVICEsubprogram specified by the user does not meet the requirements.Solution: Use a valid parameter type. For more information, see the parameter description in Overview of DBMS_AI_SERVICE.
ERROR 11118 (HY000) : This ai model '%.*s' not found in the tenant
OceanBase error code: 11118
Cause: The specified AI model does not exist.
Solution: Query the DBA_OB_AI_MODELS view to confirm whether there is a corresponding model record. If not, use 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 specified AI model already exists.
Solution: Create it using a different AI model name.
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 a transaction.
Solution: The core of the solution is to locate the root cause through detailed logs. It is recommended to seek official technical support for the most accurate solution after obtaining specific error information.
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, recreate the required snapshot.
ERROR 11122 (HY000) : Bad http request: %s
- OceanBase error code: 11122
- Cause: An HTTP request error occurred.
- Solution: Check whether the parameters of the HTTP request are correct.
ERROR 11123 (HY000) : Unauthorized http request: %s
- OceanBase error code: 11123
- Cause: HTTP request permission is denied.
- Solution: Check whether the authentication information of the HTTP request is correctly set.
ERROR 11124 (HY000) : Http request not found: %s
- OceanBase error code: 11124
- Cause: The HTTP request was not found.
- Solution: Check whether the requested resource exists.
ERROR 11125 (HY000) : Http server error: %s
- OceanBase error code: 11125
- Cause: An HTTP server error occurred.
- Solution: Check the status of the accessed HTTP service.
ERROR 11126 (HY000) : unit '%.*s' not recognized
OceanBase error code: 11126
Cause: The time unit parameter is not recognized when calling a date truncation function, such as DATE_TRUNC or DATETRUNC.
Solution: Check the first parameter of the date truncation function in your SQL statement to ensure that its spelling is correct and it is a valid time unit keyword supported by OceanBase AI 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 privileges possessed are insufficient for this operation.
Solution: Confirm the required operation privileges and grant the corresponding privileges.