guideline for setting-up a sap erp 6.0 system on linux sles 10 oracle

Guideline for Setting-Up a SAP ERP 6.0 System on Linux SLES 10 / Oracle

Applies to: SAP ERP 6.0 SR3

Oracle 10g R2

Linux SLES 10 SP1 on Itanium Systems

Summary This paper gives an updated overview of the installation procedure for setting up an ECC6 ABAP stack on Linux.

This procedure gives a detailed guideline in this simple case, and SAP notes in reference are given so that the reader can access more detailed information for his particular case.

Author: Pascal Bombardier

Company: BULL

Created on: 16 April 2008

Author Bio Pascal Bombardier has 10 years of experience in ERP consulting, integration and development. His competences range from Operating systems to ERP software, from functional analysis to implementation and development. He is working for BULL Company and currently joined the SAP Linuxlab as a hardware partner, where he certifies SAP software components on Bull hardware.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 1


Table of Contents 1 References ......................................................................................................................................................3 2 Product Versions .............................................................................................................................................4 3 System Installation – Linux SLES10...............................................................................................................4

3.1 Start Installation ........................................................................................................................................4 3.2 System Configuration..............................................................................................................................12

3.2.1 Configure Some Kernel Parameters .................................................................................................................12 3.2.2 Check the Network Configuration .....................................................................................................................12 3.2.3 Prepare SAP Paths with Adequate Volume Size ..............................................................................................13 3.2.4 Install Additional System Components..............................................................................................................13 3.2.5 Install Additional SAP SAPlocales Package......................................................................................................14

4 SAP ERP 6.0 Setup – 1st Part .......................................................................................................................15 4.1 Preparation..............................................................................................................................................15 4.2 Installation ...............................................................................................................................................15

5 Oracle installation ..........................................................................................................................................24 6 SAP ERP 6.0 Setup – 2nd Part ......................................................................................................................28 7 Oracle Upgrade .............................................................................................................................................30

7.1 Prerequisites Checks ..............................................................................................................................30 7.2 Patchset 10.2.0.2 ....................................................................................................................................30 7.3 Opatch Upgrade......................................................................................................................................37 7.4 Mopatch Installation ................................................................................................................................38 7.5 CPU Patchs.............................................................................................................................................38 7.6 Instantclient .............................................................................................................................................38 7.7 Patches Installation with mopatch...........................................................................................................40

8 Post-installation Check ..................................................................................................................................43 9 Database Configuration.................................................................................................................................47

9.1 Optionally, on a TEST System................................................................................................................47 9.2 Oracle Configuration ...............................................................................................................................47 9.3 Oracle Authorizations..............................................................................................................................50 9.4 Configure the TNS Listener ....................................................................................................................51 9.5 Activate Asynchronous I/O in Oracle ......................................................................................................53 9.6 Memory Configuration.............................................................................................................................55 9.7 Configuring Hugepages ..........................................................................................................................56 9.8 Error ORA-14508 ....................................................................................................................................57 9.9 Configure Default Tablespace ................................................................................................................57

10 SAP Kernel Upgrade ...................................................................................................................................59 11 SAP Configuration .......................................................................................................................................61

11.1 Profile Adjustment – Memory Related Parameters...............................................................................61 11.2 Transport...............................................................................................................................................62 11.3 Backup ..................................................................................................................................................62 11.4 SAP Configuration.................................................................................................................................63 11.5 Recommended SAP Note.....................................................................................................................67

12 Annex – OEM Installation ............................................................................................................................68 Related Content................................................................................................................................................70 Copyright...........................................................................................................................................................71



1 References

It is highly recommended to read the latest version of ALL the SAP notes mentioned in this document, as well as related notes.

Many of them are changing relatively often, and it is strongly recommended to get the last version of each note.

http://service.sap.com/

Read SAP Note 23345 Consistency check of ORACLE database

Read SAP Note 105047 Support for Oracle functions in the SAP environment

Read SAP Note 134592 Importing the SAPDBA role

Read SAP Note 146289 Parameter recommendations for 64-bit SAP kernel

Read SAP Note 171356 Linux Essential Information

Read SAP Note 400241 Problem with ops$ or sapr3 connect to Oracle

Read SAP Note 407314 Released SAP kernels 6/7 for Oracle

Read SAP Note 514178 ORA-14508 when validating partitioned tables

Read SAP Note 562403 FAQ : Oracle Net

Read SAP Note 700548 FAQ : Oracle authorizations

Read SAP Note 793113 FAQ : Oracle I/O configuration

Read SAP Note 819829 Oracle Database 10g – Instant Client 10.x on Unix

Read SAP Note 830576 Parameter recommendations for Oracle 10g

Read SAP Note 834917 Oracle Database 10g – New database role SAPCONN

Read SAP Note 835474 More than 32 GB extended memory

Read SAP Note 841728 Oracle Database 10g – Software installation problems 10.2.0

Read SAP Note 871096 Oracle Database 10g – Patch sets/patches for 10.2.0

Read SAP Note 941735 SAP Memory Management for 64 bits Linux systems

Read SAP Note 958253 SLES 10 Installation Notes

Read SAP Note 969674 Oracle Database 10g – Default Permanent Tablespace PSAPSAUX

Read SAP Note 972262 Inst.NW 7.0(2004s)SR2/Business Suite 2005 SR2-UNIX

Read SAP Note 986578 Oracle Support on Itanium 2 (Montecito) systems

Read SAP Note 1027012 MOPatch – Install multiple Oracle Patchs in one run

Read SAP Note 1140644 CPU Patches January 2008 (Oracle Critical Update Program)

...

and related notes


http://service.sap.com/


2 Product Versions This is the basic installation procedure for SAP ERP on Linux. The concerned versions are the following:

• Novell Suse Linux Enterprise Server SLES 10 SP1

• Oracle 10g R2

• SAP ERP 6.0 SR3

3 System Installation – Linux SLES10 Read SAP Note 171356 Linux Essential Information


Read SAP Note 407314 Released SAP kernels 6/7 for Oracle

> Operating System: LINUX ON IA64 > SAP KERNEL 7.00 64-BIT UNICODE

3.1 Start Installation

Reboot the server and boot on the Novell SLES 10 DVD

Choose English



Select Partitioning

Swap Swap recommended size is ranging from 2 times the memory size to 0.5 time the memory size for largest machines

If possible, dispatch swap on multiple drives

EFI create a 100MB FAT partition for /boot/efi

VG The use of logical volumes are recommended for maximum flexibility

Available filesystems : ext3; xfs



Select the following Software options

KDE Desktop

C/C++ Compiler and Tools

Do not select “SAP Application Base”. A newer sapinit package is available on Novell website; read chapter “3.2 System Configuration”.



Check that Primary Language is English



The setup process is starting:

The installation program reboots the server and resumes at “Configuration” steps.



Enter the root password

Click on “Expert Options” and choose MD5 encryption type

As hostname, give the short name.



Configure the network by

- enabling SSH

- disabling IPv6



Read the Notes

After detecting the remaining hardware, the installation process is finished



3.2 System Configuration

3.2.1 Configure Some Kernel Parameters


Read SAP Note 941735 SAP Memory Management for 64 bits Linux systems

Download the sapinit package from the Novell website. The current version is sapinit-3.0-1.4.

The package “sapinit” must be used to setup the kernel memory parameters.

The minimal recommended values of the kernel parameters and shared memory size are pre-defined in the configuration file “/etc/sysconfig/sapinit”.

The SHM filesystem size is configured to about 75% of RAM + swap size, and the minimum value is set to 8 GiB (see note 941735).

Check the results in /etc/sysctl.conf and /etc/security/limits.conf configuration files.

Also, set Oracle recommended system kernel parameters into /etc/sysctl.conf

net.ipv4.ip_local_port_range = 1024 65000

net.core.rmem_default = 262144

net.core.rmem_max = 262144

net.core.wmem_default = 262144

net.core.wmem_max = 262144

3.2.2 Check the Network Configuration

Configure the SAP server with a static IP address.

Check that /etc/hosts does not contain any line with 127.0.0.2.

# hostname Check that the short name is returned

# hostname -f Check that the full qualified domain name is returned

Check the DNS settings

# cat /etc/resolv.conf



3.2.3 Prepare SAP Paths with Adequate Volume Size

Prepare the following volumes

Minimum Size Recommended Size

# mkdir /sapmnt 800 MiB 3 GiB

# mkdir -p /usr/sap 800 MiB 3 GiB

# mkdir -p /oracle/<SID>/102_64 2 GiB 8.5 GiB (SAP note 819830)

If possible, use 8k block size for the Oracle datafile filesystems

# mkfs.xfs -f -b size=8192 /dev/mapper/vgxxxx

Minimum Size Recommended Size

# mkdir -p /oracle/<SID>/mirrlogA 200 MiB 500 MiB

# mkdir -p /oracle/<SID>/mirrlogB 200 MiB 500 MiB

# mkdir -p /oracle/<SID>/oraarch archivelogs Several GB

# mkdir -p /oracle/<SID>/origlogA 200 MiB 500 MiB

# mkdir -p /oracle/<SID>/origlogB 200 MiB 500 MiB

# mkdir -p /oracle/<SID>/saparch brarchive logs

# mkdir -p /oracle/<SID>/sapbackup backup logs

# mkdir -p /oracle/<SID>/sapcheck brconnect logs

# mkdir -p /oracle/<SID>/sapdata1 23 GiB depends on expected data volume




Total /oracle/<SID> 94 GiB 120 GiB

3.2.4 Install Additional System Components

Install java components

# rpm -Uvh jpackage-utils.rpm-1.6.3-18.4.ia64.rpm

# rpm -Uvh java-1.4.2-sun-1.4.2.13-0.2.ia64.rpm

Hugetlb Pages functionality



# rpm -Uvh libhugetlbfs-1.0.1-1.4.ia64.rpm

iostat tool

# rpm -Uvh gd-2.0.32-23.2.ia64.rpm

# rpm -Uvh plotutils-2.4.1-591.2.ia64.rpm

# rpm -Uvh gnuplot-4.0.0-20.2.ia64.rpm

# rpm -Uvh sysstat-6.0.2-16.19.ia64.rpm

xosview

# rpm -Uvh xosview-1.8.2-21.2.ia64.rpm

3.2.5 Install Additional SAP SAPlocales Package

Read SAP Note 171356 Linux Essential Information

Install the saplocales package, as explained in the note.

# rpm -Uvh saplocales-2.4-2.ia64.rpm



4 SAP ERP 6.0 Setup – 1st Part The following basic setup is chosen

Central Instance

Oracle Database

ABAP Stack only

4.1 Preparation

Copy all the needed DVDs onto the server or mount them through NFS

1- SAP Kernel 7.00 SR3 – Linux IA64

2- SAP Netweaver 2004s SR3 Installation Export

3- SAP ERP Central Component 6.0 SR3 DVD 1/2

4- SAP ERP Central Component 6.0 SR3 DVD 2/2

5- Oracle 10.2 – Client Software

6- Oracle 10.2 – Linux IA64

7- Oracle 10.2.0.2 Patch Set – Linux IA64

8- Business Suite 2005 SR3 Installation Master

4.2 Installation

Read SAP Note 958253 Suse Linux Enterprise Server 10 : Installation Notes

Read SAP Note 972262 Inst.NW 7.0(2004s)SR2/Business Suite 2005 SR2-UNIX

Read SAP Note 986578 Oracle Support on Itanium 2 (Montecito) systems



As root, execute sapinst



Unselect “AS Java”



Enter your system ID

Enter the user's passwords.

Enter the database ID :



Check that all the prerequisites are respected.

The swap warning should be solved on a production server!



Select “Advanced DB configuration”

Fill in the database user's passwords.

Select “Create Database Parameters”



Here you can adjust the size of the redo log files

The installation process is ready. Check the data and launch the installation process:



Ask your license key to your internal Solution Manager administrator.



The setup program stops for the database installation



5 Oracle installation

As root, change the system prerequisites

# cd /oracle/stage/102_64/database/install

# vi oraparam.ini

[Certified Versions]

Linux=redhat-3,SuSE-9,SuSE-10,redhat-4,UnitedLinux-1.0,asianux-1,asianux-2

Open a remote connection with ora<SID>

# ssh -Y ora<SID>@server

> cd /oracle/stage/102_64/database/SAP

> ./RUNINSTALLER

Some prerequisites are not verified, because SLES10 is unknown from Oracle 10g.



Logon as root

# /oracle/oraInventory/orainstRoot.sh

# /oracle/<SID>/102_64/root.sh



Click on OK to end the installation



6 SAP ERP 6.0 Setup – 2nd Part

Click on OK. The SAP setup resumes:



Stop the SAP instance

# su - <SID>adm

> stopsap



7 Oracle Upgrade

7.1 Prerequisites Checks

# su - <SID>adm

> stopsap

> logout

Login as Oracle administrator

Stop all the Oracle processes

# su – ora<SID>

> stopdb

> lsnrctl stop

> isqlplusctl stop

> emctl stop dbconsole

> ps -ef | grep ora

root 3145 2993 0 08:51 ? 00:00:02 hald-addon-storage

root 8658 3841 0 09:49 ? 00:00:00 sshd: orabul [priv]

orabul 8664 8658 0 09:49 ? 00:00:00 sshd: orabul@pts/0

orabul 8671 8664 0 09:49 pts/0 00:00:00 -csh

orabul 8901 8671 0 09:58 pts/0 00:00:00 ps -ef

orabul 8902 8671 0 09:58 pts/0 00:00:00 grep ora

7.2 Patchset 10.2.0.2

Get and unzip the patch on the server

# ssh -Y ora<SID>@server

> unzip /sapcd8/LINUX_IA64/p4547817_10202_Linux-IA64.zip

> cd Disk1/install

> vi oraparam.ini

[Certified Versions]

Linux=redhat-3,SuSE-9,SuSE-10,redhat-4,UnitedLinux-1.0,asianux-1,asianux-2



> cd ..

> ./runInstaller



Logon as root and execute the script

# /oracle/<SID>/102_64/root.sh Running Oracle10 root.sh script...

The following environment variables are set as:

ORACLE_OWNER= ora<SID>

ORACLE_HOME= /oracle/<SID>/102_64

Enter the full pathname of the local bin directory: [/usr/local/bin]:

The file "dbhome" already exists in /usr/local/bin. Overwrite it? (y/n) [n]: y

Copying dbhome to /usr/local/bin ...

The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n) [n]: y

Copying oraenv to /usr/local/bin ...

The file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n) [n]: y

Copying coraenv to /usr/local/bin ...

Entries will be added to the /etc/oratab file as needed by

Database Configuration Assistant when a database is created

Finished running generic part of root.sh script.

Now product-specific root actions will be performed.



# su – ora<SID>

> sqlplus / as sysdba

SQL> STARTUP NOMOUNT

The size should be at least 150 Mo for these 2 parameters

SQL> SHOW PARAMETER SHARED_POOL_SIZE

SQL> SHOW PARAMETER JAVA_POOL_SIZE

If necessary, set the parameters

SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;

SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;

SQL> SHUTDOWN

Upgrade the database dictionary

SQL> shutdown



SQL> startup upgrade

SQL> spool patch.log

SQL> @?/rdbms/admin/catupgrd.sql ...

PL/SQL procedure successfully completed.

DOC>#######################################################################

DOC>#######################################################################

DOC>

DOC> The above PL/SQL lists the SERVER components in the upgraded

DOC> database, along with their current version and status.

DOC>

DOC> Please review the status and version columns and look for

DOC> any errors in the spool log file. If there are errors in the spool

DOC> file, or any components are not VALID or not the current version,

DOC> consult the Oracle Database Upgrade Guide for troubleshooting

DOC> recommendations.

DOC>

DOC> Next shutdown immediate, restart for normal operation, and then

DOC> run utlrp.sql to recompile any invalid application objects.

DOC>

DOC>#######################################################################

DOC>#######################################################################

DOC>#

SQL> spool off

SQL> quit

Check that no error occurred

> grep ORA- patch.log DOC> The following statement will cause an "ORA-01722: invalid number"

DOC> The following statement will cause an "ORA-01722: invalid number"


DOC> The following statements will cause an "ORA-01722: invalid number"


DOC> The following PL/SQL block will cause an ORA-20000 error and

DOC> The following PL/SQL block will cause an ORA-20000 error and




SQL> shutdown immediate

Database closed.

Database dismounted.

ORACLE instance shut down.

SQL> startup

SQL> @?rdbms/admin/utlrp.sql

...

PL/SQL procedure successfully completed.

SQL> quit

Start SAP

> lsnrctl start

> logout

# su – <SID>adm

> startsap

Connect to SAP and check the database with DB13 and DB14

Shutdown SAP

> stopsap



7.3 Opatch Upgrade

Read SAP Note 841728 Oracle Database 10g – Software installation problems 10.2.0

Upgrade opatch to the lastest version

# su – ora<SID>

> cd $ORACLE_HOME

> rm -rf OPatch

Extract the new Opatch version files

> unzip /oracle/stage/p4898608_10202_GENERIC_v5_opatch_10.2.0.2.5.zip

inflating: OPatch/docs/FAQ

inflating: OPatch/docs/Users_Guide.txt

inflating: OPatch/docs/Prereq_Users_Guide.txt

inflating: OPatch/jlib/opatch.jar

inflating: OPatch/jlib/opatchutil.jar

inflating: OPatch/jlib/opatchprereq.jar

inflating: OPatch/opatchprereqs/opatch/opatch_prereq.xml

inflating: OPatch/opatchprereqs/opatch/rulemap.xml

inflating: OPatch/opatchprereqs/opatch/runtime_prereq.xml

inflating: OPatch/opatchprereqs/oui/knowledgesrc.xml

inflating: OPatch/opatchprereqs/prerequisite.properties

inflating: OPatch/opatch

inflating: OPatch/opatch.bat

inflating: OPatch/opatch.pl

inflating: OPatch/opatch.ini

inflating: OPatch/emdpatch.pl

inflating: OPatch/README.txt

> cd OPatch/

> ./opatch version

Invoking OPatch 10.2.0.2.5

OPatch Version: 10.2.0.2.5

OPatch succeeded.



7.4 Mopatch Installation

Read SAP Note 1027012 MOPatch – Install multiple Oracle Patchs in one run

Upgrade mopatch to the lastest version 1.8

Extract the files

> unzip mopatch-1.8.zip

Archive: mopatch.zip

creating: MOPatch/

inflating: MOPatch/mopatch.sh

inflating: MOPatch/readme.txt

7.5 CPU Patchs

Read SAP Note 1140644 CPU Patches January 2008 (Oracle Critical Update Program)

As of Oracle 10.2 – 10.2.0.2, installing CPU patches is not recommended, because it involves some risks, as defined in note 1140644

======================================

We recommend that ALL SAP customers import the CPU patch only if it is absolutely necessary. Risks: The main risk when you install the CPU is that, as soon as SAP provides a new patch, this patch could clash with the CPU (it may not clash). If a clash occurs, you must decide between the CPU and the new patch.

======================================

7.6 Instantclient

Read SAP Note 871096 Oracle Database 10g – Patch sets/patches for 10.2.0

Read SAP Note 819829 Oracle Database 10g – Instant Client 10.x on Unix

When running Oracle 10.2.0.2, the only InstantClient must be in version 10.2.0.2.

# su - <SID>adm

Check LD_LIBRARY_PATH. It should be

LD_LIBRARY_PATH=/usr/sap/<SID>/SYS/exe/run:/oracle/client/10x_64/instantclient

> stopsap



> cd /oracle/client/10x_64

> SAPCAR -xvf /oracle/stage/OCL10264.SAR

SAPCAR: processing archive /oracle/stage/OCL10264.SAR (version 2.00)

x dbclient.lst

x instantclient_10201

x instantclient_10201/libocijdbc10.so

x instantclient_10201/classes12.jar

x instantclient_10201/libociei.so

x instantclient_10201/ojdbc14.jar

x instantclient_10201/libnnz10.so

x instantclient_10201/libclntsh.so.10.1

x instantclient_10201/libocci.so.10.1

SAPCAR: 9 file(s) extracted

Check that the link /oracle/client/10x_64/instantclient links to the right directory

> ls -l instantclient

instantclient -> instantclient_10201

As <sid>adm and ora<sid>, check that the DBSL library can load the new instantclient libraries

> cdexe

> ldd dboraslib.so linux-gate.so.1 => (0xa000000000000000)

libdl.so.2 => /lib/libdl.so.2 (0x20000008001b0000)

librt.so.1 => /lib/librt.so.1 (0x20000008001c8000)

libclntsh.so.10.1 => /oracle/client/10x_64/instantclient/libclntsh.so.10.1 (0x20000008001e8000)

libnnz10.so => /oracle/client/10x_64/instantclient/libnnz10.so (0x20000008023d0000)

libc.so.6.1 => /lib/libc.so.6.1 (0x2000000802754000)

libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x20000008029a4000)

libm.so.6.1 => /lib/libm.so.6.1 (0x2000000802b10000)

libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x2000000802be0000)

libpthread.so.0 => /lib/libpthread.so.0 (0x2000000802c00000)

/lib/ld-linux-ia64.so.2 (0x2000000800000000)

libnsl.so.1 => /lib/libnsl.so.1 (0x2000000802c3c000)

libunwind.so.7 => /lib/libunwind.so.7 (0x2000000802c74000)

Check that R3trans can connect to the database



# su - <sid>adm

> startdb

> R3trans -x

This is R3trans version 6.14 (release 700 - 14.02.08 - 14:55:00).

unicode enabled version

R3trans finished (0000).

> stopdb

7.7 Patches Installation with mopatch

Read SAP Note 871096 Oracle Database 10g : Patch sets/patches for 10.2.0

According to the note 871096, the following patches should be installed as of 16/04/2008

p3748430 p4952782 p5530958 p6435823p4271217 p5063279 p5618049 p6447320p4518443 p5092134 p5635254 p6455161p4604970 p5103126 p5636728 p6663258p4638550 p5188321 p5941030 p6729801p4668719 p5308692 p6005996 p6740811p4707226 p5345999 p6024730 p6771608p4864648 p5363584 p6046043 p6819785p4883635 p5369855 p6153847 p4899479 p5442919 p6340979

and these generic patches

p4638550

p4864648

p5635254

p6005996

p6046043

p6435823

Put the non-generic patch zip files in a single directory (for example /oracle/<SID>/patchs)

# su – ora<SID>

> mkdir patchs

... (file transfers)

> cd patchs

Execute a test run (dry-run mode “-d”). The database can still be online during this run.

> /bin/sh $ORACLE_HOME/MOPatch/mopatch.sh -v -d



...

Check that all patchs are checked successfully

Checked 25 of 25 patches successfully:

...

Shutdown the database and oracle processes

SQL> shutdown

Database closed.

Database dismounted.

ORACLE instance shut down.

SQL> quit

> lsnrctl stop

Execute the installation run

> /bin/sh $ORACLE_HOME/MOPatch/mopatch.sh -v

Check the output log for eventual errors

Patch Installation Status:

--------------------------

Installed 25 of 25 patches successfully:

...

Link Status:

------------

Link script "./link.sh" executed successfully.

Also, check that no errors occurred in the ouput log and in $ORACLE_HOME/cfgtoollogs/mopatch

Install the generic patches

Unzip and Install each of the 6 generic patchs

> opatch apply

Follow these steps required by patch 6435823


SQL> startup upgrade



SQL> @?/rdbms/admin/prvtstas.plb

SQL> @?/rdbms/admin/prvtstat.plb

SQL> shutdown

SQL> quit



8 Post-installation Check

Startup SAP

# su - <SID>adm

> startsap

Check that the installation process correctly finished - Transaction SICK



Perform a database check

Open the database planning DB13, and add a “Check database” task

Click on “Start immediately”

You can check the result in the database logs DB14



Click on “brconnect” and wait for the check to finish.

Open the details



9 Database Configuration

9.1 Optionally, on a TEST System

In case of a test system, you can disable archivelog

Stop SAP system. Then login as ora<SID>

# su – ora<SID>

> startdb

> brtools -c

1- Instance Management

3- Alter database instance

3- Alter database action: noarchlog

4- Database instance: <SID>

c- continue

BR0291I BRSPACE will be started with options '-p initBUL.sap -c -l E -f dbalter -a noarchlog -i SID'

9.2 Oracle Configuration

Check Oracle parameters according to the SAP note 830576.

Check that no obsolete parameter is configured

SQL> select name from v$obsolete_parameter where isspecified = 'true';

no rows selected

If some parameters are listed, they should be deleted from the spfile with this command

SQL> alter system reset <xxxx> scope=spfile;

A SQL script “parameters.txt” is attached to the note 830576, which allows checking Oracle parameters easily. Execute SAP transaction SE38, and paste the SQL code:



Execute the SQL request; which check all the parameters according to the note and Oracle database version.

Check and correct all parameters which are not “ok” (above yellow line)



alter system set "_bloom_filter_enabled"=false scope=both;

alter system set event = '10027 trace name context forever, level 1', '10028 trace name context forever, level 1', '10162 trace name context forever, level 1', '10183 trace name context forever, level 1', '10183 trace name context forever, level 1', '10629 trace name context forever, level 1', '10891 trace name context forever, level 1', '14532 trace name context forever, level 1', '38068 trace name context forever, level 100', '38087 trace name context forever, level 1' scope = spfile;

alter system set max_dump_file_size = 20000 scope=both;

alter system set optimizer_index_caching = 50 scope=both;

alter system set optimizer_index_cost_adj = 20 scope=both;

alter system set parallel_threads_per_cpu = 1 scope=both;



9.3 Oracle Authorizations

Read SAP Note 834917 Oracle Database 10g – New database role SAPCONN

Read SAP Note 134592 Importing the SAPDBA role

Read SAP Note 700548 FAQ : Oracle authorizations

Read SAP Note 400241 Problem with ops$ or sapr3 connect to Oracle

With user ora<sid>, R3trans is not able to connect to the database

# su – ora<SID>

> R3trans -x



2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'SID'"


Adjust the configuration for ora<SID>


SQL> create synonym ops$ora<SID>.sapuser for ops$<SID>adm.sapuser;

SQL> grant select, update on ops$ora<SID>.sapuser to ops$ora<SID>;

Now, ora<sid> can connect to the database

> R3trans -x




> R3trans -d






9.4 Configure the TNS Listener

Read SAP Note 562403 FAQ : Oracle Net

When SAP is started, we can see that the SAP work processes connect to the database through TCP/IP.

> netstat -anp | grep 1527 tcp 0 0 10.17.214.174:60467 10.17.214.174:1527 ESTABLISHED 25598/dw.sapBUL_DVE

tcp 0 0 10.17.214.174:60464 10.17.214.174:1527 ESTABLISHED 25594/dw.sapBUL_DVE




tcp 0 0 10.17.214.174:1527 10.17.214.174:60463 ESTABLISHED 25600/oracleBUL




...

In a 2-tiers mode, all databases provide an IPC (shared memory) access mode.

This mode is not activated by default when SAP is installed. This is done by modifying the tnsnames.ora file.

Add one line to configure IPC in these 2 files

/sapmnt/<SID>/profile/oracle/tnsnames.ora

/oracle/<SID/102_64/network/admin/tnsnames.ora

# su – ora<SID>

> cdpro

> cd oracle/<SID/102_64/network/admin/

> vi tnsnames.ora SID.WORLD=

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = IPC)(KEY = <SID>.WORLD))

