OBE-20000 ~ 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 of spelling errors.

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 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 user-defined error code RAISE_APPLICATION_ERROR was called, causing this error.

• Solution: Fix the issue as 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

• 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

• 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 of 1 to (4 GB - 1), or a file is opened in an invalid 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

• Cause: An unexpected communication error occurred while executing the specified TCP/IP function func. The TCP/IP function returns code rc, and the function func has parameter parm.

• Solution: Contact technical support for assistance.

OBE-22288: file or LOB operation string failed

• OceanBase error code: 5954

• SQLSTATE: HY000

• Cause: An operation attempted on a file or LOB failed.

• Solution: Check whether the file or LOB exists and ensure that the necessary permissions are set for the specified operation. If the error persists, contact technical support for assistance.

OBE-22369: invalid parameter encountered in method %s

• OceanBase error code: 5955

• SQLSTATE: HY000

• 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 initialization and construction.

• Solution: Before adding attributes, initialize the handle using OCIAnyDataBeginConstruct. Complete the construction using OCIAnyDataEndConstruct. Alternatively, use OCIAny-DataConvert for construction. Ensure the object 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 being 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 that of 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 a REF.
• Solution: Retry the operation with an object or a REF.

OBE-22816: unsupported feature with RETURNING clause

• OceanBase error code: 9573

• SQLSTATE: HY000

• Cause: The RETURNING clause is not supported for object-type columns, including LONG columns, remote tables, and columns in INSERT or INSTEAD OF triggers that involve subqueries.

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

OBE-22858: invalid alteration of datatype

• OceanBase error code: 7414
• SQLSTATE: 42000
• Cause: 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 ensure the new data type is valid.
  2. Check the data size: Verify that the new data type can accommodate all the data.

OBE-22859: invalid modification of columns

• OceanBase error code: 7415
• SQLSTATE: 42000
• Cause: You attempted to modify a column or table structure that is not allowed.
• Solution:
  1. Check the table structure: Verify that the table structure allows the modification.
  2. Check the column attributes: Verify that the column attributes allow the modification.

OBE-22859: Expected XML tag , got no content

• OceanBase error code: 7416
• SQLSTATE: 42000
• Cause: The XML data is missing tag content.
• Solution:
  1. Check the XML data: Verify that the XML data is correct and all tags have content.
  2. Check the XML format: Ensure the XML format is correct, with all tags properly nested and closed.

OBE-22866: cannot replace a type with table dependents

• OceanBase error code: 11006

• SQLSTATE: HY000

• Cause: A type with table dependencies cannot be replaced.

• Solution: Delete 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: Attempting to compare 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 the usage of the output parameter to ensure it is a bound variable.

OBE-22903: MULTISET expression not allowed

• OceanBase error code: 9716
• SQLSTATE: HY000
• Cause: MULTISET expressions are 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

• Cause: You 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 a directory. Do not grant or revoke other privileges.

OBE-22933: cannot change object with type or table dependents

• OceanBase error code: 9840
• SQLSTATE: HY000
• Cause: You cannot modify an object that has type dependencies or table dependencies.
• Solution: Remove the type dependencies or table dependencies from the object before modifying it.

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

• OceanBase error code: 7412
• SQLSTATE: 42000
• Cause: The object does not have a defined MAP or ORDER method when you try to compare it.
• Solution:
  1. Define a MAP or ORDER method: You can define a MAP or ORDER method in the object's 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 sorting method: If you cannot define a MAP or ORDER method, consider modifying the sorting method to use another approach, such as sorting by another column.

OBE-22990: LOB locators cannot span transactions

• OceanBase error code: 9715

• SQLSTATE: HY000

• 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

• Cause: A fixed-width or variable-width multibyte character set CLOB or NCLOB is passed to an SQL character function, but the function does not support multibyte LOB data.

• Solution: Use DBMS_LOB functions such as DBMS_LOB.INSTR() and DBMS_LOB.SUBSTR(), 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

• Cause: The primary table does not contain a materialized view log, making fast refresh impossible.

• 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 that evaluates to a time 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

• Cause: Attempting to explicitly refresh a NEVER REFRESH MV.

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

OBE-24230: input to DBMS_DDL_WRAP is not a legal PL/SQL unit

• OceanBase error code: 9807

• SQLSTATE: HY000

• Cause: The text entered is not a valid PL/SQL unit when using the DBMS_DDL_WRAP stored procedure.

• Solution: Check if the syntax is missing a semicolon or contains incomplete statements.

OBE-24250: No supported authentication scheme found

• OceanBase error code: 9798

• SQLSTATE: HY000

• Cause: No supported authentication scheme was found.

• Solution: Check the configuration of the OceanBase client environment. If the issue occurs in specific application scenarios such as SMTP, ensure that the authentication method requested by the client matches the available methods advertised by the server.

OBE-24323: value not allowed

• OceanBase error code: 7297

• SQLSTATE: HY000

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

• Solution: Verify that all required parameters have been correctly passed with valid values.

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

• OceanBase error code: 5962

• SQLSTATE: HY000

• Cause: The PL/SQL object specified in the DBMS_PREPROCESSOR subprogram does not exist, or the required privileges to view its source code are lacking.

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

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

