9500 to 9999

Last Updated：2026-06-14 03:28:50 Updated

This range indicates procedural language (PL) error codes.

ERROR 9502 (HY000): OUT and IN/OUT modes cannot be used in this context

OceanBase error code: 9502
Cause: The OUT parameter is allowed only when the DML statement of the dynamic statement contains a returning variable and there is no external INTO variable.
Solution: Check whether the usage of the OUT parameter in the dynamic statement complies with the specifications.

ERROR 9503 (HY000): object '%.s' of type %.s not found in schema '%.*s'

OceanBase error code: 9503
Cause: An object of the specified type and name does not exist.
Solution: Use the correct type and object name.

ERROR 9506 (HY000): Only schema-level programs allow %s

OceanBase error code: 9506
Cause: The INVOKER RIGHT clause is only allowed to be defined in a standalone procedure or function.
Solution: Remove the INVOKER RIGHT clause.

ERROR 9507 (HY000): at most one declaration for '%.*s' is permitted

OceanBase error code: 9507
Cause: A duplicate identifier was found in the same namespace.
Solution: Ensure the uniqueness of identifiers in the same namespace.

ERROR 9508 (HY000): duplicate fields in RECORD,TABLE or argument list are not permitted

OceanBase error code: 9508
Cause: The PL has parameters with the same name.
Solution: Parameter names in PL must be unique.

ERROR 9509 (HY000): Pragma AUTONOMOUS_TRANSACTION cannot be specified here

OceanBase error code: 9509
Cause: The autonomous transaction clause is placed in an incorrect location. It can only appear in the first-level block.
Solution: Modify the position of the autonomous transaction clause.

ERROR 9510 (HY000): illegal EXIT/CONTINUE statement; it must appear inside a loop

OceanBase error code: 9510
Error message: The EXIT or CONTINUE statement must be used within a loop body.
Solution: Check whether the EXIT or CONTINUE clause is used correctly.

ERROR 9512 (HY000): EXIT/CONTINUE label '%.*s' must label a LOOP statement

OceanBase error code: 9512
Error message: The target of the EXIT or CONTINUE clause is not a valid label.
Solution: Check whether the target label of the EXIT or CONTINUE clause is valid.

ERROR 9513 (HY000): expression '%.*s' is inappropriate as the left hand side of an assignment statement

OceanBase error code: 9513
Error message: A static cursor cannot be used for assignment.
Solution: Check the validity of the assignment statement.

ERROR 9514 (HY000): a variable declared NOT NULL must have an initialization assignment

OceanBase error code: 9514
Error message: A variable with a NOT NULL constraint is not explicitly initialized.
Solution: Remove the NOT NULL constraint or explicitly initialize the variable.

ERROR 9515 (HY000): Constant declarations should contain initialization assignments

OceanBase error code: 9515
Error message: A constant variable is not explicitly initialized.
Solution: Remove the constant or explicitly initialize the variable.

ERROR 9516 (HY000): Cursor Variables cannot be declared as part of a package

OceanBase error code: 9516
Error message: Cursors are not allowed to be declared within a package.

ERROR 9518 (HY000): value in LIMIT clause: \'%.*s\' use is invalid

OceanBase error code: 9518
Error message: The data type of the expression in the LIMIT clause is incorrect.
Solution: Change the data type to a numeric type.

ERROR 9519 (HY000): expression is of wrong type

OceanBase error code: 9519
Cause: The result type of the expression does not match the expectation.
Solution: Check the result type of the expression.

ERROR 9520 (HY000): cannot compile body of '%.*s' without its specification

OceanBase error code: 9520
Cause: The UDT lacks a SPEC declaration.
Solution: Add a SPEC declaration first.

ERROR 9521 (HY000): subprogram '%.*s' is declared in an object type body and must be defined in the object type specification

OceanBase error code: 9521
Cause: A function definition within an object must be declared in the SPEC first.
Solution: Declare the function in the SPEC.

ERROR 9522 (HY000): subprogram or cursor '%.*s' is declared in an object type specification and must be defined in the object type body

OceanBase error code: 9522
Cause: If a subprogram or cursor is declared in the SPEC of an object type, it must be defined in the BODY.
Solution: Remove the declaration or define it.

ERROR 9523 (HY000): An object type may have only 1 MAP or 1 ORDER method

OceanBase error code: 9523
Cause: An object type can define either one MAP or one ORDER function, but not both.
Solution: Remove the redundant MAP or ORDER function and retain the appropriate one.

ERROR 9524 (HY000): A MAP or ORDER function is required for comparing objects in PL/SQL

OceanBase error code: 9524
Cause: To compare object types in PL, you need to define a MAP or ORDER function.
Solution: Define an appropriate MAP or ORDER comparison function.

ERROR 9525 (HY000): Only a function may be a MAP, ORDER or CONSTRUCTOR method

