This preface introduces you to the Oracle Database SQLJ Developer's Guide, discussing the intended audience and conventions of this document. A list of related Oracle documents is also provided.
This preface covers the following topics:
This manual is intended for anyone with an interest in SQLJ programming but assumes at least some prior knowledge of the following:
Although general knowledge of SQL is sufficient, any knowledge of JDBC and Oracle-specific SQL features would be helpful as well.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
Oracle customers have access to electronic support through My Oracle Support. For information, visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Also available from the Oracle Java Platform group are the following Oracle resources:
This book introduces the basic concepts of Java in Oracle Database 11g and provides general information about server-side configuration and functionality. Information that pertains to Oracle Database Java environment in general, rather than to a particular product such as JDBC or SQLJ, is in this book.
It also discusses Java stored procedures, which are programs that run directly in Oracle Database. With stored procedures, Java developers can implement business logic at the server level, thereby improving application performance, scalability, and security.
This book covers programming syntax and features of the Oracle implementation of the JDBC standard. This includes an overview of the Oracle JDBC drivers, details of the Oracle implementation of JDBC 1.22, 2.0, 3.0, and 4.0 features, and discussion of Oracle JDBC type extensions and performance extensions.
This book describes how to use the Oracle JPublisher utility to translate user-defined SQL types or PL/SQL packages into Java classes. If you are developing SQLJ or JDBC applications that use object types, VARRAY types, nested table types, object reference types, or PL/SQL packages, then JPublisher can generate custom Java classes to map to them.
The following documents are from the Oracle Server Technologies group:
Note:Oracle error message documentation is available in HTML only. If you have access to the Oracle Documentation CD only, you can browse the error messages by range. Once you find the specific range, use the "find in page" feature of your browser to locate the specific message. When connected to the Internet, you can search for a specific error message using the error message search feature of the Oracle online documentation.
For documentation of SQLJ standard features and syntax, refer to the following specification:
Information Technology - Database Languages - SQL - Part 10: Object Language Bindings (SQL/OLB)
Throughout this manual, the term "ISO SQLJ standard" is used to refer to this standard.
You can obtain the ISO SQLJ standard from ANSI through the following Web site:
Click eStandards Store and search for the term "INCITS/ISO/IEC 9075-10".
You can also obtain the ISO SQLJ standard from ISO through their web store
Visit the preceding link and search for the term "ISO/IEC 9075-10".
The following location has SQLJ sample applications:
This section describes the conventions used in the text and code examples of this documentation set. It describes:
Note:Also note that command-line examples are for a UNIX environment with a system prompt of "
%". This is only by convention and can be adjusted as appropriate for your operating system.
There are various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.
|Italics||Italic typeface indicates book titles or emphasis, or terms that are defined in the text.||Oracle Database Concepts
Ensure that the recovery catalog and target database do not reside on the same disk.
||Uppercase monospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, data types, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, usernames, and roles.||You can specify this clause only for a
You can back up the database by using the
||Lowercase monospace typeface indicates executables, filenames, directory names, and sample user-supplied elements. Such elements include computer and database names, net service names, and connect identifiers, as well as user-supplied database objects and structures, column names, packages and classes, usernames and roles, program units, and parameter values.
Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.
The password is specified in the
Back up the data files and control files in the
||Lowercase italic monospace font represents place holders or variables.||You can specify the
Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace (fixed-width) font and separated from standard text as shown in this example:
SELECT username FROM dba_users WHERE username = 'MIGRATE';
The following table describes typographic conventions used in code examples and provides examples of their use.
|< >||In this document, angle brackets are used instead of regular brackets to enclose one or more optional items. Do not enter the angle brackets. (Regular brackets are not used due to SQLJ syntax considerations.)||
||||A vertical bar represents a choice of two or more options within brackets or braces. Enter one of the options. Do not enter the vertical bar.||
||Horizontal ellipsis points indicate either:
|Other notation||You must enter symbols other than brackets, braces, vertical bars, and ellipsis points as shown.||
||Italicized text indicates place holders or variables for which you must supply particular values.||
Enter password: password
||Uppercase typeface indicates elements supplied by the system. These terms are in uppercase to distinguish them from terms you define. Unless terms appear in brackets, enter them in the order and with the spelling shown. However, because these terms are not case-sensitive, you can enter them in lowercase.||
||Lowercase typeface indicates programmatic elements that you supply. For example, lowercase indicates names of tables, columns, or files.