What sequence weblogic load the jdbc driver

I config a oracle thin driver,Oracle oci driver, weblogic oci
driver. But every time I reboot the weblogic ,I found the
sequence is not all the same, I changed the config.xml manally
but seems can not work.
So I want to know how the weblogic load the driver,and can I
make the sequence of load driver not change?
Thanks a lot

In order to create pools in a ordered sequence you may have to create a
startup class that dynamically creates these pools for you in sequence.
sree
"Eric.Nie" <[email protected]> wrote in message
news:[email protected]..
I config a oracle thin driver,Oracle oci driver, weblogic oci
driver. But every time I reboot the weblogic ,I found the
sequence is not all the same, I changed the config.xml manally
but seems can not work.
So I want to know how the weblogic load the driver,and can I
make the sequence of load driver not change?
Thanks a lot

Similar Messages

Load the JDBC driver

hi every one,
Iam trying to make a connection to Oracle9i using java, i know that first i have to load the JDBC driver and then establish a connection to the database but if faced 2 problems
1- I don't know the name of the jdbc driver. if any body can show me how can i know it.
2- when connecting to the database i have to provide the server name and the port number unfortunatly i don't know both.
so if any one can help to find them.
Thanks alot

hi every one,
Iam trying to make a connection to Oracle9i using
java, i know that first i have to load the JDBC
driver and then establish a connection to the
database but if faced 2 problems
1- I don't know the name of the jdbc driver. if any
body can show me how can i know it.
It depends on what driver you are using. Look it up and search the Oracle site. Or look through the gazillion examples in the JDBC forum.
2- when connecting to the database i have to provide
the server name and the port number unfortunatly i
don't know both.
Talk to your DBA. There is no way we could or should be able to help you on this one.

Unable to load the jdc driver

Hi,
I am using mckoi, but I don't succed in loading the jdbc driver:
Class.forName("com.mckoi.JDBCDriver");This line throw a ClassNotFoundException. But:
cd $CLASSPATH; ls | grep mkjdbc.jar
mkjdbc.jar
So the jar file is in the CLASSPATH.
I try also:
import com.mckoi.JDBCDriver;But when it compile:
javac ConnectToServerDemo.java
ConnectToServerDemo.java:2: package com.mckoi does not exist
import com.mckoi.JDBCDriver;
Something strange:
java -cp mckoidb.jar com.mckoi.tools.JDBCQueryTool -u "admin_user" -p "aupass00"
It's work very well !
I don't understand and I have no idea.
It will be fine if someone can help me.

You should follow duffymo's advice and explicitly pass classpath on the command line.
However, classpath environment variable can work. It appears you have the directory in which the jar file resides in the classpath. Java won't find JARs automatically, you have to include the name of the JAR file explicitly.
E.g., if your jar is located in "/mydir" and your classpath environment variable contains an entry "/mydir" change it to "/mydir/mckoidb.jar", or better yet add that in addition to "/mydir" so classes are also found.
Tim

Help - Could not load 'oracle.jdbc.driver.OracleDriver ...

I'm using oci8 to connect to the Oracle database.
URL: jdbc:oracle:oci8:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(PORT=1527)(HOST=testhost)))(CONNECT_DATA=(SID=fnoe2pa)))
When I tried to start the weblogic server, I got the following errors:
Can you suggest what I should do next (step-wise)??? Thanks, Bobby
<Sleeping in createResource()>
####<15/08/2002 14:09:43> <Error> <JDBC> <qawebmethods> <myserver>
<main> <system> <> <001060> <Cannot startup connection pool
"pool/test_myapp" weblogic.common.ResourceException:
Could not load 'oracle.jdbc.driver.OracleDriver
If this is a type-4 JDBC driver, it could occur if the JDBC
driver is not in the system CLASSPATH.
If this is a type-2 JDBC driver, it may also indicate that
the Driver native layers(DBMS client lib or driver DLL)
have not been installed properly on your system
or in your PATH environment variable.
This is most likely caused by one of the following:
1. The native layer SO, SL, or DLL could not be found.
2. The file permissions on the native layer SO, SL, or DLL
have not been set properly.
3. The native layer SO, SL, or DLL exists, but is either
invalid or corrupted.
For more information, read the installation documentation
for your JDBC Driver, available from:
http://e-docs.bea.com
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:212)
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
     at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:705)
     at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
     at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:650)
     at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy31.updateDeployments(Unknown Source)
     at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
     at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
     at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy42.start(Unknown Source)
     at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
     at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
     at weblogic.management.Admin.finish(Admin.java:644)
     at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
     at weblogic.Server.main(Server.java:35)
