Oracle9i Directory Service Integration and Deployment Guide
Release 1 (9.0.1)

Part Number A90153-01
Go To Documentation Library
Go To Product List
Book List
Go To Table Of Contents
Go To Index

Master Index


Go to previous page Go to next page


Directory Service Integration and Deployment Guide is a starting point for those who want to learn how Oracle products use an LDAP-compliant directory, specifically Oracle Internet Directory. The book is also a starting point for learning how to configure Oracle Internet Directory to use Oracle products.

This preface contains these topics:


Directory Service Integration and Deployment Guide is intended for the following readers:

The book assumes no prior knowledge of LDAP, although a basic understanding of the protocol and its purpose are helpful.


This document contains:

Chapter 1, "The Oracle Directory Environment"

This chapter introduces Oracle directory-enabled products and Oracle Internet Directory. It also examines strategies to integrate Oracle products with third-party directories.

Chapter 2, "Directory Server Concepts"

This chapter describes the function of directories, defines the LDAP protocol, and identifies the components of an online directory.

Chapter 3, "Planning and Deployment Guidelines"

This chapter provides an overview of issues to consider before deploying a directory.

Chapter 4, "Deploying Oracle Products with Oracle Internet Directory"

This chapter describes how specific Oracle products use Oracle Internet Directory. It describes where each product stores its entries and how it protects these entries from unauthorized access. The chapter also discusses deployment factors particular to each product.

Chapter 5, "Completing Directory Usage Configuration"

This chapter describes how to configure access to a directory that is already installed. It also provides links to documents that describe directory configuration tasks particular to each of the Oracle products examined in Chapter 4.

Appendix A, "Oracle-Specific LDAP Schema Extensions"

This appendix lists and describes the object classes and attributes that LDAP-enabled Oracle products use to define entries in Oracle Internet Directory.

Appendix B, "LDAP Command-Line Tools"

This appendix lists and describes six popular command-line tools available through the LDAP C-API.

Related Documentation

For more information, see these Oracle resources:

In North America, printed documentation is available for sale in the Oracle Store at

Customers in Europe, the Middle East, and Africa (EMEA) can purchase documentation from

Other customers can contact their Oracle representative to purchase printed documentation.

To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at

If you already have a username and password for OTN, then you can go directly to the documentation section of the OTN Web site at

For additional information, see:


This section describes the conventions used in the text and code examples of this documentation set. It describes:

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.

Convention  Meaning  Example 


Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both. 

When you specify this clause, you create an index-organized table.  


Italic typeface indicates book titles or emphasis. 

Oracle9i Database Concepts

Ensure that the recovery catalog and target database do not reside on the same disk. 

UPPERCASE monospace (fixed-width font) 

Uppercase monospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, 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 NUMBER column.

You can back up the database by using the BACKUP command.

Query the TABLE_NAME column in the USER_TABLES data dictionary view.


lowercase monospace (fixed-width font) 

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. 

Enter sqlplus to open SQL*Plus.

The password is specified in the orapwd file.

Back up the datafiles and control files in the /disk1/oracle/dbs directory.

The department_id, department_name, and location_id columns are in the hr.departments table.

Set the QUERY_REWRITE_ENABLED initialization parameter to true.

Connect as oe user.

The JRepUtil class implements these methods. 

lowercase monospace (fixed-width font) italic 

Lowercase monospace italic font represents placeholders or variables. 

You can specify the parallel_clause.

Run Uold_release.SQL where old_release refers to the release you installed prior to upgrading. 

Conventions in Code Examples

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 normal 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.

Convention  Meaning  Example 

[ ] 

Brackets enclose one or more optional items. Do not enter the brackets. 

DECIMAL (digits [ , precision ]) 

{ } 

Braces enclose two or more items, one of which is required. Do not enter the braces. 


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:

  • That we have omitted parts of the code that are not directly related to the example

  • That you can repeat a portion of the code


CREATE TABLE ... AS subquery;

SELECT col1, col2, ... , coln FROM employees; 



Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example. 


Other notation 

You must enter symbols other than brackets, braces, vertical bars, and ellipsis points as shown. 

acctbal NUMBER(11,2);

acct CONSTANT NUMBER(4) := 3; 


Italicized text indicates placeholders or variables for which you must supply particular values. 

CONNECT SYSTEM/system_password

DB_NAME = database_name 


Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order 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. 

SELECT last_name, employee_id FROM employees;


DROP TABLE hr.employees; 


Lowercase typeface indicates programmatic elements that you supply. For example, lowercase indicates names of tables, columns, or files.

Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown. 

SELECT last_name, employee_id FROM employees;

sqlplus hr/hr


Documentation Accessibility

Oracle's goal is to make our products, services, and supporting documentation accessible to the disabled community with good usability. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at

JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.

Go to previous page Go to next page
Copyright © 1996-2001, Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Go To Product List
Book List
Go To Table Of Contents
Go To Index

Master Index