I am using Oracle SQL V. 4.1.3.
I have installed it successfully, and established connections to our database. I see the db connections, but when expanding them this error message shows up:
Driver Class not found. Verify the Driver location. Vendor Code 0
I installed Ms JDBC driver 6.0 for SQL Server and unpacked it in my ProgramFiles. I then went to ControlPanel-SystemProperties and added the sqljdbc42.jar as <installation directory>\sqljdbc_<version>\<language>\sqljdbc.jar under my existing environment variable called PATH.
Now when I go to SQL Developer Properties, I see JDBC.JAR added to Java.library.path but not to java.class.path. Is this the reason I am still getting error message? How do I go about fixing it? Or is there some other issue at hand?
I also experienced the reported error. It appears one can go to preferences of a connection, click on 'Test' to test the connection and then it suddenly works again... Very strange, but it worked. You do have to do this for all connections, but hey, it worked.
Need to set driver path inside Preference -> Database -> 3rd Party JDBC driver -- in case of mssql add -- jtds-1.3.1.jar.
Nevermind, I was just little stupid. All I had to do was add Third Party JDBC Driver path under Preferences in SQL Developer and it works like a Charm.
Related
When I try to browse my project through IIS, I get the below error
"The provider is not compatible with the version of Oracle client"
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Oracle.DataAccess.Client.OracleException: The provider is not compatible with the version of Oracle client
enter image description here
Please let me know what are the steps that i should perform to resolve this error. Thanks!
Assuming you have Oracle client installed and you have reference to the Oracle.DataAccess.dll in your project, check its version. Go to <your oracle client path>\odp.net folder and find there *.dll file with same name. Compare versions. Most likely issue is that DLL in your dir is different and does not match your installed Oracle Client. Use DLL that matches client.
And tell your boss to stop using Oracle client and use Oracle.ManagedDataAccess.dll
Now, there could be other issues causing this but this is minimum to check before moving further.
In my case I got the same error message when migrating to the newer Oracle.ManagedDataAccess.dll and forgot to remove the existing Oracle.DataAccess.dll, resulting in a lot of ambiguity.
Everything worked once the older reference was removed.
Last time I had this problem in an c# project I had to add Oracle.DataAccess.dll reference from my Oracle client directory.
I have been using Squirrel SQL client to access Vertica (on a Windows 7 machine). It was working fine until last week but I am unable to open the Squirrel anymore and it throws an error
"error occurred initializing plugin: oracle".
I haven't installed any additional plugins and this has been working fine until last week. Can someone let me know how to debug this error?
Delete codecompletionprefs.xml file, hope it will be better. My problem has been solved.
C:\Users[Your user name].squirrel-sql\plugins\codecompletion
Was just a Java installation issue...apparently didn't work with Java 7...installing Java 6 solved the issue for me
I am trying to get some JasperReports working. To build them I am using iReport.
I need to connect to an MS SQL Server db. In iReport the MS JDBC driver is listed. However when I go to test the connection I get a class not found error.
I have made sure that I have the driver in my class path
echo $CLASSPATH
/home/USER/dev/jtds/jtds-1.2.5.jar
Has any one run into these sorts of issues and found a way around?
The key idea is "In iReport the MS JDBC driver is listed." Somewhat surprisingly... this means nothing at all.
Well... it means that the iReport team thinks this is a common enough driver that they put it into the drop down list so that you would not have to type it. It does not mean that the driver is available.
As Dan has already alluded to in the comments, the solution is to add the relevant .jar file (jtds-1.2.5.jar) to iReport's classpath using the menu Tools → Options. (On OS X it's the menu iReport → Preferences).
go to the ireport there u will see one icon on top and click it it will show paths there u establish a connection to jdbc and add ojdbc 14 jar to it . that's it simple and add that jar to classpath.
I refer this to enable the debugger in the PostgreSQL server in order to debugging the plpgsql function by stepping through the code using pgadmin.
I have already set shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll' in the postgresql.conf, run pldbgapi.sql , and restarted the server.
These steps should have been run successfully and plugin_debugger.dll should be loaded successfully as can be verified by using the command show shared_preload_libraries, and I can see the debugging option in the context menu with a right click on a function in pgAdmin.
When choosing "Debugging" --> Debug, a window pops up to allow me to enter the values for the input parameters. But after that, when I press OK, it does not respond at all.
Any ideas or did I miss something in the setup of the debugger on the server?
I am using PostgreSQL 8.3 and pgAdmin 1.14
You have to enable debugging in two places. On PGAdmin and on the database itself. That article you referenced does a wonderful job explaining it but there were some nuances.
PGAdmin
When updating your postgresql.conf file to load the debugging library, I was running PGAdmin on Windows so the file was here:
C:\Program Files\PostgreSQL\9.4\data\postgresql.conf
And the path to the plugin_debugger.dll was actually
$libdir/plugin_debugger.dll
not
$libdir/plugins/plugin_debugger.dll
as specified in the article. So your postgresql.conf would need a line like this
shared_preload_libraries = '$libdir/plugin_debugger.dll'
Search for the actual .dll if you're in doubt. If you're on Linux the file you'll be looking for is plugin_debugger.so. Don't forget that changing the postgresql.conf file will require a restart for the change to take effect.
PostgreSQL Database
Assuming you're running your PostgreSQL database on a Linux server this gist does an excellent job at explaining how to download the dependencies for enabling debugging. Make sure you're running as root when you install.
The part that's easy to miss is issuing the command against the actual database you want to debug. For newer versions on PostgreSQL all you'll need to do is this:
CREATE EXTENSION IF NOT EXISTS pldbgapi;
If that doesn't return an error, you should be good to go.
Some additional things of note:
As mentioned above, you can only debug when running as a super user account
From their docs you can only debug pl/pgsql functions. So if your function says something like LANGUAGE c PGAdmin won't even show a right-click Debug menu option when you select the function. Look for something that has LANGUAGE plpgsql and the Debug menu should show.
Ken,
Have you tried pgAdmin 1.8 to rule out issue with PgAdmin 1.14/ PostgreSQL 8.3 interaction. It's been a while since I've used 8.3 and for the article I wrote -- which you are referring to, I was testing with 1.14/ PostgreSQL 9.1 so it could very well be an issue with the interaction with older version. Unfortunately I don't have a 8.3 anymore to test with.
I vaguely remember having the issue you had once, but it was when I had another shared library in my postgresql.conf in addition to the pldebugger. Can't remember which one that was, but removing the other shared library fixed my issue.
Hope some of these suggestions help,
Regina
I had the same problem.
Make sure the only shared lib you´re loading in the postgres.conf is the debugger.
Nothing else. Not even the profiler.
If you get a SSL error when trying to debug a function, reconnect to the server.
Ok, I am probably just shooting air with this question.. but I have no idea what's happening and I have been banging my head against it for the last couple days.
I have a crystal report version 12.2.0.290... I built this report against an Oracle connection string (not ODBC as it was giving me errors to use a stored procedure as a data source). Anyway, so the report was connecting to the database fine.. and I was able to build the entire report.. refreshing data with every change I made etc.. Once I was finished.. I closed the crystal report. When I open the report again and try to refresh the data I get the error "Unknown Database Connector Error in Crystal Reports". I get this error when I try to run the report straight from crystal reports.. or from the .NET wrapper that we built for this report. I also get the same error when I run the report (in CR) from another machine. In fact I get this error just trying to connect to an any Oracle database from that report..
The really strange thing is that if I open another report that we built a while ago.. I can connect to the same exact data source from it and it I go to File -> Open and open the first report.. I can connect to the Oracle data source and the report runs fine.. I can reproduce this strange behavior at will.. I don't know what is going on.... and I have been staring at this problem for the longest while.. if anyone has any ideas I will be more than happy to try them out...
Thanks!!
This is The Resolution:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/d2811b33-2c2c-43d1-af51-9c54e9ad7920/unknown-database-connector-error?forum=wpf
I've fixed the problem, I just needed those lines:
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
</startup>
If using a stored procedure as your data source, make sure it RETURNS a RESULT SET. Once I added a 'SELECT * FROM dbo.mytable', the error went away. :-)
Are you using the latest Oracle Data Access Components?
How to check which version you are using:
During installation of ODAC, consult the ODAC Installer screen.
After installation, see the history.html file in your ODAC installation directiory.
At design-time, select Oracle | About ODAC from the main menu of your IDE.
At run-time, check the value of the OdacVersion and DACVersion constants.
Note: This was originally a comment but added as an answer after OP response on how to check for the version of ODAC