Oracle Error Messages

Error: ORA-01234: cannot end backup of file name - file is in use or recovery
Cause: You tried to end an online backup of a file, but the file is being used.
Action: The options to resolve this Oracle error are:
.If there is an instance of Oracle running that has the file open, you can try ending the online backup by executing the ALTER TABLESPACE command.
.Otherwise, if a recovery or rename operation is active on this file, you'll have to wait until these operations have been completed. Then you can try again.

Error: ORA-01400: cannot insert NULL into ("SCHEMA"."TABLE_NAME"."COLUMN_NAME")
Cause: You tried to insert a NULL value into a column that does not accept NULL values.
Action: The options to resolve this Oracle error are:
.Correct your INSERT statement so that you do not insert a NULL value into a column that is defined as NOT NULL.

Error: ORA-01401: inserted value too large for column
Cause: You tried to insert a value into a column that exceeds the maximum width for the column.
Action: The options to resolve this Oracle error are:
.Correct your SQL to truncate the value so that it fits within the field. You can always try the substr function to truncate the value.
.Modify your table definition to allow for a larger value in a field. This can be done with an ALTER TABLE command.

Error: ORA-01402: view WITH CHECK OPTION where-clause violation
Cause: You tried to INSERT or UPDATE a record in a view that contained a WITH CHECK OPTION. The resulting INSERT or UPDATE violates the WHERE clause of the view.
Action: The options to resolve this Oracle error are:
.Try viewing the source code for the view, including the WHERE clause. You can then try to correct your original SQL statement.
.If it is necessary to perform your original INSERT or UPDATE, try re-writing your SQL statement to access the underlying tables directly instead of using the view.

Error: ORA-01403: no data found
Cause: You tried one of the following:
.You executed a SELECT INTO statement and no rows were returned.
.You referenced an uninitialized row in a table.
.You read past the end of file with the UTL_FILE package.

Action: The options to resolve this Oracle error are:
.Terminate processing of the data.

Error: ORA-01404: ALTER COLUMN will make a concatenated index too large
Cause: You tried to increase the length of a column that is used in an index. This made the concatenated index larger than its maximum allowed size of 255.
The size of the index is calculated as follows:

.Date fields are a length of 7.
.Character fields are their defined length.
.Numeric fields are a length of 22.
The total index length is calculated as the sum of the individual fields as defined above + the number of columns in the index.

Action: The options to resolve this Oracle error are:
.You can drop the index and then increase the length of the column. The only problem with this method is that you will no longer be able to re-create your index.

Error: ORA-01405: fetched column value is NULL
Cause: You tried to execute a FETCH, but the INTO clause returned a NULL value.
Action: The options to resolve this Oracle error are:
.Try using the NVL function to substitutes a value when a null value is encountered.
.Try re-writing your cursor so that no NULL values are returned.

Error: ORA-01406: fetched column value was truncated
Cause: In a host language program, a FETCH was forced to truncate a column value.
Action: The options to resolve this Oracle error are:
.Try modifying the program to store a larger buffer value.

Error: ORA-01407: cannot update ("SCHEMA"."TABLE_NAME"."COLUMN_NAME") to NULL
Cause: You tried to update a column to a NULL value but the column will not accept NULL values.
Action: The options to resolve this Oracle error are:
.Correct your UPDATE statement so that you do not UPDATE a column with a NULL value when the column is defined as NOT NULL.

Error: ORA-01408: such column list already indexed
Cause: You tried to create an index on a set of columns in a table, but you've already indexed this set of columns.
Action: The options to resolve this Oracle error are:
.Correct your CREATE INDEX statement to reference a set of columns that have not already been indexed.

Error: ORA-01416: two tables cannot be outer-joined to each other
Cause: You tried to join two tables, but you performed an outer join on both tables to each other. This has created a circular outer join between the two tables.
Action: The options to resolve this Oracle error are:
.Correct your SQL so that you are not outer joining both tables to each other. You can only perform an outer join one way.

