OBE-20000 to OBE-29999

OBE-20000: operator binding does not exist

• OceanBase error code: 7299

• SQLSTATE: 42000

• Cause: The specified operator binding was not found when attempting to execute the operation.

• Solution: Verify that the operator or function name used is correct and free from spelling errors.

OBE-20000: application error from remote", "%.*s

• Error code in OceanBase Database: 9767

• SQLSTATE: HY000

• Cause: A remote application error occurred.

• Solution: Check the error reported by the remote database through the database link.

OBE-20000: '%.*s' invalid partition name

• OceanBase error code: 11002

• SQLSTATE: HY000

• Cause: The partition name '%.*s' is invalid.

• Solution: Check whether the partition name '%.*s' is correct and complies with the partition naming rules. Ensure that a valid partition name is used for the operation.

OBE-20000: The stored procedure 'raise_application_error' was called which causes this error to be generated", "ORA%06ld: %.*s

• OceanBase error code: 20000

• SQLSTATE: HY000

• Cause: The RAISE_APPLICATION_ERROR procedure was called, which generated this error.

• Solution: Fix the issue described in the error message, or contact the application administrator or DBA for more information.

OBE-21000: error number argument to raise_application_error of stringstring is out of range

• OceanBase error code: 21000

• SQLSTATE: HY000

• Error cause: The error number parameter for RAISE_APPLICATION_ERROR is out of range.

OBE-21560: argument %.*s is null, invalid, or out of range

• OceanBase error code: 5934

• SQLSTATE: HY000

• Error cause: The passed parameter value is NULL, invalid, or out of range. For example, the value of the position or size parameter for LOB / FILE exceeds the range from 1 to (4 GB - 1), or a file is opened in an invalid open mode.

• Solution: Check and correct the program to ensure that no NULL, invalid, or out-of-range parameter values are passed.

OBE-22003: value is out of range

• OceanBase error code: 4157

• SQLSTATE: 22003

• Error cause: An unexpected communication error occurred while executing the specified TCP/IP function func. The TCP/IP function return code is rc, and the function func parameter is parm.

• Solution: Contact technical support for assistance.

OBE-22160: element at index [%ld] does not exist

• Error code in OceanBase Database: 9801

• SQLSTATE: HY000

• Cause: An attempt was made to access an index position in a collection (such as an array or nested table) that does not exist.

• Solution: Ensure that the index used to access the collection is valid.

OBE-22369: invalid parameter encountered in method %s

• OceanBase error code: 5955

• SQLSTATE: HY000

• Error cause: An invalid parameter is being passed to SYS. This includes: SYS. any type, SYS. any data, or SYS. any dataset.

• Solution: Check the passed parameters and ensure they are allowed.

OBE-22370: incorrect usage of method %s

• OceanBase error code: 5956

• SQLSTATE: HY000

• Cause: SYS. any type, SYS. any data, or SYS. any dataset is used incorrectly.

• Solution: Use it correctly.

OBE-22625: OCIAnyData is not well-formed

• OceanBase error code: 5965

• SQLSTATE: HY000

• Cause: OCIAnyData is used without initializing the construction.

• Solution: Before adding attributes, initialize the handle using OCIAnyDataBeginConstruct. Complete the construction using OCIAnyDataEndConstruct. Alternatively, use OCIAny-DataConvert for construction. Ensure it is properly constructed before accessing its attributes.

OBE-22626: Type Mismatch while constructing or accessing OCIAnyData

• OceanBase error code: 5957

• SQLSTATE: HY000

• Cause: The provided type does not match the type of AnyData. If attempting segmented construction or access, the provided type does not match the type of the current attribute.

• Solution: Ensure the provided type matches the type of the object to be constructed or accessed.

OBE-22627: tc [%s] must be that of object/varray/nested table

• OceanBase error code: 5966

• SQLSTATE: HY000

• Cause: The type code is not a type code for an object, varray, or nested table.

• Solution: Ensure the type code is OCI_TYPECODE_OBJECT, OCI_TYPECODE_VARRAY, or OCI_TYPECODE_TABLE.

OBE-22806: not an object or REF

• OceanBase error code: 5477
• SQLSTATE: 42000
• Cause: The value is not an object or REF.
• Solution: Retry the operation with an object or REF.

OBE-22816: unsupported feature with RETURNING clause

• OceanBase error code: 9573

• SQLSTATE: HY000

• Error cause: The RETURNING clause is not supported for object-type columns, including LONG columns, remote tables, INSERT statements with subqueries, and INSTEAD OF triggers.

• Solution: Use a separate statement to retrieve the value.

OBE-22858: invalid alteration of datatype

• OceanBase error code: 7414
• SQLSTATE: 42000
• Error cause: When you try to change the data type, the data type cannot be changed, or the new data type is invalid.
• Solution:
  1. Check the data type: Verify whether the data type can be changed and that the new data type is valid.
  2. Check the data size: Check the size of the data to be changed and ensure the new data type can accommodate all the data.

OBE-22859: invalid modification of columns

• OceanBase error code: 7415
• SQLSTATE: 42000
• Error cause: You attempted to modify a column or table structure that is not allowed.
• Solution:
  1. Check the table structure: You can check the structure of the table to be modified to ensure it allows the modification.
  2. Check the column attributes: You can check the attributes of the column to be modified to ensure they allow the modification.

OBE-22859: Expected XML tag , got no content

• OceanBase error code: 7416
• SQLSTATE: 42000
• Error cause: The XML data is missing tag content.
• Solution:
  1. Check the XML data: You can check whether the XML data is correct to ensure all tags have content.
  2. Check the XML format: You can check whether the XML format is correct to ensure all tags are correctly nested and closed.

OBE-22866: cannot replace a type with table dependents

• OceanBase error code: 11006

• SQLSTATE: HY000

• Error cause: A type with table dependencies cannot be replaced.

• Solution: Drop all tables that depend on the current type, then retry the operation.

OBE-22901: cannot compare VARRAY or LOB attributes of an object type

• OceanBase error code: 7432

• SQLSTATE: 42000

• Cause: Attempts to compare the VARRAY or LOB attributes of an object type without a MAP or ORDER method.

• Solution: Define a MAP or ORDER method for the object type.

OBE-22902: CURSOR expression not allowed

• OceanBase error code: 9766

• SQLSTATE: HY000

• Cause: The output parameter is not a bound variable.

• Solution: Check how the output parameter is used to ensure it is a bound variable.

OBE-22903: MULTISET expression not allowed

• OceanBase error code: 9716
• SQLSTATE: HY000
• Cause: Using a MULTISET expression is not allowed.

OBE-22907: invalid CAST to a type that is not a nested table or VARRAY

• OceanBase error code: 9717
• SQLSTATE: HY000
• Cause: An invalid CAST to a type that is not a nested table or VARRAY.

OBE-22922: LOB value does not exist

• OceanBase error code: 7419
• SQLSTATE: HY000
• Cause: The LOB value does not exist when you try to access it.
• Solution: Check whether the table or index where the LOB value is located exists or has been deleted, and determine whether the table or index can be restored.

OBE-22928: invalid privilege on directories

• OceanBase error code: 5374

• SQLSTATE: HY000

• Error cause: Attempted to grant or revoke privileges on a directory, but the privilege is invalid for the directory.

• Solution: You can only grant or revoke the CREATE, DELETE, READ, WRITE, and EXECUTE privileges on directories. Do not grant or revoke other privileges.

OBE-22950: cannot ORDER objects without MAP or ORDER method

• OceanBase error code: 7412
• SQLSTATE: 42000
• Error cause: The object does not have a defined MAP or ORDER method when comparing objects.
• Solution:
  1. Define a MAP or ORDER method: You can define a MAP or ORDER method in the object definition for use during sorting. The MAP method maps an object to a scalar value, and the ORDER method compares the sizes of two objects.
  2. Modify the sort method: If you cannot define a MAP or ORDER method, consider modifying the sort method to use another sorting approach, such as sorting by another column.

OBE-22990: LOB locators cannot span transactions

• OceanBase error code: 9715

• SQLSTATE: HY000

• Error cause: LOB handles do not support write operations across transactions.

• Solution: Reassign the LOB handle before performing the write operation.

OBE-22998: CLOB or NCLOB in multibyte character set not supported

• OceanBase error code: 22998

• SQLSTATE: HY000

• Error cause: A CLOB or NCLOB variable from a fixed-width or variable-width multibyte character set is passed to an SQL character function that does not support multibyte LOB data.

• Solution: Use DBMS_LOB functions, such as DBMS_LOB.INSTR() and DBMS_LOBSUBSTR(), or use PLSQL DBMS_LOB.READ/WRITE to access LOB data.

OBE-23413: table %s.%s does not have a materialized view log

• OceanBase error code: 9755

• SQLSTATE: HY000

• Error cause: Fast refresh cannot be performed because the primary table does not contain a materialized view log.

• Solution: Please create the corresponding materialized view log.

OBE-23420: the parameter %s must evaluate to a time in the future

• OceanBase error code: 9764

• SQLSTATE: HY000

• Cause: The calculation result of the "interval" parameter is a time earlier than CURRENT_DATE.

• Solution: Select an expression whose calculation result is later than CURRENT_DATE.