• OceanBase error code: 5961

• SQLSTATE: HY000

• 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 input.

OBE-24334: no descriptor for this position

• OceanBase error code: 5973

• SQLSTATE: HY000

• Cause: The application retrieves 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 context does not exist during transaction rollback.

OBE-24761: transaction rolled back: transaction is killed

• OceanBase error code: 6211

• SQLSTATE: 25000

• Cause: The transaction is terminated during rollback.

OBE-24761: transaction rolled back: partition is frozen

• OceanBase error code: 6214

• SQLSTATE: 25000

• Cause: The partition is frozen during rollback.

OBE-24761: transaction rolled back: Transaction exiting

• OceanBase error code: 6223

• SQLSTATE: 25000

• Cause: The transaction already exists during rollback.

OBE-24761: transaction rolled back: transaction needs rollback

• OceanBase error code: 6224

• SQLSTATE: 25000

• Cause: The transaction needs to be rolled back.

OBE-24761: transaction rolled back: transaction idle timeout

• OceanBase error code: 6278

• SQLSTATE: 25000

• Cause: The transaction times out during rollback.

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

• OceanBase error code: 6234

• SQLSTATE: 25000

• 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

• Cause: You cannot create INSTEAD OF triggers on tables.

• Solution: Create INSTEAD OF triggers on views, or create DML triggers on tables.

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

• OceanBase error code: 9571

• SQLSTATE: HY000

• Cause: A WHEN clause is specified 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

• Cause: You 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 view nested-table columns to define nested-table triggers.

OBE-25020: renaming system triggers is not allowed

• OceanBase error code: 9803

• SQLSTATE: HY000

• Error cause: Renaming system triggers is not allowed.

• Solution: Indicates that you are attempting an operation that is not permitted. You should immediately stop the attempt to rename system triggers.

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 trigger referenced in the FOLLOWS or PRECEDES clause is of a different type or is not a composite trigger.

• Solution: Create the referenced trigger as the same type or a composite trigger.

OBE-25023: Cyclic trigger dependency is not allowed

• OceanBase error code: 9707

• SQLSTATE: HY000

• Error cause: A circular dependency on triggers has been formed.

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

OBE-25025: cannot specify PRECEDES clause

• OceanBase error code: 9708

• SQLSTATE: HY000

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

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

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

• OceanBase error code: 5795

• SQLSTATE: HY000

• Error 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 status of the constraint.

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

• OceanBase error code: 5800

• SQLSTATE: HY000

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

• Error 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 value.

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 qualifiers.

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 notation to specify the outer join.

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
• 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
• 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: Unable to create a security-related column policy 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, it must be enabled.

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: The same object involves too many policies.
• Solution: Abandon one or more policies.

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

• OceanBase error code: 9727
• SQLSTATE: HY000
• Error cause: An error occurred in the policy function or package. It has been deleted or is no longer valid.
• Solution: Check the status of the feature and correct the issue. Alternatively, recreate a policy with a valid feature.

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 the privilege 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 occurred 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: Integrity constraint violation. Parent record not found.
• Solution: Ensure the updated foreign key value is also visible at the parent level.

OBE-28118: policy group already exists

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

OBE-28119: policy group does not exist

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

OBE-28120: driving context already exists

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

OBE-28121: driving context does not exist

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

OBE-28122: can not update SYS_DEFAULT policy group

• OceanBase error code: 9737
• SQLSTATE: HY000
• Error cause: 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: The columns in sec_relevant_cols cannot be of object data types.
• Solution: Ensure that none of the columns specified in sec_relevant_cols are of 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 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 permission to modify the security policy, redefine it so that statement_types 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

• Cause: An invalid security marker was written.

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

• OceanBase error code: 9687

• SQLSTATE: HY000

• Cause: The input parameter is invalid.

OBE-28264: Client identifier is too long

• OceanBase error code: 9688

• SQLSTATE: HY000

• Cause: The client ID exceeds the upper limit of 64 bytes.

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

• OceanBase error code: 9690

• SQLSTATE: HY000

• 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

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

OBE-28268: Invalid NameSpace Value

• OceanBase error code: 9689

• SQLSTATE:HY000

• Cause: The name context namespace namespace is invalid.

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

• OceanBase error code: 9679

• SQLSTATE:HY000

• 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

• OceanBase error code: 9551

• SQLSTATE:HY000

• Cause: It is illegal to define both define_array and define_column on this cursor. 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

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

• OceanBase error code: 9785

• SQLSTATE: HY000

• Error cause: During TCP network communication, the buffer size for the operation is insufficient to accommodate the amount of data that needs to be read or written.

• Solution: Increase the buffer size.

OBE-29259: end-of-input reached

• OceanBase error code: 9786

• SQLSTATE: HY000

• Error cause: This error may be caused by one or more of the following situations:

  • Network or server-side interruption.
  • Incompatible security protocol.
  • Request or data format issues.
  • Database-side 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-29261: bad argument

• OceanBase error codes: 5951, 5968

• SQLSTATE: HY000

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

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

OBE-29261: bad argument

