OCI JDBC Driver migration

Hi,
We are trying to make a migration from Thin driver to OCI in a Java-Oracle application. All the paths seems to be OK (OCI classes are in casses12.zip, aren4t they?) , we have an Oacle client in the machine and the program says:"java.lang.UnsatisfiedLinkError:no ocijdbc8 in java.library.path"
In any case, is it reasonable change from Thin to OCI
to get better performance?
Thanks.

Some more info from gdb at the point of the segmentation fault:
(gdb) bt
#0 0x00002ad2b30a1326 in ?? ()
#1 0x00002aaadbfcc938 in ?? ()
#2 0x00002ad2b21dea13 in InterpreterRuntime::resolve_invoke () from /usr/local/java/jre/lib/amd64/server/libjvm.so
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) info reg
rax 0x2aaaeac240f8 46913571406072
rbx 0x2aaaeac240f8 46913571406072
rcx 0x2aaadbfcc938 46913323583800
rdx 0x0 0
rsi 0x2aaadbfcc938 46913323583800
rdi 0x2aaab1c6dba8 46912615406504
rbp 0x0 0x0
rsp 0x42675760 0x42675760
r8 0x2ad2b27e8000 47084426133504
r9 0x2aaab1c6d7f8 46912615405560
r10 0x2ad2b27b9c40 47084425944128
r11 0x2ad2b321e9b0 47084436842928
r12 0x2 2
r13 0x426758b0 1114069168
r14 0x42675918 1114069272
r15 0x2aaab1c6d000 46912615403520
rip 0x2ad2b30a1326 0x2ad2b30a1326
eflags 0x10206 [ PF IF RF ]
cs 0x33 51
ss 0x2b 43
ds 0x0 0
es 0x0 0
fs 0x63 99
gs 0x0 0
fctrl 0x27f 639
fstat 0x20 32
ftag 0xffff 65535
fiseg 0x2ad2 10962
fioff 0xb249282f -1303828433
foseg 0x0 0
fooff 0x42676cf8 1114074360
fop 0x55d 1373
mxcsr 0x1fa0 [ PE IM DM ZM OM UM PM ]

Similar Messages

Required appropriate OCI JDBC driver for Oracle 9i

Required appropriate OCI JDBC driver for Oracle 9i Enterprise Edition Release 9.2.0.6.0.

Stick to one thread please.
http://forum.java.sun.com/thread.jspa?messageID=9552360

SetString/executeBatch fails in Oracle 10g OCI JDBC driver

Hi,
I am using Oracle 10g OCI jdbc driver for batch updates.
Following is the the code that I am using
import java.sql.*;
import oracle.jdbc.*;
import oracle.jdbc.pool.OracleDataSource;
public class BatchUpdates
public static void main(String[] args)
Connection conn = null;
Statement stmt = null;
PreparedStatement pstmt = null;
ResultSet rset = null;
int i = 0;
try
String url = "jdbc:oracle:oci:@kctutf8";
try {
String url1 = System.getProperty("JDBC_URL");
if (url1 != null)
url = url1;
} catch (Exception e) {
OracleDataSource ods = new OracleDataSource();
ods.setUser("kctuser");
ods.setPassword("kana");
ods.setURL(url);
conn = ods.getConnection ();
stmt = conn.createStatement();
try { stmt.execute(
"create table mytest_table (col1 number, col2 varchar2(20))");
} catch (Exception e1) {}
pstmt = conn.prepareStatement("insert into mytest_table values (?, ?)");
pstmt.setInt(1, 1);
pstmt.setString(2, "row 1");
pstmt.addBatch();
pstmt.setInt(1, 2);
pstmt.setString(2, "row 2");
pstmt.addBatch();
pstmt.setInt(1, 3);
pstmt.setString(2, "row 3");
pstmt.addBatch();
pstmt.setInt(1, 4);
pstmt.setString(2, "row 4");
pstmt.addBatch();
pstmt.setInt(1, 5);
pstmt.setString(2, "row 5");
pstmt.addBatch();
pstmt.executeBatch();
rset = stmt.executeQuery("select * from mytest_table");
while (rset.next())
System.out.println(rset.getInt(1) + ", " + rset.getString(2));
catch (Exception e)
e.printStackTrace();
finally
if (stmt != null)
try { stmt.execute("drop table mytest_table"); } catch (Exception e) {}
try { stmt.close(); } catch (Exception e) {}
if (pstmt != null)
try { pstmt.close(); } catch (Exception e) {}
if (conn != null)
try { conn.close(); } catch (Exception e) {}
When I run this class I get the following output
1, row 1
2, row 3
3, row 5
4, null
5,
But It should have been
1, row 1
2, row 2
3, row 3
4, row 4
5, row 5
The same class runs fine if I use Thin driver.
Can anyone please help me solve this issue.
Note: This happens only in case we use setString with Varchar2 in the DB. This works fine if I have two number columns
Thanks,
Raja.S

Please post this question to the Java forum. It is located under "Technologies".

Can't connect using OCI JDBC driver in OC4J 10.1.3.3 standalone

Hi all,
I've recently upgraded my JDev from 10.1.3.2 to 10.1.3.3 and now I'm unable to establish any OCI connections with my local Oracle 10.1.0.4 database. Not even through a connection pool. The strangest thing is that when I test an OCI connection running from JDeveloper it works fine and the JDBC jars and the oci client are exactly the same.
The error is always the same when I execute a test on a connection pool using the OCI driver:
WARNING J2EE DS-00001 Exception occurred testing connection. Exception: java.sql.SQLException: Closed Connection.
If I just change the driver to the THIN one, the same test works. If I take the same URL from the OCI test and use it in a test class and run it inside JDeveloper, it works also.
I've even downloaded the instant client 10.1.0.5 (which happens to be exactly the same version of the JDBC driver that comes with JDev 10.1.3.3) and tried to use it with no success.
THIN connections are working just fine. The problem happens only when I try to connect via OCI and this problem was not happening in version 10.1.3.2.
Any help?

I found the cause of this problem. It turns out that you must be very careful with the environment variable ORACLE_HOME. On Windows, normally, we don't even set this variable because most applications are able to get it from the system's registry.
Well, it happened that I've edited the script start_oc4j.bat and, for organization reasons, I set the ORACLE_HOME variable with my JDeveloper's home directory (which is the same as my OC4J standalone's). By doing that, I kind of confused the OCI client. Once I removed the "set ORACLE_HOME=C:\JDev" line from the script, everything worked just fine again.
So, always remember: avoid setting environment variable ORACLE_HOME when using Windows and, if you must set it, be sure to do it right.
Regards,
Eduardo.

What are the benefits to using the OCI JDBC driver?

I understand that the Thin JDBC driver is geared toward Applets since it is all Java and relatively small for download. If I am running servlets is there any compelling reason for me to use the OCI driver? I would think my application would be more portable if I stuck with the Thin driver even on the server side. This would allow me to easily move my servlet application to UNIX from NT, Java Web Server to IIS, IIS to Apache... So, does anyone know what one would gain by maintaining the Oracle Client software on the server and using the OCI driver?
Thanks in advance.

It's not a separate account. It's simply an additional address on your existing account and you can use it or not use it at your own convenience. Your @me.com address will be unaffected.

Cant get OCI jdbc driver working on Mac OS X

I have installed the 10g final release for Mac OS X 10.3.7.
I did a custom install...ONLY the JDBC drivers...nothing else.
I have gotten the THIN driver to work fine and connect to the database. But when I try to use the OCI driver, I keep getting unsatisifed link errors. I have set my LD_LIBRARY_PATH and such but no luck. Anyone got any ideas for what I need to do?
Environment vars:
echo $LD_LIBRARY_PATH
/Users/michaelm/other/oracle/product/10.1.0/client_1/lib
This shows that the file in question DOES exist:
ls -l /Users/michaelm/other/oracle/product/10.1.0/client_1/lib/libocijdbc10.jnilib
-rw-r--r-- 1 michaelm michaelm 93028 29 Dec 21:22 /Users/michaelm/other/oracle/product/10.1.0/client_1/lib/libocijdbc10.jnilib
When I run the program, I get this:
Exception in thread "main" java.lang.UnsatisfiedLinkError: /Users/michaelm/other/oracle/product/10.1.0/client_1/lib/libocijdbc10.jnilib:
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1586)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1511)
at java.lang.Runtime.loadLibrary0(Runtime.java:788)
at java.lang.System.loadLibrary(System.java:834)
at oracle.jdbc.driver.T2CConnection.loadNativeLibrary(T2CConnection.java:2927)
at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:225)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:347)
at oracle.jdbc.driver.T2CConnection.<init>(T2CConnection.java:139)
at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:79)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:549)
at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:196)
at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:146)
at Test.getConnection(Test.java:32)
at Test.main(Test.java:12)
What else do I need to do?

Same error. I just don't get it. Here are some of the environment vars:
echo $ORACLE_HOME
/Users/michaelm/other/oracle/product/10.1.0/client_1
echo $LD_LIBRARY_PATH
/Users/michaelm/other/oracle/product/10.1.0/client_1/lib
echo $DYLD_LIBRARY_PATH
/Users/michaelm/other/oracle/product/10.1.0/client_1/lib
What in the world am I doing wrong? Seems like with such a basic installation (just the JDBC drivers) this thing would work!
thanks,
Mike

Is ojdbc5.jar type of thin or oci jdbc driver?

Hi!
I have downloaded ojdbc5.jar(file of jdbc driver classes for oracle 11g) from OTN,but I don't know what kind of jdbc driver class it contains,THIN or OCI?
Thanks!
Huang

I went to the OTN download site. The download area of the page was titled "JDBC Thin for All Platforms". Of course, that doesn't mean much.
So I looked at [url-http://download.oracle.com/otn/utilities_drivers/jdbc/111060/Readme.txt]this ReadMe information, found one line above the at the same place as the download. That might be helpful, would it not?
And, of course, thgere is some added information in the FAQ at
http://www.oracle.com/technology/tech/java/sqlj_jdbc/htdocs/jdbc_faq.html
<g>

Trying to use OCI Jdbc driver

I'm using OC4J v2, with JDK1.3.1 under Linux
what libs / configs are required to use OCI Jdbc Drivers ?
thanks
N.

Debu, I spent much time searching this forum for answers to the ocijdbcX.dll problems in OC4J. I finally found my answer on Metalink. Apparently this is Bug# 1918517. The recommended fix on metalink for this bug solved my problem and is probably the problem that everyone else is experiencing. Setting LD_LIBRARY_PATH and ORACLE_HOME had no affect on OC4J.
Jeff Kirby
Lockheed Martin Mission Systems

Where can i download oracle oci jdbc driver 1.2?

http://otn.oracle.com/software/tech/java/sqlj_jdbc/content.html
some error in this page. several days.

Please be more specific about the file(s) you are having trouble with.
Regards,
OTN

JDBC OCI to JDBC Thin Migration

Hi
A customer currently uses the OCI JDBC driver to connect to the database and we are currently investigating a move to the JDBC Thin driver.
One particular problem seems to be that a feature is used to find out whether a password is about to expire, and it is said this is not supported by the Thin Driver:
Connection conn;
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
try {
Properties props = new Properties();
props.put("user",us);
props.put("password",pw);
conn = DriverManager.getConnection(cs,props);
SQLWarning sqlw = conn.getWarnings();
if ( sqlw != null && sqlw.getErrorCode() == 28002 )
Properties props = new Properties();
props.put("user",us);
props.put("password",pw);
props.put("OCINewPassword",pw1);
Connection newconn = DriverManager.getConnection(cs,props);
conn = newconn;
pw = pw1;
catch (java.sql.SQLException e) {
Is something like this possible using the Thin Driver?
Bye
Tim

Not in the thin driver. The OCI driver is making use of a specialized OCI API for that. I imagine you could do it in SQL:
SQL> desc user_users
Name Null? Type
USERNAME NOT NULL VARCHAR2(30)
USER_ID NOT NULL NUMBER
ACCOUNT_STATUS NOT NULL VARCHAR2(32)
LOCK_DATE DATE
EXPIRY_DATE DATE
DEFAULT_TABLESPACE NOT NULL VARCHAR2(30)
TEMPORARY_TABLESPACE NOT NULL VARCHAR2(30)
CREATED NOT NULL DATE
INITIAL_RSRC_CONSUMER_GROUP VARCHAR2(30)
EXTERNAL_NAME VARCHAR2(4000)
It seems as though the EXPIRY_DATE column may have what you are after.

Configure Oracle OCI JDBC drivers

What is the correct configuration of the connection pools in order to use
Oracle's OCI JDBC driver:
DB=8.1.7.3
thanks,
catharine

There is a small machine specific library that's part of the JDBC OCI drivers. But it does you no good unless you have the OCI libraries themselves. And you must have exactly the same versions of the JDBC Java code, and that small machine specific library as you do OCI libraries for the driver to work. Those OCI C libraries are licensed products. If you want to use the JDBC OCI driver you should get the small machine specific library and Java code from the same source as the OCI libraries themselves. The JDBC OCI drivers are on the install CDs.
I must admit, it's not clear to me what the benefit of having the OCI driver available for download is. If you can use it, then you have access to an Oracle install CD or a downloaded installer which will contain the JDBC OCI driver. I guess that if you already have an OCI install, it's easier to download the driver than it is to find the install CD.
I'm not an expert on what is packaged where or how it's all licensed so I could be confused about some of this. I've asked Product Management to give me a clue. I could use one. I'll post another reply when I hear back.

Error while creating a report that uses Oracle OCI JDBC connectivity

Please let me know why my CR and LF characters are removed from my forum posting *****
Hi,
I was trying to create a report that uses Oracle OCI JDBC connectivity. I am using Eclipse3.4 download from "cr4e-all-in-one-win_2.0.2.zip". I have successfully created a JDBC OCI connection.
The connection parameters are given below:
URL: jdbc:oracle:oci8:@xe
Database: xe
username: <userName>
password: <password>
I have tested the above connection in Data source Explorer and it works fine!!!
But I am getting the following error when I drag-and-drop a table from the list of tables. Not sure what I am missing here? Any help is highly appreciated.
com.businessobjects.reports.jdbinterface.common.DBException: InvalidURLOrClassName
     at com.crystaldecisions.reports.queryengine.driverImpl.jdbc.JDBCConnection.Open(Unknown Source)
     at com.crystaldecisions.reports.queryengine.JDBConnectionWrapper.Open(SourceFile:123)
     at com.crystaldecisions.reports.queryengine.Connection.br(SourceFile:1771)
     at com.crystaldecisions.reports.queryengine.Connection.bs(SourceFile:491)
     at com.crystaldecisions.reports.queryengine.Connection.t1(SourceFile:2979)
     at com.crystaldecisions.reports.queryengine.Table.u7(SourceFile:2408)
     at com.crystaldecisions.reports.dataengine.datafoundation.AddDatabaseTableCommand.new(SourceFile:529)
     at com.crystaldecisions.reports.common.CommandManager.a(SourceFile:71)
     at com.crystaldecisions.reports.common.Document.a(SourceFile:203)
     at com.businessobjects.reports.sdk.requesthandler.f.a(SourceFile:175)
     at com.businessobjects.reports.sdk.requesthandler.DatabaseRequestHandler.byte(SourceFile:1079)
     at com.businessobjects.reports.sdk.JRCCommunicationAdapter.do(SourceFile:1163)
     at com.businessobjects.reports.sdk.JRCCommunicationAdapter.if(SourceFile:657)
     at com.businessobjects.reports.sdk.JRCCommunicationAdapter.a(SourceFile:163)
     at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.a(SourceFile:525)
     at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.call(SourceFile:523)
     at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
     at java.util.concurrent.FutureTask.run(Unknown Source)
     at com.businessobjects.crystalreports.designer.core.util.thread.ExecutorWithIdleProcessing$3.doWork(ExecutorWithIdleProcessing.java:182)
     at com.businessobjects.crystalreports.designer.core.util.thread.AbstractCancellableRunnable.run(AbstractCancellableRunnable.java:69)
     at com.businessobjects.crystalreports.designer.core.util.thread.PriorityTask.run(PriorityTask.java:75)
     at com.businessobjects.crystalreports.designer.core.util.thread.PriorityCompoundCancellableRunnable.runSubtask(PriorityCompoundCancellableRunnable.java:187)
     at com.businessobjects.crystalreports.designer.core.util.thread.PriorityProgressAwareRunnable.runSubtask(PriorityProgressAwareRunnable.java:90)
     at com.businessobjects.crystalreports.designer.core.util.thread.PriorityCompoundCancellableRunnable.doWork(PriorityCompoundCancellableRunnable.java:144)
     at com.businessobjects.crystalreports.designer.core.util.thread.AbstractCancellableRunnable.run(AbstractCancellableRunnable.java:69)
     at com.businessobjects.crystalreports.designer.core.util.thread.ExecutorWithIdleProcessing$IdleTask.run(ExecutorWithIdleProcessing.java:320)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
Thanks
Karthik
Edited by: KARTHIK1 on Oct 14, 2009 9:38 PM

Hi Ted,
Thanks for the feedback. I was able to create a report in Creystal Reports Designer 2008 using OCI. It is not allowing only in the Eclipse plugin. In our environment we are not allowed to user Oracle thin connections and ONLY OCI is allowed.
1) Can you please let me know if there is a way to do this?
2) Will it allow data sources using native database driver?
3) If so, can I use JRC to create these reports from a desktop java program?
Thanks & Regards
Karthik
Edited by: KARTHIK1 on Oct 15, 2009 4:38 PM

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

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

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