OBE-23481: unexpected name string '%.*s'

• OceanBase error code: 5932

• SQLSTATE: HY000

• Cause: An invalid name character.

OBE-23538: cannot explicitly refresh a NEVER REFRESH materialized view (%s)

• OceanBase error code: 9761

• SQLSTATE: HY000

• Error cause: Attempt to explicitly refresh a NEVER REFRESH MV.

• Solution: Do not perform this refresh operation or remove the MV from the list.

OBE-24230: input to DBMS_DDL.WRAP is not a legal PL/SQL unit

• Error code in OceanBase Database: 9807

• SQLSTATE: HY000

• Cause: When using the DBMS_DDL.WRAP stored procedure, the input text is not a valid PL/SQL unit.

• Solution: Check whether the syntax is missing semicolons or contains incomplete statements.

OBE-24234: unable to get source of string \'%.*s\'.\'%.*s\', insufficient privileges or does not exist

• OceanBase error code: 5962

• SQLSTATE: HY000

• Error cause: The specified PL/SQL object in the DBMS_PREPROCESSOR subprogram does not exist, or you do not have the required privileges to view its source code.

• Solution: Ensure the specified object exists and that you have the necessary privileges to view its source.

OBE-24235: bad value for object type: %.*s

• OceanBase error code: 5961

• SQLSTATE: HY000

• Error cause: The specified object type is inappropriate.

• Solution: Ensure the specified object type is one of the following: package, package body, procedure, function, trigger, type, or type body.

OBE-24236: source text is empty

• OceanBase error code: 5960

• SQLSTATE: HY000

• Cause: The input source text provided to the DBMS_PREPROCESSOR subprogram is empty.

• Solution: Pass a non-empty input source text as the argument.

OBE-24247: network access denied by access control list (ACL)

• OceanBase error codes: 9818, 9791

• SQLSTATE: HY000

• Cause: The current database user is not authorized to access external services over the network.

• Solution: Configure an ACL for the database user performing the network operation, explicitly granting it the permission to access specific external network resources.

OBE-24249: Authentication scheme '%.*s' not supported

• Error code in OceanBase Database: 9797

• SQLSTATE: HY000

• Cause: The authentication scheme is not supported.

• Solution: Verify the authentication schemes supported by the server.

OBE-24250: No supported authentication scheme found

• Error code in OceanBase Database: 9798

• SQLSTATE: HY000

• Cause: No supported authentication scheme was found.

• Solution: Check the OceanBase client environment configuration. If the problem occurs in a specific scenario such as SMTP, ensure that the authentication method requested by the client matches the methods available on the server side.

OBE-24323: value not allowed

• OceanBase error code: 7297

• SQLSTATE: HY000

• Cause: A null or invalid value was passed to a parameter.

• Solution: Verify that all required parameters are passed with valid values.

OBE-24334: no descriptor for this position

• OceanBase error code: 5973

• SQLSTATE: HY000

• Cause: The application obtained a descriptor for an invalid position from the handle.

• Solution: Check the position number.

OBE-24381: error(s) in array DML

• OceanBase error code: 5883

• SQLSTATE: HY000

• Cause: One or more rows in the DML statement failed.

• Solution: Refer to the error stack in the error handle.

OBE-24761: transaction rolled back

• OceanBase error code: 6002

• SQLSTATE: 40000

• Cause: The transaction was rolled back.

OBE-24761: transaction rolled back: transaction context does not exist

• OceanBase error code: 6213

• SQLSTATE: 40000

• Cause: The transaction was rolled back because the transaction context does not exist.

OBE-24761: transaction rolled back: transaction is killed

• OceanBase error code: 6211

• SQLSTATE: 25000

• Cause: The transaction is rolled back because it has been terminated.

OBE-24761: transaction rolled back: partition is frozen

• OceanBase error code: 6214

• SQLSTATE: 25000

• Error cause: The transaction is rolled back because the partition is frozen.

OBE-24761: transaction rolled back: Transaction exiting

• OceanBase error code: 6223

• SQLSTATE: 25000

• Error cause: The transaction is rolled back because the transaction already exists.

OBE-24761: transaction rolled back: transaction needs rollback

• OceanBase error code: 6224

• SQLSTATE: 25000

• Error cause: The transaction is rolled back because it needs to be rolled back.

OBE-24761: transaction rolled back: transaction idle timeout

• OceanBase error code: 6278

• SQLSTATE: 25000

• Error cause: The transaction is rolled back because it has timed out.

OBE-24761: transaction rolled back: transaction context count reach limit

• OceanBase error code: 6234

• SQLSTATE: 25000

• Error cause: The transaction is rolled back because the number of transaction contexts reaches the limit.

