10000 ~ 12000

This range contains error codes related to OBProxy, OBSharding, OBKV, and client errors.

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

• OceanBase error code: 10500

• Error: The route for the global index of OBKV is incorrect, and the client router needs to refresh.

• Solution: Verify your client connection and routing information.

ERROR 10501 (HY000) : TTL feature is not enabled

• OceanBase error code: 10501

• Error: The TTL feature is not enabled.

• Solution: Make sure that the TTL feature is enabled.

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

• OceanBase error code: 10502

• Error: The TTL column does not exist.

• Solution: Confirm that 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

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

• Solution: Confirm that 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

• Error: The TTL command is not allowed to be executed because the current TTL status is a specific value.

• Solution: Check the current status to make sure that it meets the expectations and use an appropriate TTL command to switch to the correct status.

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

• OceanBase error code: 10505

• Error: There are no running TTL tasks, and you need to trigger a new TTL task.

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

• OceanBase error code: 10506

• Error: The TTL task cannot be executed during tenant restore.

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

• OceanBase error code: 10507

• Error: The TTL of the HBase table must be greater than 0.

• Solution: Check the KV_ATTRIBUTES property of the current table to make sure that the defined TimeToLive is greater than 0.

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

• OceanBase error code: 10508

• Error: The MaxVersions of the HBase table must be greater than 0.

• Solution: Check the KV_ATTRIBUTES property of the current table to make sure that the defined MaxVersions is greater than 0.

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

• OceanBase error code: 10509

• Error: Access was denied because the credential '%.*s' does not match the '%.*s'.

• Solution: Re-enter the correct credentials, make sure that the username and password are correct, and make sure that you do not make any typing errors.

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

• OceanBase error code: 10510

• Error: During the execution of an operation, the number of rowkey columns in the input does not match the number of rowkey columns in the database table.

• Solution: Make sure that the number of rowkey columns in the input matches the number of rowkey columns in the table during the execution of an operation.

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

• OceanBase error code: 10511

• Error: During the execution of an operation, the input column type does not match the column type in the database table. This may lead to data conversion errors or failure to execute the operation correctly.

• Solution: Make sure that the column type in the input matches the column type in the table during the execution of an operation.

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

• OceanBase error code: 10512

• Error: The collation type does not match.

• Solution: Make sure that the input collation type matches the collation type in the table during the execution of an 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

• Error reason: The number of scan range columns does not match the number of primary key columns during a scan operation.

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

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

• OceanBase error code: 10515

• Error reason: A Redis protocol parsing error occurred.

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

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

• OceanBase error code: 10518

• Error reason: When the rollbackWhenCheckFailed parameter of the checkAndInsert interface in OBKV is set to true, this error code is thrown if the check fails.

• Solution: This error code indicates a failed check. You can choose to ignore it or handle it based on your business requirements.

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

• OceanBase error code: 10519

• Error reason: The current table is not in the disabled (DISABLED) state. Therefore, the enableTable() or deleteTable() interface of HBase Admin cannot be used.

• Solution: Call the disableTable() interface of HBase Admin to set the table to the disabled (DISABLED) state and then retry.

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

• OceanBase error code: 10520

• Error reason: The current table is not in the enabled (ENABLED) state. Therefore, the table cannot be accessed.

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

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

• OceanBase error code: 10521

• Error reason: 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

• Error reason: The specified HBase table already exists.

• Solution: Confirm whether the created table meets the requirements. If not, you can delete the table and recreate the required HBase table.

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

• OceanBase error code: 10523

• Error reason: The specified HBase table does not exist.

• Solution: Create the corresponding HBase table.

ERROR 10650 (HY000) : ODP process timeout

• OceanBase error code: 10650

• Error reason: The ODP process timed out.

• Solution: Check whether the operation contains a long-running task and increase the timeout for the operation.

ERROR 11032 (HY000) : HDFS path message %s

• OceanBase error code: 11032

• Error reason: The HDFS path was not found.

• Solution:

  1. Confirm that the Kerberos authentication keytab and principal are valid and that the corresponding user has access permissions for the HDFS cluster. Then, reconfigure the external table permissions and set up Kerberos authentication.

  2. Confirm that the corresponding HDFS path is correct and exists. Then, re-establish the HDFS path mapping for the external table.

  3. Contact the customer's O&M team to confirm the data block status. You can choose to adjust the bad blocks or replace the environment for further verification.

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

• OceanBase error code: 11056

• Error reason: The JNI Env environment initialization failed.

• Solution:

  1. Manually confirm whether the java home setting exists and check whether the current user has access permissions for the path. It is possible that java home exists, but the OBServer startup user does not have access permissions for the path.

  2. Refer to ob_java_opts to check whether the ob_java_opts parameter is missing any required configurations.

  3. Check whether the _ob_additional_lib_path path exists and whether the OBServer startup user has access permissions for the path.

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

