Runing Oracle Database On The Sun Storage 7210 - Sap - Erp

Running SAP ERP 6.
0 With
Oracle® Database on the
Sun™ Storage 7210 Unified
Storage System
Ulrich Conrad
July 2009
This article was published by BigAdmin at:

http://www.sun.com/bigadmin/features/articles/7000_sap_erp.jsp
To keep track of the latest content published by BigAdmin, subscribe
to the BigAdmin newsletter: http://www.sun.com/bigadmin/newsletter/.
BigAdmin Portal for Sun System Administrators Sun Microsystems, Inc.
Copyright © 2009 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights
reserved.
U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc.
standard license agreement and applicable provisions of the FAR and its supplements. Use is subject to license
terms. This distribution may include materials developed by third parties.
Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX
is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd.
X/Open is a registered trademark of X/Open Company, Ltd.
AMD, Opteron, the AMD logo, the AMD Opteron logo are trademarks or registered trademarks of Advanced
Micro Device.
ORACLE is a registered trademark of Oracle Corporation.

Sun, Sun Microsystems, the Sun logo, J2EE, J2SE, Java, Java runtime environment, JDK, JRE, Solaris, Sun
BluePrints, Sun Fire, and SunSolve are trademarks or registered trademarks of Sun Microsystems, Inc. or its
subsidiaries in the United States and other countries.
This product is covered and controlled by U.S. Export Control laws and may be subject to the export or import
laws in other countries. Nuclear, missile, chemical biological weapons or nuclear maritime end uses or end users,
whether direct or indirect, are strictly prohibited. Export or reexport to countries subject to U.S. embargo or to
entities identified on U.S. export exclusion lists, including, but not limited to, the denied persons and specially
designated nationals lists is strictly prohibited.
DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,

REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE
EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
Running SAP ERP 6.0 With Oracle Database on the Sun Storage 7210 Unified Storage System
BigAdmin Portal for Sun System Administrators Sun Microsystems, Inc.
Table of Contents
Revision History..................................................................................................................................................... 1
Summary............................................................................................................................................................... 2
Introduction........................................................................................................................................................... 3
Hardware and Software Components....................................................................................................................... 4

SAP Host..................................................................................................................................................... 4
Sun Storage 7210 Unified Storage System...................................................................................................... 4
Scope and Limitations............................................................................................................................................. 5
Audience............................................................................................................................................................... 5
Preparing the Server and 7210 Unified Storage System.............................................................................................. 6

Software...................................................................................................................................................... 6
Creating and Sharing Volumes on 7210 Unified Storage System....................................................................... 7
Preparing the Server..................................................................................................................................... 9
Installing the SAP ERP SR3 Software....................................................................................................................... 14

Setting Up the Environment for the Installation............................................................................................ 14
Sequence of Steps...................................................................................................................................... 14
Appendix............................................................................................................................................................. 47
SAPinst: Advanced Database Configuration................................................................................................... 47
Glossary............................................................................................................................................................... 52
Acknowledgements............................................................................................................................................... 53
For More Information............................................................................................................................................ 53
Licensing Information........................................................................................................................................... 54
Running SAP ERP 6.0 With Oracle Database on the Sun Storage 7210 Unified Storage System
1 Revision History Sun Microsystems, Inc.
Revision History
Revision Notes Date
0.1 Draft for Revision 14.11.2008
1.0 First Version 20.11.2008
1.0 Submitted to BigAdmin 04.03.2009
v8 Query on vendor review 6.23.2009
Using SAP ERP 6.0 With Oracle Database and Volumes on the Sun Storage 7210 Unified Storage System
2 Summary Sun Microsystems, Inc.
Summary
This document describes the steps to implement an SAP ERP 6.0 application on the Solaris™ 10 Operating System for x64 platforms
with Oracle® as the database platform and volumes on a Sun™ Storage 7210 Unified Storage System (hereafter called 7210 Unified
Storage System) that are mounted via NFS.
3 Introduction Sun Microsystems, Inc.
Introduction
SAP develops software for electronic management, execution, and analysis of business processes; its software portfolio covers a
broad range of business branches and types. The basis of the SAP software stack is SAP NetWeaver, a web application server with a
database. This SAP software stack can be installed on all popular operating systems and supports a variety of RDBMS software. On
top of SAP NetWeaver, an SAP application, such as ERP, CRM, and so on, can be installed.
This guide describes the implementation of SAP NetWeaver and SAP ERP 6.0 on the Solaris 10 OS with an Oracle database. The
procedure for the installation of the SAP and Oracle software has the following characteristics:
● Installation source: The installation was performed using DVD and CD images on local disk storage.
● Installation target: While the binaries and configuration files of the Oracle and SAP software are installed on the root disk,
extra volumes are mounted via NFS for the data files and for the log files of the Oracle database.
● The SAP system has the following following properties:
● The SAP System ID (SID) is VWS.
● The SAP system contains an ABAP and a Java™ instance.
● The number of the central instance is 01.
● The number of the SCS instance is 00.
● The user home directories are located in /export/home.
● The SAPinst custom installation mode is used.
● The default setting for the distribution of tablespaces of the Oracle database across subdirectories is applied:
● The data files of the database are distributed across four sapdata<N> directories. The initial size of these
directories after the installation is between 21 and 24 Gbyte.
● The database has two mirrored pairs of online redo logs.
● The database has three control files in the directories origlogA/B and in sapdata1.
● The control files are 50 Mbyte in size.
4 Hardware and Software Components Sun Microsystems, Inc.
Hardware and Software Components

This section describes the hardware and software components used for the procedures described in this paper.
SAP Host
Server Hardware
Sun Fire™ X4200 M2 server with:
● 2x AMD Opteron™ 252 processor, 2.59 GHz
● 8 Gbyte RAM
Software
● Solaris 10 5/08 OS (s10x_u5wos_10 X86)
Sun Storage 7210 Unified Storage System

● 2x AMD64 Opteron quad-core CPU, 2.14 GHz
● 32 Gbyte RAM
● Sun Storage 7000 Series software update version 2008.10 (2008.Q4)
● One ZFS storage pool with a mirrored capacity of 4.6 Tbyte was created from 42x 250-Gbyte SATA disks on the appliance
and used for the tests described in this paper.
● One 17-Gbyte SSD drive served as the Logzilla device of the NAS appliance. It is not recommended to perform the
installation of the SAP software without such a disk dedicated to caching purposes.
5 Scope and Limitations Sun Microsystems, Inc.
Scope and Limitations

This paper focuses on the steps to prepare a server running the Solaris 10 OS for x64 platforms and a 7210 Unified Storage System
for the installation the SAP software. A simple file system layout was chosen to keep the environment small, which might not satisfy
requirements regarding data protection for productive systems.
SAP AG regularly updates information on best practices, installation procedures, and supported configurations in SAP Notes. This
document reflects the relevant SAP Notes at the end of September 2008 for performing the procedures described in this paper. It is
recommended to check whether the SAP Notes mentioned herein have been updated and whether new SAP Notes about the SAP
software installation have been published in the meantime. This document should not be considered a replacement for consulting
relevant SAP Notes.
Audience
This paper is intended for readers with technical focus who have experience with:
● The Solaris 10 OS
● The Oracle RDBMS
6 Preparing the Server and 7210 Unified Storage System Sun Microsystems, Inc.
Preparing the Server and 7210 Unified Storage System

This section describes the steps that need to be performed on the 7210 Unified Storage System and on the server where the SAP
software is installed.
Software
Operating System
The operating system for the installation of an SAP central instance must be 64-bit.
SAP Installation Packages

