ORA01002 with Oracle thin driver - not with JDriver

Hi,
I use weblogic 5.1 SP10. I was using the weblogic JDriver to create a connection
pool for my entity beans with BMP. I switched from the weblogic Jdrivers to using
the Oracle thin driver (classes12.zip) for my connection pool. Now i get a ORA-01002
(fetch out of sequence) for my ORACLE 8.1.6 SELECT FOR UPDATEs. I can solve this
by - explicitly setting autocommit to false for the connection. This is within
in the EJB transaction.
Why I have to do this with the Oracle thin driver and not with the Weblogic JDriver
Any thoughts on this are appreciated !

From this I assume that you know what you are doing but I have to ask, are you
using the TxDataSource to obtain the connection in your BMP entity beans? If
so, I would talk to support...
Anand wrote:
Hi Robert,
I am using the TxDataSource in the workout.properties file.
eg:
weblogic.jdbc.TXDataSource.MyDBPool =MyDBPool
The connection pool is defined as below:
weblogic.jdbc.connectionPool.MyDBPool =\
driver=oracle.jdbc.driver.OracleDriver,\
url=jdbc:oracle:thin:@localhost:1521:MyDb,\
loginDelaySecs=1,\
initialCapacity=10,\
maxCapacity=20,\
capacityIncrement=2,\
allowShrinking=true,\
shrinkPeriodMins=15,\
refreshMinutes=10,testTable=dual,\
props=user=admin;password=password
Robert Patrick <[email protected]> wrote:
How are you obtaining the connection from the pool? Make sure you are
using a
TxDataSource...
Anand wrote:
Hi,
I use weblogic 5.1 SP10. I was using the weblogic JDriver to createa connection
pool for my entity beans with BMP. I switched from the weblogic Jdriversto using
the Oracle thin driver (classes12.zip) for my connection pool. Nowi get a ORA-01002
(fetch out of sequence) for my ORACLE 8.1.6 SELECT FOR UPDATEs. I cansolve this
by - explicitly setting autocommit to false for the connection. Thisis within
in the EJB transaction.
Why I have to do this with the Oracle thin driver and not with theWeblogic JDriver
Any thoughts on this are appreciated !

Similar Messages

Can't create connection pool using weblogic 6.1 with Oracle thin driver

Hi !
I have tried to create a connection pool from adminconsole. My CLASSPATH setting
is as follows :
F:\SOAP\soap-2_2\lib;F:\SOAP\soap-2_2;
D:\Oracle\Ora81\jdbc\lib\classes12.zip;
D:\Oracle\Ora81\jdbc\lib\nls_charset12.zip;
D:\Oracle\Ora81\jdbc\lib\classes111.zip;
F:\SOAP\soap-2_2\lib\jaf-1.0.1\activation.jar;
D:\Oracle\Ora8\Apache\Jsdk\src\javax\servlet\http;
D:\Oracle\Ora81\Apache\Jsdk\src\javax\servlet;
D:\Oracle\Ora81\lib;
F:\ant\jakarta-ant1.\bin;
E:\weblogic\oci\classes;
E:\weblogic\oci\classes\weblogic\xml\license;
E:\weblogic\oci\license;
E:\bea\wlserver6.1\lib;
E:\PetStoreHome\petstore1.3;
Following is the configuration.
#Oracle thin driver Method #2
weblogic.jdbc.connectionPool.thin=\
url=jdbc:oracle:thin:@test:1521:PROJECT,\
driver=oracle.jdbc.driver.OracleDriver,\
     initialCapacity=4,\
     maxCapacity=10,\
     capacityIncrement=1,\
     props=user=xxx;password=xxx;server=test
#Add a TXDataSource for the connection pool:
weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.thin=thin
# Add an ACL for the connection pool:
weblogic.allow.reserve.weblogic.jdbc.connectionPool.thin=everyone
I did append the file weblogic.properties with the above config. Now when I start
the Weblogic server I get the following error :
Starting WebLogic Server ....
<Nov 29, 2001 2:24:16 PM EST> <Notice> <Management> <Loading configuration file
.\config\petstore\config.xml ...>
<Nov 29, 2001 2:24:22 PM EST> <Notice> <WebLogicServer> <Starting WebLogic Admin
Server "petstoreServer" for domain "petstore">
<Nov 29, 2001 2:24:26 PM EST> <Notice> <Management> <Starting discovery of Manag
ed Server... This feature is on by default, you may turn this off by passing -Dw
eblogic.management.discover=false>
<Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data Source creation:
weblogic.common.ResourceException: DataSource(jdbcthin.SignOnDB) can't be creat
ed with non-existent Pool (connection or multi) (thin)>
<Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data Source creation:
weblogic.common.ResourceException: DataSource(jdbcthin.EstoreDB) can't be creat
ed with non-existent Pool (connection or multi) (thin)>
<Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data Source creation:
weblogic.common.ResourceException: DataSource(jdbcthin.InventoryDB) can't be
cr
eated with non-existent Pool (connection or multi) (thin)>
<Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data Source creation:
weblogic.common.ResourceException: DataSource(weblogic.jdbc.jts.thin) can't be
created with non-existent Pool (connection or multi) (thin)>
<Nov 29, 2001 2:24:41 PM EST> <Notice> <Management> <Application Poller not star
ted for production server.>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
After the server has booted, your browser should
automatically launch and point to the WebLogic Server
Tour running on this server. If your browser fails to
launch, point your browser to the URL
"http://burtsun:7001"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<Nov 29, 2001 2:24:41 PM EST> <Notice> <WebLogicServer> <ListenThread listening
on port 7001>
<Nov 29, 2001 2:24:41 PM EST> <Notice> <WebLogicServer> <SSLListenThread listeni
ng on port 7002>
<Nov 29, 2001 2:24:42 PM EST> <Notice> <WebLogicServer> <Started WebLogic Admin
Server "petstoreServer" for domain "petstore" running in Production Mode>
Could anyone please help me ?
Thanks
..Madhuri

Madhuri wrote:
>
Hi Joe !
I didn't get what you would like to point out. Actully, I am using same config.,
but not to disclose the info. I gave you @test and username/password xxx/xxx.Ok. Now, assuming your pool looks like what I showed, the issue is probably
that there are multiple Oracle driver zips around, and your standlaone program
is using a different, newer, better one than the server. Our weblogic jar files
include a classes12.zip Oracle thin driver, but there are multiple versions of
classes12.zip, and the latest from oracle is better than the one we sealed into
our packaging. Please use jave -verbose to identify exactly which Oracle sip file
you are using in the successful case, then make sure this zip file comes before
any weblogic stuff in your weblogic server's classpath, so we'll use the same
driver. This should work. Edit the script you sue to start weblogic to verify
the classpath does end up with the oracle driver ahead of all weblogic stuff.
Joe
>
Please let me know.
Thanks
.Madhuri
Joseph Weinstein <[email protected]> wrote:
Madhuri wrote:
Hi Joe !
Here is the sample java code. Please let me know how I can test thisin weblogic
6.1.
Thanks
.MadhuriWell fine! That was easy. Your pool definition didn't have the same URL
or
user or password as this code. Try this for your pool definition:
weblogic.jdbc.connectionPool.thin=\
url=jdbc:oracle:thin:@adl-gbsdevel:1521:PROJECT,\
driver=oracle.jdbc.driver.OracleDriver,\
initialCapacity=10,\
maxCapacity=10,\
capacityIncrement=1,\
testConnsOnReserve=true,\
testTable=dual,\
props=user=mkelkar;password=mkelkar
Let me know,,,
Joe
Joseph Weinstein <[email protected]> wrote:
The key is in the log:
Could not create pool connection.
The DBMS driver exception was:
java.sql.SQLException: invalid arguments in call
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
Now we need to simplify the problem. Please make a simple 15-line
standalone
Java program like you'd find with the Oracle driver's examples, with
no
weblogic code in the picture. Just make a JDBC connection using Oracle's
driver, and show me that code. Then I can translate that into a pool
definition.
Joe
Madhuri wrote:
Hi Joe !
Thanks for your prompt reply. I tried the way you suggested but
it
still it gives
me the same error. I am attching here the weblogic.log file.
Thanks again
..Madhuri
Joseph Weinstein <[email protected]> wrote:
We'd want to see the log during booting, where the pool
is being created to see why that failed. Try a pool
definition with no blank lines, no whitespace at the
end of lines, and no server property. The thin driver
doesn't like that:
weblogic.jdbc.connectionPool.thin=\
url=jdbc:oracle:thin:@test:1521:PROJECT,\
driver=oracle.jdbc.driver.OracleDriver,\
initialCapacity=4,\
maxCapacity=10,\
capacityIncrement=1,\
props=user=xxx;password=xxx
Joe
Madhuri wrote:
Hi !
I have tried to create a connection pool from adminconsole. My
CLASSPATH
setting
is as follows :
F:\SOAP\soap-2_2\lib;F:\SOAP\soap-2_2;
D:\Oracle\Ora81\jdbc\lib\classes12.zip;
D:\Oracle\Ora81\jdbc\lib\nls_charset12.zip;
D:\Oracle\Ora81\jdbc\lib\classes111.zip;
F:\SOAP\soap-2_2\lib\jaf-1.0.1\activation.jar;
D:\Oracle\Ora8\Apache\Jsdk\src\javax\servlet\http;
D:\Oracle\Ora81\Apache\Jsdk\src\javax\servlet;
D:\Oracle\Ora81\lib;
F:\ant\jakarta-ant1.\bin;
E:\weblogic\oci\classes;
E:\weblogic\oci\classes\weblogic\xml\license;
E:\weblogic\oci\license;
E:\bea\wlserver6.1\lib;
E:\PetStoreHome\petstore1.3;
Following is the configuration.
#Oracle thin driver Method #2
weblogic.jdbc.connectionPool.thin=\
url=jdbc:oracle:thin:@test:1521:PROJECT,\
driver=oracle.jdbc.driver.OracleDriver,\
initialCapacity=4,\
maxCapacity=10,\
capacityIncrement=1,\
props=user=xxx;password=xxx;server=test
#Add a TXDataSource for the connection pool:
weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.thin=thin
# Add an ACL for the connection pool:
weblogic.allow.reserve.weblogic.jdbc.connectionPool.thin=everyone
I did append the file weblogic.properties with the above config.
Now
when I start
the Weblogic server I get the following error :
Starting WebLogic Server ....
<Nov 29, 2001 2:24:16 PM EST> <Notice> <Management> <Loading
configuration
file
\config\petstore\config.xml ...>
<Nov 29, 2001 2:24:22 PM EST> <Notice> <WebLogicServer> <Starting
WebLogic
Admin
Server "petstoreServer" for domain "petstore">
<Nov 29, 2001 2:24:26 PM EST> <Notice> <Management> <Starting
discovery
of Manag
ed Server... This feature is on by default, you may turn this
off
by
passing -Dw
eblogic.management.discover=false>
<Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data
Source
creation:
weblogic.common.ResourceException: DataSource(jdbcthin.SignOnDB)
can't
be creat
ed with non-existent Pool (connection or multi) (thin)>
<Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data
Source
creation:
weblogic.common.ResourceException: DataSource(jdbcthin.EstoreDB)
can't
be creat
ed with non-existent Pool (connection or multi) (thin)>
<Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data
Source
creation:
weblogic.common.ResourceException: DataSource(jdbcthin.InventoryDB)can't be
cr
eated with non-existent Pool (connection or multi) (thin)>
<Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data
Source
creation:
weblogic.common.ResourceException: DataSource(weblogic.jdbc.jts.thin)can't be
created with non-existent Pool (connection or multi) (thin)>
<Nov 29, 2001 2:24:41 PM EST> <Notice> <Management> <Application
Poller
not star
ted for production server.>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
After the server has booted, your browser should
automatically launch and point to the WebLogic Server
Tour running on this server. If your browser fails to
launch, point your browser to the URL
"http://burtsun:7001"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<Nov 29, 2001 2:24:41 PM EST> <Notice> <WebLogicServer> <ListenThreadlistening
on port 7001>
<Nov 29, 2001 2:24:41 PM EST> <Notice> <WebLogicServer> <SSLListenThreadlisteni
ng on port 7002>
<Nov 29, 2001 2:24:42 PM EST> <Notice> <WebLogicServer> <Started
WebLogic
Admin
Server "petstoreServer" for domain "petstore" running in ProductionMode>
Could anyone please help me ?
Thanks
..Madhuri
Name: weblogic.log
weblogic.log Type: Text Document (application/x-unknown-content-type-txtfile)
Encoding: base64
Name: PrintColumns.java
PrintColumns.java Type: Visual Cafe File (application/x-unknown-content-type-VisualCafeFile.Document)
Encoding: base64

JDBC logging disabled with Oracle thin driver

Hi,
I am trying to turn on JDBC logging through the weblogic console application (WL
6.1 with CMP). In the jdbc log file I do not see the SQL statments.
It looks like logging is somehow disabled (check one of the logs statements below)
by some means. Any ideas, I am making use of oracle thin driver.
Thanks
Mohit
Following log messages are generated!!!!!!
DriverManager.initialize: jdbc.drivers = null
JDBC DriverManager initialized
registerDriver: driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
DriverManager.getDriver("jdbc:oracle:thin:@(description=(address=(host=192.168.161.120)(protocol=tcp)(port=1521))(connect_data=(sid=DOPERS01)))")
trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
DRVR OPER Disabled logging
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
registerDriver: driver[className=weblogic.jdbc.jts.Driver,weblogic.jdbc.jts.Driver@13eb9c]
registerDriver: driver[className=weblogic.jdbc.pool.Driver,weblogic.jdbc.pool.Driver@4f83d1]
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing

Mohit,
Remove oracle/jdbc/driver/OracleLog from classes12.zip, and it should
work (it needs to pick up only this class from weblogic.jar).
Paul
Hi,
I am trying to turn on JDBC logging through the weblogic console application (WL
6.1 with CMP). In the jdbc log file I do not see the SQL statments.
It looks like logging is somehow disabled (check one of the logs statements below)
by some means. Any ideas, I am making use of oracle thin driver.
Thanks
Mohit
Following log messages are generated!!!!!!
DriverManager.initialize: jdbc.drivers = null
JDBC DriverManager initialized
registerDriver: driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
DriverManager.getDriver("jdbc:oracle:thin:@(description=(address=(host=192.168.161.120)(protocol=tcp)(port=1521))(connect_data=(sid=DOPERS01)))")
trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
DRVR OPER Disabled logging
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
registerDriver: driver[className=weblogic.jdbc.jts.Driver,weblogic.jdbc.jts.Driver@13eb9c]
registerDriver: driver[className=weblogic.jdbc.pool.Driver,weblogic.jdbc.pool.Driver@4f83d1]
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing

Using Oracle thin driver with Weblogic 6.1

hi all,
i am trying to create a ConnectionPool using WLS6.1 and Oracle 8.0.5.
Since i cannot use the weblogic driver (due to the old version of oracle that
i have)
i am trying to use instead the oracle thin driver.
i configured my pool as follows:
URL jdbc:oracle:[email protected]:1521:ORC1
Driver oracle.jdbc.Driver.OracleDriver
Propeties user=SCOTT
when i try to assing the created pool to a server (using the 'Target' link),
i always got this exception
weblogic.management.DeploymentException: Error creating connection pool - with
n
ested exception:
[weblogic.common.ResourceException: Cannot load driver class: oracle.jdbc.Driver
.OracleDriver]
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:110)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:608)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:592)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:352)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBean
s(ConfigurationMBeanImpl.java:484)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:354)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
at $Proxy7.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(Dynam
icMBeanImpl.java:1448)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
anImpl.java:858)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
anImpl.java:810)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Conf
igurationMBeanImpl.java:288)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
ava:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
ava:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:
303)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy75.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.FilteredMBeanAttribute.doSet(Filtere
dMBeanAttribute.java:89)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(D
oEditMBeanAction.java:116)
at weblogic.management.console.actions.internal.ActionServlet.doAction(A
ctionServlet.java:167)
at weblogic.management.console.actions.internal.ActionServlet.doPost(Act
ionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2456)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.management.DistributedOperationUpdateException: Error creating connecti
on pool - with nested exception:
[weblogic.management.DeploymentException: Error creating connection pool - with
nested exception:
[weblogic.common.ResourceException: Cannot load driver class: oracle.jdbc.Driver
.OracleDriver]]
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBean
s(ConfigurationMBeanImpl.java:494)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:354)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:44>
However, i set the CLASSPATH & PATH of my startWebLogic.cmd as follows:
set PATH=c:\orant\bin;d:\bea\wlserver6.1\bin\oci817_8;.\bin;%PATH%
set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;.\samples\eval\cloudscape\lib\cloudscape.jar;.\config\examples\serverclasses;c:\orant\jdbc\lib\classes111.zip
AND, i have written a small program that uses JDBC (without weblogic) to query
a table
on the Oracle (using the pool's URL in the properties for getting the Connection
conn = DriverManager.getConnection("jdbc:oracle:thin:@127.0.0.1:1521:ORC1", "scott",
"tiger");
and that program works fine.
Can anyone tell me what is wrong?? it seems that everything is in order (with
respect to CLASSPATH, PATH etc..)
hope someone can solve my problem
thanx and regards
marco

your url should be
jdbc:oracle:thin:@127.0.0.1:1521:ORC1
notice the ':' before the '@'.
sree
"Marco" <[email protected]> wrote in message
news:[email protected]...
Hi Sree,
You have to place the classes11.zip file in the beginning of the classpath.i did it. my CLASSPATH is now
CLASSPATH=c:\orant\jdbc\lib\classes111.zip;.;.\lib\weblogic_sp.jar;.\lib\web
logic.jar;.\samples\eval\cloudscape\lib\cloudscape.jar;.\config\examples\ser
verclasses
But now, when i assign the target, the exception is:
--------------- nested within: ------------------
weblogic.management.DistributedOperationUpdateException: Error creating
connecti
on pool - with nested exception:
[weblogic.management.DeploymentException: Error creating connection pool -
with
nested exception:
[weblogic.common.ResourceException: weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: Sub Protocol must be specified in connection URL
        at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:352)
        at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:102)
        at
weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:192)
        at
weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:134)
        at
weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
cator.java:698)
        at
weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
ava:282)
        at
weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
ava:629)
        at
weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
        at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:329)
        at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:144)
        at java.lang.reflect.Method.invoke(Native Method)
        at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:608)
        at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
java:592)
        at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:352)
        at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
        at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
        at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBean
s(ConfigurationMBeanImpl.java:484)
        at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:354)
        at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
        at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
        at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
        at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
        at $Proxy8.addDeployment(Unknown Source)
        at weblogic.management.internal.DynamicMB>
what is SubProtocol???
my ConnectionPool is configured as follows:
Name:     MyJDBC Connection Pool
URL :     jdbc:oracle:[email protected]:1521:ORC1
Driver:   oracle.jdbc.driver.OracleDriver
Properties: user=SCOTT
Password : tiger
can u help me???
thanx in advance and regards
   marco
>
>
at
weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:110)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:608)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
java:592)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:352)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBean
s(ConfigurationMBeanImpl.java:484)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:354)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
at $Proxy7.addDeployment(Unknown Source)
at
weblogic.management.internal.DynamicMBeanImpl.updateDeployments(Dynam
icMBeanImpl.java:1448)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
anImpl.java:858)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
anImpl.java:810)
at
weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Conf
igurationMBeanImpl.java:288)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
ava:1356)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
ava:1331)
at
weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:
303)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy75.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.console.info.FilteredMBeanAttribute.doSet(Filtere
dMBeanAttribute.java:89)
at
weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(D
oEditMBeanAction.java:116)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(A
ctionServlet.java:167)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(Act
ionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2456)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.management.DistributedOperationUpdateException: Error creating
connecti
on pool - with nested exception:
[weblogic.management.DeploymentException: Error creating connection pool
with
nested exception:
[weblogic.common.ResourceException: Cannot load driver class:
oracle.jdbc.Driver
OracleDriver]]
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBean
s(ConfigurationMBeanImpl.java:494)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:354)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:44>
However, i set the CLASSPATH & PATH of my startWebLogic.cmd as follows:
set PATH=c:\orant\bin;d:\bea\wlserver6.1\bin\oci817_8;.\bin;%PATH%
set
CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;.\samples\eval\cloudsc
a
pe\lib\cloudscape.jar;.\config\examples\serverclasses;c:\orant\jdbc\lib\clas
ses111.zip
AND, i have written a small program that uses JDBC (without weblogic)
to
query
a table
on the Oracle (using the pool's URL in the properties for getting the
Connection
conn = DriverManager.getConnection("jdbc:oracle:thin:@127.0.0.1:1521:ORC1",
"scott",
"tiger");
and that program works fine.
Can anyone tell me what is wrong?? it seems that everything is in order
(with
respect to CLASSPATH, PATH etc..)
hope someone can solve my problem
thanx and regards
marco

Problem in getting Time info with webLogic using Oracle Thin Driver

We have a servlet to store/retrieve date/time data from an Oracle 9i db using use the Oracle thin driver. Everyting is ok when run on JSDK2.1 servlet container or Tomcat. But when run under WebLogic 8.1, we have problem with time portion info, it is lost. After debuging, we found under WebLogic, the returned object type is a java.sql.Date which by definition has no time info, while in other servlet containers, it is a java.sql.Timestamp. Storing date/time data in a Date column is ok under WebLogic because we see the time portion data in the db table. We did not set anything about database/jdbc in WebLogic.
It would be greatly appreciated if someone can explain what effect WebLogic has on a servlet that has its own jdbc connection or how WebLogic could change data type from a jdbc sql statement.

That's a function of the JDBC driver, not the J2EE app server.
Sounds like maybe you're using the WebLogic 8.1 driver when you deploy with WL instead of the Oracle driver. You certainly can deploy with the Oracle driver. Go into the WL config manager and set it up to use the ojdbc14.jar instead.
%

How to set SunOne IDE to work with Oracle thin driver

I am new to the SunOne IDE. I am trying to use the JDBC wizard to generate a form to work with an Oracle table. I want to use the ORacle thin driver but I am not sure how I can tell the IDE where its located. Can someone help? Thanks.

In the explorer window select "RUNTIME".(Bottom of window tabbed pane)
Expand "DATABASES"
Expand "DRIVERS"
Scrolldown and you'll see Oracle thin - click on that and set properties.
Then right click "Oracle thin" click "connect using..."
From here/there you should be able to view all tables you have access to view..etc.

Petstore throws populateServlet error with Oracle thin driver

When i point connection pool to Oracle database, i get the following error. The
data is populated in the database, looks like when petstore is enumerating db
tables and make sure all tables exist, this error is happening. Some how, database
metadata coming as NULL. Has anybody tried petstore with Oracle JDBC driver?
thanks,
PopulateServlet Error:
java.lang.NullPointerException java.lang.NullPointerException at com.sun.j2ee.blueprints.tools.populate.web.PopulateServlet.checkTables(PopulateServlet.java:276)
at com.sun.j2ee.blueprints.tools.populate.web.PopulateServlet.doGet(PopulateServlet.java:127)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

I believe that you do not have weblogicaux.jar in your classpath.
-Selvan
Laurie Cohen wrote:
Im using Solaris 2.7 with WLS 5.1.0 and Commerce Server 2.0.1 with
current service packs on both. JDK 1.2.1_04 and the Oracle thin driver
(classes111.zip which I am told is the only one supported in this
configuration). Has anyone seen this problem? Is it that the driver is
using 1.1 and I only have 1.2 installed?
devapp01% java -classpath
/usr/local/weblogic/classes:/usr/local/weblogic/license utils.t3dbping
t3://localhost:7601 username password "" oracle.jdbc.driver.OracleDriver
jdbc:oracle:thin:@10.200.201.110:1521:q01c
Connecting to WebLogic with the WebLogic JDBC Driver
Exception in thread "main" java.lang.NoClassDefFoundError:
com/sun/java/util/collections/ArrayList
at weblogic.kernel.Kernel.declareProperties(Kernel.java:253)
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:107)
at weblogic.common.T3Client.<init>(T3Client.java:218)
at weblogic.common.T3Client.<init>(T3Client.java:269)
at weblogic.common.T3Client.<init>(T3Client.java:323)
at weblogic.jdbcbase.t3.Driver.connect(Driver.java:121)
at java.sql.DriverManager.getConnection(Compiled Code)
at java.sql.DriverManager.getConnection(DriverManager.java:106)
at utils.t3dbping.main(t3dbping.java:115)
Thanks,
Laurie

Problem in WSAD 5.0.0 with Oracle thin Driver

Hi All,
Can anyone help me to solve the following problem while using a batch update
java.lang.NullPointerException
     at oracle.jdbc.dbaccess.DBData.clearItem(DBData.java:431)
     at oracle.jdbc.dbaccess.DBDataSetImpl.clearItem(DBDataSetImpl.java:3528)
     at oracle.jdbc.driver.OraclePreparedStatement.clearParameters(OraclePreparedStatement.java:3401)
     at oracle.jdbc.driver.OracleCallableStatement.clearParameters(OracleCallableStatement.java:818)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.resetStatement(WSJdbcConnection.java:1767)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.prepareCall(WSJdbcConnection.java:1381)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.prepareCall(WSJdbcConnection.java:1346)
     at com.americanexpress.statdc.manual.dao.ManualStatLoadDAO.loadStatItems(ManualStatLoadDAO.java:668)
     at com.americanexpress.statdc.manual.dao.ManualStatLoadDAO.submitStatItems(ManualStatLoadDAO.java:609)
     at com.americanexpress.statdc.manual.ejb.ManualStatLoadEJBBean.submitStatItems(ManualStatLoadEJBBean.java:252)
     at com.americanexpress.statdc.manual.ejb.EJSRemoteStatelessManualStatLoadEJB_38e2da07.submitStatItems(EJSRemoteStatelessManualStatLoadEJB_38e2da07.java:472)
     at com.americanexpress.statdc.manual.ejb._ManualStatLoadEJB_Stub.submitStatItems(_ManualStatLoadEJB_Stub.java:451)
     at com.americanexpress.statdc.manual.businessdelegate.ManualStatLoadBusinessDelegate.submitStatItems(ManualStatLoadBusinessDelegate.java:86)
     at com.americanexpress.statdc.manual.handlers.InputterStatDataRequestHandler.processRequest(InputterStatDataRequestHandler.java:123)
     at com.americanexpress.util.frontservlet.FrontServlet.processRequest(Unknown Source)
     at com.americanexpress.util.frontservlet.FrontServlet.doPost(Unknown Source)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
     at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
     at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
     at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
     at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
     at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:76)
     at com.americanexpress.statdc.infrastructure.filter.StatDCGZipFilter.doFilter(StatDCGZipFilter.java:59)
     at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:132)
     at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:71)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:1064)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:598)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:206)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:80)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:214)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:116)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:623)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:447)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672)
This exception is occuring at the time of preparing the Callable Statement.
We are using WSAD 5.0.0 with JDK 1.3.1, Oracle thin driver for Oracle 9i.
Thanks in advance.
Regards,
Shesha

Hi,
This problem is caused by bug in the jdbc oracle driver:
oracle.jdbc.dbaccess.DBData.clearItem(DBData.java:431)
Line 431 looks like:
/* 431 */ if(m_items == null && i >= m_items.length) // it never works!
NullPointerException occures when you call
java.sql.CallableStatement.clearParameters()
1. Avoid to call this method in your code.
2. Websphere also calls this method in the WSJdbcConnection.class (while reusing the statement after caching it).
You may force websphere not to reuse your statement for example by adding timestamp to it as comment:
String timestamp = String.valueOf(System.currentTimeMillis());
String myCommand = "call myprocedure( ?, ?) -- " + timestamp);
conn.prepareCall(myCommand);

