Thin driver 9 with Ora8i db ?
Hi,
I was wondering. Is it legal to use the Oracle Thin-driver 9.0.1 when connecting to a Oracle8i 8.1.7.2.0 Enterprise Edition server DB ?
The reason for asking is, that we are experiencing problems with some bugs in the Oracle Thin-driver 8.7.1, which might be fixed in the 9.0.1 driver. We are not updating to use some new features.
Regards, Per Olesen
Hi,
According to the documenttation, yes driver 9 is compatible with Ora8i db (see the link below).
Actually, I have been trying to do the same thing as you except that I need OCI not JDBC driver. I still however have not figured out how to install a driver... do we have to install Oracle Client? do we have to just copy the DLLs and JARs only???
Thanks and good luck!
http://otn.oracle.com/docs/products/oracle9i/doc_library/901_doc/java.901/a90211/getsta.htm#1008206
Similar Messages
-
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 ! -
The simple program below is a client that executes a SELECT query -
there are 13 rows in the table, of which 10 are printed when I run the
program, then after that the ORA-01002 error is reported. I am not
doing anything with LOBs, or updates. I've tried putting
con.setAutoCommit(false) as well, but that does not do anything.
Why am I getting this error? Can anyone help.
Thanks
-H
Context ctx = null;
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL,
"t3://127.0.0.1:7001");
PreparedStatement stmt = null;
ResultSet rs = null;
UserTransaction ut = null;
try {
ctx = new InitialContext(ht);
javax.sql.DataSource ds
= (javax.sql.DataSource) ctx.lookup ("jtaXADS");
java.sql.Connection conn = ds.getConnection();
// You can now use the conn object to create
// Statements and retrieve result sets:
ut = (UserTransaction)
ctx.lookup("javax.transaction.UserTransaction");
ut.begin();
stmt = conn.prepareStatement("select firstname,surname from
EMPLOYEE ");
stmt.executeQuery();
rs = stmt.getResultSet();
// Close the statement and connection objects when you are finished:
while (rs.next())
System.out.println("Result is " + rs.getString("firstname") + " " +
rs.getString("surname"));
ut.commit();
stmt.close();
conn.close();
catch (Exception e) {
e.printStackTrace();
// a failure occurred
finally {
try {ctx.close();
rs.close();}
catch (Exception e) {
// a failure occurred
e.printStackTrace();Thanks everybody.
I have tried this, calling ut.begin() first before getConnection,
however no difference. However the problem goes away if I call
stmt.setFetchSize(100);
But I would prefer not to have to code this in every time!!!
I see there is a setting within Weblogic Admin console to see the
row-prefetch, but that is already set to 45 rows, so why do have to
explicitly call stmt.setFetchSize(100)!!!
Thanks
-H
"Carl Lawstuen" <[email protected]> wrote in message news:<[email protected]>...
Agreed. The transaction must start before the connection. This is what
is most likely causing the error.
"Nils Winkler" <[email protected]> wrote in message
news:[email protected]...
Hi,
one more thing: The UserTransaction has to be started before you obtain
the connection, not after.
Nils
Humphrey wrote:
The simple program below is a client that executes a SELECT query -
there are 13 rows in the table, of which 10 are printed when I run the
program, then after that the ORA-01002 error is reported. I am not
doing anything with LOBs, or updates. I've tried putting
con.setAutoCommit(false) as well, but that does not do anything.
Why am I getting this error? Can anyone help.
Thanks
-H
Context ctx = null;
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL,
"t3://127.0.0.1:7001");
PreparedStatement stmt = null;
ResultSet rs = null;
UserTransaction ut = null;
try {
ctx = new InitialContext(ht);
javax.sql.DataSource ds
= (javax.sql.DataSource) ctx.lookup ("jtaXADS");
java.sql.Connection conn = ds.getConnection();
// You can now use the conn object to create
// Statements and retrieve result sets:
ut = (UserTransaction)
ctx.lookup("javax.transaction.UserTransaction");
ut.begin();
stmt = conn.prepareStatement("select firstname,surname from
EMPLOYEE ");
stmt.executeQuery();
rs = stmt.getResultSet();
// Close the statement and connection objects when you are finished:
while (rs.next())
System.out.println("Result is " + rs.getString("firstname") + " " +
rs.getString("surname"));
ut.commit();
stmt.close();
conn.close();
catch (Exception e) {
e.printStackTrace();
// a failure occurred
finally {
try {ctx.close();
rs.close();}
catch (Exception e) {
// a failure occurred
e.printStackTrace();
============================
[email protected] -
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
..MadhuriMadhuri 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 -
BLOB insert behavior with thin driver using standard JDBC2.0 and ORACLE-JDBC2.0API
We have a problem with a BLOB insert to an oracle 8.1.7 DB using Oracle 8.1.7 JDBC thin driver.We get socket read/write error after inserting 32k of data using the standard JDBC2.0 API but using the Oracle JDBC2.0API (using OracleResultSet) it goes fine. We have a requirement to use the standard JDBC2.0 so that our code works with multiple database vendors. Is there another way to get in the blob data with standard JDBC API & using thin driver...?
thanks,
Madhu
Here is my sample test program that does both standard & oracle specific JDBC Blob test insert.
import java.sql.*;
import java.io.*;
import oracle.sql.BLOB;
import oracle.jdbc.driver.OracleResultSet;
public class testBLOB {
//trying to insert a huge file to a BLOB
static String fileName = "/kernel/genunix";
public static void main(String[] args) {
String driverName = "oracle.jdbc.driver.OracleDriver";
String dbURL = "jdbc:oracle:thin:@localhost:1521:test"; //thin driver
String user = "BlobTest";
String passwd = "BlobTest";
Connection con=null;
try {
Class.forName(driverName);
con=DriverManager.getConnection(dbURL, user,passwd);
catch (Exception e) {
e.printStackTrace();
close(con);
int i = 0;
while (i < args.length) {
if (args.equals("-f"))
fileName = args[++i];
i++;
System.out.println("The file being Stored is: "+fileName);
createTable(con);
insertUsingOracleAPI(con);
insertUsingJDBC20API(con);
//readDB(con);
static String getFileName() {
return fileName;
public static void close(Connection con) {
try {
if (con != null) {
con.close();
catch (Exception e) {
System.exit(-1);
public static void createTable(Connection con) {
Statement stmt ;
try {
stmt = con.createStatement();
stmt.execute("DROP TABLE basic_blob_table");
stmt.close();
catch (SQLException sqlEx) {
System.out.println("Dropped the Table");
try {
stmt = con.createStatement();
stmt.execute("CREATE TABLE basic_blob_table ( x varchar2(30), b blob)");
stmt.close();
catch (SQLException sqlEx) {
sqlEx.printStackTrace();
close(con);
System.out.println("Created the Table");
public static void insertUsingOracleAPI(Connection con) {
OutputStream os = null;
Statement stmt = null;
ResultSet rs = null;
FileInputStream is = null;
try {
con.setAutoCommit(false);
stmt = con.createStatement();
stmt.execute("INSERT INTO basic_blob_table VALUES( 'OracleAPI', empty_blob())");
System.out.println("Inserted the dummy Row");
rs = stmt.executeQuery("Select * from basic_blob_table where x='OracleAPI'");
if (rs != null && rs.next()) {
BLOB blob = ((OracleResultSet)rs).getBLOB(2);
File file = new File(getFileName());
is = new FileInputStream(file);
os = blob.getBinaryOutputStream();
byte[] chunk = new byte[1024];
int length = -1;
while((length = is.read(chunk)) != -1)
os.write(chunk, 0,length);
System.out.println("Inserted the File " + getFileName() );
catch (Exception e) {
e.printStackTrace();
finally {
try {
if (os != null) {
os.flush();
os.close();
if (is != null)
is.close();
stmt.close();
con.commit();
con.setAutoCommit(true);
catch (Exception e) {}
public static void insertUsingJDBC20API(Connection con) {
PreparedStatement stmt = null;
FileInputStream is = null;
try {
stmt = con.prepareStatement("INSERT INTO basic_blob_table VALUES(?,?)");
File file = new File(getFileName());
is = new FileInputStream(file);
stmt.setString(1,"JDBC20API");
stmt.setBinaryStream(2,is,(int)file.length());
stmt.executeUpdate();
catch (Exception e) {
e.printStackTrace();
finally {
try {
if (is != null)
is.close();
stmt.close();
catch (Exception e) {}
nullThanks for the response.
I understand what you are saying...
that readers don't block writers in Oracle (the same is true in SQL Server 2000).
However, I don't see how my test case is working correctly with Oracle (the exact same code acting as I'm thinking it should with SQL Server, but I still think it is acting incorrectly with Oracle).
I have transaction A do this:
update <table> set <column2>=<value> where <column1>='1'
then I use Thread.sleep() to make that program hang around for a few minutes.
Meanwhile I sneak off and start another program which begins transaction B. I have transaction B do this:
select * from <table> where <column1>='1'
and the read works immediately (no blocking... just as you have said) however, transaction A is still sleeping, it has not called commit() or rollback() yet.
So what if transaction A were to call rollback(), the value read by transaction B would be incorrect wouldn't it ?
Both A and B use setAutoCommit(false) to start their transactions, and then call setTransactionIsolation(Connection.TRANSACTION_READ_COMMITTED).
Isn't that supposed to guarantee that a reader can only read what is committed ?
And if a row is in "flux"... in the process of having one or more values changed, then the database cannot say what the value will be ?
I can almost see what you are saying.
In letting the reader have what it wants without making it wait, I suppose it could be said that Oracle is holding true to the "only let committed data be read"
So if that's it, then what if I want the blocking ?
I want an entire row to be locked until whoever it in the middle of updating, adding, or removing it has finished.
Do you know if that can be done with Oracle ? And how ?
Thanks again for helping me. -
Error configuring the Oracle 8.1.7 XA Thin driver with WLS 6.1 SP1
I am trying to configure the Oracle 8.1.7.0 thin driver and am getting an SystemException
when the pool tries to test the connection at server startup. It looks like the
start() method is failing. I have put Oracle's Classes12.zip, jndi.zip, and the
jta.zip on the classpath immediately after the weblogic.jar entry. Is this a
classpath issue? Can someone that has this working please help me. Thanks in
advance. Steve
The following is the JDBC Pool entry in the config.xml file:
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
InitialCapacity="0" LoginDelaySeconds="1" MaxCapacity="20"
Name="oraclePoolSun3500XAThin" Properties="user=sschaber;url=jdbc:oracle:thin:@199.191.94.4:1521:ORCLT;password=sschaber;dataSourceName=oraclePoolSun3500XAThin"
RefreshMinutes="5" ShrinkPeriodMinutes="30"
Targets="memphisserver" TestConnectionsOnRelease="true"
TestConnectionsOnReserve="true" TestTableName="Dual" URL="jdbc:oracle:thin:@199.191.94.4:1521:ORCLT"/>
Also, here is the entire exception being thrown:
<Apr 5, 2002 1:33:08 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin> <javax.transaction.SystemException:
start() failed on resource 'oracle.jdbc.xa.client.Or
acleXAResource' null
at weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo.java:998)
at weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.java:234)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:374)
at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:915)
at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1114)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
<Apr 5, 2002 1:33:08 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin> <This
connection will now be refreshed.>
<Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC> <Connection for XA pool "oraclePoolSun3500XAThin"
refreshed.>
<Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin> <A connection
from pool oraclePoolSun3500XAThin was tested during reserve with a select
count(*) from Dual and failed:>
<Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin> <javax.transaction.SystemException:
start() failed on resource 'oracle.jdbc.xa.client.Or
acleXAResource' null at weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo.java:998)
at weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.java:234)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:374)
at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:915)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:465)
at weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.java:376)
at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1103)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
<Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin> <This
connection will now be refreshed.>This still does not work for me. I must be missing something here. Any help would
be appreciated.
Thanks,
Steve
"Sree Bodapati" <[email protected]> wrote:
Hi Steve,
I see the initial capacity is set to zero , can you push it up to atleast
few connections and see if it helps, and Let me know.
thanks
sree
"Steve Schaber" <[email protected]> wrote in message
news:[email protected]...
I made sure that we have the latest version of the classes12.zip file(8.1.7).
Also, moved the classes12.zip, jndi.zip, and the jta.zip file beforethe
weblogic.jar
file in the classpath. I am still getting the same error.
Steve
"Sree Bodapati" <[email protected]> wrote:
Put the classes12.zip and other zip files before the weblogic.jar
file
in
the classpath. ensure that you have the latest classes12.zip filefrom
oracle.
sree
"Steve Schaber" <[email protected]> wrote in message
news:[email protected]...
I am trying to configure the Oracle 8.1.7.0 thin driver and am gettingan
SystemException
when the pool tries to test the connection at server startup. It
looks
like the
start() method is failing. I have put Oracle's Classes12.zip,
jndi.zip,
and the
jta.zip on the classpath immediately after the weblogic.jar entry.Is
this a
classpath issue? Can someone that has this working please help
me.
Thanks in
advance. Steve
The following is the JDBC Pool entry in the config.xml file:
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
InitialCapacity="0" LoginDelaySeconds="1" MaxCapacity="20"
Name="oraclePoolSun3500XAThin"
Properties="user=sschaber;url=jdbc:oracle:thin:@199.191.94.4:1521:ORCLT;pass
word=sschaber;dataSourceName=oraclePoolSun3500XAThin"
RefreshMinutes="5" ShrinkPeriodMinutes="30"
Targets="memphisserver" TestConnectionsOnRelease="true"
TestConnectionsOnReserve="true" TestTableName="Dual"URL="jdbc:oracle:thin:@199.191.94.4:1521:ORCLT"/>
Also, here is the entire exception being thrown:
<Apr 5, 2002 1:33:08 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin><javax.transaction.SystemException:
start() failed on resource 'oracle.jdbc.xa.client.Or
acleXAResource' null
at
weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo..
java:998)
at
weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.j
ava:234)
at
weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTra
nsactionImpl.java:374)
atweblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:915)
at
weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:11
14)
at
weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigg
er.java:238)
at
weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java
:229)
atweblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
<Apr 5, 2002 1:33:08 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin><This
connection will now be refreshed.>
<Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC> <Connection for XA pool"oraclePoolSun3500XAThin"
refreshed.>
<Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin><A
connection
from pool oraclePoolSun3500XAThin was tested during reserve with
a
select
count(*) from Dual and failed:>
<Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin><javax.transaction.SystemException:
start() failed on resource 'oracle.jdbc.xa.client.Or
acleXAResource' null at
weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo..
java:998)
at
weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.j
ava:234)
at
weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTra
nsactionImpl.java:374)
atweblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:915)
at
weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:46
5)
at
weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.j
ava:376)
at
weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:11
03)
at
weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigg
er.java:238)
at
weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java
:229)
atweblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
<Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin><This
connection will now be refreshed.> -
Problem Thin Driver with browser
I have an applet that used Oracle JDBC Driver (Thin) to
connect my applet to Oracle DBMS.
But i have two problem with this driver :
1. If on the client side doesnt have file of Oracle JDBC
Driver(classes111.zip) or if environment variable
CLASSPATH on the client side doesnt set to the path of
Oracle JDBC Driver file, my applet doesnt work.
Error message that raised is 'No Suitable Driver'.
However, if I read in the documentation of Oracle JDBC
Driver, it says that Thin Driver is type 4 driver that
doesnt require Oracle-spesific software or files on
the client side.
So, is a mistake on my applet or client must have Oracle
JDBC driver (classes111.zip) and set the classpath to
that file ?
2. If i used Netscape browser, i have a problem with the
security. The error said "security.couldn't connect to
'202.154.5.29' with origin from '202.154.5.21' .
202.154.5.29 is my database server and 202.154.5.21
is my internet web server.
What is that mean and what i have to do ???
nulltry this:
conn = DriverManager.getConnection("jdbc:oracle:thin:scott/tiger:@hostname:1521:sid");
or use system/manager as username/passward
null -
JSP Not Working with Thin Driver
My JSP is not working with Oracle thin driver but it is working with Oracle OCI driver.
From my jsp i am calling a stored procedured and passing 170 parameters to the procedure. This JSP works with Oracle OCI Driver configured as thrid party drivers in iAS6.0 SP2, but not working with Oracle Thin Driver configured as third party drivers in iAS6.0. My thin driver JDBC Connection URL is as follows:
jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = MAPDBI01)(PORT = 1521)))(CONNECT_DATA =(SID = MAPS))).
I have to give this URL because my production server deployment consists of iWS4.1 SP5 and iAS6.0 SP2 in different solaris boxes and Oracle 8.1.7 Database server in another Solaris Box. There is a pool of proxy servers between iAS6.0 box and the oracle box.Wim,
I'd really appreciate it if you could provide some sample code. A complete, small, simple java class that I could copy and try out would be wonderful -- if it's not too much trouble.
Thanks heaps (in advance :-),
Avi. -
Hi,
I'm using the build-in Oracle 8.1.6 thin driver that comes with
weblogic.jar of WebLogic 6.0 SP2. It doesn't store CLOBs. Here I have
to use the class weblogic.jdbc.common.OracleClob. Why?
WebLogic 5.1 SP 9 + Oracle 8.1.6 thin driver (external) does. Here I
use the class oracle.sql.CLOB.
Must I use a OCI driver?
Thanks,
JuergenI'd also recommend to switch to 8.1.7 thin driver. It's more stable.
Regards,
Slava Imeshev
"NhaBep" <[email protected]> wrote in message
news:3b71bbcf$[email protected]..
>
You can use thin driver to persist CLOB. One thing you must be sure to setautocommit
to false. Hope this help.
[email protected] (Juergen) wrote:
Hi,
I'm using the build-in Oracle 8.1.6 thin driver that comes with
weblogic.jar of WebLogic 6.0 SP2. It doesn't store CLOBs. Here I have
to use the class weblogic.jdbc.common.OracleClob. Why?
WebLogic 5.1 SP 9 + Oracle 8.1.6 thin driver (external) does. Here I
use the class oracle.sql.CLOB.
Must I use a OCI driver?
Thanks,
Juergen -
Jdbc thin driver with Oracle 9i database
Hi,
I'm having a problem with java code which previously deployed ok on an Oracle 817 database. In attempting to access data from a 9i database I get the following error:
java.sql.SQLException: ORA-00600: internal error code, arguments: [ttcgcshnd-1], [0], [], [], [], [], [], []
From looking around I get the impression that the problem is with an incompatability with the driver and the 9i database. Any ideas as to whether this is true or not or suggestions on how to resolve it?
Any help will be greatly appreciated.
Thanks,
AlisonI don(t understand,my JBuilder use the libraries from Oracle 9.01
and when I make a connection,
with this code:
DatabaseMetaData meta = conn.getMetaData();
System.out.println("JDBC driver version is " + meta.getDriverVersion());
It send me back thin driver 8.17
how is it possible? -
Hanging problem with Oracle JDBC thin driver
Hi. We have an application running on top of WLS 6.1 accessing Oracle 8I with oracle's
JDBC thin driver. Under stress testing, it appears to hang sometimes. Thread dump
shows that many threads seem to be stuck at the same line of code in JDBC driver
(at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)). Has anyone run into similar
issue? Any help is much appreciated.
"ExecuteThread: '1' for queue: 'default'" daemon prio=5 tid=0xe18960 nid=0xf wai
ting on monitor [0xb3680000..0xb36819d8]
at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)
at oracle.sql.NUMBER._fromLnxFmt(NUMBER.java:2953)
at oracle.sql.NUMBER.toBigDecimal(NUMBER.java:557)
at oracle.sql.NUMBER.bigDecimalValue(NUMBER.java:1872)
at oracle.jdbc.dbaccess.DBConversion.NumberBytesToBigDecimal(DBConversion.ja
va:1771)
at oracle.jdbc.driver.OracleStatement.getBigDecimalValue(OracleStatement.jav
a:3357)
at oracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
66)
at oracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
23)
at oracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSetImpl.java
:401)
at weblogic.jdbc.jts.ResultSet.getObject(ResultSet.java:268)
at weblogic.jdbc.rmi.internal.ResultSetImpl.getObject(ResultSetImpl.java:592
at weblogic.jdbc.rmi.internal.ResultSetStraightReader.getObject(ResultSetStr
aightReader.java:198)
at weblogic.jdbc.rmi.SerialResultSet.getObject(SerialResultSet.java:682)
"ExecuteThread: '6' for queue: 'default'" daemon prio=5 tid=0x6d93a8 nid=0x14
wa
iting on monitor [0xb3180000..0xb31819d8]
at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)
at oracle.sql.NUMBER._fromLnxFmt(NUMBER.java:2953)
at oracle.sql.NUMBER.toBigDecimal(NUMBER.java:557)
at oracle.sql.NUMBER.bigDecimalValue(NUMBER.java:1872)
at oracle.jdbc.dbaccess.DBConversion.NumberBytesToBigDecimal(DBConversion.ja
va:1771)
at oracle.jdbc.driver.OracleStatement.getBigDecimalValue(OracleStatement.jav
a:3357)
at oracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
66)
at oracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
23)
at oracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSetImpl.java
:401)
at weblogic.jdbc.jts.ResultSet.getObject(ResultSet.java:268)
at weblogic.jdbc.rmi.internal.ResultSetImpl.getObject(ResultSetImpl.java:592
at weblogic.jdbc.rmi.internal.ResultSetStraightReader.getObject(ResultSetStr
aightReader.java:198)
at weblogic.jdbc.rmi.SerialResultSet.getObject(SerialResultSet.java:682)Try get the latest thin driver from oracle and place it in the beginning of
the classpath in the server startup script to use it. This seems like a
oracle thin driver bug, the newer driver might help.
sree
"Andrew Dong" <[email protected]> wrote in message
news:[email protected]...
>
Hi. We have an application running on top of WLS 6.1 accessing Oracle 8Iwith oracle's
JDBC thin driver. Under stress testing, it appears to hang sometimes.Thread dump
shows that many threads seem to be stuck at the same line of code in JDBCdriver
(at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)). Has anyone run intosimilar
issue? Any help is much appreciated.
"ExecuteThread: '1' for queue: 'default'" daemon prio=5 tid=0xe18960nid=0xf wai
ting on monitor [0xb3680000..0xb36819d8]
at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)
at oracle.sql.NUMBER._fromLnxFmt(NUMBER.java:2953)
at oracle.sql.NUMBER.toBigDecimal(NUMBER.java:557)
at oracle.sql.NUMBER.bigDecimalValue(NUMBER.java:1872)
atoracle.jdbc.dbaccess.DBConversion.NumberBytesToBigDecimal(DBConversion.ja
va:1771)
atoracle.jdbc.driver.OracleStatement.getBigDecimalValue(OracleStatement.jav
a:3357)
atoracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
66)
atoracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
23)
atoracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSetImpl.java
:401)
at weblogic.jdbc.jts.ResultSet.getObject(ResultSet.java:268)
atweblogic.jdbc.rmi.internal.ResultSetImpl.getObject(ResultSetImpl.java:592
atweblogic.jdbc.rmi.internal.ResultSetStraightReader.getObject(ResultSetStr
aightReader.java:198)
atweblogic.jdbc.rmi.SerialResultSet.getObject(SerialResultSet.java:682)
>
"ExecuteThread: '6' for queue: 'default'" daemon prio=5 tid=0x6d93a8nid=0x14
wa
iting on monitor [0xb3180000..0xb31819d8]
at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)
at oracle.sql.NUMBER._fromLnxFmt(NUMBER.java:2953)
at oracle.sql.NUMBER.toBigDecimal(NUMBER.java:557)
at oracle.sql.NUMBER.bigDecimalValue(NUMBER.java:1872)
atoracle.jdbc.dbaccess.DBConversion.NumberBytesToBigDecimal(DBConversion.ja
va:1771)
atoracle.jdbc.driver.OracleStatement.getBigDecimalValue(OracleStatement.jav
a:3357)
atoracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
66)
atoracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
23)
atoracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSetImpl.java
:401)
at weblogic.jdbc.jts.ResultSet.getObject(ResultSet.java:268)
atweblogic.jdbc.rmi.internal.ResultSetImpl.getObject(ResultSetImpl.java:592
atweblogic.jdbc.rmi.internal.ResultSetStraightReader.getObject(ResultSetStr
aightReader.java:198)
atweblogic.jdbc.rmi.SerialResultSet.getObject(SerialResultSet.java:682)
>
> -
Hi Everyone,
Please let me know whether the JDBC thin driver 10.1.0.3 Driver compatible with the oracle server 10G version 10.2.0.2.0? We are facing some issues with the compatibility.
The Errors we are getting is : StaleConnectionException while we are using the driver from the Websphere.
Please let us know..Very Urgent.
Thanks in Advance,
Samuel.
Message was edited by:
user637857Hi Legatti,
Thanks for taking time out and replying me.
We dont know the reason why that error is being caused. Because the error is caused on the production we are not able to make any trail and errors. If we are sure that the driver compatibility is causing the error then we can go ahead and download the latest driver. If the latest driver will solve the problem we have to convince the client that the error is caused due to the incompatible driver. So if you have any documents/information supporting that please help.
Thanks
Samuel. -
Oracle 8i DATE column returned wrong with 9i thin driver
I have an Oracle 8i database with a column named "timestamp" with the following column metadata:
DATA_TYPE=93
TYPE_NAME=DATE
I execute the following statement:
select "timestamp" from oracle_data_log
When I look at the result set metadata using the Oracle 9i drivers, I get (as expected):
getColumnType=93
getColumnTypeName=DATE
getColumnClassName=java.sql.Timestamp
When I look at the result set metadata using the Oracle 9i drivers, I get:
getColumnType=91
getColumnTypeName=DATE
getColumnClassName=java.sql.Timestamp
That column type 91 indicates it is SQL type DATE which is for date only values (no time information).
Our code (working against many different databases with many different drivers) works off the column type metadata and messes up. (Obviously I can look at the column class name string as well / instead, but I'd like the column type to come back with the proper SQL type.)
As I said, it works as expected with the 8i thin driver (and the DataDirect JDBC driver).Thanks for the info.
It seems to me that returning a SQL type DATE (which means it only stores date information) for an Oracle DATE type (which stores date and time information) is the wrong thing to do. The Oracle DATE type stores date and time information which corresponds to the SQL TIMESTAMP type. It should return TIMESTAMP as the SQL type.
It seems like it would confuse a client application into thinking there is no time information available, which there is.
A friend suggested that since a SELECT on a DATE value only displays the date portion and not the time portion, that might be why they did it, but that still doesn't sound right. The Oracle DATE type stores date and time which corresponds to the SQL TIMESTAMP type.
I guess they might have done it to distinguish between Oracle DATE and TIMESTAMP types, but I still don't like it...
I wonder if there is any documentation on why Oracle made the decision? -
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] -
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.setEscapeProcessingMohit,
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
Maybe you are looking for
-
Hi, I went into the support section for authorizing a new computer and it says the following: Open iTunes From the Store menu, choose Authorize This Computer. (In earlier versions of iTunes, access this option from the Advanced menu). When prompted,
-
How to fetch PO item delivery address from ME23n
Dear Experts, From ME23n, I have to fetch the delivery address for the po items ( at item level). This is mentioned in the 'Delivery Address' tab at item level details. I think this is the plant address, but if the user goes to ME22n and delib
-
Navigation between two webdynpro applications
Hi Colleagues, Please let me know some workaround for the below requirement here i have two webdynpro application, where i have to call the second application from a button of first application by passing a parameter please let me know hoe to proceed
-
I am connecting wirelessly to my WRT350N using the WPC300N wireless card, XP Pro. If I try and back up my laptop, either using the USB storage connection or using a gigabit NAS, the wireless connection either degrades to 1Mbs or drops off completely.
-
System setting for vendor evaluation incomplete
HI.... I want to caryout automatic vendor evaluation when i run t code ME63, its show an error system setting for purchase org incomplete where as i have maintained all the parameters from standarfd 0001, can anyone tell me how to carry out ven evalu