OceanBase error code: 9525
Cause: MAP, ORDER, or CONSTRUCTOR must be defined as a FUNCTION.
Solution: Modify the definition and recompile.

ERROR 9526 (HY000): identifier '%.*s' too long

OceanBase error code: 9526
Cause: The label name is too long. The maximum length is 128 characters.
Solution: Modify the length.

ERROR 9527 (HY000): a static method cannot be invoked on an instance value

OceanBase error code: 9527
Cause: A static function cannot be called on an instance.
Solution: Modify the calling method to call it using the type name.

ERROR 9528 (HY000):constructor method name must match type name

OceanBase error code: 9528
Cause: The constructor name must match the type name.
Solution: Ensure they are the same.

ERROR 9529 (HY000):previous use of '%.*s' conflicts with this use

OceanBase error code: 9529
Cause: Naming conflict. For example, defining variables of different types, but the variable name is already used elsewhere.
Solution: Ensure the named variable does not duplicate another name.

ERROR 9530 (HY000):the SELF parameter can be declared only as IN or as IN OUT

OceanBase error code: 9530
Cause: The modifier for the SELF parameter must be IN or IN OUT, not other modifiers.
Solution: Modify the modifier to meet the requirement.

ERROR 9531 (HY000): MAP methods must return a scalar type

OceanBase error code: 9531
Cause: A MAP function must return a scalar value, not a complex type.
Solution: Modify the function's return type.

ERROR 9532 (HY000): MAP methods must be declared without any parameters other than (optional) SELF

OceanBase error code: 9532
Cause: A MAP function has exactly one parameter, which is SELF (either explicitly or implicitly defined).
Solution: Remove any extra parameters.

ERROR 9533 (HY000): ORDER methods must return an INTEGER

OceanBase error code: 9533
Cause: An ORDER function must return an integer.
Solution: Modify the function's return type.

ERROR 9534 (HY000): The parameter type in an ORDER method must be the containing object type

OceanBase error code: 9534
Cause: The parameter type of an ORDER function must be the type of its containing object.
Solution: Modify the parameter type.

ERROR 9535 (HY000): Within SQL statements, only equality comparisons of objects are allowed without a map or order function

OceanBase error code: 9535
Cause: In SQL statements, equality comparisons are the only operations supported when no MAP or ORDER function is provided.
Solution: Add a MAP or ORDER function, or perform only equality comparisons.

ERROR 9537 (HY000): The parameters to an ORDER function must have IN mode

OceanBase error code: 9537
Cause: The parameter modifier for the ORDER function must be IN.
Solution: Modify the parameter modifier.

ERROR 9538 (HY000):ORDER methods must be declared with 1 (one) parameter in addition to (optional) SELF

OceanBase error code: 9538
Cause: The ORDER function must be defined with a parameter other than SELF.
Solution: Define an additional parameter of the corresponding type.

ERROR 9539 (HY000): type '%.*s' is malformed because it is a non-REF mutually recursive type

OceanBase error code: 9539
Cause: The types are mutually recursively referenced.
Solution: Resolve the mutual recursion.

ERROR 9540 (HY000):$ERROR: %.*s

OceanBase error code: 9540
Cause: An exception generated by the $ERROR directive. This is an expected exception.
Solution: No action is required.

ERROR 9541 (HY000): RETURN statement in a CONSTRUCTOR cannot include an expression

OceanBase error code: 9541
Cause: The RETURN statement in a CONSTRUCTOR function cannot contain any expressions.
Solution: Remove the expression following RETURN.

ERROR 9542 (HY000): wrong number or types of arguments in call to '%.*s'

OceanBase error code: 9542
Error cause: No suitable function was found when calling the subprocedure. This may be due to an incorrect function name, an incorrect number of parameters, or mismatched parameter types.
Solution: Check the function name, number of parameters, and parameter types. If the issue persists, check the function's access scope.

ERROR 9543 (HY000): '%.*s' must be a type

OceanBase error code: 9543
Error cause: The type modifier in a declaration or expression is not a valid type. For example, %type or %rowtype might be missing.
Solution: Modify the modifier to a valid type.

ERROR 9544 (HY000): too many declarations of '%.*s' match this call

OceanBase error code: 9544
Error cause: Multiple function calls match. It's possible that the called function has multiple matching invocation methods, and none can be matched exactly.
Solution: Check whether the function name and parameter types are correct.

ERROR 9574 (HY000): document is not a stylesheet

Error code in OceanBase Database: 9574
Cause: An attempt was made to use a non-stylesheet document as an XSL stylesheet.
Solution: Check the format and validity of the XSL stylesheet to ensure there are no formatting or parameter errors.

ERROR 9694 (42000): Duplicate condition information item '%s'

OceanBase error code: 9694
Error cause: A duplicate item appears in the condition definition.
Solution: Remove the duplicate item from the condition definition.

Note

This error code is introduced in V4.0.0.

ERROR 9695 (02000): Unhandled user-defined not found condition

