Related
I have an old Oracle 9i r2 database. The last JDBC driver that I managed to make work with it is ojdbc6 11.2.0.4. This keeps me stuck to SQL Developer 4.0.3. I would like to benefit from features of newer versions of SQL Developer. But they use newer driver like ojdbc8.
Is there a way to use old drivers with new versions of SQL Developer? The option to add third party JDBC drivers only work to add drivers for other databases like db2 or sql server.
I tried to delete the recent driver and replace it by an older one but SQL Developer malfunctions.
For SQL Developer version 20.2.0 on Windows 10 do:
Download and unzip SQL Developer version 20.2.0
Download and unzip Oracle Instant Client 11.2.0.4.0
Configure SQL Developer to use above instant client:
Tools > Preferences... > Database > Advanced
Mark "Use Oracle Client" > Configure...
In "Client Type" select "Instant Client"
In "Client Location" point to where you unziped instant client
Click "Test...". The log panel should show something like
Testing loading Oracle JDBC driver ... OK
Testing checking Oracle JDBC driver version ... OK
OK > restart SQL Developer
Configure connection:
Just create a normal connection
In "Advanced" tab add the key oracle.jdbc.timezoneAsRegion with value false. This avoids
ORA-00604: error occurred at recursive SQL level 1
ORA-01882: timezone region not found
This procedure enables you to use a more recent SQL Developer version with an old Oracle 9i r2 without hanging on connect or getting
ORA-01460: unimplemented or unreasonable conversion requested
every time you click something.
I am in the process of moving code from 11g to 12c. Several of the packages which I have moved will not execute, returning an error of
"The file-based source [Package Name] is not present in the database.
Was it compiled?"
The package and the package body have both been compiled normally, and compiled with debug. Neither state makes any difference.
Executing
select OBJECT_TYPE, STATUS from USER_OBJECTS where OBJECT_NAME = [Package Name];
returns valid status for both the PACKAGE_BODY and the PACKAGE.
Some of the packages which I have moved execute successfully. Some do not. I'm stuck.
This issue was fixed by upgrading SQL Developer 3.0.04 to SQL Developer 4.1.3. Apparently the older version does not play well with Oracle 12c.
lightkeeper's advice was good. In my case I installed Oracle 12c for a Windows client and I think the sql developer that comes with it with is a 3.x version. In my case 3.x allowed 1 proc to be built and then started giving the "file-base source ... " error message. Kind of a pain to install sql developer 4.x but when I did it worked a lot better. If you are building standalone procs without packages you will get an error even in sql developer 4.x that says something about packages. The key there is to compile the proc (gear symbol) and then run it (right arrow). You don't need to have a package to have some procs.
I've recently downloaded Oracle SQL Developer 4.1.3 from Oracle Website
and this with JDK as well, but I tried to run in windows 10, it only goes 10% of progress bar, then disappeared. Can't run it at all?
SQL Developer 4.1.3 can connect to Oracle 11g db, right?
I've found 2 things most likely cause what you're experiencing:
video driver conflict with windows and Java - this is usually what happens to cause the program to just 'disappear.' If you open a CMD window, CD to your sqldeveloper\bin directory, and run the exe from there, you should see some sort of Java 'crash' stack when the GUI goes away suddenly. And in there, you'll see a reference to a windows dll that belongs to the video driver. if that's the case, update that driver, and you should be good
the application settings for your OS user are corrupted. To fix, find your AppData, Roaming Profiles folder for 'SQL Developer' - there should be a system4.1.3... folder in there - rename it, and restart sql developer.
I am developping an application using Entity-Framework and Sql Server Compact 4 in a Visual Studio 2013 project.
Here is the list of add-ons I installed via NuGet :
Microsoft.SqlServer.Compact 4.0.8876.1
EntityFramework 6.1.3
EntityFramework.SqlServerCompact 6.1.3
Then I want to add an ADO.NET Entity Data Model ("Code First from database").
I choose a sdf file that I already have created with SQL Server Compact Toolbox. The Wizard find it and generate a connection string
Data Source=E:\[...]\myDBtest.sdf
Then I click "Next >", the Wizard becomes gray, freezes a few seconds and then closes itself without showing the following step.
At the end, it did not generate anything into my project.
I tried to rebuilt the project before adding the ADO item.
And I even tried to reboot the computer ... with no more success.
Any suggestion or same experience ?
Of course you can use Db First with EF and SQL Server Compact. In order to avoid the error, install the latest Visual Studio Tools for EF (6.1.3) https://www.microsoft.com/en-us/download/details.aspx?id=40762
I have a local database developed in Postgres 9.3. The Postgres server name on my computer is just "localhost". I would like to use the Entity Framework 6 Designer that is built into Visual Studio 13 to automatically generate a data model of EF classes and properties that correspond to the database tables and columns.
As described in various web articles, and using Nuget package manager, I added onto VS 13 these extensions or packages: EF 6, Npgsql, Npgsql Data Provider for EF 6, and Dotconnect express for Postgresql. Afterwards, in the VS 13 Server Explorer window, I was able to connect and see my Postgres tables and columns.
However, I cannot seem to get the EF Designer Wizard to automatically generate the .edmx file. I tried adding an ADO.net data object, selecting "EF Designer from Database" and alternatively, "Code First from Database." When I got to the next screen, I had to choose a Data Source. I tried both "MS SQL Server Database File" and alternatively, "Other." For the Data Provider, there was no other option than ".Net Data Provider for SQL."
In the next screen I tried to create a connection, using SQL server authentication, with user name and password, but I could never get VS 13 to connect or even display the Postgres server like it did in Server Explorer window. For the Server Name I used the same one as I used for the Server Explorer window, ie. localhost.mydatabasename.myschema. For the SQL User, I used the owner of the Postgres database, a Role I created, ie. mydatabasename_role.
When that faied, I tried going into MS SQL Management Studio 2014 to see if I could display the Postgres server there, using the same info used in the Server Explorer window, but I could not get SSMS to display the Postgres server there either. Is there a way to automatically generate the data model and .edmx file as I have been trying, using just VS 13 and SSMS 14? Or do I need to purchase the proprietary / licensed version of dotconnect for Postgres developed by Devart? Thank you in advance.
A Visual Studio plugin is currently being developed which supports the EF Designer Wizard.
You can find it here: https://github.com/npgsql/Npgsql/pull/213
After about a week of research and banging my head againts my desk, I FINALLY got my Npgsql MVC Entity Framework application to work... and work WITH the wizard. The steps are below....
1) Close Visual Studio, then download and install Npgsql PostgreSQL Integration from: https://marketplace.visualstudio.com/items?itemName=RojanskyS.NpgsqlPostgreSQLIntegration
2) Reboot your computer. (yes, it's needed, I promise)
3) Open visual studio and install the following NuGet packages, IN THE ORDER listed and the VERSION listed...
--> EntityFramework version 6.0.0, then clean and rebuild
--> Npgsql 3.1.0, then clean and rebuild
--> EntityFramework6.Npgsql 3.1.1, then clean and rebuild
NOTE: You may need to uninstall other Nuget packages if these will not install in the order and version listed. If so, just make note and add them back later. and yes, you will want to clean/rebuild between each one above.
4) Close all applications and restart your computer. (yes, it's needed, I promise)
5) After your computer restarts, open Visual Studio again and go to your solution. NOTE: I advise you add a new project for your database connection, but this is more a preference than anything.
6) Try using the Entity Framework Wizard again. You should see the Npgsql selections and it shouldn't just crash on you.