|Oracle8i National Language Support Guide
Release 2 (8.1.6)
Part Number A76966-01
This manual provides reference information about Oracle's National Language Support (NLS) capabilities. This information includes:
Oracle8i National Language Support Guide describes how to deal with many of the common problems in working in environments with multiple languages or character sets.
Getting to Know Oracle8i for information about the differences between Oracle8i and the Oracle8i Enterprise Edition and the available features and options. That book also describes all the features that are new in Oracle8i. Oracle8i National Language Support Guide describes those features which are common to both products.
This manual is written for database administrators, system administrators, and database application developers who need to deal with NLS-related matters.
It is assumed that readers of this manual are familiar with relational database concepts, basic Oracle server concepts, and the operating system environment under which they are running Oracle.
This manual is not an installation or migration guide. If your primary interest is installation, refer to your operating-system-specific Oracle documentation. If your primary interest is database and application migration, refer to Oracle8i Migration.
In addition to administrators, experienced users of Oracle and advanced database application designers will find information in this manual useful. However, database application developers should also refer to the Oracle8i Application Developer's Guide - Fundamentals and to the documentation for the tool or language product they are using to develop Oracle database applications.
This manual is organized as follows:
This chapter contains an overview of NLS issues and Oracle's approach to NLS.
This chapter contains an explanation of Oracle's NLS capabilities.
This chapter contains sample scenarios for enabling NLS capabilities.
This chapter describes NLS considerations for SQL programming.
This chapter describes NLS considerations for OCI programming.
This chapter describes NLS considerations for Java.
This chapter describes the languages, territories, character sets, and other locale data supported by the Oracle server.
This chapter shows how to customize NLS data objects.
This chapter lists some obsolete names for character sets.
This chapter defines NLS terminology.
The following sections describe the conventions used in this manual.
The text of this manual uses the following conventions.
Uppercase text is used to call attention to command keywords, database object names, parameters, filenames, and so on.
For example, "After inserting the default value, Oracle checks the FOREIGN KEY integrity constraint defined on the DEPTNO column," or "If you create a private rollback segment, the name must be included in the ROLLBACK_SEGMENTS initialization parameter."
Italicized words within text are book titles or emphasized words.
Commands or statements of SQL, Oracle Enterprise Manager line mode, and SQL*Plus appear in a monospaced font.
INSERT INTO emp (empno, ename) VALUES (1000, 'SMITH'); ALTER TABLESPACE users ADD DATAFILE 'users2.ora' SIZE 50K;
Example statements may include punctuation, such as commas or quotation marks. All punctuation in example statements is required. All example statements terminate with a semicolon (;). Depending on the application, a semicolon or other terminator may or may not be required to end a statement.
UPPERCASEin Code Examples
Uppercase words in example statements indicate the keywords within Oracle SQL. When you issue statements, however, keywords are not case sensitive.
lowercasein Code Examples
Lowercase words in example statements indicate words supplied only for the context of the example. For example, lowercase words may indicate the name of a table, column, or file.
We value and appreciate your comments as an Oracle user and reader of our manuals. As we write, revise, and evaluate our documentation, your opinions are the most important feedback we receive.
You can send comments and suggestions about this manual to the Information Development department at the following e-mail address:
If you prefer, you can send letters or faxes containing your comments to: