Creating an OracleContext in Microsoft Windows 2003 Active Directory
(Doc ID 361192.1)
Last updated on JANUARY 20, 2025
Applies to:
Net Configuration Assistant - NetCA - Version 10.1.0.4 to 11.2.0.4 [Release 10.1 to 11.2] Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later Gen 2 Exadata Cloud at Customer - Version N/A and later Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later Oracle Database - Enterprise Edition - Version 11.1.0.7 and later Microsoft Windows x64 (64-bit)
Purpose
An LDAP Schema is a collection of related entries (attributes, objectclasses) stored within an LDAP directory. An LDAP Context refers to all information relating to entries (users, groups, etc.) as well as their state.
An LDAP directory stores information (Schema/Context) pertaining to Oracle software under an entry called an Oracle Context (cn=OracleContext). An OracleContext may exist under any entry in a Directory Information Tree (DIT). Oracle Net Configuration Assistant (NetCA) can be used to create an OracleContext as well as to configure access to the directory. Once configured for directory access, Database Configuration Assistant (DBCA) can be used to register databases. Registration adds entries for databases and associated Oracle Net connect descriptors.
Though OracleContexts are typically created in Oracle Internet Directory (OID), they are not limited to using OID as their LDAP store. It is possible to create an OracleContext in a foreign Directory Schema, such as Microsoft Active Directory (AD).
The purpose of this article is to describe how to create an OracleContext within Microsoft Active Directory 2003.
Scope
This article is intended for Microsoft Windows System Administrators and Oracle Database Administrators looking to create an OracleContext within Microsoft Active Directory.
Oracle Internet Directory (OID) provides rich features and functionality. However, depending on deployment requirements, the use of an OracleContext collocated within an existing Active Directory Schema may be sufficient. This approach does not require additional hardware, administration or maintenance of a dedicated Oracle Internet Directory installation.
Creating an OracleContext within Active Directory requires that you already have a fully functional and correctly configured Active Directory server. The procedure described uses the following topology and product versions:
Oracle Client
Hostname: <CLIENT HOSTNAME>
IP Address: <IP ADDRESS USED BY CLIENT>
Microsoft Windows Server 2003 Enterprise Edition Service Pack 1
Oracle Client Oracle10g Release 1 Patchset 2 (10.1.0.4.0) for Microsoft Windows
Active Directory Server
Hostname: <LDAP SERVER HOSTNAME>
IP Address: <IP ADDRESS USED BY LDAP SERVER>
Microsoft Windows Server 2003 Enterprise Edition Service Pack 1
Active Directory Realm: home.com
This article describes how to create an OracleContext within Microsoft Windows Server 2003 Enterprise Edition Active Directory, however other Windows Server 2003 Editions, such as Standard or Datacenter, may also be used. The various features of Windows 2003 Editions can be compared at http://www.microsoft.com/windowsserver2003/evaluation/features/compareeditions.mspx.
Note - Microsoft Windows 2003 Service Pack 1 was applied before the Server was promoted (dcpromo) to a standalone Domain Controller/DNS server in it's own forest.
Details
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!