OBE-20000 ~ OBE-29999

OBE-20000: operator binding does not exist

• OceanBase Database error code: 7299

• SQLSTATE: 42000

• Cause: The specified operator binding does not exist when the operation is attempted.

• Solution: Confirm that the operator or function name is correct and has no spelling errors.

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

• OceanBase Database error code: 11002

• SQLSTATE: HY000

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

• Solution: Check whether the partition name '%.*s' is correct and conforms to the partition naming rules. Make sure to use a valid partition name.

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

• OceanBase Database error code: 20000

• SQLSTATE: HY000

• Cause: The procedure custom error code RAISE_APPLICATION_ERROR is called, which causes 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 Database error code: 21000

• SQLSTATE: HY000

• Cause: The error number parameter of RAISE_APPLICATION_ERROR is out of range.

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

• OceanBase Database 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 of LOB / FILE is out of the range of 1 to (4 GB-1). Or the 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 Database error code: 4157

• SQLSTATE: 22003

• Cause: An unexpected communication error occurs when the specified TCP/IP function func is executed. The return code of the TCP/IP function is rc, and the parameter of the function func is parm.

• Solution: Contact Technical Support for troubleshooting.

OBE-22369: invalid parameter encountered in method %s

• OceanBase Database error code: 5955

• SQLSTATE: HY000

• Cause: An invalid parameter is passed to SYS. any type, SYS. any data, or SYS. any dataset.

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

OBE-22370: incorrect usage of method %s

• OceanBase Database error code: 5956

• SQLSTATE: HY000

• Cause: SYS. any type, SYS. any data, or SYS. any dataset is used in an incorrect way.

• Solution: Use these parameters correctly.

OBE-22625: OCIAnyData is not well-formed

• OceanBase Database error code: 5965

• SQLSTATE: HY000

• Cause: OCIAnyData is used without initialization.

• Solution: Use OCIAnyDataBeginConstruct to initialize the handle before adding attributes. Use OCIAnyDataEndConstruct to complete the construction. Alternatively, use OCIAnyDataConvert for construction. Make sure the attribute is properly constructed before accessing it.

OBE-22626: Type Mismatch while constructing or accessing OCIAnyData

• OceanBase Database error code: 5957

• SQLSTATE: HY000

• Cause: The provided type does not match the AnyData type. If you are attempting to construct or access segments, the provided type does not match the current attribute's type.

• Solution: Ensure that the provided type matches the type of the object you are constructing or accessing.

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

• OceanBase Database error code: 5966

• SQLSTATE: HY000

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

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

OBE-22806: not an object or REF

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

OBE-22816: unsupported feature with RETURNING clause

• OceanBase Database error code: 9573

• SQLSTATE: HY000

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

• Solution: Use separate statements to retrieve values.

OBE-22858: invalid alteration of datatype

• OceanBase Database error code: 7414
• SQLSTATE: 42000
• Cause: The data type cannot be changed or the changed data type is invalid.
• Solution:
  1. Check the data type: Check whether the data type to be changed is allowed to be changed and ensure that the changed data type is valid.
  2. Check the data size: Check the data size to be changed and ensure that the changed data type can accommodate all the data.

OBE-22859: invalid modification of columns

• OceanBase Database error code: 7415
• SQLSTATE: 42000
• Cause: The column or table structure to be modified cannot be modified.
• Solution:
  1. Check the table structure: Check the table structure to be modified and ensure that the table structure can be modified.
  2. Check the column attributes: Check the column attributes to be modified and ensure that the column attributes can be modified.

OBE-22859: Expected XML tag , got no content

• OceanBase Database error code: 7416
• SQLSTATE: 42000
• Cause: The XML data does not contain tag content.
• Solution:
  1. Check the XML data: Check whether the XML data is correct and ensure that all tags contain content.
  2. Check the XML format: Check whether the XML format is correct and ensure that all tags are properly nested and closed.

OBE-22866: cannot replace a type with table dependents

• OceanBase Database error code: 11006

• SQLSTATE: HY000

• Cause: The type has dependent tables.

• Solution: Delete all tables that depend on the current type and retry the operation.

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

• OceanBase Database error code: 7432

• SQLSTATE: 42000

• Cause: The VARRAY or LOB attribute of an object type is compared without a MAP or ORDER method.

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

OBE-22902: CURSOR expression not allowed