• OceanBase error code: 11058

• Error reason: The valid JAVA_HOME environment variable could not be found or recognized.

• Solution: Ensure that the OceanBase Database process can read the correct and valid JAVA_HOME environment variable when it is running. This typically involves three levels: the operating system user environment, the service startup environment, and the path validity.

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

• OceanBase error code: 11065

• Error reason: The ORC file could not be read.

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

ERROR 11093 (HY000) : OBLogService rpc execute failed

• OceanBase Database error code: 11093

• Error reason: The RPC execution of the log service failed because the target node has insufficient resources or a network failure occurred.

• Solution: First, locate the log of the target node by using trace_id, and then resolve the issue by using resource monitoring and parameter adjustment.

ERROR 11100 (HY000) : kerberos execution error

• OceanBase Database error code: 11100

• Error reason: The Kerberos execution failed. This may be caused by a configuration error or an invalid key file.

• Solution: Check the Kerberos configuration file (such as krb5.conf) and the key file path to ensure that the permissions and content are correct.

ERROR 11101 (HY000) : HMS execution error

• OceanBase Database error code: 11101

• Error reason: The HMS execution failed. This may be caused by an unavailable HMS service or a configuration error.

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

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

• OceanBase Database error code: 11102

• Error reason: The HMS host is invalid. This may be caused by an invalid host address format or an inability to resolve the host.

• Solution: Check the IP address format of HMS to ensure that the configuration is correct.

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

• OceanBase Database error code: 11103

• Error reason: The HMS port is invalid.

• Solution: Confirm that the port number conforms to the specifications and check whether the firewall rules allow access to the port.

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

• OceanBase Database error code: 11104

• Error reason: The HMS table storage path is invalid.

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

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

• OceanBase Database error code: 11105

• Error reason: The HMS service is invalid.

• Solution: Check whether the HMS service name matches the actual deployment and confirm that the service has been started.

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

• OceanBase Database error code: 11106

• Error reason: The HMS service FQDN is invalid or cannot be resolved.

• Solution: Verify the FQDN format and ensure that the DNS resolution is normal.

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

• OceanBase Database error code: 11107

• Error reason: The HMS transport is invalid.

• Solution: Confirm that the transport protocol is compatible with the HMS service.

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

• OceanBase Database error code: 11108

• Error reason: The HMS metastore is invalid.

• Solution: Check the connection parameters of the HMS metastore.

ERROR 11109 (HY000) : HMS partition error

• OceanBase Database error code: 11109

• Error reason: The HMS partition operation failed. This may be caused by a mismatch in the partition field types or data conflicts.

• Solution: Check the partition field definitions and data content to ensure they conform to the HMS metadata specifications.

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

• OceanBase Database error code: 11110

• Error reason: The requested HMS database does not exist.

• Solution: Confirm 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 Database error code: 11111

• Error reason: The requested HMS table does not exist.

• Solution: Check the spelling of the table name and the database context to ensure that the table has been correctly created.

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

• OceanBase Database error code: 11112

• Error reason: The specified AI model endpoint does not exist.

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

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

• OceanBase Database error code: 11113

• Error reason: The specified AI model endpoint already exists.

• Solution: Create an AI model endpoint with a different name.

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

• OceanBase Database error code: 11114

• Error reason: The specified parameter of the DBMS_AI_SERVICE subprogram cannot be empty or NULL.

• Solution: Check whether the specified parameter of the DBMS_AI_SERVICE subprogram is empty or NULL. For more information, see the parameters in DBMS_AI_SERVICE subprograms.

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

• OceanBase Database error code: 11115

• Error reason: The specified parameter of the DBMS_AI_SERVICE subprogram does not meet the requirements.

• Solution: Use a valid parameter. For more information, see the parameters in DBMS_AI_SERVICE subprograms.

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

• OceanBase Database error code: 11116

• Error reason: The specified value of the DBMS_AI_SERVICE subprogram does not meet the requirements.

• Solution: Use a valid value. For more information, see the parameters in DBMS_AI_SERVICE subprograms.

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

• OceanBase Database error code: 11117

• Error reason: The specified type of the DBMS_AI_SERVICE subprogram does not meet the requirements.

• Solution: Use a valid type. For more information, see the parameters in DBMS_AI_SERVICE subprograms.

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

• OceanBase Database error code: 11118

• Error reason: The specified AI model does not exist.

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

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

• OceanBase Database error code: 11119

• Error reason: The specified AI model already exists.

• Solution: Create an AI model with a different name.