JDBC Driver Version

Hello gurus,
How can I tell my existing JDBC Driver version?
We are runninging Netweaver 7.01 SPS5 with an Oracle database on AIX.
Regards,
Bryan

Hi,
Go to /usr/sap/<SID>/JC<XX>/j2ee/configtool directory.
Open 'config.properties' file and you'll see JDBC jar file.
Regards,
Omri

Similar Messages

How can I find the JDBC Driver version

Hi,
How can I find the JDBC Driver version installed on my Sun Solaris machine which
has Weblogic Server 7.0 installed on it. Is there some kind of tool/command to
do so or does Weblogic console say something about it
Thanks
Parikshit Khanna

Parikshit Khanna wrote:
Hi,
How can I find the JDBC Driver version installed on my Sun Solaris machine which
has Weblogic Server 7.0 installed on it. Is there some kind of tool/command to
do so or does Weblogic console say something about it
Thanks
Parikshit KhannaThere is a jdbc DatabaseMetaData call getDriverVersion().
The best thing to do is to download Oracle's latest appropriate
driver from their site, and edit the start-weblogic script to
make sure the downloaded driver is ahead of any weblogic stuff in
the server's classpath. We do ship a driver, but Oracle usually
has a newer better one very soon after that...
Joe

In Trouble with the Oracle JDBC Driver version - 10.1.0.5.0

Hi !
Without any problems i'm using the Oracle JDBC Driver version - 10.1.0.3.0 to access to the
Oracle database (Oracle Database 10g Release 10.2.0.1.0 - 64bit Production).
But exchanging the JDBC Driver 10.1.0.3.0 to 10.1.0.5.0 brings up the following problem:
the statement
con.prepareStatement(sql, resultSetType, resultSetConcurrency, resultSetHoldability)
(with parameters resultSetType = 1003, resultSetConcurrency = 1007, resultSetHoldability= 1)
returns null !
while using the Oracle JDBC Driver version - 10.1.0.3.0 the statement (with same parameters)
returns a correct PreparedStatement.
Every hint or idea is welcome.
Best regards,
Claus

Duplicate post:
In Trouble with the Oracle JDBC Driver version - 10.1.0.5.0
Claus,
Pardon me if I am stating the obvious, but why don't you use the 10.2 JDBC driver with your 10.2 database? The driver is part of the database distribution. Otherwise, you can download the driver from the OTN Web site.
Good Luck,
Avi.

New e-Sourcing 5.0 Install - Error checking JDBC Driver version

Hi All,
I am currently attempting to install an e-Sourcing 5.0 Patch Level E instance on a Windows system using Oracle 10.2.0.3 and WebLogic 8.1 SP4. e-Sourcing's installation and configuration complete without issue. The schema in the database is loaded with the e-Sourcing tables and data.
However, when attempting to deploy the ear file via WebLogic, I receive the following JDBC error:
Error checking JDBC Driver version. Detail: Error: found unsupported JDBC Driver name: Oracle JDBC driver version: 10.1.0.2.0.
The JDBC driver in use is from my Oracle install ..\oracle\product\10.2.0\db_1\jdbc\lib\ojdbc14.jar
I've also tried classes12.jar for versions 9.2.0.8, 10.1.0.2, and 10.2.0.1 but always receive the same error (...driver version: 10.1.0.2.0...) message regardless of the version of driver I am using.
Error Log:
*** Starting Frictionless SRM (5.0.00 E build 08-Apr-2008.16:46) 2009-10-14 20:33:40.656 local3 DEBUG class=ConfigDatabase;server=CAGTAW804886;method=loadFromServletContext();thread=ExecuteThread: '4' for queue: 'weblogic.kernel.System' Cached weblogic.httpd.servlet.reloadCheckSecs=-1 from servlet context
2009-10-14 20:33:40.681 INFO local3 ExecuteThread: '4' for queue: 'weblogic.kernel.System' Disabling logging blackbox support
Unable to start server: unable to connect to the database: oracle [localhost:1521:orcl (SAP/SAP)]:0 reason: Error checking JDBC Driver version. Detail: Error: found unsupported JDBC Driver name: Oracle JDBC driver version: 10.1.0.2.0. Exiting.
Given that the database is loaded with the tables and data I know my instance can connect to the DB. Does anyone know why the deployment would complain that the JDBC driver is incorrect? Is there a way to disable the check and complete the server startup? Is there only a single specific driver that is acceptable for this e-Sourcing version?
Thanks,
Greg
Edited by: Greg Stewart on Oct 15, 2009 3:20 PM

