Sap basis installation on win nt oracle 4.6d

SAP
®
AG • Neurottstr. 16 • D-69190 Walldorf
SAP Basis Installation on
Windows NT:
Oracle
4.6D Support Release

SAP Basis Installation on Windows NT: Oracle
2 July 2001
Copyright
©Copyright 2001 SAP AG. All rights reserved.
No part of this brochure may be reproduced or transmitted in any form or for any purpose without
the express permission of SAP AG. The information contained herein may be changed without
prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft®, WINDOWS®, NT®, EXCEL®, Word® and SQL Server® are registered trademarks of
Microsoft Corporation.
IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®,
AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.
ORACLE® is a registered trademark of ORACLE Corporation, California, USA.
INFORMIX®-OnLine for SAP and Informix® Dynamic Server are registered trademarks of
Informix Software Incorporated.
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of The Open Group.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide
Web Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute of
Technology, 545 Technology Square, Cambridge, MA 02139.
JAVA® is a registered trademark of Sun Microssystems, Inc. , 901 San Antonio Road, Palo Alto,
CA 94303 USA.
JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.
ADABAS® is a registered trademark of Software AG.
SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com Workplace, mySAP.com
Business Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP, SAP
Business Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, Management
Cockpit, SEM, SAP DB are trademarks or registered trademarks of SAP AG in Germany and in
several other countries all over the world. All other products mentioned are trademarks or
registered trademarks of their respective companies.
Documentation in the SAP Service Marketplace
You can find this documentation at the following address:
http://service.sap.com/instguides

July 2001 3
Typographic Conventions
Type Style Represents
Interface Text Words or characters that appear on the screen. This
includes system messages, field names, screen titles,
pushbuttons, menu names, and menu options.
Document Title Cross-references to other documentation
User Entry Exact user entry. These are words and characters that
you enter exactly as they appear in the documentation.
File Name File names, batch files, paths or directories, and
screen messages
<Variable User
Entry>
Variable user entry. Pointed brackets indicate that you
replace these words and characters with appropriate
entries.
NAME Names of elements in the SAP System. These include
report names, program names, transaction codes,
table names, and ABAP language elements.
KEY Keys on your keyboard. These include function keys
(for example, F2) and the ENTER key.
Icons
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
Tip

4 July 2001
Contents
SAP Basis Installation on Windows NT: Oracle Database ........... 7
Part I Standard SAP System Installation............................................. 9
1 Installation Planning ...............................................................................15
1.1 Hardware and Software Requirements Check...............................................................17
1.1.1 Checking Requirements for a Central System .........................................................18
1.1.2 Checking Requirements for a Standalone Database System ..................................20
1.1.3 Checking Requirements for a Dialog Instance.........................................................23
1.1.4 Checking Requirements for the Network..................................................................24
1.2 Distribution of Components to Disks..............................................................................26
1.2.1 Standard Configuration.............................................................................................29
1.2.2 Large Configuration ..................................................................................................31
1.2.3 Test System Configuration .......................................................................................33
1.2.4 SAP Directories ........................................................................................................35
2 Installation Preparations.........................................................................38
2.1 Checking for Windows NT File System..........................................................................38
2.2 Checking the Windows NT Domain Structure................................................................39
2.3 Installing Microsoft Management Console .....................................................................39
2.4 Installing Up-To-Date Dynamic Link Libraries................................................................40
2.5 Adjusting Virtual Memory ...............................................................................................41
2.6 Reducing the Size of the NT File Cache........................................................................41
2.7 Granting User Rights for the Installation ........................................................................42
2.8 Choosing the SAP System Name and the Host Name..................................................43
2.9 Preparing SAP System Transport Host..........................................................................44
2.10 Integration of Active Directory Services .......................................................................45
2.10.1 Preparing the Active Directory for SAP ..................................................................47
2.11 Installation of Multiple Components on One Database................................................49
3 The SAP System Installation ..................................................................51
3.1 Central System Installation ............................................................................................53
3.1.1 Installing the Database Software..............................................................................53
3.1.2 Installing R3SETUP..................................................................................................56
3.1.3 Installing the SAP System and Loading the Database.............................................58
3.1.4 Input for a Central System Installation......................................................................61
3.2 Standalone Database System Installation .....................................................................66
3.2.3 Installing the SAP System and Loading the Database.............................................73
3.2.4 Input for Central Instance Installation.......................................................................77
3.2.5 Input for the Database Instance Installation.............................................................81
3.3 Dialog Instance Installation ............................................................................................83
3.3.3 Installing a Dialog Instance.......................................................................................87
3.3.4 Input for Dialog Instance Installation ........................................................................89
3.4 Standalone Gateway Instance Installation.....................................................................92

July 2001 5
3.4.2 Installing a Gateway Instance...................................................................................94
4 Post-Installation Activities......................................................................96
4.2 Starting and Stopping the SAP System .........................................................................98
4.3 Logging on to the SAP System ......................................................................................99
4.4 Installing and Using the SAP License ..........................................................................100
4.5 Recognizing Initial System Problems...........................................................................101
4.6 Installing the Online Documentation ............................................................................101
4.7 Checking the RFC Destination.....................................................................................102
4.8 Configuring SAProuter and SAPNet - R/3 Frontend....................................................102
4.9 Secure Single Sign-On.................................................................................................103
4.9.1 Preparing the Application Server for Single Sign-On .............................................104
4.9.2 Preparing SAPgui and SAP Logon for Single Sign-On ..........................................105
4.9.3 Mapping SAP System Users to NT Users for Single Sign-On ...............................106
4.10 Performing a Full Backup of the Installation ..............................................................107
4.11 SAP Internet Solution Installation...............................................................................108
5 The R3SETUP Tool................................................................................109
5.1 INSTGUI.......................................................................................................................111
5.2 R3SETUP Command Files ..........................................................................................112
5.3 Changing Tablespace Sizes or Locations....................................................................113
5.4 R3SETUP Messages ...................................................................................................115
5.5 Using R3SETUP Online Help.......................................................................................115
5.6 Continuing an Interrupted Installation ..........................................................................116
5.7 Monitoring a Remote Installation..................................................................................117
5.8 R3SEDIT Utility ............................................................................................................118
6 Additional Information ..........................................................................119
6.1 Deletion of an SAP System Installation........................................................................119
6.1.1 Deleting an SAP Instance.......................................................................................119
6.1.2 Deleting the Database ............................................................................................120
6.2 SAP System Security on Windows NT.........................................................................122
6.2.1 Automatic Creation of Accounts and Groups .........................................................125
6.2.2 Manually Granting Rights for the Installation..........................................................126
6.2.3 Performing a Domain Installation as Local Administrator.......................................127
6.3 Installing Multiple Components on One Database.......................................................128
Part II MSCS SAP Installation........................................................... 131
7 Installation Planning for MSCS ............................................................135
7.1 Checking Hardware Requirements for MSCS .............................................................135
7.2 Checking Software Requirements for MSCS...............................................................137
7.3 Distribution of Components to Disks for MSCS ...........................................................137
7.4 Directories in an MSCS Configuration .........................................................................139
7.5 Obtaining Addresses for MSCS ...................................................................................140
8 Installation Preparations for MSCS......................................................144
8.1 Using Addresses in an MSCS Configuration ...............................................................146
8.2 Mapping Host Names to IP Addresses ........................................................................148
8.3 Checking the Mapping of Host Names for MSCS........................................................149
8.4 Assigning Drive Letters for MSCS................................................................................150
9 Central and Database Instance Installation for MSCS .......................151
9.1 Rebooting During the Installation for MSCS ................................................................153

6 July 2001
9.2 Moving MSCS Groups..................................................................................................153
9.3 Installing the Oracle Fail Safe Software.......................................................................154
10 The Conversion to MSCS....................................................................156
10.1 Rebooting during the Conversion...............................................................................158
10.2 Converting Node A for MSCS ....................................................................................158
10.3 Converting the DB to a Fail Safe DB..........................................................................160
10.4 Converting Node B for MSCS ....................................................................................163
10.5 Completing the MSCS Conversion ............................................................................165
11 Post-Installation Activities for MSCS.................................................166
11.1 Starting and Stopping the SAP System in an MSCS Configuration ..........................167

July 2001 7
SAP Basis Installation on Windows NT:
Oracle
Purpose
This documentation explains how to install the SAP System when your operating system is
Windows NT and your database is Oracle.
Throughout this documentation, the term SAP System is the same as SAP Basis
System. Also, SAP stands for SAP Basis in terms such as SAP profile or SAP
instance.
Implementation Considerations
There are two different procedures for installing an SAP System. Both are explained in detail in
this documentation.
• Standard SAP installation
The standard procedure must be followed for all systems except those on clustered
hardware. It can be used to set up different system configurations:
• A central system, in which the central instance and the database instance are on the
same host machine
• A standalone database system, in which the central instance and the database
instance are on different host machines
The procedure optionally includes the installation of dialog or gateway instances. The
installation of frontends for the SAP System is a separate procedure.
• MSCS SAP installation
This procedure must only be used for a Microsoft Cluster Server (MSCS) configuration. The
central instance and database are installed on two clustered machines and then configured
to protect the system against failure. The installation is performed in two stages. In the first
stage, a standard installation is performed including supplementary, cluster-specific steps. In
the second stage, the system is configured so that it becomes cluster-aware and is able to
take advantage of features that improve availability.
Multiple Components on One Database
With this SAP Release, SAP offers the installation of Multiple Components on one Database
(MCOD).That is, you can install an SAP Web AS System into an existing SAP System database.
For an MCOD installation, you can only combine systems for which the MCOD feature is
released by SAP.
For more information on MCOD, see:
• Installation of Multiple Components on One Database [page 49] for general information on
this feature
• Installing Multiple Components on One Database [page 128] for the installation procedure

