A very easy one for someone,
The following insert is giving me the
ORA-01722: invalid number
why?
INSERT INTO CUSTOMER VALUES (1,'MALADY','Claire','27 Smith St Caulfield','0419 853 694');
INSERT INTO CUSTOMER VALUES (2,'GIBSON','Jake','27 Smith St Caulfield','0415 713 598');
INSERT INTO CUSTOMER VALUES (3,'LUU','Barry','5 Jones St Malvern','0413 591 341');
INSERT INTO CUSTOMER VALUES (4,'JONES','Michael','7 Smith St Caulfield','0419 853 694');
INSERT INTO CUSTOMER VALUES (5,'MALADY','Betty','27 Smith St Knox','0418 418 347');
Vy Do
46.9k60 gold badges215 silver badges318 bronze badges
asked Sep 23, 2012 at 1:24
Phillip GibsonPhillip Gibson
1,4852 gold badges10 silver badges5 bronze badges
7
An ORA-01722 error occurs when an attempt is made to convert a character string into a number, and the string cannot be converted into a number.
Without seeing your table definition, it looks like you’re trying to convert the numeric sequence at the end of your values list to a number, and the spaces that delimit it are throwing this error. But based on the information you’ve given us, it could be happening on any field (other than the first one).
answered Sep 23, 2012 at 1:32
3
Suppose tel_number is defined as NUMBER — then the blank spaces in this provided value cannot be converted into a number:
create table telephone_number (tel_number number);
insert into telephone_number values ('0419 853 694');
The above gives you a
ORA-01722: invalid number
cellepo
4,0312 gold badges38 silver badges57 bronze badges
answered Sep 23, 2012 at 8:37
holhol
8,2655 gold badges33 silver badges59 bronze badges
0
Here’s one way to solve it. Remove non-numeric characters then cast it as a number.
cast(regexp_replace('0419 853 694', '[^0-9]+', '') as number)
answered Dec 27, 2013 at 15:35
gmlacrossegmlacrosse
3622 silver badges8 bronze badges
2
Well it also can be :
SELECT t.col1, t.col2, ('test' + t.col3) as test_col3
FROM table t;
where for concatenation in oracle is used the operator || not +.
In this case you get : ORA-01722: invalid number ...
answered Aug 8, 2016 at 12:35
Lazar LazarovLazar Lazarov
2,4124 gold badges26 silver badges35 bronze badges
1
This is because:
You executed an SQL statement that tried to convert a string to a
number, but it was unsuccessful.
As explained in:
- Oracle/PLSQL: ORA-01722 Error.
To resolve this error:
Only numeric fields or character fields that contain numeric values
can be used in arithmetic operations. Make sure that all expressions
evaluate to numbers.
answered Sep 23, 2012 at 1:31
Mahmoud GamalMahmoud Gamal
78.3k17 gold badges140 silver badges164 bronze badges
1
As this error comes when you are trying to insert non-numeric value into a numeric column in db it seems that your last field might be numeric and you are trying to send it as a string in database. check your last value.
answered Sep 23, 2012 at 3:10
FreelancerFreelancer
9,0187 gold badges43 silver badges81 bronze badges
Oracle does automatic String2number conversion, for String column values! However, for the textual comparisons in SQL, the input must be delimited as a String explicitly: The opposite conversion number2String is not performed automatically, not on the SQL-query level.
I had this query:
select max(acc_num) from ACCOUNTS where acc_num between 1001000 and 1001999;
That one presented a problem: Error: ORA-01722: invalid number
I have just surrounded the «numerical» values, to make them ‘Strings’, just making them explicitly delimited:
select max(acc_num) from ACCOUNTS where acc_num between '1001000' and '1001999';
…and voilà: It returns the expected result.
edit:
And indeed: the col acc_num in my table is defined as String. Although not numerical, the invalid number was reported. And the explicit delimiting of the string-numbers resolved the problem.
On the other hand, Oracle can treat Strings as numbers. So the numerical operations/functions can be applied on the Strings, and these queries work:
select max(string_column) from TABLE;
select string_column from TABLE where string_column between ‘2’ and ‘z’;
select string_column from TABLE where string_column > ‘1’;
select string_column from TABLE where string_column <= ‘b’;
answered Nov 15, 2017 at 12:08
FrantaFranta
99610 silver badges17 bronze badges
1
In my case the conversion error was in functional based index, that I had created for the table.
The data being inserted was OK. It took me a while to figure out that the actual error came from the buggy index.
Would be nice, if Oracle could have gave more precise error message in this case.
answered Sep 2, 2014 at 14:28
iTakeiTake
4,0823 gold badges33 silver badges26 bronze badges
0
If you do an insert into...select * from...statement, it’s easy to get the ‘Invalid Number’ error as well.
Let’s say you have a table called FUND_ACCOUNT that has two columns:
AID_YEAR char(4)
OFFICE_ID char(5)
And let’s say that you want to modify the OFFICE_ID to be numeric, but that there are existing rows in the table, and even worse, some of those rows have an OFFICE_ID value of ‘ ‘ (blank). In Oracle, you can’t modify the datatype of a column if the table has data, and it requires a little trickery to convert a ‘ ‘ to a 0. So here’s how to do it:
- Create a duplicate table:
CREATE TABLE FUND_ACCOUNT2 AS SELECT * FROM FUND_ACCOUNT; - Delete all the rows from the original table:
DELETE FROM FUND_ACCOUNT; -
Once there’s no data in the original table, alter the data type of its OFFICE_ID column:
ALTER TABLE FUND_ACCOUNT MODIFY (OFFICE_ID number); -
But then here’s the tricky part. Because some rows contain blank OFFICE_ID values, if you do a simple
INSERT INTO FUND_ACCOUNT SELECT * FROM FUND_ACCOUNT2, you’ll get the «ORA-01722 Invalid Number» error. In order to convert the ‘ ‘ (blank) OFFICE_IDs into 0’s, your insert statement will have to look like this:
INSERT INTO FUND_ACCOUNT (AID_YEAR, OFFICE_ID) SELECT AID_YEAR, decode(OFFICE_ID,' ',0,OFFICE_ID) FROM FUND_ACCOUNT2;
answered Sep 23, 2015 at 22:23
1
I have found that the order of your SQL statement parameters is also important and the order they are instantiated in your code, this worked in my case when using «Oracle Data Provider for .NET, Managed Driver».
var sql = "INSERT INTO table (param1, param2) VALUES (:param1, :param2)";
...
cmd.Parameters.Add(new OracleParameter("param2", Convert.ToInt32("100")));
cmd.Parameters.Add(new OracleParameter("param1", "alpha")); // This should be instantiated above param1.
Param1 was alpha and param2 was numeric, hence the «ORA-01722: invalid number» error message. Although the names clearly shows which parameter it is in the instantiation, the order is important. Make sure you instantiate in the order the SQL is defined.
Dharman♦
31.1k25 gold badges86 silver badges137 bronze badges
answered Mar 16, 2022 at 13:38
JayKayOf4JayKayOf4
1,2021 gold badge12 silver badges15 bronze badges
For me this error was a bit complicated issue.
I was passing a collection of numbers (type t_numbers is table of number index by pls_integer;) to a stored procedure. In the stored proc there was a bug where numbers in this collection were compared to a varchar column
select ... where ... (exists (select null from table (i_coll) ic where ic.column_value = varchar_column))
Oracle should see that ic.column_value is integer so shouldn’t be compared directly to varchar but it didn’t (or there is trust for conversion routines).
Further complication is that the stored proc has debugging output, but this error came up before sp was executed (no debug output at all).
Furthermore, collections [<empty>] and [0] didn’t give the error, but for example [1] errored out.
answered Sep 5, 2022 at 12:43
Pasi SavolainenPasi Savolainen
2,4701 gold badge22 silver badges35 bronze badges
The ORA-01722 error is pretty straightforward. According to Tom Kyte:
We’ve attempted to either explicity or implicity convert a character string to a number and it is failing.
However, where the problem is is often not apparent at first. This page helped me to troubleshoot, find, and fix my problem. Hint: look for places where you are explicitly or implicitly converting a string to a number. (I had NVL(number_field, 'string') in my code.)
answered May 11, 2016 at 23:01
BaodadBaodad
2,4252 gold badges38 silver badges39 bronze badges
This happened to me too, but the problem was actually different: file encoding.
The file was correct, but the file encoding was wrong. It was generated by the export utility of SQL Server and I saved it as Unicode.
The file itself looked good in the text editor, but when I opened the *.bad file that the SQL*loader generated with the rejected lines, I saw it had bad characters between every original character. Then I though about the encoding.
I opened the original file with Notepad++ and converted it to ANSI, and everything loaded properly.
answered Mar 12, 2020 at 14:54
cienciaciencia
4564 silver badges11 bronze badges
In my case it was an end of line problem, I fixed it with dos2unix command.
answered Oct 25, 2022 at 22:59
tsunlllytsunllly
1,5681 gold badge13 silver badges15 bronze badges
In my case I was trying to Execute below query, which caused the above error ( Note : cus_id is a NUMBER type column)
select *
from customer a
where a.cus_id IN ('115,116')
As a solution to the caused error, below code fragment(regex) can be used which is added in side IN clause (This is not memory consuming as well)
select *
from customer a
where a.cus_id IN (select regexp_substr (
com_value,
'[^,]+',
1,
level
) value
from (SELECT '115,116' com_value
FROM dual)rws
connect by level <=
length ( com_value ) - length ( replace ( com_value, ',' ) ) + 1)
answered Dec 23, 2022 at 3:21
SQL error «ORA-01722: invalid number»
Normally this issue you faced over test env the query which is working fine over test env will create issue over prod due to version control issue.
In case the below query was working over test env accurately.
- Test ENV.
SELECT * FROM FBS.TSPTable WHERE RTCODE=230 AND ID =23431839941 AND CREATION_DATE = (SELECT MAX (CREATION_DATE) FROM TSPTable WHERE RTCODE = 230 AND ID=23431839941)
Qry Result Successful over test env.
- Over PROD.
SELECT * FROM FBS.TSPTable WHERE RTCODE=230 AND ID =23431839941 AND CREATION_DATE = (SELECT MAX (CREATION_DATE) FROM TSPTable WHERE RTCODE = 230 AND ID =23431839941)
Error:java.sql.SQLSyntaxErrorException: ORA-01722: invalid number
3.How I solved this ISSUE by Adding Colon to the parameter values as belowThis is strange i fixed it by addin colon as below .
SELECT * FROM FBS.TSPTable WHERE RTCODE=’230′ AND ID =’23431839941′ AND CREATION_DATE = (SELECT MAX (CREATION_DATE) FROM TSPTable WHERE RTCODE = ‘230’ AND ID =’23431839941′)
And get the success result over the PROD, the same query work on both env well.
answered Sep 14 at 9:41
Najaf AliNajaf Ali
1,43316 silver badges26 bronze badges
try this as well, when you have a invalid number error
In this
a.emplid is number and b.emplid is an varchar2 so if you got to convert one of the sides
where to_char(a.emplid)=b.emplid
answered Jun 8, 2016 at 14:35
You can always use TO_NUMBER() function in order to remove this error.This can be included as INSERT INTO employees phone_number values(TO_NUMBER(‘0419 853 694’);
answered Oct 11, 2014 at 6:08
A very easy one for someone,
The following insert is giving me the
ORA-01722: invalid number
why?
INSERT INTO CUSTOMER VALUES (1,'MALADY','Claire','27 Smith St Caulfield','0419 853 694');
INSERT INTO CUSTOMER VALUES (2,'GIBSON','Jake','27 Smith St Caulfield','0415 713 598');
INSERT INTO CUSTOMER VALUES (3,'LUU','Barry','5 Jones St Malvern','0413 591 341');
INSERT INTO CUSTOMER VALUES (4,'JONES','Michael','7 Smith St Caulfield','0419 853 694');
INSERT INTO CUSTOMER VALUES (5,'MALADY','Betty','27 Smith St Knox','0418 418 347');
Vy Do
46.9k60 gold badges215 silver badges318 bronze badges
asked Sep 23, 2012 at 1:24
Phillip GibsonPhillip Gibson
1,4852 gold badges10 silver badges5 bronze badges
7
An ORA-01722 error occurs when an attempt is made to convert a character string into a number, and the string cannot be converted into a number.
Without seeing your table definition, it looks like you’re trying to convert the numeric sequence at the end of your values list to a number, and the spaces that delimit it are throwing this error. But based on the information you’ve given us, it could be happening on any field (other than the first one).
answered Sep 23, 2012 at 1:32
3
Suppose tel_number is defined as NUMBER — then the blank spaces in this provided value cannot be converted into a number:
create table telephone_number (tel_number number);
insert into telephone_number values ('0419 853 694');
The above gives you a
ORA-01722: invalid number
cellepo
4,0312 gold badges38 silver badges57 bronze badges
answered Sep 23, 2012 at 8:37
holhol
8,2655 gold badges33 silver badges59 bronze badges
0
Here’s one way to solve it. Remove non-numeric characters then cast it as a number.
cast(regexp_replace('0419 853 694', '[^0-9]+', '') as number)
answered Dec 27, 2013 at 15:35
gmlacrossegmlacrosse
3622 silver badges8 bronze badges
2
Well it also can be :
SELECT t.col1, t.col2, ('test' + t.col3) as test_col3
FROM table t;
where for concatenation in oracle is used the operator || not +.
In this case you get : ORA-01722: invalid number ...
answered Aug 8, 2016 at 12:35
Lazar LazarovLazar Lazarov
2,4124 gold badges26 silver badges35 bronze badges
1
This is because:
You executed an SQL statement that tried to convert a string to a
number, but it was unsuccessful.
As explained in:
- Oracle/PLSQL: ORA-01722 Error.
To resolve this error:
Only numeric fields or character fields that contain numeric values
can be used in arithmetic operations. Make sure that all expressions
evaluate to numbers.
answered Sep 23, 2012 at 1:31
Mahmoud GamalMahmoud Gamal
78.3k17 gold badges140 silver badges164 bronze badges
1
As this error comes when you are trying to insert non-numeric value into a numeric column in db it seems that your last field might be numeric and you are trying to send it as a string in database. check your last value.
answered Sep 23, 2012 at 3:10
FreelancerFreelancer
9,0187 gold badges43 silver badges81 bronze badges
Oracle does automatic String2number conversion, for String column values! However, for the textual comparisons in SQL, the input must be delimited as a String explicitly: The opposite conversion number2String is not performed automatically, not on the SQL-query level.
I had this query:
select max(acc_num) from ACCOUNTS where acc_num between 1001000 and 1001999;
That one presented a problem: Error: ORA-01722: invalid number
I have just surrounded the «numerical» values, to make them ‘Strings’, just making them explicitly delimited:
select max(acc_num) from ACCOUNTS where acc_num between '1001000' and '1001999';
…and voilà: It returns the expected result.
edit:
And indeed: the col acc_num in my table is defined as String. Although not numerical, the invalid number was reported. And the explicit delimiting of the string-numbers resolved the problem.
On the other hand, Oracle can treat Strings as numbers. So the numerical operations/functions can be applied on the Strings, and these queries work:
select max(string_column) from TABLE;
select string_column from TABLE where string_column between ‘2’ and ‘z’;
select string_column from TABLE where string_column > ‘1’;
select string_column from TABLE where string_column <= ‘b’;
answered Nov 15, 2017 at 12:08
FrantaFranta
99610 silver badges17 bronze badges
1
In my case the conversion error was in functional based index, that I had created for the table.
The data being inserted was OK. It took me a while to figure out that the actual error came from the buggy index.
Would be nice, if Oracle could have gave more precise error message in this case.
answered Sep 2, 2014 at 14:28
iTakeiTake
4,0823 gold badges33 silver badges26 bronze badges
0
If you do an insert into...select * from...statement, it’s easy to get the ‘Invalid Number’ error as well.
Let’s say you have a table called FUND_ACCOUNT that has two columns:
AID_YEAR char(4)
OFFICE_ID char(5)
And let’s say that you want to modify the OFFICE_ID to be numeric, but that there are existing rows in the table, and even worse, some of those rows have an OFFICE_ID value of ‘ ‘ (blank). In Oracle, you can’t modify the datatype of a column if the table has data, and it requires a little trickery to convert a ‘ ‘ to a 0. So here’s how to do it:
- Create a duplicate table:
CREATE TABLE FUND_ACCOUNT2 AS SELECT * FROM FUND_ACCOUNT; - Delete all the rows from the original table:
DELETE FROM FUND_ACCOUNT; -
Once there’s no data in the original table, alter the data type of its OFFICE_ID column:
ALTER TABLE FUND_ACCOUNT MODIFY (OFFICE_ID number); -
But then here’s the tricky part. Because some rows contain blank OFFICE_ID values, if you do a simple
INSERT INTO FUND_ACCOUNT SELECT * FROM FUND_ACCOUNT2, you’ll get the «ORA-01722 Invalid Number» error. In order to convert the ‘ ‘ (blank) OFFICE_IDs into 0’s, your insert statement will have to look like this:
INSERT INTO FUND_ACCOUNT (AID_YEAR, OFFICE_ID) SELECT AID_YEAR, decode(OFFICE_ID,' ',0,OFFICE_ID) FROM FUND_ACCOUNT2;
answered Sep 23, 2015 at 22:23
1
I have found that the order of your SQL statement parameters is also important and the order they are instantiated in your code, this worked in my case when using «Oracle Data Provider for .NET, Managed Driver».
var sql = "INSERT INTO table (param1, param2) VALUES (:param1, :param2)";
...
cmd.Parameters.Add(new OracleParameter("param2", Convert.ToInt32("100")));
cmd.Parameters.Add(new OracleParameter("param1", "alpha")); // This should be instantiated above param1.
Param1 was alpha and param2 was numeric, hence the «ORA-01722: invalid number» error message. Although the names clearly shows which parameter it is in the instantiation, the order is important. Make sure you instantiate in the order the SQL is defined.
Dharman♦
31.1k25 gold badges86 silver badges137 bronze badges
answered Mar 16, 2022 at 13:38
JayKayOf4JayKayOf4
1,2021 gold badge12 silver badges15 bronze badges
For me this error was a bit complicated issue.
I was passing a collection of numbers (type t_numbers is table of number index by pls_integer;) to a stored procedure. In the stored proc there was a bug where numbers in this collection were compared to a varchar column
select ... where ... (exists (select null from table (i_coll) ic where ic.column_value = varchar_column))
Oracle should see that ic.column_value is integer so shouldn’t be compared directly to varchar but it didn’t (or there is trust for conversion routines).
Further complication is that the stored proc has debugging output, but this error came up before sp was executed (no debug output at all).
Furthermore, collections [<empty>] and [0] didn’t give the error, but for example [1] errored out.
answered Sep 5, 2022 at 12:43
Pasi SavolainenPasi Savolainen
2,4701 gold badge22 silver badges35 bronze badges
The ORA-01722 error is pretty straightforward. According to Tom Kyte:
We’ve attempted to either explicity or implicity convert a character string to a number and it is failing.
However, where the problem is is often not apparent at first. This page helped me to troubleshoot, find, and fix my problem. Hint: look for places where you are explicitly or implicitly converting a string to a number. (I had NVL(number_field, 'string') in my code.)
answered May 11, 2016 at 23:01
BaodadBaodad
2,4252 gold badges38 silver badges39 bronze badges
This happened to me too, but the problem was actually different: file encoding.
The file was correct, but the file encoding was wrong. It was generated by the export utility of SQL Server and I saved it as Unicode.
The file itself looked good in the text editor, but when I opened the *.bad file that the SQL*loader generated with the rejected lines, I saw it had bad characters between every original character. Then I though about the encoding.
I opened the original file with Notepad++ and converted it to ANSI, and everything loaded properly.
answered Mar 12, 2020 at 14:54
cienciaciencia
4564 silver badges11 bronze badges
In my case it was an end of line problem, I fixed it with dos2unix command.
answered Oct 25, 2022 at 22:59
tsunlllytsunllly
1,5681 gold badge13 silver badges15 bronze badges
In my case I was trying to Execute below query, which caused the above error ( Note : cus_id is a NUMBER type column)
select *
from customer a
where a.cus_id IN ('115,116')
As a solution to the caused error, below code fragment(regex) can be used which is added in side IN clause (This is not memory consuming as well)
select *
from customer a
where a.cus_id IN (select regexp_substr (
com_value,
'[^,]+',
1,
level
) value
from (SELECT '115,116' com_value
FROM dual)rws
connect by level <=
length ( com_value ) - length ( replace ( com_value, ',' ) ) + 1)
answered Dec 23, 2022 at 3:21
SQL error «ORA-01722: invalid number»
Normally this issue you faced over test env the query which is working fine over test env will create issue over prod due to version control issue.
In case the below query was working over test env accurately.
- Test ENV.
SELECT * FROM FBS.TSPTable WHERE RTCODE=230 AND ID =23431839941 AND CREATION_DATE = (SELECT MAX (CREATION_DATE) FROM TSPTable WHERE RTCODE = 230 AND ID=23431839941)
Qry Result Successful over test env.
- Over PROD.
SELECT * FROM FBS.TSPTable WHERE RTCODE=230 AND ID =23431839941 AND CREATION_DATE = (SELECT MAX (CREATION_DATE) FROM TSPTable WHERE RTCODE = 230 AND ID =23431839941)
Error:java.sql.SQLSyntaxErrorException: ORA-01722: invalid number
3.How I solved this ISSUE by Adding Colon to the parameter values as belowThis is strange i fixed it by addin colon as below .
SELECT * FROM FBS.TSPTable WHERE RTCODE=’230′ AND ID =’23431839941′ AND CREATION_DATE = (SELECT MAX (CREATION_DATE) FROM TSPTable WHERE RTCODE = ‘230’ AND ID =’23431839941′)
And get the success result over the PROD, the same query work on both env well.
answered Sep 14 at 9:41
Najaf AliNajaf Ali
1,43316 silver badges26 bronze badges
try this as well, when you have a invalid number error
In this
a.emplid is number and b.emplid is an varchar2 so if you got to convert one of the sides
where to_char(a.emplid)=b.emplid
answered Jun 8, 2016 at 14:35
You can always use TO_NUMBER() function in order to remove this error.This can be included as INSERT INTO employees phone_number values(TO_NUMBER(‘0419 853 694’);
answered Oct 11, 2014 at 6:08
Using Oracle database is very common but sometimes due to some uncertain reasons, you may get ORA-01722 invalid number error. Do you want to know what is ORA-01722 invalid number error and how to resolve ora-01722 invalid number error? If you want to know so then I must say that you have come to the right place. I am saying so because here I am going to mention some best ways to fix ORA-01722 error in Oracle.
Now, let’s get started with the introduction of this error, causes and then the ways to fix ora-01722 invalid number error and so on…..
What Is ORA_01722 Invalid Number Error?
ORA-01722 invalid number error is actually a fairly typical error in Oracle database. It is an invalid number error that occurs during a failure when you convert a character string to a valid number. It is an error that occurs due to arithmetic operation in the statement failed to calculate just because a single operand cannot be implicitly converted to a valid number. This error can take place due to several reasons which are further mentioned in this blog, so do not skip going through this blog.
Causes Of Occurring ORA-01722 Invalid Number Error
Several causes are that can lead you to face ORA-01722 invalid number error. However, some of the major causes are as follows:
Cause #1: Error During String Concatenation
If you use a plus (add) sign then it cannot concatenate strings. So, if you are using a wrong sign to concatenate two strings then you can get ORA-01722 invalid number error. Below is the code you might have tried to concatenate two strings:
SQL> set heading off;
SQL> select ‘Today is ‘ + sysdate from dual;
select ‘Today is ‘ + sysdate from dual
*
ERROR at line 1:
ORA-01722: invalid number
Here, SQL parser thought the statement tried to make arithmetic operation, however, it failed to continue. The right ways to concatenate two strings are as follows:
SQL> select ‘Today is ‘ || sysdate from dual;
Today is 26-DEC-19
The output of this code is perfect in concatenating two strings.
Cause #2: Error During Type Conversion
When you create a simple table that contains only one column with NUMBER type with the below code:
SQL> create table salaries (salary number);
Table created.
If you try to insert a row into the table that contains NUMBER column, you may get ORA_01722 error with the below code:
SQL> insert into salaries (salary) values (‘200,000’);
insert into salaries (salary) values (‘200,000’)
*
ERROR at line 1:
ORA-01722: invalid number
You may get this error because the value ‘200,000’ of column SALARY can’t be converted into a valid number. You can make it easier by just removing the comma separator:
SQL> insert into salaries (salary) values (‘200000’);
1 row created.
When it comes to fixing ORA_01722 invalid number error, you can try several ways but the best options you can try are further mentioned here. All these solutions are very easy to try and are the most effective and working ways:
Fix #1: Insert Or Update Using a Subquery
If you are inserting or updating values in a table by using a subquery then you can get this error. This error can be quite difficult to detect because you are not explicitly stating the values to be inserted. You get this error because sometimes even one of the values found in the subquery is trying to be inserted into some numeric column. Also, the value is not a number.
Well, to find the major causes of this error, you can try running the subquery by itself and you can add a WHERE condition as mentioned below:
WHERE UPPER(column) != LOWER(column)
Here, you can replace the column with the column you found has the bad data. Here, the UPPER and the LOWER functions will return the different values from character strings and then you will be left with the rows that have strings values.
If you want to dig further then you can follow the below steps:
- You can run the subquery by itself to check the results.
- You can look at the values in the column you are expecting to be numeric to identify any that look like the same characters.
- You can also perform a TO_NUMBER on the columns to find the error.
- Also, you can get a DISTINCT list of each column in the subquery and then you can perform a TO_NUMBER.
- Apart from this, you can use a WHERE clause to restrict the results of the subquery and so you are just looking at a small data set at a time.
After you found the value that causes this error, you can either update the bad data or you can update the query to properly handle this data.
Fix #2: Mismatch Of Data Types In An Insert Query
If you are trying to INSERT data into a table with the use of INSERT INTO VALUES?
If yes then you can check that the columns are aligned to the values you want. It means that you have to make sure that the position of the columns that used to contain numbers that you are trying to insert.
The below query will then produce ORA-01722 invalid number error:
INSERT INTO student_results (student_id, subject_name, score, comments)
VALUES (1, ‘Science’, ‘Pretty good’, 95);
After this query, you will get the columns around the wrong way and in order to correct the query, you have to move the score value of 95 to in between the comments and the subject name.
INSERT INTO student_results (student_id, subject_name, score, comments)
VALUES (1, ‘Science’, 95, ‘Pretty good’);
Fix#3: Convert Implicitly In a Select Statement
If you are getting the error ‘ora-01722 invalid number’ when you are running a SELECT statement there would be two possible reasons:
- Invalid format mask while using TO_NUMBER
- Convert implicitly in WHERE clause
In some cases, this error takes place due to implicit conversion in a WHERE clause. An implicit conversion is where a value is being converted by Oracle but you do not specify it.
However, in order to fix this issue, you have to check for a numeric column that is being compared to a character column. As for example:
SELECT …
WHERE number_col = varchar_col;
This code insertion will result in an implicit conversion of the VARCHAR column to a number which may also cause the invalid number error.
However, if you are using the TO_NUMBER function in the query, you have to make sure that the format mask includes acceptable characters.
Fix #4: Some Common Possible Fixes
Apart from the above fixes, you can try these other possible ways to fix ORA-01722 invalid number error. Here are the other possible fixes you can try:
- The database formats for numbers are mismatched between these two databases. As for example, European numeric data uses 12.345,67 where US format is 12,345.67. You can review the NLS_LANG settings to make sure that it is not causing any problem.
- Fields that used to contain spaces cannot be easily converted, so it is important to make sure that you TRIM this data. After that, you convert it to NULL or also can convert it to ZERO.
- It is possible that a function-based index is causing ORA_01722 invalid number error. You can review the table to see if there are any function-based indexes that could be converting the data.
Ultimate Solution: Oracle File Repair Tool To Fix ORA-01722 Invalid Number Error
Even after trying all the above ways, you are still unable to resolve ora-01722 invalid number then you can try Oracle File Repair Tool. This tool has the best features that can definitely let you know how to resolve ora-01722 invalid number error? You can just try this tool and fix ora-01722 invalid number error due to its great features. All you have to do is to download and install Oracle File Repair Tool to fix ora-01722 invalid number error.
Below, you will get the step by step guide to know how to resolve ora-01722 invalid number error with this best-featured tool.
Steps To Fix ORA-01722 Invalid Number Error
Step 1: Search the Initial screen of Stellar Phoenix Oracle Repair & Recovery with a pop-up window showing options to select or search corrupt Oracle databases on your computer.
Step 2: Click Scan File to initiate the scan process after selecting the oracle database. The recoverable database objects get listed in left-side pane.
Step 3: Click an object to see its preview.
Step 4: : Click Start Repair in the icon bar to start the repair process. A pop-up window is displayed which show the steps needed to perform further. Click next and continue.
Step 5: Give the user name, password and path of the blank database where you want to save the repaired database objects.
Step 6: Repairing and restoring various database objects after establishing a connection with blank oracle database.
Final Verdict
While using Oracle database, if you ever come across an error stated as ‘ORA-01722 Invalid Number’ then you should try these ways mentioned above. I have tried my best to provide you the working and the effective solution I can. However, if manual ways do not work in your case, then you can also try Oracle File Repair Tool. This tool has the capability to fix any kind of error related to Oracle database. So, know how to resolve ora-01722 invalid number error in Oracle database and recover the database easily in no time.
Jacob Martin is a technology enthusiast having experience of more than 4 years with great interest in database administration. He is expertise in related subjects like SQL database, Access, Oracle & others. Jacob has Master of Science (M.S) degree from the University of Dallas. He loves to write and provide solutions to people on database repair. Apart from this, he also loves to visit different countries in free time.
I have a query in the package throwing error
ORA-01722 : invalid number.
I tried many ways but no luck.
select h.column
from table1 h,table2 c
where c.created_date='17-MAY-17'
and nvl(c.acct_nmbr,0)=nvl(to_number(h.v_acct_num),0)
c.acct_nmbris ofNUMBER(19,0)h.v_acct_numis ofvarchar2(4000 byte)
Please suggest me the solution
asked Jan 23, 2020 at 4:41
2
Obviously v_acct_num column contains non-numeric values. to_number() function has restriction that the value in the argument shouldn’t contain any non-numeric character, otherwise the system hurls with ORA-01722 : invalid number. If you’re sure about the data matches when non-numeric characters are extracted then use regexp_replace(t2.v_acct_num,'[^[:digit:]]') within the collation of the join‘s on clause :
select t2.column
from table1 t1
join table2 t2 on nvl(t1.acct_nmbr,0) = nvl(regexp_replace(t2.v_acct_num,'[^[:digit:]]'),0)
where t2.created_date = date'2017-05-17'
Use ANSI-92 standard for Join, and ISO-8601 standard for date syntaxes.
answered Jan 23, 2020 at 7:52
Barbaros ÖzhanBarbaros Özhan
59.5k10 gold badges31 silver badges55 bronze badges
If you are using Oracle 12.2 or higher then you can use the TO_NUMBER with ON CONVERSION ERROR clause as follows:
SELECT
H.COLUMN
FROM
TABLE1 H
JOIN TABLE2 C
ON NVL(C.ACCT_NMBR, 0) = NVL(TO_NUMBER(H.V_ACCT_NUM DEFAULT -999 ON CONVERSION ERROR), 0)
-- use any number which is impossible in your column
-- so that it do not match any random records.
WHERE
C.CREATED_DATE = DATE '2017-05-17';
Note:
- Use standard ANSI joins
- Use
DATEliteral wherever you want to convert string to date orTO_DATEfunction
Cheers!!
answered Jan 23, 2020 at 8:39
PopeyePopeye
35.5k4 gold badges10 silver badges31 bronze badges
Identify what data is non-numeric:
select * from table1 h
where regexp_like(h.v_acct_num, '[^0-9]')
and delete them
.
Hope it helps.
answered Jan 23, 2020 at 5:57
J. ChomelJ. Chomel
8,21315 gold badges41 silver badges69 bronze badges
1
Have you gotten an “ORA-01722 invalid number” error? I’ll explain what this error is and how you can resolve it in this article.
ORA-01722 Cause
The ORA-01722 error is caused by trying to convert a string into a number. It could be because of an invalid numeric character in your expression, or you’re trying to add a text value into a number column.
You’ve run an SQL query (which can be SELECT, INSERT, UPDATE, for example), and you’ve got this error:
ORA-01722: invalid number
The reason for this error is that Oracle has attempted to convert a string into a number, but could not perform the conversion.
For example, converting the value of “Hello” to a number cannot be done.
A valid number contains these characters:
- Digits 0 to 9
- Possibly a decimal point
- A + or – sign
- An E or e character
The error can appear in the following queries:
SELECT TO_NUMBER('123,100') FROM dual;
SELECT 'DatabaseStar' - 2016 FROM dual;There are a few ways to resolve this error, so let’s take a look.
The solution to the “invalid number” error message could be one of several things:
- An incorrect character or typo in your query
- Bad data in your database
- An issue with the query logic
While you’re here, if you want an easy-to-use list of the main features in Oracle SQL, get my SQL Cheat Sheet here:
1 – Mismatch of Data Types in an Insert Query
Are you trying to INSERT data into a table using INSERT INTO VALUES?
If so, check that your columns are aligned to your values. I mean, make sure that the position of the columns that contain numbers match the numbers you’re trying to insert.
This query will produce an error (assuming that score is a number):
INSERT INTO student_results (student_id, subject_name, score, comments)
VALUES (1, 'Science', 'Pretty good', 95);I’ve got the columns around the wrong way here. To correct the query, I need to move the score value of 95 to in between the subject name and comments.
INSERT INTO student_results (student_id, subject_name, score, comments)
VALUES (1, 'Science', 95, 'Pretty good');2 – Inserting or Updating using a Subquery
Are you inserting or updating values in a table using a subquery?
This error can be harder to detect, because you’re not explicitly stating the values to be inserted.
The error occurs because one of the values found in the subquery is trying to be inserted into a numeric column, and the value is not a number.
To find the cause of the error, you can run the subquery by itself and add a WHERE condition:
WHERE UPPER(column) != LOWER(column)Replace the “column” with the column you suspect has the bad data. The UPPER and LOWER functions will return different values from character strings, and you should be left with the rows that have string values.
If you want to dig further, or if that doesn’t work:
- Run the subquery by itself to see the results
- Look at the values in the columns you’re expecting to be numeric to identify any that look like obvious characters.
- If you can’t easily tell, you can perform a TO_NUMBER on the columns to find the error.
- If this doesn’t help, try getting a DISTINCT list of each column in the subquery, and then performing a TO_NUMBER.
- You can also use a WHERE clause to restrict the results of the subquery, so you’re only looking at a small data set at a time.
Once you’ve found the value that causes the issue, you can either update the bad data, or update your query to handle this data.
3 – Implicit Conversion in a Select Statement
Are you getting this “ORA-01722 invalid number” error when running a SELECT statement?
There are a few reasons for this error:
- Implicit conversion in WHERE clause
- Invalid format mask when using TO_NUMBER
In most cases, it is due to an implicit conversion in a WHERE clause. An implicit conversion is where a value is being converted by Oracle but you didn’t specify it.
To resolve this, check for a numeric column that’s being compared to a character column.
For example:
SELECT ...
WHERE number_col = varchar_col;This will result in an implicit conversion of the VARCHAR column to a number, which may cause the invalid number error.
If you’re using the TO_NUMBER function in your query, make sure that the format mask includes acceptable characters.
The earlier example would cause an error.
4 – Other Possible Solutions
There are some other solutions to this error:
- Fields that contain spaces cannot be converted, so ensure that you TRIM this data, convert it to NULL or zero.
- The database formats for numbers are mismatched between two databases. For example, European numeric data uses 12.345,67 where US format is 12,345.67. Review your NLS_LANG settings to ensure this isn’t causing any issues.
- A function-based index on the table could be causing the error. Review your table to see if there are any function-based indexes that could be converting data.
So, that’s how you resolve the ORA-01722 invalid number error in Oracle!
While you’re here, if you want an easy-to-use list of the main features in Oracle SQL, get my SQL Cheat Sheet here: