Oracle Error Messages

Error: ORA-01653: unable to extend table name.name by num in tablespace name
Cause: You tried to allocate an extent for a table segment in the specified tablespace.
Action: The options to resolve this Oracle error are:
.Try using the ALTER TABLESPACE ADD DATAFILE command to add file(s) to the tablespace.

Error: ORA-01700: duplicate username in list
Cause: You tried to execute a GRANT or REVOKE statement and listed the same username more than once.
Action: The options to resolve this Oracle error are:
.Remove the duplicate username from the grant or revoke statement and re-execute the command.

Error: ORA-01704: string literal too long
Cause: You tried to reference a quoted string that was longer than 2000 characters.
Action: The options to resolve this Oracle error are:
.Try reducing the size of the quoted string to be no more than 2000 characters.

Error: ORA-01710: missing OF keyword
Cause: You tried to execute a SELECT FOR UPDATE statement, but missed the OF keyword.
Action: The options to resolve this Oracle error are:
.Re-write the SELECT FOR UPDATE statement

Error: ORA-01711: duplicate privilege listed
Cause: You tried to execute a GRANT or REVOKE statement and listed the same privilege more than once.
Action: The options to resolve this Oracle error are:
.Remove the duplicate privilege from the grant or revoke statement and re-execute the command.

Error: ORA-01719: outer join operator (+) not allowed in operand of OR or IN
Cause: You tried to perform an outer join when using an OR Condition.
Action: The options to resolve this Oracle error are:
.If you've tried to use the OR Condition with an outer join, you will need to re-write your SQL. You can try using a UNION ALL query to achieve the same results.

Error: ORA-01722: invalid number
Cause: You executed an SQL statement that tried to convert a string to a number, but it was unsuccessful.
Action: The options to resolve this Oracle error are:
.Only numeric fields or character fields that contain numeric values can be used in arithmetic operations. Make sure that all expressions evaluate to numbers.
.If you are adding or subtracting from dates, make sure that you added/substracted a numeric value from the date.

Error: ORA-01723: zero-length columns are not allowed
Cause: You tried to create a table, but you specified a column as either CHAR(0) or VARCHAR2(0).
Action: The options to resolve this Oracle error are:
.Try modifying your CREATE TABLE statement so that the VARCHAR2 and CHAR columns are at least 1 character in length.

Error: ORA-01724: floating point precision is out of range 1 to 126
Cause: You tried to specify a FLOAT datatype, but you did not specify a precision value between 1 and 126.
Action: The options to resolve this Oracle error are:
.Try modifying your FLOAT datatype so that precision is between 1 and 126.

Error: ORA-01727: numeric precision specifier is out of range 1 to 38
Cause: You tried to specify a NUMERIC datatype, but you did not specify a precision value between 1 and 38.
Action: The options to resolve this Oracle error are:
.Try modifying your NUMERIC datatype so that precision is between 1 and 38. If you do not specify a precision, Oracle assumes a precision of 22.

Error: ORA-01728: numeric scale specifier is out of range -84 to 127
Cause: You tried to specify a NUMERIC datatype, but you did not specify a scale value between -84 and 127.
Action: The options to resolve this Oracle error are:
.Try modifying your NUMERIC datatype so that scale is between -84 and 127. If you do not specify a scale, Oracle assumes a scale of 0 (ie: 0 decimal places).

Error: ORA-01747: invalid user.table.column, table.column, or columns specification
Cause: You tried to reference a column name, but the column name used is a reserved word in Oracle.
Action: The options to resolve this Oracle error are:
.Try redefining your table so that none of your column names are reserved words.
.Try enclosing the reserved word in double quotes.

Error: ORA-01756: quoted string not properly terminated
Cause: You tried to execute a statement that contained a string that was not surrounded by two single quotes. One of the quotes was entered without the second accompanying quote.
Action: The options to resolve this Oracle error are:
.Rewrite the statement so that the string is surrounded by two single quotes.

Error: ORA-01775: looping chain of synonyms
Cause: You created a series of synonyms that resulted in a circular reference.
Action: The options to resolve this Oracle error are:
.Correct the synonyms so that the circular reference is removed.

Error: ORA-01779: cannot modify a column which maps to a non-key-preserved table
Cause: You tried to INSERT or UPDATE columns in a join view which map to a non-key-preserved table.
Action: The options to resolve this Oracle error are:
.Try updating the tables directly.

Error: ORA-01785: ORDER BY item must be the number of a SELECT-list expression
Cause: You tried to execute a SELECT statement that included an ORDER BY clause that referenced a column number that did not correspond to a valid column in your SELECT list.
Action: The options to resolve this Oracle error are:
.Rewrite the SELECT statement so that the ORDER BY clause references valid column numbers from your SELECT list. Remember that the first item in your SELECT list is column 1, the second is column 2, and so on.

Error: ORA-01789: query block has incorrect number of result columns
Cause: You tried to execute a SELECT statement (probably a UNION or a UNION ALL), and all of the queries did not contain the same number of result columns.
Action: The options to resolve this Oracle error are:
.Re-write the SELECT statement so that each query contains the same number of result columns.

Error: ORA-01790: expression must have same datatype as corresponding expression
Cause: You tried to execute a SELECT statement (probably a UNION or a UNION ALL), and all of the queries did not contain matching data types in the result columns.
Action: The options to resolve this Oracle error are:
.Re-write the SELECT statement so that each matching column is the same data type.

Error: ORA-01810: format code appears twice
Cause: You tried to use the to_date function in a query, but you used a format code twice in the date format.
Action: The options to resolve this Oracle error are:
.Re-write the to_date function so that you only use each format code once.

Error: ORA-01818: HH24 precludes use of meridian indicator
Cause: You tried to reference a date value using both the 24 hour indicator (hh24) and the meridian indicator (AM or PM).
Action: The options to resolve this Oracle error are:
.Correct the date by using either the 24 hour indicator (hh24) or the meridian indicator (AM or PM).

Error: ORA-01820: format code cannot appear in date input format
Cause: You tried to enter a date value, but you used a date format that is not valid.
Action: The options to resolve this Oracle error are:
.Check the date formats recognized by the to_date function. Correct the format and retry.

Error: ORA-01821: date format not recognized
Cause: You tried to enter a date value, but you used a date format that is not supported by Oracle.
Action: The options to resolve this Oracle error are:
.Check the date formats recognized by the to_date function. Correct the format and retry.

Error: ORA-01830: date format picture ends before converting entire input string
Cause: You tried to enter a date value, but the date entered did not match the date format.
Action: The options to resolve this Oracle error are:
.This error can occur when you try to enter a date value without using the to_date function.
.In Oracle, the default date format is generally DD-MON-YYYY. If you try to enter a date value that does not comply with this format, you need to use the to_date function.

Error: ORA-01839: date not valid for month specified
Cause: You tried to enter a date value, but you specified an invalid day value.
Action: The options to resolve this Oracle error are:
.Check your DD value (ie: day of the month). This value must be between 1 and the number of days in the month.

Error: ORA-01843: not a valid month
Cause: You entered a date, but the month portion of the date was not a valid month.
Action: The options to resolve this Oracle error are:
.Re-enter the date value using either a MONTH format mask. Valid values are:
January, February, March, April, May, June, July, August, September, October, November, December.

Or you could use the MON format mask. Valid values are:

Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec.

.If all else fails, you may want to consider using the to_date function and specifying the date format mask.