Hi,
there is something called the README file that comes
with your Oracle, please make the effort to read it:
Oracle JDBC Drivers release 8.1.6 README
========================================
What Is New In This Release?
----------------------------
The major new features added since the initial
distribution of 8i
(8.1.5) are listed in the following:
- Support for JDBC 2.0 Core API including:
* Scrollable result set.
* Batch updates.
* Large objects and structured types. (Support
for these data
types are also available in 8.1.5).
- Support for JDBC 2.0 Optional Package (used to be
called JDBC 2.0
Standard Extension API) including:
* Connection pooling.
* Distributed transaction.
- Oracle JDBC connection caching.
- Other new improvements:
* Vendor code for errors.
* Improved performance on JDBC Server-side
Internal Driver.
- Basic zip files for debugging.
- Support for JDK 1.2.x. (In 8.1.6 SDK, only the
JDBC Thin Driver
supports JDK 1.2.x. If you have JDBC programs
that were written
for previous releases of Oracle's drivers and you
would like to
run them with JDK 1.2.x, you may have to port your
programs.
Please see the "Support For JDK 1.2.x" section
below for details.)
- Support for NLS in the Server-side Internal
Driver. (Note ##)
- Support for the Server-side Thin Driver for
middle-tier
applications. (Note ##)
- Discontinued support for JDK 1.0.2. (Note ##)
## Note: Also available in 8.1.6 SDK.
Driver Versions
---------------
These are the driver versions in the 8.1.6 release:
- JDBC OCI Driver 8.1.6
Client-side JDBC for use on a machine where OCI
8.1.6 is installed.
- JDBC Thin Driver 8.1.6
100% Java client-side JDBC for use in applets and
applications.
- JDBC Thin Server-side Driver 8.1.6
JDBC for use by Java Stored Procedures or by Java
CORBA objects
running in Oracle 8.1.6. This driver is typically
used in a middle
tier server.
- JDBC Server-side Internal Driver 8.1.6
Server-side JDBC for use by Java Stored procedures
or by Java CORBA
objects running in Oracle 8.1.6. This driver used
to be called the
"JDBC Kprb Driver".
For complete documentation, please refer to "JDBC
Developer's Guide
and Reference".
Contents Of This Release
------------------------
The [ORACLE_HOME]/jdbc/lib directory contains:
- classes111.zip
Classes for use with JDK 1.1.x. It contains the
JDBC driver
classes except classes necessary for NLS support
in Object and
Collection types.
- nls_charset11.zip
NLS classes for use with JDK 1.1.x. It contains
classes necessary
for NLS support in Object and Collection types.
- classes111_g.zip
Same as classes111.zip, except that classes were
compiled with
"javac -g".
- classes12.zip
Classes for use with JDK 1.2.x. It contains the
JDBC driver
classes except classes necessary for NLS support
in Object and
Collection types.
- nls_charset12.zip
NLS classes for use with JDK 1.2.x. It contains
classes necessary
for NLS support in Object and Collection types.
- classes12_g.zip
Same as classes12.zip, except that classes were
compiled with
"javac -g".
Note that the packaging of the JDBC classes to
support NLS was
changed in 8i. The classes pertaining to specific
character sets
support in Object and Collection types have been
separated from the
basic zip files. These NLS classes are now packaged
into the
extension zip files. This allows the user to
include the NLS
classes only if necessary. Please refer to the "NLS
Extension Zip
Files (for client-side only)" for further details.
[ORACLE_HOME]/lib directory contains libocijdbc8.so
and
libocijdbc8_g.so (on Solaris), which are the shared
libraries used by
the JDBC OCI driver.
[ORACLE_HOME]/jdbc/doc/javadoc.tar contains the JDBC
Javadoc. This
release contains a beta release of the Javadoc files
for the public
API of the public classes of Oracle JDBC.
[ORACLE_HOME]/jdbc/demo/demo.tar contains sample JDBC
programs.
Demo programs written for JDK 1.1 must be modified to
run in JDK 1.2.
Please refer to the "Support For JDK 1.2" for porting
details.
NLS Extension Zip Files (for client-side only)
----------------------------------------------
The JDBC Server-side Internal Driver provides complete
NLS support.
It does not require any NLS extension zip files,
nls_charset*.zip.
Discussions in this section do not apply to the JDBC
Server-side
Internal Driver. You can skip this section if you
only use the
Server-side Internal Driver.
The basic zip files, classes111.zip and classes12.zip,
contain all the
necessary classes to provide complete NLS support for:
- Oracle Character sets for
CHAR/VARCHAR/LONGVARCHAR/CLOB type data
that is not retrieved or inserted as a data member
of an Oracle 8
Object or Collection type.
- NLS support for CHAR/VARCHAR data members of
Objects and
Collections for a few commonly used character
sets. These
character sets are: US7ASCII, WE8DEC,
WE8ISO8859P1 and UTF8.
Users must include the appropriate extension zip in
their CLASSPATH
if utilization of other character sets in CHAR/VARCHAR
data members
of Objects/Collections is desired. It is important to
note that
extension zip files are large in size due to the
requirement of
supporting a large number of character sets. Users
may choose to
include only the necessary classes from the extension
zip file.
To do so, users can first unzip the extension zip
file, and then put
only the necessary classes in the CLASSPATH. The
character set
extension class files are named in the following
format:
CharacterConverter<OracleCharacterSetId>.class
where <OracleCharacterSetId> is the hexidecimal
representation of the
Oracle character set id of the corresponding character
set.
-----------------------------------------------------------------------
Support For JDBC 2.0 Core API
-----------------------------
These are the supported JDBC 2.0 Core features:
- Scrollable result set.
- Batch updates.
- Large objects (including BLOB and CLOB), and
structured types
(including Oracle 8 Objects, REFs and
Collections). Support for
these data types are also available in 8.1.5.
Support For JDBC 2.0 Optional Package (Standard
Extension API)
--------------------------------------------------------------
These are the supported JDBC 2.0 Optional Package
features:
- Connection pooling.
- Distributed transaction.
Oracle JDBC Connection Caching
------------------------------
The JDBC 2.0 specification does not madate JDBC
vendors to implement
a connection cache module. However, we have one
implemented as an
example. Oracle's connection caching facilitates the
users in
implementing their own connection cache. It leverages
the
infrastructure of the JDBC 2.0 Connection Pooling
features. Please
refer to the "JDBC Developer's Guide and Reference"
for APIs and
details.
Other New Improvements
----------------------
These are the new improvements in 8.1.6:
- Vendor codes are now reported with SQLExceptions
thrown by the
JDBC drivers.
- The performance of the JDBC Server-side Internal
Driver has been
improved.
Basic Zip Files For Debugging
-----------------------------
Debug version of library and zip files
(libocijdbc8_g.so,
classes12_g.zip and classes111_g.zip) are included for
debugging
purposes.
Support For JDK 1.2.x
---------------------
JDK 1.2 is now supported by all drivers. If you have
JDBC programs
that were developed using previous versions of Oracle
JDK 1.1.x
drivers, you may have to modify these programs before
they can be run
with the new JDK 1.2 drivers. Programs written for
JDK 1.1 will
continue to run in JDK 1.1. However, if you are using
the
Server-side Internal Driver, you must port your
programs to JDK 1.2.
It is because, unlike the client-side drivers, JDK 1.2
is the only
version supported by the Server-side Internal Driver.
The steps to port your program to JDK 1.2 are as
follows:
- Replace all imports and other mentions of
"oracle.jdbc2" with
"java.sql" in your programs.
The package oracle.jdbc2 contains those parts of
the JDK 1.2 JDBC
specification that Oracle implemented in the JDK
1.1 versions of
Oracle's drivers. Since those classes and
interfaces are
available in JDK 1.2, oracle.jdbc2 is not included
in
classes12.zip, nor in the Server-side Internal
Driver.
- The return type of the getTypeMap() method of
Connection has been
changed from "java.util.Dictionary" to
"java.util.Map". Please
modify your application accordingly. No change is
necessary if
you are using java.util.Hashtable, because
Hashtable implements
java.util.Map.
Support For NLS In The Server-side Internal Driver
--------------------------------------------------
Full NLS support is available in the Server-side
Internal Driver.
No special installation is necessary.
Support For The Server-side Thin Driver For
Middle-Tier Applications
--------------------------------------------------------------------
The Thin driver is also available in JServer, the Java
VM inside the
database. No special installation is necessary. It
is intended to be
used for middle-tier applications to connect to
back-end servers. The
Server-side Thin Driver has the same features as the
Thin Driver for
clients.
In 8.1.6 SDK, there was a limitation that the
Server-side Thin Driver
can only connect to ASCII servers. This limitation no
longer exists.
Discontinued Support for JDK 1.0.2
----------------------------------
Starting form 8.1.6 SDK, we no longer ship JDBC
drivers that support
JDK 1.0.2 with our new releases. If you are running
with JDK 1.0.2,
you can continue to use our JDBC drivers that are made
available as
part of the prior releases. These drivers will
continue to be
maintained as part of the maintenance of our prior
releases, although
there will be no new development on the JDK 1.0.2
drivers.
Solaris 2.6
-----------
Oracle JDBC drivers have been tested and certified on
Solaris 2.6.
They should also work on platforms above 2.6 because
of binary
backward compatibility. We do not support versions
below 2.6.
-----------------------------------------------------------------------
Installation
------------
Please do not try to put multiple versions of the
Oracle JDBC drivers
in your CLASSPATH. The Oracle installer installs the
JDBC Drivers in
the [ORACLE_HOME]/jdbc directory.
Setting Up Your Environment
---------------------------
On Win95/Win98/NT:
- Add [ORACLE_HOME]\jdbc\lib\classes111.zip and
[ORACLE_HOME]\jdbc\lib\nls_charset11.zip to your
CLASSPATH.
(Add classes12.zip and nls_charset12.zip if JDK
1.2.x is used.)
- Add [ORACLE_HOME]\jdbc\lib to your PATH.
On Solaris/Digital Unix:
- Add [ORACLE_HOME]/jdbc/lib/classes111.zip and
[ORACLE_HOME]/jdbc/lib/nls_charset11.zip to your
CLASSPATH.
(Add classes12.zip and nls_charset12.zip if JDK
1.2.x is used.)
- Add [ORACLE_HOME]/jdbc/lib to your
LD_LIBRARY_PATH.
On HP/UX:
- Add [ORACLE_HOME]/jdbc/lib/classes111.zip and
[ORACLE_HOME]/jdbc/lib/nls_charset11.zip to your
CLASSPATH.
(Add classes12.zip and nls_charset12.zip if JDK
1.2.x is used.)
- Add [ORACLE_HOME]/jdbc/lib to your SHLIB_PATH and
LD_LIBRARY_PATH.
On AIX:
- Add [ORACLE_HOME]/jdbc/lib/classes111.zip and
[ORACLE_HOME]/jdbc/lib/nls_charset11.zip to your
CLASSPATH.
(Add classes12.zip and nls_charset12.zip if JDK
1.2.x is used.)
- Add [ORACLE_HOME]/jdbc/lib to your LIBPATH and
LD_LIBRARY_PATH.
Some Useful Hints In Using the JDBC Drivers
-------------------------------------------
Please refer to "JDBC Developer's Guide and Reference"
for details
regarding usage of Oracle's JDBC Drivers. This
section only offers
useful hints. These hints are not meant to be
exhaustive.
These are a few simple things that you should do in
your JDBC program:
1. Import the necessary JDBC classes in your programs
that use JDBC.
For example:
import java.sql.*;
import java.math.*;
2. Register the Oracle driver before before calling
other JDBC APIs.
(This is not needed if you are using the JDBC
Server-side Internal
Driver because registration is done automatically
in the server.)
To register the Oracle driver, make sure the
following statement
is executed at least once in your Java session:
DriverManager.registerDriver(
new oracle.jdbc.driver.OracleDriver());
3. Open a connection to the database with the
getConnection call.
Different connection URLs should be used for
different JDBC
drivers. The following examples demonstrate the
different URLs.
For the JDBC OCI8 Driver:
Connection conn = DriverManager.getConnection(
"jdbc:oracle:oci8:@<database>",
"scott", "tiger");
where <database> is either an entry in
tnsnames.ora or a SQL*net
name-value pair.
For the JDBC Thin Driver, or Server-side Thin
Driver:
Connection conn = DriverManager.getConnection(
"jdbc:oracle:thin:@<database>",
"scott", "tiger");
where <database> is either a string of the form
<host>:<port>:<sid> or a SQL*net name-value
pair.
For the JDBC Server-side Internal Driver:
Connection conn = DriverManager.getConnection(
"jdbc:oracle:kprb:");
Note that the trailing ':' character is
necessary. When you use
the Server-side Internal Driver, you always
connect to the
database you are executing in. You can also do
this:
Connection conn
= new
oracle.jdbc.driver.OracleDriver().defaultConnection();
Java Stored Procedures
----------------------
Please note that examples for callins and instance
methods using Oracle
8 Object Types are provided in:
[ORACLE_HOME]/javavm/demo/demo.zip
Once unzipped, the directory containing the examples
is:
[ORACLE_HOME]/javavm/demo/examples/jsp
Known Problems/Limitations In This Release
------------------------------------------
The following is a list of known problems/limitations:
1. There is a limitation regarding the use of stream
input for LOB
types. Stream input for LOB types can only be
used for 8.1.6
JDBC OCI driver connecting to an 8.1.6 Oracle
server. The use of
stream input for LOB types in all other
configurations may result
in data corruption. PreparedStatement stream
input APIs include:
setBinaryStream(), setAsciiStream(),
setUnicodeStream(),
setCharacterStream() and setObject().
2. BUG-1018797
Extra characters may be appended to the end of a
CLOB value
mistakenly under the following conditions:
- setCharacterStream() is used to insert a CLOB
value, and
- The Oracle server uses multi-byte character set.
(See 1 for limitation of stream input for LOB
type.)
3. Defining a RAW or CHAR column to a BLOB/CLOB will
cause the server
to crash, regardless of the driver type.
4. Programs can fail to open 16 or more connections
using our
client-side drivers at any one time. This is not
a limitation
caused by the JDBC drivers. It is most likely
that the limit of
per-process file descriptors is exceeded. The
solution is to
increase the limit.
5. The Server-side Internal Driver has the following
limitation:
- Data access for LONG and LONG RAW types is
limited to 32K of
data.
- Inserts of Object Types (Oracle 8 Objects,
Collections and
References) will not work when the database
compatibility mode
is set to 8.0. This limitation does not apply
when the
compatibility mode is set to 8.1.
- Statement.cancel() is not implemented.
- In a chain of SQLExceptions, only the first one
in the chain
will have a getSQLState value.
- Batch updates with Oracle 8 Object, REF and
Collection data
types are not supported.
6. The JDBC OCI driver on an SSL connection hangs
when the Java
Virtual Machine is running in green threads mode.
A work-around
is to run the Java Virtual Machine in native
threads mode.
7. Date-time format, currency symbol and decimal
symbols are always
presented in American convention.
8. BUG-903011
The JDBC Thin driver cannot be used with usernames
that contain
Latin-1 characters, when the server uses UTF8
character set.
9. When using OracleStatement.defineColumnType(), it
is not necessary
to define the column type to be the same as the
column type
declared in the database. If the types are
different, the
retrieved values are converted to the type
specified in
defineColumnType.
Note: Most reasonable conversions work, but not
all. If you find
a conversion that you think is reasonable, but
that does not work,
please submit a TAR to Oracle Support.
10. The utility dbms_java.set_output or
dbms_java.set_stream that is
used for redirecting the System.out.println() in
JSPs to stdout
SHOULD NOT be used when JDBC tracing is turned on.
This is
because the current implementation of
dbms_java.set_output and
set_stream uses JDBC to write the output to
stdout. The result
would be an infinite loop.
11. The JDBC OCI and Thin drivers do not read CHAR
data via binary
streams correctly. In other word, using
getBinaryStream() to
retrieve CHAR data may yield incorrect results. A
work-around is
to use either getCHAR() or getAsciiStream()
instead. The other
alternative is to use getUnicodeStream() although
the method is
deprecated.
12. BUG#899078 (since 8.1.6 SDK):
The JDBC Server-side Internal driver has extra
space padding with
PL/SQL CHAR OUT (2 to 3 space depending on
character set).
Problem occurs in most of the multibyte database
character set
except UTF8.
13. There is a limitation for Triggers implemented in
Java and Object
Types. It only affects the IN argument types of
triggers
implemented using Java on the client-side. The
restriction does
not apply to JDBC programs running inside the
server. Triggers
implemented as Java methods cannot have IN
arguments of Oracle 8
Object or Collection type. This means the Java
methods used to
implement triggers cannot have arguments of the
following types:
- java.sql.Struct
- java.sql.Array
- oracle.sql.STRUCT
- oracle.sql.ARRAY
- oracle.jdbc2.Struct
- oracle.jdbc2.Array
- any class implementing oracle.jdbc2.SQLDATA or
oracle.sql.CustomDatum
14. The scrollable result set implementation has the
following
limitation:
- setFetchDirection() on ScrollableResultSet is
not supported.
- refreshRow() on ScrollableResultSet does not
support all
combinations of sensitivity and concurrency.
The following
table depicts the supported combinations.
Support Type
Concurrency
-------------------------------------------------------
no TYPE_FORWARD_ONLY
CONCUR_READ_ONLY
no TYPE_FORWARD_ONLY
CONCUR_UPDATABLE
no TYPE_SCROLL_INSENSITIVE
CONCUR_READ_ONLY
yes TYPE_SCROLL_INSENSITIVE
CONCUR_UPDATABLE
yes TYPE_SCROLL_SENSITIVE
CONCUR_READ_ONLY
yes TYPE_SCROLL_SENSITIVE
CONCUR_UPDATABLE
15. Bug 1052489:
There is a limit on the maximum size of the array
which can be bound using
preparedStatement::setBytes, and on the string
which can be bound using
preparedStatement::setString. This limit does not
depend on the datatype
in the server, but does depend on the version of
the server. Above this
limit, you should use setBinaryStream or
setCharacterStream instead.
When connecting to an Oracle7 database, the limit
for setBytes is 255 (the
maximum size of a RAW in Oracle7). When
connecting to an Oracle8 database,
the limit for setBytes is 2000 (the maximum size
of a RAW in Oracle8).
When connecting to an Oracle7 database, the limit
for setString is 2000
(the maximum size of a VARCHAR2 in Oracle7). When
connecting to an
Oracle8 database, the limit is 4000 (the maximum
size of a VARCHAR2 in
Oracle8).
The 8.1.6 JDBC drivers may not raise an error if
you exceed the limit
when using setBytes or setString, but you may
receive the error
"ORA-17070: Data size bigger than max size for
this type". Future versions
of the drivers will raise an error if the length
exceeds these limits.
16. Bug 1069768:
Insertion of ADTs with an image bigger than 4K
with JDBC Thin driver might raise
an exception. A work-around is to have these
ADT(s) at the end of the bindings list.
You can use insert by name shown in
InsertExample.java from the demo samples,
to change the order of the bindings.
17. JDBC/ASO
Thin JDBC clients can connect securely with only
40-bit DES and RC4 encryption, as
well as with MD5 integrity. The 56-bit encryption
algorithms for thin JDBC clients
will be supported in future patch or release.
--- "Aggarwal, Pawan" <[EMAIL PROTECTED]>
wrote:
<HR>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;
charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server
version 5.5.2650.12">
<TITLE>JDk1.2.2 with Oracle</TITLE>
</HEAD>
<BODY>
<BR>
<P><FONT SIZE=2 FACE="Arial">I have the Oracle
8I(version 8.1.5.0.0) drivers classes111.zip</FONT>
<BR><FONT SIZE=2 FACE="Arial">Now does this work with
JDK12.2</FONT>
<BR><FONT SIZE=2 FACE="Arial">Do I need to some other
thin jdbc driver which is compatible,,</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Cos when I run the
program I am getting errors like </FONT>
<BR><FONT SIZE=2 FACE="Arial">The network adapter
could not establish the connection...</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">If I use Net Easy config
then I can connect to db from my m/c(Win 95)</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Please advice</FONT>
<BR><FONT SIZE=2 FACE="Arial">Thanks,</FONT>
</P>
</BODY>
</HTML>
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with
body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
__________________________________________________
Do You Yahoo!?
Yahoo! Photos -- now, 100 FREE prints!
http://photos.yahoo.com
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
