Find Oracle Error Code Ora- and Pl/SQL Tips and Tricks

What is Oracle Error Code and Oracle Error Message ?

For you Oracle Developer, Oracle Programmer and Oracle Professional, should be familiar with this Oracle Error Code Ora-XXXXX and Oracle Error Messages. This Oracle Error Code and Oracle error messages basically generated by Oracle database. The prefix “ORA-” shows that the message was generated by Oracle products. Every oracle error code or messages contains the message statement, a brief explanation of the probable causes, and a recommended action that you can do.

On this OraFind.com you can find the Oracle Error Code or Oracle Error Messages that you got. It is based on Oracle database error messages (Oracle 11g release 1 and some of it Oracle 8i). Please use this information only for personal, informational and non-commercial purposes. If you still don’t have any solution for your problem, you can leave your comment in every Error Code or Error Message that you find at OraFind.com, or for more detailed information please contact Oracle Support Services.

Popularity: 100% [?]

Share This

ORA-01002: fetch out of sequence

Cause : This error means that a fetch has been attempted from a cursor which is no longer valid. Note that a PL/SQL cursor loop implicitly does fetches, and thus may also cause this error. There are a number of possible causes for this error, including:
1) Fetching from a cursor after the last row has been retrieved and the ORA-1403 error returned.
2) If the cursor has been opened with the FOR UPDATE clause, fetching after a COMMIT has been issued will return the error.
3) Rebinding any placeholders in the SQL statement, then issuing a fetch before reexecuting the statement.
Action:
1) Do not issue a fetch statement after the last row has been retrieved -there are no more rows to fetch.
2) Do not issue a COMMIT inside a fetch loop for a cursor that has been opened FOR UPDATE.
3) Reexecute the statement after rebinding, then attempt to fetch again.

Popularity: 58% [?]

Share This

ORA-01001 : invalid cursor

Cause : Either a host language program call specified an invalid cursor or the values of the AREASIZE and MAXOPENCURSORS options in the precompiler command were too small. All cursors must be opened using the OOPEN call before being referenced in any of the following calls: SQL, DESCRIBE, NAME, DEFINE, BIND, EXEC, FETCH, and CLOSE. The Logon Data Area (LDA) must be defined by using OLON or OLOGON. If the LDA is not defined, this message is issued for the following calls: OPEN, COM, CON, ROL, and LOGOFF.
Action: Check the erroneous call statement. Specify a correct LDA area or open the cursor as required. If there is no problem with the cursor, it may be necessary to increase the AREASIZE and MAXOPENCURSORS options before precompiling.

Popularity: 60% [?]

Share This

ORA-01000 : maximum open cursors exceeded

Cause : A host language program attempted to open too many cursors. The initialization parameter OPEN_CURSORS determines the maximum number of cursors per user.
Action : Modify the program to use fewer cursors. If this error occurs often, shut down Oracle, increase the value of OPEN_CURSORS, and then restart Oracle.

Popularity: 62% [?]

Share This

ORA-00999 : invalid view name

Cause : In a CREATE VIEW statement, the view name was missing or invalid.
Action : Enter a valid view name following CREATE VIEW. Valid view names must begin with a letter, consist of only alphanumeric characters and the special characters $, _, and #, be less than or equal to 30 characters, and may not be reserved words. If the view name contains other characters, it must be enclosed in double quotation marks.

Popularity: 58% [?]

Share This

ORA-00998 : must name this expression with a column alias

Cause : An expression or function was used in a CREATE VIEW statement, but no corresponding column name was specified. When expressions or functions are used in a view, all column names for the view must be explicitly specified in the CREATE VIEW statement.
Action : Enter a column name for each column in the view in parentheses after
the view name.

Popularity: 58% [?]

Share This

ORA-00997 : illegal use of LONG datatype

Cause : A value of datatype LONG was used in a function or in a DISTINCT, WHERE, CONNECT BY, GROUP BY, or ORDER BY clause. A LONG value can only be used in a SELECT clause.
Action : Remove the LONG value from the function or clause.

Popularity: 57% [?]

Share This

ORA-00996 : the concatenate operator is ||, not |

Cause : A single bar (|) was interpreted as an attempt to specify concatenation, but the concatenation operator is a double bar (||).
Action : Enter a double bar (||) for concatenation or remove the single bar (|) if concatenation was not intended.

Popularity: 57% [?]

Share This

ORA-00995 : missing or invalid synonym identifier

Cause : In a CREATE or DROP SYNONYM statement, the synonym name was either missing or invalid.
Action : Check syntax and spelling. A valid synonym name must be specified immediately following the keyword SYNONYM in both statements. Valid synonym names must begin with a letter, consist of alphanumeric characters
and the special characters $, _, and #, and be less than or equal to 30 characters.
They may not be reserved words.

Popularity: 59% [?]

Share This

ORA-00994 : missing OPTION keyword

Cause : The keywords WITH GRANT were specified at the end of a GRANT statement without the keyword OPTION.
Action : Change the keywords WITH GRANT to the keywords WITH GRANT OPTION. Then retry the statement.

Popularity: 57% [?]

Share This