ORA-20000 to ORA-29999

ORA-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 error code of RAISE_APPLICATION_ERROR defined by the stored procedure is called.

• Solution: Fix the problem based on the description in the error message, or contact the application administrator or database administrator for more information.

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

• OceanBase error code: 21000

• SQLSTATE: HY000

• Cause: The error code of RAISE_APPLICATION_ERROR is out of range.

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

• OceanBase error code: 5934

• SQLSTATE: HY000

• Cause: The passed argument value is NULL, invalid, or out of range. For example, the value of the LOB/FILE positional or size argument exceeds the range of 1 to (4 GB – 1), or files are opened in invalid open modes.

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

ORA-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 return code of the TCP/IP function is rc, and the argument of the func function is parm.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ORA-22369: invalid parameter encountered in method %s

• OceanBase error code: 5955

• SQLSTATE: HY000

• Cause: An invalid parameter is being passed to SYS, including SYS.AnyType, SYS.AnyData, and SYS.AnyDataSet.

• Solution: Check the parameters being passed and make sure that the parameters are allowed.

ORA-22370: incorrect usage of method %s

• OceanBase error code: 5956

• SQLSTATE: HY000

• Cause: SYS.AnyType, SYS.AnyData, or SYS.AnyDataSet is being used inappropriately.

• Solution: Make sure that the usage is correct.

ORA-22625: OCIAnyData is not well-formed

• OceanBase error code: 5965

• SQLSTATE: HY000

• Cause: You are attempting to use OCIAnyData without initializing or constructing it.

• Solution: Use OCIAnyDataBeginConstruct to initialize the handle before attributes are added. Use OCIAnyDataEndConstruct to complete the construction. Alternatively, use OCIAnyDataConvert to perform the construction. Make sure that OCIAnyData is properly constructed before it accesses attributes.

ORA-22626: Type Mismatch while constructing or accessing OCIAnyData

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

ORA-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 the object/varray/nested table.

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

ORA-22806: not an object or REF

• OceanBase error code: 5477
• SQLSTATE: 42000
• Cause: The item is neither an object nor a REF.
• Solution: Use an object or REF and retry the operation.

ORA-22816: unsupported feature with RETURNING clause

• OceanBase error code: 9573

• SQLSTATE: HY000

• Cause: The object type column does not support the RETURNING clause, LONG column, remote tables, and INSERT and INSTEAD OF triggers with subqueries.

• Solution: Use independent statements to obtain values.

ORA-22858: invalid alteration of datatype

• OceanBase error code: 7414
• SQLSTATE: 42000
• Cause: The data type cannot be changed or the specified new data type is invalid.
• Solution:
  1. Check whether the data type can be changed and make sure that the specified new data type is valid.
  2. Check the size of the data to be changed and make sure that all data can be accommodated in the new data type.

ORA-22859: invalid modification of columns

• OceanBase error code: 7415
• SQLSTATE: 42000
• Cause: The column or table schema cannot be modified.
• Solution:
  1. Confirm whether the table schema can be modified before you perform modifications.
  2. Confirm whether the column attributes can be modified before you perform modifications.

ORA-22859: Expected XML tag, got no content

• OceanBase error code: 7416
• SQLSTATE: 42000
• Cause: The XML data lacks tag content.
• Solution:
  1. Make sure that the XML data is valid and all tags have content.
  2. Make sure that the XML format is valid and all tags are correctly nested and closed.

ORA-22903: MULTISET expression not allowed

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

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

• OceanBase error code: 9717
• SQLSTATE: HY000
• Cause: The CAST operation was performed on something other than a nested table or VARRAY type.

ORA-22922: LOB value does not exist

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

ORA-22928: invalid privilege on directories

• OceanBase error code: 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, and EXECUTE privileges on directories. Do not grant or revoke other privileges.

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

• OceanBase error code: 7412
• SQLSTATE: 42000
• Cause: The MAP or ORDER method is not specified for the comparison of objects.
• Solution:
  1. 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.
  2. If you cannot specify the MAP or ORDER method, you can modify the sorting method. For example, you can use other columns for sorting.

ORA-22990: LOB locators cannot span transactions

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

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

• OceanBase error code: 22998

• SQLSTATE: HY000

• Cause: CLOB or NCLOB data in a fixed-width or variable-width multi-byte character set is passed to an SQL character function that does not support multi-byte LOB data.

• Solution: Use a DBMS_LOB function such as DBMS_LOB.INSTR() and DBMS_LOB.SUBSTR(), or use PL/SQL statements DBMS_LOB.READ/WRITE to access LOB data.

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

• OceanBase error code: 5932

• SQLSTATE: HY000

• Cause: The name string is invalid.

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