>
####<15/08/2002 14:09:43> <Info> <JDBC> <qawebmethods> <myserver>
<main> <system> <> <001082> <Creating Data Source named
jdbc/test_myapp for pool pool/test_myapp>
####<15/08/2002 14:09:43> <Info> <JDBC> <qawebmethods> <myserver>
<main> <system> <> <001070> <Checking existence of connection pool
pool/test_myapp requested by user system>
####<15/08/2002 14:09:43> <Error> <JDBC> <qawebmethods> <myserver>
<main> <system> <> <001059> <Error during Data Source creation:
weblogic.common.ResourceException: DataSource(jdbc/test_myapp) can't
be created with non-existent Pool (connection or multi)
(pool/test_myapp)>
####<15/08/2002 14:09:50> <Info> <EJB> <qawebmethods> <myserver>
<main> <system> <> <010008> <EJB Deploying file: myapp-ejb.jar>
####<15/08/2002 14:09:50> <Warning> <J2EE> <qawebmethods> <myserver>
<main> <system> <> <160007> <You are running WebLogic Server with J2EE
1.3 features enabled. The implementation of specific J2EE 1.3 features
(EJB 2.0, JSP 1.2, Servlet 2.3, and J2EE Connector Architecture 1.0)
in BEA WebLogic Server 6.1 is of a non-final version of the
appropriate specification. It is subject to change in future releases
once the specification becomes finalized. This may cause application
code developed for BEA WebLogic Server 6.1 that uses the new features
of J2EE 1.3 to be incompatible with the J2EE 1.3 platform supported in
future releases of BEA WebLogic Server.>
####<15/08/2002 14:09:59> <Error> <J2EE> <qawebmethods> <myserver>
<main> <system> <> <160001> <Error deploying application myapp-ejb:
Unable to deploy EJB: Counter from myapp-ejb.jar:
The DataSource with the JNDI name: jdbc/test_myapp could not be
located. Please ensure that the DataSource has been deployed
successfully and that the JNDI name in your EJB Deployment descriptor
is correct.
>
####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101053> <[HTTP myserver] Loading web app: myapp>
####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101059> <[myserver] Loading myapp from WAR file:
C:\bea\wlserver6.1\.\config\mydomain\applications\.wlnotdelete\wlap31483\myapp.war>
####<15/08/2002 14:09:59> <Warning> <J2EE> <qawebmethods> <myserver>
<main> <system> <> <160007> <You are running WebLogic Server with J2EE
1.3 features enabled. The implementation of specific J2EE 1.3 features
(EJB 2.0, JSP 1.2, Servlet 2.3, and J2EE Connector Architecture 1.0)
in BEA WebLogic Server 6.1 is of a non-final version of the
appropriate specification. It is subject to change in future releases
once the specification becomes finalized. This may cause application
code developed for BEA WebLogic Server 6.1 that uses the new features
of J2EE 1.3 to be incompatible with the J2EE 1.3 platform supported in
future releases of BEA WebLogic Server.>
####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101031>
<[WebAppServletContext(1412030,myapp,/myapp)] extracting classfiles to
C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\wlap31483\WEB-INF\_tmp_war_myapp:>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101032>
<[WebAppServletContext(1412030,myapp,/myapp)] extracted classfiles
successfully...>
####<15/08/2002 14:10:04> <Info> <HTTP Session> <qawebmethods>
<myserver> <main> <system> <> <100037> <Creating SessionContext of
type: memory for webapp: /myapp>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101047>
<[WebAppServletContext(1412030,myapp,/myapp)] registering classpath
servlet with initArgs 'null'>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101047>
<[WebAppServletContext(1412030,myapp,/myapp)] registering getior
servlet with initArgs 'null'>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101047>
<[WebAppServletContext(1412030,myapp,/myapp)] registering tunneling
servlets with initArgs 'wl-dispatch-policy=direct'>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101047>
<[WebAppServletContext(1412030,myapp,/myapp)] registering JSPServlet
with initArgs '[JspConfig:
verbose=true,packagePrefix=jsp_servlet,-compiler=javac,compileFlags=,workingDir=C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\wlap31483\WEB-INF\_tmp_war_myapp,pageCheckSeconds=1,superclass=null,keepgenerated=false,precompileContinue=false,compilerSupportsEncoding=true,encoding=null,defaultfilename=index.jsp,compilerclass=null,noTryBlocks=false]'>
####<15/08/2002 14:10:04> <Debug> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101097> <Registering ServletContext:
"myapp:/myapp">
####<15/08/2002 14:10:04> <Info> <J2EE> <qawebmethods> <myserver>
<main> <system> <> <160003> <Deployed : myapp>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101133> <Initializing WEB server myserver>
####<15/08/2002 14:10:04> <Notice> <Management> <qawebmethods>
<myserver> <main> <system> <> <141052> <Application Poller started for
development server.>
####<15/08/2002 14:10:04> <Notice> <WebLogicServer> <qawebmethods>
<myserver> <ListenThread> <system> <> <000202> <ListenThread listening
on port 7001>
####<15/08/2002 14:10:04> <Info> <NT Performance Pack> <qawebmethods>
<myserver> <ListenThread> <system> <> <000000> <NATIVE: NTSocketMuxer
was built on Nov 1 2001 16:39:28
>
####<15/08/2002 14:10:04> <Notice> <WebLogicServer> <qawebmethods>
<myserver> <SSLListenThread> <system> <> <000202> <SSLListenThread
listening on port 7002>
####<15/08/2002 14:10:05> <Notice> <Management> <qawebmethods>
<myserver> <main> <system> <> <141030> <Starting discovery of Managed
Server... This feature is on by default, you may turn this off by
passing -Dweblogic.management.discover=false>
####<15/08/2002 14:10:05> <Notice> <WebLogicServer> <qawebmethods>
<myserver> <main> <system> <> <000331> <Started WebLogic Admin Server
"myserver" for domain "mydomain" running in Development Mode>
####<15/08/2002 14:10:11> <Info> <NT Performance Pack> <qawebmethods>
<myserver> <ExecuteThread: '14' for queue: 'default'> <> <> <000000>
<Allocating: '2' NT reader threads>
####<15/08/2002 14:10:13> <Info> <HTTP> <qawebmethods> <myserver>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(5367844,console,/console)] actions:
init>
####<15/08/2002 14:10:18> <Info> <HTTP> <qawebmethods> <myserver>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(5367844,console,/console)]
FileServlet: init>
####<15/08/2002 14:10:18> <Info> <HTTP> <qawebmethods> <myserver>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(5367844,console,/console)]
FileServlet: Using standard I/O>

