ORA-01000 to ORA-01499

ORA-01000: maximum open cursors exceeded

• OceanBase error code: 5930

• SQLSTATE: HY000

• Cause: The maximum number of open cursors allowed is exceeded.

ORA-01001: invalid cursor

• OceanBase error code: 5844

• SQLSTATE: HY000

• Cause: The cursor is invalid.

ORA-01002: fetch out of sequence

• OceanBase error code: 5931

• SQLSTATE: HY000

• Cause: The operation attempted to fetch data from an invalid cursor. Possible causes:

  • The data is fetched from the cursor after the retrieval reaches the last line and the ORA-1403 error is returned.

  • The FOR UPDATE clause is used to open the cursor, and then the data is fetched after the COMMIT statement is issued.

  • All placeholders in the SQL statement are re-bound, and the data is fetched before the statement is re-executed.

  Note

  This error can also occur if a PL cursor is circularly and implicitly fetched.

• Solution:

  • Do not issue the FETCH statement after the retrieval reaches the last line.

  • After you use the FOR UPDATE clause to open the cursor, do not fetch the data after you issue the COMMIT statement.

  • Bind placeholders again, execute the SQL statement, and then fetch the data.

ORA-01003: no statement parsed

• OceanBase error code: 9678

• SQLSTATE: HY000

• Cause: DBMS_SQL PARSE attempts to parse a DDL statement.

• Solution: Change the type of the statement to be parsed by DBMS_SQL PARSE to SELECT.

ORA-01006: bind variable does not exist

• OceanBase error code: 5979 and 9685

• SQLSTATE: HY000

• Cause: The bound variable does not exist.

• Solution: Bind a defined variable.

ORA-01007: variable not in select list", 1007, "variable not in select list

• OceanBase error code: 9745
• SQLSTATE: HY000
• Cause: The variable is not in the selection list.
• Solution: Check whether the entered SQL statement is correct.

ORA-01008: not all variables bound

• OceanBase error code: 5857 and 5978

• SQLSTATE: HY000

• Cause: Some variables are not configured.

ORA-01012: not logged on

• OceanBase error code: 5846

• SQLSTATE: HY000

• Cause: You have not logged on.

ORA-01017: invalid username/password; logon denied

• OceanBase error code: 5845

• SQLSTATE: HY000

• Cause: The username or password is invalid, and the logon is denied.

ORA-01031: insufficient privileges

• OceanBase error code: 5360

• SQLSTATE: HY000

• Cause: You do not have the required privileges to perform the database operations.

• Solution: Contact the database administrator or specified security administrator to grant you the required privileges.

ORA-01045: user %.*s lacks CREATE SESSION privilege; logon denied

• OceanBase error code: 5361

• SQLSTATE: HY000

• Cause: You are attempting to connect to the database by using a user ID that does not have the CREATE SESSION privilege.

• Solution: Grant the CREATE SESSION privilege to this user.

ORA-01086: savepoint does not exist

• OceanBase error code: 6242

• SQLSTATE: 42000

• Cause: You are attempting to roll back to an invalid savepoint or a nonexistent savepoint in this session.

• Solution: Roll back to a savepoint from the session where this savepoint is created.

ORA-01092: OceanBase instance terminated. Disconnection forced

• OceanBase error code: 5066

• SQLSTATE: HY000

• Cause: The session to which this process connects is abnormally terminated.

• Solution: Check the alert logs for details. Then, restart the session.

ORA-01400: cannot insert NULL into '(%.*s)'

• OceanBase error code: 4235

• SQLSTATE: 23000

• Cause: You are attempting to insert a NULL value to the listed objects that do not accept the NULL value.

ORA-01400: cannot insert NULL into (%.*s)

• OceanBase error code: 5030

• SQLSTATE: 42000

• Cause: You are attempting to insert a NULL value to existing objects that do not accept the NULL value.

ORA-01402: view WITH CHECK OPTION where-clause violation

• OceanBase error code: 5971

• SQLSTATE: HY000

• Cause: The DML operation performed on the view violated the WITH CHECK OPTION constraint on the view.

