Oracle Connectivity problem

[Bassel]

I've installed Telerik ORM 2010 Q3
I'm Building ASP.NET web application with  Oracle 10g DB
when I'm trying to create a new ORM domain module and create a new connection with Oracle an Exception appears
with the following details :
Connection Error, Exception Telerik.OpenAccess.Exceptions.DataStorExcpetion, Details: Database driver installation problem: Cannot use factory for oracle..........................................Could not load file or assembly 'Oracle.DataAccess, version= 2.102.2.20, Culture = neutral, PublicToken= 89b483f429c47342' or one of its dependencies. The system cannot find the file specified.
File name: 'Oracle.DataAccess, version= 2.102.2.20, Culture = neutral, PublicToken= 89b483f429c47342' at Telerik.OpenAccess.RT.Adonet2Generic.Impl.OracleODPFactory..ctor()...............................


I'm using vs2008

help please???

[Jan Blessenohl]

Hello Bassel,
You have to install the Oracle ODP.NET driver on your machine. To check you can have a look into the GAC (c:\windows\Assembly) and see which version of the Oracle.DataAccess you have installed.

Greetings,
Jan Blessenohl
the Telerik team

[David Thompson]

Thanks, we had the same problem but reverted back to the previous version.  Once we get past our current issues, we will upgrade again.

[Bassel]

Hi

in fact the oracle dataaccess client was installed but I had to use gacutil to register the dll in the GAC
when I did it worked just fine.

thank you very much 

[David Thompson]

Ok - we are trying this again because there is a bug with the Q2 version when using composite keys.  I am getting this same error (see file attachment).  The Oracle client we are using is 10.2.0.100 and that is what is installed in the GAC.  Is there a different version I need to install?  Is there something else I need to do?

Thanks.

[David Thompson]

All,

I think this is looking for the 11g Oracle Data Access even though we have only installed the 10g client.  I should be able so specifiy what assembly I need by putting an entry in the web.config file but ORM is not using that when you connect to reverse the database.  Any ideas on how I can tell Telerik ORM to use 10g instead of 11g?

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<qualifyAssembly partialName="Oracle.DataAccess" fullName="Oracle.DataAccess, Version=10.2.0.2.100, Culture=neutral, PublicKeyToken=89b483f429c47342"/>
</assemblyBinding>
</runtime>

Thanks,
David

[David Thompson]

All,

--------------------------------

Some more info:

http://www.telerik.com/help/openaccess-orm/visual-designer-deployment-consideration-prerequisities.html

   Oracle Settings

Oracle databases can be accessed by two database drivers. The first is the Microsoft driver that comes with the .NET installation, which is the default. The other is the .NET ODP driver from Oracle. Telerik OpenAccess ORM refers to the ODP driver version 2.102.2.20.

The Microsoft driver works with the Oracle 10, Oracle 10 XE and the Oracle 11 native client, the ODP works with Oracle 10 R2 and the Oracle 11 native client.

The drivers can be downloaded from here.The minimal version should be 10.2.0.2.20.

For Oracle, you will need an account on an active database. Telerik OpenAccess ORM will automatically create/update the class schema information.

Check with your RDBMS administrator if you need help.

[David Thompson]

Looks like I need at least the 10g R2 client:

http://www.oracle.com/technetwork/database/windows/install10202-083849.html

Sigh...I will do that under protest as this will now need full regression testing on all my applications.

[David Thompson]

The 10g R2 client worked fine.  Plus all my other applications seem to be working without any trouble.

I am on the newest version of ORM now (and from what I see, there are a few great changes!).

David

[Jan Blessenohl]

Hello David Thompson,
Good to hear that you have now a working setup. We are usually adding great stuff to our new versions ;) Please stay tuned for all the features in the Q1 release.

Regards,
Jan Blessenohl
the Telerik team

[Kevin]

We just ran into this exact error and found that changing the build options (WPF project properties in VS2010) to x86 from AnyCpu (defaults to 64bit) resolved the problem.