"thorick" <[email protected]> wrote in message news:<[email protected]>...
Most likely, the OCI libraries could not be loaded.
Before continuing down this path, is there any reason
why you want to use an OCI based Driver as opposed to the
all Java Oracle thin driver ?There is indeed a valid reason for my choice.
I am currently connecting to the Oracle "Rdb" 7.0 database (located on
VMS) - not Oracle Oracle.
The SQL Service software we're currently using is version 7.1. This
version works well with the OCI8 driver (when connecting to the
database from Windows NT). This version of SQL Service however does
NOT work for the THIN driver (unless we upgrade the SQL Service to
version 7.1.5.5 - which we're not prepared to do so because it is not
stable enough from our previous test/trials). SQLSRV Version 7.1.5.5
works for THIN driver but it will result in uncommitted
transactions/unresolved connection/stopping of listener issues and
there is a need to restart the service from time to time. Oracle has
since confirmed that this is a bug that they have yet to resolve...
So we have to stick to OCI8 (THICK) for the time being. I would really
appreciate it very much if you can tell me the various OCI libraries
that I need to load (in terms of WebLogic Server config file settings
etc..).
By the way I have already installed the Oracle 8 client software on
the NT server (where WebLogic Server is) and I have also set up the
relevant SID (using the Net8 Assistant) that points to the Oracle Rdb
database on the VMS. I have also tried using SQL*Plus to connect to
the database and I can connect properly to the database. But WebLogic
simply doesn't seem to load the software.
Help...
Regards,
Bobby Brown, writing from Australia.