• OceanBase Database error code:

• SQLSTATE: HY000

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

• Solution: Check the usage of the output parameter and ensure that a bind variable is used.

OBE-22903: MULTISET expression not allowed

• OceanBase Database error code: 9716
• SQLSTATE: HY000
• Cause: The MULTISET expression is not allowed.

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

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

OBE-22922: LOB value does not exist

• OceanBase Database error code: 7419
• SQLSTATE: HY000
• Cause: The LOB value does not exist when the value is accessed.
• Solution: Check whether the table or index that contains the LOB value exists or has been deleted, and confirm whether the table or index can be restored.

OBE-22928: invalid privilege on directories

• OceanBase Database error code: 5374

• SQLSTATE: HY000

• Cause: The privilege to be granted or revoked for the directory is invalid.

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

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

• OceanBase Database error code: 7412
• SQLSTATE: 42000
• Cause: The object does not define a MAP or ORDER method when the object is compared.
• Solution:
  1. Define a MAP or ORDER method: You can define a MAP or ORDER method in the object definition to use during sorting. A MAP method maps an object to a scalar value, and an ORDER method compares the sizes of two objects.
  2. Modify the sorting method: If you cannot define a MAP or ORDER method, you can modify the sorting method and use other methods for sorting, such as sorting by other columns.

OBE-22990: LOB locators cannot span transactions

• OceanBase Database error code: 9715

• SQLSTATE: HY000

• Cause: The LOB locator does not support write operations across transactions.

• Solution: Assign a new value to the LOB locator and then perform the write operation.

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

• OceanBase Database error code: 22998

• SQLSTATE: HY000

• Cause: The CLOB or NCLOB data in 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_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 Database error code: 9755

• SQLSTATE: HY000

• Cause: The primary table does not contain a materialized view log, so a fast refresh cannot be performed.

• Solution: Create a materialized view log for the primary table.

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

• OceanBase Database error code: 9764

• SQLSTATE: HY000

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

• Solution: Choose an expression that results in a time later than CURRENT_DATE.

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

• OceanBase Database error code: 5932

• SQLSTATE: HY000

• Cause: The name string is invalid.

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

• OceanBase Database error code: 9761

• SQLSTATE: HY000

• Cause: An attempt is made to explicitly refresh a NEVER REFRESH materialized view (MV).

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

OBE-24323: value not allowed

• OceanBase Database error code: 7297

• SQLSTATE: HY000

• Cause: The parameter is passed an empty value or an invalid value.

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

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

• OceanBase Database error code: 5962

• SQLSTATE: HY000

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

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

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

• OceanBase Database error code: 5961

• SQLSTATE: HY000

• Cause: The specified object type is invalid.

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

OBE-24236: source text is empty

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

OBE-24334: no descriptor for this position

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

• SQLSTATE: HY000

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

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

OBE-24761: transaction rolled back

• OceanBase Database error code: 6002

• SQLSTATE: 40000

• Cause: The transaction is rolled back.

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

• OceanBase Database error code: 6213

• SQLSTATE: 40000

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

OBE-24761: transaction rolled back: transaction is killed

• OceanBase Database error code: 6211

• SQLSTATE: 25000

• Cause: The transaction is rolled back because the transaction is terminated.

OBE-24761: transaction rolled back: partition is frozen

• OceanBase Database error code: 6214

• SQLSTATE: 25000

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

OBE-24761: transaction rolled back: Transaction exiting

• OceanBase Database error code: 6223

• SQLSTATE: 25000

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

OBE-24761: transaction rolled back: transaction needs rollback

• OceanBase Database error code: 6224

• SQLSTATE: 25000

• Cause: The transaction is rolled back because the transaction needs to be rolled back.

OBE-24761: transaction rolled back: transaction idle timeout

• OceanBase Database error code: 6278

• SQLSTATE: 25000

• Cause: The transaction is rolled back because the transaction times out.

Related case:

• Transaction idle timeout, error code OBE-24761

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

• OceanBase Database error code: 6234

• SQLSTATE: 25000

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

OBE-25002 : cannot create INSTEAD OF triggers on tables

• OceanBase Database error code: 9572

• SQLSTATE: HY000

• Error reason: 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 Database error code: 9571

• SQLSTATE: HY000

• Error reason: You specified the WHEN clause in an INSTEAD OF trigger.

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

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