The issue is still occurring.
The Supported Platform documentation indicates that the Oracle JDBC thin driver 10.2.0.1.0 is the supported driver. I have tried both the Classes12.jar and ojdbc14.jar for this version of driver.
What is odd about this error is that it always displays the same message and version #, no matter what version of driver I use.
"found unsupported JDBC Driver name: Oracle JDBC driver version: 10.1.0.2.0" (I execute setup and configuration each time I use a different driver to ensure the ear file is updated)
I have also tried using a different Driver Class path. The installation guides for 5.0 and 5.1 indicate Driver Class as oracle.jdbc.driver.OracleDriver. I have also tried oracle.jdbc.OracleDriver for a few of the versions with no success. I still receive the same error at the same point.
If anyone has run into a similar situation any suggestions or tips to resolving the issue would be appreciated.
Thanks,
Greg

About jdbc driver version?

I use oracle8.05, I want to know what I should do if I want it support JDBC2.0?
just download classes12.zip?
I use jdk1.2.2, so jvm supports the standard of jdbc2.0.

I believe, the following link will answer your question:
http://otn.oracle.com/software/tech/java/sqlj_jdbc/htdocs/install.html
Regards,
Shalu Aggarwal

Multiple versions of the same JDBC driver - OK ?

Hello
We are using SJSAS 8.1 on our production server, it makes access to an Oracle database for user authentication and thus we have a copy of the Oracle thin driver ojdbc14.jar located in the directory.
<sjsas_install>/lib
Each of our web applications also access an Oracle database and thus the build of each web application includes the same oracle jar file in the directory
domains/domain1/applications/j2ee-modules/<name_of_web_app>/WEB-INF/lib/
This is all good and it works OK. In a perfect world where CLOBs had not been invented that would be the end of the story.
However in order to get around the nightmare of JDBC, Oracle and CLOBs I am contemplating using a different version of the JDBC driver for one web app only.
If I were to build one of the web apps to include a different revision of the Oracle JDBC driver, what are the chances of that web application sticking to its intended version and other applications sticking to theirs ?
We currently use Oracle's JDBC driver version 9.2.0.8 I am contemplating using 10.2.0.3 but I do not want to mess with the version used by other web apps.
Any help you can give me would be very much appreciated.
Thank you

Hi Kim,
May be you can try this and see if this works for you. I am not 100% sure if it will work for you, but worth a try I guess. Create a Test WebDynpro project and try the following steps on this project. If they work out correctly and serve the purpose for you only then try them on your actual Web Dynpro project.
1. Create a test Web Dynpro project say "TestWDProject" with Component say "Comp1" and the default views and windows etc.
Also create some working application our of this component and Windows using the Context.
2. Right click the "Comp1" and select Copy.
3. Right click 'Components" node in the project structure and select "Paste"
4.This step will try to paste the copy of Comp1 as a new Component.
5. You can change the Name and Package of the Component.
6.Similarly you'll get the prompts for views,windows etc.
7.Once you have copied everything, Just check if everything looks good.
8.Now you can create a new Application using this new component and the Component Interface View and Deploy it.
9.Test whether the Application created out of this copy works same as the original component.
You can also try to create another Web Dynpro project and paste the Comp1 in the Components node of that new project and perform the same steps.
Again, try with these Test Projects and see if this serves your purpose before applying the steps on actual projects.
Regards,
Ajay

How do I determine JDBC Version? - oracle.jdbc.driver