"Error loading native JDBC driver library" received when connecting to a DB

I recently installed 10g client onto my PC. After installation I now recieve an "Error loading native JDBC driver library" error when attempting to connect to a database.
This is a dual core Dell loaded with XP sp 2. I am attempting to connect to a 10gR2 instance. I tried the solution mentioned in another post to no avail. I am using SQL Developer v 1.2.1 build main-32.13.

Hi,
I found this thread from googling and am having the same problem for four days now...
For those who can get SQL Developer to work, could you please detail what properties you have in your installation? Could you please describe what we are supposed to see in the SQL Developer Properties tab? I found this tab in Help>About>Properties but have no idea where SQL Developer picks up those attributes. And it does not seem we can change any of them within SQL Developer. How frustrating!
Even more frustrating is that I am able to access the database I want to connect to with SQL Plus (right click on the connect node in SQL Developer)...
Thanks,
Clueless

Win2000+weblogic510+oracle8i,Could not load 'oracle.jdbc.driver.OracleDriver'

星期四 三月 23 20:30:17 GMT+08:00 2000:<E> <JDBC Pool>
Failed to create connection pool "ejavaPool"
weblogic.common.ResourceException: Could not load 'oracle.jdbc.driver.OracleDriver'
because
System.loadLibrary threw java.lang.UnsatisfiedLinkError
with the message 'oracle.jdbc.driver.OracleDriver'.
This could occur if the JDBC driver is not in the weblogic.class.path.
If this is a type-2 JDBC driver, it may also indicate that
the Driver native layers(DBMS client lib or driver DLL)
have not been installed properly on your system or in your environment.
This is most likely caused by one of the following:
1. The native layer SO, SL, or DLL could not be found.
2. The file permissions on the native layer SO, SL, or DLL
have not been set properly.
3. The native layer SO, SL, or DLL exists, but is either
invalid or corrupted.
For more information, read the installation documentation
for your JDBC Driver, available from:
http://www.weblogic.com/docs/install/install_jdbc.html
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.loadDriver(ConnectionEnvFactory.java:82)
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.<init>(ConnectionEnvFactory.java:97)
     at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:328)
     at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java, Compiled Code)
     at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:220)
     at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
     at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java, Compiled Code)
     at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
any idea?

If you are trying to use the thin driver you need to make sure you have the
classes12.zip file in the weblogic server classpath. You can download this
driver from Oracle website.
hth
sree
"meijunyong" <[email protected]> wrote in message
news:[email protected]...
>
星期四 三月 23 20:30:17 GMT+08:00 2000:<E><JDBC Pool>
Failed to create connection pool "ejavaPool"
weblogic.common.ResourceException: Could not load'oracle.jdbc.driver.OracleDriver'
because
System.loadLibrary threw java.lang.UnsatisfiedLinkError
with the message 'oracle.jdbc.driver.OracleDriver'.
This could occur if the JDBC driver is not in the weblogic.class.path.
If this is a type-2 JDBC driver, it may also indicate that
the Driver native layers(DBMS client lib or driver DLL)
have not been installed properly on your system or in your environment.
This is most likely caused by one of the following:
1. The native layer SO, SL, or DLL could not be found.
2. The file permissions on the native layer SO, SL, or DLL
have not been set properly.
3. The native layer SO, SL, or DLL exists, but is either
invalid or corrupted.
For more information, read the installation documentation
for your JDBC Driver, available from:
http://www.weblogic.com/docs/install/install_jdbc.html
atweblogic.jdbc.common.internal.ConnectionEnvFactory.loadDriver(ConnectionEnvF
actory.java:82)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.<init>(ConnectionEnvFacto
ry.java:97)
atweblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:328
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java,Compiled Code)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:220)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java, CompiledCode)
atweblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
any idea?

8.1 will not load the dvd driver error 39

The dvd played with no problem in 8, worked fine. I loaded 8.1 now it will not load the driver, says error 39. I uninstalled and reinstalled still the same. I got a external working DVD, plugged it in and the same code, same problem. windows
8.1 does not load the DVD driver.
what is the fix I understand it 8 does not play dvd movies, video this does not even recognize the player for music CD
jack walsh