OceanBase error code: 9695
Error cause: A user-defined condition that was not found was used.
Solution: Do not use undefined conditions.

Note

This error code is introduced in V4.0.0.

ERROR 9743(HY000): Can't drop or alter a procedure/function from within another stored routine.Can't drop or alter a '%s' from within another stored routine

OceanBase error code: 9743
Compatible MySQL error code: 1357

Note

This error code is introduced in V4.1.0.

ERROR 9747 (HY000): malformed ps packet

OceanBase error code: 9747
Cause: The format of the prepared statement packet sent by the client is incorrect.
Solution: Check whether the client and server versions are compatible and ensure that they match.

Note

This error code is introduced in V4.2.0.

ERROR 9749 (HY000): object does not exist

OceanBase error code: 9749
Cause: The requested object does not exist.
Solution: Check whether the name of the requested object is correct and confirm whether the object can be found.

Note

This error code is introduced in V4.2.0.

ERROR 9750 (HY000): PL/SQL: index for PL/SQL table out of range for host language array

OceanBase error code: 9750
Cause: When using a PL/SQL table, the index exceeds the range of the array.
Solution: Ensure that the index value does not exceed the array range.

Note

This error code is introduced in V4.2.0.

ERROR 9754 (HY000): debug_session_id = %u does not exist

OceanBase error code: 9754
Error cause: The debug_session_id does not exist.
Solution: Check whether the session ID exists.

Note

This error code is introduced in V4.2.2.

ERROR 9760 (HY000): cannot fast refresh materialized view %s: %s

OceanBase error code: 9760
Error cause: The basic requirements for creating an incremental refresh materialized view are not met. For example:
- The base table in the definition of the incremental refresh materialized view does not have a materialized view log (mlog) table created.
- The definition of the incremental refresh materialized view does not support set operators.
- The columns used in the incremental refresh materialized view need to be maintained in the base table's mlog.
Solution: Check whether the definition for creating the incremental refresh materialized view meets the basic requirements for incremental refresh. For more information about the basic requirements, see Refresh a materialized view.

Note

This error code is introduced in V4.3.0.

ERROR 9762 (42000): Loading local data is disabled; this must be enabled on both the client and server sides

OceanBase error code: 9762
Compatible MySQL error code: 3948
Error cause: Local Data import failed.
Solution: To use the LOAD DATA LOCAL feature, ensure that:
- OBClient version is later than or equal to 2.2.4.
- ODP version is later than or equal to 3.2.4 (this requirement does not apply for direct connection to OBServer).
- OBJDBC version is later than or equal to 2.4.8 (if using Java + OBJDBC).
  
  Alternatively, you can directly use native MySQL or MariaDB clients, which have no specific version requirements.
  
  Note
  
  When connecting to a database with a MySQL/MariaDB client, add the command-line parameter --local-infile.
  
  If the versions are correct, set the local_infile variable value to ON:
  - Enable variables.
```
set @@local_infile=1;
```
  - Check variables.
```
show variables like 'local_infile';
```

Note

This error code is introduced in V4.3.0.

ERROR 9765 (HY000): object '%.*s' must be of type function or array to be used this way

OceanBase error code: 9765
Cause: The object '%.*s' must be of the function or array type to be used in this way.
Solution: Check the object's type and adjust it as necessary.

Note

This error code is introduced in V4.3.0.

ERROR 9800 (HY000): To be compatible with MySQL, if an exception occurs when compiling an OB PL object (such as the object does not exist or a parameter mismatch), the relevant statement will be converted to a statement that throws an exception, and compiled object will be evicted by any schema change which may cause performance problems. User should create or redefine the pl object of the problem indicated in the warning. Problem object name: '%.*s'

Error code in OceanBase Database: 9800
Cause:

A MySQL compatibility exception occurred during PL object compilation. This may be caused by one of the following:
- The referenced object does not exist.
- Parameter mismatch.
- Type incompatibility.
Solution: Fix the references, parameters, types, and other issues in the PL object, and then recompile the PL object to prevent performance issues caused by frequent recompilation.

ERROR 9808 (HY000): Table type is not valid, the definition of materialized view can only reference user tables or other materialized views

Error code in OceanBase Database: 9808
Cause: The table type referenced in the materialized view definition is invalid.
Solution: Check the object types referenced in the materialized view definition. A materialized view definition can reference only user tables or other materialized views.

ERROR 9809 (HY000): Base tables are altered during the creation or complete refresh of materialized views, please try again when base tables have no ongoing DDL operations

Error code in OceanBase Database: 9809
Cause: DDL operations are in progress on base tables during the creation or complete refresh of a materialized view.
Solution: Check whether DDL operations are in progress on the base tables of the materialized view.

ERROR 9810 (HY000): Materialized view %s.%s has invalid dependency info, please perform a complete refresh to recover

Error code in OceanBase Database: 9810
Cause: The dependency information of materialized view %s is invalid.
Solution: Perform a complete refresh of the materialized view.