Article-ID: <Note:111424.1>
Circulation: PUBLISHED (EXTERNAL)
Folder: server.DBA.Security
Title: How to Install Oracle 8.1.6 with Integration for Windows
2000 Active Directory
Document-Type: BULLETIN
Impact: LOW
Skill-Level: NOVICE
Server-Version: 08.01.06
Updated-Date: 04-APR-2001 09:16:51
References:
Shared-Refs:
Attachments: NONE
Content-Type: TEXT/PLAIN
Keywords: 8.1.6; ACTIVE; DATABASE; DIRECTORY; INSTALL; REGISTER;
Products: 5/RDBMS;
Platforms: 100;

PURPOSE
-------

To Install Oracle 8.1.6 With Integration for
Microsoft Windows 2000 Active Directory


SCOPE & APPLICATION
-------------------

Intended Audience: DBA
Use: Help for installing 8.1.6 with Active Directory


How to Install Oracle 8.1.6 with Integration for
Microsoft Windows 2000 Active Directory
------------------------------------------------

I. Introduction
A. This document introduces the procedures for performing a Typical
install of the Oracle 8.1.6.0.0 EE database on a Windows 2000 server domain
controller. The operating system on this server is installed with one 6 GB
partition, formatted as NTFS with the default permission settings. The fully
qualified domain name of the server is rocky.mountain.com, with a downlevel
NetBIOS name of Rocky (the domain controller for the Mountain domain).

B. It should be noted that although this procedure has been performed
on the only domain controller in the Active Directory forest, the steps are
very similar if they are performed on a member server in an Active Directory
domain. Moreover, this domain controller will be left in mixed mode (an Active
Directory status which allows interaction with downlevel Windows NT domain
controllers).


II. Requirements
A. It is vital that the person performing this procedure has the proper
administrative control, both in the Active Directory forest, as well as on the
local member server (if this procedure is performed on a member server), or
domain controller. Integrating the Oracle database with Active Directory will
cause a modification of the Active Directory Schema and will also create new
services. Since these processes will run with the credentials of the logged on
user, it is required that the person logged on has the necessary credentials
for performing these tasks.

B. The person who is installing the Oracle 8.1.6 database must be a member
of the Schema Admins group in order to make changes to the Active Directory
Schema. By default, this group has only one member: the Administrator account
of the first domain in the forest. If the installer is not using this account,
the installer must be manually added to Schema Admins prior to installing the
database. Keep in mind that when a user is added to this group, that user must
log off and log back on in order to have the new membership reflected in the
access token of the user (i.e., to have this new membership take effect). This
person should also be a member of Domain Admins and this group should be a
member of the local Administrators group. The Administrator account in the
first domain created in the forest is a member of all of these groups by
default, as well as being a default member of Enterprise Admins (a forest
level group). If possible, the installer should log on as Administrator, the
administrative account in the first domain in the forest and check to make sure
that this account has the proper forest wide control. If it is not possible to
log on with this account, the installer must at the very least be a member of
the local Administrators group and a member of the forest wide Schema Admins
group.

C. DNS should be properly installed somewhere in the Active Directory
forest, and the installer should verify that the service is available and
correctly resolving the machine names involved in the installation of the
database. This is especially important if the database is being installed
on a machine which is remote from the domain controller where the Schema
resides (by default, the first domain controller in the first domain in the
Active Directory forest is the Schema Operations Master).


III. Procedures
A. Create or open a Microsoft Management Console which contains snap-ins
for Active Directory Domains and Trusts, Active Directory Sites and Services,
Active Directory Users and Computers, and Computer Management. This mmc is
necessary to enable writing to the Schema and perform troubleshooting as
necessary. To create the mmc, Click Start, Run, and type mmc. When the window
opens, click the Console menu and click Add/Remove Snap-in. When that window
opens, click Add. When the Add Standalone Snap-in window opens, highlight the
above snap-ins one at a time and click add. When all are added, click close,
then OK, and then save the console by clicking on the Console menu, click Save
As and choose a location and name for the new console. Leave the console open.

B. In order to install a snap-in for the Active Directory Schema, you must
first register a .dll file to make the tool visible. Click Start, Run, and
type regsvr32 schmmgmt.dll. You should see a confirmation window stating:
“DllRegisterServer in schmmgmt.dll succeeded”. Click OK.

C. On the Console menu of your new console, click Add/Remove Snap-in.
When the Add/Remove Snap-in Window opens, click Add. When the Add Standalone
Snap-in window opens, you should see a new snap-in listed second from the top
called Active Directory Schema. Highlight it and click Add. Click Close and
then OK. Your console should now show Active Directory Schema at the bottom
of the console tree. Click the Console menu, and click Save.