• OceanBase error code: 5962

• SQLSTATE: HY000

• Cause: The specified PL/SQL object in a DBMS_PREPROCESSOR subprogram 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.

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

• OceanBase error code: 5961

• SQLSTATE: HY000

• Source: 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.

ORA-24236: source text is empty

• OceanBase error code: 5960

• SQLSTATE: HY000

• Cause: The input source text provided for a DBMS_PREPROCESSOR subprogram was empty.

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

ORA-24334: no descriptor for this position

• OceanBase error code: 5973

• SQLSTATE: HY000

• Cause: The application was trying to get a descriptor of an illegal position from a handle.

• Solution: Check the position number.

ORA-24381: error(s) in array DML

• OceanBase error code: 5883

• SQLSTATE: HY000

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

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

ORA-24761: transaction rolled back

• OceanBase error code: 6002

• SQLSTATE: 40000

• Cause: The transaction is rolled back.

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

• OceanBase error code: 6213

• SQLSTATE: 40000

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

ORA-24761: transaction rolled back: transaction is killed

• OceanBase error code: 6211

• SQLSTATE: 25000

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

ORA-24761: transaction rolled back: partition is frozen

• OceanBase error code: 6214

• SQLSTATE: 25000

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

ORA-24761: transaction rolled back: Transaction exiting

• OceanBase error code: 6223

• SQLSTATE: 25000

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

ORA-24761: transaction rolled back: transaction needs rollback

• OceanBase error code: 6224

• SQLSTATE: 25000

• Cause: The transaction is rolled back as required.

ORA-24761: transaction rolled back: transaction idle timeout

• OceanBase error code: 6278

• SQLSTATE: 25000

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

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

• OceanBase error code: 6234

• SQLSTATE: 25000

• Cause: The transaction is rolled back because the transaction context count reaches the limit.

ORA-25002: cannot create INSTEAD OF triggers on tables

• OceanBase error code: 9572

• SQLSTATE: HY000

• Cause: You cannot create an INSTEAD OF trigger on a table.

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

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

• OceanBase error code: 9571

• SQLSTATE: HY000

• Cause: The WHEN clause is specified in an INSTEAD OF trigger.

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

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

• OceanBase error code: 9663

• SQLSTATE: HY000

• Cause: You cannot create an INSTEAD OF trigger on a read-only view.

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

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

• OceanBase error code: 9569

• SQLSTATE: HY000

• Cause: Nested table clauses are allowed only in INSTEAD OF triggers.

• Solution: Define nested table triggers by using the nested table columns of a view.

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

• OceanBase error code: 9705

• SQLSTATE: HY000

• Cause: The referenced trigger in the FOLLOWS clause was defined on another table.

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

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

• OceanBase error code: 9706

• SQLSTATE: HY000

• Cause: The referenced trigger in the FOLLOWS or PRECEDES clause was either a different type or not a compound trigger.

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

ORA-25023: Cyclic trigger dependency is not allowed

• OceanBase error code: 9707

• SQLSTATE: HY000

• Cause: Cyclic trigger dependency was formed.

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

ORA-25025: cannot specify PRECEDES clause

• OceanBase error code: 9708

• SQLSTATE: HY000

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

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

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

• OceanBase error code: 5795

• SQLSTATE: HY000

• Cause: The operation attempted to perform an insert, update, or delete operation on a table with the DISABLE VALIDATE constraint.

• Solution: Change the status of the constraint.

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

• OceanBase error code: 5800

• SQLSTATE: HY000

• Cause: The specified constraint does not exist in the table.

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

• OceanBase error code: 4157

• SQLSTATE: 22003

• Cause: After conversion, the operand value is greater than the target value.

• Solution: Increase the target value.

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

• OceanBase error code: 5619

• SQLSTATE: HY000

• Cause: A column used to name a join, such as the NATURAL join or a join that uses the USING clause, cannot contain explicit qualifiers.

• Solution: Delete the qualifiers.

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

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

ORA-25405: Transaction state unknown

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

ORA-28001: the password has expired

• OceanBase error code: 4366

• SQLSTATE: HY000

• Cause: The user account has expired, and the password must be changed.

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

ORA-28101: policy already exists

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

ORA-28102: policy does not exist

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

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

• OceanBase error code: 9720
• SQLSTATE: HY000
• Cause: You cannot add strategies to objects owned by the sys tenant.
• Solution: Do not perform this operation.

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

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

• OceanBase error code: 9722
• SQLSTATE: HY000
• Cause: Security-related column strategies cannot be created in an object view.

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

• OceanBase error code: 9723
• SQLSTATE: HY000
• Cause: The input value of the parameter is invalid or missing.

ORA-28107: policy was disabled

