Applicability
This topic applies only to the Oracle-compatible mode OceanBase Database.
OBE-20000: operator binding does not exist
Error code in OceanBase Database: 7299
SQLSTATE: 42000
Cause: The specified operator binding is not found when you are attempting to perform the operation.
Solution: Make sure that the operator or function name is correct without spelling errors.
Note
- For OceanBase Database V4.3.x, this error code is introduced since OceanBase Database V4.3.2.
- For OceanBase Database V4.2.x, this error code is introduced since OceanBase Database V4.2.4.
OBE-20000: '%.*s' invalid partition name
Error code in OceanBase Database: 11002
SQLSTATE: HY000
Cause: The partition name '%.*s' is incorrect.
Solution: Check whether the partition name '%.*s' is correct and complies with the naming rules. Make sure that the partition name is valid.
Note
This error code is introduced since OceanBase Database V4.3.0.
OBE-20000: The stored procedure 'raise_application_error' was called which causes this error to be generated", "ORA%06ld: %.*s
Error code in OceanBase Database: 20000
SQLSTATE: HY000
Cause: The error code of
RAISE_APPLICATION_ERRORdefined by the stored procedure is called.Solution: Fix the issue based on the description in the error message, or contact the application administrator or database administrator for more information.
OBE-21000: error number argument to raise_application_error of stringstring is out of range
Error code in OceanBase Database: 21000
SQLSTATE: HY000
Cause: The error code of
RAISE_APPLICATION_ERRORis out of range.
OBE-21560: argument %.*s is null, invalid, or out of range
Error code in OceanBase Database: 5934
SQLSTATE: HY000
Cause: The passed argument value is
NULL, invalid, or out of range. For example, the value of the location or size parameter ofLOB/FILEdata is beyond the range of 1 to (4 GB - 1), or a file is opened in an invalid opening mode.Solution: Check and correct the program to ensure that no
NULL, invalid, or out-of-range value is passed.
OBE-22003: value is out of range
Error code in OceanBase Database: 4157
SQLSTATE: 22003
Cause: An unexpected communication error occurred while executing the specified
TCP/IPfunctionfunc. The return code of theTCP/IPfunction isrc, and the argument of thefuncfunction isparm.Solution: Contact OceanBase Technical Support for troubleshooting.
OBE-22369: invalid parameter encountered in method %s
Error code in OceanBase Database: 5955
SQLSTATE: HY000
Cause: One of the following invalid parameters is being passed to
SYS:SYS.AnyType,SYS.AnyData, andSYS.AnyDataSet.Solution: Check the parameters being passed and make sure that the parameters are allowed.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-22370: incorrect usage of method %s
Error code in OceanBase Database: 5956
SQLSTATE: HY000
Cause:
SYS.AnyType,SYS.AnyData, orSYS.AnyDataSetis being used inappropriately.Solution: Make sure that the usage is correct.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-22625: OCIAnyData is not well-formed
Error code in OceanBase Database: 5965
SQLSTATE: HY000
Cause: You are attempting to use
OCIAnyDatawithout initializing or constructing it.Solution: Use
OCIAnyDataBeginConstructto initialize the handle before attributes are added. UseOCIAnyDataEndConstructto complete the construction. Alternatively, useOCIAnyDataConvertto perform the construction. Make sure thatOCIAnyDatais properly constructed before it accesses attributes.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-22626: Type Mismatch while constructing or accessing OCIAnyData
Error code in OceanBase Database: 5957
SQLSTATE: HY000
Cause: The provided type did not match the type of AnyData. If the operation is attempting to do piecewise construction or access, the type provided does not match the type of the current attribute.
Solution: Make sure that the type provided matches the type of object to be constructed or accessed.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-22627: tc [%s] must be that of object/varray/nested table
Error code in OceanBase Database: 5966
SQLSTATE: HY000
Cause: The type code is not that of the object, varray, or nested table.
Solution: Make sure that the type code is
OCI_TYPECODE_OBJECT,OCI_TYPECODE_VARRAY, orOCI_TYPECODE_TABLE.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-22806: not an object or REF
- Error code in OceanBase Database: 5477
- SQLSTATE: 42000
- Cause: The item is neither an object nor a REF.
- Solution: Use an object or REF and retry the operation.
OBE-22816: unsupported feature with RETURNING clause
Error code in OceanBase Database: 9573
SQLSTATE: HY000
Cause: The object type column does not support the
RETURNINGclause, LONG column, remote tables, andINSERTandINSTEAD OFtriggers with subqueries.Solution: Use independent statements to obtain values.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-22858: invalid alteration of datatype
- Error code in OceanBase Database: 7414
- SQLSTATE: 42000
- Cause: The data type cannot be changed or the specified new data type is invalid.
- Solution:
- Check whether the data type can be changed and make sure that the specified new data type is valid.
- Check the size of the data to be changed and make sure that all data can be accommodated in the new data type.
Note
This error code is introduced since OceanBase Database V4.2.0.
OBE-22859: invalid modification of columns
- Error code in OceanBase Database: 7415
- SQLSTATE: 42000
- Cause: The column or table schema cannot be modified.
- Solution:
- Confirm whether the table schema can be modified before you perform modifications.
- Confirm whether the column attributes can be modified before you perform modifications.
Note
This error code is introduced since OceanBase Database V4.2.0.
OBE-22859: Expected XML tag , got no content
- Error code in OceanBase Database: 7416
- SQLSTATE: 42000
- Cause: The XML data lacks tag content.
- Solution:
- Make sure that the XML data is valid and all tags have content.
- Make sure that the XML format is valid and all tags are correctly nested and closed.
Note
This error code is introduced since OceanBase Database V4.2.0.
OBE-22866: cannot replace a type with table dependents
Error code in OceanBase Database: 11006
SQLSTATE: HY000
Cause: You cannot replace a type with table dependencies.
Solution: Delete all tables that depend on the current type and try again.
Note
This error code is introduced since OceanBase Database V4.2.2.
OBE-22901: cannot compare VARRAY or LOB attributes of an object type
Error code in OceanBase Database: 7432
SQLSTATE: 42000
Cause: You are attempting to compare the VARRAY or LOB attributes of an object type without the MAP or ORDER method.
Solution: Define the MAP or ORDER method for the object type.
Note
This error code is introduced since OceanBase Database V4.2.2.
OBE-22902: CURSOR expression not allowed
Error code in OceanBase Database:
SQLSTATE: HY000
Cause: The output parameter is not a bind variable.
Solution: Check the use method of the output parameter and make sure that the output parameter is a bind variable.
Note
This error code is introduced since OceanBase Database V4.3.0.
OBE-22903: MULTISET expression not allowed
- Error code in OceanBase Database: 9716
- SQLSTATE: HY000
- Cause: The MULTISET expression is not allowed.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-22907: invalid CAST to a type that is not a nested table or VARRAY
- Error code in OceanBase Database: 9717
- SQLSTATE: HY000
- Cause: The CAST operation was performed on something other than a nested table or VARRAY type.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-22922: LOB value does not exist
- Error code in OceanBase Database: 7419
- SQLSTATE: HY000
- Cause: The LOB value that you tried to access does not exist.
- Solution: Make sure that the table or index that contains the LOB value exists or can be restored.
Note
This error code is introduced since OceanBase Database V4.2.0.
OBE-22928: invalid privilege on directories
Error code in OceanBase Database: 5374
SQLSTATE: HY000
Cause: You are attempting to grant or revoke a directory operation privilege that is invalid for directories.
Solution: You can grant or revoke only the
CREATE,DELETE,READ,WRITE, andEXECUTEprivileges on directories. Do not grant or revoke other privileges.
OBE-22950: cannot ORDER objects without MAP or ORDER method
- Error code in OceanBase Database: 7412
- SQLSTATE: 42000
- Cause: The MAP or ORDER method is not specified for the comparison of objects.
- Solution:
- Specify the MAP or ORDER method in the definition of an object for sorting. You can use the MAP method to map an object to a scalar value, and use the ORDER method to compare the values of two objects.
- If you cannot specify the MAP or ORDER method, you can modify the sorting method. For example, you can use other columns for sorting.
Note
This error code is introduced since OceanBase Database V4.2.0.
OBE-22990: LOB locators cannot span transactions
Error code in OceanBase Database: 9715
SQLSTATE: HY000
Cause: The LOB locator cannot span transactions in writing.
Solution: Assign another value to the LOB locator before performing the write operation.
OBE-22998: CLOB or NCLOB in multibyte character set not supported
Error code in OceanBase Database: 22998
SQLSTATE: HY000
Cause:
CLOBorNCLOBdata in a fixed-width or variable-width multi-byte character set is passed to an SQL character function that does not support multi-byteLOBdata.Solution: Use a
DBMS_LOBfunction such asDBMS_LOB.INSTR()andDBMS_LOB.SUBSTR(), or use PL/SQL statementsDBMS_LOB.READ/WRITEto accessLOBdata.
OBE-23413: table %s.%s does not have a materialized view log
Error code in OceanBase Database: 9755
SQLSTATE: HY000
Cause: Fast refreshes are not supported because the primary table does not have a materialized view log.
Solution: Create the corresponding materialized view log.
Note
This error code is introduced since OceanBase Database V4.2.2.
OBE-23420: the parameter %s must evaluate to a time in the future
Error code in OceanBase Database: 9764
SQLSTATE: HY000
Cause: The
intervalparameter evaluates to a value earlier than the time returned byCURRENT_DATE.Solution: Select an expression that evaluates to a value later than the time returned by
CURRENT_DATE.
Note
This error code is introduced since OceanBase Database V4.2.2.
OBE-23481: unexpected name string'%.*s'
Error code in OceanBase Database: 5932
SQLSTATE: HY000
Cause: The name string is invalid.
OBE-23538: cannot explicitly refresh a NEVER REFRESH materialized view (%s)
Error code in OceanBase Database: 9761
SQLSTATE: HY000
Cause: You are attempting to explicitly perform a NEVER REFRESH MV operation.
Solution: Do not perform this refresh operation, or remove the materialized view from the list.
Note
This error code is introduced since OceanBase Database V4.2.2.
OBE-24323: value not allowed
Error code in OceanBase Database: 7297
SQLSTATE: HY000
Cause: An empty or invalid value is passed to a parameter.
Solution: Make sure that valid values are correctly passed to all required parameters.
Note
This error code is introduced since OceanBase Database V4.2.2.
OBE-24234: unable to get source of string \'%.*s\'.\'%.*s\', insufficient privileges or does not exist
Error code in OceanBase Database: 5962
SQLSTATE: HY000
Cause: The specified PL/SQL object in a
DBMS_PREPROCESSORsubprogram did not exist, or you did not have the privileges required to view its source.Solution: Make sure that the specified object exists and you have the privileges required to view its source.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-24235: bad value for object type: %.*s
Error code in OceanBase Database: 5961
SQLSTATE: HY000
Cause: The specified object type was not appropriate.
Solution: Make sure that the specified object type is one of the following types: package, package body, procedure, function, trigger, type, and type body.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-24236: source text is empty
Error code in OceanBase Database: 5960
SQLSTATE: HY000
Cause: The input source text provided for a
DBMS_PREPROCESSORsubprogram was empty.Solution: Pass non-empty input source text as the input.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-24334: no descriptor for this position
Error code in OceanBase Database: 5973
SQLSTATE: HY000
Cause: The application was trying to get a descriptor of an illegal position from a handle.
Solution: Check the position number.
OBE-24381: error(s) in array DML
Error code in OceanBase Database: 5883
SQLSTATE: HY000
Cause: One or multiple rows in the DML statement failed.
Solution: Refer to the error stack in the error handle.
OBE-24761: transaction rolled back
Error code in OceanBase Database: 6002
SQLSTATE: 40000
Cause: The transaction is rolled back.
OBE-24761: transaction rolled back: transaction context does not exist
Error code in OceanBase Database: 6213
SQLSTATE: 40000
Cause: The transaction is rolled back because the transaction context does not exist.
OBE-24761: transaction rolled back: transaction is killed
Error code in OceanBase Database: 6211
SQLSTATE: 25000
Cause: The transaction is rolled back because the transaction is terminated.
OBE-24761: transaction rolled back: partition is frozen
Error code in OceanBase Database: 6214
SQLSTATE: 25000
Cause: The transaction is rolled back because the partition is frozen.
OBE-24761: transaction rolled back: Transaction exiting
Error code in OceanBase Database: 6223
SQLSTATE: 25000
Cause: The transaction is rolled back because the transaction already exists.
OBE-24761: transaction rolled back: transaction needs rollback
Error code in OceanBase Database: 6224
SQLSTATE: 25000
Cause: The transaction is rolled back as required.
OBE-24761: transaction rolled back: transaction idle timeout
Error code in OceanBase Database: 6278
SQLSTATE: 25000
Cause: The transaction is rolled back because the transaction timed out.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-24761: transaction rolled back: transaction context count reach limit
Error code in OceanBase Database: 6234
SQLSTATE: 25000
Cause: The transaction is rolled back because the transaction context count reaches the limit.
OBE-25002: cannot create INSTEAD OF triggers on tables
Error code in OceanBase Database: 9572
SQLSTATE: HY000
Cause: You cannot create an
INSTEAD OFtrigger on a table.Solution: Create an
INSTEAD OFtrigger on a view, or create aDMLtrigger on a table.
OBE-25004: WHEN clause is not allowed in INSTEAD OF triggers
Error code in OceanBase Database: 9571
SQLSTATE: HY000
Cause: The
WHENclause is specified in anINSTEAD OFtrigger.Solution: Delete the
WHENclause when you create anINSTEAD OFtrigger.
OBE-25005: cannot CREATE INSTEAD OF trigger on a read-only view
Error code in OceanBase Database: 9663
SQLSTATE: HY000
Cause: You cannot create an
INSTEAD OFtrigger on a read-only view.Solution: Create the
INSTEAD OFtrigger on a non-read-only view.
OBE-25009: Nested tableclause allowed only for INSTEAD OF triggers
Error code in OceanBase Database: 9569
SQLSTATE: HY000
Cause: Nested table clauses are allowed only in
INSTEAD OFtriggers.Solution: Define nested table triggers by using the nested table columns of a view.
OBE-25021: cannot reference a trigger defined on another table
Error code in OceanBase Database: 9705
SQLSTATE: HY000
Cause: The referenced trigger in the
FOLLOWSclause was defined on another table.Solution: Create the referenced trigger on the same table.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-25022: cannot reference a trigger of a different type
Error code in OceanBase Database: 9706
SQLSTATE: HY000
Cause: The referenced trigger in the
FOLLOWSorPRECEDESclause was either a different type or not a compound trigger.Solution: Create the referenced trigger as the same type or as a compound trigger.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-25023: Cyclic trigger dependency is not allowed
Error code in OceanBase Database: 9707
SQLSTATE: HY000
Cause: Cyclic trigger dependency was formed.
Solution: Do not create a trigger that can form cyclic dependency.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-25025: cannot specify PRECEDES clause
Error code in OceanBase Database: 9708
SQLSTATE: HY000
Cause: The
PRECEDESclause was specified when a regular trigger was created.Solution: Do not create a regular trigger with a
PRECEDESclause.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-25128: No insert/update/delete on table with constraint disabled and validated
Error code in OceanBase Database: 5795
SQLSTATE: HY000
Cause: You are attempting to perform an INSERT, UPDATE, or DELETE operation on a table with the
DISABLE VALIDATEconstraint.Solution: Change the status of the constraint.
OBE-25129: cannot modify constraint (%.*s) - no such constraint
Error code in OceanBase Database: 5800
SQLSTATE: HY000
Cause: The specified constraint does not exist in the table.
OBE-25137: Data value %s out of range in '%s'
Error code in OceanBase Database: 4157
SQLSTATE: 22003
Cause: After conversion, the operand value is greater than the target value.
Solution: Increase the target value.
OBE-25154: Column part of using clause can not have qualifier
Error code in OceanBase Database: 5619
SQLSTATE: HY000
Cause: A column used to name a join, such as the
NATURALjoin or a join that uses theUSINGclause, cannot contain an explicit qualifier.Solution: Delete the qualifiers.
OBE-25156: old style outer join (+) cannot be used with ANSI joins
Error code in OceanBase Database: 5625
SQLSTATE: HY000
Cause: If a query block uses an ANSI style join, the old-style join (+) used to specify an outer join cannot be used.
Solution: Use an ANSI style to specify an outer join.
OBE-25405: Transaction state unknown
Error code in OceanBase Database: 6222
SQLSTATE: HY000
Cause: A failure occurred when a transaction is committed. The transaction status may not be automatically checked during failover.
Solution: Manually check the transaction status.
OBE-28001: the password has expired
Error code in OceanBase Database: 4366
SQLSTATE: HY000
Cause: The user account has expired, and the password must be changed.
Solution: Change the password or contact the database administrator.
OBE-28101: policy already exists
- Error code in OceanBase Database: 9718
- SQLSTATE: HY000
- Cause: The strategy already exists.
- Solution: Check whether the strategy has been added or use a different strategy name.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28102: policy does not exist
- Error code in OceanBase Database: 9719
- SQLSTATE: HY000
- Cause: The strategy does not exist.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28103: adding a policy to an object owned by SYS is not allowed
- Error code in OceanBase Database: 9720
- SQLSTATE: HY000
- Cause: You cannot add strategies to objects owned by the sys tenant.
- Solution: Do not perform this operation.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28104: input value for %s is not valid
- Error code in OceanBase Database: 9721
- SQLSTATE: HY000
- Cause: The input value of the parameter is invalid.
- Solution: Specify a valid parameter value.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28105: cannot create security relevant column policy in an object view
- Error code in OceanBase Database: 9722
- SQLSTATE: HY000
- Cause: Security-related column strategies cannot be created in an object view.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28106: input value for argument %s is not valid
- Error code in OceanBase Database: 9723
- SQLSTATE: HY000
- Cause: The input value of the parameter is invalid or missing.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28107: policy was disabled
- Error code in OceanBase Database: 9724
- SQLSTATE: HY000
- Cause: The strategy was disabled.
- Solution: Enable the strategy before using it.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28108: circular security policies detected
- Error code in OceanBase Database: 9725
- SQLSTATE: HY000
- Cause: Strategies on the same object are mutually referenced.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28109: the number of related policies has exceeded the limit of 16
- Error code in OceanBase Database: 9726
- SQLSTATE: HY000
- Cause: The strategies on an object has exceeded the upper limit.
- Solution: Drop one or more strategies.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28110: policy function or package %.*s.%.*s has error
- Error code in OceanBase Database: 9727
- SQLSTATE: HY000
- Cause: The strategy function or package is incorrect, has been deleted, or is no longer valid.
- Solution: Check the status of the feature and fix the issue, or create a new strategy with a valid feature.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28111: insufficient privilege to evaluate policy predicate
- Error code in OceanBase Database: 9728
- SQLSTATE: HY000
- Cause: The owner of the strategy function does not have privilege to access the object.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28112: failed to execute policy function
- Error code in OceanBase Database: 9729
- SQLSTATE: HY000
- Cause: The strategy function cannot be executed. One or more errors occurred during the execution of the strategy function.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28113: policy predicate has error
- Error code in OceanBase Database: 9730
- SQLSTATE: HY000
- Cause: The strategy predicate has encountered an error.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28116: insufficient privileges to do direct path access
- Error code in OceanBase Database: 9731
- SQLSTATE: HY000
- Cause: You do not have sufficient privileges to access the path directly.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28117: integrity constraint violated * parent record not found
- Error code in OceanBase Database: 9732
- SQLSTATE: HY000
- Cause: The parent record cannot be found because the integrity constraint is violated.
- Solution: Make sure that the updated foreign key value is visible at the parent level.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28118: policy group already exists
- Error code in OceanBase Database: 9733
- SQLSTATE: HY000
- Cause: The strategy group already exists.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28119: policy group does not exist
- Error code in OceanBase Database: 9734
- SQLSTATE: HY000
- Cause: The strategy group does not exist.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28120: driving context already exists
- Error code in OceanBase Database: 9735
- SQLSTATE: HY000
- Cause: The driving context already exists.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28121: driving context does not exist
- Error code in OceanBase Database: 9736
- SQLSTATE: HY000
- Cause: The driving context does not exist.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28122: can not update SYS_DEFAULT policy group
- Error code in OceanBase Database: 9737
- SQLSTATE: HY000
- Cause: The SYS_DEFAULT strategy group cannot be updated.
- Solution: Do not create or drop the SYS_DEFAULT strategy group. Such operations are not allowed.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28123: Driving context %.*s,%.*s contains invalid group %.*s
- Error code in OceanBase Database: 9738
- SQLSTATE: HY000
- Cause: The driving context contains an invalid group.
- Solution: Make sure that a valid strategy group is passed to DBMS_SESSION.SET_CONTEXT when the driving context of the strategy is initialized.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28124: Column %.*s in sec_relevant_cols cannot be of an object data type
- Error code in OceanBase Database: 9739
- SQLSTATE: HY000
- Cause: The column in
sec_relevant_colscannot be of an object data type. - Solution: Make sure that none of the columns specified in
sec_relevant_colsare of an object data type or XML type.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28125: A protected base column was referenced in an unprotected virtual column expression
- Error code in OceanBase Database: 9740
- SQLSTATE: HY000
- Cause: A protected base column was referenced in an unprotected virtual column expression.
- Solution: Check the strategy definition and ensure that the virtual columns are also protected.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28126: Attribute association failed for policy %.*s
- Error code in OceanBase Database: 9741
- SQLSTATE: HY000
- Cause: The attribute association of the strategy failed.
- Solution: Specify a context attribute of a local application.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28132: The MERGE INTO syntax does not support the security policy
- Error code in OceanBase Database: 9742
- SQLSTATE: HY000
- Cause: The MERGE INTO syntax does not support security strategies.
- Solution:
- If you do not have the privilege to modify security strategies, use INSERT, UPDATE, and DELETE DML statements instead of the MERGE INTO statement on tables with defined security strategies.
- If you have the privilege to modify security strategies, redefine the security strategy so that its statement_types include all DML statement types, including INSERT, UPDATE, and DELETE, or ensure that the strategy has no security-related columns.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-28115: policy with check option violation
Error code in OceanBase Database: 5789
SQLSTATE: HY000
Cause: The security flag written into data is invalid.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-28106: input value for argument #%d is not valid
Error code in OceanBase Database: 9687
SQLSTATE: HY000
Cause: The input value for the argument is invalid.
OBE-28264: Client identifier is too long
Error code in OceanBase Database: 9688
SQLSTATE: HY000
Cause: The client ID is longer than 64 bytes in length.
Note
This error code is introduced since OceanBase Database V3.2.4.
OBE-28265: Namespace beginning with 'SYS_' is not allowed
Error code in OceanBase Database: 9690
SQLSTATE: HY000
Cause: A context namespace beginning with
'SYS_'was not allowed.
Note
This error code is introduced since OceanBase Database V3.2.4.
OBE-28267: The maximum size specified by the _session_context_size parameter was exceeded
Error code in OceanBase Database: 9691
SQLSTATE: HY000
Cause: The number of key-value pairs for a session-based context exceeds the upper limit specified by
_session_context_size.
Note
This error code is introduced since OceanBase Database V3.2.4.
OBE-28268: Invalid NameSpace Value
Error code in OceanBase Database: 9689
SQLSTATE: HY000
Cause: The name of the context namespace was invalid.
Note
This error code is introduced since OceanBase Database V3.2.4.
OBE-29253: Invalid count argument passed to procedure dbms_sql.define_array
Error code in OceanBase Database: 9679
SQLSTATE: HY000
Cause: The
countargument specified in the call to the proceduredefine_arrayof thedbms_sqlpackage had an invalid value. Invalid values are negative numbers and nulls. The argument value must be a positive integer.Solution: Correct your PL/SQL program so that only valid arguments are passed to define the array and try again.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-29257: host %.*s unknown
Error code in OceanBase Database: 5928
SQLSTATE: HY000
Cause: The specified host is unknown.
Solution: Check the spelling of the host name or the IP address, and ensure that the host name and the IP address are valid.
OBE-29261: bad argument
Error code in OceanBase Database: 5951 and 5968
SQLSTATE: HY000
Cause: A wrong argument is passed to the PL API.
Solution: Check the arguments passed to the PL API, and try again.
OBE-29295: invalid mime header tag
Error code in OceanBase Database: 5970
SQLSTATE: HY000
Cause: An error occurred while scanning the string for the
mimeheader tag.Solution: Verify that the source data is a valid
mimeheader string in the format of charset/encoding/encoded string.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-29357: %s %.*s already exists
Error code in OceanBase Database: 4702
SQLSTATE: HY000
Cause: The parameter name
CREATE_CATEGORYof theCREATE_PLAN, CREATE_CDB_PLAN, orCREATE_CONSUMER_GROUPprogram, or of theDBMS_RESOURCE_MANAGERprogram package is already in use.Solution: Specify an unused parameter name.
OBE-29358: resource plan %.*s does not exist
Error code in OceanBase Database: 4703
SQLSTATE: HY000
Cause: An invalid plan name is specified for the
UPDATE_PLANorUPDATE_CDB_PLANparameter of theDBMS_RESOURCE_MANAGERprogram package.Solution: Specify a valid plan name.
OBE-29361: value %ld for %s is outside valid range of 0 to 100
Error code in OceanBase Database: 4704
SQLSTATE: HY000
Cause: An invalid value is specified for the plan directive parameter.
Solution: Specify a value ranging from 0 to 100.
OBE-29362: plan directive %.*s, %.*s does not exist
Error code in OceanBase Database: 4705
SQLSTATE: HY000
Cause: A nonexistent plan directive is specified for
UPDATE_PLAN_DIRECTIVEorUPDATE_CDB_PLAN_DIRECTIVEparameter of theDBMS_RESOURCE_MANAGERprogram package.Solution: Specify an existing plan directive.
OBE-29364: plan directive %.*s, %.*s already exists
Error code in OceanBase Database: 4706
SQLSTATE: HY000
Cause: You are attempting to create a plan directive that already exists.
Solution: Use another value and try again.
OBE-29366: plan directive name '%.*s' not supported
Error code in OceanBase Database: 4707
SQLSTATE: HY000
Cause: The plan directive name is not supported.
OBE-29368: consumer group %.*s does not exist
Error code in OceanBase Database: 4710
SQLSTATE: HY000
Cause: A nonexistent consumer group is specified.
Solution: Specify an existing consumer group.
OBE-29471: DBMS_SQL access denied
Error code in OceanBase Database: 5856
SQLSTATE: HY000
Cause: Access to
DBMS_SQLis denied for security considerations.Solution: Obtain more information from the alert logs and trace file.
OBE-29474: DBMS_SQL.OPEN_CURSOR failed. security_level of 0 is not allowed
Error code in OceanBase Database: 9677
SQLSTATE: HY000
Cause: The security level of 0 is specified for
DBMS_SQL.OPEN_CURSOR.Solution: Specify a valid security level.
OBE-29879: cannot create multiple domain indexes on a column list using same
Error code in OceanBase Database: 7301
SQLSTATE: 42000
Cause: You are attempting to create multiple indexes based on the same domain on a list of columns.
Solution: Check for and remove any unnecessary repeated index requests.
Note
- For OceanBase Database V4.3.x, this error code is introduced since OceanBase Database V4.3.2.
- For OceanBase Database V4.2.x, this error code is introduced since OceanBase Database V4.2.4.
OBE-29900: operator binding does not exist
Error code in OceanBase Database: 7298
SQLSTATE: 42000
Cause: The specified operator binding is not found when you are attempting to perform the operation.
Solution: Make sure that the operator or function name is correct without spelling errors.
Note
- For OceanBase Database V4.3.x, this error code is introduced since OceanBase Database V4.3.2.
- For OceanBase Database V4.2.x, this error code is introduced since OceanBase Database V4.2.4.