OBE-25002: cannot create INSTEAD OF triggers on tables

• OceanBase error code: 9572

• SQLSTATE: HY000

• Error cause: You cannot create INSTEAD OF triggers on tables.

• Solution: Create an INSTEAD OF trigger on the view, or create a DML trigger on the table.

OBE-25004: WHEN clause is not allowed in INSTEAD OF triggers

• OceanBase error code: 9571

• SQLSTATE: HY000

• Error cause: Specifying a WHEN clause in an INSTEAD OF trigger.

• Solution: Remove the WHEN clause when creating the INSTEAD OF trigger.

OBE-25005: cannot CREATE INSTEAD OF trigger on a read-only view

• OceanBase error code: 9663

• SQLSTATE: HY000

• Error cause: Cannot create INSTEAD OF triggers on read-only views.

• Solution: Create the INSTEAD OF trigger on a non-read-only view.

OBE-25009: Nested tableclause allowed only for INSTEAD OF triggers

• OceanBase error code: 9569

• SQLSTATE: HY000

• Error cause: The nested table clause is only allowed in INSTEAD OF triggers.

• Solution: Use nested table columns in a view to define a nested table trigger.

OBE-25020: renaming system triggers is not allowed

• Error code in OceanBase Database: 9803

• SQLSTATE: HY000

• Cause: Renaming system triggers is not allowed.

• Solution: Stop the attempt to rename system triggers immediately.

OBE-25021: cannot reference a trigger defined on another table

• OceanBase error code: 9705

• SQLSTATE: HY000

• Error cause: The trigger referenced in the FOLLOWS clause is defined on another table.

• Solution: Create the referenced trigger on the same table.

OBE-25022: cannot reference a trigger of a different type

• OceanBase error code: 9706

• SQLSTATE: HY000

• Error cause: The triggers referenced in the FOLLOWS or PRECEDES clause are of different types or are not composite triggers.

• Solution: Create the referenced triggers as triggers of the same type or combined triggers.

OBE-25023: Cyclic trigger dependency is not allowed

• OceanBase error code: 9707

• SQLSTATE: HY000

• Error cause: A cyclic trigger dependency has been formed.

• Solution: Do not create triggers that can form a cyclic dependency.

OBE-25025: cannot specify PRECEDES clause

• OceanBase error code: 9708

• SQLSTATE: HY000

• Cause: The PRECEDES clause was specified when creating a regular trigger.

• Solution: Do not create a regular trigger with the PRECEDES clause.

OBE-25128: No insert/update/delete on table with constraint disabled and validated

• OceanBase error code: 5795

• SQLSTATE: HY000

• Cause: An attempt was made to perform an INSERT, UPDATE, or DELETE operation on a table with the DISABLE VALIDATE constraint enabled.

• Solution: Change the state of the constraint.

OBE-25129: cannot modify constraint (%.*s) - no such constraint

• OceanBase error code: 5800

• SQLSTATE: HY000

• Cause: The specified constraint does not exist for this table.

OBE-25137: Data value %s out of range in '%s'

• OceanBase error code: 4157

• SQLSTATE: 22003

• Cause: The value of the operand after conversion is greater than the size of the conversion target.

• Solution: Increase the size of the conversion target.

OBE-25154: Column part of using clause can not have qualifier

• OceanBase error code: 5619

• SQLSTATE: HY000

• Cause: Columns used to name a join (NATURAL join or a join using the USING clause) cannot have explicit qualifiers.

• Solution: Remove the qualifier.

OBE-25156: old style outer join (+) cannot be used with ANSI joins

• OceanBase error code: 5625

• SQLSTATE: HY000

• Cause: When a query block uses ANSI-style joins, the old notation for specifying an outer join (+) cannot be used.

• Solution: Use the ANSI-style syntax to specify outer joins.

OBE-25405: Transaction state unknown

• OceanBase error code: 6222

• SQLSTATE: HY000

• Cause: A failure occurred when the transaction attempted to commit. The failover may not automatically determine the transaction status.

• Solution: You must manually determine the transaction status.

OBE-28001: the password has expired

• OceanBase error code: 4366

• SQLSTATE: HY000

• Cause: The user's account has expired and the password needs to be changed.

• Solution: Change the password or contact the database administrator.

OBE-28101: policy already exists

• OceanBase error code: 9718
• SQLSTATE: HY000
• Cause: The policy already exists.
• Solution: Check whether the policy has been added or use a different policy name.

OBE-28102: policy does not exist

• OceanBase error code: 9719
• SQLSTATE: HY000
• Cause: The policy does not exist.

OBE-28103: adding a policy to an object owned by SYS is not allowed

