MS OLEDB Provider for Oracle

[jayare1948]

I'm having problems configuring an OracleDataAdaptor.
I can create an OleDataAdaptor using Oracle OleDb and make a connection (Provider = OraOLEDB.Oracle.1). But When I try to use the Microsoft OLeDb (Provider = MSDAORA.1) to create
an OracleDataAdaptor, I get the following error when the
Data Adaptor Wizard Test Connection is run:
"Test Connection failed because of an error in
initializing provider. Oracle Error occurred, but
error nessage could not be retrieved from Oracle."
The error seems to have come up since we upgraded to
Oracle 9i. Does anyone know if this is a known issue
and if so is there a workaround (newer Mircosoft Provider).

Thanks for any help!

jayare1948

 

[Custom24]

Not sure, but you could try the Microsoft Dot Net Provider for Oracle, rather than going thru OleDb. It's free - you can download it from MSDN.

This is what they are pushing now, and for good reason. I would not be surprised if this solved your problem.

HTH

Mark

 

[jayare1948]

Mark:
Thanks for the speedy reply. I spent 2 hours looking all
over the MS Knowledge Base for any answer. About (5) minutes
after I posted, I ran accross Knowledge Base Article
264012 which covers the same kind of problem I was having
only with 8i instead of 9i. I got a fix immediately!
MDAC does not update the OCI Registry entries needed for
the Provider to connect. Here's the fix.
[HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSDTC\MTxOCI]
(8.0i)
"OracleXaLib" = "xa80.dll"
"OracleSqlLib" = "sqllib80.dll"
"OracleOciLib" = "oci.dll"
(8.1i)
"OracleXaLib" = "oraclient8.dll"
"OracleSqlLib" = "orasql8.dll"
"OracleOciLib" = "oci.dll"
(9.0i)
"OracleXaLib" = "oraclient9.dll"
"OracleSqlLib" = "orasql9.dll"
"OracleOciLib" = "oci32.dll"
Thanks again!
By the way, would you happen to know about
ANY books that cover VB.Net programming with
Oracle??? I have Snowdon's Oracle Programming with
Visual Basic and it's great for VB 6.0, but I
can't find anything for VB.NET???

Thanks again

John

 

[Custom24]

Good that you sorted out the problem.
I don't know of any books, but I would still recommend that you have a look at the MS dot net provider for Oracle, rather than using OleDb. If your application is going to do anything other than just firing regular SQL statements at the db, the dot net provider does give you some extra functionality, and is faster and less fiddly as well.


Mark