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');
asked Sep 23, 2012 at 1:24
Phillip GibsonPhillip Gibson
1,4872 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
3,8512 gold badges36 silver badges57 bronze badges
answered Sep 23, 2012 at 8:37
holhol
8,2355 gold badges32 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 badges25 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
77.8k17 gold badges139 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
8,9837 gold badges42 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
98810 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,0123 gold badges32 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♦
30.4k22 gold badges84 silver badges132 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,4401 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,3852 gold badges36 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
4464 silver badges10 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,5481 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
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
CREATE OR REPLACE FUNCTION evaluation (a DATE,m Number)
RETURN VARCHAR2
IS
BEGIN
RETURN CASE
WHEN (floor(sysdate - a) < m) THEN 'Yes'
ELSE 'No'
END;
Am i doing wrongly, when executing the following code if shows me an error like:
Error: ORA-01722: invalid number
asked Mar 25, 2013 at 9:23
3
The posted code is missing an END; (the first END ends the CASE, so a second is needed to end the procedure), but other than that it is working, provided you enter a number and not a string that cannot be converted to a number.
select evaluation(sysdate+3, 2) from dual;
YES
select evaluation(sysdate+3, '2') from dual;
YES
select evaluation(sysdate+3, 'a') from dual;
Error: ORA-01722: invalid number
answered Mar 25, 2013 at 9:32
Klas LindbäckKlas Lindbäck
33k5 gold badges57 silver badges82 bronze badges
Include another end @ last…..
CREATE OR REPLACE FUNCTION evaluation (a DATE,m Number)
RETURN VARCHAR2
IS
BEGIN
RETURN (CASE
WHEN (floor(sysdate - a) < m) THEN 'Yes'
ELSE 'No'
END);
END;
answered Mar 25, 2013 at 11:30
AspirantAspirant
2,2289 gold badges31 silver badges43 bronze badges
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.
ORA-01722: неправильный номер
Причина:
Пробное преобразование символьной строки в числовую провалилось, потому что символьная строка не была правильной числовой литерой. Только числовые поля или символьные поля содержащие числовые данные могут быть использованы в арифметических функциях или выражениях. Только числовые поля могут быть добавлены или вычтены из данных.
Действие:
Проверьте символьные строки в функции или в выражении; убедитесь в том, что они содержат только числа, знаки, десятичные точки, и символ «E» или «e», затем повторите операцию.
In my previous article i have given the brief introduction about different errors like ORA-12154: TNS listener error and ORA-00600 which is related to internal error codes.The third most searched Error for oracle is ORA-01722 Error which is Invalid Number error. This error is searched approximately 25 k times per month in google search engine.In this article i will try to explain you why this error will come and how this error will solve.You will get this error while converting non numeric string to number or while inserting string value or character value in to number column.
“ORA-01722 error will be searched approximately 25 k times per month on google.”
Why ORA-01722 error will come?
This is another common error the SQL and PL SQL developers and DBAs will face.This error will come in oracle for mismatching the datatype as number to string or trying to insert the string value in to number values.There should be different reasons for this error.I will mention some scenarios in which this error will come.
Situation 1 :
When user tries to convert string value to number value.
To explain this scenario i will take a simple example. I will try to convert the string in to number using TO_NUMBER function.
Query :
select to_number(‘XYZ’) from dual;
Output :
Error at line 1:
ORA-01722: invalid number
Situation 2:
When user tries to insert the string value in to number column.
Query:
create table Employee
(rollno number(10));insert into Employee
values(1);
commit;select * from Employee;
insert into Employee
values(‘amit’);
commit;
Output :
Error at line 1:
ORA-01722: invalid number
The ORA-01722 error will come when you try to convert the string value in to number.
Situation 3 :
Query :
create table Test111
(no1 varchar2(10));insert into Test111
values(‘1′);
commit;insert into Test111
values(’10’);
commit;insert into Test111
values(‘a’);
commit;select * from Test111 where no1 between 0 and 10;
Output :
Error at line 1:
ORA-01722: invalid number
NO TIME TO READ CLICK HERE TO GET THIS ARTICLE
Resolution of the Error :
I have given the basic scenarios of producing the ORA-1722 error.This error will come when we tries to convert the string value in to number using to_number function. The string can not be converted to number.So to resolve the error we need to use number value in to_number function.
Resolution 1 :
Use number value in to_number function.
Query :
select to_number(‘111’) from dual;
Output :
111
Always use number value (for varchar2 column) in to_number function to convert that value to number.
Resolution 2 :
Check description of table and change the column to varchar2 column if you want to insert the varchar2 value in the column.
Query :
Alter table Employee
modify rollno varchar2(10);
insert into Employee
values(‘amit’);
commit;
1 Record inserted
So to resolve this error we need to find out the number column from the table and change it to varchar2 column.After altering the column we will be able to insert varchar datatype values.