ORA-20000 to ORA-29999

ORA-20000: The stored procedure 'raise_application_error' was called which causes this error to be generated

• Error code in OceanBase Database: 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 '%d' is out of range

• Error code in OceanBase Database: 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

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

• Error code in OceanBase Database: 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-22816: unsupported feature with RETURNING clause

• Error code in OceanBase Database: 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-22928: invalid privilege on directories

• Error code in OceanBase Database: 5374

• SQLSTATE: HY000

• Cause: You attempted 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-22998: CLOB or NCLOB in multibyte character set not supported

• Error code in OceanBase Database: 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'

• Error code in OceanBase Database: 5932

• SQLSTATE: HY000

• Cause: The name string is invalid.

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

ORA-24761: transaction rolled back

• Error code in OceanBase Database: 6002

• SQLSTATE: 40000

• Cause: The transaction is rolled back.

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

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

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

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

ORA-24761: transaction rolled back: transaction needs rollback

• Error code in OceanBase Database: 6224

• SQLSTATE: 25000

• Cause: The transaction is rolled back as required.

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

ORA-25002: cannot create INSTEAD OF triggers on tables

• Error code in OceanBase Database: 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

• Error code in OceanBase Database: 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

• Error code in OceanBase Database: 9663

• SQLSTATE: HY000

• Cause: You attempted to create an INSTEAD OF trigger on a view that is created by using read-only options. You cannot update the view by using an INSTEAD OF trigger.

• Solution: Do not create the trigger.

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

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

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

• Error code in OceanBase Database: 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

• Error code in OceanBase Database: 5800

• SQLSTATE: HY000

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

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

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

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

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

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

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

• Error code in OceanBase Database: 9687

• SQLSTATE: HY000

• Cause: The input value of the parameter is missing or invalid.

• Solution: Change the input value.

ORA-28115: policy with check option violation

• Error code in OceanBase Database: 5789

• SQLSTATE: HY000

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

ORA-28264: Client identifier is too long

• Error code in OceanBase Database: 9688

• SQLSTATE: HY000

• Cause: The length of the client identifier exceeds 64 bytes.

• Workaround: Set a client identifier containing less than 64 bytes.

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

• Error code in OceanBase Database: 9690

• SQLSTATE: HY000

• Cause: A namespace that starts with "SYS_" is not allowed.

• Solution: Use a namespace that does not start with "SYS_".

ORA-28267: Invalid NameSpace Value

• Error code in OceanBase Database: 9689

• SQLSTATE: HY000

• Cause: The context namespace conflicts with the reserved keyword, or security namespaces are not allowed for the context of this type of applications.

• Solution: Use a valid namespace.

ORA-28268: The maximum size specified for the _session_context_size parameter was exceeded.

• Error code in OceanBase Database: 9691

• SQLSTATE: HY000

• Cause: The maximum value specified for the _session_context_size init.ora parameter is exceeded.

• Solution: Change the value of _session_context_size in the configuration file.

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

ORA-29261: bad argument

• Error code in OceanBase Database: 5951

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

• Error code in OceanBase Database: 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

• Error code in OceanBase Database: 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

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

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

• Error code in OceanBase Database: 4706

• SQLSTATE: HY000

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

• Solution: Use another value and try again.

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

• Error code in OceanBase Database: 4707

• SQLSTATE: HY000

• Cause: The plan directive name is not supported.

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

ORA-29471: DBMS_SQL access denied

• Error code in OceanBase Database: 5856

• SQLSTATE: HY000

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

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