Problems with Oracle Thin Driver

Hi,
I'm having major problems configuring the Oracle Thin Driver for use
with CMP Entity Beans. What am I doing wrong?
Configuration: Windows 2000 Professional, WebLogic 6.1, Oracle 8.1.6,
Oracle Thin Driver 8.1.7 (classes12.zip is the first thing in the
classpath)
I first created the connection pool through the console, here's the
generated xml:
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
MaxCapacity="2" Name="myXAPool"
Properties="user=XXX;url=jdbc:oracle:thin:@192.168.0.145:1521:db;password=XXX;dataSourceName=myXAPool"
Targets="server"/>
The connection pool deployed fine, so I went ahead and created the TX
DataSource through the console:
<JDBCTxDataSource JNDIName="mySource" Name="myXASource"
PoolName="myXAPool" Targets="server"/>
The log file shows that the TX DataSource was also created. Next step
was deploying the application. I created a new application through the
console and uploaded the ear file containing the application (several
SessionBeans, EntityBeans and a web application). Upon loading the first
CMP EntityBean (They have "mySource" set as the name of the DataSource
in the <data-source-name> tag), the following error showed up in the
log:
<04.10.2001 09:02:50 CEST> <Info> <EJB> <EJB Deploying file:
ContractClassStopover.jar>
<04.10.2001 09:02:51 CEST> <Error> <J2EE> <Error deploying application
ContractClassStopover:
Unable to deploy EJB: ContractClassStopoverBean from
ContractClassStopover.jar:
The Entity EJB requires the table: CONTRACT_CLASS_STOPOVER to be
accessible. Please ensure that this table exists and is accessible.
>
<04.10.2001 09:02:51 CEST> <Error> <Management> <Error deploying
application .\config\server\applications\app.ear:
java.lang.reflect.UndeclaredThrowableException>
The table exists, so I had a look at the jdbc log file. Here's what
happened in there:
DRVR FUNC OracleConnection.OracleConnection(par, pc, autoCommit=false)
DRVR FUNC
OracleConnection.initialize(ur="jdbc:oracle:thin:@192.168.0.145:1521:db",
us="XXX", access)
DRVR FUNC OracleConnection.initClientDataSupport()
DRVR OPER OracleConnection.setAutoCommit(autoCommit=false)
DRVR OPER OracleConnection.getAutoCommit() returned false
DRVR DBG1 OracleXAResource.start():start
DRVR DBG1 Should use OracleXid for 8.1.6 database
DRVR OPER OracleConnection.getTransactionIsolation() returned 2
DRVR OPER OracleConnection.isReadOnly()
DRVR OPER OracleConnection.getCatalog()
DRVR OPER OracleConnection.getAutoCommit() returned false
DRVR OPER OracleConnection.close()
DRVR OPER OracleConnection.close()
DRVR FUNC OracleConnection.OracleConnection(par, pc, autoCommit=false)
DRVR FUNC
OracleConnection.initialize(ur="jdbc:oracle:thin:@192.168.0.145:1521:db",
us="XXX", access)
DRVR FUNC OracleConnection.initClientDataSupport()
DRVR OPER OracleConnection.setAutoCommit(autoCommit=false)
DRVR OPER OracleConnection.getAutoCommit() returned false
SQLException: SQLState() vendor code(-6)
java.sql.SQLException: XA error: XAER_PROTO : Routine was invoked in an
inproper context start() failed on resource 'myXAPool' null
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1044)
at
weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1010)
at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:148)
at
weblogic.jdbc.jta.Connection.prepareStatement(Connection.java:226)
at
weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
at
weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
at
weblogic.ejb20.utils.TableVerifier.checkTableAndColumns(TableVerifier.java:125)
at
weblogic.ejb20.utils.TableVerifier.verifyTableAndColumnsExist(TableVerifier.java:226)
at
weblogic.ejb20.utils.TableVerifier.verifyTableExistsAndCreateMaybe(TableVerifier.java:294)
at
weblogic.ejb20.cmp11.rdbms.PersistenceManagerImpl.verifyTablesExist(PersistenceManagerImpl.java:172)
at
weblogic.ejb20.cmp11.rdbms.PersistenceManagerImpl.setup(PersistenceManagerImpl.java:120)
at
weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:197)
at
weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:173)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:793)
at
weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1250)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:939)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.addComponent(Application.java:160)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:482)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:926)
at
weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:913)
at
weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:898)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:618)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy68.addTarget(Unknown Source)
at
weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:833)
at
weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:930)
at
weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:852)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:768)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:701)
at
weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:198)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy5.update(Unknown Source)
at
weblogic.management.console.webapp._domain.__upload_app._jspService(__upload_app.java:150)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:263)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:190)
at
weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at
weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java:35)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:172)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:263)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2390)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1959)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Can someone please help me figure out what's going wrong here?
Thanks in advance,
Nils
============================
[email protected]

Thanks for the reply!! I was expecting something like this. I will look
into an upgrade to 8.1.7.
Take care,
Nils
Priscilla Fung wrote:
>
Hi,
You need to use an Oracle 8.1.7 server for XA features. Refer to Third Party
JDBC XA drivers doc for more info: http://e-docs.bea.com/wls/docs61/jta/thirdpartytx.html#1070650
Regards,
Priscilla
Nils Winkler <[email protected]> wrote:
Hi,
I'm having major problems configuring the Oracle Thin Driver for use
with CMP Entity Beans. What am I doing wrong?
Configuration: Windows 2000 Professional, WebLogic 6.1, Oracle 8.1.6,
Oracle Thin Driver 8.1.7 (classes12.zip is the first thing in the
classpath)
I first created the connection pool through the console, here's the
generated xml:
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
MaxCapacity="2" Name="myXAPool"
Properties="user=XXX;url=jdbc:oracle:thin:@192.168.0.145:1521:db;password=XXX;dataSourceName=myXAPool"
Targets="server"/>
The connection pool deployed fine, so I went ahead and created the TX
DataSource through the console:
<JDBCTxDataSource JNDIName="mySource" Name="myXASource"
PoolName="myXAPool" Targets="server"/>
The log file shows that the TX DataSource was also created. Next step
was deploying the application. I created a new application through the
console and uploaded the ear file containing the application (several
SessionBeans, EntityBeans and a web application). Upon loading the first
CMP EntityBean (They have "mySource" set as the name of the DataSource
in the <data-source-name> tag), the following error showed up in the
log:
<04.10.2001 09:02:50 CEST> <Info> <EJB> <EJB Deploying file:
ContractClassStopover.jar>
<04.10.2001 09:02:51 CEST> <Error> <J2EE> <Error deploying application
ContractClassStopover:
Unable to deploy EJB: ContractClassStopoverBean from
ContractClassStopover.jar:
The Entity EJB requires the table: CONTRACT_CLASS_STOPOVER to be
accessible. Please ensure that this table exists and is accessible.
>
<04.10.2001 09:02:51 CEST> <Error> <Management> <Error deploying
application .\config\server\applications\app.ear:
java.lang.reflect.UndeclaredThrowableException>
The table exists, so I had a look at the jdbc log file. Here's what
happened in there:
DRVR FUNC OracleConnection.OracleConnection(par, pc, autoCommit=false)
DRVR FUNC
OracleConnection.initialize(ur="jdbc:oracle:thin:@192.168.0.145:1521:db",
us="XXX", access)
DRVR FUNC OracleConnection.initClientDataSupport()
DRVR OPER OracleConnection.setAutoCommit(autoCommit=false)
DRVR OPER OracleConnection.getAutoCommit() returned false
DRVR DBG1 OracleXAResource.start():start
DRVR DBG1 Should use OracleXid for 8.1.6 database
DRVR OPER OracleConnection.getTransactionIsolation() returned 2
DRVR OPER OracleConnection.isReadOnly()
DRVR OPER OracleConnection.getCatalog()
DRVR OPER OracleConnection.getAutoCommit() returned false
DRVR OPER OracleConnection.close()
DRVR OPER OracleConnection.close()
DRVR FUNC OracleConnection.OracleConnection(par, pc, autoCommit=false)
DRVR FUNC
OracleConnection.initialize(ur="jdbc:oracle:thin:@192.168.0.145:1521:db",
us="XXX", access)
DRVR FUNC OracleConnection.initClientDataSupport()
DRVR OPER OracleConnection.setAutoCommit(autoCommit=false)
DRVR OPER OracleConnection.getAutoCommit() returned false
SQLException: SQLState() vendor code(-6)
java.sql.SQLException: XA error: XAER_PROTO : Routine was invoked in
an
inproper context start() failed on resource 'myXAPool' null
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1044)
at
weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1010)
at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:148)
at
weblogic.jdbc.jta.Connection.prepareStatement(Connection.java:226)
at
weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
at
weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
at
weblogic.ejb20.utils.TableVerifier.checkTableAndColumns(TableVerifier.java:125)
at
weblogic.ejb20.utils.TableVerifier.verifyTableAndColumnsExist(TableVerifier.java:226)
at
weblogic.ejb20.utils.TableVerifier.verifyTableExistsAndCreateMaybe(TableVerifier.java:294)
at
weblogic.ejb20.cmp11.rdbms.PersistenceManagerImpl.verifyTablesExist(PersistenceManagerImpl.java:172)
at
weblogic.ejb20.cmp11.rdbms.PersistenceManagerImpl.setup(PersistenceManagerImpl.java:120)
at
weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:197)
at
weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:173)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:793)
at
weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1250)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:939)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.addComponent(Application.java:160)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:482)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:926)
at
weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:913)
at
weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:898)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:618)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy68.addTarget(Unknown Source)
at
weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:833)
at
weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:930)
at
weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:852)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:768)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:701)
at
weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:198)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy5.update(Unknown Source)
at
weblogic.management.console.webapp._domain.__upload_app._jspService(__upload_app.java:150)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:263)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:190)
at
weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at
weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java:35)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:172)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:263)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2390)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1959)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Can someone please help me figure out what's going wrong here?
Thanks in advance,
Nils
============================
[email protected]
============================
[email protected]

Web Logic 6.1 JDBC Pooling with the Oracle Thin Driver

Hi,
We're slowly getting through a WebLogic 4.5.1 to 6.1 conversion for a small application
at my company. Initially, we had trouble getting the Oracle thin driver working.
We've finally cracked this nut. Now we're trying to get pooling working, and
cannot find an example of doing this with the Oracle thin driver.
Would anyone be able to provide:
1. the portion of the config.xml that pertains to building a connection pool using
the Oracle thin driver
2. the two lines of code for loading the driver and getting a connection from
this pool
i.e.
Driver d = (Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
Connection c = d.connect("jdbc:weblogic:pool:myPool", null);
Thanks very much!
Jeff Ryan
The Hartford

"Jeff Ryan" <[email protected]> wrote:
>
1. the portion of the config.xml that pertains to building a connection
pool using
the Oracle thin driver
You don't usually edit the config.xml unless it is absolutely necessar. Instead,
you can config the pool in the GUI admin console, quite easily. After you successfully
configed the pool in the console, it is written into the config.xml file for you.
Only thing special when config the pool is the name of the driver and the url.
url: jdbc:oracle:thin@dbhost:dbport:dbinstance
driver: oracle.jdbc.driver.OracleDriver
If you prefer, you can also config the pool from the command line. It is detailed
in the "Weblogic Server Command-line Interface Reference".
2. the two lines of code for loading the driver and getting a connection
from
this pool
i.e.
Driver d = (Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
Connection c = d.connect("jdbc:weblogic:pool:myPool", null);
Again, you don't use the connection directly. Instead, you use "Data Source".
Data source in weblogic is just a connection object factory associated with a
JNDI name. You can therefore lookup the data source with the JNDI name and from
the data source object, you get the connectin object. No need to explicitly load
the driver class.
There are plenty of example codes available in the weblogic examples installed
with 6.1, that uses the data source.
Charles

Dbping errors with Oracle8.1.5 and Oracle thin driver

I am trying to connect to Oracle 8.1.5.0.0 with Oracle thin driver 8.1.5. However I keep getting error ORA-24327. Any suggestions on how to fix this error?

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Jayanta Ghosh ([email protected]):
Hi,
Does XML parser for PL/SQL work with Oracle 8.1.5? Did any one install the
same and if so what are steps to follow? I ran initjvm.sql to install
JServer and then tried to load jar files using loadjava, but it's giving
error. It's working fine with Oracle8.1.6.
Any idea?
Thanks,
Jayanta<HR></BLOCKQUOTE>
Oracle XML Parser has differents distributions for 8.1.5 and 8.1.6 databases, try the correct version, then runs the oraclexmlsqlload.csh from the lib directory of XSU distribution.
Best regards, Marcelo.
null

Update Batching With Oracle Thin Driver

executeBatch() method throws missing IN or Out Parameters when used with Oracle
thin driver(jdbc.oracle.driver.OracleDriver)

Thanks for the reply. But, I tried it and I still get the same problem. Now
I am running on Solaris 7. Does that make a difference?
-Sudheendra
"Slava Imeshev" <[email protected]> wrote in message
news:[email protected]..
Hi Sudheendra,
Here is the patch for 5.1 put it as the first thing
in weblogic.classpath.
Regards,
Slava Imeshev
"Sudheendra Galgali" <[email protected]> wrote in message
news:3b69a4be$[email protected]..
I am having a similar problem with WL 5.1, service pack 9 with Oracle Thin
drivers. I am unable to find patch CR047274 either. Help please!
"Soumik" <[email protected]> wrote in message
news:[email protected]..
executeBatch() method throws missing IN or Out Parameters when used with
Oracle
thin driver(jdbc.oracle.driver.OracleDriver)

Using oracle thin driver with to_char gives invalid column name

select x,y,z, to_char(event_time,'YYYY-MMM-DD') from eventtable;
if i execute the above query using oracle thin driver it gives me invalid column name. It works fine if i use weblogic driver. So what could be the problem ???
thanks.

Sorry , forgot to add that 'YYYY-MM-DD' or 'YYYY-Month-DD' or 'Year-MM-DD' or 'Year-Month-DD' are also allowed(please cheek also for other combinations), not 'YYYY-MMM-DD'.
Thanks

How to use oracle thin driver with jsp?...pls help

Hello. I am trying to insert a word file into my Oracle 9i database using JSP. I have tomcat running as my standalone server. So far, i have been using the sun.jdbc.odbc driver to implement all my DB accesses. Recently however, i found out that in order to use Oracle specific objects such as BLOBS or BFILES, i have to use the oracle thin driver or OCI driver.
So far, i have downloaded the thin driver and put it into the tomcat shared/common folder and also put the .jar file into my classpath. Now, i am having trouble as to how to call the oracle thin driver inside my JSP code.
My previous code read as:
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection con = DriverManager.getConnection("jdbc:odbc:Andy","user","pass");
How do i switch over to the oracle thin driver in JSP? Any help would be much appreciated. Thank you
Andrew

my code is:
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
conn = DriverManager.getConnection(sConnStr, sUser, sPassword);
notice the driver --"oracle.jdbc.driver.OracleDriver"!
and copy the class12.zip to lib path
if still not work
change the class12.zip to class12.jar
good luck

Multiple ResultSets with Oracle Thin Driver.

Hi,
I am using Oracle Thin Driver to Connect to the Oracle Database (8.1.7). I wanted to take advantage
of the multiple Resultsets Scenario for fetching Data from the DB. Please have a look at the code
fragment below.
String sql = "select * from TAB1; select * from TAB2";
Connection conn = getConnection();
PreparedStatement stmnt = conn.prepareStatement(sql);
stmnt.execute();
However , I am getting the following Error.
java.sql.SQLException: ORA-00911: invalid character
Could anyone give me the possible reason/corrected syntax for the SQL.
Thanks for any help in advance.

It's unclear what your problem is...
However...
Oracle will only execute one SQL statement at a time in a Statement or PreparedStatement; therefore these can only return a single ResultSet.
However, an Oracle stored procedure can be written to return multiple results; it can therefore be run from a CallableStatement and getMoreResults() is then used to get the additional ResultSet data.
An example of doing this is here:
http://edocs.beasys.com/wls/docs81/jdbc_drivers/oracle.html
scroll towards the bottom and look for Listing 5-3

ORA01002 with Oracle thin driver - not with JDriver

Similar Messages

Maybe you are looking for