All Oracle errors
ORA-01722sql

Invalid number

ORA-01722: invalid number

Why it happens

A character value that is not a number was implicitly converted to NUMBER — for example a string column compared to a numeric literal, or text like '1,000' with a comma.

How to fix it

Cast explicit TO_NUMBER(COLUMN), fix bad data (REGEXP_REPLACE non-digits), or change the comparison to a string. Find the culprit row by selecting the column alone and cat-arting the bad value.

A note on ORA-01722

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?