Ora-1722, ORA-01461, or ORA-1460 via 11.2 ODBC when Deleting Records Through Ms Access
(Doc ID 1244424.1)
Last updated on MARCH 04, 2022
Applies to:
Oracle ODBC Driver - Version 11.2.0.1 to 11.2.0.2 [Release 11.2]Information in this document applies to any platform.
Symptoms
Using 11.2.0.1.0 Oracle ODBC Driver and Oracle client and getting:
"[Oracle][ODBC][Ora]ORA-01722: invalid number" trying to delete records in MS Access.
Or
"Microsoft Office Access can't update all the records in the update query.
Microsoft Office Access didn't update 0 field(s) due to a type conversion failure, 0 records(s)due to key violations,
6668 record(s) due to lock violations, and 0 record(s) due to validation rule violations. Do you want to continue running this type of action queryanyway?
To ignore the error(s) and run the query, click Yes.
For an explanation of the causes of the violations, click Help."
An ODBC trace reveals the following Oracle error is occurring:
DIAG [S1000] [Oracle][ODBC][Ora]ORA-01461: can bind a LONG value only for insert into a LONG column
This has also be seen with SQL-Query over an ODBC-Connection with a Delphi Program and throws the following error:
programname : [Oracle][ODBC][Ora]ORA-01460: unimplemented or unreasonable conversion requested
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 |
| Cause |
| Solution |
| References |