• Solution: The data inserted into the view by using the INSERT statement or the data updated by using the UPDATE statement must meet the where condition in the view definition.

ORA-01403: no data found

• OceanBase error code: 4026

• SQLSTATE: 02000

• Cause: No data can be found in the object.

• Solution: If data extraction ends, no data from the object can be found, which is normal. In this case, you do not need to take any action.

ORA-01405: fetched column value is NULL

• OceanBase error code: 5958

• SQLSTATE: HY000

• Cause: In a call to the ANYTYPE SETINFO stored procedure, elem_count was set to NULL.

• Solution: Do not set elem_count to NULL.

ORA-01408: such column list already indexed

• OceanBase error code: 5672

• SQLSTATE: HY000

• Cause: This type of list is already indexed.

ORA-01410: invalid ROWID

• OceanBase error code: 5802

• SQLSTATE: HY000

• Cause: The ROWID is invalid.

ORA-01416: two tables cannot be outer-joined to each other

• OceanBase error code: 5620

• SQLSTATE: HY000

• Cause: Two tables are outer-joined, which is not allowed.

ORA-01418: specified index does not exist

• OceanBase error code: 5209

• SQLSTATE: 42000

• Cause: The specified index does not exist.

ORA-01422: exact fetch returns more than requested number of rows

• OceanBase error code: 5294

• SQLSTATE: 42000

• Cause: The quantity specified in exact fetch is less than the number of returned rows.

• Solution: Rewrite the query or change the number of requested rows.

ORA-01424: missing or illegal character following the escape character

• OceanBase error code: 5665

• SQLSTATE: HY000

• Cause: In LIKE mode, the character following the escape character is missing or is not a percent sign (%) or an underscore (_).

• Solution: Delete the escape character or specify a valid character following the escape character.

ORA-01425: escape character must be character string of length 1

• OceanBase error code: 5666

• SQLSTATE: HY000

• Cause: In LIKE mode, the escape character is not a string whose length is 1.

• Solution: Change it to a string whose length is 1.

ORA-01426: numeric overflow, value larger than specified precision(%ld,%ld) allowed for this column

• OceanBase error code: 5088

• SQLSTATE: 22003

• Cause: The calculation of the value expression causes an overflow or an underflow.

• Solution: Reduce the operands.

ORA-01426: numeric overflow, value(%s) larger than specified precision(%ld,%ld) allowed for this column

• OceanBase error code: 5089

• SQLSTATE: 22003

• Cause: The calculation of the value expression causes an overflow or an underflow.

• Solution: Reduce the operands.

ORA-01426: numeric overflow

• OceanBase error code: 5093

• SQLSTATE: 22003

• Cause: The calculation of the value expression causes an overflow or an underflow.

• Solution: Reduce the operands.

ORA-01427: single-row subquery returns more than one row

• OceanBase error code: 5615

• SQLSTATE: HY000

• Cause: Multiple rows are returned for a single-row subquery.

ORA-01427: single-row subquery returns more than one row

• OceanBase error code: 5153

• SQLSTATE: 21000

• Cause: Multiple rows are returned for a single-row subquery.

ORA-01428: argument '%ld' is out of range

• OceanBase error code: 5674

• SQLSTATE: HY000

• Cause: The argument is out of range.

ORA-01436: CONNECT BY loop in user data

• OceanBase error code: 5764

• SQL STATE: HY000

• Cause: A CONNECT BY loop exists in the user data.

ORA-01437: cannot have join with CONNECT BY

• OceanBase error code: 5765

• SQLSTATE: HY000

• Cause: A join with CONNECT BY is not allowed.

ORA-01438: value larger than specified precision allowed for this column '%.*s' at row %ld

• OceanBase error code: 4224

• SQLSTATE: 22003

• Cause: When a record is inserted or updated, the entered value exceeds the precision of this column.

• Solution: Enter a value within the precision of the numeric column, or use the MODIFY option of the ALTER TABLE command to extend the column precision.

ORA-01441: cannot decrease column length because some value is too big

• OceanBase error code: 5897

• SQLSTATE: HY000