• OceanBase error code: 9813

• SQLSTATE: HY000

• Error cause: This error is triggered when the parameters passed in are not valid when using the UTL_HTTP package to call a function or procedure.

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

OBE-29262: bad URL

• OceanBase error code: 9814

• SQLSTATE: HY000

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

• Solution: Check whether the URL is correct.

OBE-29266: end-of-body reached

• OceanBase error code: 9815

• SQLSTATE: HY000

• Error 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 it has reached 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-29280: invalid directory path

• OceanBase error code: 9554

• SQLSTATE: HY000

• Error cause: The directory object does not exist.

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

OBE-29281: invalid mode

• OceanBase error code: 9555

• SQLSTATE: HY000

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

• Solution: Set the mode to one of the following values: r, a, or w.

OBE-29282: invalid file ID

• OceanBase error code: 9556

• SQLSTATE: HY000

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

• Solution: Verify that the value of the file ID handle is the value returned by calling UTL_FILE.FOPEN.

OBE-29283: invalid file operationstring

• OceanBase error code: 9557

• SQLSTATE: HY000

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

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

OBE-29284: file read error

• OceanBase error code: 9558

• SQLSTATE: HY000

• Cause: Failed to read a file.

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

OBE-29285: file write error

• OceanBase error code: 9559

• SQLSTATE: HY000

• Cause: Unable 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

• OceanBase error code: 9560

• SQLSTATE: HY000

• Error cause: A fatal error occurred while allocating memory for the PL session.

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

OBE-29287: invalid maximum line size

• OceanBase error code: 9562

• SQLSTATE: HY000

• Error cause: The specified maximum line value is invalid.

• Solution: Correct the maximum line value.

OBE-29288: invalid file name

• OceanBase error code: 9563

• SQLSTATE: HY000

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

• OceanBase error code: 9564

• SQLSTATE: HY000

• Error cause: A directory object was specified, but permission to access it is lacking.

• 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

• OceanBase error code: 9565

• SQLSTATE: HY000

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

• Solution: If an absolute offset is specified, ensure it is within the range [0, total bytes in the file]. If a relative offset is specified, ensure it does not exceed the current byte position plus the number of remaining bytes in the file.

OBE-29291: file remove operation failed

• OceanBase error code: 9566

• SQLSTATE: HY000

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

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

OBE-29292: file rename operation failed

• OceanBase error code: 9567

• SQLSTATE: HY000

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

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

  • The source file is inaccessible.

  • 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-29268: HTTP client error

• OceanBase error code: 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

• OceanBase error code: 9817

• SQLSTATE: HY000

• Cause: An issue with the HTTP server.

• Solution: Check the status of the HTTP server.

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

• OceanBase error code: 9818

• 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 network operations, explicitly granting it permission to access specific external network resources.

OBE-29275: partial multibyte character

• OceanBase error code: 9819

• SQLSTATE: HY000

• Cause: A multibyte character was processed incompletely.

• Solution: Check starting from the UTL_HTTP response data processing code to see if there are any operations involving byte-length calculations or truncation.

OBE-29263: HTTP protocol error

• OceanBase error code: 9820

• SQLSTATE: HY000

• Cause: An HTTP protocol error occurred.

• Solution: Check the server or network issues.

OBE-29273: HTTP request failed

• OceanBase error code: 9821

• SQLSTATE: HY000

• Cause: The HTTP request failed.

• Solution: Check the server or network connectivity.

OBE-29270: too many open HTTP requests

• OceanBase error code: 9822

• SQLSTATE: HY000

• Cause: Too many HTTP requests are open.

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

OBE-29276: transfer timeout

• OceanBase error code: 9823

• SQLSTATE: HY000

• Cause: The transfer timed out.

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

OBE-29277: invalid SMTP operation

• OceanBase error code: 9794

• SQLSTATE: HY000

• Cause: The SMTP operation is invalid.

• Solution: Check the calling sequence of SMTP protocol commands and the compliance of the email data format.

OBE-29264: unknown or unsupported URL scheme

• OceanBase error code: 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-29357: %s %.*s already exists

• OceanBase error code: 4702

• SQLSTATE: HY000

• Cause: The parameter name is already in use by 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 non-existent plan directive was specified for the UPDATE_PLAN_DIRECTIVE or UPDATE_CDB_PLAN_DIRECTIVE procedure of the DBMS_RESOURCE_MANAGER package.

• Solution: Specify an existing plan directive.

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

• OceanBase error code: 4706

• SQLSTATE: HY000

• Cause: An attempt was made 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 to obtain 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

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

• Solution: Specify a valid security level.

OBE-29549: class %.*s has changed, Java session state cleared

• OceanBase error code: 9839

• SQLSTATE: HY000

• Cause: The Java class currently being used by the session has been redefined or deleted, causing the Java session state to become invalid and the system to automatically clear it.

• Solution: Deploy or reload the relevant Java class.

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

• OceanBase error code: 7301

• SQLSTATE: 42000

• Cause: You are trying to create multiple domain-based indexes on a column list.

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

OBE-29900: operator binding does not exist

• OceanBase error code: 7298

• SQLSTATE: 42000

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

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