• OceanBase error code: 9724
• SQLSTATE: HY000
• Cause: The strategy was disabled.
• Solution: Enable the strategy before using it.

ORA-28108: circular security policies detected

• OceanBase error code: 9725
• SQLSTATE: HY000
• Cause: Strategies on the same object are mutually referenced.

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

• OceanBase error code: 9726
• SQLSTATE: HY000
• Cause: The strategies on an object has exceeded the upper limit.
• Solution: Drop one or more strategies.

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

• OceanBase error code: 9727
• SQLSTATE: HY000
• Cause: The policy function or package is incorrect, has been deleted, or is no longer valid.
• Solution: Check the status of the feature and correct the problem, or create a new strategy with a valid feature.

ORA-28111: insufficient privilege to evaluate policy predicate

• OceanBase error code: 9728
• SQLSTATE: HY000
• Cause: The owner of the strategy function does not have privilege to access the object.

ORA-28112: failed to execute policy function

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

ORA-28113: policy predicate has error

• OceanBase error code: 9730
• SQLSTATE: HY000
• Cause: The strategy predicate has encountered an error.

ORA-28116: insufficient privileges to do direct path access

• OceanBase error code: 9731
• SQLSTATE: HY000
• Cause: You do not have sufficient privileges to access the path directly.

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

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

ORA-28118: policy group already exists

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

ORA-28119: policy group does not exist

• OceanBase error code: 9734
• SQLSTATE: HY000
• Cause: The strategy group does not exist.

ORA-28120: driving context already exists

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

ORA-28121: driving context does not exist

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

ORA-28122: can not update SYS_DEFAULT policy group

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

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

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

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

• OceanBase error code: 9739
• SQLSTATE: HY000
• Cause: The column in sec_relevant_cols cannot be of an object data type.
• Solution: Make sure that none of the columns specified in sec_relevant_cols are of an object data type or XML type.

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

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

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

• OceanBase error code: 9741
• SQLSTATE: HY000
• Cause: The attribute association of the strategy failed.
• Solution: Specify a context attribute of a local application.

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

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

ORA-28115: policy with check option violation

• OceanBase error code: 5789

• SQLSTATE: HY000

• Cause: The security flag written into data is invalid.

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

• OceanBase error code: 9687

• SQLSTATE: HY000

• Cause: The input value for the argument is invalid.

ORA-28264: Client identifier is too long

• OceanBase error code: 9688

• SQLSTATE: HY000

• Cause: The client ID is longer than 64 bytes in length.

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

• OceanBase error code: 9690

• SQLSTATE: HY000

• Cause: A context namespace beginning with 'SYS_' was not allowed.

ORA-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 for a session-based context exceeds the upper limit specified by _session_context_size.

ORA-28268: Invalid NameSpace Value

• OceanBase error code: 9689

• SQLSTATE: HY000

• Cause: The name of the context namespace was invalid.

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

• OceanBase error code: 9679

• SQLSTATE: HY000

• Cause: The count argument specified in the call to the procedure define_array of the dbms_sql package 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.

ORA-29257: host %.*s unknown

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

ORA-29261: bad argument

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

ORA-29295: invalid mime header tag

• OceanBase error code: 5970

• SQLSTATE: HY000

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

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

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

• OceanBase error code: 4702

• SQLSTATE: HY000

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

• Solution: Specify an unused parameter name.

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

• OceanBase error code: 4703

• SQLSTATE: HY000

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

• Solution: Specify a valid plan name.

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

• OceanBase error code: 4704

• SQLSTATE: HY000

• Cause: An invalid value is specified for the plan directive parameter.

• Solution: Specify a value ranging from 0 to 100.

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

• OceanBase error code: 4705

• SQLSTATE: HY000

• Cause: A nonexistent plan directive is specified for UPDATE_PLAN_DIRECTIVE or UPDATE_CDB_PLAN_DIRECTIVE of the DBMS_RESOURCE_MANAGER program package.

• Solution: Specify an existing plan directive.

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

• OceanBase error code: 4706

• SQLSTATE: HY000

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

• Solution: Use another value and try again.

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

• OceanBase error code: 4707

• SQLSTATE: HY000

• Cause: The plan directive name is not supported.

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

• OceanBase error code: 4710

• SQLSTATE: HY000

• Cause: A nonexistent consumer group is specified.

• Solution: Specify an existing consumer group.

ORA-29471: DBMS_SQL access denied

• OceanBase error code: 5856

• SQLSTATE: HY000

• Cause: Access to DBMS_SQL is denied for security considerations.

• Solution: Obtain more information from the alert logs and trace file.

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

• OceanBase error code: 9677

• SQLSTATE: HY000

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

• Solution: Specify a valid security level.