• Cause: The column length cannot be decreased due to big values.

ORA-01442: column to be modified to NOT NULL is already NOT NULL

• OceanBase error code: 5849

• SQLSTATE: HY000

• Cause: The column to be set to NOT NULL already has the NOT NULL attribute.

ORA-01445: cannot select ROWID from, or sample, a join view without a key-preserved table

• OceanBase error code: 5902

• SQLSTATE: HY000

• Cause: You cannot query ROWID from a join view or a sample without key-preserved table.

ORA-01446: cannot select ROWID from, or sample, a view with DISTINCT, GROUP BY, etc

• OceanBase error code: 5903

• SQLSTATE: HY000

• Cause: The ROWID cannot be queried from a view with the DISTINCT or GROUP BY clause.

ORA-01450: maximum key length (%ld) exceeded

• OceanBase error code: 5196

• SQLSTATE: 42000

• Cause: The maximum key length is exceeded.

ORA-01451: column to be modified to NULL cannot be modified to NULL

• OceanBase error code: 5850

• SQLSTATE: HY000

• Cause: The column already allows NULL values, and the NOT NULL constraint is part of the primary key or CHECK constraint.

• Solution: If the primary key or CHECK constraint forcibly enables the NOT NULL constraint, delete the constraint.

ORA-01453: SET TRANSACTION must be first statement of transaction

• OceanBase error code: 5219

• SQLSTATE: 25001

• Cause: You cannot modify the characteristics of an ongoing transaction.

• Solution: Commit or roll back the transaction and then modify it.

ORA-01456: may not perform insert/delete/update operation inside a READ ONLY transaction

• OceanBase error code: 5220 and 6226

• SQLSTATE: 25006

• Cause: You are attempting to perform an INSERT, DELETE, or UPDATE operation in a read-only transaction.

• Solution: Commit or roll back the transaction and then try again.

ORA-01463: cannot modify column datatype with current constraint(s)

• OceanBase error code: 5860

• SQLSTATE: HY000

• Cause: You are attempting to modify the data type of a column with the CHECK constraint. However, the data type of the column constrained by the CHECK constraint can be changed only from CHAR to VARCHAR.

• Solution: Delete the constraint or do not perform the operation.

ORA-01465: invalid hex number

• OceanBase error code: 5342

• SQLSTATE: HY000

• Cause: The hexadecimal number is invalid.

ORA-01466: Unable to read data -* Table definition has changed

• OceanBase error code: 5386
• SQLSTATE: HY000
• Cause: The snapshot is too old to be correctly read or parsed because the table definition has changed.
• Solution: Check whether a column is added or deleted, or whether the data type or length is modified, and perform troubleshooting based on the actual situation.

ORA-01468: a predicate may reference only one outer-joined table

• OceanBase error code: 5621

• SQLSTATE: HY000

• Cause: A predicate can reference only one outer-joined table.

ORA-01476: divisor is equal to zero

• OceanBase error code: 4333

• SQLSTATE: HY000

• Cause: The divisor is 0.

ORA-01481: invalid number format model

• OceanBase error code: 5606

• SQLSTATE: 42000

• Cause: You are attempting to convert a number into a string through TO_CHAR or convert a string into a number through TO_NUMBER by using an invalid number format.

• Solution: For more information, see Number format models in SQL Reference (Oracle Mode) on the official website.

ORA-01481: invalid number format model

• OceanBase error code: 5608

• SQLSTATE: 42000

• Cause: You are attempting to convert a number into a string through TO_CHAR or convert a string into a number through TO_NUMBER by using an invalid number format.

• Solution: For more information, see Number format models in SQL Reference (Oracle Mode) on the official website.

ORA-01482: unsupported character set

• OceanBase error code: 5937

• SQLSTATE: 42000

• Cause: The character set used for the operation is not supported.

• Solution: Use a supported character set.

ORA-01489: result of string concatenation is too long

• OceanBase error code: 5348

• SQLSTATE: HY000

• Cause: The result of string concatenation exceeds the maximum value.

• Solution: Ensure that the result of string concatenation does not exceed the maximum value.