8 July 2001
Integration
For both installation procedures, SAP provides the tool R3SETUP. This has a graphical user
interface (GUI) called INSTGUI that allows you to watch the progress of the installation and see
all messages issued by R3SETUP. You can call online help from the INSTGUI while you perform
the installation. You can start INSTGUI on a remote computer if you want.

Part I Standard SAP System Installation
July 2001 9
Part I Standard SAP System Installation
Purpose
When you set up an SAP System, you need to install the main components that enable the
system to operate. These are the:
• Central instance
• Database instance
• Dialog instances, if required
• Frontends
The following gives you an overview of the installation process.
Prerequisites
Read the installation notes before you begin the installation. These notes contain the most recent
information regarding the installation, as well as corrections to the installation documentation.
Installation Notes
420379 INST: 4.6D SR1 SAP Basis Inst. on Windows - General
420381 INST: 4.6D SR1 SAP Basis Inst. on Windows - Oracle
162266 Questions and Tips for R3SETUP NT
Configuration Planning
Before you can begin with the practical tasks that are necessary to install the main components
of the SAP System, you have to plan the configuration of the system. This involves deciding
which components you need and working out how these must be distributed to hosts. Normally
an SAP hardware partner can assist you in this task. On the basis of information about the
expected workload, set of applications that are to be deployed and number of users, the partner
can recommend a feasible configuration.
As the system configuration fundamentally influences the installation procedure, it is important to
have a clear configuration plan before you start the installation. There are two basic configuration
types: a central system and standalone database system.

10 July 2001
• Central System
The central instance and database instance are installed on a single host.
Database
Server
Central
Instance
• Standalone Database System
The central instance and database Instance are installed on two different hosts.
Database
Server
Central
Instance

July 2001 11
The configuration plan must specify whether a central or standalone database system is to be
installed and how many frontends and dialog instances are required. Once the plan is complete
and the required hardware is available, you can start with the installation process as summarized
in the following. Keep in mind that the process differs, depending on the hardware configuration
you have decided to implement.
Process Flow
The task of installing an SAP System can be subdivided into a number of phases:
Preparations
Preparations
SAP System Installation
SAP System Installation
Post-Installation Activities
Post-Installation Activities
Planning
Planning
The following summarizes the actions that have to be performed in each of the phases.
1. In the planning phase, you have to:
− Check the hardware and software requirements
SAP specifies hardware and software requirements for different system configurations in
check lists. On the basis of these lists you can determine whether your hardware meets
the minimal requirements for your planned configuration and find out which software
versions are necessary for the subsequent installation process.
For more information, see Hardware and Software Requirements Check. [Page 17]
− Work out how the main system directories are to be distributed to RAID arrays in the
system
During the actual installation procedure, the utilities that help you to install the database
and SAP software prompt you to specify the drives on which the main software
components are to be installed. Before you run these utilities, it is therefore essential to
get an overview the directories involved and to decide how these can be best distributed
to RAID arrays. An effective distribution takes into account aspects, such as the
expected workload, the size of individual components, performance of the system and
security of the data.
For more information, see Distribution of Components to Disks [Page 26].

12 July 2001
2. In the preparations phase, before you run the installation utilities, you need to perform a
number of tasks that are a prerequisite for a successful installation. These can be grouped
into two categories:
− Preparations related to the operating system
• Checking the Windows NT file system
• Checking the Windows NT domain structure
• Installing the Microsoft Management Console
• Updating the Dynamic Link Libraries
• Reserving virtual memory
• Reducing the size of the NT cache
• Granting user rights for the installation
• Preparing the Active Directory (optional)
− Other preparations
• Choosing system and host names
• Preparing the SAP System transport host
For more information, see Installation Preparations [Page 38].
3. In the installation phase, you have to carry out the steps that are necessary to set up the
core components of the SAP System. This involves installing the:
− Central and database instance
− Dialog instances
− Frontends
The installation procedure differs, depending on the planned system
configuration. When you set up a central system, all the required steps are
performed on the same host. When you set up a standalone database system
some actions are carried out on the database host, others on the central instance
host. The following summarizes the actions for both configuration types.

July 2001 13
a. Installation of the central and database instance
Central System Standalone Database System
a) Actions on the central system host:
− Installation of the Oracle server
software and latest Patch using the
Oracle Installer.
− Installation of the R3SETUP tool using
the file R3SETUP.BAT.
− Installation of the central instance and
database instance using the R3SETUP
option Install Central and Database
Instance.
a) Actions on the central instance host:
− Installation of the Oracle client
software and latest patch using the
Oracle Installer.
− Installation of the central instance
using the R3SETUP option Install
Central Instance.
b) Actions on the database host:
− Installation of the Oracle server
software and latest patch using the
Oracle Installer.
− Database creation and load using the
R3SETUP option Install Database
Instance.
b. Installation of the dialog instances
When the central and database instance have been installed, you can optionally install
one or more dialog instances on further hosts in the system. The following actions are
necessary to set up a dialog instance:
• Installation of the Oracle client software and the latest patch using the Oracle
Installer.
• Installation of the R3SETUP tool with the file R3SETUP.BAT.
• Installation of the dialog instance with the R3SETUP option Install Dialog Instance.
c. Installation of the frontends
Once the central, database and dialog instances have been set up, you can install the
SAP frontends following the instructions given in the documentation Installing SAP
Frontend Software for PCs.
For more information, see The SAP System Installation [Page 51]

14 July 2001
In a final, post-installation activities phase, you have to perform a number of tasks to
complete the installation. Some of these tasks are mandatory, others are optional and serve
to activate optional features that may be useful.
− Necessary tasks
• Starting and stopping the system
• Logging on to the system
• Installing the SAP License
• Checking the services
• Installing the online documentation
• Configuring the SAProuter and SAPNet - R/3 Frontend
• Performing steps specified in the System Administration Assistant
• Performing a full backup
− Optional tasks
• Configuring Single Sign-On
• Installing the SAP Internet solution
For more information, see Post-Installation Activities [Page 96].

1 Installation Planning
July 2001 15
Purpose
Before you begin with the practical installation tasks, it is essential to have a planning phase in
which you make a number of fundamental decisions that influence the subsequent installation
procedure. Careful planning is a prerequisite for the successful installation of the system.
Process Flow
When you plan the installation you have to:
• Decide on the optimal configuration for the system
• Decide whether a domain or local installation is suitable
• Make sure that you can meet the hardware and software requirements specified by SAP
• Work out how the software components must be distributed to disks
• Decide whether you want to integrate Active Directory Services
System Configuration
The configuration of the system is generally planned well in advance of the installation together
with the hardware vendor. Configuration planning involves deciding whether a central system or
standalone database system is to be installed, and how many dialog instances and frontends
are required.
The configuration is worked out with the hardware partner on the basis of sizing information that
reflects the system workload. Details such as the set of applications that are to be deployed, how
intensively these are to be used, and the number of users enable the hardware vendor to
recommend a configuration that performs well. To simplify the process of planning an appropriate
configuration, SAP provides a Quick Sizer tool that helps to determine the right combination of
resources such as CPU, disk space and memory.
Domain or Local Installation
One of the fundamental decisions that have to be made before the installation, is to decide
whether a domain or a local installation is to be performed. Depending on the type of
installation, different rights and privileges are necessary to permit the execution of the installation
steps. To perform a local installation, you need to be Local Administrator of the machine
involved. To perform a domain installation, you need to be Domain Administrator of the
domain involved, and all machines in the system must belong to the same domain. In a local
installation, all Windows NT account and user information is stored locally on one host and is not
visible to any other hosts in the system. In a domain installation, the user information is stored
centrally on the domain controller and is accessible to all hosts in the system.
If the SAP System is to run on a single machine, you can perform a local installation. If the
system is to be distributed across more than one machine SAP strongly recommends a domain
installation.
Performing a local installation for a distributed system leads to authorization
problems that have to be resolved.

