Query Producing ORA-1722 Error After Upgrade or Access Path Change
(Doc ID 2054729.1)
Last updated on MARCH 03, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 6.0.0.0 and laterOracle Database - Standard Edition - Version 7.0.16.0 and later
Oracle Database - Personal Edition - Version 7.1.4.0 and later
Information in this document applies to any platform.
Symptoms
- 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.
Changes
This may happen after an upgrade, a change in execution plan, a change in stats, or for no apparent reason.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |