Oracle SQLJ Release 220.127.116.11.0 Production
SQLJ requires an installation of JDK1.1
or JDK1.2 or
later from Sun Microsystems. It must be installed and the Java interpreter
must be available in your path. In the rest of this page we assume that
both the Java compiler (javac) and the Java interpreter (java)
are installed correctly in your path.
Since SQLJ runs on top of the JDBC API, a driver compliant
with the database to be used must be installed in your system. The current
version of SQLJ has been tested with the 18.104.22.168.0 release of Oracle's
Configure your environment as follows:
We assume that SQLJ has been installed with the Oracle installer. Let ORACLE_HOME
be the location into which your Oracle products have been installed.
Verify your JDBC installation before using SQLJ. Refer to the section "Getting
Started" in the book SQLJ
Developer's Guide and Reference Oracle 9i Release 2 (9.2.0)
for information on testing your SQLJ and JDBC installations. (Note: You
must be signed up for the Oracle Technology Network at http://technet.oracle.com
in order to access the online documentation.)
Specifically, in order to use SQLJ you must have ORACLE_HOME/jdbc/lib/classesxxx.jar
in your CLASSPATH environment variable (where xxx
is either 111 or 12, depending on the version of your Java
compiler). Additionally -depending on the nature of your JDBC driver- dynamic
link libraries may have to be installed.
Ensure that the directory ORACLE_HOME/bin is included
in your environment variable PATH.
You must add the files ORACLE_HOME/sqlj/lib/translator.jar
and one of the ORACLE_HOME/sqlj/lib/runtimexxx.jar
libraries. to the environment variable CLASSPATH.
If you use JDK 1.1.x and Oracle JDBC 9.0.1 or later, use runtime11.jar.
If you use JDK 1.2 or later and Oracle JDBC 9.0.1 or later use runtime12.jar.
You can also use runtime12ee.jar if you have a J2EE environment.
If you use an Oracle JDBC driver version prior to JDBC 9.0.1 use runtime.jar.
If you do not have an Oracle JDBC driver in your environment use runtime-nonoracle.jar.
This completes the installation.
If you are using runtime.jar, you need to explicitly specify -codegen=iso.
This runtime version is not compatible with the default code generation
option -codegen=oracle for the Oracle 9.0.1 or later JDBC driver.
Earlier SQLJ releases only required that you place translator.jar
in the CLASSPATH in order to translate and/or run SQLJ programs. SQLJ
versions 8.1.7 and later require additionally one of the runtime jar files
(runtime.jar, runtime11.jar, or runtime12.jar) in your CLASSPATH in
order to translate SQLJ programs.
To verify that your installation is correct, follow the instructions in
the "Getting Started" section of theSQLJ
Developer's Guide and Reference.
The following table provides information about the Oracle JDBC drivers.
||JDBC Driver Class Name
|Oracle server-side JDBC
In the table, host corresponds to the machine name of the database
server, for example, localhost. The port corresponds to
the tcp/ip port # of the listener, for example 1521. The
corresponds to the TNS_alias defined in your local
Since SQLJ relies on JDBC for acquiring the connections to be
used, your application can use any of the JDBC mechanisms recommended by
your vendor for loading the JDBC driver and specifying the database URL.
Installation: follow the SQLJ installation steps.If you have installed
SQLJ, you also have installed JPublisher. Specifically, you must have an
Oracle JDBC driver (classesxxx.jar), translator.jar
and an appropriate runtime jar in your CLASSPATH. If you installed
SQLJ through the Oracle installer, a shell script, or a .bat file
-depending on your platform- for jpub will have been created and
placed in [Oracle Home]/bin. It contains all required references
to JRE, JDBC, and SQLJ classes. However, in order to properly compile generated
.sqlj code, you still want to ensure that your environment is
correctly set up for SQLJ. Note also that while JPublisher only requires
a Java Runtime Environment, the SQLJ translator must have a full JDK environment.
While in previous releases, JPublisher only required translator.jar
in the CLASSPATH, you now also have to supply a runtime
jar (if you use JDK 1.1 and Oracle JDBC 9.0.1 or later you can specify
runtime11.jar and under JDK 1.2 or later and JDBC 9.0.1 or later
you can specify runtime12.jar).
User's Guide and Reference
JPublisher Demos: [Oracle Home]/sqlj/demo/jpub/
Join the Oracle
Technology Network for additional SQLJ and JDBC information, examples,
Visit Oracle's Java Homepage
for information and updates on JDBC, SQLJ and other Java technologies
This product is serviced through Oracle Support. For more information see