• OceanBase error code: 9720
• SQLSTATE: HY000
• Error cause: Adding a policy to an object owned by SYS is not allowed.
• Solution: You cannot perform this operation.

OBE-28104: input value for %s is not valid

• OceanBase error code: 9721
• SQLSTATE: HY000
• Error cause: The input value of the parameter is invalid.
• Solution: Specify a valid parameter value.

OBE-28105: cannot create security relevant column policy in an object view

• OceanBase error code: 9722
• SQLSTATE: HY000
• Error cause: A security-related column policy cannot be created in an object view.

OBE-28106: input value for argument %s is not valid

• OceanBase error code: 9723
• SQLSTATE: HY000
• Error cause: The input value for the parameter is invalid or missing.

OBE-28107: policy was disabled

• OceanBase error code: 9724
• SQLSTATE: HY000
• Error cause: The policy has been disabled.
• Solution: To enforce this policy, you must enable it.

OBE-28108: circular security policies detected

• OceanBase error code: 9725
• SQLSTATE: HY000
• Error cause: Policies refer to each other for the same object.

OBE-28109: the number of related policies has exceeded the limit of 16

• OceanBase error code: 9726
• SQLSTATE: HY000
• Error cause: Too many policies are involved for the same object.
• Solution: Abandon one or more policies.

OBE-28110: policy function or package %.*s.%.*s has error

• OceanBase error code: 9727
• SQLSTATE: HY000
• Error cause: The policy function or package is incorrect, has been deleted, or is invalid.
• Solution: Check the status of the function and correct the issue. Alternatively, recreate a policy with a valid function.

OBE-28111: insufficient privilege to evaluate policy predicate

• OceanBase error code: 9728
• SQLSTATE: HY000
• Error cause: The owner of the policy function does not have permission to access the object.

OBE-28112: failed to execute policy function

• OceanBase error code: 9729
• SQLSTATE: HY000
• Error cause: The policy function cannot be executed. One or more errors occurred during the execution of the policy function.

OBE-28113: policy predicate has error

• OceanBase error code: 9730
• SQLSTATE: HY000
• Error cause: An error exists in the policy predicate.

OBE-28116: insufficient privileges to do direct path access

• OceanBase error code: 9731
• SQLSTATE: HY000
• Error cause: Insufficient privileges to perform direct path access.

OBE-28117: integrity constraint violated * parent record not found

• OceanBase error code: 9732
• SQLSTATE: HY000
• Error cause: An integrity constraint violation occurred and the parent record could not be found.
• Solution: Ensure that the updated foreign key value is also visible in the parent record.

OBE-28118: policy group already exists

• OceanBase error code: 9733
• SQLSTATE: HY000
• Error message: The policy group already exists.

OBE-28119: policy group does not exist

• OceanBase error code: 9734
• SQLSTATE: HY000
• Error message: The policy group does not exist.

OBE-28120: driving context already exists

• OceanBase error code: 9735
• SQLSTATE: HY000
• Error message: The driving context already exists.

OBE-28121: driving context does not exist

• OceanBase error code: 9736
• SQLSTATE: HY000
• Error message: The driving context does not exist.

OBE-28122: can not update SYS_DEFAULT policy group

• OceanBase error code: 9737
• SQLSTATE: HY000
• Error message: The SYS_DEFAULT policy group cannot be updated.
• Solution: Do not attempt to create or delete the SYS_DEFAULT policy group. This operation is not allowed.

OBE-28123: Driving context %.*s,%.*s contains invalid group %.*s

• OceanBase error code: 9738
• SQLSTATE: HY000
• Error cause: The driving context contains an invalid group.
• Solution: Ensure that a valid policy group is passed to DBMS_SESSION.SET_CONTEXT when initializing the policy driving context.

OBE-28124: Column %.*s in sec_relevant_cols cannot be of an object data type

• OceanBase error code: 9739
• SQLSTATE: HY000
• Error cause: A column in sec_relevant_cols cannot be of an object data type.
• Solution: Ensure that none of the columns specified in sec_relevant_cols are of an object data type or XMLType.

OBE-28125: A protected base column was referenced in an unprotected virtual column expression

• OceanBase error code: 9740
• SQLSTATE: HY000
• Error cause: A protected base column was referenced in an unprotected virtual column expression.
• Solution: Check the policy definition and ensure that the virtual column is also protected.

OBE-28126: Attribute association failed for policy %.*s

• OceanBase error code: 9741
• SQLSTATE: HY000
• Error cause: Attribute association for the policy failed.
• Solution: Specify a local application context attribute.

OBE-28132: The MERGE INTO syntax does not support the security policy