16 July 2001
A domain installation requires an additional component called the NT primary domain controller
(PDC). This stores user account information centrally for the whole system and must therefore be
installed on one of the hosts in the domain. For performance and security reasons it must not be
located on a host where the central instance or database are running.
It is not advisable to run an SAP instance (including the database instance) on
the primary domain controller (PDC) or on the backup domain controllers (BDC).
Never perform a local installation on a domain controller.
For more information, see Granting User Rights for the Installation [Page 41].
Checking SAP Hardware and Software Requirements
SAP specifies minimal hardware and software requirements for different system configurations to
ensure that a newly installed system performs well. These requirements are summarized in
check lists that are available for a central system and a standalone database system.
In the planning stage, it is essential to look at the check lists to find out the requirements and to
make sure that they can be met.
For more information see, Hardware and Software Requirements Check [Page 17]
Distribution of Components to Disks
When you install the SAP System, the installation tools prompt you to enter drive letters for the
main components of the system. This gives you the opportunity to distribute components to disks
in the system as you wish. The way in which you do this significantly affects system throughput
and data security, and must therefore be carefully planned. The best distribution depends on
your specific environment and must take into consideration factors such as the size of the
components involved, security requirements and the expected workload.
When you work out the assignment of components to disks, you first need to get an overview of
the main components and their corresponding directories. Then, on the basis of sample
configurations and the recommendations provided in this documentation, you can decide which
assignment is best for your particular system.
SAP Systems are normally installed on RAID arrays that ensure data redundancy. This
documentation therefore focuses on RAID subsystems and drives.
Integration of Active Directory Services
Optionally, if a Windows 2000 Domain Controller is available on the network, you can decide to
integrate Active Directory Services for the SAP System. Integration of the services has the
advantage that the system can subsequently access and utilize a wide range of information
stored centrally in the directory. You must decide whether you want to use Active Directory in
advance of the installation because it influences the procedure. Both the directory and the SAP
System have to be prepared appropriately.
For details on how the system can benefit from and be prepared for Active Directory see
Integration of Active Directory Services [Page 45].

1.1 Hardware and Software Requirements Check
July 2001 17
Purpose
In the following sections you can find check lists that specify the software and hardware
requirements for different SAP system configurations. Use the check lists to ensure that you
install the correct software components and that your hardware is suitably sized.
Each system has individual hardware requirements that are influenced by the
number of concurrent users, the transaction load, and the amount of customer
data. The following lists can only give you a rough idea of the minimal
requirements for a new system without taking customer data into account. For a
more precise definition that reflects your particular system load, you can:
• Use the Quick Sizer tool that is available on the SAPNet. This prompts
you to enter information on your planned system and then works out the
requirements that have to be met to handle the load. To access the tool
enter the alias QUICKSIZING in the SAPNet.
• Contact a hardware vendor. The vendor analyses the load and works out
suitable hardware sizing.
The check lists are only valid for Release 4.6D.
Prerequisites
• Remote support
To get remote support, the remote connection specified in the contract agreement must be
available before installation. The internet address setup at SAP and registration are dealt
with during the installation.
• Hardware certification
You are only allowed to install an SAP System on certified hardware. iXOS R/3NTC certifies
hardware platforms for SAP on Microsoft Windows NT. iXOS certifies a specified release of
MS Windows NT. SAP customers can then run the SAP System on the respective platform
for all combinations of the SAP System and databases released by SAP for the specified
release of MS Windows NT.
For the list of certified platforms, see the internet address http:www.r3onnt.com.
Process Flow
1. You follow the relevant procedure to check the requirements on each machine where you
intend to install the SAP System:
a. To install the central instance and database, you check one of the following:
• Central system requirements
• Standalone database system requirements
b. To install the dialog instance, you check the dialog instance requirements.
2. You check the network requirements.

18 July 2001
1.1.1 Checking Requirements for a Central System
Use
For the installation of a central SAP System, make sure you meet the minimal requirements listed
in this section.
Prerequisites
You are installing a standard SAP System as a central system. That is, the central instance and
the Oracle database are on the same host machine.
Procedure
1. Ensure that the host machine meets the hardware requirements that enable the SAP system
to perform well. The following list gives you a rough idea of the requirements for a new
system with no customer data.
Hardware Requirement How to check
CD drive locally connected to host
running central instance
–
Tape drive for backups, either 4mm DAT
or DLT. Hardware compression is
recommended.
–
Disk space of 13 GB (not including virtual
memory) on at least 3 physically
separate disks
Choose Start → Programs →
Administrative Tools (Common) → Disk
Administrator.
RAM of 512 MB Choose Start → Programs →
Administrative Tools (Common) →
Windows NT Diagnostics.
Virtual memory of at least 4 times RAM.
Maximum required is 10GB.
a. Choose Start → Settings → Control
Panel → System.
b. Choose Performance.
c. If required, in section Virtual Memory,
choose Change.

July 2001 19
2. Check that the software on the host machine meets the following requirements:
Software Requirement How to check
Oracle version 8.1.6
Patch 8.1.6.1.1)
–
Windows NT Server Version 4.0, English
(international), service pack 6 or higher
a. Choose Start → Programs →
Command Prompt.
b. Enter the command winver
Microsoft Internet Explorer 4.0, service
pack 1
or
Microsoft Internet Explorer 5.0
In the Explorer, choose Help → About
Internet Explorer.
Windows NT Resource Kit is strongly
recommended to enable support
–
3. Check that the network configuration meets the requirements in Checking Requirements for
the Network [Page 24].
4. To prepare printers for use in the SAP System, check that they operate correctly at the
Windows NT level by using the Print Manager:
a. Choose Start → Settings → Printers to check the printer installation.
b. If you can print from a Windows application (for example, Notepad), the printer is
installed correctly.
For more information, see the Windows NT documentation.
Result
You have met the requirements for the machine where the central system is to be installed.

20 July 2001
1.1.2 Checking Requirements for a Standalone Database System
Use
For the installation of an SAP System with a standalone Oracle database, make sure you meet
the minimal requirements listed in this section.
Prerequisites
You are installing a standard SAP System with a standalone database. That is, the central
instance and the database are on different host machines.
Procedure
Checking the Host for the Central Instance
1. Check that the host machine meets the following hardware requirements:
–
recommended.
–
Disk space of 300 MB (not including
virtual memory)
Administrator.
Virtual memory of 4 times RAM.
Maximum required is 10GB.
Panel → System → Performance.
b. If required, in section Virtual Memory,
choose Change.

July 2001 21
Patch 8.1.6.1.1
–
Command Prompt.
Microsoft Internet Explorer 4.0, service
pack 1
or
Microsoft Internet Explorer 5.0
In the Explorer, choose Help → About
Internet Explorer.
–
Windows NT level using the Print Manager as follows:

22 July 2001
Checking the Host for the Database Instance
–
recommended.
–
Disk space of 13 GB (not including virtual
memory)
Administrator.
Virtual memory of 2 times RAM. a. Choose Start → Settings → Control
Panel → System.
b. Choose Performance.
c. If required, in section Virtual Memory,
choose Change.
Oracle version 8.1.6.
Patch 8.1.6.1.1
–
Command Prompt.
–
Checking the Network
Check that the network configuration meets the requirements in Checking Requirements for the
Network [Page 24].

July 2001 23
1.1.3 Checking Requirements for a Dialog Instance
Use
For the installation of a dialog instance, make sure you meet the minimal requirements listed in
this section.
Procedure
–
recommended.
–
Disk space of 250 MB (not including
virtual memory)
Administrator.
Virtual memory of 4 times RAM.
Maximum required is 10 GB.
Panel → System → Performance.
b. If required, in section Virtual Memory,
choose Change.
2. Check that the software on the host machine meets the following requirements
Patch 8.1.6.1.1
–
Command Prompt.
Internet Explorer 4.0, service pack 1
or
Internet Explorer 5.0
–
3. Check that the network configuration meets the requirements in Checking Requirements for
the Network [Page 24].

24 July 2001
Windows NT level using the Print Manager as follows:
Result
You have met the requirements for the machine where the dialog instance is to be installed.
1.1.4 Checking Requirements for the Network
Use
Be sure to meet the minimal requirements for the network of your SAP System installation listed
in this section.
Prerequisites
You have read the following documentation, available in SAPNet:
• Network Integration of R/3 Servers
• SAP Software in PC Networks (SAP Note 5324)
If you do not meet the requirements in this section, you might have problems or
be restricted when working with the SAP System.
Procedure
1. Check the configuration of the network on each host machine by choosing Start → Settings
→ Control Panel → Network.
2. Check whether the TCP/IP protocol is installed correctly. For more information, see the
Windows NT documentation.
3. Check whether the file C:WINNTSYSTEM32DRIVERSETCHOSTS is complete and up-to-
date. The notation used for the computer name in the file must be compatible with the
"TCP/IP Protocol" entries. Also, the file must contain the following entry:
127.0.0.1 localhost
4. Open a command prompt with Start → Programs → Command Prompt .

July 2001 25
5. Enter the following commands in the sequence specified. Use the output of each command
as the input for the next command:
Command Output
hostname Local host name
ping <hostname> The IP address of the local host
ping -a <IP_address> The host name of the local host
The name returned by the commands hostname and ping -a <IP_address> must be the
same, including upper and lowercase. If the output returned by the commands is consistent and
corresponds to the entries in the HOSTS file, the network connection is functioning properly.

1.2 Distribution of Components to Disks
26 July 2001
When you install a SAP System with an Oracle database, the main directories required for the
system are automatically created. However, during the installation procedure you have to
explicitly specify where these directories are to be located, that is, on which drives or disks they
must reside. The assignment of the directories to drives and corresponding disks fundamentally
affects the security and performance of the system and must therefore be carefully considered.
The following graphic gives you an overview of the main SAP System components and
directories, their purpose, and the amount of free space they initially require. A good distribution
of these to disks ensures that enough free space is available for system growth, the data is
secure and Performance is good.
R/3
usrsap
usrsaptrans
R/3 kernel and related files
R/3 transport directory
500 MB
ORANT Oracle DBMS software 600 MB
ORACLE<SAPSID>sapdata<1> R/3 data
R/3 data
ORACLE<SAPSID>origlogA Original online redo logs, set A
Original online redo logs, set B
200 MB
DBMS
DB Data
Redo Logs
sapdata<2>
"
"
Mirrored online redo logs, set A
"
Mirrored online redo logs, set B
"
origlogB
mirrlogA
mirrlogB
200 MB
200 MB
200 MB
ORACLE<SAPSID>saptrace
Oracle alert and trace files 20 MB
saparch Backup of online redo logs 5-6 GB
"
R/3 data
sapdata<3>
"
R/3 data
sapdata<4>
"
R/3 data
sapdata<5>
"
R/3 data
sapdata<6>
"
1150 KB
910 KB
1540 KB
1520 KB
970 KB
1020 KB
100 - 200 MB
Approx. Size

July 2001 27
SAP DBA
sapreorg Workingdirec
toryfor databaseadm
inistration
sapbac
kup B
RB
AC
KUP logsand B
RB
AC
K
UP default
direc
toryfor bac
kupstoharddisk
sapc
hec
k L
ogsfor sapdba-c
hec
k, -next -analyze
appr. 2 G
B
Directory Sizes
sapreorg and sapbackup
No definite initial size can be specified for the SAPDBA directories sapreorg
and sapbackup because they are normally only used when tablespaces have
to be reorganized. sapbackup is generally used for backup logs and online
backups that are made in preparation for a database reorganization. sapreorg
is used for the reorganization itself. If you have to reorganize the database, the
SAPDBA utility informs you how much space is necessary.
saparch
The space required for saparch can vary between 100 MB and 10 GB. It
depends on the workload and the archiving strategy you plan to implement. If the
archive logs are written directly from saparch to tape, this reduces the amount
of disk space required. If a backup is being executed and only one tape drive is
available, more free space is necessary. In this case, at least enough space must
be free to allow all the redo logs generated during the backup to be archived. If
the archive directory fills up, the backup stops. It only continues processing when
enough space for archiving logs is available again.
Sample Configurations
As SAP production systems are generally installed on RAID arrays, the following
focuses on the use of RAID technology.
The best way to assign the SAP System directories to RAID arrays depends on your specific
workload and individual performance and security requirements. There is no single solution or
any definite rules. To help you work out a good solution that suits your particular environment,
the following shows you some examples and gives recommendations that may be useful.
For a discussion of a basic distribution that provides adequate data security and performance in
an average size production system, see the example:
Standard Configuration [Page 29]

28 July 2001
For an illustration of a large configuration that provides a large degree of data redundancy and
benefits performance, see the example:
Large Configuration [Page 31]
For a distribution that is suitable for a small test or demo system, see the example:
Test System Configuration [Page 33]
General Recommendations
The following gives you information and recommendations that are valid for all systems.
• For security and performance reasons always distribute the following to different arrays:
− Original online redo logs
− Mirrored redo logs
− Archived redo logs
− Database data
• For performance reasons, do not install several database systems for different SAP Systems
on a single host.
• Use the standard naming conventions for the main directories to ensure trouble-free
database administration.
• Use RAID disk technology
− RAID 1 disk arrays are recommended for the original and mirrored redo logs. This
technology writes data to a primary disk and duplicates it on a second disk thus providing
a high level of data security.
− RAID 5 disk arrays are recommended for the database data and the archived redo logs.
This RAID level stripes the data over all the disks in the array and writes parity
information. The parity information enables data to be reconstructed if a single disk fails.
Changing Tablespace Sizes
When the directories for the database data are created, they are assigned to tablespaces that
have a predefined default size. If you have a large amount of data and are uncertain whether the
predefined tablespaces are big enough, you can increase their sizes before beginning the
installation. For more information about the tablespace sizes and how to proceed in order to
change them, see Changing Tablespace Sizes or Locations [Page 113]. System Components
and Directories.

July 2001 29
1.2.1 Standard Configuration
The following graphic illustrates how the main directories that are created during the installation
can be distributed to RAID arrays. The distribution is suitable for an average-sized production
system. Keep in mind that this is only an example and that no single solution is fitting for all
environments.
The configuration shown is suitable for the main host of a central system or the
database server of a standalone database system. The components in the box on
the left can be assigned to any of the arrays depicted. The transport directory
does not necessarily have to reside on the central instance host.
Distribution of Components to RAID Arrays
Archived Logs
Redo Logs Set B
Mirrored Redo Logs A
DB Data
Redo Logs Set A
Mirrored Redo Logs B
R/3 Kernel
R/3 Transport Directory
RDBMS Executables
SAPDBA Directories
RAID 5
RAID 1
RAID 1
RAID 5
Distribution of Directories to Arrays
Array 1 ORACLE<SAPSID>sapdata1
...
ORACLE<SAPSID>sapdata6
Array 2 ORACLE<SAPSID>origlogA
ORACLE<SAPSID>mirrlogB
usrsap
ORANT
Array 3 ORACLE<SAPSID>origlogB
ORACLE<SAPSID>mirrlogA
ORACLE<SAPSID>sapreorg
ORACLE<SAPSID>sapbackup
ORACLE<SAPSID>sapcheck
Array 4 ORACLE<SAPSID>saparch

30 July 2001
Comments
• Security of the Redo Logs
From a security point of view, the redo logs play a crucial role. They record all the changes
made to the database and thus provide the information that is necessary to recover a
database that has been damaged. It is therefore important that they are stored very securely
and are never lost together with the database data. By placing the redo logs on a different
array to the database data, you can ensure that they are not lost if the array with the
database data is severely damaged.
• Security of the Oracle Control files
The Oracle control files contain important information for the operation of the database, for
example, they store the structure of the data files and the SCN. They enable the database to
function properly and are essential to recover the database.
To ensure that the control files are not lost in the event of a disk failure, the R3SETUP tool
locates them in directories that always have to be placed on separate arrays or disks.
Altogether there are 3 control files that are all named cntrl<DB_SID>.dbf. After the
installation they are located in the following directories:
CONTROLFILE 1:
<DRIVE>:ORACLE<SAPSID>SAPDATA1cntrlcntrl<DB_SID>.dbf
CONTROLFILE 2:
<DRIVE>:ORACLE<SAPSID>origlogAcntrlcntrl<DB_SID>.dbf
CONTROLFILE 3:
<DRIVE>:ORACLE<SAPSID>saparch cntrlcntrl<DB_SID>.dbf
• Performance
Locating the first and second set of online redo logs (set A and B) on different RAID arrays
enables you to avoid I/O bottlenecks. When set A of the online redo logs is full, the system
immediately begins to read and archive these. As a consequence, there is a high level of
read activity. At the same time the online redo logs are switched to set B, thus resulting in
intensive write operations. To avoid simultaneous high read and write activity on the same
array, it is therefore advisable to locate set A and B of the redo logs on different arrays.
Further potential sources of I/O bottlenecks can be eliminated by placing the original redo
logs of set A and B on different arrays to their corresponding mirrored logs. Original and
mirrored redo logs are written in parallel, therefore if they are located on the same array this
results in a high level of write activity that has to be handled by the same controller. A
separation of original and mirrored logs distributes the write activity to two different arrays,
thus reducing the likelihood of I/O bottlenecks.
• RAID levels
The use of RAID 1 arrays for the original and mirrored redo logs provides a high degree of
data security combined with good performance. The data is written to a primary disk and
duplicated identically on a second disk. If one disk fails the data is still intact on the second
disk.
The use of RAID 5 for the database and archive logs ensures fault tolerance. The data is
striped over all the disks in the array together with parity information. If one disk fails, the
parity information is used to automatically reconstruct the data lost on the damaged disk.

July 2001 31
• Number of Raid Arrays
In the graphic above, three RAID 1 arrays are used for the redo logs to achieve optimal
performance and security. If you do not need the disk capacity offered by 3 arrays and can
accept a less optimal level of performance, it is also feasible to use a single array. In this
case a single RAID 1 array can be used for the original, online and archived redo logs.
1.2.2 Large Configuration
The following illustrates a good disk configuration for a large production system with a high
throughput. The main system directories are distributed across several RAID arrays in a manner
which ensures good performance and security, despite the large amount of data and heavy
workload.
The configuration shown is suitable for the database server of a standalone
database system, or the main host of a central system. The components
displayed in the box on the left can be distributed to any of the arrays depicted.
The transport directory does not necessarily have to reside on the central
instance or database host.
Distribution of System Components to RAID Arrays
Archived Redo Logs
Mirrored Redo Logs B
Mirrored Redo Logs A
Redo Logs Set B
DB Data
Redo Logs Set A
R/3 Kernel
R/3 Transport Directory
DBMS Software
SAPDBA Directories
DB Data RAID 1 or 5
RAID 5
RAID 1
RAID 1
RAID 1
RAID 1
RAID 5

32 July 2001
Distribution of Directories to Arrays
RAID Array Directories
Array 1 and 2 ORACLE<SAPSID>sapdata1
...
Array 3 ORACLE<SAPSID>origlogA
usrsaptrans
Array 4 ORACLE<SAPSID>origlogB
ORANT
Array 5 ORACLE<SAPSID>mirrlogA
Array 6 ORACLE<SAPSID>mirrlogB
usrsap
Array 7 ORACLE<SAPSID>saparch
Comments
The following recommendations are only relevant for large systems. An optimal distribution can
sometimes only be achieved once the system is running and additional information is available
about read and write activity on individual tables.
• Separating index and table data
In installations where a large amount of customer data is expected, storing index and data
tablespaces on separate arrays improves performance. Whenever an insert operation takes
place, generally both the data and the index tablespaces have to be modified. Consequently,
two write operations have to be executed simultaneously. It is advantageous if both
operations are not on the same array. Avoiding the double write operation at the same
location by separating indexes and data improves I/0 performance.
Ensuring that index and table data are separated during the installation is a complex task.
You have to manually edit the R3SETUP installation files that control the creation of the
tablespaces. In these files, index and data tablespaces are assigned to different SAP data
directories. By changing this assignment and subsequently, during the installation,
appropriately distributing the data directories to different arrays you can achieve index and
data separation.
Often it is sufficient to ensure that only particular index and data tablespaces containing
heavily accessed tables are distributed across different arrays.
Table data and index data can be distinguished as follows:
− Tablespaces with table data always end with D, for example, PSAPPOOLD.
− Tablespaces with index data always end with I, for example, PSAPPOOLI.

July 2001 33
−
• Alternative RAID levels for the SAP data directories
− RAID configurations, other than the one illustrated above, also provide good solutions for
the SAP data directories. One available option is a combination of RAID 1 and RAID 0,
also referred to as RAID 1/0. This solution could replace array 1 and 2 in the above
graphic. It provides maximum protection by mirroring the data (RAID 1) and also good
performance by striping the data across all drives (RAID 0).
Another option for the data directories is to use RAID 5, but to include one or more
additional RAID 1 arrays. RAID 1 offers significantly better write performance than RAID
5 and is therefore a good choice for heavily accessed tablespaces. To take advantage of
such a configuration, you have to place tablespaces with a high write load on the array
implementing RAID 1.
− To locate certain tablespaces on a particular array, you have to edit the R3SETUP files
that assign tablespaces to SAP data directories. In these files you need to assign critical
tablespaces with a high level of read and write activity to a particular SAP data directory.
Subsequently, during the installation, you have to ensure that this particular directory is
created on the RAID 1 array.
See also:
Changing Tablespace Sizes or Locations [Page 113]
1.2.3 Test System Configuration
The following illustrates a disk configuration for a small test or demo system. As security and
performance play a less crucial role in this type of system, many different configurations are
feasible. The following shows one of the possible options.
Use the illustrated configuration exclusively for test or demo systems with a final
database size of less than 10 GB. It is unsuitable for production systems because
it only minimally satisfies security and performance requirements.
Distribution of Components to Disks
Archived Log
Files
DB Data
DB Data
R/3 Kernel
DBMS Software
SAPDBA Directories
Mirrored Logs
Redo Logs

34 July 2001
Distribution of Directories to Disks
Disk 1 ORANT
ORACLE<SAPSID>origlogA
ORACLE<SAPSID>origlogB
Disk 2 ORACLE<SAPSID>mirrlogA
ORACLE<SAPSID>mirrlogB
usrsap
Disk 3 ORACLE<SAPSID>saparch
Comments
• The configuration ensures that no data can be lost, but the process for recovering a
damaged database is complicated and time-consuming.
• The redo logs and database files are located on the same disks. This means that a single
disk failure can result in the loss of both the redo logs and database data.
• The I/O-intensive redo logs are on the same disk volumes as the data files. This can impede
performance.
• An equally good alternative would be to simply place all components on a single RAID 5
array.

July 2001 35
1.2.4 SAP Directories
Definition
The following gives you some background information about the SAP directories that are created
during the installation. The base directories required for the SAP central instance are:
• usrsap, created on the central instance and contains general SAP software
• usrsaptrans, created on the transport host and contains SAP software for the
transport of objects between SAP Systems
Both these directories are global, that is, they are accessed by all hosts in the SAP System.
Therefore, they have names that follow the Universal Naming Convention (UNC).
The following explanation distinguishes between a global, local and database host.
The global host is the machine on which the R/3 central instance runs.
The local host, is the current machine on which an SAP instance is running.
The DB host is the machine on which the database server runs.
Use
Directory usrsap
The SAP software is stored in the directory usrsap and contains global and local (instance-
specific) data on a global host.
On local hosts, usrsap contains only instance-specific data and copies of the SAP
executables. The executables on the local host are replicated from those on the global host each
time the local instance is started.
The installation program creates the directory usrsap on the global host and shares it with
the names sapmnt and saploc. The same directory on the local host is shared as saploc.
Since SAP traces for the instance are created in the directory usrsap,
sufficient space must be available in this directory. Changes in SAP profiles can
also affect the disk space.
If you create the subdirectory ......SYS (global data) locally on application or
presentation servers, you have to distribute the software for the SAP System
manually when upgrading to a new SAP release. SAP does not provide support
in this case.
Directory usrsaptrans
In an SAP System landscape there must be a global directory, called usrsaptrans, for the
transport of objects between SAP Systems. This directory is created on one SAP instance host in
the SAP System landscape (the transport host). It must be accessible for every host on which an
SAP instance is installed and which belongs to this SAP System landscape. The path on every
host must be <SAPTRANSHOST>usrsaptrans.
If you want to use the Change and Transport System, additional space is required in directory
usrsaptrans. Since the required storage size differs depending on the transport volume,

36 July 2001
SAP cannot specify the required amount of free disk space. We recommend that you reserve 20
MB per user of the transport system, with a minimum of 200 MB.
SAP enables you to make a transport host known to the Domain Name Server for all Windows
NT systems. For more information, see Preparing SAP System Transport Host [Page 44].
Structure
The following diagrams show how the physical directory usrsap is shared, on the global host
and in a distributed installation. In either case, UNC names are used as follows:
• <SAPGLOBALHOST>sapmnt to access global directories
• <SAPLOCALHOST>saploc to access local instance-specific data
Directory Structure on the Global Host
Instance Directories
<SAPLOCALHOST>saploc
(UNC name)
log
Physical Directory
Structure
Global Directories
<SAPGLOBALHOST>sapmnt
(UNC name)
<instance name>
sap
usr
<SID>
opt
data
work
dbg
run
sys
global
profile
exe
refers to
refers to
This graphic shows the directory structure on the global host. The global data is stored in the
global directories on the global host. This data physically exists only once for each SAP System.
Other computers access the data using the UNC name, <SAPGLOBALHOST>sapmnt, where
SAPGLOBALHOST is replaced by the SAP System with the name of the global host. The global
host accesses its own instance-specific data using the UNC name
<SAPLOCALHOST>saploc. On the global host, the parameters SAPGLOBALHOST and
SAPLOCALHOST have the same value.

July 2001 37
Directory Structure of a Distributed Installation
<SAPLOCALHOST>saploc
(UNC name)
log
Access to local
instance directories
<SAPGLOBALHOST>sapmnt
(UNC name)
<instance name>
data
work
Distributed Instance
Distributed Instance
Central Instance
Central Instance
Access to
global directories
sap
usr
<SID>
sys
global
profile exe
sap
usr
<SID>
exe
This graphic shows how the central instance, which runs on the global host, interacts with a
distributed instance running on another computer. On a distributed instance host, the parameters
SAPGLOBALHOST and SAPLOCALHOST have different values. Distributed instances use
SAPGLOBALHOST to access global data on a separate host, that is, the global host with the
central instance.

