All posts by mpbod

ORA-00921: unexpected end of SQL command

ORA-00921: unexpected end of SQL command

ORA-00921: unexpected end of SQL command
Cause: The SQL command was not complete. Part of a valid command was entered, but at least one major component was omitted
Action: Correct the syntax

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00920: invalid relational operator

ORA-00920: invalid relational operator

ORA-00920: invalid relational operator
Cause: A search condition was entered with an invalid or missing relational operator
Action: Include a valid relational operator such as =, !=, ^=, <>, >, <, >=, <=, ALL, ANY, [NOT] BETWEEN, EXISTS, [NOT] IN, IS [NOT] NULL, or [NOT] LIKE in the condition

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00919: invalid function

ORA-00919: invalid function

ORA-00919: invalid function
Cause: An entry was formatted like a function call, but it is not recognizable as an Oracle function
Action: Correct the syntax

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00918: column ambiguously defined

ORA-00918: column ambiguously defined

ORA-00918: column ambiguously defined
Cause: A column name used in a join exists in more than one table and is thus referenced ambiguously. In a join, any column name that occurs in more than one of the tables must be prefixed by its table name when referenced. The column should be referenced as TABLE.COLUMN or TABLE_ALIAS.COLUMN. For example, if tables EMP and DEPT are being joined and both contain the column DEPTNO, then all references to DEPTNO should be prefixed with the table name, as in EMP.DEPTNO or E.DEPTNO
Action: Prefix references to column names that exist in multiple tables with either the table name or a table alias and a period (.), as in the examples above

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00917: missing comma

ORA-00917: missing comma

ORA-00917: missing comma
Cause: A required comma has been omitted from a list of columns or values in an INSERT statement or a list of the form ((C,D),(E,F), …)
Action: Correct the syntax

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00915: network access of dictionary table not currently allowed

ORA-00915: network access of dictionary table not currently allowed

ORA-00915: network access of dictionary table not currently allowed
Cause: This is an internal error message not usually issued
Action: Contact Oracle Support Services

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00914: missing ADD keyword

ORA-00914: missing ADD keyword

ORA-00914: missing ADD keyword
Cause: The keyword ADD does not precede one of the following:
 The keyword log file in an ALTER DATABASE statement
 A column element or table constraint in an ALTER TABLE statement
 The keyword DATAFILE in an ALTER TABLESPACE statement
Action: Specify the keyword ADD in the ALTER statement

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00913: too many values

ORA-00913: too many values

ORA-00913: too many values
Cause: The SQL statement requires two sets of values equal in number. This error occurs when the second set contains more items than the first set. For example, the subquery in a WHERE or HAVING clause may return too many columns, or a VALUES or SELECT clause may return more columns than are listed in the INSERT
Action: Check the number of items in each set and change the SQL statement to make them equal

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00912: input parameter too long

ORA-00912: input parameter too long

ORA-00912: input parameter too long
Cause: one of your input strings was too long
Action: shorten the input parameter length

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00911: invalid character

ORA-00911: invalid character

ORA-00911: invalid character
Cause: identifiers may not start with any ASCII character other than letters and numbers. $#_ are also allowed after the first character. Identifiers enclosed by doublequotes may contain any character other than a doublequote. Alternative quotes (q’#…#’) cannot use spaces, tabs, or carriage returns as delimiters. For all other contexts, consult the SQL Language Reference Manual
Action: none

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/