• OceanBase error code: 9742
• SQLSTATE: HY000
• Error cause: The MERGE INTO syntax does not support the security policy.
• Solution:
  • If you do not have the permission to modify the security policy, use INSERT, UPDATE, and DELETE DML statements on the table with the defined security policy instead of MERGE INTO.
  • If you have the permission to modify the security policy, redefine it so that the statement_types clause includes all DML statement types (INSERT, UPDATE, and DELETE), or ensure that the policy does not contain security-related columns.

OBE-28115: policy with check option violation

• OceanBase error code: 5789

• SQLSTATE: HY000

• Error cause: An incorrect security marker was written for the data.

OBE-28106: input value for argument #%d is not valid

• OceanBase error code: 9687

• SQLSTATE: HY000

• Error cause: The input parameter is invalid.

OBE-28264: Client identifier is too long

• OceanBase error code: 9688

• SQLSTATE: HY000

• Error cause: Exceeds the Client ID upper limit of 64 bytes.

OBE-28265: Namespace beginning with 'SYS_' is not allowed

• OceanBase error code: 9690

• SQLSTATE: HY000

• Error cause: The created context namespace cannot have the 'SYS_' prefix.

OBE-28267: The maximum size specified by the _session_context_size parameter was exceeded

• OceanBase error code: 9691

• SQLSTATE: HY000

• Error cause: The number of session based context key-value pairs exceeds the upper limit specified by _session_context_size.

OBE-28268: Invalid NameSpace Value

• OceanBase error code: 9689

• SQLSTATE: HY000

• Error cause: The context namespace name is invalid.

OBE-29253: Invalid count argument passed to procedure dbms_sql.define_array

• OceanBase error code: 9679

• SQLSTATE: HY000

• Error cause: The value of the count parameter specified when defining an array in the dbms_sql package procedure is invalid. Invalid values are negative numbers and null values. The parameter must be a positive integer.

• Solution: Correct the PL/SQL program to pass only valid parameters for defining the array, and then try again.

OBE-29256: Cursor contains both regular and array defines which is illegal

• Error code in OceanBase Database: 9551

• SQLSTATE: HY000

• Cause: Both define_array and define_column are defined on this cursor, which is illegal. A cursor cannot contain both column and array definitions.

• Solution: Modify the PL program to call only one of the two functions.

OBE-29257: host %.*s unknown

• OceanBase error code: 5928

• SQLSTATE: HY000

• Cause: The specified host is unknown.

• Solution: Check the spelling of the hostname or IP address to ensure it is valid.

OBE-29258: buffer too small

• Error code in OceanBase Database: 9785

• SQLSTATE: HY000

• Cause: During TCP network communication, the buffer size is insufficient to hold the amount of data to be read or written.

• Solution: Increase the buffer size.

OBE-29259: end-of-input reached

• Error code in OceanBase Database: 9786

• SQLSTATE: HY000

• Cause: This error may be caused by one or more of the following:

  • Network or server interruption.
  • Incompatible security protocols.
  • Request or data format issues.
  • Database resource or timeout limits.

• Solution:

  • Verify network connectivity and the status of the target service.
  • Check and upgrade security protocol support.
  • Adjust database network configuration and timeouts.

OBE-29260: network error: %.*s

• Error code in OceanBase Database: 9787

• SQLSTATE: HY000

• Cause: A network error occurred.

• Solution: Troubleshoot the network configuration.

OBE-29261: bad argument

• Error code in OceanBase Database: 5951, 5968, 9813, and 9788

• SQLSTATE: HY000

• Cause: An invalid parameter was passed to the PL API.

• Solution: Check the parameters passed to the PL API and try again.

OBE-29262: bad URL

• Error code in OceanBase Database: 9814

• SQLSTATE: HY000

• Cause: The URL format passed to the UTL_HTTP package is incorrect or invalid.

• Solution: Check whether the URL is correct.

OBE-29263: HTTP protocol error

• Error code in OceanBase Database: 9820

• SQLSTATE: HY000

• Cause: An HTTP protocol error occurred.

• Solution: Check the server or network.

OBE-29264: unknown or unsupported URL scheme

• Error code in OceanBase Database: 9824

• SQLSTATE: HY000

• Cause: The UTL_HTTP package cannot recognize or does not support the protocol scheme you specified in the URL.

• Solution: Check and correct your URL string.

OBE-29266: end-of-body reached

• Error code in OceanBase Database: 9815

• SQLSTATE: HY000

• Cause: When using the UTL_HTTP package to read an HTTP response body, the program attempts to continue reading data from the HTTP response stream after reaching the end.

• Solution: In most cases, this is a normal process signal that needs to be caught and handled properly, rather than a fault that requires fixing. You must ensure your code has robust exception handling logic to gracefully end the HTTP request.