D. Right-click Active Directory Schema and click Operations Master. Click
the check box next to “The Schema may be modified on this Domain Controller”.
Note the name of the operations master on which the schema resides. Click OK
to close the box.

E. Ensure that you have sufficient free space to install the database.
A typical install requires 1001 MB, but expansion of the installation files may
require up to 2 GB for the install to succeed. Place the Oracle 8.1.6 EE
CD-ROM into the CD-ROM drive and when the auto-run brings up the Install
window, click Install/Deinstall Products.

F. At the Welcome Screen, Click Next.

G. Modify or accept the name and location for the Destination options and
click Next.

H. Ensure that Oracle8i Enterprise Edition 8.1.6.0.0 is selected and click
Next.

I. Ensure that Typical is selected and click Next.

J. Type in orcl.world at the Global Database Name window. Orcl should now
appear in the SID window. Click Next.

K. At the Summary window, click Install

L. At the end of the install, click Exit and Yes to confirm the exit.

M. At this point, you must configure the naming methods and Directory
Service Access.

N. Click Start, Programs, Oracle- OraHome81, Network Administration, Net8
Configuration Assistant.

O. Select Directory Service Access configuration.

P. Select Perform directory access configuration for a server.

Q. Pull down the Directory Type select box and choose Microsoft Active
Directory and click Next.

R. At the Hostname window, type in the fully qualified domain name of the
domain controller on which the schema resides. For this example, the fully
qualified domain name of my server is rocky.mountain.com. Click Next.

S. Ensure that “Yes, I want to add the required Oracle Schema” is selected
and click Next only ONCE. This process may take up to a minute. You will
receive a warning which appears to be an error that states that the NET8
Configuration Assistant is unable to create or update the schema. The process
has actually succeeded. Click OK only ONCE to close the window.

T. You may see another window with a Red alarm bell. Select “I want to
verify the directory service information and try again” and click OK

U. Ensure that Directory Service Access configuration is selected and
click Next.

V. Select Perform directory access configuration for a server and click
Next.

W. Ensure that Directory Type is selected for Microsoft Active Directory
and click Next.

X. Type in the fully qualified domain name of your schema operations
master and click next.

Y. Note that this screen has now changed from the option in step S to
“Yes, I want to create a new Oracle Context”. Click Next only ONCE and you
should receive a message that Directory Server Access configuration is complete.
Click Next and select Naming Methods configuration and click Next.

Z. Select “Directory” from the left window and click the right arrow. You
may choose to remove Oracle Names and Host Name from the list, but ensure that
you have at least Directory and local in the right window and then click Next
and Next again. You will receive a message that Naming methods configuration
is complete. Click Next and then Finish.

AA. Open your mmc console, expand the Active Directory Schema and highlight
Classes. In the right pane, scroll down and you should note several classes
which begin with orcl. The Schema has now been updated to reflect Oracle
objects.

BB. Expand the Active Directory Users and Computers and Expand the domain
name and expand the Oracle Context. If any of the icons are not fully formed,
log off and log back on. This is caused by the addition of your account to
groups created by the Active Directory configuration. Logging back on will
update your access token.

CC. Close the mmc console. Leaving it open at this point may cause the
next procedure to fail.

DD. To register the database with Active Directory, Click Start, Programs,
Oracle-OraHome81, Database Administration, Database Configuration Assistant.

EE. When the application opens, select Change database configuration.

FF.Ensure that the servicesid for your database is selected
and click Next.

GG. Select Dedicated Server mode and click Next. Click Next again.

HH. Ensure that Yes, register the database is selected and click Finish.

II. You will be prompted to confirm the location of the init.ora file
for your database. Confirm it and click OK. You will be prompted to confirm
the changing of the init.ora. Click OK.

JJ. Open the mmc console, expand Active Directory Users and Computers and
Expand the domain name and expand the Oracle Context. You should now notice
that the sid name of your database appears under Oracle Context.
The Oracle Database is now registered with Active Directory with a service
name which is identical to your sid name.

IV. Optional Procedures
A. If you choose, you may add the snap in for the Oracle Managed Products
and complete the OS authentication procedures or create users in the database.

B. Click the Console Menu and click Add/Remove Snap-in.

C. Click Add, scroll down, and highlight Oracle Primary MMC Snap-in and
click Add and then click close.

D. Click OK, then Click the console menu and click Save.

E. Expand the Oracle Managed Objects Snap-in, Expand Computers, Expand
your computer name, and expand databases. You should now see your sid name.
Right click the sid name and click connect database. You should connect
immediately since your Administrator account is a member by default in the
newly created Ora_Dba group. You may right click External OS Users and OS
database Administrators and create users in the database.

F. Client machines can be set up and configured by installing the Oracle
client from the CD-ROM, running the Net8 Configuration Assistant, choosing
Directory Service Access Configuration, and choosing directory access
configuration for a client.