What XA JDBC driver should I use with Oracle 8i 8.1.6

I need to use an XA JDBC driver for Oracle 8i 8.1.6. I am using the driver in
a ConnectionPool in a TxDataSource for use by some entity beans using EJB 2.0.
I'm running WebLogic Server 6.0 sp2, EJB 2.0, Java 2 SDK 1.3.1 Server VM, Solaris
2.7, and Oracle 8i 8.1.6.
I know of three different Oracle XA drivers: WebLogic jDriver for Oracle XA, Oracle
OCI type 2 driver XA, and Oracle Thin tyoe 2 XA. Are there any other drivers
that I can use for Oracle 8.1.6? Which driver and which version should I use?
For example, can I use the Oracle 8.1.7 JDBC drivers with the Oracle 8.1.6 server,
or would the Oracle 9i drivers work with the Oracle 8i server? Which drivers
are faster, and which support more features? I assume that I should not use the
type 4 driver since I am not using an applet, but I don't know if there are bugs
in the OCI C library for Solaris or in the JDBC drivers that use it that prevent
XA from woking. Which version of the Oracle C OCI library should I use if I use
a type 2 driver?
Thanks,
Ross Goldberg

Hi,
I think you can't use the 8.1.6 thin driver for XA, you would have to
use the OCI driver or 2PC-enable your datasource. AFAIK this has been
changed for 8.1.7
Check http://e-docs.bea.com/wls/docs61/////jta/thirdpartytx.html.
Daniel
-----Original Message-----
From: Gene Chuang [mailto:[email protected]]
Posted At: Thursday, August 30, 2001 2:04 AM
Posted To: jdbc
Conversation: What XA JDBC driver should I use with Oracle 8i 8.1.6
Subject: Re: What XA JDBC driver should I use with Oracle 8i 8.1.6
I've asked this question before. This is the reply from Joe
Weinstein:
For reliability and JDBC 2.0 compliance, I recommend the
Oracle thin driver.
If not that driver, you should verify that a type-2 driver
actually does
deliver better performance, but then I would not have a
strong preference
between their type-2 and ours. Theirs may be faster, and JDBC
2.0 compliant.
Both are succeptible to OCI bugs, some of which only they can
fix, but we
listen.
Gene
"Ross Goldberg" <[email protected]> wrote in message
news:[email protected]...
>
I need to use an XA JDBC driver for Oracle 8i 8.1.6. I am using thedriver in
a ConnectionPool in a TxDataSource for use by some entity beans usingEJB 2.0.
I'm running WebLogic Server 6.0 sp2, EJB 2.0, Java 2 SDK 1.3.1 ServerVM, Solaris
2.7, and Oracle 8i 8.1.6.
I know of three different Oracle XA drivers: WebLogic jDriver forOracle XA, Oracle
OCI type 2 driver XA, and Oracle Thin tyoe 2 XA. Are there any otherdrivers
that I can use for Oracle 8.1.6? Which driver and which versionshould I use?
For example, can I use the Oracle 8.1.7 JDBC drivers with the Oracle8.1.6 server,
or would the Oracle 9i drivers work with the Oracle 8i server? Whichdrivers
are faster, and which support more features? I assume that I shouldnot use the
type 4 driver since I am not using an applet, but I don't know ifthere are bugs
in the OCI C library for Solaris or in the JDBC drivers that use itthat prevent
XA from woking. Which version of the Oracle C OCI library should Iuse if I use
a type 2 driver?
Thanks,
Ross Goldberg

How do I get IWS 4.1 to recognize a MySql JDBC driver?

I have developed a web application the access a MySql database from a JSP using tomcat 3.3. I am now migrating the application to the production envionment, IPWS 4.1 SP7. I get a serverlet exception : no sutable driver when the JSP tries to connect using the mm.mysql-2.0.6.1 JDBC driver. I have tried other driver versions (older and newer) to no avail. How do I get IPWS to work with MySql data base?

I've recently done this with iWs 4.1 and mm.mysql 2.0.11 on a Windows 2000 box.
Download and install the mm.mysql software, I put the jar file mm.mysql-2.0.11-bin.jar into C:\mm.mysql
Then on the iWs Management Interface... Servlets, Configure JVM attributes. Go to the end of the ClassPath field and add ";C:/mm.mysql/mm.mysql-2.0.11-bin.jar" and save the change.
Then my JSP code looks like the following:
Class.forName("org.gjt.mm.mysql.Driver").newInstance();
Connection con = DriverManager.getConnection("jdbc:mysql://dbserver.mydomain.com/mydatabase?user=xxx&password=xxx");
Regards,
Jim

OCI JDBC Driver migration

Similar Messages

Maybe you are looking for