OBE-29268: HTTP client error

• Error code in OceanBase Database: 9816

• SQLSTATE: HY000

• Cause: The HTTP client request failed.

• Solution: Check whether the request information sent by the client is correct, and check the network connectivity and server status.

OBE-29269: HTTP server error

• Error code in OceanBase Database: 9817

• SQLSTATE: HY000

• Cause: An HTTP server issue occurred.

• Solution: Check the HTTP server status.

OBE-29270: too many open HTTP requests

• Error code in OceanBase Database: 9822

• SQLSTATE: HY000

• Cause: Too many HTTP requests are open.

• Solution: Adjust the session connection limit and close unnecessary connection requests.

OBE-29273: HTTP request failed

• Error code in OceanBase Database: 9821

• SQLSTATE: HY000

• Cause: The HTTP request failed.

• Solution: Check the server or network connectivity.

OBE-29275: partial multibyte character

• Error code in OceanBase Database: 9819 and 9789

• SQLSTATE: HY000

• Cause: A multibyte character was processed incompletely.

• Solution: Start checking the UTL_HTTP response data processing code to see if there are any operations that calculate lengths or truncate based on bytes.

OBE-29276: transfer timeout

• Error code in OceanBase Database: 9823 and 9790

• SQLSTATE: HY000

• Cause: The transfer timed out.

• Solution: Adjust the network environment, optimize server performance, or increase the client's timeout settings.

OBE-29277: invalid SMTP operation

• Error code in OceanBase Database: 9794

• SQLSTATE: HY000

• Cause: The SMTP operation is invalid.

• Solution: Check the call order of SMTP protocol commands and the compliance of the email data format.

OBE-29278: SMTP transient error: %.*s

• Error code in OceanBase Database: 9795

• SQLSTATE: HY000

• Cause: SMTP communication encountered a transient obstacle.

• Solution: Verify the SMTP server information and check network and environment restrictions.

OBE-29279: SMTP permanent error: %.*s

• Error code in OceanBase Database: 9796

• SQLSTATE: HY000

• Cause: This error indicates that a permanent failure preventing email delivery was encountered when using database mail features (such as the UTL_SMTP package).

• Solution: Determine whether the problem is an address error, authentication failure, server policy rejection, or network connectivity issue based on the error details.

OBE-29280: invalid directory path

• Error code in OceanBase Database: 9554

• SQLSTATE: HY000

• Cause: The directory object does not exist.

• Solution: Correct the directory object parameter or use the CREATE DIRECTORY command to create the directory object.

OBE-29281: invalid mode

• Error code in OceanBase Database: 9555

• SQLSTATE: HY000

• Cause: An invalid value was specified for the file open mode.

• Solution: Change the mode value to one of the following: r, a, or w.

OBE-29282: invalid file ID

• Error code in OceanBase Database: 9556

• SQLSTATE: HY000

• Cause: A file ID handle was specified, but no corresponding file is open.

• Solution: Verify that the file ID handle value is the value returned by a call to UTL_FILE.FOPEN.

OBE-29283: invalid file operationstring

• Error code in OceanBase Database: 9557

• SQLSTATE: HY000

• Cause: An attempt was made to read a file from a nonexistent file or directory, or the operating system denied file or directory access.

• Solution: Verify file and directory access permissions on the file system. If you are reading, verify that the file exists.

OBE-29284: file read error

• Error code in OceanBase Database: 9558

• SQLSTATE: HY000

• Cause: Failed to read the file.

• Solution: Verify that the file exists, is accessible, and is open in read mode.

OBE-29285: file write error

• Error code in OceanBase Database: 9559

• SQLSTATE: HY000

• Cause: Failed to write, flush, or close the file.

• Solution: Verify that the file exists, is accessible, and is open in write or append mode.

OBE-29286: internal error

• Error code in OceanBase Database: 9560

• SQLSTATE: HY000

• Cause: A fatal error occurred while allocating PL session memory.

• Solution: Verify that the PL session is connected and sufficient memory resources are available.

OBE-29287: invalid maximum line size

• Error code in OceanBase Database: 9562

• SQLSTATE: HY000

• Cause: The specified maximum line value is invalid.

• Solution: Correct the maximum line value.

OBE-29288: invalid file name

• Error code in OceanBase Database: 9563

• SQLSTATE: HY000

• Cause: An invalid file name or a file name with an invalid length was specified.

• Solution: Correct the file name.

OBE-29289: directory access denied

• Error code in OceanBase Database: 9564

• SQLSTATE: HY000

• Cause: A directory object was specified, but you do not have permission to access it.

• Solution: Use the command GRANT [privilege] ON DIRECTORY [object] TO [username]; to grant access to the directory object.

