Oracle JDBC 2.0 Connector configuration

I'm trying to configure a JDBC 2.0 connector (with XA support) through the Visual Administrator's JDBC Connector tab.
I've configured a driver called "ORACLE" which includes the classes12.zip file from Oracle.
I've configured a DataSource called ORACLEDS, using the ORACLE driver I've configured, and set the object factory to "oracle.jdbc.pool.OracleDataSourceFactory" and the XADS Classname to "oracle.jdbc.xa.client.OracleXADataSource".
I've set additional properties of "ServerName", "User", "Password" and "PortNumber" to their right values.
I've also changed the SQL Engine to "Vendor SQL".
Still, I cannot make this connection work. It says:
java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide execption: server ID 9244251:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot start DataSource "ORACLEDS".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1549)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1818)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:349)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:371)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:370)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.run(ParallelAdapter.java:79)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:134)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: java.sql.SQLException: Ungültiger Oracle-URL angegeben: OracleDataSource.makeURL
     at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.createManagedConnection(XAManagedConnectionFactoryImpl.java:193)
     at com.sap.engine.services.connector.jca.ConnectionHashSet.init(ConnectionHashSet.java:149)
     at com.sap.engine.services.connector.jca.ConnectionHashSet.(ConnectionHashSet.java:118)
     at com.sap.engine.services.connector.jca.AdapterCache.open(AdapterCache.java:192)
     at com.sap.engine.services.connector.ResourceObjectFactory.startConnectionFactory(ResourceObjectFactory.java:290)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1540)
     ... 9 more
Caused by: java.sql.SQLException: Ungültiger Oracle-URL angegeben: OracleDataSource.makeURL
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
     at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:1130)
     at oracle.jdbc.pool.OracleDataSource.makeURL(OracleDataSource.java:966)
     at oracle.jdbc.pool.OracleDataSource.getURL(OracleDataSource.java:575)
     at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:115)
     at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:86)
     at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.createManagedConnection(XAManagedConnectionFactoryImpl.java:153)
     ... 14 more
What am I doing wrong?

Hi.
We got it working now, so I'm going to describe the configuration we've made that made it run successfully:
1. Create a driver (I'll refer to it as "ORACLE"), and include the classes12.zip file in it.
2. Create a DataSource ("ORACLEDS") and configure it like this:
a. Add an alias ("ALIAS")
b. Driver Name = ORACLE
c. JDBC Version = 2.0 (with XA support)
d. Object Factory =
e. DataSource Type = XADataSource
f. XADS Classname = oracle.jdbc.xa.client.OracleXADataSource
g. In the additional properties pane, add 3 properties:
i. Password = ~PWD to your Oracle server~
ii. User = ~Username to your Oracle server~
iii. URL = jdbc:oracle:thin:@~IP:PORT:ALIAS~
(where IP means the IP to the oracle server, PORT means the port to the oracle server, and ALIAS means the alias you've defined in chapter 'a' in this mini-guide).
h. SQL Engine = Vendor SQL
Everything else is just default values.
I realy hope it'll work for you... as it works for us.
Regards,
Nir

Similar Messages

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).

COnfiguring oracle JDBC Driver with Web Sphere

I have oracle 7.3.4(on Solaris) and IBM Web Sphere standard
Edition 2.03 (on NT) I want connect to Oracle ina Servlet. Can
any one help in configuring Oracle JDBC driver in Web
Sphere?
Thanks very much
Tom
null

I have oracle 7.3.4(on Solaris) and IBM Web Sphere standard
Edition 2.03 (on NT) I want connect to Oracle ina Servlet. Can
any one help in configuring Oracle JDBC driver in Web
Sphere?
Thanks very much
Tom
null

Disable oracle connector configuration wizard.

I m using outlook connector 9.2 with MS outlook, and when i create ny profile from outlook client every thing is ok. but when i tested outlook connector 10.1.2 doesn't want to create profile from outlook client, i ask me to use the oracle connector configuration wizard.
There any way to disable the oracle connector configuration wizard ?
thanks

Hi,
Firstly, please check whether you PC meets the client requirements:
Get Connected in Windows Server Essentials
Did you mean that after you typed “http://<ServerName>/connect”, and dowload the software, then there was no User Account Control message appears,right? Did you click Run in the file download security warning message?
Best regards,
Susie
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

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.

Oracle JDBC driver 10.1.0.2.0

Hi All,
I have installed Oracle 9iR2 on Windows 2000 Advance server, and i am looking for Oracle JDBC driver 10.1.0.2.0 to be installed and configured, it would be real help if some one could send me the download path and how to continue further with installing the JDBC driver
Thanks,
Kumar

You can download the latest JDBC drivers from http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
You just need to place the jar somewhere and add the location to your classpath.
Kuassi

Differences between Oracle JDBC Thin and Thick Drivers

If any body is looking for this information...
============================================================
I have a question concerning the Oracle JDBC thin vs. thick drivers
and how they might affect operations from an application perspective.
We're in a Solais 8/Oracle 8.1.7.2 environment. We have several
applications on several servers connecting to the Oracle database.
For redundancy, we're looking into setting up TAF (transparent
application failover). Currently, some of our apps use the Oracle
<B>JDBC thin</B> drivers to talk to the database, with a connection
string that like this:
<B> jdbc:oracle:thin:@host:port:ORACLE_SID </B>
In a disaster recovery mode, where we would switch the database
from one server to another, the host name in the above string
would become invalid. That means we have to shut down our application
servers and restart them with an updated string.
Using the Oracle <B>OCI (thick)</B> driver though, allows us to connect
to a Net8 service instead of a specific server:
<B> jdbc:oracle:oci8:@NET8_SERVICE_NAME </B>
Coupled with the FAILOVER=ON option configured in Net8, it is
then possible to direct a connection from the first server to
the failover database on another server. This is exactly what
we would like to do.
My question is, from an application perspective, how is the Oracle
thick driver different from the thin driver? If everything
else is "equal" (i.e. the thick driver is compatible with the
app servers) would there be something within the the thick/OCI
driver that could limit functionality vs. the thin driver?
My understand, which obviously is sketchy, is that the thick
driver is a superset of the thin driver. If this is the case,
and for example if all database connections were handled through
a configuration file with the above OCI connection string, then
theoretically the thick driver should work.
============================================================
<B>
In the case with the Oracle, they provide a thin driver that is a 100% Java driver for client-side use without the need of an Oracle installation (maybe that's why we need to input server name and port number of the database server). This is platform indipendent, and has good performance and some features.
The OCI driver on the other hand is not java, require Oracle installation, platform dependent, performance is faster, and has a complete list of all the features.
</B>
========================================================
I hope this is what you expect.
JDBC OCI client-side driver: This is a JDBC Type 2 driver that uses Java native methods to call entrypoints in an underlying C library. That C library, called OCI (Oracle Call Interface), interacts with an Oracle database. <B>The JDBC OCI driver requires an Oracle (7.3.4 or above) client installation (including SQL*Net v2.3 or above) and all other dependent files.</B> The use of native methods makes the JDBC OCI driver platform specific. Oracle supports Solaris, Windows, and many other platforms. This means that the Oracle JDBC OCI driver is not appropriate for Java applets, because it depends on a C library to be preinstalled.
JDBC Thin client-side driver: This is a JDBC Type 4 driver that uses Java to connect directly to Oracle. It emulates Oracle's SQL*Net Net8 and TTC adapters using its own TCP/IP based Java socket implementation. <B>The JDBC Thin driver does not require Oracle client software to be installed, but does require the server to be configured with a TCP/IP listener. Because it is written entirely in Java, this driver is platform-independent.</B> The JDBC Thin driver can be downloaded into any browser as part of a Java application. (Note that if running in a client browser, that browser must allow the applet to open a Java socket connection back to the server.
JDBC Thin server-side driver: This is another JDBC Type 4 driver that uses Java to connect directly to Oracle. This driver is used internally by the JServer within the Oracle server. This driver offers the same functionality as the client-side JDBC Thin driver (above), but runs inside an Oracle database and is used to access remote databases. Because it is written entirely in Java, this driver is platform-independent. There is no difference in your code between using the Thin driver from a client application or from inside a server.
======================================================
How does one connect with the JDBC Thin Driver?
The the JDBC thin driver provides the only way to access Oracle from the Web (applets). It is smaller and faster than the OCI drivers, and doesn't require a pre-installed version of the JDBC drivers.
import java.sql.*;
class dbAccess {
public static void main (String args []) throws SQLException
DriverManager.registerDriver (new oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection
("jdbc:oracle:thin:@qit-uq-cbiw:1526:orcl", "scott", "tiger");
// @machineName:port:SID, userid, password
Statement stmt = conn.createStatement();
ResultSet rset = stmt.executeQuery("select BANNER from SYS.V_$VERSION");
while (rset.next())
System.out.println (rset.getString(1)); // Print col 1
stmt.close();
How does one connect with the JDBC OCI Driver?
One must have Net8 (SQL*Net) installed and working before attempting to use one of the OCI drivers.
import java.sql.*;
class dbAccess {
public static void main (String args []) throws SQLException
try {
Class.forName ("oracle.jdbc.driver.OracleDriver");
} catch (ClassNotFoundException e) {
e.printStackTrace();
Connection conn = DriverManager.getConnection
("jdbc:oracle:oci8:@qit-uq-cbiw_orcl", "scott", "tiger");
// or oci7 @TNSNames_Entry, userid, password
Statement stmt = conn.createStatement();
ResultSet rset = stmt.executeQuery("select BANNER from SYS.V_$VERSION");
while (rset.next())
System.out.println (rset.getString(1)); // Print col 1
stmt.close();
=================================================================

Wow, not sure what your question was, but there sure was a lot of information there...
There really is only one case where failover occurs, and it would not normally be in a disaster recovery situation, where you define disaster recovery as the obliteration of your current server farm, network and concievably the operational support staff. This would require a rebuild of your server, network etc and isn't something done with software.
Fail over is normally used for high availablity that would take over in case of hardware server failure, or when your support staff wants to do maintenance on the primary server.
Using the thin and thick driver should have ZERO affect on a failover. Transparent failover will make the secondary server the same IP as the primary, therefore the hostname will still point to the appropriate server. If you are doing this wrong, then you will have to point all your applications to a new IP address. This should be something that you tell your management is UNACCEPTABLE in a fail-over situation, since it is almost sure to fail to fail-over.
You point out that you are providing the TNSNAME, rather than the HOSTNAME when using the thick driver. That's true within your application, but that name is resolved to either a HOSTNAME, or IP ADDRESS before it is sent to the appropriate Oracle server/instance. It is resolved using either a NAME server (same as DNS server but for Oracle), or by looking at a TNSNAMES file. Since the TNSNAMES files profilerate like rabbits within an organization you don't want a fail over that will make you find and switch all the entries, so you must come up with a fail over that does not require it.
So, the application should not be concerned with either the hostname, or the IP address changing during fail over. That makes use of the thin or thick client acceptable for fail over.
Don't know if this will help, but this shows the communication points.
THIN DRIVER
client --> dns --> server/port --> SID
THICK DRIVER
client --> names server --> dns --> server/port --> SID
client --> tnsnames --> dns --> server/port --> SID

Oracle JDBC receiver error

Hi,
I am trying to setup a file to Oracle JDBC receiver scenario. In this case I am trying to just insert a single line to Oracle. I get no error in SXMB_MONI, no error in the message mapping test, and no error in the Test configuration in the ID.
Here is the error I get in the RWB comm channel monitoring for my adapter:
<i>No "action" attribute found in XML document ("action" attribute missing or wrong XML structure)
MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
Exception caught by adapter framework: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure).</i>
Here is my structure for the oracle receiver:
DTOracleReceiver_INSERT
    TEMP_DATA_XI                                             1
         action   (attribute)          xsd:string
         access
               NCODE                  xsd:string              1
               VNAME                  xsd:integer            1
               DDATE                   xsd:date                1
               NPRICE                  xsd:decimal           1
               LSTATES               xsd:string               1
TEMP_DATA_XI is my table name in Oracle
action is set to constant "INSERT" in the message mapping.
When I look at the payload in the OracleReceiver adapter, this is what shows up:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MTOracleReceiver_INSERT xmlns:ns0="http://test.com/jdbc">
- <TEMP_DATA_XI action="INSERT">
    - <access>
        <NCODE>200</NCODE>
        <VNAME>Inserttest</VNAME>
        <DDATE>2007-06-15 09:25:43.0</DDATE>
        <NPRICE>20.00</NPRICE>
        <LSTATES>test of JDBC receiver</LSTATES>
     </access>
</TEMP_DATA_XI>
</ns0:MTOracleReceiver_INSERT>
Any thoughts or ideas on how to fix this error?   Any help would be greatly appreciated.
Thanks,
Jake

I now get a different error:
Unable to execute statement for table or stored procedure. 'TEMP_DATA_XI' (Structure 'STATEMENTNAME') due to java.sql.SQLException: ORA-00928: missing SELECT keyword
2007-06-19 10:03:54 Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'TEMP_DATA_XI' (structure 'STATEMENTNAME'): java.sql.SQLException: ORA-00928: missing SELECT keyword
2007-06-19 10:03:54 Error Exception caught by adapter framework: Error processing request in sax parser: Error when executing statement for table/stored proc. 'TEMP_DATA_XI' (structure 'STATEMENTNAME'): java.sql.SQLException: ORA-00928: missing SELECT keyword
2007-06-19 10:03:54 Error Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'TEMP_DATA_XI' (structure 'STATEMENTNAME'): java.sql.SQLException: ORA-00928: missing SELECT keyword.
My current datatype for the receiver is:
DTOracleReceiver_INSERT                                                    1
     STATEMENTNAME                                                          1
             TEMP_DATA_XI                                                       1
                        action   (attribute)          xsd:string                  required
                        Table                            xsd:string                  1
                        access                                                         0:unbounded
                               NCODE                  xsd:string              1
                               VNAME                  xsd:integer            1
                               DDATE                   xsd:date                1
                               NPRICE                  xsd:decimal           1
                               LSTATES               xsd:string               1
action is mapped to "INSERT"
Table is mapped to "TEMP_DATA_XI"

Issue encountered when Login as sysdba role using Thin Oracle JDBC Driver

Hello all,
we are now considering to use Thin oracle JDBC driver to create database in our project, but we met one issue when we tried to connect to oracle as sysdba role using Thin driver, and it throws java.sql.SQLException: Io Exception: SO Exception was generated, I have found some tips on oracle jdbc website and it says :
How do I connect as SYSDBA or SYSOPER?
The only way to do this is to use the Properties object when connecting, rather than specifying the username and password as strings. Put the username into the "user" property, and the password into the "password" property. Then, put the mode into the "internal_logon" property. Something like the following:
Properties props = new Properties();
props.put("user", "scott");
props.put("password", "tiger");
props.put("internal_logon", "sysoper");
Connection conn = DriverManager.getConnection (url, props);
When connecting as SYSDBA or SYSOPER using the Thin driver, the RDBMS must be configured to use a password file. See "Creating and Maintaining a Password File" in the "Oracle Database Administrator's Guide".
So, i did execute orapwd command to create a password file and also set remote_login_passwordfile=execlusive in my initxxx.ora initial parameter file, however, when i tried to connect, it failed.
private static void createEmsdbDatabase(){
String url = "jdbc:oracle:thin:@localhost:1521:";
StringBuffer sqlStatement = new StringBuffer();
sqlStatement.append("create database xxx");
sqlStatement.append("maxdatafiles 254 ");
sqlStatement.append("maxinstances 8 ");
sqlStatement.append("maxlogfiles 32 ");
sqlStatement.append("character set UTF8 ");
sqlStatement.append("national character set UTF8 ");
sqlStatement.append("DATAFILE 'c:\\oracle\\xxx\\system01.dbf' SIZE 18M REUSE ");
sqlStatement.append("logfile 'c:\\oracle\\xxx\\redo01.log' SIZE 2M REUSE, ");
sqlStatement.append("'c:\\oracle\\xxx\\redo02.log' SIZE 2M REUSE, ");
sqlStatement.append("'c:\\oracle\\xxx\\redo03.log' SIZE 2M REUSE ");
try {
DriverManager.registerDriver(new OracleDriver());
Properties props = new Properties();
props.put("user", "sys");
props.put("password", "password");
props.put("database","xxx");
props.put("internal_logon", "sysdba");
Connection conn = DriverManager.getConnection(url, props);
Statement statement = conn.createStatement();
statement.executeUpdate(sqlStatement.toString());
statement.close();
conn.close();
} catch (SQLException e) {
e.printStackTrace();
But what made me puzzled a lot is if i use OCI driver, it did work great, why??? guys, anybody knows, please give me some tips, thanks in advance.
regards,
Kaixuan @ Shanghai

clarify my question in detail:
Step 1 : create password file using orapwd command
Step 2 : create database instance using oradim command
Step 3 : login using sys as sysdba to startup database, e.g startup nomount pfile='...\initxxx.ora'
Step 4 : create database.
java code showing below:
private static void createEmsdbDatabase(){
String url = "jdbc:oracle:thin:@localhost:1521:";
StringBuffer sqlStatement = new StringBuffer();
sqlStatement.append("create database xxx ");
sqlStatement.append("maxdatafiles 254 ");
sqlStatement.append("maxinstances 8 ");
sqlStatement.append("maxlogfiles 32 ");
sqlStatement.append("character set UTF8 ");
sqlStatement.append("national character set UTF8 ");
sqlStatement.append("DATAFILE 'c:\\oracle\\xxx\\system01.dbf' SIZE 18M REUSE ");
sqlStatement.append("logfile 'c:\\oracle\\xxx\\redo01.log' SIZE 2M REUSE, ");
sqlStatement.append("'c:\\oracle\\xxx\\redo02.log' SIZE 2M REUSE, ");
sqlStatement.append("'c:\\oracle\\xxx\\redo03.log' SIZE 2M REUSE ");
try {
DriverManager.registerDriver(new OracleDriver());
Properties props = new Properties();
props.put("user", "sys");
props.put("password", "password");
props.put("database","xxx");
props.put("internal_logon", "sysdba");
Connection conn = DriverManager.getConnection(url, props);
Statement statement = conn.createStatement();
statement.executeUpdate(sqlStatement.toString());
statement.close();
conn.close();
} catch (SQLException e) {
e.printStackTrace();
issue was met here, when i tried to login as sysdba using sys, and in my java code, i use Thin driver, it then thrus exception, but when OCI driver is used, it works great, i don't know why.
that is, when i use "jdbc:oracle:oci8:@" as database URL and then properties.put("database","xxx"), it works great. but, when i use "jdbc:oracle:thin:@localhost:1521:" as database URL and then properties.put("database","xxx"), it failed. hopefully, i have clarified my question clearly. thanks.

Java.lang.ClassNotFoundException: oracle.jdbc.OracleDriver

Hi everyone,
Can any one plz help me with this problem in connection with the database...im unable to connect from the servlet where my jdbc connectivity code is written when i compile it gives me this error:
Ljava.lang.String;@e53220java.lang.ClassNotFoundException: oracle.jdbc.OracleDriver
     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1352)
     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1198)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:164)
     at shoppingcart.shoppingcartservlet.doit(shoppingcartservlet.java:83)
     at shoppingcart.shoppingcartservlet.doPost(shoppingcartservlet.java:30)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
     at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Thread.java:595)

Hi
The server is not able to load the jdbc driver path. Place your driver in server classpath
Venkat

Exception:org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper cannot be cast to oracle.jdbc.OracleConnection

Hi All,
i am using jdev version 11.1.1.5.0
and deployed my Adf application on Apache Tomcat 6.0.
in my use case i have created simple adf application using adf business component. create a vo based on eo and drag-drop on jspx page.
i have created JNDI data source in Apache server using edit context.xml file and add following line-
<Resource name="jdbc/TestDB" auth="Container"
              type="javax.sql.DataSource" driverClassName="oracle.jdbc.OracleDriver"
              url="jdbc:oracle:thin:@localhost:1521:dst"
              username="jagrandb" password="jagrantest" maxActive="20" maxIdle="10"
              maxWait="-1" accessToUnderlyingConnectionAllowed="true" />
3.using same data source in my adf applicatioin as -
right click on AM --> Configuration-->edit-->select connection type jdbc datasource -->java:/comp/env/jdbc/TestDB
4. after that i have deployed my application on apace server but when i have running application i have got following error-
org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper cannot be cast to oracle.jdbc.OracleConnection
i have goggling and find following solution-
oracle.jdbc.driver.OracleConnection delConn = (oracle.jdbc.driver.OracleConnection) ((org.apache.tomcat.dbcp.dbcp.DelegatingConnection)c_stmt.getConnection()).getDelegate();
but my problem is that i'm using Adf Business Component so where i set following type casting.
Is there any method on ADF BC which handle JNDI Data source setting or any other way to do this.
thanks in Advance
Manish

Hi dvohra21,
thanks for reply.
i don't understand where i go to set accessToUnderlyingConnectionAllowed =true
i have already set this property on context.xml file
<Resource name="jdbc/TestDB" auth="Container"
              type="javax.sql.DataSource" driverClassName="oracle.jdbc.OracleDriver"
              url="jdbc:oracle:thin:@localhost:1521:dst"
              username="jagrandb" password="jagrantest" maxActive="20" maxIdle="10"
              maxWait="-1" accessToUnderlyingConnectionAllowed="true" />
any other place where i set this propery
please elaborate this steps how to Configuree DBCP

Oracle.jdbc.driver error using jdk1.2.2 on Win 2k

Im trying to run a jsp page that is dependent on an oricle database. However whenever I try to connect to the database over a thin line client I always get a java.lang.ClassNotFoundException error. I've gone over the path and classpath serveral time, and can't get it to work.
classpath =
C:\jdk1.2.2\lib\tools.jar;C:\Program Files\Tomcat4.0\common\lib\servlet.jar;C:\ORANT\jdbc\lib\classes102.zip;
C:\ORANT\jdbc\lib\classes111.zip;C:\jdk1.2.2\bin\java.exe;
C:\jdk1.2.2\lib\tools.jar;C:\jdk1.2.2\lib\dt.jar;
path =
C:\WINNT\system32;C:\WINNT\system32;C:\jdk1.2.2\bin\java.exe;C:\ORANT\jdbc\lib;
If anyone knows how to fix this problem Id appreciate it.

it doesn't say, it just gives me this error message.
javax.servlet.ServletException: oracle.jdbc.driver.OracleDriver
     at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:463)
     at org.apache.jsp.index$jsp._jspService(index$jsp.java:105)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java, Compiled Code)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java, Compiled Code)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:475)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java, Compiled Code)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java, Compiled Code)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java, Compiled Code)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java, Compiled Code)
     at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java, Compiled Code)
     at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java, Compiled Code)
     at java.lang.Thread.run(Thread.java:472)
root cause
java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver
     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java, Compiled Code)
     at java.lang.Exception.(Exception.java, Compiled Code)
     at java.lang.ClassNotFoundException.(ClassNotFoundException.java, Compiled Code)
     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java, Compiled Code)
     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java, Compiled Code)
     at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java, Compiled Code)
     at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java, Compiled Code)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java, Compiled Code)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java, Compiled Code)
     at org.apache.jsp.index$jsp._jspService(index$jsp.java:87)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java, Compiled Code)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java, Compiled Code)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:475)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java, Compiled Code)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java, Compiled Code)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java, Compiled Code)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java, Compiled Code)
     at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java, Compiled Code)
     at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java, Compiled Code)
     at java.lang.Thread.run(Thread.java:472)

Oracle JDBC driver initilalize an applet in the background

I am writing an APPLICATION that is connecting with database.
When I execute the code two dialog windows with title 'APPLET ALERT' appear and it ask for a permission:
-The applet is attempting to invoke the java/lang/System.getProperty() operation on user.name
-The applet is attempting to connect to [database name]
When I allow permissions then program continues ok, when i disallow then an exception is thrown: Exception in thread "main" com.trend.iwss.jscan.runtime.AppletTrapStopError: Applet disabled by IWSVA Javascan site policy.
Whether I allow or disallow following output is printed on the console:
Current policy properties:
mmc.sess_pe_act.block_unsigned: false
window.num_max: 5
jscan.sess_applet_act.sig_trusted: pass
file.destructive.state: disabled
jscan.sess_applet_act.block_all: false
window.num_limited: true
jscan.sess_applet_act.unsigned: instrument
mmc.sess_pe_act.action: validate
jscan.session.daemon_protocol: http
file.read.state: disabled
mmc.sess_pe_act.block_invalid: true
mmc.sess_pe_act.block_blacklisted: false
net.bind_enable: false
jscan.session.policyname: TU1DIERlZmF1bHQgUG9saWN5
mmc.sess_cab_act.block_unsigned: false
file.nondestructive.state: disabled
jscan.session.origin_uri: http://download.oracle.com/otn/utilities_drivers/jdbc/111070/ojdbc6.jar
mmc.sess_cab_act.action: validate
net.connect_other: false
jscan.session.user_ipaddr: 10.10.0.110
jscan.sess_applet_act.sig_invalid: block
mmc.sess_cab_act.block_invalid: true
thread.thread_num_max: 8
jscan.sess_applet_act.sig_blacklisted: block
net.connect_src: true
thread.thread_num_limited: true
jscan.sess_applet_act.stub_out_blocked_applet: true
mmc.sess_cab_act.block_blacklisted: true
jscan.session.user_name: 10.10.0.110
thread.threadgroup_create: false
file.write.state: disabled
-->> returning Frame NULL
BaseDialog: owner frame is a java.awt.Frame
Why is the driver initializing an applet? What should I change?
I am using JDK 1.6 and driver 11g Release 1 (11.1.0.7.0) - ojdbc6.jar, database is Oracle 9i (9.2.0.7.0).
Below is my code.
import java.sql.*;
public class Test {
public static void main(String args[]) {
try{
Class.forName("oracle.jdbc.driver.OracleDriver");
Connection conn = DriverManager.getConnection(
"jdbc:oracle:thin:@DBNAME:1521:DBNAME", "user", "password");
Statement stmt = conn.createStatement();
ResultSet rset = stmt
.executeQuery("select 'Hello '||USER||'.' from dual");
while (rset.next())
System.out.println(rset.getString(1));
rset.close();
stmt.close();
conn.close();
} catch (Exception e) {
System.out.println(e.getMessage());
}

This is a console software. The code above is only an example but it causes the same effect.
The program behavior is the same whether I start it from Eclipse (normal or debug) or from command line.
I think the case is our company IWSVA internet scanner, a kind of firewall.
I found on google few similar problems with IWSVA or IWSS but with no solution.
Already our administrators are checking the configuration.
+When I allow permissions then program continues ok, when i disallow then an exception is thrown: Exception in thread "main" com.trend.iwss.jscan.runtime.AppletTrapStopError: Applet disabled by IWSVA Javascan site policy+

NullPointerException at oracle.jdbc.driver.OracleDriver.connect()

I have written a java stored procedure. The method can be executed properly in local PC environment.
but when the java program is load into Oracle DB JVM by loadjava command. such method is called in SQL> prompt as a java stored procedure. I got
java.lang.NullPointerException
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:379)
at java.sql.DriverManager.getConnection(DriverManager.java:573)
at java.sql.DriverManager.getConnection(DriverManager.java:187)
at WCZSynchronizer.testLocalConn(WCZSynchronizer:901)
as shown in the trace file.
The line in my own java program WCZSynchronizer is simply
Connection conn = java.sql.DriverManager.getConnection(db_connection_string,username,password);
I am sure that the db_connection_string, username and password are correct as it works in my local PC.
I even try to get default connection by
Connection conn = java.sql.DriverManager.getConnection("jdbc:default:connection:");
and
Connection conn = new oracle.jdbc.driver.OracleDriver().defaultConnection();
I got the same NullPointerException in both cases too.
In fact, the java stored procedure worked before. but suddenly it's failed! The Oracle DB server is under my control and I did not change any configuration nor setting on it.
I can't find similar case from this forum. Do any one know why?
thanks.

First try debugging the test case by making sure that none of the parameters passed to getConnection is null.
When you are sure that none of the parameters are null, if the issue still reproduces. Let us know
- The driver version
- The jar file you are using
cheers
Ashok

Oracle JDBC Drivers with Tomcat

I try to connect to Oracle DB with the JDBC Drivers throught Tomcat JNDI access.
I've tried with the oracle.jdbc.driver.OracleDriver and I have an UnsupportedOperationException when calling the getConnection() method on ma dataSource ref.
So I've tried with the oracle.jdbc.pool.OracleConnectionPoolDataSource and I have an java.sql.SQLException:
Cannot create JDBC driver of class
'oracle.jdbc.pool.OracleConnectionPoolDataSource' for connect URL
'jdbc:oracle:thin:@(description=(address=(host=meditws322)(protocol=tcp)(port=1521)
)(connect_data=(sid=HABILLE)))'
Please help I'm about to break down

Thanks for your reply. I use Oracle JDBC driver. The XSQLConfig.xml was changed to have the following setting:
<connection-manager>
<factory>oracle.xml.xsql.XSQLOracleDatasourceConnectionManager</factory>
</connection-manager>
I'm using Tomcat 4.1.x and Apache Commons DBCP Datasources with org.apache.commons.dbcp.BasicDataSourceFactory. The configuration file does set driverClassName to oracle.jdbc.driver.OracleDriver. All other queries embedded in .xsql files work great, I only have issues with queries containing CURSOR() statements. If I switch back to built-in database connectivity, by changing XSQLConfig.xml and connection parameters in .xsql files everything is working again. When I attempt to use DataSources, I get things like this "oracle.jdbc.driver.OracleResultSetImpl@15780d9" instead of nested XML. The non-nested portion of XML looks fine also, so it is retrieving the data from the database properly. Please let me know if I can provide any additional information that could help in resolving this. Thanks in advance!
-M-

Oracle JDBC 2.0 Connector configuration

Similar Messages

Maybe you are looking for