Oracle Error ORA-00904

Error code

ORA-00904

Product

Oracle Database

Versions

Oracle Database 19c, 21c, 23ai and 26ai (same message; the documented cause was expanded)

Category

Objects, Names & Identifiers

Last reviewed

24 October 2026

What it means

ORA-00904 means a column name or other identifier in the statement does not exist in the tables it refers to, is not visible at that point of the query, or is not a valid Oracle name. The message shows the name Oracle could not resolve.

Oracle checks every column reference against the tables, views and subqueries in the FROM clause. A name that is misspelled, belongs to another table, or is used where it is not in scope cannot be resolved, and the statement fails with ORA-00904 before it runs. The name in the message is the one Oracle tried, in upper case for an unquoted name, which often shows the mistake straight away.

Oracle's current reference also covers the naming rules. A valid unquoted identifier begins with a letter, contains only letters, digits and the characters $, _ and #, and is not a reserved word; any other name must be in double quotes. Unquoted names are stored and compared in upper case, while quoted names keep their exact case. So a column created as "CustomerName" has to be written that way every time. The maximum length is 128 bytes when the COMPATIBLE parameter is 12.2 or higher (the 19c error text still says 30 characters, which was the older limit).

A column alias from the SELECT list is a common trap. Oracle's SQL Language Reference says the alias can be used in ORDER BY but not in other clauses of the same query, and that from Release 23 it can also be used in GROUP BY. Using it in WHERE, or in GROUP BY on 19c, raises ORA-00904.

Common causes

• The column name is misspelled, or the column does not exist in this version of the table (a migration has not run yet).
• A SELECT list alias is used in WHERE, HAVING or (before Release 23) GROUP BY of the same query.
• The column was created with a quoted mixed-case or lower-case name, such as "CustomerName", and is referenced without matching quotes.
• The column is qualified with the wrong table alias, or the alias is used outside the subquery where it is defined.
• The name is a reserved word or contains characters that are only allowed inside double quotes, for example in a CREATE TABLE written for another database.

Diagnose it

Read-only These queries only read the data dictionary (USER_, ALL_ and DBA_ views) and dynamic performance views (V$). They do not change data, privileges or settings, so they are safe to run first. DBA_ and V$ views need the matching privileges.

SELECT column_name, data_type
FROM all_tab_columns
WHERE owner = 'SHOP'
  AND table_name = 'CUSTOMERS'
ORDER BY column_id;

SELECT owner, table_name, column_name
FROM all_tab_columns
WHERE owner = 'SHOP'
  AND UPPER(column_name) LIKE '%EMAIL%'
ORDER BY table_name;

SELECT keyword, reserved, res_semi
FROM v$reserved_words
WHERE keyword = 'COMMENT';

How to fix it

Each fix is labelled with what it changes. Try read-only checks and the least invasive fix first, and test changes outside production.

SELECT c.id, c.email
FROM shop.customers c
WHERE c.email LIKE '%@example.com';

SELECT *
FROM (
    SELECT order_id, quantity * unit_price AS line_total
    FROM shop.order_lines
)
WHERE line_total > 100;

SELECT "CustomerName"
FROM shop.customers;

ALTER TABLE shop.customers RENAME COLUMN "CustomerName" TO customer_name;

Examples

Using a SELECT alias in WHERE

Not reproduced here: no Oracle Database is installed for this site. The result shows the message format from Oracle's error reference with the identifier filled in, as Oracle reports an unquoted name: in upper case and in double quotes. The rule that a column alias cannot be used in WHERE comes from the SELECT page of Oracle's SQL Language Reference.

SELECT order_id, quantity * unit_price AS line_total
FROM order_lines
WHERE line_total > 100;

ORA-00904: "LINE_TOTAL": invalid identifier

A column created with a quoted mixed-case name

Not reproduced here: no Oracle Database is installed for this site. The case rules come from Oracle's SQL Language Reference (unquoted names are read as upper case, quoted names are case sensitive) and the message format from its error reference. Tools that generate DDL from other databases often quote names like this.

CREATE TABLE customers (
    id             NUMBER PRIMARY KEY,
    "CustomerName" VARCHAR2(100)
);

-- unquoted, so Oracle looks for CUSTOMERNAME
SELECT customername FROM customers;

ORA-00904: "CUSTOMERNAME": invalid identifier

GROUP BY a column alias on Oracle Database 19c

Not reproduced here: no Oracle Database is installed for this site. Oracle's SQL Language Reference states that a column alias can be used in GROUP BY from Release 23, so this query is accepted on 23ai and 26ai; on 19c and 21c, group by the expression itself. The message format comes from Oracle's error reference.

SELECT EXTRACT(YEAR FROM order_date) AS order_year, COUNT(*)
FROM orders
GROUP BY order_year;

ORA-00904: "ORDER_YEAR": invalid identifier

How to prevent it

Create tables with plain unquoted names in a single style (for example customer_name), so they work in any case. Qualify every column with a short table alias in queries that join tables; it makes wrong references obvious when you read the query.

When code has to support several Oracle releases, remember that newer conveniences (such as GROUP BY alias from Release 23) are not available on 19c. Test queries against the oldest release you support.

Common questions

Learn more on CodeWithSQL

• SQL SELECT statement explained
• SQL WHERE clause explained

Official documentation

• ORA-00904 (Oracle Database Error Messages)
• Database object names and qualifiers (Oracle SQL Language Reference 19c)
• SELECT: column aliases (Oracle SQL Language Reference 26ai)
• V$RESERVED_WORDS (Oracle Database Reference 19c)

Last technically reviewed 24 October 2026; examples and diagnostics run on Oracle Database Error Messages reference (26ai, 21c and 19c); not run locally. Messages and explanations follow Oracle's Database Error Messages reference; no Oracle Database was available, so the examples were not run locally.