2 Installation Preparations
2.1 Checking for Windows NT File System
38 July 2001
Purpose
Before you start the installation, you must prepare the operating system and the SAP System.
Prerequisites
You have finished the planning phase.
Only the English (International) version of Windows NT is supported.
Process Flow
1. You perform preparations for the operating system on hosts that are to be used with the SAP
System:
a. You check that Windows NT File System (NTFS) is being used [Page 38].
b. You check that the Windows NT domain structure is correct [Page 39].
c. You install Microsoft Management Console (MMC). [Page 39]
d. You install up-to-date dynamic link libraries (DLLs) [Page 40].
e. You adjust virtual memory [Page 40].
f. You reduce the size of the NT file cache [Page 41].
g. You grant user rights for the installation [Page 41].
2. You perform preparations for the SAP System:
a. You choose the SAP System name and the host name [Page 43].
b. You prepare the SAP System transport host [Page 44].
3. Optionally, you prepare for the integration of Active Directory [Page 45] and Installation of
Multiple Components on One Database (MCOD) [Page 49].
Result
You can now start the installation.
2.1 Checking for Windows NT File System
Use
This section describes how to check that you are using the Windows NT File System (NTFS) on
hosts where the SAP System and database are to be installed. NTFS supports full Windows NT
security and long file names.
You must use NTFS for an SAP System installation. Do not install the SAP
directories on an FAT partition.

2.2 Checking the Windows NT Domain Structure
July 2001 39
Procedure
1. Open the Windows NT Explorer.
2. Select the root directory.
3. Choose File → Properties.
4. Switch to the General tab to see the type of file system that is in use.
2.2 Checking the Windows NT Domain Structure
Use
This section describes how to check that all SAP System and database hosts are members of a
single Windows NT domain. We recommend this for all SAP System setups, whether standalone
central systems or distributed systems.
For performance and security reasons, no SAP instance (including the database
instance) should run on the primary domain controller (PDC) or on the backup
domain controllers (BDC).
Prerequisites
You are familiar with checking NT domain structures. See the Windows NT documentation if you
need more information.
Procedure
1. Check that all SAP System and database hosts are part of a single Windows NT domain.
2. If you want to use the Change and Transport System to move objects between different SAP
Systems (that is, SAP Systems with different <SAPSIDs>), check that all these systems are
either a member of one domain or members of different domains with a trust relationship
established between them. Only SAP application and database servers should be members
of this domain.
2.3 Installing Microsoft Management Console
Use
You must set up the following components on all hosts in the system where you intend to run an
SAP instance, so that the installation functions correctly:
• Internet Explorer version 4.01 or higher
• Active Directory Service Interfaces (ADSI)
• Microsoft Management Console (MMC)
The MMC lets you monitor and start or stop the SAP System and instances centrally, that is, from
a single location.
On a standalone database host, you do not have to install MMC and ADSI.

2.4 Installing Up-To-Date Dynamic Link Libraries
40 July 2001
Procedure
1. If necessary, install the Internet Explorer.
a. Insert the Presentation CD into the CD-ROM drive.
b. Switch to the directory <CD_DRIVE>:MS_IE5<processor><EN>
c. Start the program ie5setup.exe.
2. Install ADSI and MMC:
a. Insert the SAP Kernel CD into the CD-ROM drive.
b. Switch to the following directory:
• <CD_DRIVE>:NTI386MMC
• On DEC-ALPHA: <CD_DRIVE>:NTALPHAMMC
c. To install the Active Directory Services, start the program ads.exe.
d. To install the Microsoft Management Console 1.1, start the program immc.exe.
2.4 Installing Up-To-Date Dynamic Link Libraries
Use
You must install up-to-date dynamic link libraries (DLLs) on all hosts in the system where you
intend to run an SAP instance. This includes hosts where a standalone database or gateway
instance are to run. The DLLS are required for correct functioning of the SAP System.
Procedure
1. Insert the SAP Kernel CD in the CD-ROM drive.
2. Switch to the directory <CD_DRIVE>:NTI386NTPATCH
For ALPHA: <CD_DRIVE>:NTALPHANTPATCH
3. Start the program r3dllins.exe.
When the installation has finished, you are prompted to reboot the system to
activate the changes.
If your DLLs were already up-to-date before you started the r3dllins.exe
program, no new DLLs are installed and you are not prompted to reboot.

2.5 Adjusting Virtual Memory
July 2001 41
2.5 Adjusting Virtual Memory
Use
You must adjust virtual memory on all hosts in the system where you intend to run an SAP
instance.
Procedure
1. Choose Start →
→
→
→ Settings →
→
→
→ Control Panel →
→
→
→ System.
2. Make a note of the amount of RAM installed.
3. Choose Performance.
4. Choose Change to change the paging file size if required.
The size should be at least four times the RAM installed. More than 10 GB is not required.
On a host for a standalone database or a gateway instance, the paging file should be
approximately double the size of the RAM.
2.6 Reducing the Size of the NT File Cache
Use
You must reduce the size of the NT file cache on all hosts in the system where you intend to run
an SAP instance. This avoids conflicts between the NT file cache and SAP programs in memory.
If you do not reduce the cache size, this might cause SAP programs to be displaced from
memory.
Procedure
1. Choose Start → Settings → Control Panel →Network.
2. Choose Services.
3. From the list under Network Services, select Server.
4. Choose Properties.
The Server dialog box opens.
5. Under Optimization, select Maximize the throughput for Network Applications.
6. Choose OK to confirm.
The setting for the size of the NT cache has now been reduced.
7. Reboot your server to activate the new setting.

2.7 Granting User Rights for the Installation
42 July 2001
2.7 Granting User Rights for the Installation
Use
The installation of the SAP System and the R3SETUP tool is only possible with certain NT rights
and privileges that authorize the execution of the installation steps. Without these rights and
privileges any attempt to install the system aborts. Therefore, before you start the installation,
you have to ask the system administrator to grant you the necessary authorizations.
The rights you need depend on whether you intend to perform a domain or local installation. For
more information, see Domain or Local Installation. [Page 15]
For performance and security reasons, it is advisable not to run an SAP instance
(including the database instance) on the primary domain controller (PDC) or on
the backup domain controllers (BDC).
Never perform a local installation on a domain controller.
Procedure
Local Installation
To perform a local installation, you need to have Local Administration rights for the central
instance host.
Domain Installation
To perform a domain installation, you need to have Domain Administration rights. To obtain
these rights the system administrator must enter you as a member of the Domain Admins
group.
Domain Installation Without Domain Administration Rights
If, for any reason, you are unable to get domain administrator rights for the installation, you can
perform the installation as a user with local administrator rights. However, you first have to
prepare this user as follows:
1. Ask the current Domain Administrator to create a new global group called
SAP_SAPSID_GlobalAdmin and the following two user accounts.
− SAPServiceSAPSID (this is not required for Informix installations)
− sapsidadm
Be careful to enter SAPServiceSAPSID, sapsidadm and
SAP_SAPSID_GlobalAdmin exactly as specified observing upper and
lowercase. For example, for a system called PRD enter
SAPServicePRD and prdadm

2.8 Choosing the SAP System Name and the Host Name
July 2001 43
2. Once the accounts have been created:
− Assign the users SAPServiceSAPSID and sapsidadm to the newly created
group SAP_SAPSID_GlobalAdmin
− Assign the user sapsidadm to the group Domain Users.
Any user with local administrator rights can now perform a domain installation with R3SETUP
without being a member of the Domain admins group.
See also:
Performing a Domain Installation as Local Administrator [Page 127].
2.8 Choosing the SAP System Name and the Host Name
Use
You need to choose an SAP System name that identifies the whole system. This name has to be
entered for the variable SAPSID when you install the central instance. You also need to check
the host name for compatibility.
You cannot change the SAP System name after the installation.
Procedure
1. Choose a name for your SAP System, conforming to the following conventions:
− It must be unique within your network.
− It must consist of three alphanumeric characters, for example, C11.
− Only uppercase letters are allowed.
− The first character must be a letter, not a digit.
− Since the following names are reserved, you cannot assign them to your SAP System:
ADD, ALL, AND, ANY, ASC, AUX, B20, B30, BCO, BIN, COM, CON, DBA,
END, EPS, FAX, FOR, GID, INT, KEY, LOG, LPT, MAX, MIN, MON, NOT,
OFF, OMS, P30, PRN, PUT, RAW, ROW, SAP, SET, SGA, SHG, SID, UID,
VAR, TMP
2. Make sure that the host name of your system does not contain any special character such as
a hyphen or an underscore. In addition, the host name must not exceed 32 characters in
length. Otherwise, unpredictable problems might arise using the SAP System, especially
when using the Change and Transport System.

2.9 Preparing SAP System Transport Host
44 July 2001
2.9 Preparing SAP System Transport Host
Use
You need to prepare one host in the SAP System for the role of transport host. This host has the
function of controlling the import or export of files between the current SAP System and other
SAP Systems (for example, a test or development system).
The transport host uses the directory usrsaptrans to temporarily store files that have been
exported from one system and are waiting to be imported into another system. Depending on
your requirements, you can decide to use the central instance host, the dialog instance host, or
any other host as the transport host.
Procedure
1. Map the IP address of the transport host to the alias SAPTRANSHOST using one of the
following methods:
− On the DNS server
If a DNS server is available for your system, ask your administrator to map the IP
address of the transport host to the alias SAPTRANSHOST.
The DNS server is a database that contains a set of files with information about the
TCP/IP network, including the mapping of host names or aliases to IP addresses.
− In the hosts files
If no DNS server is available, you can map the IP address to the alias SAPTRANSHOST
in the hosts file. This is located in the Windows NT default directory:
Drive:WINNTsystem32driversetc
Open the hosts file with an editor and add the line:
IP_address hostname SAPTRANSHOST
The result of this step is to assign the alias SAPTRANSHOST to the transport host.
Copy the newly edited hosts file to all hosts where an SAP instance is to run.
If the transport host has more than one network card, take special care when you
determine the IP address that is entered in the hosts file or on the DNS Server.
Make sure you enter the main IP address and that the binding order is correctly
defined. To check the binding order choose:
Start → Settings → Control Panel → Network → Bindings
2. If your transport host is not the central instance host, you have to create the transport
directory as follows:
a. On the transport host, create the directory usrsaptrans.
b. Grant Everyone the permission Full Control for the directory.