OBE-29290: invalid offset specified for seek

• Error code in OceanBase Database: 9565

• SQLSTATE: HY000

• Cause: An attempt was made to seek to a position beyond the end of the file, or both the absolute offset and relative offset are NULL, or the absolute offset is less than zero.

• Solution: If you specify an absolute offset, ensure that it is within the range of [0, total bytes in the file]. If you specify a relative offset, ensure that it is not greater than the current byte position plus the remaining bytes in the file.

OBE-29291: file remove operation failed

• Error code in OceanBase Database: 9566

• SQLSTATE: HY000

• Cause: The operating system denied the file deletion operation.

• Solution: Verify that the file exists and that you have delete permissions for the file and directory.

OBE-29292: file rename operation failed

• Error code in OceanBase Database: 9567

• SQLSTATE: HY000

• Cause: The operating system denied the file rename operation. Possible causes include:

  • The source or destination directory does not exist or is not accessible.

  • The source file is not accessible.

  • The destination file already exists.

• Solution: Verify that the source file, source directory, and destination directory exist and are accessible, and that the destination file does not exist.

OBE-29295: invalid mime header tag

• OceanBase error code: 5970

• SQLSTATE: HY000

• Cause: An error occurred while scanning the string of the mime header tag.

• Solution: Verify whether the source data is a valid mime header string and whether its format is charset/encoding/encoded string.

OBE-29298: Character set mismatch

• Error code in OceanBase Database: 9561

• SQLSTATE: HY000

• Cause: The character set mode of the file does not match the character set of the read or write operation.

• Solution: Use the correct UTL_FILE read/write routines that correspond to the character set mode of the file.

OBE-29357: %s %.*s already exists

• OceanBase error code: 4702

• SQLSTATE: HY000

• Cause: The parameter name has been used for the CREATE_PLAN, CREATE_CDB_PLAN, CREATE_CONSUMER_GROUP programs, or the CREATE_CATEGORY program of the DBMS_RESOURCE_MANAGER package.

• Solution: Specify an unused parameter name.

OBE-29358: resource plan %.*s does not exist

• OceanBase error code: 4703

• SQLSTATE: HY000

• Cause: An invalid plan name was specified as a parameter for the UPDATE_PLAN or UPDATE_CDB_PLAN program of the DBMS_RESOURCE_MANAGER package.

• Solution: Specify an existing plan name.

OBE-29361: value %ld for %s is outside valid range of 0 to 100

• OceanBase error code: 4704

• SQLSTATE: HY000

• Cause: An invalid value was specified for a plan directive parameter.

• Solution: Specify a value between 0 and 100 (inclusive).

OBE-29362: plan directive %.*s, %.*s does not exist

• OceanBase error code: 4705

• SQLSTATE: HY000

• Cause: An invalid plan directive was specified for the UPDATE_PLAN_DIRECTIVE or UPDATE_CDB_PLAN_DIRECTIVE procedure of the DBMS_RESOURCE_MANAGER package.

• Solution: Specify a valid plan directive.

OBE-29364: plan directive %.*s, %.*s already exists

• OceanBase error code: 4706

• SQLSTATE: HY000

• Cause: You attempted to create a plan directive that already exists.

• Solution: Retry the creation operation with a different value.

OBE-29366: plan directive name '%.*s' not supported

• OceanBase error code: 4707

• SQLSTATE: HY000

• Cause: The specified plan directive name is not supported.

OBE-29368: consumer group %.*s does not exist

• OceanBase error code: 4710

• SQLSTATE: HY000

• Cause: A non-existent consumer group was specified.

• Solution: Specify an existing consumer group.

OBE-29471: DBMS_SQL access denied

• OceanBase error code: 5856

• SQLSTATE: HY000

• Cause: Access to DBMS_SQL has been denied for security reasons.

• Solution: Try obtaining more information from the alert logs and trace files.

OBE-29474: DBMS_SQL.OPEN_CURSOR failed. security_level of 0 is not allowed

• OceanBase error code: 9677

• SQLSTATE: HY000

• Error cause: The security level specified for DBMS_SQL.OPEN_CURSOR is 0.

• Solution: Specify a valid security level.

OBE-29879: cannot create multiple domain indexes on a column list using same

• OceanBase error code: 7301

• SQLSTATE: 42000

• Error cause: Attempt to create multiple indexes on a list of columns based on the same domain.

• Solution: Check and remove any unnecessary duplicate index requests.

OBE-29900: operator binding does not exist

• OceanBase error code: 7298

• SQLSTATE: 42000

• Error cause: The specified operator binding could not be found when attempting to execute an operation.

• Solution: Confirm that the name of the operator or function used is correct and free of spelling errors.