Oracle Error Messages

Error: ORA-00936: missing expression
Cause: You tried to execute an SQL statement but you omitted a part of the syntax.
Action: The options to resolve this Oracle error are:
.This error most commonly occurs when you try to execute a SELECT statement and forget to the list of the columns in the SELECT statement.

Error: ORA-00937: not a single-group group function
Cause: You tried to execute a SELECT statement that included a GROUP BY function (ie: MIN, MAX, SUM, COUNT), but was missing the GROUP BY clause.
Action: The options to resolve this Oracle error are:
.Rewrite the SELECT statement so that the column or expression listed in the SELECT list is also found in the GROUP BY clause.
.Remove the GROUP BY function (ie: MIN, MAX, SUM, COUNT) from the SELECT statement.
.Remove the expression from the SELECT list that was not in the GROUP BY clause.

Error: ORA-00938: not enough arguments for function
Cause: You tried to call an Oracle function, but you supplied too few arguments for the function.
Action: The options to resolve this Oracle error are:
.This error can be corrected by providing the correct number of arguments when calling the Oracle function.

Error: ORA-00939: too many arguments for function
Cause: You tried to call an Oracle function, but you supplied too many arguments for the function.
Action: The options to resolve this Oracle error are:
.This error can be corrected by providing the correct number of arguments when calling the Oracle function.

Error: ORA-00942: table or view does not exist
Cause: You tried to execute an SQL statement that references a table or view that either does not exist, that you do not have access to, or that belongs to another schema and you didn't reference the table by the schema name.
Action: The options to resolve this Oracle error are:
.If this error occurred because the table or view does not exist, you will need to create the table or view.
.If this error occurred because you do not have access to the table or view, you will need to have the owner of the table/view, or a DBA grant you the appropriate privileges to this object.
.If this error occurred because the table/view belongs to another schema and you didn't reference the table by the schema name, you will need to rewrite your SQL to include the schema name.

Error: ORA-00946: missing TO keyword
Cause: You tried to execute a GRANT command and missed the TO keyword.
Action: The options to resolve this Oracle error are:
.Try adding the missing TO keyword and re-execute the command.

Error: ORA-00947: not enough values
Cause: You tried to execute an SQL statement that required two equal sets of values, but the second set contains fewer values than the first set.
Action: The options to resolve this Oracle error are:
.This error can occur when you are performing an INSERT and the values entered are less in number than the columns that you are inserting into.
.This error can also occur when you perform a sub-select in a WHERE clause or HAVING clause but the sub-select returns too few columns.

Error: ORA-00948: ALTER CLUSTER statement no longer supported
Cause: You tried to execute an ALTER CLUSTER statement, but this statement is no longer supported.
Action: The options to resolve this Oracle error are:
.Try adding your cluster from an existing table.

Error: ORA-00955: name is already used by an existing object
Cause: You tried to create a table, view, index, synonym or other object with a name that is already in use.
Action: The options to resolve this Oracle error are:
.Rename your object that you are trying to create so that it is unique.
.Drop the existing object and create the new object.

Error: ORA-00957: duplicate column name
Cause: You tried to execute either a CREATE TABLE or INSERT statement where the same column name was listed more than once.
Or you tried to execute an UPDATE statement where the same column name was listed more than once in the SET clause.
Action: The options to resolve this Oracle error are:
.If this error occurred during a CREATE TABLE, correct the statement so that each column listed in the CREATE TABLE statement is unique.
.If this error occurred during an INSERT statement, correct the statement so that each column listed is unique.
.If this error occurred during an UPDATE statement, correct the statement so that each column listed in the SET clause is unique.

Error: ORA-00960: ambiguous column naming in select list
Cause: You tried to execute a SELECT statement where a column with the same name is listed in the SELECT list and then ambiguously defined within the ORDER BY clause.
Action: The options to resolve this Oracle error are:
.Try prefixing the column that is ambiguously defined in the ORDER BY clause with the table name.

Error: ORA-00962: too many group-by or order-by expressions
Cause: You tried to execute an SQL statement that contained more than 255 Group By or Order By expressions.
Action: The options to resolve this Oracle error are:
.Re-write your SQL statement so that there are no more than 255 Group By or Order By expressions.