2.10 Integration of Active Directory Services
July 2001 45
These permissions are only necessary during the course of the R3SETUP
installation. After the installation, only the SAP_SID_GloabalAdmin groups of
all the systems that are part of your transport infrastructure must be granted Full
Control on the directory. R3SETUP assigns the appropriate rights with the help of
an additional SAP_LocalAdmin group. For more information, see Automatic
Creation of Accounts and Groups [Page 124].
c. If no SAP instance is to be installed on the transport host, you have to share the directory
usrsap on the transport host as SAPMNT. This enables R3SETUP to address the
transport directory in the standard way as SAPTRANSHOSTSAPMNTtrans.
Result
You have configured your system so that the installation tool R3SETUP can recognize the
transport host.
Purpose
The Active Directory is a Windows 2000 feature that allows important information within a
corporate network to be stored centrally on a server where it can easily be accessed and
administered. Storing information at one central location for the entire network has the advantage
that data only has to be maintained once and will therefore not be redundant or inconsistent.
If an Active directory is available in the corporate network, the SAP System can be configured to
take advantage of it. An appropriately configured SAP system can read information from the
directory and also store information there.
The following explains how SAP Systems can benefit from using the Active Directory and also
gives an overview of steps the that are necessary to configure the system for the use of the
directory.
The SAP System is able to interact with the Active directory on the basis of the
LDAP protocol. This defines how communication between the SAP System and
the directory is conducted and how data in the directory is structured, accessed or
modified. If directory types other than the Active Directory also support the LDAP
protocol, the SAP System can take advantage of the information stored there. For
example, if there is an LDAP directory on a Unix or NT machine, the SAP System
can be configured so that it can use the information available there. In the
following, directories other than the Active directory that implement the LDAP
protocol are referred to as generic LDAP directories.
In the SAP environment, the information stored in an Active Directory or Generic LDAP directory
can be exploited by:
• The Microsoft Management Console (MMC)
• The LDAP Connector
• SAP Logon (planned for the future)

46 July 2001
The MMC
The MMC is a graphical user interface for administering and monitoring SAP Systems from a
central location. It presents and analyses system information that is gathered from various
sources, including the Active Directory if the SAP System has been prepared appropriately.
When the Active Directory is integrated as a source of information this has advantages for the
MMC. It can read system information straight from the directory which automatically registers
changes to the system landscape. As a result, up-to-date information about all SAP application
servers, their status and parameter settings is always available in the MMC.
The use of the MMC in combination with Active Directory services is particularly recommended
for the administration of distributed systems. For example, in a distributed environment that
implements the Workplace with the mySAP.com components BW, B2B. APO and CRM, this
simplifies administration. It is possible to keep track of significant events in all of the systems
from a single MMC interface. Changes within the system configuration do not have to be
registered manually, they are automatically updated in the directory and subsequently reflected in
the MMC.
The LDAP Connector
The LDAP Connector is an ABAP interface to the Active Directory that enables SAP applications
to access and utilize information stored in the directory. For example, the LDAP Connector
enables the SAP Office application to fill and update its address book data simply by reading
information from the directory. The Connector can be used by SAP applications, but also by
customers that wish to develop enhancements for applications that integrate Active Directory
Services.
Before the LDAP Connector can be used, it has to be installed as described in the SAPNet- R/3
Frontend Note 188371.
The SAP Logon
In future, the configuration of the SAP Logon dialog box will be simplified with the help of the
Active Directory. At present, after the SAP installation, the SAP logon for each frontend has to be
manually configured by entering technical details on available systems. A planned SAP feature
will be able to automatically configure the logon for systems that integrate Active Directory
services.
Prerequisites
The SAP System can only be configured for Active Directory services or other LDAP directories if
these are already available on the network. The Active directory is part of a Windows 2000
installation and is automatically available on all Domain Controllers. A Generic LDAP directory is
an additional component that has to be installed separately on a Unix or Windows NT Server.
Process Flow
Active Directory
To enable an SAP System to make use of the features offered by the Active directory, both the
Active directory and the SAP System have to be configured.
• In a first step, the Active Directory has to be prepared so that it can store SAP data. This
involves extending the schema for the SAP data types, creating a root container for the
storage of SAP-specific information and defining accounts that allow directory access. These
tasks are all performed with the help of the R3SETUP tool which offers the option Configure
Active directory for SAP.

July 2001 47
For more information see Preparing the Active Directory for SAP [Page 47]
• In a second step, the SAP System has to be configured to enable interaction with the Active
Directory. This is done during the installation of the SAP central instance with the help of the
R3SETUP tool. The R3SETUP tool prompts for information related to the Active Directory
and then configures the system correspondingly.
For information on R3SETUP prompts that have to be answered for the Active Directory
configuration see Input for a Central System Installation [Page 61].
Generic LDAP Directories
The process of preparing the SAP System for the use of generic LDAP services involves a
number of manual steps. Again, both the LDAP directory and the SAP System must be
configured appropriately:
• The LDAP directory has to be prepared so that it can store SAP data. This involves
extending the directory schema and creating a container for the SAP data.
• The SAP System has to be configured to enable interaction with the LDAP directory. The
configuration steps are performed by the R3SETUP tool during the installation of the SAP
central instance. R3SETUP is able to configure the system correctly on the basis of
information related to the directory that has to be entered before the installation procedure
begins. For details on LDAP-related input for R3SETUP see Input for a Central System
Installation [Page 61]
• A user with a password has to be set up on the machine where the SAP System is running to
permit the system to access and modify the LDAP directory. This is done by running the
script ldappasswd.
For detailed instructions on how to enable interaction between a generic LDAP directory and the
SAP System, refer to the documentation available in the SAPNet under:
Solutions → mySAP.com Technology → System Management → Directory Access Services.
2.10.1 Preparing the Active Directory for SAP
Use
The SAP System can only store and access data in the Active Directory, if the directory has been
prepared appropriately. To prepare the directory, you use the R3SETUP tool which automatically
performs the following tasks:
• Extends the Active Directory schema to include the SAP-specific data types.
• Creates domain accounts that are a prerequisite for enabling the SAP System to access and
modify the Active Directory. These are the group SAP_LDAP and the user sapldap.
• Creates the root container where information related to SAP is stored.
• Regulates access to the container for SAP data by giving members of the SAP_LDAP group
permission to read and write to the directory.

48 July 2001
Prerequisites
A Windows 2000 Domain Controller with an Active Directory must be installed on the network.
Procedure
Installing R3SETUP
Use the R3SETUP tool to prepare the Active Directory for the SAP System. In a first step, you
install the R3SETUP tool on the domain controller where the Active Directory is located.
1. Log on to the Domain Controller as domain administrator.
2. Make sure that the TEMP environment variable has been set.
To check the variable, choose Start → Settings → Control Panel → System. On the
Environment tab, look under User Variables. TEMP is normally set to C:temp. Make sure
that the specified directory really exists in your file system.
3. Insert the Kernel CD-ROM.
4. Start the program R3SETUP.BAT from the directory
CD_DRIVE:NTCOMMON
The R3SETUP window opens.
5. When you are prompted, enter the following:
− The name of your SAP System SAPSID
− The directory on your hard disk that the R3SETUP files are to be copied to. The default
directory is DRIVE:USERSSAPSIDADMINSTALL
When you have made all the required entries, R3SETUP is automatically installed.
6. Enter Yes when a dialog box appears prompting you to log off or reboot.
R3SETUP now automatically logs off or reboots.
Configuring the Active Directory
1. Log on as the same user that installed the R3SETUP tool.
2. From the NT Start menu choose, Start → Programs → SAP System Setup for SAPSID →
Configure Active Directory for SAP.
3. When you are prompted:
− Confirm the name of the domain where the SAP_LDAP group is to be created. This is the
domain that you are logged on to.
− Enter the password for the sapldap user.
When you have made these entries, R3SETUP automatically configures the Active Directory.