The following is my path and classpath and script.
Path = D:\oracle\ora90\bin;
D:\oracle\ora90\Apache\Perl\5.00503\bin\mswin32-x86;
C:\Program Files\Oracle\jre\1.1.8\bin;
%SystemRoot%\system32;
%SystemRoot%;
%SystemRoot%\System32\Wbem;
C:\Program Files\Common Files\AdaptecShared\System;
C:\Program Files\Java\j2re1.4.2\bin;
D:\oracle\ora90\LIB
classpath = .;
C:\Program Files\Java\j2re1.4.2\bin;
D:\oracle\ora90\jdbc\lib\
JDBCVersion.java
import java.sql.*;
import oracle.jdbc.driver.*;
class JDBCVersion
public static void main (String args[])
throws SQLException
//DriverManager.registerDriver
//(new oracle.jdbc.driver.OracleDriver());
// Load the Oracle JDBC driver
DriverManager.registerDriver
(new oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection
("jdbc:oracle:thin:scott/tiger@t3100:1521:oracle");
// Create Oracle DatabaseMetaData object
DatabaseMetaData meta = conn.getMetaData();
// gets driver info:
System.out.println("JDBC driver version is " + meta.getDriverVersion());
this throws the following:
D:\oracle\ora90\jdbc\demo\samples\thin\basic\JDBCVersion.java:2: package oracle.jdbc.driver does not exist
import oracle.jdbc.driver.*;
^
D:\oracle\ora90\jdbc\demo\samples\thin\basic\JDBCVersion.java:14: package oracle.jdbc.driver does not exist
(new oracle.jdbc.driver.OracleDriver());

DON'T import the Oracle packages.
That's all hidden from you by the java.sql code. All you do is register the driver and get a connection:
Class.forName("driverClassName");
Connection connection = DriverManager.getConnection("url", "user", "pswd");You might have a "ClassNotFoundException" in your future. I'll bet the JDBC JARs aren't in your CLASSPATH. Make sure they're JARs, not zips. Oracle used to have everything in classes12.zip, but now they've gotten smart and put them in JARs for 9.2.0.1. - MOD

Oracle JDBC Driver 10.1.0.4.0 and IndexOutOfBounds-Exception

Hello all,
we´ve experienced a weird problem using the Oracle JDBC driver version 10.1.0.4.0. While executing SELECT statement we get an ArrayIndexOutOfBounds exception from the JDBC driver. Here´s the stacktrace:
java.lang.ArrayIndexOutOfBoundsException
at java.lang.System.arraycopy(Native Method)
at oracle.jdbc.driver.T4CDateAccessor.saveDataFromOldDefineBuffers(T4CDateAccessor.java:212)
at oracle.jdbc.driver.T4CPreparedStatement.saveDefineBuffersIfRequired(T4CPreparedStatement.java:405)
at oracle.jdbc.driver.OracleStatement.prepareAccessors(OracleStatement.java:859)
at oracle.jdbc.driver.OracleStatement.execute_maybe_describe(OracleStatement.java:949)
at oracle.jdbc.driver.T4CPreparedStatement.execute_maybe_describe(T4CPreparedStatement.java:532)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1037)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2905)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:2946)
at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:124)
We couldn´t find anything on the web on this error. We´re using Weblogic 8.1 SP4 with JDBC version. Does anyone have a hint or an idea what could be the problem here?
Thanks for any help in advance!
Cheers,
Joerg

I may have a related bug, I get a similiar exception when running JIRA...
java.lang.ArrayIndexOutOfBoundsException: -1
at oracle.jdbc.driver.DateTimeCommonAccessor.computeJulianDay(DateTimeCommonAccessor.java:341)
at oracle.jdbc.driver.DateTimeCommonAccessor.getMillis(DateTimeCommonAccessor.java:386)
at oracle.jdbc.driver.DateAccessor.getTimestamp(DateAccessor.java:142)
at oracle.jdbc.driver.OracleResultSetImpl.getTimestamp(OracleResultSetImpl.java:1018)...I tried the 10.1.0.2 and 10.1.0.4 drivers, both throw the same exception. I would try the 10.2 drivers, but they just hang! Gotta love Oracle QA!

Oracle jdbc driver spending 40 seconds to make connection to Oracle db 11g

