ORA-00939: too many arguments for function
Cause: The function was referenced with too many arguments
Action: Check the function syntax and specify only the required number of arguments
Category Archives: ORA Database Error Messages
ORA-00938: not enough arguments for function
ORA-00938: not enough arguments for function
Cause: The function was referenced with too few arguments
Action: Check the function syntax and specify the required number of arguments
ORA-00937: not a single-group group function
ORA-00937: not a single-group group function
Cause: A SELECT list cannot include both a group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, and an individual column expression, unless the individual column expression is included in a GROUP BY clause
Action: Drop either the group function or the individual column expression from the SELECT list or add a GROUP BY clause that includes all individual column expressions listed
ORA-00936: missing expression
ORA-00936: missing expression
Cause: A required part of a clause or expression has been omitted. For example, a SELECT statement may have been entered without a list of columns or expressions or with an incomplete expression. This message is also issued in cases where a reserved word is misused, as in SELECT TABLE
Action: Check the statement syntax and specify the missing component
ORA-00935: group function is nested too deeply
ORA-00935: group function is nested too deeply
Cause: This is an internal error message not usually issued
Action: Contact Oracle Support Services
ORA-00934: group function is not allowed here
ORA-00934: group function is not allowed here
Cause: One of the group functions, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, was used in a WHERE or GROUP BY clause
Action: Remove the group function from the WHERE or GROUP BY clause. The desired result may be achieved by including the function in a subquery or HAVING clause
ORA-00933: SQL command not properly ended
ORA-00933: SQL command not properly ended
Cause: The SQL statement ends with an inappropriate clause. For example, an ORDER BY clause may have been included in a CREATE VIEW or INSERT statement. ORDER BY cannot be used to create an ordered view or to insert in a certain order
Action: Correct the syntax by removing the inappropriate clauses. It may be possible to duplicate the removed clause with another SQL statement. For example, to order the rows of a view, do so when querying the view and not when creating it. This error can also occur in SQL*Forms applications if a continuation line is indented. Check for indented lines and delete these spaces
ORA-00932: inconsistent datatypes: expected string got string
ORA-00932: inconsistent datatypes: expected string got string
Cause: One of the following: An attempt was made to perform an operation on incompatible datatypes. For example, adding a character field to a date field (dates may only be added to numeric fields) or concatenating a character field with a long field. An attempt was made to perform an operation on a database object (such as a table or view) that is not intended for normal use. For example, system tables cannot be modified by a user. Note that on rare occasions this error occurs because a misspelled object name matched a restricted object’s name. An attempt was made to use an undocumented view
Action: If the cause is different datatypes, then use consistent datatypes. For example, convert the character field to a numeric field with the TO_NUMBER function before adding it to the date field. Functions may not be used with long fields. an object not intended for normal use, then do not access the restricted object
ORA-00931: missing identifier
ORA-00931: missing identifier
Cause: The specified string does not contain an identifier
Action: Correct the string argument
ORA-00930: missing asterisk
ORA-00930: missing asterisk
Cause: This is an internal error message not usually issued
Action: Contact Oracle Support Services