2.11 Installation of Multiple Components on One Database
July 2001 49
2.11 Installation of Multiple Components on One
Database
Use
You can install multiple SAP Systems in a single database. This is called Multiple Components
on One Database (MCOD).
You install an SAP R/3 central instance and an SAP CRM central instance in a
single database.
MCOD is scheduled to be available with all mySAP.com components. We are releasing this
technology on all the major databases for the SAP System, in line with our commitment to deliver
platform-independent solutions.
Using this technology is as easy as installing a separate component. No extra effort is required
because the MCOD installation is fully integrated into the standard installation procedure.
For more information on released platforms and availability, see
http://service.sap.com/platforms.
Choose Platform Availability for mySAP.com → Multiple Components on One Database (MCOD).
Prerequisites
• SAP R/3 customers need to upgrade to mySAP.com (including the latest SAP R/3 4.6C
component) or SAP R/3 Enterprise.
• Improved sizing required
In general, you calculate the CPU usage for an MCOD database by adding up the CPU
usage for each individual SAP System. The same applies to memory resources and disk
space.
You can size multiple components on one database by sizing each individual component
using the SAP Quick Sizer and then adding the requirements together. For more information
on the SAP Quick Sizer, see http://service.sap.com/quicksizer.
Features
We strongly recommend you to test MCOD in a test or development system.
We recommend running MCOD systems in the same context. We do not
recommend you to mix test, development, and productive systems in the same
MCOD.
• Reduced administration effort
• Consistent system landscape for backup, system copy, administration, and recovery
• Increased security and reduced database failure for multiple SAP Systems due to monitoring
and administration of only one database
• In an MCOD landscape you can upgrade a single component independently from the other
components running in the same database, assuming that the upgraded component runs on

2.11 Installation of Multiple Components on One Database
50 July 2001
the same database version. However, if you need to restore a backup, be aware that all other
components are also affected.
• Special MCOD considerations and differences from the standard procedure are listed where
relevant in the installation documentation.
Constraints
• In the event of database failure, all SAP Systems running on the single database are
affected.
• There are no automatic procedures and no tool support in an MCOD landscape for the
following administrative tasks:
Copying a single component from an MCOD landscape to another database
De-installing a single component from an MCOD landscape
We intend to support these tasks in the future. In the meantime, you can request support via
SAPNet - R/3 Frontend.

3 The SAP System Installation
July 2001 51
Purpose
Once you have planned and prepared the installation, you can begin with the actual installation
steps. In this core part of the installation process, you set up the main components that enable
the operation of an SAP System. These are:
• The central instance
• The database instance
• The SAP frontends
• If required, one or more dialog instances
• If required, a standalone gateway instance
Two fundamentally different approaches are possible:
• You can install a central system
In this type of configuration you locate the SAP central system and database on a single
host.
• You can install a standalone database system
In this type of configuration you install SAP central instance on one host and the database
server on a second host.
Which of these two approaches is best for your environment depends on various factors such as
the type of applications you intend to deploy, the size of the anticipated workload and the number
of expected concurrent users. The most commonly implemented configuration for an average-
size system is a central system. A standalone database system is usually implemented for larger
systems with a high throughput.
In a standalone database system, the database can be installed on a UNIX host.
The installation procedure is the same as for a normal system on NT hosts, but
the database has to be installed according to the instructions given in the
documentation R/3 Installation on UNIX.
Prerequisites
In a sizing phase, well in advance of the actual installation procedure, you have decided whether
a central system or standalone database system best meets your business requirements.
Process Flow
The installation of the SAP System comprises several steps. Essentially, various components
have to be installed on the different hosts in the system according to a predefined sequence and
using the installation tools provided. To get a clear picture of what has to be done, it is useful to
get an overview of the different hosts involved and which components have to be installed on
each host. The following table gives you an overview. It distinguishes between a central and
standalone database system configuration and shows:
• The hosts that make up the system

52 July 2001
• The components that have to installed on each host
• The sequence in which the components have to be installed
• The tool that must be used to install the various components
Central System Installation
Host Components to Install Tool
Central instance host 1. Database server software
2. R3SETUP tool
3. Central and database
instance
1. Oracle Installer
2. File R3SETUP.BAT
3. R3SETUP
Dialog instance hosts
(optional)
1. Database client software
2. R3SETUP tool
3. Dialog instance
1. Oracle Installer
2. File R3SETUP.BAT
3. R3SETUP
Frontend machines SAP frontends
For more information, see Central System Installation [Page 53].
Standalone Database System Installation
Host Component to Install Tool
Central instance host 1. Database client software
2. R3SETUP tool
3. Central instance
1. Oracle Installer
2. File R3SETUP.BAT
3. R3SETUP
Database server host 1. Database server software
2. R3SETUP tool
3. Database instance
1. Oracle Installer
2. File R3SETUP.BAT
3. R3SETUP
Dialog instance hosts
(optional)
1. Database client software
2. R3SETUP tool
3. Dialog instance
1. Oracle Installer
2. File R3SETUP.BAT
3. R3SETUP
Frontend machines SAP frontends
For more information, see Standalone Database System Installation [Page 66].

3.1 Central System Installation
July 2001 53
Purpose
When a small to medium-sized SAP System is set up, the core parts of the system, namely the
central instance and database, are generally installed on a single machine.
Process Flow
The following graphic illustrates the actions required to install the central and database instance
on a single machine.
Install
R/3SETUP
2
2
Database
Server
Run R/3SETUP to Install
Central and Database Instance
3
3
Install
DB Server Software
1
1
3.1.1 Installing the Oracle 8.1.6 Database Software
Use
The server software and patch 8.0.6.1.1 must be installed on the host where the database runs.
Prerequisites
600 MB free space must be available for the server software.
Procedure
1. Make sure you are logged on as a user with administrator rights.
2. Insert the Oracle DBMS CD into the CD-ROM drive and switch to the directory:
CD_DRIVE:NTI386INSTALLWIN32
3. Choose the file SETUP.EXE to start the Oracle installation program.
The Oracle Universal Installer guides you through the process in a series of screens and
prompts you to make the following entries:

54 July 2001
Window Entry
1. File Locations Under Source:
The path to the Oracle source software is displayed. Do
not change the path.
Under Destination:
For Name
enter the name of the Oracle Home directory. SAP
recommends the name SAPSIDORACLE_VERSION,
for example, C11816
You must specify a new Oracle home.
For Path
enter the path of the Oracle Home directory. SAP
recommends:
DRIVE:ORACLESAPSIDORA_VERS, for example,
C:ORACLEC11816
2. Available
Products
Select Oracle8i Enterprise Edition 8.1.6.0.0
3. Installation
Types
Select Minimal.
4. Upgrading or
Migrating an
Existing
Database
Appears only if there is an other configured oracle
database instance on the host;
Choose Do not upgrade or migrate an existing DB

July 2001 55
Window Entry
5. Select Starter
Database
Choose No, if the window appears.
6. Summary View the information displayed on the screen and then
choose Install.
7. Install No entries are required. The Oracle 8.1.6 software is
installed and the Net8 Configuration Assistant is started
in the background.
8. Net8
Configuration
Assistant
Select Perform typical configuration.
9. Oracle
Universal
Installer: End of
Installation
Choose Exit to close the Installer.
Installing Oracle Patch 8.1.6.1.1
1. Make sure the Oracle RDBMS CD is in the CD Drive and switch to the directory:
CD_DRIVE:NTI386Patches8.1.6.1.1
2. To start the Oracle Universal Installer, double-click the file setup.exe.
The installer opens and guides you through the patch installation process in a series of
windows.
Window Entry
2. File Locations Under Source:
The path to the Oracle source software is
displayed. Do not change the path.
Under Destination:
Name
From the dropdown box, select the name of Oracle
Home for 8.1.6.
Path
Make sure that the path of the Oracle 8.1.6 Home
directory is displayed and then choose Next.
3. Summary: Oracle 8i
Patch Set 8.1.6.1.1
View the information displayed on the screen about
the patch set and then choose Install.
4. Install No entries are required. The patch is installed and
the progress is indicated with a progress bar.

56 July 2001
3.1.2 Installing R3SETUP
Use
The R3SETUP tool can only be used for the installation of an SAP component on a specific host
if it is available locally on that host. You must therefore make sure that R3SETUP is installed
locally on the host before you install a central, database, dialog, or gateway instance.
Prerequisites
• 50 MB free space must be available on the drive where the R3SETUP files are to be
installed. By default, R3SETUP is copied to the directory:
DRIVE:USERSSAPSIDADMINSTALL
• To install R3SETUP, you need certain NT rights and privileges. These differ, depending on
whether a domain or local installation is to be performed:
− For a domain installation, you need Domain Administration Rights and you must
therefore be a member of the Domain Admins group.
If you cannot acquire domain administration rights, you can also install R3SETUP with
local administrator rights, but you have to carry out a number of steps to prepare the user
involved. This includes creating the group SAP_SAPSID_GlobalAdmin, with the two
domain user accounts SapServiceSAPSID (this user is not created for Informix
installations) and sapsidadm.
− For a local installation, log on as a user with Local Administration Rights.
For details, see Granting User Rights for the Installation [Page 41]

Sap basis installation on win nt oracle 4.6d

Sap basis installation on win nt oracle 4.6d

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Similar to Sap basis installation on win nt oracle 4.6d

Similar to Sap basis installation on win nt oracle 4.6d (20)

Recently uploaded

Recently uploaded (20)

Sap basis installation on win nt oracle 4.6d