Forum Stats

  • 3,768,286 Users
  • 2,252,771 Discussions
  • 7,874,515 Comments

Discussions

oraOLEDB.Oracle: Provider not found: Oracle 11.2.0.3 Client installation

793999
793999 Member Posts: 3
edited Jan 11, 2013 9:17AM in Oracle Provider for OLE DB
We installed the 11.2.0.3.0 client runtime on Windows 7 32 bit (which installs "Oracle Provider for OLE DB 11.2.0.3.0" by default) and were still receiving "Provider cannot be found" errors. Simply re-installing the exact same product "Oracle Provider for OLE DB 11.2.0.3.0" from the 11.2.0.3.0 ODAC installation corrected it. Maybe an issue with the Oracle client installation? Just thought I'd post and possibly save someone a day of frustration.
7665ef99-dd7c-4c55-92dd-1a7d720b8b67

Answers

  • It's a known bug.

    You can also just run regsvr32 on oraoledb11.dll to register the provider 'manually' as well.

    Greg
    7665ef99-dd7c-4c55-92dd-1a7d720b8b67
  • 934895
    934895 Member Posts: 1
    Hi,

    "it is a known bug."

    I could not find the bug ID / do you know it / how to find it?

    I am looking for an official Oracle statement saying that their installer is not registering the Oledb provider properly.

    Thanks,

    Vincent
  • user5819808
    user5819808 Member Posts: 1 Blue Ribbon
    Hi Vincent,

    Here is what you are looking for.

    NOTE> Installing the 11.2.0.3 Oracle Provider for OLE DB from the Client Install Media Does Not Properly Register the Provider [ID 1380742.1]

    Bug:13417266 WHILE UPGRADING TO 11.2.0.3, INSTALLER FAILS TO REGISTER ORAOLEDB DLL

    Regards!
    Stefanie
  • hi all !!

    We have installed the client 11.2.0.2.0 , and I register the oraOLEDB , and the vb6 programs raise the error "Provider cannot be found. It may not be properly installed" , and we re install MDAC , and continue with these problem.

    can you give us any sugestion?

    thanx!
  • Michael-O
    Michael-O Member Posts: 16 Blue Ribbon
    Thanks, just ran into this issue too. The workaround of the bug is incomplete in My Oracle Support. In order to register the driver correct you need to run the regsvr32 comand from an elevated command prompt otherwhise you will get this: http://social.technet.microsoft.com/Forums/en-US/itprovistasecurity/thread/71037d62-d842-44a3-86df-6ed74df6fc39
This discussion has been closed.