All Oracle errors
ORA-00933sql

SQL command not properly ended

ORA-00933: SQL command not properly ended

Why it happens

The statement has extra keywords or misplaced clauses — usually a stray semicolon inside a parenthesised sub-query, or ORDER BY/LIMIT placed where Oracle does not expect it.

How to fix it

Remove the trailing semicolon inside the statement body, move ORDER BY outside any sub-query, and replace MySQL-style LIMIT with ROWNUM or FETCH FIRST n ROWS ONLY.

A note on ORA-00933

This entry is part of a hand-curated set of ORA-, FRM-, REP- and TNS- codes that actually turn up in production Oracle estates — SQL*Plus, APEX, 19c/21c, ODP.NET apps, Oracle Forms 6i/12c and Reports included. The message text above is the canonical wording; the cause and fix are written in plain language so a developer or DBA can act without digging through pages of Oracle reference docs first.

Codes outside this list of 44 are far less common. If you hit one, the official Oracle error reference and your instance's alert or listener log remain the authoritative source.

Related sql errors

ORA-00001 · Unique constraint violated ORA-00900 · Invalid SQL statement ORA-00904 · Invalid identifier

Build custom software with us

From internal tools to full platforms — we deliver end to end.

Start a Project
Was this tool useful?