• OceanBase Database error code: 9663

• SQLSTATE: HY000

• Error reason: You cannot create INSTEAD OF triggers on read-only views.

• Solution: Create INSTEAD OF triggers on nonread-only views.

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

• OceanBase Database error code: 9569

• SQLSTATE: HY000

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

• Solution: Define nested table triggers by using nested table columns of views.

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

• OceanBase Database error code: 9705

• SQLSTATE: HY000

• Error reason: 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 Database error code: 9706

• SQLSTATE: HY000

• Error reason: The trigger referenced in the FOLLOWS or PRECEDES clause is of a different type or 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 Database error code: 9707

• SQLSTATE: HY000

• Error reason: A cyclic trigger dependency is formed.

• Solution: Do not create triggers that form cyclic dependencies.

OBE-25025 : cannot specify PRECEDES clause

• OceanBase Database error code: 9708

• SQLSTATE: HY000

• Error reason: You specified the PRECEDES clause when you create 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 Database error code: 5795

• SQLSTATE: HY000

• Error reason: You attempt to insert, update, or delete data from a table with the DISABLE VALIDATE constraint.

• Solution: Change the constraint status.

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

• OceanBase Database error code: 5800

• SQLSTATE: HY000

• Error reason: The table does not have the specified constraint.

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

• OceanBase Database error code: 4157

• SQLSTATE: 22003

• Error reason: The value of the converted operand 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 Database error code: 5619

• SQLSTATE: HY000

• Error reason: The column used to name the join (NATURAL join or join with the USING clause) cannot have an explicit qualifier.

• Solution: Remove the qualifier.

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

• OceanBase Database error code: 5625

• SQLSTATE: HY000

• Error reason: When the query block uses ANSI-style joins, the old-style outer join + cannot be used.

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

OBE-25405：Transaction state unknown

• OceanBase Database error code: 6222

• SQLSTATE: HY000

• Error reason: The transaction failed when it tried to commit. Automatic failover may not determine the transaction state.

• Solution: Manually determine the transaction state.

OBE-28001：the password has expired

• OceanBase Database error code: 4366

• SQLSTATE: HY000

• Error reason: The user account has expired, and you must change the password.

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

OBE-28101：policy already exists

• OceanBase Database error code: 9718
• SQLSTATE: HY000
• Error reason: 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 Database error code: 9719
• SQLSTATE: HY000
• Error reason: The specified 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: Cannot add a policy to a sys-owned object.
• Resolution: You cannot perform this action.

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

• OceanBase error code: 9721
• SQLSTATE：HY000
• Cause: An invalid value was provided for the parameter.
• Solution: Specify a valid value for the parameter.

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

• OceanBase error code: 9722
• SQLSTATE：HY000
• Cause: Could not create a column-level security policy in the object view.

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

• OceanBase Database error code: 9723
• SQLSTATE：HY000
• Reason: The input value is invalid or missing.

OBE-28107：policy was disabled

• OceanBase Database error code: 9724
• SQLSTATE：HY000
• Cause: The policy is disabled.
• Solution: If you enforce the policy, you must enable it.

OBE-28108：circular security policies detected

• OceanBase Error: 9725
• SQLSTATE：HY000
• Cause: Policies for the same object reference each other.

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

• OceanBase Database error code: 9726
• SQLSTATE：HY000
• Cause: A large number of policies are associated with this object.
• Resolution: Drop one or more policies.

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

• OceanBase Database error code: 9727
• SQLSTATE：HY000 *Cause: The strategy function or package is invalid. It might have been deleted or its validity has expired.
• Fix: Check the status of the feature and correct the issue. Or recreate a policy with a valid feature.

OBE-28111：insufficient privilege to evaluate policy predicate

• OceanBase error code: 9728
• SQLSTATE：HY000
• Cause: The owner of the strategy function cannot access the object.

OBE-28112：failed to execute policy function

• OceanBase Database error: 9729
• SQLSTATE：HY000
• Error cause: The strategy is invalid because there are multiple errors in the strategy function.

OBE-28113：policy predicate has error

• OceanBase error code: 9730
• SQLSTATE：HY000
• Cause: The policy has an error in a predicate.

OBE-28116：insufficient privileges to do direct path access

• OceanBase Error Code: 9731
• SQLSTATE：HY000
• Cause: You do not have the required permissions to access the direct path.

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

• OceanBase error code: 9732
• SQLSTATE：HY000
• Cause: A constraint violation error occurred because the parent record was not found.
• Fix: Ensure that the updated foreign key values are also visible in the parent record.

OBE-28118：policy group already exists

• OceanBase error code: 9733
• SQLSTATE：HY000
• Cause: The strategy group already exists.

OBE-28119：policy group does not exist

• OceanBase error code: 9734
• SQLSTATE：HY000
• The error occurred because the strategy group does not exist.

OBE-28120：driving context already exists

• OceanBase Database error code: 9735
• SQLSTATE：HY000
• Cause: A context already exists.

OBE-28121: driving context does not exist

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

OBE-28122: can not update SYS_DEFAULT policy group

• OceanBase Database error code: 9737
• SQLSTATE: HY000
• Error: 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 Database error code: 9738
• SQLSTATE: HY000
• Error: The driving context contains an invalid group.
• Solution: Make sure to pass a valid policy group to DBMS_SESSION.SET_CONTEXT when you initialize the policy driving context.

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

• OceanBase Database error code: 9739
• SQLSTATE: HY000
• Error: The column in the sec_relevant_cols list cannot be of an object data type.
• Solution: Make sure that the columns specified in the sec_relevant_cols list are not of an object data type or XMLType.

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

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

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

• OceanBase Database error code: 9741
• SQLSTATE: HY000
• Error: The 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 Database error code: 9742
• SQLSTATE: HY000
• Error: The MERGE INTO syntax does not support the security policy.
• Solution:
  • If you do not have the permission to modify the security policy, use the INSERT, UPDATE, and DELETE DML statements instead of the MERGE INTO statement on a table that has a defined security policy.
  • If you have the permission to modify the security policy, redefine it to include all DML statement types (INSERT, UPDATE, and DELETE) in the statement_types parameter, or make sure that the policy does not include any security-related columns.

OBE-28115: policy with check option violation

• OceanBase Database error code: 5789

• SQLSTATE: HY000

• Error: The security label of the written data is incorrect.

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

• OceanBase Database error code: 9687

• SQLSTATE: HY000

• Error: The input parameter is invalid.

OBE-28264: Client identifier is too long

• OceanBase Database error code: 9688

• SQLSTATE: HY000

• Error: The length of the client ID exceeds 64 bytes.

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

• OceanBase Database error code: 9690

• SQLSTATE: HY000

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

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

• OceanBase Database error code: 9691

• SQLSTATE: HY000

• Error: The number of key-value pairs in the session based context exceeds the maximum size specified by the _session_context_size parameter.

OBE-28268: Invalid NameSpace Value

• OceanBase Database error code: 9689

• SQLSTATE: HY000

• Error: The name of the context namespace is invalid.

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

• OceanBase Database error code: 9679

• SQLSTATE: HY000

• Error cause: The value of the count parameter specified when calling the dbms_sql package to define an array 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 when defining an array, and then retry.

OBE-29257: host %.*s unknown

• OceanBase Database error code: 5928

• SQLSTATE: HY000

• Error cause: The specified host is unknown.

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

OBE-29261: bad argument

• OceanBase Database error code: 5951, 5968

• SQLSTATE: HY000

• Error cause: An incorrect parameter is passed to the PL API.

• Solution: Check the parameters passed to the PL API and then retry.

OBE-29261: bad argument

• OceanBase Database error code: 9813

• SQLSTATE: HY000

• Error cause: This error is triggered when the parameters passed to a function or procedure in the UTL_HTTP package do not meet the requirements.

• Solution: Check the parameters passed to the PL API and then retry.

OBE-29262: bad URL

• OceanBase Database error code: 9814

• SQLSTATE: HY000

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

• Solution: Check whether the URL is correct.

OBE-29266: end-of-body reached

• OceanBase Database error code: 9815

• SQLSTATE: HY000

• Error cause: When using the UTL_HTTP package to read the HTTP response body, the program attempts to read data from an HTTP response stream that has already reached the end.

• Solution: In most cases, this is a normal process signal that needs to be captured and properly handled, not a fault that needs to be fixed. You need to ensure that the code has robust exception handling logic to gracefully end the HTTP request.

OBE-29295: invalid mime header tag

• OceanBase Database error code: 5970

• SQLSTATE: HY000

