Query Producing ORA-1722 Error After Upgrade or Access Path Change
Last updated on MARCH 02, 2017
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Oracle Database - Standard Edition - Version 220.127.116.11 and later
Oracle Database - Personal Edition - Version 18.104.22.168 and later
Information in this document applies to any platform.
- A query that had been running without error now produces an ORA-1722: invalid number error.
- The statement contains an implicit or explicit conversion from a character to a numeric type (such as during a comparison between a character type and a numeric type).
- The character column that is converted includes non-numeric data, but when the query works, such data should be filtered out using other predicates before it is checked.
This may happen after an upgrade, a change in execution plan, a change in stats, or for no apparent reason.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms