Database Upgrade Guide Upgrade to Oracle Database 11g Release 2 (11.

2): UNIX
Target Audience ■ Technology Consultants ■ System Administrators

PUBLIC Document version: 1.14 – 2010-09-10

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document. You can find the latest version at the following location: http://service.sap.com/instguides Database Upgrades Oracle The following table provides an overview of the most important document changes.
Version Date Description

1.14 1.13 1.12 1.11 1.10 1.01 1.00

2010-09-10 2010-08-25 2010-08-03 2010-06-15 2010-06-09 2010-04-27 2010-04-01

Chapter Changing the Location of the JDBC Driver added Various corrections Various corrections Change to section Updating BR*Tools Major update including upgrade from Oracle 9.2.0.8 Various corrections Initial Version

2/50

PUBLIC

2010-09-10

Table of Contents

Chapter 1 1.1 1.2 1.3 Chapter 2 2.1 2.2 2.3 2.4 Chapter 3 3.1 3.2 3.3 3.4 3.4.1 3.4.2 3.4.3 3.4.4 3.4.5 3.4.6 3.4.7 3.5 3.6 3.7 3.8 Chapter 4 4.1 4.2

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Notes for the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . More Information on SAP Service Marketplace . . . . . . . . . . . . . . . . . . . . . . . . .

5 6 6 7

Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Checking the Original Version of Your Database . . . . . . . . . . . . . . . . . . . . . . . . 9 Checking Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . 9 Reviewing the Oracle-Specified Kernel Parameters and Shell Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Checking Additional Requirements for the Upgrade . . . . . . . . . . . . . . . . . . . . 11 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Correct UNIX Users, Groups, and Authorizations . . . . . . . . . . . Checking the Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Prerequisites for the Oracle Universal Installer . . . . . . . . . . . . . Database Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking and Setting the Environment Variables . . . . . . . . . . . . . . . . . . . . . . Backing Up the Oracle Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the Oracle Universal Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Current Patch Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Required SAP Bundle Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Symbolic Link for the Data Shared Library . . . . . . . . . . . . . . . . . . . Copying and Adapting the SQL*Net Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the Pre-Upgrade Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the Pre-Upgrade Scripts (Oracle 9.2.0.8) . . . . . . . . . . . . . . . . . . . . . . Checking the SAP System Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating the Oracle Instant Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 13 13 15 16 16 18 18 20 20 21 21 22 23 24 25

Oracle Database Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Backing Up the Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Shutting Down the SAP System and Oracle Listener Process . . . . . . . . . . . . . . 27

2010-09-10

PUBLIC

3/50

4.3 4.3.1 4.3.2 4.3.3 Chapter 5 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 5.13 5.14 5.15 5.16 5.17

