Applicability
This topic applies only to OceanBase Database Enterprise Edition. OceanBase Database Community Edition provides only the MySQL mode.
OBE-06500: PL/SQL: storage error
Error code in OceanBase Database: 5842
SQLSTATE: HY000
Cause: The PL program cannot allocate other storage. The program may be out of control.
Solution:
Make sure that the PL program does not use additional memory.
Release unused objects through programming. For example, set them to
NULL.Increase the size of the available shared or process memory space if applicable.
OBE-06501: PL/SQL: program error
Error code in OceanBase Database: 5840
SQLSTATE: HY000
Cause: An internal error occurred. An error was detected in the PL program.
Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.
OBE-06502: PL/SQL: numeric or value error: %.*s
Error code in OceanBase Database: 5677
SQLSTATE: HY000
Cause: An arithmetic, numeric, string, conversion, or constraint error occurred. For example, if you attempt to assign the
NULLvalue to a variable that declares aNOT NULLconstraint, or assign a value greater than99to a variable that declaresNUMBER(2), this error is reported.Solution: Modify the data, the data calculation method, or the data declaration method so that the value does not violate the constraint.
OBE-06504: PL/SQL: Return types of Result Set variables or query do not match
Error code in OceanBase Database: 5841
SQLSTATE: HY000
Cause: The number or type of columns in the query does not match the return types declared by result set variables, or the types declared by two result set variables do not match.
Solution: Modify the program statement or declaration. Identify the query referenced by variables during execution.
OBE-06508: PL/SQL: could not find program unit being called: '%.*s'
Error code in OceanBase Database: 5933
SQLSTATE: HY000
Cause: The program unit is not found.
OBE-06513: PL/SQL: index for PL/SQL table out of range for host language array
- Error code in OceanBase Database: 9750
- SQLSTATE: HY000
- Cause: When you use a PL/SQL table, the index values exceed the value range of the array.
- Solution: Make sure that the values of the index do not exceed the value range of the array.
Note
This error code is introduced since OceanBase Database V4.2.0.
OBE-06519: active autonomous transaction detected and rolled back
Error code in OceanBase Database: 5796
SQLSTATE: HY000
Cause: All active autonomous transactions in an autonomous PL block must be completed (committed or rolled back) before they return from the block. If these transactions are not completed, the active autonomous transactions are implicitly rolled back, thereby inducing this error.
Solution: Make sure that all active autonomous transactions are explicitly specified or rolled back before they return from the autonomous PL block.
OBE-06530: Reference to uninitialized composite
Error code in OceanBase Database: 5837
SQLSTATE: HY000
Cause: An object, large object, or another composite object (such as a nested table or a record) that is not initialized is referenced on the left side.
Solution: Initialize the composite object by using a proper constructor or through global object assignment.
OBE-06531: Reference to uninitialized collection
Error code in OceanBase Database: 5838
SQLSTATE: HY000
Cause: A nested table,
VARRAYelement, orMemberfunction is referenced, which requires an initialized collection, but the collection is not initialized.Solution: Initialize the collection by using an appropriate constructor or through global object assignment.
OBE-06532: Subscript outside of limit
Error code in OceanBase Database: 5843
SQLSTATE: HY000
Cause: The subscript exceeds the upper limit for a
VARRAYarray, or the subscript is a non-positive value of aVARRAYarray or nested table.Solution: Check the program logic and increase the upper limit for a
VARRAYarray if necessary.
OBE-06533: Subscript beyond count
Error code in OceanBase Database: 5828
SQLSTATE: HY000
Cause: The subscript exceeds the maximum length of the
VARRAYor is too large for the nested table.Solution: Check the program logic and perform explicit extension if necessary.
OBE-06535: statement string in EXECUTE IMMEDIATE is NULL or 0 length
Error code in OceanBase Database: 9711
SQLSTATE: HY000
Cause: The program was attempting to use a dynamic statement string that was either NULL or 0 in length.
Solution: Check the program logic and make sure that the dynamic statement string is properly initialized.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-06546: DDL statement is executed in an illegal context
Error code in OceanBase Database: 5981
SQLSTATE: HY000
Cause: A DDL statement is executed dynamically in an illegal PL/SQL context:
Dynamic OPEN cursor for a DDL statement in PL/SQL.
The Bind variable is used in the
USINGclause to immediately execute a DDL statement.The Define variable is used in the
INTOclause to immediately execute a DDL statement.
Solution: Use
EXECUTE IMMEDIATEwithoutUSINGandINTOclauses to execute the DDL statement.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-06547: RETURNING clause must be used with INSERT, UPDATE, or DELETE statements
Error code in OceanBase Database: 9713
SQLSTATE: HY000
Cause:
EXECUTE IMMEDIATEwith aRETURNINGclause is used to execute only dynamicUPDATE,INSERT, orDELETEstatements.Solution: Use the
RETURNINGclause inEXECUTE IMMEDIATEonly for executingINSERT,UPDATE, orDELETEstatements. For other statements, use theUSINGclause instead.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-06548: no more rows needed
Error code in OceanBase Database: 5839
SQLSTATE: HY000
Cause: The caller of the pipelined function does not require the pipelined function to generate more rows.
Solution: Do not handle the
NO_DATA_NEEDEDexception in an exception handling block.
OBE-06553: wrong number or types of arguments in call to '%.*s'
Error code in OceanBase Database: 5343
SQLSTATE: 42000
Cause: SQL statement compilation failed due to the invalid reference of a PL unit.
Solution: If the PLS error message does not provide a solution, try to execute the SQL statement as a top-level call.
Note
The operator must have the required privilege.
OBE-06562: type of out argument must match type of column or bind variable
Error code in OceanBase Database: 9568
SQLSTATE: HY000
Cause: The
LONGtype is specified for thecolumn_value_longanddefine_value_longfunctions, which is not allowed.Solution: Specify supported argument types for the
column_value_longanddefine_value_longfunctions.
OBE-06563: name has too many parts
Error code in OceanBase Database: 9714
SQLSTATE: HY000
Cause:
The name to be resolved was specified as one of the following forms:
A.B.C: The A.B part was resolved to a valid object that did not expose any visible nested procedures, and therefore the C part could not be resolved.
A.B: The A part was resolved to a valid object that did not expose any visible nested procedures, and therefore the B part could not be resolved.
Solution: Specify the valid name of an object without specifying any additional trailing parts.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-06564: object %.*s does not exist
- Error code in OceanBase Database: 9749
- SQLSTATE: HY000
- Cause: The requested object does not exist.
- Solution: Make sure that the specified name of the requested object is correct.
Note
This error code is introduced since OceanBase Database V4.2.0.
OBE-06575: Package or function PRO is in an invalid state
- Error code in OceanBase Database: 5465
- SQLSTATE: 42000
- Cause: The PL/SQL function referenced by the SQL statement is invalid.
- Solution: Check the SQL statement and PL/SQL functions for syntax errors and incorrectly authorized or missing privileges on the referenced object.
Note
This error code is introduced since OceanBase Database V4.1.0.
OBE-06576: not a valid function or procedure name
Error code in OceanBase Database: 5980
SQLSTATE: HY000
Cause: The function (if an
INTOclause was present) or procedure (if the statement did not have anINTOclause) to be called is not found.Solution: Change the statement to call the function or procedure.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-06577: output parameter not a bind variable
Error code in OceanBase Database: 9763
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-07452: specified resource manager plan does not exist in the data dictionary
Error code in OceanBase Database: 4718
SQLSTATE: HY000
Cause: You are attempting to load a nonexistent resource manager plan.
Solution: Use a resource manager plan that exists in the data dictionary.
OBE-08002: sequence is not yet defined in this session
- Error code in OceanBase Database: 9753
- SQLSTATE: HY000
- Cause: The
NEXTVALof the sequence object has not been accessed in the session. - Solution: Access the
NEXTVALof the sequence object in the session before you access theCURRVALof the sequence object.
Note
This error code is introduced since OceanBase Database V4.2.1.
OBE-08004: sequence exceeds %s and cannot be instantiated
Error code in OceanBase Database: 4332
SQLSTATE: HY000
Cause: Instantiating
NEXTVALwould violate eitherMAXVALUEorMINVALUE.Solution: Change the sequence so that new values can be requested.
OBE-08006: specified row no longer exists
Error code in OceanBase Database: 38105
SQLSTATE: HY000
Cause: Other users have deleted this row since the operation begins.
Solution: Retry this operation.
OBE-08102: index key not found
Error code in OceanBase Database: 4380
SQLSTATE: HY000
Cause: This is an internal error code. The indexes may be inconsistent.
Solution: Contact OceanBase Technical Support for troubleshooting.
Note
This error code is introduced since OceanBase Database V4.0.0.
OBE-08177: can't serialize access for this transaction
Error code in OceanBase Database: 6235
SQLSTATE: 25000
Cause: Data modification is performed after a serializable transaction begins.
Solution: Retry this operation in a read/write transaction.
OBE-08186: invalid timestamp
Error code in OceanBase Database: 4344
SQLSTATE: HY000
Cause: The timestamp is invalid. If you are using a flashback query, this error may be caused because OceanBase Database has performed a minor compaction after the specified flashback point in time.
Solution: Enter a valid timestamp.
OBE-08187: snapshot expression not allowed here
Error code in OceanBase Database: 32491
SQLSTATE: HY000
Cause: The specified
AS OFsnapshot expression is not supported here.Solution: Do not use the
AS OFclause.