Devart Forums

Starting with fresh MVC template (VS2013) using EF6.01 and 8.2.90.6 driver. When code first creates the tables its creating with NCLOB where I would expect VARCHAR2. It then errors with the subject. If I change the fields to VARCHAR2 everything works, but how can I get it to stop generating incorrectly? Its defined as string in my migration.

This is all the built in template stuff, I have not written any code - just configured the web.config to use devart.

I have an application that works fine locally and remotely but when ran in our dmz it cannot connect to the database and gives the useless error "The server could not be contacted". On that machine I can use Sql Plus and connect to the database and run queries with no issue. I have tried with both tns and with ip and get the same error.

Most likely its a firewall related issue, but besides port 1521 what ports are needed for this to work? Since Sql Plus works and tnsping resolves correctly I did not expect any problems.

How does this need to be configured to properly going through the firewall? It has to be as strict as possible.

Windows 2008 server, 64bit, 64bit and 32bit oracle drivers installed. Running dotConnect 6.80.350.0

I just exported a schema that resulted in a 6.5gig file. It was quick enough but when I tried to import I got an Oracle error "ORA-02024: data link not found" which if I ignore goes to "ORA-00933: SQL command not properly ended". The offending generated code is:
I assume its the password part? But its a bit of a pain to have errors in a such a large sql file that you can't open through normal means.

Also, it would be nice if dbForge could open the file it creates. Luckily there are programs that can. I could definitely see it not highlighting and giving intellisense but at least let us open it and goto line for debugging purposes. LTF Viewer works well for this but my wish would be to do it without another tool

Sure enough, that fixed it...thank you.

I just installed the latest Oracle client 11.2.0.2.1 and afterward I get this error. I have verified that the path appears to be correct and is not too long. My sql plus works, Rapid SQL works, but dbForge wont use any of my existing connections. It was previously working. I can tnsping my databases.

My application that uses dotConnect works fine. Devart Entity Developer also works fine.

What all should I check?

"Can not obtain Oracle client information from registry. Make sure that Oracle Client Software is installed, or use Direct mode of connecting to server."

Windows 7 64bit
Oracle 11.2.0.2.1 32bit
dbForge 3.1.170

I have the Text Editor->Code Completion->General->Commit selection in completion list by typing: Tab checked but Tab does NOT commit the selection. Enter works, and with Whitespace checked the space bar works...but my Tab does not commit, it just puts a tab in the text editor and the code completion window closes.

How do I get this to work?

Why can't I edit the "Initial" value of a sequence using the editor? Its grayed out and I couldn't find any options to allow me to do so, I had to script a drop and create...which is easy enough but...why have an editor. Am I missing something?

We are using IdeaBlades tool DevForce for our silverlight development. Their most recent update has introduced an error ORA-24777 when running particular queries that use a database link. I am working with IdeaBlade but they are not familiar with Oracle and technically only deal with Entity.

Any help would be appreciated.

I am using EF v2 (.NET 4) and still require:

Devart.Data.Oracle.Entity.OracleEntityProviderServices.TypedNulls = true;

I thought this wasn't needed in EF v2 (.NET 4)?

We are having several issues where the result from a LINQ does not match the data that we expect and get from a sql query. My latest issue should return all the data in the table (232 rows) but it only returns 187. This is a straight query, no conditions. I am pretty frustrated at this point and need some ideas to discover where the problem lies.

Our other issue is a a query that depending on the conditions return wildly different data (rows) and neither reflected the actual results a sql query would. The resulting queries of the linq statements where too different to even diff. These conditions should not have resulted in any additional joins yet the resulting queries where vastly different.