(ADDRESS =

(COMMUNITY = SID.WORLD)

(PROTOCOL = TCP)

(HOST = ls3170)



(PORT = 1527)

)

)

(CONNECT_DATA =

(SID = SID)

(GLOBAL_NAME = SID.WORLD)

)

)

Check the result with netstat

> stopsap r3 && startsap

> netstat -anp | grep 1527

tcp 0 0 0.0.0.0:1527 0.0.0.0:* LISTEN -

or check the result in the listener log

> cd $ORACLE_HOME/network/log

> tail listener.log ...

09-AUG-2007 15:56:08 * (CONNECT_DATA=(SID=BUL)(GLOBAL_NAME=BUL.WORLD)(CID=(PROGRAM=dw.sapBUL_DVEBMGS00)(HOST=ls3170)(USER=buladm))) * (ADDRESS=(PROTOCOL=ipc)(KEY=<SID>.WORLD)) * establish * BUL * 0



9.5 Activate Asynchronous I/O in Oracle

Read SAP Note 793113 FAQ : Oracle I/O configuration

Check that the libraries “libaio” and “libaio-devel” are installed

# su – ora<SID>

> rpm -qa | grep libaio

libaio-0.3.104-14.2

libaio-devel-0.3.104-14.2

> cd $ORACLE_HOME/rdbms/lib

> ln -s /usr/lib/libaio.so skgaio.o

> make -f ins_rdbms.mk async_on

Check that the binary is now linked to the library

> cd $ORACLE_HOME/bin

> ldd oracle linux-gate.so.1 => (0xa000000000000000)

libskgxp10.so => /oracle/<SID>/102_64/lib/libskgxp10.so (0x200000000004c000)

libhasgen10.so => /oracle/<SID>/102_64/lib/libhasgen10.so (0x20000000000a0000)

libskgxn2.so => /oracle/<SID>/102_64/lib/libskgxn2.so (0x200000000038c000)

libocr10.so => /oracle/<SID>/102_64/lib/libocr10.so (0x20000000003a0000)

libocrb10.so => /oracle/<SID>/102_64/lib/libocrb10.so (0x20000000004fc000)

libocrutl10.so => /oracle/<SID>/102_64/lib/libocrutl10.so (0x20000000005e4000)

libjox10.so => /oracle/<SID>/102_64/lib/libjox10.so (0x20000000006b0000)

libclsra10.so => /oracle/<SID>/102_64/lib/libclsra10.so (0x20000000014a8000)

libdbcfg10.so => /oracle/<SID>/102_64/lib/libdbcfg10.so (0x20000000014d0000)

libnnz10.so => /oracle/<SID>/102_64/lib/libnnz10.so (0x2000000001500000)

libaio.so.1 => /usr/lib/libaio.so.1 (0x2000000001880000)

libdl.so.2 => /lib/libdl.so.2 (0x2000000001894000)

libpthread.so.0 => /lib/libpthread.so.0 (0x20000000018ac000)

libnsl.so.1 => /lib/libnsl.so.1 (0x20000000018ec000)

libm.so.6.1 => /lib/libm.so.6.1 (0x2000000001924000)

libc.so.6.1 => /lib/libc.so.6.1 (0x20000000019f4000)

/lib/ld-linux-ia64.so.2 (0x2000000000000000)

Check that the asynchronous feature of Oracle is enabled



− filesysemio_options = 'setall'

− disk_asynch_io = true


SQL> show parameter filesystemio_options

NAME TYPE VALUE

------------------------------------ ----------- ------------------------------

filesystemio_options string setall

SQL> show parameter disk_asynch_io

NAME TYPE VALUE

------------------------------------ ----------- ------------------------------

disk_asynch_io boolean TRUE

# grep kio /proc/slabinfo kioctx 64 165 256 15 1 : tunables 120 60 8 : slabdata 11 11 0

kiocb 16 31 128 31 1 : tunables 120 60 8 : slabdata 1 1 0

Check that the first two columns have none zero values.



9.6 Memory Configuration

Suppose we decide to allocate 2 GB of memory to Oracle.

We have to set up these values in the Oracle instance:

SGA max = 2 GB

Shared Pool = 500 MB

Buffer Cache = 1300 MB

Java Pool = 160 MB

# su – ora<SID>

> brtools -c

1- Instance Management

4- Alter database parameters

3- Alter parameter action: change

4- Database parameter: sga_max_size

c- continue

5- New parameter value: 2147483648

c- continue

4- Database parameter: shared_pool_size

c- continue


c- continue

4- Database parameter: db_cache_size

c- continue


c- continue

4- Database parameter: java_pool_size

c- continue


c- continue



9.7 Configuring Hugepages

Determine the hugepage size

# cat /proc/meminfo

...

Hugepagesize: 262144 kB

In this IA64 system, the hugepage size is 256 MB. We need 8 hugepages for Oracle SGA.

Determine the “oper” group ID

# cat /etc/group | grep oper

oper:!:1003:buladm,orabul

We need to authorize the group 1003 to use hugepages. Configure these 2 parameters:

# vi /etc/sysctl.conf

vm.nr_hugepages = 8

vm.hugetlb_shm_group = 1003

It is advisable to reboot the server, so that the memory allocation happens when most of the main memory is free

# reboot

Check that the hugepage memory is reserved

# cat /proc/meminfo

...

HugePages_Total: 8 HugePages_Free: 8 HugePages_Rsvd: 0


8 hugepages are now available for Oracle SGA

Authorize the oper group to use this memory

# vi /etc/security/limits.conf

@oper soft memlock 2359296

@oper hard memlock 2359296



Restart the database

> stopdb && startdb

