WebLogic jDriver for Oracle (Deprecated)
Note: The WebLogic jDriver for Oracle is deprecated and will be removed in a future release. BEA recommends that you use the BEA WebLogic Type 4 JDBC Oracle driver. For more information, see BEA WebLogic Type 4 JDBC Drivers.
This section discusses the following topics:
Before you can use the WebLogic jDriver for Oracle, you must complete the tasks described in this section:
For details about the platforms, operating systems, JVMs, DBMS versions, and client libraries supported by the WebLogic jDrivers, see WebLogic Server Supported Configurations.
To set up your environment to support the use of WebLogic jDrivers, you must set your path variable to include pathnames for the following:
dll
, so
, or sl
file, depending on your operating system.) The file containing the driver must be available to your WebLogic Server client. The name of the path variable depends on the system you are using:PATH
.LD_LIBRARY_PATH
.SHLIB_PATH
.The directory containing the driver file varies, depending on several factors discussed in the following text.
WebLogic Server uses the dll
, so
, or sl
files built with the Oracle Call Interface (OCI) version 8 API as the native interface for accessing an Oracle DBMS.
The tables in the following platform-specific sections list the directories—based on the Oracle client version—that you must specify in your system PATH
to access the desired version of the driver.
Add the pathnames for the WebLogic shared library (.dll
) directory and the directory where you installed the Oracle client to the PATH
as follows:
WL_HOME\server\bin\
and the appropriate WebLogic Server shared library directory from the table below to your PATH
, where WL_HOME
is the directory of your WebLogic Server installation. For example: %WL_HOME%\server\bin\ocixxxx
ORACLE_HOME\bin
to your PATH,
where ORACLE_HOME
is the directory of your Oracle client installation. Always add the WebLogic jDriver for Oracle and Oracle home information at the beginning of your PATH
. For example:%
ORACLE_HOME%\bin
;%PATH%
Using the above syntax to create an actual example for Oracle 8.1.7, your path may look like:
$set PATH=
%WL_HOME%\server\bin\oci817_8;%ORACLE_HOME%\bin;%PATH%
The following table provides the directory and Oracle client versions for Windows.
Add the pathnames for the WebLogic shared library (.dll
) directory and the directory where you installed the Oracle client to the PATH
as follows:
WL_HOME\server\bin\win64\oci920_8
to your PATH
, where WL_HOME
is the directory of your WebLogic Server installation.ORACLE_HOME\bin
to your PATH,
where ORACLE_HOME
is the directory of your Oracle client installation. Always add the WebLogic jDriver for Oracle and Oracle home information at the beginning of your PATH
. For example:%
ORACLE_HOME%\bin
;%PATH%
Using the above syntax to create an actual example for Oracle 9.2.0, your path may look like:
set PATH=
%WL_HOME%\server\bin\win64\oci920_8;%ORACLE_HOME%\bin;%PATH%
To set up your Solaris environment to support the use of WebLogic jDrivers, you must set your environment variable LD_LIBRARY_PATH
to include the directory that contains the native interface file (the driver file) and the directory in which you installed the Oracle client.
libweblogicoci39.so
and libweblogicoxa39.so
reside. For example:
$WL_HOME/server/lib/solaris/oci
xxxx
$ORACLE_HOME/lib
Using the above syntax to create an actual path for Oracle 8.1.7, your path may look like:
export LD_LIBRARY_PATH
=$WL_HOME/server/lib/solaris/oci817_8:$
ORACLE_HOME/lib:$LD_LIBRARY_PATH
The following table provides the directory and Oracle client versions for Solaris.
The following table lists the directory in which vendor-supplied libraries from Oracle reside for 32-bit and 64-bit installations on Solaris.
Note: To make sure your platform is supported on the WebLogic Server release you are running, see BEA WebLogic Server Certifications.
To set up your AIX environment to support the use of WebLogic jDriver for Oracle, you must set your environment variable LIBPATH
to include the directory that contains the native interface file (the driver file) and the directory in which you installed the Oracle client.
libweblogicoci39.so
and libweblogicoxa39.so
reside. For example:
$WL_HOME/server/lib/aix/oci
xxxx
$ORACLE_HOME/lib
Using the above syntax to create an actual path for Oracle 9.2.0, your path may look like:
export LIBPATH
=$WL_HOME/server/lib/aix/oci920_8:$
ORACLE_HOME/lib:$LIBPATH
The following table provides the directory and Oracle client versions for AIX.
The following table lists the directory in which vendor-supplied libraries from Oracle reside for 32-bit installations on AIX.
To set up your HP environment to support the use of WebLogic jDrivers, you must set your environment variable SHLIB_PATH
to include the directory that contains the native interface file (driver file) and the directory in which you installed your Oracle client.
Note: Oracle 9 for HP-UX is available in a 64-bit version only, including the Oracle client, and can only be installed on 64-bit machines. Because the WebLogic jDriver for Oracle is a type-2 JDBC driver, it requires the Oracle client for database access. Therefore, to use the WebLogic jDriver for Oracle with Oracle 9, you must run WebLogic Server on a 64-bit machine. The Oracle 9 installation contains both 32-bit and 64-bit libraries. The WebLogic jDriver uses the 32-bit libraries so you must set SHLIB_PATH as described below.
For Oracle 8, use the following syntax:
libweblogicoci39.sl
and libweblogicoxa39.so
for Oracle 8i reside. For example:
$WL_HOME/server/lib/hpux11/
oci817_8
$ORACLE_HOME/lib
For Oracle 9i, use the following syntax:
libweblogicoci39.sl
and libweblogicoxa39.so
for Oracle 9i reside. For example:
$WL_HOME/server/lib/hpux11/
oci901_8
$ORACLE_HOME/lib32
Using the above syntax to create an actual path for Oracle 8.1.7, your path may look like:
export SHLIB_PATH
=
$WL_HOME/server/lib/hpux11/oci817_8:$ORACLE_HOME
/lib:$SHLIB_PATH
For Oracle 9.0.1, your path may look like:
export SHLIB_PATH
=
$WL_HOME/server/lib/hpux11/oci901_8:$ORACLE_HOME
/lib32:$SHLIB_PATH
The following table provides the directory and Oracle client versions for HP-UX.
The following table lists the directory in which vendor-supplied libraries from Oracle reside for 32-bit and 64-bit installations on HP.
To find out if your platform is supported, see BEA WebLogic Server Certifications.
To find out if your platform is supported, see BEA WebLogic Server Certifications.
To find out if your platform is supported, see BEA WebLogic Server Certifications.
Once you have installed WebLogic jDriver for Oracle, verify that you can use it to connect to your database. To test your connection, use a utility called dbping
that is provided with the WebLogic Server software.
To set your environment and to use dbping
, type the following commands on the command line:
WL_HOME
\server\bin\setWLSEnv.cmd
set path=WL_HOME
\server\bin\oci817_8;%PATH%
java utils.dbping ORACLE user password server
Where WL_HOME
is the directory where WebLogic Platform is installed, typically c:\bea\weblogic
XX
.
For detailed instructions for using the dbping
utility, see Using the WebLogic Java Utilities in the Command Reference Guide.
If you have problems, check Testing JDBC Connections and Troubleshooting in Programming WebLogic JDBC.
If you are using WebLogic jDriver for Oracle with either BEA WebLogic Server or BEA WebLogic Express, you can set up a pool of connections to your Oracle DBMS to be established when WebLogic Server starts. Because the connections are shared among users, these connection pools eliminate the overhead of opening a new database connection for each user.
Your application then looks up a DataSource on the JNDI tree and requests a connection from the connection pool. When finished with the database connection, your application returns it to the connection pool.
PATH
(Windows) or load library path
(UNIX) of the shell where you will start WebLogic Server. For more information, see Starting and Stopping Servers in the Administration Console Online Help.
DataSource on the JNDI tree or the WebLogic RMI, Pool, and JTS drivers |
Connecting To a Database Using a JDBC Connection Pool in Programming WebLogic HTTP Servlets. |
If you are using a connection from a connection pool (that uses the WebLogic jDriver for Oracle to create database connections) in a client application , JDBC activity on the client is not automatically included in the JDBC log on the server. To enable JDBC logging and to include JDBC activity on the client in the JDBC log on the server, follow these steps:
If you are using an integrated development environment (IDE) or a debugger, copy the WebLogic-supplied native library (driver file) to a new file with a name that ends in _g
before the file extension. For example,
libweblogicoci39.so
to libweblogicoci39_g.so
. For distributed transactions, copy libweblogicoxa39.so
to libweblogicoxa39_g.so
.weblogicoci39.dll
to weblogicoci39_g.dll
. For distributed transactions, copy weblogicoxa39.dll
to weblogicocoxa39_g.dll
.
For more information, read the following:
Using WebLogic jDriver for Oracle in Configuring and Using WebLogic jDriver for Oracle (this guide). |