Hi,
I just updated a working application from dotconnect for Oracle 7.8 to V 8.2 (Jan 16, 2014).
Now I am getting ORA-01480 without chanding anything in the application (pure ADO.NET)...
This seems to be a bug since the application was working absolutely fine before the update...
Please help.
Thanks in advance
Yahia
EDIT:
The problem comes up with ExecuteArray in combination with a complex INSERT.
If I replace the call to ExecuteArry with ExecuteNonQuery (values from index 0 of the the respective arrays) it works without a problem!
V 8.2 / ORA-01480 - Bug?
Re: V 8.2 / ORA-01480 - Bug?
Additional information:
Oracle Client V 11.2.01 x64
Windows Server 2008 R2 Enterprise (x64)
Application is .NET 4 Full Framework Windows Forms x64
Oracle Server on Windows Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options
Please help.
Oracle Client V 11.2.01 x64
Windows Server 2008 R2 Enterprise (x64)
Application is .NET 4 Full Framework Windows Forms x64
Oracle Server on Windows Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options
Please help.
-
Pinturiccio
- Devart Team
- Posts: 2420
- Joined: Wed 02 Nov 2011 09:44
Re: V 8.2 / ORA-01480 - Bug?
We could not reproduce the issue. In our environment array binding feature works with dotConnect for Oracle 8.2.80.
Please try using 'Unicode=true' parameter in your connection string. Does it work?
As a workaround try using Direct connection mode.
Please also create and send us a small test project with the corresponding DDL/DML scripts for reproducing the issue.
Please try using 'Unicode=true' parameter in your connection string. Does it work?
As a workaround try using Direct connection mode.
Please also create and send us a small test project with the corresponding DDL/DML scripts for reproducing the issue.
Re: V 8.2 / ORA-01480 - Bug?
Thanks alot.
I was able to workaround the problem by explicitely creating the Parameters.
I was able to workaround the problem by explicitely creating the Parameters.