Check that the hugepage memory is used by Oracle. Hugepages_Free should be lower than HugePages_Total

> cat /proc/meminfo

...

HugePages_Total: 8 HugePages_Free: 0

HugePages_Rsvd: 0


9.8 Error ORA-14508

Read SAP Note 23345 Consistency check of ORACLE database

Read SAP Note 514178 ORA-14508 when validating partitioned tables

Verifying the database gives some ORA-14508 errors.

According to the note 514178, the table INVALID_ROWS is missing from the <sid>adm schema.

Follow the procedure given in the note.

# su - ora<SID>


SQL> @?/rdbms/admin/utlvalid.sql

Table created.

SQL> grant all on invalid_rows to public;

SQL> create synonym ops$<sid>adm.invalid_rows for invalid_rows;

Synonym created.

9.9 Configure Default Tablespace

Read SAP Note 969674 Oracle Database 10g – Default Permanent Tablespace PSAPSAUX

As explained in this note, it is advisable to set the SAP users' default tablespace to PSAPSAUX.



First create the tablespace

# su – ora<SID>

> mkdir /oracle/<SID>/sapdata1/saux_1


SQL> CREATE TABLESPACE PSAPSAUX

DATAFILE '/oracle/<SID>/sapdata1/saux_1/saux.data1'

SIZE 200M REUSE AUTOEXTEND OFF

EXTENT MANAGEMENT LOCAL AUTOALLOCATE

SEGMENT SPACE MANAGEMENT AUTO;

SQL> ALTER DATABASE DEFAULT TABLESPACE PSAPSAUX;

Check the default tablespace of SAP users. It should be either PSAPSR3USR or PSAPSAUX

SQL> select username, default_tablespace from dba_users order by username; USERNAME DEFAULT_TABLESPACE

------------------------------ ------------------------------

DBSNMP SYSAUX

DIP PSAPSAUX

MGMT_VIEW PSAPSAUX

OPS$BULADM PSAPSAUX

OPS$ORABUL PSAPSAUX

OPS$SAPSERVICEBUL PSAPSAUX

OUTLN SYSTEM

SAPSR3 PSAPSR3USR

SYS SYSTEM

SYSMAN SYSAUX

SYSTEM SYSTEM

TSMSYS PSAPSAUX

12 rows selected.



10 SAP Kernel Upgrade Valid as of April 2008

CHECK SAP WEBSITE FOR UP TO DATE VERSIONS

Shutdown completely SAP application

# su - <SID>adm

> stopsap

> saposcol -k

> logout

# rcsapinit stop

Download from http://service.sap.com/ and upload to the SAP server the following files

- Database independent files (Kernel 7.00 Unicode) SAPEXE_146-20001223.SAR (04/02/2008)

ccmagent_18-20001223.sar

dsrlib_18-20001223.sar

dw_156-20001223.sar

enserver_152-20001223.sar

R3trans_151-20001223.SAR

rslgcoll_4-20001223.sar

rslgsend_4-20001223.sar

saposcol_58-20001223.sar

sapwebdisp_156-20001223.sar

sapxpg_9-20001223.sar

tp_156-20001223.sar

- Database dependent files SAPEXEDB_146-20001223.SAR

DBATL700O10_33-20001223.SAR

lib_dbsl_152-20001223.sar

R3ldctl_16-20001223.SAR

R3load_84-20001223.SAR

R3szchk_14-20001223.SAR

Backup the current binaries

# cd /sapmnt/<SID>



# cp -rp exe exe_bak

# cd exe

Copy SAPCAR into another directory from the path

# cp SAPCAR /usr/local/bin/SAPCAR

# cd /usr/local/bin

# ln -s SAPCAR sapcar

Extract each SAR file into this exe directory (sapexe and sapexedb first)

> cd /sapmnt/<SID>/exe

> /usr/local/bin/sapcar -xvf ~/SAPEXE_*.SAR

> /usr/local/bin/sapcar -xvf ~/SAPEXEDB_*.SAR

Then the other SAR files

> /usr/local/bin/sapcar -xvf ~/<xxxx>.SAR

Update also this sapcar

> cp /sapmnt/<SID>/exe/SAPCAR /usr/local/bin/SAPCAR

Restore the authorizations

# cd /sapmnt/<SID>/exe

# ./saproot.sh <SID>

Preparing /usr/sap/<SID>/SYS/exe/run/brbackup ...

Preparing /usr/sap/<SID>/SYS/exe/run/brarchive ...

Preparing /usr/sap/<SID>/SYS/exe/run/brconnect ...

Preparing /usr/sap/<SID>/SYS/exe/run/brtools ...

Preparing saposcol ...

Preparing icmbnd ...

done



11 SAP Configuration

11.1 Profile Adjustment – Memory Related Parameters

Read SAP Note 941735 SAP Memory management for 64-bit Linux systems

Read SAP Note 146289 Parameter recommendations for 64-bit SAP kernel

Read SAP Note 835474 More than 32 GB extended memory

SAP uses shared memory to store common data, usable by the work processes.

Set the following parameters

Usage Parameter Default value Adjusted

Memory mapping es/implementation map std

Nametab Table COUNT rsdb/ntab/entrycount 20000 40000

Nametab Table SIZE

Nametab Fields COUNT rsdb/ntab/entrycount see Table

Nametab Fields SIZE rsdb/ntab/ftabsize 30000 40000

Nametab Short NTAB COUNT rsdb/ntab/entrycount see Table

Nametab Short NTAB SIZE rsdb/ntab/sntabsize 3000

Nametab Initial Record COUNT rsdb/ntab/entrycount see Table

Nametab Initial Record SIZE rsdb/ntab/irbdsize 6000