Please repost your inquiry in the
Windows 8.1 Community Forum. Thank you!
Carey Frisch

JDBC adapter can't find the jdbc driver class

Hello, my jdbc driver give an very strange error
11:46:13 (4207): JDBC adapter terminated
Mon Aug 02 11:46:13 CEST 2004 *****
11:46:13 (4210): ERROR: Attempt to load JDBC driver failed ("java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver")
Attempt to intialize JDBC adapter failed
11:46:13 (4203): Unable to start JDBC adapter (not initialized)
I know that the jdbc driver is in the classpath, and to confirm that I have created a java program in the IB (repository) which import the class oracle.jdbc.driver.OracleDriver. I can compile and run that program without problems.
Here you can see my jdbc adapter configuration file:
jdbc adapter java class
classname=com.sap.aii.messaging.adapter.ModuleDB2XMB
mode=DB2XMB
Integration Engine address and document settings (example, see docu)
XMB.TargetURL=http://<host>:<port>/sap/xi/engine?type=entry
XMB.SenderBusinessSystem=ExtAdapterSender
XMB.SenderInterfaceNamespace=http://sap.com/xi/xidemo
XMB.SenderInterfaceName=ExtAdapterSenderIF
XMB.QualityOfService=EO
##DB Adapter specific parameters (example for SQL-Server, see docu)
db.jdbcDriver=oracle.jdbc.driver.OracleDriver
db.connectionURL=jdbc:oracle:<user>:<password>/hello@<url>:<port>:<instance>
db.processDBSQLStatement=Select * emp
db.pollInterval=600
xml.recordsetsPerMessage=1

Hi Ernesto,
Can you try to the following:
1. Remove your JDBC driver entries from the CLASSPATH.
2. Put those jars into your jre/lib/ext directory.
3. Restart the whole adapter engine, and
4. Config the driver java class for the adapter. the class name to be used can be found in your JDBC driver document.
Let me know whether it works.
Hart

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

Question about load Microsoft JDBC driver for Sql server 2000

Hello,
I have some problem while trying load the sqlserver2000 jdbc driver
My program is a third party application and it works with the other type 4 JDBC driver well. So I tried to use Microsoft SQL server 2000 JDBC driver instead.
I installed JDBC driver and set up the classpath.
My error message is:
"Driver class 'com.microsoft.jdbc.sqlserver.SQLServerDriver' could not be loaded"
Is above message means that my classpath setup correctly but the application could not load the class or the application could not find the jar file which containes the driver class?
By the way, the third party application I was using to load this JDBC driver does not certified to use microsoft JDBC driver. But I don't think it matter?
Thanks for your help
Hui Lu

Hello,
I have some problem while trying load the
sqlserver2000 jdbc driver
My program is a third party application and it works
with the other type 4 JDBC driver well. So I tried to
use Microsoft SQL server 2000 JDBC driver instead.
I installed JDBC driver and set up the classpath.
My error message is:
"Driver class
'com.microsoft.jdbc.sqlserver.SQLServerDriver' could
not be loaded"
That is an unusual message. Presumably you did not see "NoClassDefFoundError". If you see that it means the class could not be found.
Is above message means that my classpath setup
correctly but the application could not load the class
or the application could not find the jar file which
containes the driver class?
By the way, the third party application I was using to
load this JDBC driver does not certified to use
microsoft JDBC driver. But I don't think it matter?
It could. Perhaps the app expects a certain functional level and the driver doesn't support that. And so it bails with the message that you see.
Or it could mean that you have do something special because it has its own class path, and the driver is not in that.

Where is the jdbc driver to change it in IAS folders

Hello ...
we are developing an application in Jdevelper 10.1.2. When we test the application in the jdeveloper embedded container, a specific query is not returning the correct information from the database. However, if we deploy the application in an IAS 10g instance in the A server, the specific query in the application works correctly. We deploy the same application in another server and the specific query doesn't work correctly... we belive that the reason of this error is the jdbc driver
The question is: Where is located the oracle jdbc driver in the IAS 10g folders to change the driver.... i try in the jdbc folder from the Home folder but the folders in both servers are equals the applib folder in the instance path are diferent in some jar files but no one of this files are related with jdbc driver