we are using weblogic 10.3.3 and teh default Oracle11.1.0.7 Driver ojdbc6.jar to talk to Oracle db 11.2.0.1
After reviewing weblogic logs I see that it takes 50 secodns for each connection to db
HHere is a snippet (note I put in a 10 sec login dleay as i was experimenting, butt eh problem still occurs with or without login delay)
<Dec 21, 2010 1:28:19 AM GMT> <Info> <JDBC> <BEA-001516> <Connection Pool "acm_repository" connected to Database: "Oracle", Version: "Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options".>
Dec 21, 2010 1:28:19 AM GMT> <Info> <JDBC> <BEA-001517> <Connection Pool "acm_repository" using Driver: "Oracle JDBC driver", Version: "11.1.0.7.0-Production".>
<Dec 21, 2010 1:28:19 AM GMT> <Info> <JDBC> <BEA-001132> <Initialized statement cache of size "10" for connection in pool "acm_repository".>
<Dec 21, 2010 1:28:19 AM GMT> <Info> <JDBC> <BEA-001066> <Delaying 10 seconds before making a acm_repository pool connection.>
<Dec 21, 2010 1:29:09 AM GMT> <Info> <JDBC> <BEA-001068> <Connection for pool "acm_repository" created.>
There is someting wrong in this environment
I donwloaded the _g version fo teh exact same driver and had weblogic use it so I could generate verbose logs
Here is a snippet fo teh oracle drivers verbose log file . If you notice the key parts
it seems like its spending 40 second to make the connection, goes into a setConnectionDuringExceptionHandling method and creates the connection
can someone shed light on what causes itto go into an exception state
This happens for each and every connection but only in one specific environment
we have other environments which seem towork fine with the exact same product versions except for this environment
Thank you for any guidance on troubleshooting this further
-Y
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection parseConnectionProperty_Object
TRACE_16: Exit
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection readOCIConnectionPoolProperties
TRACE_16: Exit
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection readConnectionProperties
TRACE_16: Exit
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection initialize
TRACE_16: Enter: null, null, null
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection initialize
TRACE_16: Exit
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection needLine
TRACE_16: Enter:
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection needLineUnchecked
TRACE_16: Enter:
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection needLineUnchecked
TRACE_16: Exit
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection needLine
TRACE_16: Exit
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.T4CConnection logon
**TRACE_16: Enter:**
**Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.T4CConnection connect**
**TRACE_16: Enter: "10.135.3.80:1521:EPFDSQA"**
**Dec 21, 2010 1:28:18 AM oracle.jdbc.driver.T4CMAREngine setConnectionDuringExceptionHandling**
**TRACE_16: Enter:**
**Dec 21, 2010 1:28:18 AM oracle.jdbc.driver.T4CMAREngine setConnectionDuringExceptionHandling**
TRACE_16: ExitDec 21, 2010 1:28:18 AM oracle.jdbc.driver.DBConversion findDriverCharSet
TRACE_16: Enter: 178, 8100
Dec 21, 2010 1:28:18 AM oracle.jdbc.driver.DBConversion findDriverCharSet
TRACE_16: return: 178
Dec 21, 2010 1:28:18 AM oracle.jdbc.driver.DBConversion findDriverCharSet
TRACE_16: Exit
Dec 21, 2010 1:28:18 AM oracle.jdbc.driver.DBConversion <init>
TRACE_16: Enter: 178, 178, 2000
Dec 21, 2010 1:28:18 AM oracle.jdbc.driver.DBConversion init
TRACE_16: Enter: 178, 178, 2000

I would file an oracle jdbc bug to begin with, but I am guessing the driver is simply waiting
for the DBMS to respond, so yo may need a good DBA to see what the DBMS thinks is going
on at the time. I did hear of a case where the DBMS was doing some auditing, logging
some info during every login. This info was being written to an OS file which just happened
to be remote-mounted and would occasionally take 30 seconds, which caused connection
requests to timeout at the driver end.... WebLogic is just asking the driver for a connection
using your properties, so it's not involved directly with the problem....

Load JDBC-Driver dynamically with JarClassLoader