Program (ABAP buffer) abap/buffersize 150000 500000 or more (depends on usage)

CUA SIZE rsdb/cua/buffersize 3000

Screen COUNT sap/bufdir_entries 2000

Screen SIZE zcsa/presentation_buffer_area 4400000

Calendar COUNT zcsa/calendar_ids 200

Calendar SIZE zcsa/calendar_area 500000

OTR COUNT rsdb/otr/max_objects 2000

OTR SIZE rsdb/otr/buffersize_kb 4096

Table generic key COUNT zcsa/db_max_buftab 5000 20000

Table generic key SIZE zcsa/table_buffer_area 30000000

Table single record COUNT rtbb/max_tables 500

Table single record SIZE rtbb/buffer_length 10000

Export/Import buffer COUNT rsdb/obj/max_objects 2000 20000

Export/Import buffer SIZE rsdb/obj/buffersize 8192 40000

Export/Import SHM COUNT rsdb/esm/max_objects 2000



Export/Import SHM SIZE rsdb/esm/buffersize 4096

Roll Area ztta/roll_area 6500000

Page Area

Extended Memory em/initial_size_MB 6912 set to 75% (RAM + Swap)

Heap Memory

11.2 Transport

Transport configuration can be done with transaction STMS, to integrate this new system in its landscape.

Log in into client 000, transaction STMS.

If this system is the first of a new domain, create the relevant domain, and add the system as a domain controller.

Otherwise, enter the domain parameters so that the system can register against it.

11.3 Backup

Read note 171356 Linux Essential Information

At this moment, a whole or full database backup is highly recommended, as well as a complete local filesystem backup.

Adjust the configuration file “/oracle/<SID>/102_64/dbs/init<SID>.sap” according to your needs.

However, it is recommended to change at least the following parameters:

compress_cmd = "gzip -c $ > $"

uncompress_cmd = "gunzip -c $ > $"

tape_copy_cmd = dd

disk_copy_cmd = dd



11.4 SAP Configuration

Correct the languages configuration with SE38 – RSCPINST

English Language is the only configured language

Click on “Current NLS Configuration”



Come back to the configuration page, add the German language

Click on “Activate” to validate the new configuration



11.5 Recommended SAP Note

When starting a SAP instance, you may get this error

You can correct this error by:

− applying SAP Note 1120534

− or importing the Support Package SAPKB70015



12 Annex – OEM Installation Read SAP Note 105047 Support for Oracle functions in the SAP environment

This tool is not supported by SAP, and no configuration change should be done with this tool.

However, OEM gives a good overview of an Oracle database, especially with the performance tab:

How to setup this tool

# su – ora<SID>

> emca -config dbcontrol db -repos create

STARTED EMCA at Aug 8, 2007 4:44:01 PM

EM Configuration Assistant, Version 10.2.0.1.0 Production

Copyright (c) 2003, 2005, Oracle. All rights reserved.

Prepare to enter the following information:

Database SID:

Listener port number:

Password for SYS user:

Password for DBSNMP user:

Password for SYSMAN user:



Email address for notifications (optional):

Outgoing Mail (SMTP) server for notifications (optional):

-----------------------------------------------------------------

You have specified the following settings

Database ORACLE_HOME ................ /oracle/<SID>/102_64

Database hostname ................ xxxxxxxxxxxxx

Listener port number ................ 1527

Database SID ................ SID

Email address for notifications ...............

Outgoing Mail (SMTP) server for notifications ...............

-----------------------------------------------------------------

Do you wish to continue? [yes(Y)/no(N)]: y

Aug 8, 2007 4:47:21 PM oracle.sysman.emcp.EMConfig perform

INFO: This operation is being logged at /oracle/<SID>/102_64/cfgtoollogs/emca/<SID>/emca_2007-08-08_04-44-01-PM.log.

Aug 8, 2007 4:47:24 PM oracle.sysman.emcp.EMReposConfig createRepository

INFO: Creating the EM repository (this may take a while) ...

Aug 8, 2007 4:51:40 PM oracle.sysman.emcp.EMReposConfig invoke

INFO: Repository successfully created

Aug 8, 2007 4:51:45 PM oracle.sysman.emcp.util.DBControlUtil startOMS

INFO: Starting Database Control (this may take a while) ...

Aug 8, 2007 4:53:31 PM oracle.sysman.emcp.EMDBPostConfig performConfiguration

INFO: Database Control started successfully

Aug 8, 2007 4:53:31 PM oracle.sysman.emcp.EMDBPostConfig performConfiguration

INFO: >>>>>>>>>>> The Database Control URL is http://server:1158/em <<<<<<<<<<<

Enterprise Manager configuration completed successfully

FINISHED EMCA at Aug 8, 2007 4:53:31 PM

Stop and start this management application with these commands

# su - ora<SID>

> emctl stop dbconsole

> emctl start dbconsole

Then browse into the application at this address: Erreur ! Référence de lien hypertexte non valide.

This management feature can be uninstalled with the following command

> emca -deconfig dbcontrol db -repos drop



Related Content SAP on Linux

https://www.sdn.sap.com/irj/sdn/linux

Supported Platforms

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/792dd957-0d01-0010-319b-e1211e5c66b0

SAP on Linux Forum

https://www.sdn.sap.com/irj/sdn/forum?forumID=189


https://www.sdn.sap.com/irj/sdn/index



https://www.sdn.sap.com/irj/sdn/index



Copyright © 2008 SAP AG. All rights reserved.

No part of this publication 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

These materials are provided “as is” without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages.

Any software coding and/or code lines/strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

guideline for setting-up a sap erp 6.0 system on linux sles 10 oracle

Documents