Database Structure Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the oratab Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Database Upgrade Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Database Upgrade Assistant (Oracle 9.2.0.8) . . . . . . . . . . . . . . . . . Post-Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finalizing the Environment of the ora<dbsid>User . . . . . . . . . . . . . . . . . . . . Checking the Upgraded Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating BR*Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Post-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing Up the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Listener Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Renaming the Old $ORACLE_HOME/bin Directory . . . . . . . . . . . . . . . . . . . . Renaming the Alert Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Read Authorization of the <sapsid>adm User . . . . . . . . . . . . . Updating the SAP Kernel from 640_REL to 640_EX2 . . . . . . . . . . . . . . . . . . . . Changing the Environment for the <sapsid>adm user . . . . . . . . . . . . . . . . . . Updating the SQL*Net Configuration Files for the <sapsid>adm and ora<sid> Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking SAP Profile Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Location of the JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the National Character Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the New Features for Oracle Database 11g Release 2 (11.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

28 28 29 31 35 35 36 36 37 38 38 38 39 39 39 39 40 41 41 44 45 45

4/50

PUBLIC

2010-09-10

1

Introduction

1 Introduction

This documentation explains how to upgrade the Oracle database for the SAP system on the UNIX operating system: ■ From Oracle 9.2.0.8 and Oracle Database 10g Release 2 (10.2.0.4) or higher ■ To Oracle Database 11g Release 2 (11.2)
CAUTION

Oracle 11.2 is only supported for SAP systems with an EX2 kernel. If you have a 640_REL kernel, you need to switch to the 640_EX2 kernel immediately after the database upgrade to Oracle 11.2. We do not support running a 640_REL kernel with the Oracle 11.2 database. This documentation covers upgrades from both Oracle 9.2.0.8 and 10.2.0.4 to Oracle 11. If your source database is Oracle 9.2.0.8, there are some differences in the procedure and these are clearly marked in the text.
Implementation Considerations

■ For more information about implementation considerations, including the most important SAP Notes for the upgrade, see Planning [page 9]. ■ Be sure to read the relevant SAP Notes before beginning the upgrade. These notes contain the most recent information about the upgrade, as well as corrections to the documentation. You can find the most recent version of the SAP Notes at http://service.sap.com/notes ■ You might find useful information for the upgrade in the following Oracle documentation: ● Oracle 11gR2 Upgrade Companion [ID 785351.1] ● Operating Systems Installation and Configuration Requirements Quick Reference (8.0.5 to 11.2) [ID 169706.1] ■ You use the tools Oracle Universal Installer (OUI), Oracle SQL*Plus, and Oracle Database Upgrade Assistant (DBUA) to perform the upgrade.
NOTE

Make sure you are using the Oracle Universal Installer (OUI) shipped with the installation CDs for Oracle Database 11g Release 2 (11.2).
Naming Conventions

■ We use <DBSID> for the database instance identifier and <SAPSID> for the SAP system identifier. These can be different if your: ● Database system uses Oracle Real Application Clusters (RAC) ● SAP system uses Multiple Components in One Database (MCOD)

2010-09-10

PUBLIC

5/50

2.1 1.2. see the New Features documentation from Oracle.2.0: Patches/ Patchcollections for 11.0: Troubleshooting the Software Installation Oracle 11.2.2.2 SAP Notes for the Upgrade Make sure that you read the following SAP Notes: Number Title Remarks 1431800 1454627 1398634 1431798 Oracle 11. which replaces the native CONNECT role from Oracle 1431796 1431797 1431799 1431795 1431793 1431794 850306 134592 834917 6/50 PUBLIC 2010-09-10 .0 Upgrade Scripts Oracle 11.0: Database Parameter Settings Oracle 11.0: Current Patch Set Oracle 11.2.2.0 Required for upgrading Oracle client software to Oracle 11g Release 2 (11.2.1 Oracle 11.1 Describes the shell and SQL upgrade scripts for 11.2) Describes the current Oracle security fixes Describes how to update the SAPDBA role after the upgrade Describes the new SAPCONN role.1 Introduction New Features 1.0: Troubleshooting the Database Upgrade Oracle 11.com 1.0: Instant Client Oracle Critical Patch Update Program Importing the SAPDBA role (sapdba_role.oracle.2.0: Central Technical Note Additional Info / Corrections to Oracle 11g Upgrade Guide Oracle Database 11g: Integration into the SAP environment Oracle 11.2. You can access the complete Oracle documentation at the Oracle Technology Network (OTN) website.2).sql) Oracle Database 10g: New database role SAPCONN Provides a starting point for information about Oracle 11g with multiple links to notes on Oracle 11g.0.1 New Features For the complete list of new features of the Oracle Database 11g Release 2 (11.2. Required late-breaking information Provides information about integration of Oracle 11g products and options within SAP Provides information about Oracle initialization parameters that need to be reset to their default values or that need to be removed Describes software installation problems and solutions or workarounds Describes database upgrade problems and solutions or workarounds Describes the current Oracle patch set Lists the status of Oracle patch sets and interim patches for 11. RECOMMENDATION We recommend that you check the most important new features in the Oracle documentation since some new features might affect the operation of your production system. which you can find here: http://otn.0.

com/irj/sdn/ Title SAP Notes Oracle Database Administration None SAP Database Guide: Oracle SAP ON ORACLE KNOWLEDGE CENTER Documentation ora SAP None Upgrade to Oracle Database <Version>: UNIX SAP Software Distribution Center Oracle Database Upgrade Guide – that is.com/ instguides Database Upgrades Oracle https://service.sap.sap.com/notes www.sdn.sap.com/swdc http://service.3 Introduction More Information on SAP Service Marketplace Title Remarks Number 839182 1027012 1430669 Using OPatch to install Oracle patches MOPatch – Install Multiple Oracle Patches in One Run BR*Tools Support for Oracle 11g Describes how to use OPatch with Oracle – Windows only Describes how to use MOPatch with Oracle – UNIX only Describes the support offered by BR*Tools for Oracle 11g 1.sap.com Oracle Patches Download Area oracle-download 2010-09-10 PUBLIC 7/50 .3 More Information on SAP Service Marketplace You can find more information as following on SAP Service Marketplace: Description Internet Address http://service.sap. the guide you are now reading Oracle patch download area http://service.1 1.

.This page is left blank for documents that are printed on both sides.

you must complete this procedure before running the Oracle Universal Installer [page 18].4 or later. make sure that you perform a test upgrade on your backup system.0.1 Checking the Original Version of Your Database You need to check the original version of the database you want to upgrade and.0. You check the hardware and software requirements [page 9]. 4.2 2. You check the original version of your database [page 9]. if necessary.2) upgrade at the Oracle Technology Network (OTN) website.2.0 to Oracle Database 11g Release 2 (11.2 Checking Hardware and Software Requirements You need to check that you meet the hardware and software requirements for running the new Oracle release. Process For more information in these special cases. The complete list of hardware and software requirements for every platform is included in the Oracle documentation. see the documentation for the Oracle Database 11g Release 2 (11. 2. 1.2. You can access the complete Oracle documentation as a member of the Oracle Technology Network (OTN).1 Planning Checking the Original Version of Your Database 2 Planning RECOMMENDATION Before the production upgrade. CAUTION To make sure that the checks complete successfully.2. 3.2) in manual mode ■ If the source database runs Oracle 10. you need to first update the source database to patch set 10. obtain more information.2. You review the Oracle-specified kernel parameters and shell limits [page 10]. 2. You check additional requirements for the upgrade [page 11]. Prerequisites In the following special cases you need to obtain more information: ■ If you are upgrading from Oracle 10. 2. 2010-09-10 PUBLIC 9/50 .

RECOMMENDATION If you have access to My Oracle Support (formerly Oracle Metalink) at https:// support.1. 3. If your database resides on Network Attached Storage (NAS) you need to review and implement the Oracle NAS guidelines.3 Reviewing the Oracle-Specified Kernel Parameters and Shell Limits You need to review the Oracle-recommended kernel parameters and shell limits for your operating system with Oracle Database 11g Release 2 (11.2 2. Note the following general hardware requirements: ■ At least 1024 MB of physical RAM ■ About 1024 MB free space in the /tmp directory ■ Swap space about 1. including all required patches. the amount of swap space should be the same as the memory ■ At least 10-15 GB for the Oracle Home directory. which you can find at the Oracle website.5 times the available memory for memory up to 2 GB.oracle. Select the appropriate documentation for Oracle Database 11g Release 2 (11. which you can find at: 10/50 PUBLIC 2010-09-10 . This document provides information on all operating system prerequisites and is regularly updated. For memory of 2 GB and above. CAUTION 2.com. consisting of: ● 3 to 5 GB for the Oracle software ● About 5 GB for the patch information stored by OPATCH tool This high space requirement is necessary due to the large number of patches that must be applied on top of any given Oracle patch set. You might need to upgrade your operating system before you start. You need to mount network file systems with specific mount options. These are only recommendations from Oracle for optimizing the system performance in production environments. which you can find in the Oracle installation guide. Check that your operating system meets the software requirements for running the new Oracle release.3 Planning Reviewing the Oracle-Specified Kernel Parameters and Shell Limits Procedure 1.2).2). 2. Obtain the full and updated list of hardware and software requirements from the relevant Oracle database installation guide for your operating system. Procedure Obtain the recommended shell limits and kernel parameters from the relevant Oracle database installation guide for your operating system. If the recommended settings are not suitable for your system you must tune the kernel parameters accordingly. we strongly recommend that you read document 169706.

see the Product Availability Matrix (PAM) at http://service.2) installation guide for your operating system from the Oracle Technology Network (OTN). RECOMMENDATION 4.2 2. You need this document to review the hardware and software requirements and to configure the kernel parameters and shell limits. Make sure you have read the SAP Notes for the upgrade [page 6]. Download the Oracle Database 11g Release 2 (11.4 Checking Additional Requirements for the Upgrade You need to check the additional requirements for the Oracle database upgrade as described in this section. Procedure 1. You can download the patches from: http://service. Download the Oracle Database 11g Release 2 (11. This document provides information on all operating system prerequisites and is regularly updated.2) software and the latest patch sets and required patches or patch collection. If you have access to My Oracle Support. we strongly recommend that you read document 169706. To upgrade from a remote PC. To check for your application or product. The SAP Note with the list of patches is referenced in SAP Note 1431800. RECOMMENDATION 5.2). In such cases we recommend you to start the OUI and the DBUA directly from the console. 2.com/pam.sap.2 is released and certified for SAP products running with SAP BASIS 640 and above. you need X-Windows software on the PC. Oracle 11.4 Planning Checking Additional Requirements for the Upgrade www. which you can find at http://service. 3.com/oracle-download 2010-09-10 PUBLIC 11/50 .sap. see SAP Note 758563. Download the recommended documents from My Oracle Support (formerly Oracle Metalink) at https://support.oracle. Make sure your operating system and initial database version meets SAP requirements. as described in SAP Note 432861.1.com/technology/documentation Select the appropriate documentation for Oracle Database 11g Release 2 (11.oracle.com. In some situations the OUI and DBUA screens are not displayed correctly when started remotely.com/notes 2. For access to My Oracle Support. and SAP kernel release 640_EX2 and above.sap.

8 and your SAP kernel is 640_REL kernel.com/oracle-download Download the latest version of the DBATOOLS (BR*Tools) to be used immediately after the database upgrade from: http://service.2 Instant Client software from: http://service.2.sap. as of release 7.or Release 7.sap. Make sure that you download the complete 640_EX2 kernel: both SAPEXE.10 (patch level 30).0. 12/50 PUBLIC 2010-09-10 . make sure that you install all these patches. Download the latest version of the Oracle 10.SAR.SAR and SAPEXEDB.2 2. To avoid severe database problems. download the 640_EX2 kernel from SAP Service Marketplace. 7. BR*Tools supports the Oracle Database 11g Release 2 (11.20 (patch level 1) . For more information. The patches listed in the SAP Note referenced in SAP Note 1431800 are mandatory.com/swdc 8.4 Planning Checking Additional Requirements for the Upgrade CAUTION 6. If your source database is Oracle 9. see SAP Note 1430669.2).

groups.2. and authorizations [page 13].2 Checking the Directory Structure You need to verify the availability and correctness of the following Oracle directories: ■ stage directory 2010-09-10 PUBLIC 13/50 . Groups.0. and Authorizations You need to check that the ora<dbsid> user has write authorization for the /oracle directory. Check if you are able to start an XTERM as the Oracle user since this is the user who starts the OUI. 8.8) [page 23]. since the ora<dbsid> user performs the database installation. 7. 6. You check the prerequisites for the Oracle Universal Installer [page 15]. You check the directory structure [page 13]. 5. log on to your system with the user root and enter the command: chgrp dba /oracle chmod 775 /oracle 2.0. Groups.1 Preparation Checking the Correct UNIX Users. Procedure 1. Enter the following command with the user ora<dbsid>: umask 022 3. You check the SAP System prerequisites [page 24]. 4. and Authorizations 3 Preparation You have to complete the following preparations: 1.1 Checking the Correct UNIX Users. If your source database is Oracle 10. You install the database software [page 16]. you run the pre-upgrade scripts (Oracle 9.3 3. You update the Oracle Instant Client [page 25].8. If your source database is Oracle 9.4. 3. you run the pre-upgrade scripts [page 22]. 2. Enter the following commands: touch /oracle/write_test rm /oracle/write_test If the user ora<dbsid> does not have write authorization.2.2. You check the correct UNIX users. 3.0.

If there is not enough space.SAR After you have finished the extraction of all the RDBMS CDs. 3. usually called /oracle/stage. 14/50 PUBLIC 2010-09-10 . The Oracle Database DVD contains a total of seven SAR files. For the upgrade to Oracle Database 11g Release 2 (11. Before starting the installation of the new Oracle software on the database host. The path to the Oracle inventory directory is mentioned in the file oraInst. client. Ensure that the stage directories contain enough freespace prior to extraction of the SAR files. and so on. use the SAP tool SAPCAR to extract all the RDBMS CDs to /oracle/stage/112_64 as user ora<sid>. The Oracle inventory directory maintains the inventory of all Oracle software installed on the system. the following subdirectories exist under /oracle/stage/112_64: ■ database ■ client ■ grid ■ examples ■ gateways ■ deinstall Check the Oracle inventory directory. which include the various Oracle 11. the following command extracts a single CD (the fifth in this example): SAPCAR –xvf OR511264. you can delete previous stage directories. 2.2 components such as database.3 3. 1.2 Preparation Checking the Directory Structure ■ Oracle inventory directory ■ Home directory Procedure 1. create it manually. NOTE On HP-UX PARISC.loc is present in either the directory /etc or directory /var/opt/oracle and check that it has the following entries: ■ inventory_loc=<location of the oracle inventory> 2. make sure that the file oraInst. If it already exists it might contain software stages from previous installations or upgrades. Check the Oracle stage directory. the Oracle Database DVD contains a total of only six files because the gateways component is not released for this platform. which you can find under /var/opt/oracle or under /etc. When the RDBMS CDs have been mounted.loc. only the software contained within the component database is used. 3.2) create the staging directory /oracle/ stage/112_64. gateways. grid. For the database upgrade. If this directory does not exist. For example.

Only valid for: AIX | On AIX. Log on as the Oracle user ora<dbsid>./runInstaller –executeSysPrereqs Checking operating system requirements (release. make sure that the variable inventory_loc in the file oraInst. call the script rootpre./runInstaller –executePrereqs 2010-09-10 PUBLIC 15/50 . kernel parameters): . 3.sh End of: AIX | Procedure 1. enter the location where you want the inventory log files to be written to. kernel parameters): . 2./runInstaller –executeSysPrereqs Checking operating system requirements (release.3 3. Prerequisites Make sure that the DISPLAY environment variable is set correctly. patches. Execute the following commands: ■ 32-bit platforms: cd /oracle/stage/112_32/database Checking prerequisites for the OUI: .3 Preparation Checking the Prerequisites for the Oracle Universal Installer ■ inst_group=dba If the Oracle Universal Installer has already been run on this host. If this is the first time that the OUI has been executed on this host.sh: .sh: End of: AIX | Only valid for: AIX | 1. patches.3 Checking the Prerequisites for the Oracle Universal Installer You must check the prerequisites for the Oracle Universal Installer (OUI)./runInstaller –executePrereqs ■ 64-bit platforms: cd /oracle/stage/112_64/database Checking prerequisites for the OUI: ./rootpre.loc points to the location where the Oracle inventory is located. call the script rootpre. Change to the directory /oracle/stage/112_64/database using the following command: cd /oracle/stage/112_64/database As the user root. 2.

You create a symbolic link for the data shared library [page 21]. 2. to reduce downtime you can perform the following steps before you stop your system. 3. 3. 4. You copy and adapt the old Oracle SQL*Net files [page 21]. NOTE You can install the database software while the SAP system is still running with the existing database (that is. see Changing the Environment for the <sapsid>adm User [page 39]. We recommend you to back up the old environment files before making the changes permanent. 6. You install the current patch set [page 20]. 16/50 PUBLIC 2010-09-10 .2). 5. Process Flow 1. Prerequisites Make sure that you set the environment variables as described below for the duration of this session only. You install the required SAP bundle patch [page 20]. You make them permanent in the database structure upgrade.2 software. You back up the Oracle inventory [page 18]. 7.4 Preparation Database Software Installation If the OUI still complains of missing patches or OS kernel parameters. CAUTION Do not make the changes to the environment permanent while the old database is still running. you install the Oracle 11.4 Database Software Installation As part of preparations.3 3.4. 3. NOTE For more information about changes to the environment of the SAP user <sapsid>adm. you need to check and set the environment variables of user ora<dbsid> because this user installs the Oracle software. Oracle 10. you need to apply these before you can proceed with the software installation. Therefore. You run the Oracle Universal Installer [page 18].1 Checking and Setting the Environment Variables To install the database software. You check and set the environment variables [page 16].

set this as follows: /oracle/<DBSID>/102_64 This environment variable is only relevant if the DBUA wrapper script from SAP is to be used. you might have to start an X terminal (xterm) session and run the command: 2010-09-10 PUBLIC 17/50 .0 NOTE <hostname>:0. Delete this environment variable when the upgrade has finished. we strongly recommend moving it to UTF8 before the upgrade. Value <hostname>:0.WE8DEC AMERICAN.AMERICA.UTF8 If your database still runs with the character set US7ASCII.0 is the host on which the Oracle Universal Installer (OUI) is to be displayed.4 Preparation Database Software Installation Procedure 1. You only need to set it if your ORACLE_HOME is not the SAP standard path. Make sure the following environment variables are not set: ■ TWO_TASK ■ ORA_NLS ■ ORA_NLS32 ■ ORA_NLS33 ■ ORA_NLS10 Set the following environment variables: Environment Variable DISPLAY 2. you do not need to set this variable.2. The setting of the DISPLAY environment variable is described in SAP Note 432861.3 3. NOTE If you are updating from Oracle 9.0. ORACLE_BASE ORACLE_SID ORACLE_HOME /oracle <DBSID> One of the following values: /oracle/<DBSID>/112_32 /oracle/<DBSID>/112_64 NLS_LANG One of the following values: AMERICAN_AMERICA.8. SAPDATA_HOME ORACLE_HOME_SRC /oracle/<DBSID> ORACLE_HOME of the source system to be upgraded EXAMPLE If you are upgrading from Oracle 10g Release2. To make sure that the OUI screen can be displayed correctly on your system.

set up the TEMP or TMPDIR environment variables to specify a temporary directory on the filesystem. Procedure 1. If not. where $ORACLE_HOME is the variable that you set in step 2 above. Log on as user ora<dbsid>. check its location by looking at the entry in one of the following files: ■ /var/opt/oracle/oraInst. Linux HP-UX 4.3 3.loc ■ /etc/oraInst.3 Running the Oracle Universal Installer To install the database software. Include $ORACLE_HOME/bin in your PATH or path variable. you need to back up the Oracle inventory.4. HP Tru64 UNIX. This makes sure that dynamic libraries are loaded first from $ORACLE_HOME/lib. Make sure there is only one $ORACLE_HOME/bin in your PATH or path variable.loc The location is shown as follows: inventory_loc=<path to Oracle inventory> 2. 18/50 PUBLIC 2010-09-10 . NOTE 5. Check if the temporary directory (usually /tmp) has at least 1024 MB of free space. you run the Oracle Universal Installer (OUI). 3. RECOMMENDATION You can check the correctness of the new environment with the UNIX env command. Procedure 1. 3. Make sure that the path variable does not contain the old $ORACLE_HOME/bin from the source database. If the Oracle inventory exists.4 Preparation Database Software Installation $ xhost + 3.2 Backing Up the Oracle Inventory Before you install the database software.4. Set the corresponding environment variable for the library path: Operating System Environment Variable LIBPATH LD_LIBRARY_PATH SHLIB_PATH Value $ORACLE_HOME/lib:$LIBPATH $ORACLE_HOME/lib:$LD_LIBRARY_PATH $ORACLE_HOME/lib:$SHLIB_PATH AIX Solaris.2) software installation. Make a backup of your existing Oracle inventory before you start the Oracle Database 11g Release 2 (11. Or you can run the UNIX umask command and check that the returned value is 22.

these are dba and oper. Respond to the OUI as follows: Prompt or Condition Action Configure Security Updates Select Installation Option Grid Installation Options Select Product Language Select Database Edition Specify Installation Location Privileged OS Groups Perform Prerequisite Checks Do not select the checkbox. Confirm the default option English and then choose Next. You see a message that a response file is being generated./RUNINSTALLER ■ For 64-bit systems. Choose OK and then Next. Confirm the default option Enterprise Edition and then choose Next.0 export DISPLAY Bourne shell (sh) C shell (csh) Korn shell (ksh) setenv DISPLAY <host_name>:0. Confirm the default selection Single Instance Installation and then choose Next. Select this option and then Next. It might take several minutes before you see the OUI screen. This screen displays the value for ORACLE_BASE which is set in the environment. Shell Used Command DISPLAY=<host_name>:0. Normally. Confirm the default selections by choosing Next./RUNINSTALLER 4. Start the OUI with the user ora<dbsid> as follows: ■ For 32-bit systems. This screen displays the operating system groups for the DBA and the operator.0. Since you are already logged on as user root.0 3. This screen checks if all the required system prerequisites for installation of the database software 2010-09-10 PUBLIC 19/50 .3 3. which should be /oracle/DBSID/ 112_64.0 export DISPLAY=<host_name>:0. enter the following: cd /oracle/stage/112_64/database/SAP . It also displays the value for ORACLE_HOME. Make sure that the DISPLAY environment variable is set to <host_name>:0.4 Preparation Database Software Installation 2. where <host_name> is the host on which you want to display the GUI of the Oracle Universal Installer (OUI). you can switch to user ora<dbsid> by entering the following command: su – ora<dbsid>. enter the following: cd /oracle/stage/112_32/database/SAP . The runInstaller issues a warning.

see SAP Note 1431799. you need to install the current patch set for Oracle Database 11g Release 2 (11. If some of the checks are displayed as Failed. For more information. see SAP Note 1431799. CAUTION Do not perform any of the post-installation steps mentioned in the patch set README file.4 Preparation Database Software Installation Prompt or Condition Action have been met. Finish the software installation by executing the root. At this stage. Procedure 1. 5.4. Install the patch set as described in the patch set README file. 3. ■ You only have to install the latest (that is.5 Installing the Required SAP Bundle Patch After the Oracle database software installation. You need the SAP bundle patch in addition to the current patch set. Review the information displayed on this screen and choose Finish. The database itself is still not Oracle 11.2 database. To exit the OUI.3 3.sh script as the root user from another session.2 software. you have only installed the Oracle 11. using the Oracle tool MOPatch. you need to install the required SAP bundle patch. choose Exit and confirm the dialog box that appears. 20/50 PUBLIC 2010-09-10 . see the patch set README file. ■ For more information about how to install the patch set. 3. make sure that you do not perform the post-installation steps mentioned in the README file. Only perform the post-installation steps on an existing Oracle 11. 2.2. the current) patch set.4. RECOMMENDATION Summary Finish We strongly recommend you to make sure that there are no failed checks before starting the software installation.4 Installing the Current Patch Set After the database software installation [page 16]. you can fix these problems (either by installing the missing patches or configuring the kernel parameters) and run the check again by choosing Check Again. Prerequisites ■ For more information on the latest patch set available for Oracle 11.2). Log on at the operating system level with the ora<dbsid> user.2. Therefore.

sl End of: HP-UX | 3.Solaris | Only valid for: HP-UX | ln –s libnnz11.Solaris | ln –s libnnz11.so libnnz10.3 3. and tnsnames. 2.7 Copying and Adapting the SQL*Net Files After the database software installation.so End of: AIX.sl libnnz10.4. After the software installation has finished. 2010-09-10 PUBLIC 21/50 .2 client) can use the newer Oracle 11. which you can find at SAP Note 1027012. Prerequisites ■ Make sure you have downloaded and installed OPatch from SAP Service Marketplace as described in SAP Note 839182.ora. ■ Check SAP Note 1027012 for instructions on how to use MOPatch.2 clients. you must copy and modify the old SQL*Net files. Log on at the operating system level as the ora<dbsid> user.4. you do not need to install any critical patch updates (CPUs). The SAP bundle patch also delivers a set of upgrade scripts that automate most of the pre-upgrade and post-upgrade tasks.Linux. ■ Check SAP Note 1431800 to find a cross-reference to the current SAP Note with the list of required patches to be installed.6 Creating a Symbolic Link for the Data Shared Library You need to create this link so that BR*Tools (which is linked to the Oracle 10. Install the SAP bundle patch according to the instructions in the SAP bundle patch README file. sqlnet. that is. Procedure 1. ■ Make sure you have already installed the current patch set [page 20].ora. After installing the SAP bundle patch.4 Preparation Database Software Installation NOTE You must install the SAP bundle patch in a single step using the Oracle tool MOPatch.Linux.ora. listener. Procedure 1. create a symbolic link in $ORACLE_HOME/lib as follows: cd $ORACLE_HOME/lib Only valid for: AIX. 3. You only need to install the latest SAP bundle patch because these patches are cumulative.

3.2.3 3. 4.0. The scripts do the following on your pre-upgrade database: ■ Provide information on the database ■ Suggest any changes that you need to make to the database before you start the upgrade ■ Perform some of the pre-upgrade tasks on the database NOTE You always execute these scripts as the ora<dbsid> user connected to the database as sysdba in the Oracle 10. The directory where the upgrade scripts are installed is called ora_upgrade. Prerequisites You are logged on as user ora<dbsid> in the Oracle 10.4. Log on as user ora<dbsid>.2.5 Preparation Running the Pre-Upgrade Scripts Procedure 1. 3. If your source database is Oracle 9.2 environment.2 software home): ■ 64-bit: cd /oracle/<DBSID>/112_64/sap/ora_upgrade/pre_upgrade 22/50 PUBLIC 2010-09-10 .2 software home directory: ■ 64-bit: /oracle/<DBSID>/112_64/sap/ora_upgrade ■ 32-bit: /oracle/<DBSID>/112_32/sap/ora_upgrade Procedure 1.2. the scripts are installed as part of the SAP bundle patch in the relevant Oracle 11. Copy the SQL*Net parameter files from <old_ORACLE_HOME>/network/admin to <new_ORACLE_HOME>/network/admin.0.5 Running the Pre-Upgrade Scripts You run the Oracle pre-upgrade scripts. 2. Be sure to adapt the value of ORACLE_HOME in the listener. see Running the Pre-Upgrade Scripts (9. do not start the listener with the new listener. By default. which automatically perform various tasks and checks on your database.2 environment with the database also started up. This section only applies if your source database is Oracle 10. Edit the new SQL*Net files by adapting all file paths for the new directory.8.0.ora file. See SAP Note 1431793. Change to the correct directory by entering the relevant command (since the scripts have been extracted to the Oracle 11. Add the following entry to the file listener.ora: ADR_BASE_LISTENER = /oracle/DBSID/saptrace Since your database is still running in the old environment.8) [page 23].ora file at this point.

By default. the scripts are installed as part of the SAP bundle patch in the relevant Oracle 11. Prerequisites ■ You are logged on as user ora<dbsid> in the Oracle 9.6 Preparation Running the Pre-Upgrade Scripts (Oracle 9. However.0.3 3.log Make sure that you check any warnings issued in the log files.sqlSQL> spool off Result You can check the results of the pre-upgrade scripts by looking at the following log files: ■ PRE_UPGRADE_STATUS.0. see Running the Pre-Upgrade Scripts [page 22].2. This parameter must be set to TRUE for the SAP logon mechanism to work correctly after the database upgrade.0. If your source database is Oracle 10. Execute the following commands to perform pre-upgrade tasks.2.log SQL> @pre_upgrade_tasks.0. This section only applies if your source database is Oracle 9.6 Running the Pre-Upgrade Scripts (Oracle 9.log ■ PRE_UPGRADE_TASKS.2 database. otherwise you might have problems during the upgrade. you must ignore the warning regarding the database parameter remote_os_authent. which can improve the performance of the upgrade process: sqlplus / as sysdba SQL> spool PRE_UPGRADE_TASKS.2 software home directory: 2010-09-10 PUBLIC 23/50 . NOTE You always execute these scripts as the ora<dbsid> user connected to the database as sysdba in the Oracle 9.8.2 environment. ■ The directory where the upgrade scripts are installed is called ora_upgrade. which is reported as DEPRECATED. You can run the pre-upgrade scripts as often as you like on the pre-upgrade Oracle 10. 3.8) You run the Oracle pre-upgrade scripts. CAUTION Make the changes listed in the log file.2 environment with the database also started up. The post-upgrade script sets it to TRUE again after the database upgrade.2.2.sql 3. ■ 32-bit: cd /oracle/<DBSID>/112_32/sap/ora_upgrade/pre_upgrade Execute the following commands to check the pre-upgrade status of your database: sqlplus / as sysdba SQL> @pre_upgrade_status. Do not touch this parameter.4. which automatically perform checks on your database.8) 2.

Make sure that you check any warnings and perform the suggested corrective actions mentioned in the log file.11 SP05 ■ SAP_BASIS 7. CAUTION Make the changes listed in the log file. 1414733. which is reported as DEPRECATED. The post-upgrade script sets it to TRUE again after the database upgrade.log.sql Result You can check the results of the pre-upgrade script by looking at the following log file utlu112i.01 SP06 ■ SAP_BASIS 7. otherwise you might have problems during the upgrade.log SQL> @utlu112i.7 Checking the SAP System Prerequisites Procedure 1.20 SP02 24/50 PUBLIC 2010-09-10 .2 software home): ■ 64-bit: cd /oracle/<DBSID>/112_64/sap/ora_upgrade/pre_upgrade ■ 32-bit: cd /oracle/<DBSID>/112_32/sap/ora_upgrade/pre_upgrade Execute the following commands to check the pre-upgrade status of your database: sqlplus / as sysdba SQL> spool utlu112i.7 Preparation Checking the SAP System Prerequisites ● 64-bit: /oracle/<DBSID>/112_64/sap/ora_upgrade ● 32-bit: /oracle/<DBSID>/112_32/sap/ora_upgrade Procedure 1. For SAP systems 7. 3.00 SP21 ■ SAP_BASIS 7. and 1433301 if you are running any of the following support packages: ■ SAP_BASIS 7.2 database.3 3. This parameter must be set to TRUE for the SAP logon mechanism to work correctly after the database upgrade. apply SAP Notes 1416108. you must ignore the warning regarding the database parameter remote_os_authent.10 SP10 ■ SAP_BASIS 7. Do not touch this parameter. 2. Change to the correct directory by entering the relevant command (since the scripts have been extracted to the Oracle 11. However. You can run the pre-upgrade script as often as you like on the pre-upgrade Oracle 9.XX.02 SP02 ■ SAP_BASIS 7.

3.3 3. you need to use DBSL (dboraslib.2.2. Procedure Update the Oracle Database Instant Client for UNIX as described in SAP Note 1431794. If your SAP system is SAP BASIS 7xx. apply the advanced correction from SAP Note 1417124 This correction resolves an Oracle issue that results in an ABAP short dump during statistics updates. NOTE This step also applies to SAP systems running the 640_REL kernel with the Oracle 9. The error is fixed in later support packages. This error is seen only after the database has been upgraded to Oracle 11.4 Version 3 (V3). The Instant Client 10.so) patch level 81 or higher.8 database. This resolves an error in an ABAP program that causes it to report problems during the consistency checks within transaction SE14.0.0. 2010-09-10 PUBLIC 25/50 .4 is used immediately after the kernel switch to 640_EX2.0.8 Preparation Updating the Oracle Instant Client 2. 3. If your SAP system uses SAP Kernel 711.2. For more information.8 Updating the Oracle Instant Client You need to ensure that the SAP system runs with at least Instant Client release 10. see SAP Note 1456323.2.

This page is left blank for documents that are printed on both sides. .

2 Shutting Down the SAP System and Oracle Listener Process You need to shut down the SAP system and the Oracle listener running process running in the old ORACLE_HOME. in /oracle/<DBSID>/102_64 or /oracle/<DBSID>/920_64. You upgrade the database structure [page 28]. Stop the SAP application server by entering the following command as user <sapsid>adm: stopsap Stop the Oracle listener by entering the following command as user ora<dbsid>: lsnrctl stop 2010-09-10 PUBLIC 27/50 . You back up the Oracle database [page 27].1 Oracle Database Upgrade Backing Up the Oracle Database 4 Oracle Database Upgrade This section describes how to upgrade the Oracle database. Procedure 1. 4. 4. 1. 3. for example. see SAP Note 1431797. Make sure that you do a log file switch for all online redo log files. Procedure 1. Create a complete database backup and back up any archive logs from Oracle 10g.4 4. You shut down the SAP system and Oracle listener process [page 27]. Check that the backup is usable. RECOMMENDATION Before backing up the archive logs. switch the log files with the following SQL command: alter system switch logfile 2. NOTE If you have problems during the upgrade. 2.1 Backing Up the Oracle Database You must have a complete and usable database backup otherwise you might lose data. 2. If for any reason you have problems during the upgrade you must be able to restore the database from this backup.

3. 3. Prerequisites You have installed the database software [page 16]. Make sure that you reschedule these processes when the upgrade has finished. Result Now continue with the Post-Upgrade Steps [page 35]. Prerequisites You can find the oratab file as follows: ■ ■ Only valid for: AIX. You check the oratab entry [page 28].8.2. you start the Database Upgrade Assistant to perform the upgrade [page 29]. you upgrade the database structure. If your source database is Oracle 10. you need to check the entry for the oratab file. Make sure that the oratab file contains the following entry: <DBSID>:<old_ORACLE_HOME>:N Where old_ORACLE_HOME stands for the path to the old oracle software installation.3 Oracle Database Upgrade Database Structure Upgrade NOTE Make sure that processes that log on to the database.Linux | /etc End of: AIX.4 4.4. 2.Linux | Only valid for: Solaris | /var/opt/oracle End of: Solaris | Procedure 1. you start the Database Upgrade Assistant to perform the upgrade (Oracle 9.HP-UX. 4. 4.3 Database Structure Upgrade As part of the Oracle database upgrade [page 27].2 source database 28/50 PUBLIC 2010-09-10 .2. are not active during the upgrade.1 Checking the oratab Entry To upgrade the database structure.HP-UX. Process Flow 1.0.0.8) [page 31]. such as CRON jobs. If your source database is Oracle 9.0.2. EXAMPLE The entry for a system with a <DBSID> equal to C11 is as follows: ■ Oracle 10.

3 Oracle Database Upgrade Database Structure Upgrade C11:/oracle/C11/102_64:N.3.sh Calling the script without any option ensures that the compatible parameter is automatically set to 11. If this entry does not exist.8) [page 31]. 4.0 after completion of the database upgrade. Run this script in query mode initially to verify that the environment is correct: .. you need to start the Oracle Database Upgrade Assistant (DBUA). SHLIB_PATH.2 user environment./dbua. carefully check the first point below.sh is a wrapper script to automate most of the post-upgrade tasks.2 source database C11:/oracle/C11/920_64:N 2. Start the DBUA.2.sap.2.2 directories: ● ORACLE_HOME points to /oracle/<DBSID>/112_64 ● PATH ● LD_LIBRARY_PATH. If your source database is Oracle 9. or LIBPATH ■ Before you start the DBUA make sure that the DISPLAY environment variable is correctly set. ■ Ensure that you have write permissions on /etc/oratab. ■ Oracle 9. If you call the DBUA with this option.2 Starting the Database Upgrade Assistant To upgrade the database structure. see Starting the Database Upgrade Assistant (Oracle 9. Procedure 1. This section only applies if your source database is Oracle 10.4. 3.sap. dbua.0.sap.” – in Performing PostUpgrade Tasks [page 37]. Prerequisites CAUTION Make sure that you start the DBUA in the Oracle 11./dbua. you do not need to perform the first step – “Change database compatibility.2.. To do this.8. Change to the correct directory: cd $ORACLE_HOME/sap/ora_upgrade/post_upgrade 2.sh -q Run this script in either of the two following ways: ■ .0.0. Note that activating the compatible parameter invalidates any restore points that were defined before the start of the upgrade.2.4 4. The DBUA tool is a graphical tool that leads you step by step through the upgrade. ■ Confirm that the following environment variables point to Oracle 11. 1. insert it using a text editor. 2010-09-10 PUBLIC 29/50 .

30/50 PUBLIC 2010-09-10 . and issues warnings if necessary. Respond appropriately to the DBUA dialogs: The Welcome screen provides information about the upgrade assistant 1. After the upgrade. performs pre-upgrade checks. If the database server has multiple CPUs. Calling the script with the no_compatible option ensures that the database is upgraded and all the post-upgrade steps are performed.sql. Any invalid SYS/SYSTEM objects found before upgrading the database are stored in table registry$sys_inv_objs Any invalid non-SYS/SYSTEM objects found before upgrading the database are stored in table registry $nonsys_inv_objs. The most common warning or information messages are as follows: Message Explanation or Solution Information message: Database is using a timezone file older than version 11 Warning message: Database contains schemas with stale optimizer statistics Warning message: Database contains INVALID objects prior to upgrade Explanation: Upgrade of TSTZ data is done automatically if the DBUA was started using dbua. Therefore.sh -help. Select the correct database and choose Next.sh -no_compatible 2.sap. run ORACLE_HOME/rdbms/admin/ utluiobj. The DBUA now analyzes the database to be upgraded.sap. you need to manually perform the first step – “Change database compatibility../dbua. The screen Recompiling Invalid Objects lets you choose whether the DBUA has to automatically recompile all PL/SQL modules after the upgrade. However.2.sap. see SAP note 1431793 or run dbua. use SQL*Plus to execute the script $ORACLE_HOME/rdbms/admin/utlrp. the DBUA automatically proposes the number of parallel processes to be used for the recompilation.4 4.” – in Performing Post-Upgrade Tasks [page 37]..sap.3 Oracle Database Upgrade Database Structure Upgrade ■ .0. you need to analyze and act on these warnings.sh. Solution: Run the following command: brconnect -u / -c -f stats -t oradict_stats Solution: To recompile any invalid objects. RECOMMENDATION If the DBUA warns you of issues that need to be fixed before the upgrade. 2.sql to identify any new invalid objects due to the upgrade. the compatible parameter is not set to 11. The Databases screen lets you select the database to be upgraded.sh. Choose Next to continue. For more information on how to use dbua.

This section only applies if your source database is Oracle 9.0. if required. parameters to be added. Make sure that Configure the database with Enterprise Manager is not selected and choose Next. The DBUA tool is a graphical tool that leads you step by step through the upgrade.8) To upgrade the database structure. select Recompile invalid objects after the upgrade.2. Accept the default values. 2010-09-10 PUBLIC 31/50 . Before you start it. The DBUA automatically removes the database initialization parameters that are now obsolete in Oracle Database 11g Release 2 (11.3. removed.4 4.4. 4.0. make sure that you also specify the location and the size of the flash recovery area and its files. This includes the warnings that you ignored or did not fix. and choose Next. To do this. Prerequisites CAUTION Make sure that you start the DBUA in the Oracle 11. components to be upgraded. 4. NOTE 4. Start the database upgrade by choosing Finish. see Starting the Database Upgrade Assistant [page 29]. The screen Management Options lets you set up the database so that it can be managed with the Enterprise Manager. 5. The screen Move Database Files lets you move the database files during the upgrade process. If you select this option.8. 6. you do not need to select the Backup option on this screen. select Specify Flash Recovery Area if you have set up a restore point on the database to facilitate database recovery in the event of problems.2. The upgrade process itself runs for some time. Review the summary of changes and choose Back to make any final adjustments. Since you have already performed the database backup [page 27]. For a complete list of obsolete and deprecated parameters.2). Select Do not move the database files as part of the upgrade and choose Next. see the documentation for Oracle Database 11g Release 2 (11. 5.0. On the screen Recovery and Diagnostic Location.2).2. and changed after the upgrade.3 Oracle Database Upgrade Database Structure Upgrade 3.3 Starting the Database Upgrade Assistant (Oracle 9. 3. the DBUA displays a summary of the changes to be made. When the DBUA has completed successfully the results of the upgrade are displayed Review the changes made and exit the DBUA.2 user environment. If your source database is Oracle 10. depending mainly on the size of the database and the capacity of the hardware. you need to start the Oracle Database Upgrade Assistant (DBUA). carefully check the first point below.

The Databases screen lets you select the database to be upgraded.3 Oracle Database Upgrade Database Structure Upgrade ■ Confirm that the following environment variables point to Oracle 11.sql. ■ Ensure that you have write permissions on /etc/oratab./oracle//<DBSID>//112_64/sap/ora_upgrade/post_upgrade/ upgrade_TSTZ.sql. 2. No action is necessary. Respond appropriately to the DBUA dialogs: The Welcome screen provides information about the upgrade assistant 1. Solution: Run the following commands: brconnect -u / -c -f stats -t oradict_stats brconnect -u / -c -f stats -t system_stats Solution: To recompile any invalid objects. Select the correct database and choose Next.sql.4 4.sql. RECOMMENDATION If the DBUA warns you of issues that need to be fixed before the upgrade. SHLIB_PATH. Start the DBUA as follows: . Procedure 1. or LIBPATH ■ Before you start the DBUA make sure that the DISPLAY environment variable is correctly set.sql 3.2 directories: ● ORACLE_HOME points to /oracle/<DBSID>/112_64 ● PATH ● LD_LIBRARY_PATH. The DBUA now analyzes the database to be upgraded. you need to analyze and act on these warnings./oracle//<DBSID>//112_64/sap/ora_upgrade/post_upgrade/ set_compatible. Switch to $ORACLE_HOME/112_64/bin. performs pre-upgrade checks. Choose Next to continue./oracle//<DBSID>//112_64/sap/ora_upgrade/post_upgrade/ set_remote_os_authent. 32/50 PUBLIC 2010-09-10 . use SQL*Plus to execute the script $ORACLE_HOME/rdbms/admin/utlrp. The most common warning or information messages are as follows: Message Explanation or Solution Information message: Database is using a timezone file older than version 11 Warning message: Database contains schemas with stale optimizer statistics Warning message: Explanation: Upgrade of TSTZ data is done automatically using one of the postupgrade custom scripts. 2. and issues warnings if necessary./dbua -diagnosticDest /oracle/<DBSID>/saptrace -recompile_invalid_objects true initParam audit_file_dest=/oracle/<DBSID>/saptrace/audit -emConfiguration NONE postUpgradeScripts /oracle/<DBSID>/112_64/sap/ora_upgrade/post_upgrade/ post_upgrade_tasks.

3 Oracle Database Upgrade Database Structure Upgrade Message Explanation or Solution Database contains Any invalid SYS/SYSTEM objects found before upgrading the database INVALID objects prior to are stored in table registry$sys_inv_objs upgrade Any invalid non-SYS/SYSTEM objects found before upgrading the database are stored in table registry$nonsys_inv_objs. make sure that you also specify the location and the size of the flash recovery area and its files. 3.sql script after the database upgrade as described in roles. The screen Move Database Files lets you move the database files during the upgrade process. 5.4 4. You need to run role granted to some user/ the sapconn_role. If the check asks for space extension in any particular Tablespace Size tablespace. select Recompile invalid objects after the upgrade. the DBUA automatically proposes the number of parallel processes to be used for the recompilation. you do not need to select the Backup option on this screen.data1 Check Reuse Existing Filename. Warning Message Solution: Parameter Update "compatible" must be set to at least 10. no further action is necessary as the DBUA automatically switches this parameter after the upgrade. Select Do not move the database files as part of the upgrade and choose Next.0. specify the location for the datafiles along with the size and other attributes by entering the following: Datafile: /oracle/<SID>/sapdata1/sysaux_1/sysaux. On the screen Recovery and Diagnostic Location. and choose Next. 4. If you select this option. Information Message: Explanation: Obsolete/Deprecated The pre-upgrade check script lists the obsolete or deprecated parameters. On the screen SYSAUX Tablespace. run ORACLE_HOME/rdbms/admin/utluiobj. 6. Information Message: Explanation: SYSAUX Tablespace No action is necessary as the tablespace is created automatically by the DBUA. Since you have already performed the database backup [page 27]. Updating BR*Tools [page 36]. Accept the default values. The screen Recompiling Invalid Objects lets you choose whether the DBUA has to automatically recompile all PL/SQL modules after the upgrade. Warning message: Solution: Deprecated CONNECT The default connect role is deprecated as of Oracle 10g.sql to identify any new invalid objects due to the upgrade. select Specify Flash Recovery Area if you have set up a restore point on the database to facilitate database recovery in the event of problems. Size: 2048 MB 2010-09-10 PUBLIC 33/50 . You need to adapt all other parameters as suggested by the pre-upgrade check. If the database server has multiple CPUs. For this warning.1. you need to perform this. After the upgrade. Parameters: No action is necessary as these parameters are automatically removed by Information Message the DBUA.

For a complete list of obsolete and deprecated parameters. removed. The upgrade process itself runs for some time. if required. Start the database upgrade by choosing Finish.2). This includes the warnings that you ignored or did not fix. 6. Before you start it. 8. you can set up the database so that it can be managed with the Enterprise Manager. and changed after the upgrade. When the DBUA has completed successfully. On the screen Management Options. see the documentation for Oracle Database 11g Release 2 (11. depending mainly on the size of the database and the capacity of the hardware. The DBUA automatically removes the database initialization parameters that are now obsolete in Oracle Database 11g Release 2 (11. 34/50 PUBLIC 2010-09-10 .2).4 4. Review the summary of changes and choose Back to make any final adjustments.3 Oracle Database Upgrade Database Structure Upgrade 4. 7. NOTE 5. Check AUTOEXTEND ON. the results of the upgrade are displayed Review the changes made and exit the DBUA. the DBUA displays a summary of the changes to be made. components to be upgraded. parameters to be added. Make sure that Configure the database with Enterprise Manager is not selected and choose Next. Increment Size 100 MB Maximum Size: Unlimited Choose Next to continue.

and so on). you need to perform the steps described here.5 5. You restart the SAP system [page 44]. You check the SAP profile parameters [page 41]. 16. 15. 2010-09-10 PUBLIC 35/50 . You rename the old alert log file [page 39]. 17.1 Post-Upgrade Steps Finalizing the Environment of the ora<dbsid>User 5 Post-Upgrade Steps After the Oracle database upgrade.1 Finalizing the Environment of the ora<dbsid>User You need to make sure that the changes you made to the Oracle user environment are permanently stored in the profiles (. .dbenv_<hostname>. you change the national character set of your database to UTF8 [page 45]. 10.2) [page 45]. You check the upgraded database [page 36]. You start the listener process [page 38]. You back up the database [page 38]. You update the SQL*Net configuration files for the <sapsid>adm and ora<sid> users [page 40]. You configure the new features for Oracle Database 11g Release 2 (11. 9. 1. If your source database is Oracle 9. 8. Procedure Check the values for the environment variables as described in Checking and Setting the Environment Variables [page 16]. you change the location of the JDBC driver [page 41].csh.cshrc. You check the read authorization of the <sapsid>adm user [page 39]. You perform post-upgrade tasks [page 37]. You finalize the environment of the ora<dbsid> user [page 35]. 13. 6. 5. If your SAP kernel is 640_REL. you update the SAP kernel to 640_EX2 [page 39]. 3.2. 5. If necessary. You update BR*Tools [page 36]. 14. 2. You change the environment for the <sapsid>adm user [page 39]. 7. 4. You rename the old $ORACLE_HOME/bin directory [page 38]. NOTE Make sure that the environment does not contain any variables that still refer to the old database release. 11. 12.

with the latest patch level.0 VALID CATPROC 11.2.8. the DBUA automatically creates an spfile. For example. Check that the database is now running with Oracle Database 11g Release 2 (11. Procedure 1.0. We recommend that you continue to use the spfile.log. you need to update the SAPDBA role using the script sapdba_role.2.1.2 Post-Upgrade Steps Checking the Upgraded Database 5.0. Procedure 1.sql and create the SAPCONN role using sapconn_role.5 5. If your source database was Oracle 9.0. 2. Log on to the database as the ora<sid> user. 5.2. Download the most current version of the BR*Tools from SAP Service Marketplace at: 36/50 PUBLIC 2010-09-10 . Check that the value for the version returned from the above command is the same level as the installed patchset.2 Checking the Upgraded Database You need to check the upgraded database. EXAMPLE This is an example of the output from this command: COMP ID VERSION STATUS CATALOG 11. RECOMMENDATION If the old database used an initialization file init<DBSID>.0.2) environment by entering the following commands: 1.0 VALID 2.2.2.ora. 4. The script is automatically extracted when you extract BR*Tools.1. Change to the correct directory: cd $ORACLE_HOME/sap/ora_upgrade/post_upgrade 3. Enter the following command to start SQLPLUS: sqlplus / as sysdba Run post_upgrade_status.sql: SQL> @post_upgrade_status.3 Updating BR*Tools You update BR*Tools to the latest release.sql Check the log POST_UPGRADE_STATUS.2.2) software in an Oracle Database 11g Release 2 (11. if the installed patchset is Oracle 11. the above command should also report the version for the CATALOG and CATPROC components as 11.2. Make sure that the command returns the status VALID.sql. Do not switch back to the initialization file after the upgrade. This is essential so that the new release of BR*Tools works correctly.0.

sap. Make sure that you execute this command for every SAPSCHEMA_ID in your database.sql as follows: cp /usr/sap/<SAPSID>/SYS/exe/run/sapconn_role.5 5.sql $ORACLE_HOME/dbs cd $ORACLE_HOME/dbs Only valid for: ABAP | sqlplus /nolog @sapdba_role <SAPSCHEMA_ID> End of: ABAP | Only valid for: Java | sqlplus /nolog @sapdba_role <SAPSCHEMA_ID>DB End of: Java | NOTE If you have an ABAP+Java system. Gather Oracle optimizer statistics by executing the following commands as the ora<dbsid> user: brconnect -u / -c -f stats -t system_stats brconnect -u / -c -f stats -t oradict_stats 3. Restart the Oracle database. you have to enter both commands. Check the Oracle database parameters against SAP Note 1431798 and adjust them if necessary. CAUTION 3.4 Post-Upgrade Steps Performing Post-Upgrade Tasks http://service.4 Performing Post-Upgrade Tasks You need to perform certain post-upgrade tasks.0' scope = spfile. Change database compatibility by executing the following SQL command as the ora<dbsid> user: SQL> alter system set compatible='11.8. Execute the following commands as the ora<dbsid> user to update the SAPDBA role: cp /usr/sap/<SAPSID>/SYS/exe/run/sapdba_role.2.2. 2010-09-10 PUBLIC 37/50 . You can find an automated script in SAP Note 1171650 to help you check whether your SAP system complies with the database parameter recommendations at any given point in time.com/swdc CAUTION 2. Procedure 1. Perform the following steps only if your source database was Oracle 9.2. Check database compatibility by executing the following command: SQL> show parameter compatible If not set to 11.sql $ORACLE_HOME/dbs cd $ORACLE_HOME/dbs sqlplus /nolog @sapconn_role 5. 2.0. do the following: 1.0. 2. Execute the SQL script sapconn_role.

2 software. 2. Update the Oracle database statistics with BRCONNECT as follows: brconnect -c -u / -f stats -t all –f collect -p 4 NOTE For more information about update statistics.com/irj/sdn/ora SAP ON ORACLE KNOWLEDGE CENTER SAP Documentation 5. Procedure Rename the old Oracle home directory bin with the following command: 38/50 PUBLIC 2010-09-10 . Procedure 1.5 Post-Upgrade Steps Backing Up the Database 4.sdn. Prerequisites Make sure that you have copied the SQL*Net configuration files from the old Oracle installation to the location of the Oracle Database 10g or 9.7 Renaming the Old $ORACLE_HOME/bin Directory Once the database is running correctly.6 Starting the Listener Process You start the listener process.5 Backing Up the Database You need to back up your upgraded Oracle Database 11g database.sap. as described in Copying and Adapting the SQL*Net Files [page 21]. 5.5 5. you need to rename the bin directory from the old $ORACLE_HOME to prevent accidental usage of the old binaries. see the documentation SAP Database Guide: Oracle at: www. Procedure Perform a full database backup. Start the listener: lsnrctl start Check that you can remotely connect to the database through the listener: sqlplus SAP<SAPSCHEMA_ID>/pwd@SID 5. CAUTION You risk losing data if you do not back up your database.

5 5. Procedure 1.log file to avoid confusion with the new alert log file used in Oracle 11g.40 and lower) running on the database server.10 Updating the SAP Kernel from 640_REL to 640_EX2 If you are running a 640_REL kernel. 2010-09-10 PUBLIC 39/50 .8 Renaming the Alert Log File You need to rename the old alert_<SID>.log 5. Prerequisites You have an SAP System running with 640_REL kernel and you just upgraded your Oracle 9.9 Checking the Read Authorization of the <sapsid>adm User You check the read authorization of the <sapsid>adm user. enter the following command as the ora<dbsid> user: chmod 755 $ORACLE_HOME 5.2.8 Post-Upgrade Steps Renaming the Alert Log File mv <old_oracle_home>/bin <old_oracle_home>/bin-old CAUTION Do not rename the entire old_oracle_home in case you have SAP systems (SAP kernel release 6.2. Procedure Enter the following command: mv alert_<SID>. This is because the SAP system running on the database server might still use the Oracle 9i client software. 5.0.11 Changing the Environment for the <sapsid>adm user You have to change the environment for the <sapsid>adm user. Make sure that the <sapsid>adm user has read authorization for the directory $ORACLE_HOME.8 database to Oracle 11.2 database. 5. Procedure Update your SAP kernel to 640_EX2. We do not support running a 640_REL kernel with an Oracle 11. but only on the database server. you must update it to 640_EX2. If this is not true.log OLD_alert_<SID>. 2. performing the kernel switch as described in SAP Note 1058988.

the SQL*Net files are used from the specified location (even if ORACLE_HOME is set).ora file that is used by the <sapsid>adm user: LISTENER_<DBSSID>. Procedure Adapting the SQL*Net Files for the ora<sid> User 1. set the ORACLE_HOME environment variable to point to the location of the Oracle Database 11g software installation.5 5.ora file for the <sapsid>adm and ora<sid> users after the upgrade: ■ For the ora<sid> user. On the database server.WORLD)(PROTOCOL = TCP)(HOST = <hostname>)(PORT = <listener_port>)) NOTE Although this entry is only needed on the database server or on central systems where the startdb or stopdb scripts are used. Check whether R3trans can connect to the database: R3trans –d 5.12 Updating the SQL*Net Configuration Files for the <sapsid>adm and ora<sid> Users You need to update the tnsnames. it is recommended to repeat the change described above on all application servers.cshrc. for example: /oracle/<DBSID>/112_<32>/<64> 2. you need to adapt the SQL*Net files are located in the directory $ORACLE_HOME/network/admin. and so on). 40/50 PUBLIC 2010-09-10 . . Procedure 1. Determine the SQL*Net files used by <sapsid>adm as follows: ■ If the environment variable TNS_ADMIN is set. 3. Log out and log on again as the <sapsid>adm user. ■ For the <sapsid>adm user.dbenv_<hostname>. Without this entry. Make sure that the change to the user environment is permanently stored in the profiles (.WORLD = (ADDRESS = (COMMUNITY = SAP. the startdb or stopdb script fails with the following error message: ORA-00119: invalid specification for system parameter LOCAL_LISTENER Adapting the SQL*Net Files for the <sapsid>adm User 1.12 Post-Upgrade Steps Updating the SQL*Net Configuration Files for the <sapsid>adm and ora<sid> Users NOTE You do not need to change the environment for <sapsid>adm on application servers because SAP applications still use Oracle 10g clients. Add the following entry to the tnsnames. 4.csh. you need to adapt the SQL*Net files that are located in the directory pointed to by the environment variable TNS_ADMIN.

the startdb or stopdb script fails with the following error message: ORA-00119: invalid specification for system parameter LOCAL_LISTENER 5. ■ If the environment variable TNS_ADMIN is not set. the Oracle client major version as used in the procedure below is Oracle 10.WORLD)(PROTOCOL = TCP)(HOST = <hostname>)(PORT = <listener_port>)) NOTE Although this entry is only needed on the database server or on central systems where the startdb or stopdb scripts are used.5 5. 2. Set DIR_SERVER_ORAHOME in the default profile to the value of the ORACLE_HOME environment variable of the ora<dbsid> user on the database server. Only valid for: ABAP+Java.13 Checking SAP Profile Parameters You have to check the following SAP profile parameters: ■ ■ ■ DIR_ORAHOME DIR_CLIENT_ORAHOME DIR_SERVER_ORAHOME Procedure 1. look for a tnsnames. 2010-09-10 PUBLIC 41/50 .13 Post-Upgrade Steps Checking SAP Profile Parameters 2. So you need to replace occurrences of the variable <Oracle_client_major_version> with 10. Set DIR_ORAHOME and DIR_CLIENT_ORAHOME in the instance profiles to the corresponding values of the ORACLE_HOME environment variable of the <sapsid>adm user.ora file under /etc and use this file for the change described below in the next step. Add the following entry to the tnsnames.ora file that is used by the <sapsid>adm user: LISTENER_<DBSSID>. These variables point to the ORACLE_HOME used by the application server.Java. NOTE ■ You only need to perform this procedure if your source database was Oracle 9. Without this entry. Otherwise the J2EE Engine cannot start because the location of the JDBC driver might still point to the path of the old Oracle server or client software home.WORLD = (ADDRESS = (COMMUNITY = SAP. ■ At the publication time of this guide.Java Add-In | 5.2. you might have to change the location of the JDBC driver after you have upgraded the database server or client software. it is recommended to repeat the change described above on all application servers.14 Changing the Location of the JDBC Driver If you have an SAP system with Java components.

properties. 3.properties: ■ ■ 2. you use a text editor to change the JDBC driver location.ConfigTool by double-clicking the configtool. where XXXXXXX is the instance number 42/50 PUBLIC 2010-09-10 .JavaParameters 2. start the J2EE Engine . Replace the old driver location with the new one: /oracle/client/<Oracle_client_major_version>x_<32/64>/instantclient/ <java_class_archive>.5 5.driverLocation. Procedure 1.driverLocation= followed by the driver location: ■ cluster_data/Propertysheet instance. Change to the correct directory containing the file config.Java Add-In | /usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee/configtool End of: ABAP+Java. Make sure that you nonetheless replace the old driver location in all locations belonging to your SAP system. CAUTION Do not change the file <java_class_archive>.jar. 1.jar ■ ojdbc14. Change the file config.14 Post-Upgrade Steps Changing the Location of the JDBC Driver You change the location of the JDBC driver as follows: ■ In files that are located in the database. Only valid for: Java | /usr/sap/<SAPSID>/JC<instance_number>/j2ee/configtool End of: Java | Only valid for: ABAP+Java. which is one of the following: ■ classes12.jar ■ ojdbc6.jar ■ ojdbc5.IDXXXXXXX/ IDXXXXXXX. ■ In files that are not located in the database. Use the Edit mode to replace the driver location in the following property sheets that contain the string rdbms.Java Add-In | Open the file with your text editor and search for the property rdbms. 2. some of the JDBC driver references stated in this procedure might not exist in your SAP system. you use the J2EE Engine Config Tool to change the JDBC driver location. CAUTION Depending on your SAP version.jar In the same directory as in the first step.jar where <Oracle_client_major_version> is the major version of the Oracle client that you are using after this upgrade. Change to Configuration Editor mode.properties as follows: 1.sh file.

3. There might be several IDXXXXXX. 3. Change to the correct directory containing the file bootstrap. If you have more than one server or dispatcher you must modify all relevant property sheets. Only valid for: Java | /usr/sap/<SAPSID>/JC<instance_number>/SDM/program/config End of: Java | Only valid for: ABAP+Java. ■ ■ cluster_data/dispatcher/IDXXXX/kernel/propertysheet ConfigurationManager cluster_data/server/IDXXXX/kernel/propertysheet ConfigurationManager where XXXX is the instance number NOTE 3. Replace the old driver location with the new one: /oracle/client/<Oracle_client_major_version>x_<32/64>/instantclient/ <java_class_archive>. Change the file bootstrap.Java Add-In | /usr/sap/<instance_ID>/DVEBMGS<instance_number>/j2ee/cluster/bootstrap End of: ABAP+Java.ConfigTool. Replace the old driver location with the new one: /oracle/client/<Oracle_client_major_version>x_<32/64>/instantclient/ <java_class_archive>. Change the driver location in the instance profile as follows: 1.JavaParameters properties in the property sheet.5 5. Open the file with your text editor and search for the property j2ee/dbdriver.properties as follows: 1. Change to the correct directory containing the instance profile <SAPSID>_JC<instance_number>_<host>: /usr/sap/<SAPSID>/SYS/profile 2. Change the file sdmrepository.jar 5.driverLocation.properties: ■ ■ 2.14 Post-Upgrade Steps Changing the Location of the JDBC Driver NOTE Make sure that you change all occurrences. Change to the correct directory containing the file sdmrepository. 3.jar 4.sdc as follows: 1.sdc: ■ ■ 2.Java Add-In | Open the file with your text editor and search for the property rdbms.Java Add-In | /usr/sap/<SAPSID>/DVEBMGS<instance_number>/SDM/program/config End of: ABAP+Java. Only valid for: Java | /usr/sap/<SAPSID>/JC<instance_number>/j2ee/cluster/bootstrap End of: Java | Only valid for: ABAP+Java.Java Add-In | Search for the following text: 2010-09-10 PUBLIC 43/50 . Close the J2EE Engine .

jar 6. If required. 44/50 PUBLIC 2010-09-10 . If R3trans connects without problems.Java Add-In | /usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee End of: ABAP+Java.properties: ■ ■ 2. Replace the old driver location with the new one: /oracle/client/<Oracle_client_major_version>x_<32/64>/instantclient/ <java_class_archive>. Change the file templateconfigurator.jar 7.jar End of: ABAP+Java.Java Add-In | Open the file with your text editor and search for the property RDBMS_DRIVER_LOCATION.Java.Java Add-In | /usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee/deploying End of: ABAP+Java.15 Post-Upgrade Steps Starting the SAP System <Param type="String" hide="false" name="jarPaths" encrypted="false" displayName="Driver Paths (separated by .)"> 3. 3. Only valid for: Java | /usr/sap/<SAPSID>/JC<instance_number>/j2ee/deploying End of: Java | Only valid for: ABAP+Java. start the SAP system: startsap Check the new Oracle version using SAP transaction ST04.Java Add-In | 5. Replace the old driver location with the new one: /oracle/client/<Oracle_client_major_version>x_<32/64>/instantclient/ <java_class_archive>. Change to the correct directory containing the file templateconfigurator.Java Add-In | Open the file with your text editor and search for the property rdbms. 2. Only valid for: Java | /usr/sap/<SAPSID>/JC<instance_number>/j2ee End of: Java | Only valid for: ABAP+Java. Change to the correct directory containing the file rdb.5 5. 3.properties as follows: 1.properties as follows: 1.properties: ■ ■ 2. Change the file rdb.15 Starting the SAP System You need to restart the SAP system.driverLocation. replace the old driver location with the new one: /oracle/client/<Oracle_client_major_version>x_<32/64>/instantclient/ <java_class_archive>. Procedure 1.

you need to change it to UTF8. the national character set must be UTF8.17 Configuring the New Features for Oracle Database 11g Release 2 (11. Procedure For more information about new features with Oracle Database 11g Release 2 (11. This note provides links to other SAP notes that describe how to configure or activate each new feature.2) You need to configure the new Oracle Database 11g Release 2 (11.2) see SAP Note 1431800.5 5. Procedure If necessary. follow SAP Note 669902 to change the national character set to UTF8.16 Post-Upgrade Steps Checking the National Character Set 5.2) features. 2010-09-10 PUBLIC 45/50 . You can expect to experience severe problems during SAP upgrades if the database national character set is not set to UTF8. If you already use a Java system or plan to use one in the future. 5.16 Checking the National Character Set If your database still runs with a national character set (NLS_NCHAR_CHARACTERSET) different from UTF8.

and database tools Technical names of system objects. SELECT and INCLUDE Keys on the keyboard http://www. for example. names of variables and parameters. for example. These include report names. for example. and names of installation. messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths. SAP Note 123456 ■ Words or characters quoted from the screen. These include field labels.com /example 123456 Example Example EXAMPLE EXAMPLE 46/50 PUBLIC 2010-09-10 . for example. upgrade. ■ Cross-references to other documentation or published works ■ Output on the screen following a user action.sap. menu names. program names. screen titles. database table names. and key concepts of a programming language when they are surrounded by body text. “Enter your <User Name>”. pushbutton labels. menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note. Arrows separating the parts of a navigation path. transaction codes. for example. and menu options.Typographic Conventions Example <Example> Description Example Example Example Example Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system.

S/390 Parallel Enterprise Server. SAP. xApps. DB2 Connect. OS/2. Nothing herein should be construed as constituting an additional warranty. POWER. WinFrame. XHTML and W3C are trademarks or registered trademarks of W3C®. Parallel Sysplex. System z. Inc. System x. System z9. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. Duet. All rights reserved. i5/OS. z/OS.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www. R/3. OpenPower. if any. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. ICA. National product specifications may vary. RACF. z10. PostScript. VideoFrame. SAP NetWeaver.. 2010-09-10 PUBLIC 47/50 . ByDesign. z/VM. POWER6. Microsoft.S. and MultiWin are trademarks or registered trademarks of Citrix Systems. RETAIN. Inc. Citrix. without representation or warranty of any kind. PowerPC. and Motif are registered trademarks of the Open Group. Disclaimer Some components of this product are based on Java™. The information contained herein may be changed without prior notice. the Adobe logo. xApp. Netfinity. Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Program Neighborhood. Outlook. XML. 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. X/Open. POWER5+. Java is a registered trademark of Sun Microsystems. 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. HTML. pSeries. The information contained herein may be changed without prior notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only. DB2. Massachusetts Institute of Technology. HACMP. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. PowerVM. as is any decompilation of these components. Windows. Power Architecture. AS/400. eServer. System p5. WebSphere. and PowerPoint are registered trademarks of Microsoft Corporation. Acrobat. iSeries. OS/400. and SAP Group shall not be liable for errors or omissions with respect to the materials. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way. GPFS. System i. System p. PartnerEdge. UNIX. BladeCenter. OS/390. These materials are subject to change without notice.sap. MetaFrame. Adobe. z9. SAP Business ByDesign. xSeries. JavaScript is a registered trademark of Sun Microsystems. used under license for technology invented and implemented by Netscape. and other countries. System i5. MVS/ESA. Oracle is a registered trademark of Oracle Corporation. zSeries. World Wide Web Consortium. Intelligent Miner. Linux is the registered trademark of Linus Torvalds in the U. System z10. OSF/1. POWER6+. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Excel.com © Copyright 2010 SAP AG. All other product and service names mentioned are the trademarks of their respective companies. IBM. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited. Redbooks. BatchPipes. DB2 Universal Database. POWER5. System Storage. Data contained in this document serves informational purposes only. Inc. S/390. AIX.

com/instguides 48/50 PUBLIC 2010-09-10 .sap.Documentation in the SAP Service Marketplace You can find this document at the following address: http://service.

.

sap. The information contained herein may be changed without prior notice. .com © Copyright 2010 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.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.

Sign up to vote on this title
UsefulNot useful