Error: ORA-00971: missing SET keyword
Cause: You tried to execute an UPDATE statement, but you missed the SET keyword.
Action: The options to resolve this Oracle error are:
.Re-write your UPDATE statement to include the SET clause.

Error: ORA-00972: identifier is too long
Cause: You tried to reference a table, cluster, view, index, synonym, tablespace, or username with a value that was longer than 30 characters.
Action: The options to resolve this Oracle error are:
.Names for tables, clusters, views, indexes, synonyms, tablespaces, and usernames must be 30 characters or less. You must shorten the name to no more than 30 characters for these objects.

Error: ORA-00975: date + date not allowed
Cause: You tried to add two dates together. This is not allowed. You can only add numeric values to dates.
Action: The options to resolve this Oracle error are:
.Re-write your expression so that a numeric value is added to the date.

Error: ORA-00979: not a GROUP BY expression
Cause: You tried to execute a SELECT statement that included a GROUP BY function (ie: MIN, MAX, SUM, COUNT) and an expression in the SELECT list that was not in the GROUP BY clause.
Action: The options to resolve this Oracle error are:
.Rewrite the SELECT statement so that the column or expression listed in the SELECT list is also found in the GROUP BY clause.
.Remove the GROUP BY function (ie: MIN, MAX, SUM, COUNT) from the SELECT statement.
.Remove the expression from the SELECT list that was not in the GROUP BY clause.

Error: ORA-00980: synonym translation is no longer valid
Cause: You tried to reference a synonym that no longer exists.
Action: The options to resolve this Oracle error are:
.Reference the object directly (include schema name, if appropriate).
.Re-create the synonym.

Error: ORA-00984: column not allowed here
Cause: You tried to execute an SQL statement that included a column name where it was not permitted.
Action: The options to resolve this Oracle error are:
.This error most commonly occurs when you try to include a column name in the VALUES clause of an INSERT statement.

Error: ORA-00985: invalid program name
Cause: You tried to execute an operation that probably contained a syntax error.
Action: The options to resolve this Oracle error are:
.You need to correct the syntax error and re-execute the operation.

Error: ORA-00995: missing or invalid synonym identifier
Cause: You tried to CREATE or DROP a synonym, but the name of the synonym that you used was either missing or invalid.
Action: The options to resolve this Oracle error are:
.Correct the name of the synonym.

Error: ORA-01000: maximum open cursors exceeded
Cause: You tried to open too many cursors at once. Each user is restricted to the number of cursors open based on the OPEN_CURSORS parameter in the initialization file.
Action: The options to resolve this Oracle error are:
.Try to close cursors that you are no longer using before opening new cursors.
.You may need to shut down Oracle, increase the OPEN_CURSORS parameter in the initialization file, and restart Oracle.

Error: ORA-01001: invalid cursor
Cause: You tried to reference a cursor that does not yet exist. This may have happened because:
.You've executed a FETCH cursor before OPENing the cursor.
.You've executed a CLOSE cursor before OPENing the cursor.
.You've executed a FETCH cursor after CLOSING the cursor.

Action: The options to resolve this Oracle error are:
.Make sure you haven't CLOSEd the cursor and are still referencing it in your code.
.Make sure you've OPENed the cursor before calling a FETCH cursor or CLOSE cursor.
.If everything else is fine, you may need to increase the AREASIZE and MAXOPENCURSORS options.

Error: ORA-01002: fetch out of sequence
Cause: You tried to perform a FETCH at a time when it is not allowed.
Action: The options to resolve this Oracle error are:
.This error may occur if you perform a FETCH on an active cursor after all records have been fetched.
.This error may also occur if you perform a FETCH on a SELECT FOR UPDATE after a COMMIT has been issued.

Error: ORA-01004: default username feature not supported; logon denied
Cause: You tried to perform an automatic logon to Oracle, but your system does not support this.
Action: The options to resolve this Oracle error are:
.Try logging on again by providing a username and password.

Error: ORA-01005: null password given; logon denied
Cause: You tried to log onto Oracle, but provided an invalid password.
Action: The options to resolve this Oracle error are:
.Try logging on again, but provide a valid password.