Error: ORA-01417: a table may be outer joined to at most one other table
Cause: You tried to perform an outer join to the same table from more than one other table.
Action: The options to resolve this Oracle error are:
.Correct your SQL so that you are only performing an outer join to the same table from only one other table.

Error: ORA-01418: specified index does not exist
Cause: You have referenced an index that does not exist in an ALTER INDEX, DROP INDEX, or VALIDATE INDEX command.
Action: The options to resolve this Oracle error are:
.Make sure that your index exists before referencing it in an ALTER INDEX, DROP INDEX, or VALIDATE INDEX command.
You can list all of the indexes that exist by querying the ALL_INDEXES Oracle system table:

Error: ORA-01422: exact fetch returns more than requested number of rows
Cause: You tried to execute a SELECT INTO statement and more than one row was returned.
Action: The options to resolve this Oracle error are:
.Rewrite your SELECT INTO statement so that only one row is returned.
.Replace your SELECT INTO statement with a cursor.

Error: ORA-01423: error encountered while checking for extra rows in exact fetch
Cause: You tried to execute an exact fetch and an error was encountered.
Action: The options to resolve this Oracle error are:
.This error message is always accompanied by a second error message that is more descriptive. Correct the error based on the second error message.

Error: ORA-01424: missing or illegal character following the escape character
Cause: You tried to execute a LIKE condition using an escape character, but you the character following the escape character was not % or _.
Action: The options to resolve this Oracle error are:
.Try modifying your LIKE condition to use % or _ as the character that follows the escape character.

Error: ORA-01425: escape character must be character string of length 1
Cause: You tried to execute a LIKE condition using an escape character, but you tried to define the escape character as a string longer than 1 character.
Action: The options to resolve this Oracle error are:
.Try modifying your LIKE condition to use an escape character that is one character long.

Error: ORA-01426: numeric overflow
Cause: You tried to evaluate an expression that resulted in a numeric overflow (or underflow).
Action: The options to resolve this Oracle error are:
.Re-write your expression using fewer operands.
.Make sure that your expression does not evaluate to infinity.

Error: ORA-01427: single-row subquery returns more than one row
Cause: You tried to execute an SQL statement that contained a subquery that returns more than one row.
Action: The options to resolve this Oracle error are:
.Rewrite your query so that the subquery only returns one row.
.Change your query to use one of the following functions against your subquery results:

Error: ORA-01428: argument num is out of range
Cause: You tried to execute a mathematical function but the parameter passed into the function was not a valid value.
Action: The options to resolve this Oracle error are:
.Re-write your function parameters using values that are valid for the function.

Error: ORA-01429: Index-Organized Table: no data segment to store overflow row-pieces
Cause: There was no data segment defined to store the overflow.
Action: The options to resolve this Oracle error are:
.Define a data segment and retry the operation.

Error: ORA-01430: column being added already exists in table
Cause: You tried to add a column to a table, but the column name already exists in that table.
Action: The options to resolve this Oracle error are:
.Rewrite your ALTER TABLE command to create a column with a unique name. Each column name must be unique within a table.

Error: ORA-01432: public synonym to be dropped does not exist
Cause: You tried to drop a public synonym that does not exist.
Action: The options to resolve this Oracle error are:
.Check to make sure that you specified the public synonym name correctly.
.Your synonym may be a private synonym, not a public synonym.

Error: ORA-01433: synonym to be created is already defined
Cause: You tried to create a synonym whose name is the same as an existing synonym, table, view, or cluster.
Action: The options to resolve this Oracle error are:
.Select a name that has not already been used by a synonym, table, view, or cluster and then rerun your CREATE SYNONYM command with this new name.

Error: ORA-01434: private synonym to be dropped does not exist
Cause: You tried to drop a private synonym that does not exist.
Action: The options to resolve this Oracle error are:
.Check to make sure that you specified the private synonym name correctly.
.Your synonym may be a public synonym, not a private synonym.