Hey!
I have a problem loading JDBC drivers dynamically with a JarClassLoader:
Code:
public class URLLoaderTest {
public static void main(String[] args) {
try {
    URL[] urlList = {new File("D:\\jbuilder5\\SQLServerJDBC\\lib\\mssqlserver.jar").toURL(),
                     new File("D:\\jbuilder5\\SQLServerJDBC\\lib\\msbase.jar").toURL(),
                     new File("D:\\jbuilder5\\SQLServerJDBC\\lib\\msutil.jar").toURL()};
    ClassLoader classLoader = new URLClassLoader(urlList);
    Class c = Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver",true,classLoader);
    Object d = c.newInstance();
    DriverManager.registerDriver((Driver)d);
    // DriverManager.getDrivers()    Enumeration is empty
    Connection conn = DriverManager.getConnection("jdbc:microsoft:sqlserver://Server:1433","test","test");
    DatabaseMetaData meta = conn.getMetaData();
    System.out.println("JDBC driver version is " + meta.getDriverVersion());
catch (Exception e) {System.out.println(e.getMessage());}
}Problem:
Till the DriverManager registraton everything is ok.
The registerDriver Method throws no exception but if I call DriverManager.getDrivers() after calling the registerDriver Method an empty Enumeration is returned.
So the driver is not loaded and DriverManager.getConnection throws an Exception (no suitable driver).
If I include the driver jars into the Classpath everything is running (but that isn't what I want to do).
Is there a solution for this problem? Maybe it is possible to load the data into the AppClassLoader??!!
Thanx in advance.

Found a solution!
For everyone who is interested:
public class URLLoaderTest {
public static void main(String[] args) {
try {
    URL[] urlList = {new File("D:\\jbuilder5\\SQLServerJDBC\\lib\\mssqlserver.jar").toURL(),
                     new File("D:\\jbuilder5\\SQLServerJDBC\\lib\\msbase.jar").toURL(),
                     new File("D:\\jbuilder5\\SQLServerJDBC\\lib\\msutil.jar").toURL()};
    ClassLoader classLoader = new URLClassLoader(urlList);
    Class c = Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver",true,classLoader);
    Object d = c.newInstance();
    Driver driver = (Driver)d;
    Properties prop = new Properties();
    prop.setProperty("user","test");
    prop.setProperty("password" ,"test");
    Connection conn = driver.connect("jdbc:microsoft:sqlserver://test:1433",prop);
    System.out.println("JDBC driver version is " + meta.getDriverVersion());
catch (Exception e) {System.out.println(e.getMessage());}
}

Urg:Executing SQL From Java App using Jdbc Driver

Hi
I am using JDBC Driver version 9.0.1.1.0.
I am running this in Thin Client Mode
My Code Snippet Looks Like This:=
==========================================================
String url = "jdbc:oracle:thin:@localhost:1521:VpDb";
String userName = "scott";
String password = "tiger";
Connection conn = null ;
Statement st = null ;
ResultSet rs = null ;
String categoryCode="ABC";
try
conn = DriverManager.getConnection (url, userName, password);
st = conn.createStatement ();
String sqlStatement = "Select Count(*) From News Where CategoryCode=" +"\'" + categoryCode + "\'" + ";";
System.out.println(sqlStatement);
rs = st.executeQuery ( sqlStatement );
if( rs.next() )
System.out.println("Headline Exists");
else
System.out.println("No Headline Exists");
catch (SQLException e )
System.out.println();
System.out.println (" SQL ERROR IN IS_NEWS_EMPTY: " + e) ;
=========================================================
I have added the classes12.zip and nls_charset12.zip in the classpath.
Now when i run this it gives me an error saying the following error message:-
SQL ERROR IN IS_NEWS_EMPTY: java.sql.SQLException: ORA-00911: invalid character
Can anyone help me with this as to whats going wrong because the exact equivalent of my sqlStamenet runs on SQL command line but not from java code.Why??
Any Help appreciated
Thanks
Mum

I think it is complaining about the ";" that you add at the end of your string. You don't need to add that to the query.

Jdbc driver creates new thread for each statement with a query timeout set

I am profiling a web application that is using the Microsoft JDBC driver, version 1.1 to connect to a sql server 2005 database. Each java.sql.Statement that is created, within the application, gets a query timeout value set on it ( statement.setQueryTimeout(...) ).
I have discovered that the JDBC driver creates a new thread to monitor each Statement and the query timeout value. When the application is under load these threads are getting created faster then they are being destroyed and I am concerned that this will cause a performance problem in production.
One option I have is to remove the query timeout value and the monitor threads will not be created, another is to change JDBC drivers.
I'm curious is there any way to control this behavior so that these threads are not created or are managed more efficiently. Is there a workaround that anyone is aware of? Is this considered a bug?
I have found a similar bug here for the 2000 driver:
http://support.microsoft.com/default.aspx/kb/894552
Cheers

Hi,
Thank you for using the Microsoft SQL Server JDBC driver. You are correct that a new thread is started to monitor the query timeout when a statement is executed. This is a potential performance issue that we may look at addressing in the upcoming v1.2 release. The current behavior is not configurable. The only workaround with the v1.1 driver is to limit your use of query timeouts to only those statements which you reasonably might expect to actually time out.
We do take customer feedback very seriously, so if anyone else is concerned about this particular issue, please chime in and we will be able to give it appropriate weight.
--David Olix [MSFT]

Servlets/ oracle jdbc driver

i am trying to connect to my oracle database within a servlet. the driver i want to use is a oracle jdbc oci8 driver, but but unfortuntately i always get an unsatisfied link error (this only happens in servlets)
the errormessage i get is:
java.lang.UnsatisfiedLinkError: no ocijdbc8 in java.library.path
at org.apache.jserv.JServServletManager.load_init(JServServletManager.java:589)
at org.apache.jserv.JServServletManager.loadServlet(JServServletManager.java:498)
at org.apache.jserv.JServConnection.processRequest(JServConnection.java:269)
at org.apache.jserv.JServConnection.run(JServConnection.java:188)
at java.lang.Thread.run(Thread.java:484)
can anyone help me?
thx, laurenz
null

make sure your servlet engine platform has an oracle client installed matching the jdbc driver version being used.
You must also properly configure your servlet engine to access the jdbc oci driver's executables.

Upgrade MS SQL 2005 platform to MS SQL 2008 - Update the JDBC driver...

Hello to all,
This is the second post that I created reporting this error because in the first one I open this message in group of "SAP on SQL Server" but without any kind of help from community:
My problem is...
I´m planning to do an upgrade of a sap system (SAP ECC 6.0) from SQL Server 2005 to a SQL Server 2008 but I´m facing with a little problem. This system has two stacks - ABAP + JAVA - and because of that the Upgrade Guide to MS SQL Server 2008 describe which are the requirements for this upgrade DB platform, and one of them is this:
"If you use a Java system, you have updated the JDBC driver as described in SAP Note 639702"
... the updated of JDBC driver when we have in system a Java part, like it has in this case! But I´m with a serious problems to find in SAP System Files in Windows 2003 Server the four files that is mentioned in that note 639702. I can´t find it anywhere... in note says:
Depending on the SAP release and the system configuration, the driver files base.jar, util.jar, sqlserver.jar, and spy.jar are available in an installed system at:
(NetWeaver'04, Java:) usrsap<SAP SID>JC<InstanceNumber>j2eejdbc
(NetWeaver'04, ABAP+Java:) usrsap<SAP SID>DVEBMGS<InstanceNumber>j2eejdbc
(NetWeaver 2004s:) usrsap<SAPSID>SYSexe<NUC|UC>Platformmssjdbc
But... still I didn´t find them! I also read other note 1109274 - New JDBC driver for NetWeaver 7.0 and higher but even so I still can´t find it!
Can you help me to find this files on my operation system? I have to update that JDBC... but of course for this task I have to find it first!!!
Best regards,
João Dimas - Portugal

Hi,
Have you considered the possibility that the directory that was supposed to contain the jdbc drivers has been replaced by a recent kernel upgrade and you never noticed?
Anyway, looking forward, put in a new set of JDBC drivers in the correct location.
Also, with reference to the following point from the first note:
Check your JDBC Driver version before you download it. To do this, unpack the attached check tool SAPCheckVersion in the relevant JDBC directory (refer to the previous paragraph). Then open a command prompt there and execute the following command:
SAPCheckVersion.cmd <server name> <username> <password>
Replace <server name> with the name of the database server, <username> and <password> with the logon data of an SQL user (for example, sa or SAP<SID>DB). If you call SAPCheckVersion.cmd without a parameter, the system displays detailed help. The tool supports both DataDirect and Microsoft drivers.
*The download name tells you which version of the driver you need to download from SAP Service Marketplace.*
Run this SAPCheckVersion and find out which drivers you need to download and then download them and use them.
Regards,
Shitij

Duplicate class definition: oracle/jdbc/driver/OracleDriver

Hi
I using Jdeveloper 10.1.3.3 and I tried to add jdbc driver version 11.1.0.6.0 to Project by add Library to the project property. And I tried to run my application when step to connect database the program will occur the error.
This below is the error
500 Internal Server Error
oracle.classloader.util.AnnotatedLinkageError: duplicate class definition: oracle/jdbc/driver/OracleDriver
     Invalid class: oracle.jdbc.driver.OracleDriver
     Loader: current-workspace-app.root:0.0.0
     Code-Source: /D:/oracle/jdbc/11/ojdbc5.jar
     Configuration: <library> in /D:/Jdev10133/jdev/mywork/Trainning/Trainning-oc4j-app.xml
     Dependent class: java.sql.DriverManager
     Loader: jre.bootstrap:1.5.0_06
     Code-Source: unknown
     Configuration: jre bootstrap
     at oracle.classloader.PolicyClassLoader.findLocalClass (PolicyClassLoader.java:1462) [D:/Jdev10133/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@17332331]     at oracle.classloader.SearchPolicy$FindLocal.getClass (SearchPolicy.java:167) [D:/Jdev10133/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@17332331]     at oracle.classloader.SearchSequence.getClass (SearchSequence.java:119) [D:/Jdev10133/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@17332331]     at oracle.classloader.SearchPolicy.loadClass (SearchPolicy.java:645) [D:/Jdev10133/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@17332331]     at oracle.classloader.PolicyClassLoader.askParentForClass (PolicyClassLoader.java:1289) [D:/Jdev10133/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@17332331]     at oracle.classloader.SearchPolicy$AskParent.getClass (SearchPolicy.java:68) [D:/Jdev10133/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@17332331]     at oracle.classloader.SearchSequence.getClass (SearchSequence.java:119) [D:/Jdev10133/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@17332331]     at oracle.classloader.PolicyClassLoader.internalLoadClass (PolicyClassLoader.java:1674) [D:/Jdev10133/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@17332331]     at oracle.classloader.PolicyClassLoader.loadClass (PolicyClassLoader.java:1635) [D:/Jdev10133/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@17332331]     at oracle.classloader.PolicyClassLoader.loadClass (PolicyClassLoader.java:1620) [D:/Jdev10133/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@17332331]     at java.lang.ClassLoader.loadClassInternal (ClassLoader.java:319) [jre bootstrap, by jre.bootstrap:1.5.0_06]     at java.lang.Class.forName0 (Native method) [unknown, by unknown]     at java.lang.Class.forName (Class.java:242) [jre bootstrap, by jre.bootstrap:1.5.0_06]     at java.sql.DriverManager.getCallerClass (DriverManager.java:442) [jre bootstrap, by jre.bootstrap:1.5.0_06]     at java.sql.DriverManager.getConnection (DriverManager.java:519) [jre bootstrap, by jre.bootstrap:1.5.0_06]     at java.sql.DriverManager.getConnection (DriverManager.java:171) [jre bootstrap, by jre.bootstrap:1.5.0_06]     at com.util.Util.getConnection (Util.java:14) [D:/Jdev10133/jdev/mywork/Trainning/DBProgramming/classes/ (from <classpath> in D:\Jdev10133\jdev\mywork\Trainning\DBProgramming\public_html), by current-workspace-app.web.dbprogram:0.0.0]     at com.blob.BLOBTest.uploadFileToDB (BLOBTest.java:37) [D:/Jdev10133/jdev/mywork/Trainning/DBProgramming/classes/ (from <classpath> in D:\Jdev10133\jdev\mywork\Trainning\DBProgramming\public_html), by current-workspace-app.web.dbprogram:0.0.0]     at com.upload.doPost (upload.java:28) [D:/Jdev10133/jdev/mywork/Trainning/DBProgramming/classes/ (from <classpath> in D:\Jdev10133\jdev\mywork\Trainning\DBProgramming\public_html), by current-workspace-app.web.dbprogram:0.0.0]     at javax.servlet.http.HttpServlet.service (HttpServlet.java:763) [D:/Jdev10133/j2ee/home/lib/servlet.jar (from <code-source> (ignore manifest Class-Path) in META-INF/boot.xml in D:\Jdev10133\j2ee\home\oc4j.jar), by api:1.4.0]     at javax.servlet.http.HttpServlet.service (HttpServlet.java:856) [D:/Jdev10133/j2ee/home/lib/servlet.jar (from <code-source> (ignore manifest Class-Path) in META-INF/boot.xml in D:\Jdev10133\j2ee\home\oc4j.jar), by api:1.4.0]     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.ServletRequestDispatcher.invoke (ServletRequestDispatcher.java:713) [D:/Jdev10133/j2ee/home/lib/oc4j-internal.jar (from <code-source> in META-INF/boot.xml in D:\Jdev10133\j2ee\home\oc4j.jar), by oc4j:10.1.3]     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.ServletRequestDispatcher.forwardInternal (ServletRequestDispatcher.java:370) [D:/Jdev10133/j2ee/home/lib/oc4j-internal.jar (from <code-source> in META-INF/boot.xml in D:\Jdev10133\j2ee\home\oc4j.jar), by oc4j:10.1.3]     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpRequestHandler.doProcessRequest (HttpRequestHandler.java:871) [D:/Jdev10133/j2ee/home/lib/oc4j-internal.jar (from <code-source> in META-INF/boot.xml in D:\Jdev10133\j2ee\home\oc4j.jar), by oc4j:10.1.3]     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpRequestHandler.processRequest (HttpRequestHandler.java:453) [D:/Jdev10133/j2ee/home/lib/oc4j-internal.jar (from <code-source> in META-INF/boot.xml in D:\Jdev10133\j2ee\home\oc4j.jar), by oc4j:10.1.3]     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpRequestHandler.serveOneRequest (HttpRequestHandler.java:221) [D:/Jdev10133/j2ee/home/lib/oc4j-internal.jar (from <code-source> in META-INF/boot.xml in D:\Jdev10133\j2ee\home\oc4j.jar), by oc4j:10.1.3]     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpRequestHandler.run (HttpRequestHandler.java:122) [D:/Jdev10133/j2ee/home/lib/oc4j-internal.jar (from <code-source> in META-INF/boot.xml in D:\Jdev10133\j2ee\home\oc4j.jar), by oc4j:10.1.3]     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpRequestHandler.run (HttpRequestHandler.java:111) [D:/Jdev10133/j2ee/home/lib/oc4j-internal.jar (from <code-source> in META-INF/boot.xml in D:\Jdev10133\j2ee\home\oc4j.jar), by oc4j:10.1.3]     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run (ServerSocketReadHandler.java:260) [D:/Jdev10133/j2ee/home/lib/oc4j-internal.jar (from <code-source> in META-INF/boot.xml in D:\Jdev10133\j2ee\home\oc4j.jar), by oc4j:10.1.3]     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run (ReleasableResourcePooledExecutor.java:303) [D:/Jdev10133/j2ee/home/lib/oc4j-internal.jar (from <code-source> in META-INF/boot.xml in D:\Jdev10133\j2ee\home\oc4j.jar), by oc4j:10.1.3]     at java.lang.Thread.run (Thread.java:595) [jre bootstrap, by jre.bootstrap:1.5.0_06]
Please help to suggest me. How should I do to let out this error?
Thanks

many people use the two interchangeably, though technically it can mean something different.
What you get back from a call to newInstance() is the same as what you'd get when using the new keyword and no constructor arguments, a reference to an instance of a class (there are other ways to dynamically create an instance using other constructors).
"Creating a class object" technically means loading the class which causes a Class instance (so an instance of the class Class) to be created for that particular class, making the class available to the JVM for instantiation of instances.
newInstance() and its sisters are useful for when the class to be instantiated is not known (or even doesn't exist) when compiling the class that needs to instantiate it.
This is of course the case with JDBC. The people creating the JVM can't know what driver classes will be out there at some point in the future (and if they did know and have access to all of them in the past it would still be foolish to have them all hardwired into the JVM).

JDBC Driver Version

Similar Messages

Maybe you are looking for