JDBC Thin Drivers

Hi,
I have downloaded Oracle thin drivers for jdk1.2.2 from oracle's site. But when i tried to hit the Database with it iam getting "Network Adapter error". I ahd given the url correctly. I checked up the application by running on the system where oracle is installed and it is running perfectly but when i access the database by installing thin drivers on some other machine and testing it, iam not able to connect to database. Iam getting Network adapter error and i also checked up with the network people and the assured me that there are no network problems as i am able to oracle server by pinging and thru telnet also. Any help will be greatly appreciated and Thanx in Advance.

Marcelo,
You can download JDBC 2.0 - friendly drivers from Openlink
Software (http://www.openlinksw.com). Our latest 3.2 versions
that support JDK 1.2 can be found at
ftp://ftp.openlinksw.com/pre-3.2/index.html
... if you scroll to the NT / 95 section at the bottom of the
page, you'll find the "opljdbc2.jar" in the list.
Best regards,
Stephen
Marcelo Malagutti (guest) wrote:
: Hello.
: I3d like to know when will be released the JDBC thin drivers
for
: Oracle 8.0.4, compatible with the JDK 1.2. I need it to use
the
: new Java BLOB features of the JDK 1.2. Thanks.
null

Similar Messages

JDBC-Thin-Drivers on different Platforms

Hello,
Is there a difference between the JDBC thin drivers for Win NT and IBM AIX when using the same driver version (8.1.7) ?
thanks in advance
Joachim Helf

the jdbc thin driver spec requires platform indepenedence.
so you should not have a problem.
if you do have a problem, then oracle support wants to hear about it.
in that case, log a tar with your local oracle support center.

JDBC thin drivers for 8.0.4 and JDK 1.2

Hello.
I3d like to know when will be released the JDBC thin drivers for
Oracle 8.0.4, compatible with the JDK 1.2. I need it to use the
new Java BLOB features of the JDK 1.2. Thanks.
null

Marcelo,
You can download JDBC 2.0 - friendly drivers from Openlink
Software (http://www.openlinksw.com). Our latest 3.2 versions
that support JDK 1.2 can be found at
ftp://ftp.openlinksw.com/pre-3.2/index.html
... if you scroll to the NT / 95 section at the bottom of the
page, you'll find the "opljdbc2.jar" in the list.
Best regards,
Stephen
Marcelo Malagutti (guest) wrote:
: Hello.
: I3d like to know when will be released the JDBC thin drivers
for
: Oracle 8.0.4, compatible with the JDK 1.2. I need it to use
the
: new Java BLOB features of the JDK 1.2. Thanks.
null

Jdbc thin drivers for windows 95

Where can I find jdbc thin drivers for windows 95 for Personal Oracle 8.0. Thanks for the help.
AP

The thin driver is for the most part OS and RDBMS independant so any of them should work. The problem is more likely to be that you do NOT have a TCP/IP listener running on Personal Oracle (it doesn't have a listener at all by default).

JDBC thin drivers for oracle 8.0.5 for linux

I want to use Java SDK 1.2.2 and need the oracle thin drivers.
I have trouble with the 816 thin drivers connecting to the 8.0.5
server.
when using statement.executeQuery(..... I get the following
Exception.
Exception error: java.sql.SQLException: ORA-03120: two-task
conversion routine:integer overflow
I think my solution is to upgrade to a 8.1.6 server or use the
java 1.1.6 driver on the JDK1.1.6
I tried downoading the 8.1.5 enterprise server but this fails to
complete.
Can someone help me to this version on CDROM or to the JDBC thin
driver for the 8.0.5 server?
null

You must include "classes12.zip" instead of "classes111.zip".
Since "classes111.zip" is required only for Java 1
and "classes12.zip" is required for Java 2 which means from J2SE 1.2 on forward.
In adition you might need to inlcude "nls_charset12.zip" as well. Try it first without and if it is not working include it as well.
The required files can you get from the OTN.
This should help
Roger

JDBC Thin Drivers and Tom Cat Compatibility Error

I tried to use thin drivers in JDK 1.4 and Oracle 9i. The Oracle 9i has got a jar file named classes12.jar.
i usually compile my .java files with the command:
javac -classpath D:\oracle\jdbc\lib\classes12.jar <nameOfFile.java>
the same is run in the console by the command
java -classpath D:\oracle\jdbc\classes12.jar; <nameOfClassFile>
I am giving the entire code that I want to compile and run below.
The problem thing I am facing is ..... When even I try to start TOMCAT v5.0 I have to close the TSNListener of Oracle 9i and let the Oracle database only running. But when I request for a execution of a servlet that uses the class file, it gives an error. Telling ClassNotFound. If I add up the classes12.jar file in the classpath then tom cat does not run properly.
So may anyone help me out of the situation of how to use the thin drivers, compile and run servlets and jsp's in TomCat v5.0.
If not the solution of my above problem, then I want to know how can I use the Thin Drivers and implement a MVC architechture using TOMCAT and JDK1.5 and JRE1.5

Where did you add the classes12.jar file reference in Tomcat?
You need not add it to classpath. Just drop the jar file into the path":
<TomCatInstallDir>\common\lib
Tomcat loads all Jars inside this folder and then uses it for Runtime. It does not look at your machine's Classpath attribute

Using JDBC thin drivers against 9.2 DB ?

Is anyone doing this? How? Which JDK? Which drivers?
I would really like to uses JDBC 2.0 (classes12.zip) - but this hangs on the very first getConnect() or Driver.connect()
Mike

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

JDBC 2 thin drivers

Hi.
On Jun 08 I3ve asked you about JDBC 2 thin drivers for Oracle.
I3ve been told that by the end of the month (June, I understod)
the 8.1.6 thin driver would be released. I3m already using Oracle
8.1.5. What I want to know is:
1) When will actually be released the new drivers ?
2) Will it be necessary to upgrade the server ?
3) Is there any Tech Track I should sign to receive updated
information about thin drivers ?
Thank you for your answer.
null

Marcelo,
You can download JDBC 2.0 - friendly drivers from Openlink
Software (http://www.openlinksw.com). Our latest 3.2 versions
that support JDK 1.2 can be found at
ftp://ftp.openlinksw.com/pre-3.2/index.html
... if you scroll to the NT / 95 section at the bottom of the
page, you'll find the "opljdbc2.jar" in the list.
Best regards,
Stephen
Marcelo Malagutti (guest) wrote:
: Hello.
: I3d like to know when will be released the JDBC thin drivers
for
: Oracle 8.0.4, compatible with the JDK 1.2. I need it to use
the
: new Java BLOB features of the JDK 1.2. Thanks.
null

I think Oracle JDBC Thin driver has many problems

I developed application & applet using Oracle JDBC/Thin Drivers
for use with JDK 1.2 and SUN JDK 1.2.2.
In my computer, application runs correctly.
On the other hand, applet isn't run and throws error "Cannot
find class java/util/Map" on connecting to Oracle database.
You know, java/util/Map class is only in SUN JDK 1.2.x and
current web-browsers (for example, IE5.0, Netscape 4.7, ...)
don't support Java Run time 1.2.x.
I think this is very critial problem.
So I tried with Oracle JDBC/Thin Drivers for use with JDK 1.1.x
and SUN JDK 1.1.8. (Now SUN only supports JDK 1.1.8 in JDK 1.1.x
series)
But this time, applet throws error "Cannot find class javax/..."
You know, JDK 1.1.8 doesn't have javax/... classes but early JDK
1.1.x series had javax/.... classes.
May be Oracle JDBC/Thin Drivers for use with JDK 1.1.x are made
using these early JDK 1.1.x series, so I think Oracle JDBC/Thin
Drivers for use with JDK 1.1.x can't be used with SUN JDK 1.1.8.
Whatever is the matter!
null

You need to remote onto the server and go into start->control panel-Administration-> ODBC (or sometimes start->administration->ODBC) and set up ODBC connections . Make sure you set them up on the system tab, then you should see them in EAS. I don't remember, b ut don't think you need to restart the Essbase servise for them to take effect

JDBC Thin driver connection

Hi,
I am trying to open a connection from Java using JDK 1.1.6 and the Oracle JDBC Thin drivers. My Oracle drivers register just fine. However, I get an exception which I catch saying "Security.couldn't connect to HOST with origin from." HOST is my local server name where I'm running Oracle 8.0.4.0.0 and OAS 4.0.8. My connection statement in my .java code is:
Connecttion conn =
DriverManager.getConnection("jdbc:oracle:thin@HOST:1521:orcl,"scott","tiger")
I can connect just fine using sqlplus with the scott/tiger@orcl descriptor.
How can I resolve this?

<BLOCKQUOTE>quote:<HR>Originally posted by JDBC Development Team:
Not sure whether this is the cause of the problem. There should be a ":" before the "@" sign in the connect string. That is,
"jdbc:oracle:thin:@host"
Please do let us know if this doesn't fix the problem
<HR></BLOCKQUOTE>
Thank you for pointing out the missing : before the @ symbol. I made that change. Still, I get the same message when the applet loads in my browser page. If I load the applet in appletviewer then I get the error message "checkconnect.networkhost1".

JDBC thin 8.0.4 connect to Server 8.0.5?

Oracle:
I have a test application (not an applet) that executes correctly
connecting to an Oracle Server 7.X database using Oracle's JDBC
thin drivers. But when I try to connect to an Oracle Server
8.0.5 database, I receive an Oracle error:
ORA-01034: ORACLE not available
The environment for successful application execution is:
Oracle Server 7.X with a TCP Listener on Port 1521
Client workstation NT 4.0
SQL*Net Client is installed (N/A since we're using jdbc thin?)
Java 1.1.1
Oracle JDBC Thin Driver Release 8.0.4
Classes111.zip (7/10/98; 383,256 bytes)
The environment for the un-successful execution is:
Oracle Server 8.0.5 with a TCP Listener on Port 1521
Client workstation NT 4.0
SQL*Net8 Client is installed (N/A since we're using jdbc thin?)
Java 1.1.1
Oracle JDBC Thin Driver Release 8.0.4
Classes111.zip (7/10/98; 383,256 bytes)
Everything else is identical; the only difference is the Oracle
server (7.x vs 8.0.5). The jdbc drivers were downloaded from the
OTN web site. I've reviewed the jdbc documentation available and
reviewed other threads. Is the jdbc thin driver release 8.0.4
compatible with Oracle Server 8.0.5? Is there a more recent
release of Oracle's jdbc thin driver not published on the OTN web
site? Is there something else I should be looking at?
After successful test as an application, I will be testing this
as an applet. As an applet connecting to Server 7.x, it also
works correctly. I have not yet tried the applet connecting to
Server 8.0.5.
Thank you in advance,
Ed Vinarski
5/19/99
null

<BLOCKQUOTE>quote:<HR>Originally posted by Edward Vinarski ([email protected]):
Oracle:
I have a test application (not an applet) that executes correctly
connecting to an Oracle Server 7.X database using Oracle's JDBC
thin drivers. But when I try to connect to an Oracle Server
8.0.5 database, I receive an Oracle error:
ORA-01034: ORACLE not available
The environment for successful application execution is:
Oracle Server 7.X with a TCP Listener on Port 1521
Client workstation NT 4.0
SQL*Net Client is installed (N/A since we're using jdbc thin?)
Java 1.1.1
Oracle JDBC Thin Driver Release 8.0.4
Classes111.zip (7/10/98; 383,256 bytes)
The environment for the un-successful execution is:
Oracle Server 8.0.5 with a TCP Listener on Port 1521
Client workstation NT 4.0
SQL*Net8 Client is installed (N/A since we're using jdbc thin?)
Java 1.1.1
Oracle JDBC Thin Driver Release 8.0.4
Classes111.zip (7/10/98; 383,256 bytes)
Everything else is identical; the only difference is the Oracle
server (7.x vs 8.0.5). The jdbc drivers were downloaded from the
OTN web site. I've reviewed the jdbc documentation available and
reviewed other threads. Is the jdbc thin driver release 8.0.4
compatible with Oracle Server 8.0.5? Is there a more recent
release of Oracle's jdbc thin driver not published on the OTN web
site? Is there something else I should be looking at?
After successful test as an application, I will be testing this
as an applet. As an applet connecting to Server 7.x, it also
works correctly. I have not yet tried the applet connecting to
Server 8.0.5.
Thank you in advance,
Ed Vinarski
5/19/99<HR></BLOCKQUOTE>
Net8 introduces the notion of service name and dbname. I think the version of thin JDBC you are using expect a sid name. Do a lsnrctl serv and find out your sid name and pass it to the connect string for JDBC.
null

ORACLE JDBC Thin 8.0.x - NOT Y2K compliant?

it seems that the oracle 8.0.x jdbc thin drivers are NOT Y2K
compliant...
i am using an 8.0.4/8.0.5 jdbc thin driver and jdk1.1.8
i use ResultSet for issuing SELECT statements:
ResultSet r = stmt.executeQuery("select date_field from....");
i set the date_field to year 2003
when i issue this in my java program:
java.sql.Date d = r.getDate("date_field");
the Date object returned in d has a year value of 1903!!!!!!!
of course there is a workaround...but ORACLE claims that their
jdbc drivers are Y2K compliant yet it fails
here.........frustrating...
null

dexter (guest) wrote:
: it seems that the oracle 8.0.x jdbc thin drivers are NOT Y2K
: compliant...
: i am using an 8.0.4/8.0.5 jdbc thin driver and jdk1.1.8
: i use ResultSet for issuing SELECT statements:
: ResultSet r = stmt.executeQuery("select date_field from....");
: i set the date_field to year 2003
: when i issue this in my java program:
: java.sql.Date d = r.getDate("date_field");
: the Date object returned in d has a year value of 1903!!!!!!!
: of course there is a workaround...but ORACLE claims that their
: jdbc drivers are Y2K compliant yet it fails
: here.........frustrating...
please disregard the previous message.
i think i was on drugs when i did the test...the field returns
1903 because the year value of the field is 1903...i changed the
date to 2003 and it all works fine now...
null

NCHAR, NVARCHAR2 with JDBC THICK drivers

Hi,
I am using weblogic Thick jdbc drivers. We have a requirement of storing data
in multiple languages. So we have added two columns in the oracle 9i table with
data type NCHAR and NVARCHAR2.
I tried the code using Oracle jdbc thin drivers. Its working fine.
But when I tried with weblogic thick drivers its not able to read the data...
Its reading null values.
Any suggestions/links/guidelines would of great help.
Thanks & Regards,
Purvesh Vora

Purvesh Vora wrote:
Hi,
I am using weblogic Thick jdbc drivers. We have a requirement of storing data
in multiple languages. So we have added two columns in the oracle 9i table with
data type NCHAR and NVARCHAR2.
I tried the code using Oracle jdbc thin drivers. Its working fine.
But when I tried with weblogic thick drivers its not able to read the data...
Its reading null values.
Any suggestions/links/guidelines would of great help.
Thanks & Regards,
Purvesh VoraHi. Our type-2 driver (weblogic.jdbc.oci.Driver) uses Oracle's OCI, which
may need some OCI-specific charset properties and/or environment variables
set for what you need. Please check our docs. I wouldn't expect nulls though,
maybe corrupted data, but not nulls... What happens if you try Oracle's own
thick driver? (all you would need to do is to change their URL).
Joe

Problems writing from BLOB to File with Thin-drivers

I'm having problems when I'm trying to put a blob to a file
using jdbc-thin drivers(8.1.5).
It works perfectly well with the oci-drivers but not with thin.
When I execute the same code with the thin-drivers I get:
Error: java.io.IOException: ORA-21560: argument 2 is null,
invalid, or out of range
ORA-06512: at "SYS.DBMS_LOB", line 640
ORA-06512: at line 1
Please help me...
/Stefan Fgersten
lob_loc = ((OracleResultSet)rset).getBLOB(1);
in = lob_loc.getBinaryStream();
FileOutputStream file =
new FileOutputStream("d:/dir/picture.jpg");
int c;
while ((c = in.read()) != -1)
file.write(c);
file.close();
in.close();
null

Has anyone managed to find a solution (other than switching drivers) for this? I too am using the 8.1.5 thin driver on an 8.1.5 database and receive the same error. Please help!!
Nkem
<BLOCKQUOTE>quote:<HR>Originally posted by Stefan Fgersten ([email protected]):
I'm having problems when I'm trying to put a blob to a file
using jdbc-thin drivers(8.1.5).
It works perfectly well with the oci-drivers but not with thin.
When I execute the same code with the thin-drivers I get:
Error: java.io.IOException: ORA-21560: argument 2 is null,
invalid, or out of range
ORA-06512: at "SYS.DBMS_LOB", line 640
ORA-06512: at line 1
Please help me...
/Stefan Fgersten
lob_loc = ((OracleResultSet)rset).getBLOB(1);
in = lob_loc.getBinaryStream();
FileOutputStream file =
new FileOutputStream("d:/dir/picture.jpg");
int c;
while ((c = in.read()) != -1)
file.write(c);
file.close();
in.close();<HR></BLOCKQUOTE>
null

Differences between Oracle JDBC Thin and Thick Drivers

If any body is looking for this information...
============================================================
I have a question concerning the Oracle JDBC thin vs. thick drivers
and how they might affect operations from an application perspective.
We're in a Solais 8/Oracle 8.1.7.2 environment. We have several
applications on several servers connecting to the Oracle database.
For redundancy, we're looking into setting up TAF (transparent
application failover). Currently, some of our apps use the Oracle
JDBC thin drivers to talk to the database, with a connection
string that like this:
 jdbc:oracle:thin:@host:port:ORACLE_SID 
In a disaster recovery mode, where we would switch the database
from one server to another, the host name in the above string
would become invalid. That means we have to shut down our application
servers and restart them with an updated string.
Using the Oracle OCI (thick) driver though, allows us to connect
to a Net8 service instead of a specific server:
 jdbc:oracle:oci8:@NET8_SERVICE_NAME 
Coupled with the FAILOVER=ON option configured in Net8, it is
then possible to direct a connection from the first server to
the failover database on another server. This is exactly what
we would like to do.
My question is, from an application perspective, how is the Oracle
thick driver different from the thin driver? If everything
else is "equal" (i.e. the thick driver is compatible with the
app servers) would there be something within the the thick/OCI
driver that could limit functionality vs. the thin driver?
My understand, which obviously is sketchy, is that the thick
driver is a superset of the thin driver. If this is the case,
and for example if all database connections were handled through
a configuration file with the above OCI connection string, then
theoretically the thick driver should work.
============================================================

In the case with the Oracle, they provide a thin driver that is a 100% Java driver for client-side use without the need of an Oracle installation (maybe that's why we need to input server name and port number of the database server). This is platform indipendent, and has good performance and some features.
The OCI driver on the other hand is not java, require Oracle installation, platform dependent, performance is faster, and has a complete list of all the features.

========================================================
I hope this is what you expect.
JDBC OCI client-side driver: This is a JDBC Type 2 driver that uses Java native methods to call entrypoints in an underlying C library. That C library, called OCI (Oracle Call Interface), interacts with an Oracle database. The JDBC OCI driver requires an Oracle (7.3.4 or above) client installation (including SQL*Net v2.3 or above) and all other dependent files. The use of native methods makes the JDBC OCI driver platform specific. Oracle supports Solaris, Windows, and many other platforms. This means that the Oracle JDBC OCI driver is not appropriate for Java applets, because it depends on a C library to be preinstalled.
JDBC Thin client-side driver: This is a JDBC Type 4 driver that uses Java to connect directly to Oracle. It emulates Oracle's SQL*Net Net8 and TTC adapters using its own TCP/IP based Java socket implementation. The JDBC Thin driver does not require Oracle client software to be installed, but does require the server to be configured with a TCP/IP listener. Because it is written entirely in Java, this driver is platform-independent. The JDBC Thin driver can be downloaded into any browser as part of a Java application. (Note that if running in a client browser, that browser must allow the applet to open a Java socket connection back to the server.
JDBC Thin server-side driver: This is another JDBC Type 4 driver that uses Java to connect directly to Oracle. This driver is used internally by the JServer within the Oracle server. This driver offers the same functionality as the client-side JDBC Thin driver (above), but runs inside an Oracle database and is used to access remote databases. Because it is written entirely in Java, this driver is platform-independent. There is no difference in your code between using the Thin driver from a client application or from inside a server.
======================================================
How does one connect with the JDBC Thin Driver?
The the JDBC thin driver provides the only way to access Oracle from the Web (applets). It is smaller and faster than the OCI drivers, and doesn't require a pre-installed version of the JDBC drivers.
import java.sql.*;
class dbAccess {
public static void main (String args []) throws SQLException
DriverManager.registerDriver (new oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection
("jdbc:oracle:thin:@qit-uq-cbiw:1526:orcl", "scott", "tiger");
// @machineName:port:SID, userid, password
Statement stmt = conn.createStatement();
ResultSet rset = stmt.executeQuery("select BANNER from SYS.V_$VERSION");
while (rset.next())
System.out.println (rset.getString(1)); // Print col 1
stmt.close();
How does one connect with the JDBC OCI Driver?
One must have Net8 (SQL*Net) installed and working before attempting to use one of the OCI drivers.
import java.sql.*;
class dbAccess {
public static void main (String args []) throws SQLException
try {
Class.forName ("oracle.jdbc.driver.OracleDriver");
} catch (ClassNotFoundException e) {
e.printStackTrace();
Connection conn = DriverManager.getConnection
("jdbc:oracle:oci8:@qit-uq-cbiw_orcl", "scott", "tiger");
// or oci7 @TNSNames_Entry, userid, password
Statement stmt = conn.createStatement();
ResultSet rset = stmt.executeQuery("select BANNER from SYS.V_$VERSION");
while (rset.next())
System.out.println (rset.getString(1)); // Print col 1
stmt.close();
=================================================================

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

JDBC Thin Drivers

Similar Messages

Maybe you are looking for