Hi,
I don't want to use JDeveloper.
I want to write a Java program that connects to the database using Jdbc.
The PATH and CLASSPATH are defined for Java 1.4.
Here is the current CLASSPATH:
L:\oracle\product\10.2.0\db_1\jdbc\lib\ojdbc14.jar;
L:\oracle\product\10.2.0\db_1\jlib\orai18n.jar;.
What "import java......." should I code?
Many thanks.

How to resolve "Failed to load TTSQLDB JDBC driver" problem

Hi,
I installed timesten112140.sparc64.tar on solaris m/c.
Details of solaris m/c are
SunOS pun-ldom-rds70 5.10 Generic_139555-08 sun4v sparc SUNW,T5240
I am getting below mentioned error when trying connecting to the database through java process.
ERROR: failed to load TTSQLDB JDBC driver.
java.sql.SQLException: Problems with loading native library/missing methods: /op
t/TimesTen/ttsolaris21/lib/libttJdbc.so: ld.so.1: java: fatal: /opt/TimesTen/tts
olaris21/lib/libttJdbc.so: wrong ELF class: ELFCLASS64 (Possible cause: architec
ture word width mismatch)
at com.timesten.jdbc.JdbcOdbcConnection.connect(JdbcOdbcConnection.java:
1753)
at com.timesten.jdbc.TimesTenDriver.connect(TimesTenDriver.java:349)
at com.timesten.jdbc.TimesTenDriver.connect(TimesTenDriver.java:205)
at java.sql.DriverManager.getConnection(DriverManager.java:582)
at java.sql.DriverManager.getConnection(DriverManager.java:207)
at CreateConnectionDemo.createConnection(CreateConnectionDemo.java:43)
at CreateConnectionDemo.<clinit>(CreateConnectionDemo.java:26)
Exception in thread "main" java.lang.NullPointerException
at CreateConnectionDemo.closeConnection(CreateConnectionDemo.java:69)
at CreateConnectionDemo.main(CreateConnectionDemo.java:62)

You are trying to open a direct mode connection to 64-bit TimesTen from a JVM running in 32-bit mode. This is not possible. Run the JVM in 64-bit mode instead and thsi issue will be resolved.
Chris

Failure loading native JDBC driver

When i go into sql developer and try to create a connection for oracle using TNS connection identifier i get a failure loading native JDBC driver. any ideas?
thanks
m

Can you create a basic connection? Which platform are you on? What version of sqldev are you running? What version of JDK do you have?
K.

Equium - Windows can't load the device driver for USB dongle

I have been using a dongle without problems for about a month, however now it is saying (in device manager ) "Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)"
what does this mean and how can i fix it?

hi it's a vodafone 3gb cheap as chips dongle
it's an equium a200 i think
everything cam as one on the dongle, it uninstalled ok after initial problem, but now won't acknowledge it is in fact a dongle, just a 'usb mass filter' something or other?
i know i sound completely stupid, but when it comes to technology i am!

About the JDBC driver for Oracle805

Hello everyone,
I'm using the thin driver to config the JDBC Connection Pool in Weblogic 7.0,
and the
Oracle is 8.0.4. I can config it but it worked well just at the first time. I
get the
Connection from the WLS connection pool as the EJB does. Now both my JDBC code
and the EJB
can not access the database. I doubt if the JDBC driver is the correct version.
regards

For the record, Oracle 8.0.4 is no longer supported. The earliest version supported is now 8.1.7.
Not that this is the problem that you are seeing.
Can you use dbping to test if you can connect to the database?
"Jason Feng" <[email protected]> wrote in message news:3ebf8f2c$[email protected]..
>
Hello everyone,
I'm using the thin driver to config the JDBC Connection Pool in Weblogic 7.0,
and the
Oracle is 8.0.4. I can config it but it worked well just at the first time. I
get the
Connection from the WLS connection pool as the EJB does. Now both my JDBC code
and the EJB
can not access the database. I doubt if the JDBC driver is the correct version.
regards

What sequence weblogic load the jdbc driver

Similar Messages

Maybe you are looking for