This content has been marked as final. Show 4 replies
The proper thing is "oraoledb.oracle", not "oraoledb".
What error do you get?
What Oracle client did you install? 32 bit or 64 bit?
VS2008 projects default to target cpu of AnyCPU, which means it will run as 64 bit process on 64 bit OS.
VS2010 projects default to x86, which means it will run as 32 bit even on a 64 bit OS.
Edited by: gdarling on Oct 5, 2011 9:04 AM
Also, you may want to consider using the Oracle Data Provider for .NET rather than OLEDB.
Thanks for the response and sorry, but I am using OraOLEDB.Oracle, not just OraOLEDB.
I installed the 11g 32-bit client to allow connection to 10g database and use of Toad. This client is running fine in Toad and SQL-plus.
The error is "The 'OraOLEDB.Oracle' provider is not registered on the local machine."
This is the same error received regarding "MSDAORA.1" that was installed by Visual Studio 2008.
VS2008 doesn't install MSDAORA btw, it comes with the operating system, and only comes in 32 bit flavor (there is no 64 bit msdaora).
Anyway, what do you have targetCPU set to in the project properties? VS2008 defaults to AnyCPU, VS2010 defaults to x86.
If it's AnyCPU, it will run as a 64 bit process, so you'll need 64 bit oracle client software installed. Or, switch it to x86 and it will run as a 32 bit process and work with your 32 bit client install (and msdaora for that matter).
CONNECTION TIMEOUT=300;DATA SOURCE=tnsitemname;MIN POOL SIZE=5;MAX POOL SIZE=100;STATEMENT CACHE SIZE=5000;USER ID=MyId;PASSWORD=MyPwd;
This connection string can use native provider. To use System.Data.OracleClient you can use
Data Source=tnsitemname;user id=MyId;Password=MyPwd;
Further connection strings can be taken from www.connectionstrings.com