• Error cause: An error occurs when scanning the mime header tag string.

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

OBE-29268: HTTP client error

• OceanBase Database error code: 9816

• SQLSTATE: HY000

• Error 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 Database error code: 9817

• SQLSTATE: HY000

• Error cause: An error occurs in the HTTP server.

• Solution: Check the HTTP server status.

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

• OceanBase Database error code: 9818

• SQLSTATE: HY000

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

• Solution: Configure the ACL for the database user that performs network operations and explicitly grant it the permission to access specific external network resources.

OBE-29275: partial multibyte character

• OceanBase Database error code: 9819

• SQLSTATE: HY000

• Error cause: The multibyte character is partially processed.

• Solution: Check the UTL_HTTP response data processing code to see whether the length is calculated based on bytes or the data is truncated.

OBE-29263: HTTP protocol error

• OceanBase Database error code: 9820

• SQLSTATE: HY000

• Error cause: An error occurs in the HTTP protocol.

• Solution: Check the server or network issues.

OBE-29273: HTTP request failed

• OceanBase Database error code: 9821

• SQLSTATE: HY000

• Error cause: The HTTP request failed.

• Solution: Check the server or network connectivity.

OBE-29270: too many open HTTP requests

• OceanBase Database error code: 9822

• SQLSTATE: HY000

• Error cause: Too many HTTP requests are open.

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

OBE-29276: transfer timeout

• OceanBase Database error code: 9823

• SQLSTATE: HY000

• Error cause: The transfer timed out.

• Solution: Optimize the network environment, improve the server performance, or increase the client timeout setting.

OBE-29264: unknown or unsupported URL scheme

• OceanBase Database error code: 9824

• SQLSTATE: HY000

• Error reason: The protocol scheme specified in the URL cannot be identified or is not supported by the UTL_HTTP package.

• Solution: Check and correct the URL string.

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

• OceanBase Database error code: 4702

• SQLSTATE: HY000

• Error reason: The parameter name of the CREATE_PLAN, CREATE_CDB_PLAN, CREATE_CONSUMER_GROUP, or CREATE_CATEGORY procedure in the DBMS_RESOURCE_MANAGER package is already in use.

• Solution: Specify an unused parameter name.

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

• OceanBase Database error code: 4703

• SQLSTATE: HY000

• Error reason: The plan name specified for the UPDATE_PLAN or UPDATE_CDB_PLAN procedure in the DBMS_RESOURCE_MANAGER package does not exist.

• Solution: Specify an existing plan name.

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

• OceanBase Database error code: 4704

• SQLSTATE: HY000

• Error reason: An invalid value is 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 Database error code: 4705

• SQLSTATE: HY000

• Error reason: The plan directive specified for the UPDATE_PLAN_DIRECTIVE or UPDATE_CDB_PLAN_DIRECTIVE procedure in the DBMS_RESOURCE_MANAGER package does not exist.

• Solution: Specify an existing plan directive.

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

• OceanBase Database error code: 4706

• SQLSTATE: HY000

• Error reason: An attempt is made to create a plan directive that already exists.

• Solution: Retry the operation with other values.

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

• OceanBase Database error code: 4707

• SQLSTATE: HY000

• Error reason: The plan directive name is not supported.

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

• OceanBase Database error code: 4710

• SQLSTATE: HY000

• Error reason: The consumer group specified does not exist.

• Solution: Specify an existing consumer group.

OBE-29471: DBMS_SQL access denied

• OceanBase Database error code: 5856

• SQLSTATE: HY000

• Error reason: Access to DBMS_SQL is denied for security reasons.

• Solution: Obtain more information from the Alert log and Trace file.

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

• OceanBase Database error code: 9677

• SQLSTATE: HY000

• Error reason: 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 Database error code: 9839

• SQLSTATE: HY000

• Error reason: The Java class currently used in the session is redefined or deleted, causing the Java session state to become invalid. The system automatically clears the session state.

• Solution: Deploy or reload the relevant Java class.

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

• OceanBase Database error code: 7301

• SQLSTATE: 42000

• Error reason: An attempt is made to create multiple domain indexes on a column list using the same domain.

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

OBE-29900: operator binding does not exist

• OceanBase Database error code: 7298

• SQLSTATE: 42000

• Error reason: The specified operator binding cannot be found when attempting to execute an operation.

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