The installation media for SAP software are available for download on SAP's Service Marketplace (http://service.sap.com).
The SAP Support Portal contains a link called Software Download, which leads to the SAP Software Distribution Center where the
collection of media for the desired software in compressed state can be selected for download.
To access the SAP Software Distribution Center, a login is required. The selected software media is put into a Download Basket and
cannot be downloaded directly from there; instead, the SAP Download Manager program must be used for this purpose. This
program must be downloaded, installed, and configured for Internet access first; then it connects to the SAP download web site
and downloads the selected items that are in the Download Basket.
The following SAP software is needed for the installation of SAP ERP 6.0:
● SAP Business Suite 2005 Installation Master for SAP NetWeaver 7.0 SR3; SAP ERP 6.0 SR3; SAP SRM 5.0 SR3; SAP SCM 5.0
SR3; SAP CRM 5.0 SR3 (51033511; size: 143 Mbyte) This contains the sapinst executable that launches the installation.
● SAP NetWeaver 7.0 SR3: Java based Software Components (51033513; size: 3.3 Gbyte)
● SAP ERP 6.0 SR3: Installation Export (51033500_1; size: 3.8 Gbyte and 51033500_2; size: 2.4 Gbyte)
● SAP NetWeaver 7.0 SR3: Kernel 7.00, Solaris on x64 64-bit (51033509; size: 216 Mbyte)
Additionally, the following media of the Oracle software are needed:
● Oracle 10.2 64-bit RDBMS: Solaris on x64 64-bit (51031947)
● Oracle 10.2 64-bit Client: Solaris on x64 64-bit (51032881; size: 34 Mbyte)
Oracle Patches
For Oracle 10.2.0 on the Solaris 10 OS for x64 platforms, the Oracle Patch set 10.2.0.2 is available and has been approved by SAP for
use with the SAP software. This patch set can be downloaded from the SAP web site. It comes as a zip file that must be extracted
and that contains a runInstaller executable for the installation. The Oracle patch set for a given operating system version that
is currently recommended by SAP can be found in SAP Note 871735.
Additionally, it is recommended to apply a number of Oracle patches. The list of Oracle patches is subject to change. For the
installation described herein, SAP Note 871096 in the version from 18.08.2008 was used to determine the required patches for
Oracle 10.2. All patches are available for download on the SAP Service Marketplace. Oracle patches are applied by using one of the
following executables:
● OPatch. With this executable, each Oracle patch is installed individually and separately. The user must take care that
the order of the patches to be applied is correct.
● MOPatch. This executable evaluates the patch level of the current Oracle installation and applies the required packages
in the correct order automatically. MOPatch requires the OPatch executable. SAP Note 1027012 describes the use and
the capabilities of this tool. MOPatch was used to apply the Oracle patches for the installation of the present SAP system.
Java Software
The SAP installation requires 64-bit Java 2 Platform, Standard Edition (J2SE™) version 1.4.2 (SAP Note 941595). The official download
site (http://java.sun.com/products/archive) offers only 32-bit Java software versions; the 64-bit Java software can be
obtained from http://java.sun.com/j2se/1.4.2/SAPsite/download.html.
According to a recommendation of SAP Note 716604, the J2SDK/JRE™ software version 1.4.2_13 was selected for download. The
following software packages were downloaded and used for this SAP installation:
● j2sdk-1.4.2_13-solaris-i586.sh (the 32-bit version)
● j2sdk-1.4.2_13-solaris-amd64.sh (the 64-bit version)
The Java Cryptography Extension 1.4.2 can be obtained from http://java.sun.com/j2se/1.4.2/download.html.
unrar
Most of the SAP software on the SAP Software Distribution Center is available in .rar format.
unrar is needed to decompress these files. The version of unrar used for preparing the installation was 3.10.
Creating and Sharing Volumes on 7210 Unified Storage System

The disk space requirements for the Oracle database of an SAP installation are given in SAP Note 1094599. For the ERP Central
Component, SAP ERP 6.0, an initial size of 84 Gbyte disk capacity, distributed across four directories, is needed for the database.
The 7210 Unified Storage System (NAS appliance) is configured and managed via a web-based GUI, which is accessible via
https://<IP_Address_of_NASAppliance>:215.
The preparation of the 7210 Unified Storage System comprises two steps:
● Creation of a project
● Creation of two volumes, one for Oracle data files and one for Oracle log files
Creating a Project
File systems on a NAS appliance are created as part of a project. A project is the topmost level in a hierarchy of storage objects that
depend on each other: Project — File System — Snapshot — Clone. On project level, settings on three configuration pages are
defined, which can be inherited by child objects. For the SAP installation, a new project was created by clicking Add in the left pane
of the screen under Projects.
Figure 1. Sun Storage 7210 Management GUI: Projects Page
This opens a dialog window:
Figure 2. Sun Storage 7210 Management GUI: Project Creation
The default settings of the new project are kept, except for the NFS protocol, where the server hosting the SAP application is
granted root access privileges to the shared volume. This ensures that both volumes that are created under this project inherit this
setting automatically.
Figure 3. Sun Storage 7210 Management GUI: Common Protocol Settings of the Project
Creating Volumes
Volumes are created in the Shares page of a project by clicking the  symbol.
Figure 4. Sun Storage 7210 Management GUI: Shares Page
This opens a new window where the user root is supplied rather than nobody:
Figure 5. Sun Storage 7210 Management GUI: Creation of a Share
After committing the creation by clicking Apply, the new volume appears in the Shares listing of the project:
Figure 6. Sun Storage 7210 Management GUI: List of Shares
Preparing the Server

On the server running the Solaris 10 OS for x64 platforms, the following tasks need to be completed before the SAP software is
installed:
● Creating users and groups
● Setting kernel parameters and rebooting the server
● Providing enough swap space
● Mounting the NFS shares for Oracle data files and logs
● Building the directory structure for the SAP installation
● Installing the 64-bit Java 1.4.2 software
● Supplying the Java Cryptography Extension
Users and Groups

An SAP implementation requires three users on the OS level:
● <SAP_SID>adm for the SAP application. This user ID is created beforehand.
● ora<SAP_SID> for the database. This user ID is created beforehand.
● <Solution_Manager_ID>adm for diagnostic purposes. The SAP installation program terminates with an error if this
user and its home directory already exist. Therefore, the user and its home directory are created by the SAP installation
routine. The user name sapadm was chosen for the installation described herein.
Additionally, four groups need to be created on the OS level:
● sapsys
● oper
● dba
● sapinst
The C shell is recommended by SAP as a login shell for these SAP users (SAP Note 202227). The following script was used to create
users and groups for the SAP SID VWS:
groupadd -g 1000 sapsys

groupadd -g 1001 oper
groupadd -g 1002 dba
groupadd -g 1003 sapinst
useradd -m -d /export/home/vwsadm -s /usr/bin/csh -g sapsys -u 101 -c "SAP

System Administrator" vwsadm
useradd -d /oracle/VWS -s /usr/bin/csh -u 102 -g dba -c "Oracle Database

Administrator" oravws
Solaris Kernel Parameters

For the Solaris 10 OS, kernel parameters have been set according to SAP Note724713:
In /etc/system, the following line was added. The server must be rebooted to make the new setting effective.
set rlim_fd_cur=8192
A Solaris project was created to specify kernel settings that are required by Oracle. This project was assigned to the three users
created for the SAP installation. Additionally, the root user's project settings were modified. With VWS as SAP SID, the script for
this purpose is the following:
USER1=vwsadm
USER2=oravws
USER3=sapadm
projadd -p 100 -c "SAP System VWS" -U $USER1,$USER2,$USER3 -K "project.max-
sem-ids=(priv,1024,deny)" -K "process.max-sem-nsems=(priv,2048,deny)" -K
"project.max-shm-ids=(priv,256,deny)" -K "project.max-shm-
memory=(priv,18446744073709551615,deny)" SAP_VWS
echo $USER1::::project=SAP_VWS >> /etc/user_attr

projmod -K "project.max-sem-ids=(priv,1024,deny)" -K "process.max-sem-

nsems=(priv,2048,deny)" -K "project.max-shm-ids=(priv,256,deny)" -K
"project.max-shm-memory=(priv,18446744073709551615,deny)" user.root
Both the SAP installation program and the Oracle Universal Installer program perform prerequisite checks and issue warnings if any
of the required prerequisites are missing. Neither program is capable of verifying the Solaris kernel parameters if these are specified
by project settings. The resulting warnings can be safely ignored.
SWAP Space
The total amount of disk-based swap space used for the SAP installation was 28 Gbyte in two disk slices on internal disks of the Sun
Fire X4200 M2 server.
Mounting the NFS Shares

The following script was used to mount the volumes on the 7210 Unified Storage System. The mount options have been specified
according to recommendations from a joint publication by Sun and NetApp1. For the initial installation and database load, the
mount option forcedirectio was omitted, which would otherwise slow down the installation process. For production, it is
recommended to bypass file system caching mechanisms through the forcedirectio option.
NAS_APPLIANCE=10.9.168.97
ORACLE_DATA=/export/SAP_Oracle_Data
ORACLE_LOGS=/export/SAP_Oracle_Logs
MOUNT_OPTIONS=rw,bg,intr,suid,wsize=32768,rsize=32768,vers=3,proto=tcp,hard
MOUNTPOINT_DATA=/mnt2
MOUNTPOINT_LOGS=/mnt3
mount -F nfs -o $MOUNT_OPTIONS $NAS_APPLIANCE:$ORACLE_DATA $MOUNTPOINT_DATA

mount -F nfs -o $MOUNT_OPTIONS $NAS_APPLIANCE:$ORACLE_LOGS $MOUNTPOINT_LOGS
Building the SAP Directory Structure

Symbolic links have been used to construct the folder structure that the SAP installation program expects on the root file system of
the server, which then point to the targets on shared NAS volumes. All Oracle log files have been placed on the same volume for the
tests performed for this paper. It should be noted that having all redo and archive logs on the same volume is not recommended.
The following illustration displays the directory structure for the Oracle database.
1 Colaco, G., Suggs, D.: Database Performance with NAS: Optimizing Oracle on NFS, Technical Whitepaper, May 2004
Figure 7. SAP Database Directories and Symbolic Links
The script for the setup of the SAP directories is as follows:

SAP_SID=<SAP_SID>
ORACLE_ADMIN=<Oracle_Admin>:dba
MOUNTPOINT_SAP_DATA1=<mountpoint_for_sapdata1>
MOUNTPOINT_ONLINE_REDO_LOGS=<mountpoint_for_redo_logs>
MOUNTPOINT_MIRROR_REDO_LOGS=<mountpoint_for_mirrored_redo_logs>
MOUNTPOINT_ARCHIVE_LOGS=<mountpoint_for_archived_redo_logs>
mkdir /sapmnt
mkdir /usr/sap
mkdir -p /oracle/$SAP_SID
mkdir /oracle/oraInventory
mkdir $MOUNTPOINT_SAP_DATA1/sapdata1
mkdir $MOUNTPOINT_ONLINE_REDO_LOGS/origlogA
mkdir $MOUNTPOINT_ONLINE_REDO_LOGS/origlogB
mkdir $MOUNTPOINT_MIRROR_REDO_LOGS/mirrlogA
mkdir $MOUNTPOINT_MIRROR_REDO_LOGS/mirrlogB
mkdir $MOUNTPOINT_ARCHIVE_LOGS/oraarch
ln -s $MOUNTPOINT_SAP_DATA1/sapdata1 /oracle/$SAP_SID/sapdata1
ln -s $MOUNTPOINT_ONLINE_REDO_LOGS/origlogA /oracle/$SAP_SID/origlogA
ln -s $MOUNTPOINT_ONLINE_REDO_LOGS/origlogB /oracle/$SAP_SID/origlogB
ln -s $MOUNTPOINT_MIRROR_REDO_LOGS/mirrlogA /oracle/$SAP_SID/mirrlogA
ln -s $MOUNTPOINT_MIRROR_REDO_LOGS/mirrlogB /oracle/$SAP_SID/mirrlogB
ln -s $MOUNTPOINT_ARCHIVE_LOGS/oraarch /oracle/$SAP_SID/oraarch
chown -R $ORACLE_ADMIN /oracle

chown -R $ORACLE_ADMIN $MOUNTPOINT_SAP_DATA1
chown -R $ORACLE_ADMIN $MOUNTPOINT_ONLINE_REDO_LOGS
chown -R $ORACLE_ADMIN $MOUNTPOINT_MIRROR_REDO_LOGS
chown -R $ORACLE_ADMIN $MOUNTPOINT_ARCHIVE_LOGS
Installing the J2SE Software

The 32-bit Java SDK Standard Edition was installed by executing j2sdk-1.4.2_13-solaris-i586.sh as user root in the
folder /usr/jdk. This creates subfolder j2sdk1.4.2_13. Afterwards, j2sdk-1.4.2_13-solaris-amd64.sh is run as
root in folder /usr/jdk.
Java Cryptography Extension

The zip file containing the Java Cryptography Extension is extracted and installed in the JDK™ directory by the sapinst program.
No additional action must be taken other than providing the path to this zip file.
14 Installing the SAP ERP SR3 Software Sun Microsystems, Inc.
Installing the SAP ERP SR3 Software

Setting Up the Environment for the Installation
The SAP installation program, sapinst, is GUI-based and requires the following for its execution:
● The SAP installation program supports three UNIX® shells: Bourne shell, C shell, and Korn shell. For the installation
described herein, the C shell was used.
● The DISPLAY variable must be set.
● The installation GUI requires Java. The sapinst process uses the environment variable SAPINST_JRE_HOME to
identify the Java runtime environment™ (JRE) that is used during the installation. This Java runtime environment need not
necessarily match the 64-bit Java installation that the SAP application is using.
● The SAP installation program uses a directory, specified in the environment variable TEMP, to store scripts for and logs of
the installation. This directory should be persistent, that is, not automatically cleared by the operating system as it is the
case with /tmp, because the sapinst program uses the contents of this folder to determine the progress and state of
an interrupted installation of the SAP software. The contents of the $TEMP folder allows an interrupted SAP installation to
be resumed without supplying all installation parameters again. For the installation described herein, /var/tmp was
used as $TEMP folder.
The following shell script was used to define the additional environment variables needed:
#!/usr/bin/csh
setenv DISPLAY 172.20.98.83:0.0

setenv TEMP /var/tmp
setenv SAPINST_JRE_HOME /usr/jdk/j2sdk1.4.2_13
These variables were set by executing the following command as root at a C shell prompt:
source <Script_With_SAPINST_Environment_Variables>
Sequence of Steps
The installation of the SAP software is done in four phases:
1. Parameters for the installation of the SAP software are supplied in a series of dialog windows. These parameters cover the
following:
● The type of installation: For the implementation described in this paper, a Central System with an ABAP and a Java
instance was chosen. The custom setup type was selected, which requires that more settings need to be specified than
with the typical setup type.
● A three-digit alphanumerical string as SAP SID. Some values are not allowed2. The SAP SID is then used as follows:
● To define the names of users for database administration, ora<SAP_SID>, and for the application
administration, <SAP_SID>adm
● As the name of the subdirectory under /oracle that contains the directory structure of the SAP database,
which is created beforehand (see section Building the SAP Directory Structure on page 11).
2 See Installation Guide: SAP ERP 6.0 SR3 ABAP+Java on Solaris:Oracle 1.0 03/28/2008, p. 31
● The path to the 64-bit Java SDK and JRE.
● The location of the CD/DVD media used for the installation.
● Passwords for user accounts on the operating system, database, and application level; a character string for the
encryption.
● Options to configure the Oracle database. The input is used to create an answer file, which is used during the installation
of the Oracle RDBMS software.
● The option to add the new SAP system to a NetWeaver Development Infrastructure.
● The option to add the new SAP system to a System Landscape Directory.
2. Then the installation commences with the creation of users and their environment.
3. The Oracle database software is installed. This comprises three steps:
● Installing the Oracle RDBMS 10.2.0.1 software
● Installing the Oracle 10.2.0.2 Patch set
● Applying Oracle patches according to SAP Note 871096
4. The database for the SAP system is created and populated. Then the SAP system is configured and made ready for initial use.
SAPinst Initialization
The sapinst executable is located on the disk SAP Business Suite 2005 Installation Master for SAP NetWeaver 7.0 SR3. This
program is called by the user root , the directory context of which was set to /var/tmp.
Figure 8. SAPinst: Launch of the Installation Process
The GUI of the SAP installation program appears. From the selection list, choose SAP ERP 6.0 Support Release 3 with Oracle as the
database platform. The menu entry Central System must be highlighted before the next screen can be accessed.
Figure 9. SAPinst: Choosing the System to Be Installed
SAPinst Part One: Define Parameters

The custom type for SAPinst is selected.
Figure 10. SAPinst: Installation Type
The ERP application was installed with the following units:
Figure 11. SAPinst: Choosing the Components for ERP and for NetWeaver
Because the SAP Java Web Application Server shall be installed, the SAP installation program verifies that some Java software is
available. First, the location of the SAP NetWeaver 7.0 SR3: Java based Software Components disk must be specified by supplying
the path to the file CDLABEL.ASC. The Browse button can be used to supply the path.
Figure 12. SAPinst: Supplying the Installation Media for the Java Component
After clicking Next, the location of the installation path for a 64-bit JDK must be supplied:
Figure 13. SAPinst: Supplying the Path for the 64-bit JDK
In the last step of Java software verification, the location of the Java Cryptography Extension (JCE) for Java version 1.4.2 is specified.
The SAP installation program automatically extracts the .zip file containing the JCE software and copies the content to the JDK
installation path that was provided in the preceding screen.
Figure 14. SAPinst: Java Cryptography Extension
When all required Java software is verified to be available, the SAPinst installation program continues with general settings for the
SAP system that shall be installed.
Figure 15. SAPinst: Defining the SAP System
In the following screen, a password can be set that is globally valid for all user accounts of the SAP application server. This includes
accounts for users on the OS and Oracle database level, as well as accounts for SAP application users.
Figure 16. SAPinst: Supplying a Global Password for All Accounts to Be Created
The next screen asks for the database ID, which is usually the same as the SAP SID.
Figure 17. SAPinst: Name and Host of the Oracle Database
SAPinst checks OS settings and reports on deviations from recommended settings that may cause potential problems. In the
installation described herein, SAPinst verifies these settings in /etc/system; it is not capable of verifying kernel parameters
defined via projects.
Figure 18. SAPinst: Verification of OS Kernel Parameters
After you click Next, a warning for unverified system parameters is displayed. This can be ignored by clicking Cancel to continue the
installation.
Figure 19. Warning About Failed Parameter Checks
The location of the Installation Export media is requested in the next two screens:
Figure 20. SAPinst: Supplying the Path to Installation Media
The following windows control the setup of the Oracle database for the SAP application. The first screen lets the you adjust the
distribution of physical memory between the database and the OS.
Figure 21. SAPinst: Parameters for the Database
The size of the database files to be created can be defined in the next screen. Selecting the Advanced DB Configuration option
brings up an additional screen, depicted in Figure 26.
Figure 22. SAPinst: Basic Parameters for the Database Creation
In the course of the installation process, SAPinst creates a new database with two database user accounts. If no passwords are
provided, the master password defined in the screen shown in Figure 16 on page 19 is assigned.
Figure 23. SAPinst: Users for the Database
In the next screen, the path for the Oracle RDBMS installation media must be supplied.
Figure 24. SAPinst: Supplying the Path to the Installation Media for Oracle
The configuration of the Oracle Listener is provided in the following window.
Figure 25. SAPinst: Oracle Listener Settings
If the option Advanced DB Configuration is selected in the screen depicted in Figure 22 on page 22, the following menu is presented:
Figure 26. SAPinst: Advanced Database Configuration Settings
An overview about the options available in this Advanced DB Configuration page is given in the Appendix on page 47. For the
installation described herein, the default settings were kept. The following screen defines the SAP codepage and the number of
processes that are used for the database load.
Figure 27. SAPinst: Database Load Parameters
For the encryption of data in the Java Web Application Server, a passphrase is used. If no extra passphrase is supplied in the
following window, the master password from Figure 16 (page 19) is used.
Figure 28. SAPinst: Encryption Phrase
By default, SAPinst performs an update statistics task after the database has been loaded. The next screen allows you to switch off
this task.
Figure 29. SAPinst: Optimizing the Database After Loading
In the next step, the instance numbers for the central instance and for the SCS instance are defined.
Figure 30. SAPinst: Instance Numbers
The values provided in this page control the default values of the port numbers for the message servers of both instances. The
installation described in this paper uses 01 for the central instance and 00 for SCS. The default values are 00 for the central instance
and 01 for SCS. Figure 31 shows the port numbers suggested by the SAPinst program:
Figure 31. SAPinst: Ports to Be Used by the SAP System
The following two screens allow you to specify individual passwords for user accounts of the ABAP and the Java instances. If no
passwords are supplied here, the master password that was defined in the screen of Figure 16 applies. First, the users of the ABAP
instance are listed:
Figure 32. SAPinst: User Accounts of the SAP System — Passwords

In a second step, the users of the Java instance are provided:
Figure 33. SAPinst: User Accounts of the SAP System — More Passwords
Before SAPinst displays a summary of the settings and parameters that will be used for the installation of the SAP software, you are
asked to provide the location of installation media for the last time:
Figure 34. SAPinst: Supplying the Path to Installation Media
Some installation media contain archives that SAPinst extracts. The following screen shows a list of archives and the destination of
their extracted content. For the installation described herein, the default paths are used.
Figure 35. SAPinst: Installation Archives to Be Extracted
SAPinst offers to integrate the new SAP system in a NetWeaver Development Infrastructure. For the system installation described in
this paper, no integration is done.
Figure 36. SAPinst: NWDI
An SAP system can be integrated in a System Landscape Directory (SLD): For this installation, creating a new SLD was chosen.
Figure 37. SAPinst: SLD Registration
The creation of a new SLD requires that some additional parameters be defined. While the default settings were kept for the SLD
users, the value for Object server name was set to the host name of the Solaris OS.
Figure 38. SAPinst: SLD Parameters
In the following screen, the passwords for some J2EE™ users need to be set:
Figure 39. SAPinst: User Accounts of the SAP System — Passwords
The parameters for the OS user of the Diagnostics agent instance are specified in the next window. For this installation, the user
name sapadm is chosen. A path for its home directory was provided because SAPinst would otherwise create such a home directory
in /home. This user is assigned the same project as ora<SAP_SID> and <SAP_SID>adm. The default value for the SID of the
Diagnostics instance, SMD, was kept.
This is the last screen in the installation phase where parameters are being defined. A summary of the input provided in the
preceding steps is given before the installation commences.
Figure 40. SAPinst: Summary of the Installation Parameters
SAPinst Part Two: Installation

When all parameters for the installation of the SAP software have been supplied, the installation process starts by asking for an SAP
Solution Manager key. This key is created by an SAP Solution Manager. For the creation of such a key, the following values are
needed:
● SAP SID of the system that shall be installed
● Host name of the server where the SAP software shall be installed
● Instance number of the Central Instance
The procedure for the creation of such a Solution Manager key is described in SAP Note 805390.
Figure 41. SAPinst: Supplying a Solution Manager Key
After supplying a Solution Manager key, SAPinst continues with the installation process:
Figure 42. SAPinst: The Installation Is Running
When SAPinst comes to step #9 (Install database server software), the installation process in interrupted, and you are asked to
perform the installation of the Oracle RDBMS software:
Figure 43. SAPinst: Prompt for Installing the Oracle RDBMS Software
SAPinst Part Three: Installation of the Oracle RDBMS Software

The installation of the Oracle database software is accomplished in three steps:
1. Installing the Oracle database software, version 10.2.0
2. Installing the Oracle 10.2.0.2 patch set
3. Applying Oracle patches
Installing the Oracle Database Software 10.2.0

In another terminal window, call the RUNINSTALLER executable in /oracle/stage/102_64/database/Disk1/SAP as
user ora<SAP_SID>. Set the DISPLAY variable before calling the executable. RUNINSTALLER evaluates the database-specific
parameters that have been defined in the screens depicted in Figure 21-26 and produces an installation script for the Oracle RDBMS
installation, which is then executed and requires only minimal user input.
Figure 44. Oracle RDBMS Installation: Launching RUNINSTALLER
The Oracle Universal Installer (OUI) is launched. All values in the fields of the following screens have been supplied by the SAPinst
script. No user input is necessary. The first step in the OUI process is to specify the path to the Oracle inventory.
Figure 45. Oracle RDBMS Installation: oraInventory
In the next step, the packages that shall be installed are listed for review. No changes need to be made here.
Figure 46. Oracle RDBMS Installation: List of Predefined Components
OUI verifies if the appropriate OS kernel parameters are set in /etc/system. Since these parameters have been made effective
via the user's project settings, the check fails.
Figure 47. Oracle RDBMS Installation: Checking the OS Configuration
The warning issued by OUI can safely be ignored:
Figure 48. Oracle RDBMS Installation: Warning
The next screen displays a summary of the installation parameters.
Figure 49. Oracle RDBMS Installation: Summary
After you click Install, OUI begins the installation process:
Figure 50. Oracle RDBMS Installation in Progress
At the end of the installation process, the following screen appears.
Figure 51. Oracle RDBMS Installation: Scripts to Be Executed
In another terminal window, execute the shell scripts listed in Figure 51 as user root.
Figure 52. Running the Scripts
After the shell scripts are run and the system returns to the OUI window in Figure 51, click OK to bring up the final screen of the
OUI.
Figure 53. Oracle RDBMS Installation Finished
Installing the Oracle 10.2.0.2 Patch Set

After installing the Oracle RDBMS software, the Oracle patch set for Oracle version 10.2.0.2 needs to be applied. The media for the
patch set contains a runInstaller executable, which is called by the user ora<SAP_SID>. The OUI is launched:
Figure 54. Oracle Patch Set 10.2.0.2: Start Screen
The Create Starter Database option must not be selected. SAPinst installs the application database in a later step.
Figure 55. Oracle Patch Set 10.2.0.2: Summary
Start the update of the RDBMS installation by clicking Install:
Figure 56. Oracle Patch Set 10.2.0.2 in Progress
At the end of the patch set installation, the root.sh script must be run again by the user root.
Figure 57. Oracle Patch Set 10.2.0.2: Script to Be Executed
The output of the script execution is the following:
Figure 58. Executing the Script
When you return to the OUI window, click OK to terminate the installation.
Figure 59. Oracle Patch Set 10.2.0.2 Finished

Applying Oracle Patches Using MOPatch
MOPatch uses a repository with the downloaded Oracle patches. It is recommended to run the MOPatch executable in the C shell.
The script shown next was used to apply the patches for the Oracle RDBMS installation. It performs the following:
● The contents of ORACLE_HOME and oraInventory are backed up.
● The zip files with OPatch and MOPatch are extracted in $ORACLE_HOME. The file names for both executables in the
following shell script are the current and recommended version as of writing this document.
● MOPatch is executed in "dry-run" mode, which simulates applying the patches and produces an output that can be
checked for any potential problems.
BACKUP_DIR=<Path_for_Backup_of_ORACLE_HOME_and_oraInventory>
ORACLE_PATCH_LOCATION=<Path_of_Oracle_Patches>
ORACLE_OPATCH_INSTALLER_LOCATION=<Path_of_new_versions_of_OPatch_MOPatch>
OPATCH_ZIP_FILE=p4898608_10202_GENERIC_v5.zip
MOPATCH_ZIP_FILE=mopatch-1_9.zip
mkdir $BACKUP_DIR
zip -r $BACKUP_DIR/ORACLE_HOME_Backup.zip $ORACLE_HOME

zip -r $BACKUP_DIR/OraInventory_Backup.zip /oracle/oraInventory
mv $ORACLE_HOME/OPatch $ORACLE_HOME/OPatch.orig
unzip -d $ORACLE_HOME $ORACLE_OPATCH_INSTALLER_LOCATION/$OPATCH_ZIP_FILE

unzip -d $ORACLE_HOME $ORACLE_OPATCH_INSTALLER_LOCATION/$MOPATCH_ZIP_FILE
cd $ORACLE_PATCH_LOCATION
/bin/sh $ORACLE_HOME/MOPatch/mopatch.sh -v -d
The output of the dry run looks similar to the following.
Patch Installation Status:

--------------------------
Installed 38 of 38 patches successfully:
p3748430_10202_Solaris8664.zip
p4604970_10202_Solaris8664.zip (patch number 5253303)
p4638550_10202_GENERIC.zip
p4668719_10202_Solaris8664.zip
p4704890_10202_Solaris8664.zip
p4770693_10202_Solaris8664.zip
p4883635_10202_Solaris8664.zip
p4899479_10202_Solaris8664.zip
p4952782_10202_Solaris8664.zip
p5063279_10202_Solaris8664.zip
p5092134_10202_Solaris8664.zip (patch number 5253307)
p5103126_10202_Solaris8664.zip
[...]
Patch Inventory Status:

-----------------------
Patches installed in Oracle Home /oracle/VWS/102_64:
3748430
4638550
4668719
4704890
4770693
4773931
4864648
4883635
4899479
4952782
5063279
5103126
[...]
Link Status:
------------
Link script "./link.sh" executed successfully
Because there is no database present at this time, the patches can be applied without any problems by executing the following
command:
/bin/sh $ORACLE_HOME/MOPatch/mopatch.sh -v
SAPinst Part Four: Continuing With Creation and Load of the Database and Initial
Configuration of the SAP System
After the Oracle database software and the required patches have been applied, the SAPinst installation process can be resumed by
clicking OK in the screen shown in Figure 43. The following tasks are executed without user interaction, provided that SAPinst does
not encounter any problems. The end of the installation is marked by the following pop-up window.
Figure 60. SAPinst Finished
The database is up and running, and the SAP system is ready for use. It is recommended to re-mount the NFS share holding the redo
log files with the forcedirectio option enabled1. Additionally, some post-installation tasks should be performed after SAPinst
has completed the installation. These tasks are not specific for an OS and database platform. For an overview, the SAP
documentation should be consulted3.
3 See Installation Guide: SAP ERP 6.0 SR3 ABAP+Java on Solaris:Oracle 1.0 03/28/2008, p. 129 ff.
47 Appendix Sun Microsystems, Inc.
Appendix
SAPinst: Advanced Database Configuration
SAPinst offers the option to configure the database differently from the default settings that the installation program applies (see
Figure 26). The options to configure are:
● Distribution of Oracle database files to sapdata directories
● Installation paths
● Database parameters
● Tablespace creation
● Layout and properties of Oracle control files
● Autoextend feature
● Extent management
The following series of screenshots depicts the options that SAPinst allows you to configure. First, the layout of the sapdata
directories can be specified.
Figure 61. SAPinst: Advanced Database Configuration (1)
The next option is about the tablespaces to be created.
The number of control files and their location can be specified in the following screen:
Settings for individual tablespaces are defined in the next two screens. In the first one, general storage parameters can be defined
for tablespaces.
Default tablespace storage parameters can be configured in the second step:
Properties of the database instance can be adjusted in the following screen.
The installation paths for ORACLE_HOME, SAPDATA_HOME, and the stage directory can be customized in the next screen:
Settings for the autoextend feature can be fine-tuned on tablespace level.
The last option is about advanced tablespace properties:
52 Glossary Sun Microsystems, Inc.
Glossary
The following table contains common abbreviations and acronyms that are used in the present study.
Abbreviation Explanation
ABAP Advanced Business Application Programming
ERP Enterprise Resource Planning
NAS Network Attached Storage
NFS Network File System
OS Operating System
OUI Oracle Universal Installer
SCS System Central Services
SLD System Landscape Directory
SSD Solid State Disk
53 Acknowledgements Sun Microsystems, Inc.
Acknowledgements
We want to thank the following colleagues for their kind help, assistance, and support during the work on the present paper:
Ryan Arneson, Sun Microsystems in Broomfield, CO, for preparing the Sun Fire X4200 M2 server and for assistance with hardware.
Sridhar Ranganathan, Sun Microsystems in Nashua, NH, for preparing the NAS appliance and for providing answers to numerous
questions about Fishworks.
For More Information

Here are some additional resources:
● SAP web site: http://www.sap.com

● SAP documentation: http://help.sap.com
● Oracle Technology Network: http://www.oracle.com/technology/index.html
● Sun download site: http://www.sun.com/download/
● Sun training courses at http://www.sun.com/training/, such as:
● Sun Storage 7000 Unified Storage System Administration (NWS-6425)
● Sun Fire X4100 and X4200 Server Maintenance and Troubleshooting CD Bundle (CDLE-4923)
● Discussions:
● Sun Storage forums: http://forum.java.sun.com/category.jspa?categoryID=66
● Sun Hardware - Servers forums: http://forums.sun.com/forum.jspa?forumID=830
● BigAdmin Discussions collection: http://www.sun.com/bigadmin/discussions/
● Product documentation at http://docs.sun.com, for example, Sun Storage 7210 Unified Storage System
documentation
● Documentation Center: http://www.sun.com/documentation/
● Wikis:
● Sun BluePrints™ wiki (http://wikis.sun.com/display/BluePrints/Main), which provides Sun
BluePrints papers (registration required), such as Configuring Sun Storage 7000 Systems for Oracle Databases
(http://wikis.sun.com/display/BluePrints/Configuring+Sun+Storage+7000+Systems
+for+Oracle+Databases )
● Sun Storage Administration wiki: http://wikis.sun.com/display/StorageAdmin/Home
● BigAdmin Databases wiki: http://wikis.sun.com/display/BigAdmin/Databases
● BigAdmin Storage Tech Tips wiki:

http://wikis.sun.com/display/BigAdmin/Storage+Tech+Tips
● Other resources:
● Sun Storage 7210 Unified Storage System web site:
http://www.sun.com/storage/disk_systems/unified_storage/7210/
● Sun Fire X4200 M2 server web site: http://www.sun.com/servers/entry/x4200/
54 For More Information Sun Microsystems, Inc.
● BigAdmin Storage resource collection:

http://www.sun.com/bigadmin/collections/storage.html
● Sun Storage web site: http://www.sun.com/storagetek/index.jsp
● Storage Stop Blog: http://blogs.sun.com/storage
● Support:
● Sun resources:
● Register your Sun gear: https://inventory.sun.com/inventory/
● Services: http://www.sun.com/service/index.jsp
● SunSolveSM Online: http://sunsolve.sun.com
● Community system administration experts:
http://www.sun.com/bigadmin/content/communityexperts/
● Events of interest to users of Sun products:
● Worldwide developer events and Sun Tech Days: http://developers.sun.com/events/
● Current events: http://www.sun.com/events/index.jsp
Licensing Information
Unless otherwise specified, the use of this software is authorized pursuant to the terms of the license found at
http://www.sun.com/bigadmin/common/berkeley_license.html.

Runing Oracle Database On The Sun Storage 7210 - Sap - Erp

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Runing Oracle Database On The Sun Storage 7210 - Sap - Erp

Caricato da

Copyright:

Formati disponibili

Running SAP ERP 6.

This article was published by BigAdmin at:

ORACLE is a registered trademark of Oracle Corporation.

DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,

Hardware and Software Components....................................................................................................................... 4

Scope and Limitations............................................................................................................................................. 5

Preparing the Server and 7210 Unified Storage System.............................................................................................. 6

Installing the SAP ERP SR3 Software....................................................................................................................... 14

For More Information............................................................................................................................................ 53

● The SAP system has the following following properties:

● The SAP System ID (SID) is VWS.

● The SAP system contains an ABAP and a Java™ instance.

● The number of the central instance is 01.

● The number of the SCS instance is 00.

● The user home directories are located in /export/home.

● The SAPinst custom installation mode is used.

● The database has two mirrored pairs of online redo logs.

● The control files are 50 Mbyte in size.

Hardware and Software Components

● 2x AMD Opteron™ 252 processor, 2.59 GHz

Sun Storage 7210 Unified Storage System

● Sun Storage 7000 Series software update version 2008.10 (2008.Q4)

Scope and Limitations

● The Oracle RDBMS

Preparing the Server and 7210 Unified Storage System

SAP Installation Packages

Additionally, the following media of the Oracle software are needed:

● Oracle 10.2 64-bit RDBMS: Solaris on x64 64-bit (51031947)

● j2sdk-1.4.2_13-solaris-i586.sh (the 32-bit version)

● j2sdk-1.4.2_13-solaris-amd64.sh (the 64-bit version)

The Java Cryptography Extension 1.4.2 can be obtained from http://java.sun.com/j2se/1.4.2/download.html.

Creating and Sharing Volumes on 7210 Unified Storage System

Figure 1. Sun Storage 7210 Management GUI: Projects Page

This opens a dialog window:

Figure 2. Sun Storage 7210 Management GUI: Project Creation

Figure 4. Sun Storage 7210 Management GUI: Shares Page

Figure 5. Sun Storage 7210 Management GUI: Creation of a Share

Figure 6. Sun Storage 7210 Management GUI: List of Shares

Preparing the Server

● Creating users and groups

● Setting kernel parameters and rebooting the server

● Providing enough swap space

● Building the directory structure for the SAP installation

● Installing the 64-bit Java 1.4.2 software

● Supplying the Java Cryptography Extension

Users and Groups

● <SAP_SID>adm for the SAP application. This user ID is created beforehand.

● ora<SAP_SID> for the database. This user ID is created beforehand.

Additionally, four groups need to be created on the OS level:

groupadd -g 1000 sapsys

useradd -m -d /export/home/vwsadm -s /usr/bin/csh -g sapsys -u 101 -c "SAP

useradd -d /oracle/VWS -s /usr/bin/csh -u 102 -g dba -c "Oracle Database

Solaris Kernel Parameters

projadd -p 100 -c "SAP System VWS" -U $USER1,$USER2,$USER3 -K "project.max-

echo $USER1::::project=SAP_VWS >> /etc/user_attr

projmod -K "project.max-sem-ids=(priv,1024,deny)" -K "process.max-sem-

Mounting the NFS Shares

mount -F nfs -o $MOUNT_OPTIONS $NAS_APPLIANCE:$ORACLE_DATA $MOUNTPOINT_DATA

Building the SAP Directory Structure

Figure 7. SAP Database Directories and Symbolic Links

The script for the setup of the SAP directories is as follows:

chown -R $ORACLE_ADMIN /oracle