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

2): UNIX
For Oracle Patch Set Release 11.2.0.2 and 11.2.0.3
Target Audience ■ Technology Consultants ■ System Administrators ■ Database Administrators ■ Developers

PUBLIC Document version: 3.00 – 2011-12-20

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

3.00 2.10 2.01 2.00 1.14 1.13 1.12 1.11 1.10 1.01 1.00

2011-12-20 2011-09-16 2011-05-19 2011-04-14 2010-09-10 2010-08-25 2010-08-03 2010-06-15 2010-06-09 2010-04-27 2010-04-01

Major update for Oracle Patch Set Release 11.2.0.3 Various corrections Various corrections Major update for Oracle Patch Set Release 11.2.0.2 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

2011-12-20

Table of Contents

Chapter 1 1.1 1.2 1.3 Chapter 2 2.1 2.2 2.3 2.4 2.5 Chapter 3 3.1 3.2 3.3 3.4 3.5 3.5.1 3.5.2 3.5.3 3.5.4 3.5.5 3.6 3.7 Chapter 4 4.1 4.2 4.3 4.3.1

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 . . . . . . . . . . . . . . . . . . . . . . . 10 Reviewing the Oracle-Specified Kernel Parameters and Shell Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Checking Additional Requirements for the Upgrade . . . . . . . . . . . . . . . . . . . . 10 Checking the SAP System Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Correct UNIX Users, Groups, and Authorizations . . . . . . . . . . . Checking the Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating the Oracle Installation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Software Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . Database Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking and Setting the Environment Variables . . . . . . . . . . . . . . . . . . . . . . Backing Up the Central Oracle Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Oracle Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Required SAP Bundle Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying and Adapting the SQL*Net Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the Pre-Upgrade Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the Pre-Upgrade Scripts (Oracle 9.2.0.8) . . . . . . . . . . . . . . . . . . . . . . Oracle Database Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing Up the Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shutting Down the SAP System and Oracle Listener Process . . . . . . . . . . . . . . Database Structure Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Database Upgrade Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 13 13 15 16 17 17 19 20 21 22 22 24 27 27 27 28 28

2011-12-20

PUBLIC

3/50

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 5.18 5.19

Starting the Database Upgrade Assistant (Oracle 9.2.0.8) . . . . . . . . . . . . . . . . . 30 Checking the oratab Entry (Oracle 9.2.0.8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Post-Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finalizing the Environment of the ora<dbsid> User . . . . . . . . . . . . . . . . . . . . Creating a Symbolic Link for Runtime Oracle Home . . . . . . . . . . . . . . . . . . . . Checking the Upgraded Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating BR*Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Post-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Symbolic Link for the Data Shared Library . . . . . . . . . . . . . . . . . . . Backing Up the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Listener Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Renaming or Deleting the Old $ORACLE_HOME/bin Directory . . . . . . . . . . Checking the Read Authorization of the <sapsid>adm User . . . . . . . . . . . . . Updating the Oracle Instant Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 35 36 36 37 38 39 39 40 40 40 41 41 41 42 43 43 46 47 47

4/50

PUBLIC

2011-12-20

1

Introduction

1 Introduction

This documentation describes how to upgrade the Oracle database for the SAP system on the UNIX operating system: ■ From source release Oracle 9.2.0.8, Oracle Database 10g Release 2 (10.2.0.4 or 10.2.0.5), Oracle Database 11g Release 2 (11.2.0.1), or higher ■ To target release Oracle Database 11g Release 2 (11.2) (11.2.0.2 or 11.2.0.3 or higher) This guide is suitable for both major release upgrades (for example, from Oracle 9.2.0.8 or Oracle 10.2.0.5 to Oracle 11.2.0.2 or Oracle 11.2.03) and for patch set upgrades (for example, from Oracle 11.2.0.1 to 11.2.0.2 or 11.2.0.3). In both cases, the upgrade target release is the current 11.2 patch set release. This guide does not cover upgrades of Oracle databases with Real Application Clusters (RAC) Automatic Storage Management (ASM), or Exadata. We plan to document these at a later date. 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.
CAUTION

Oracle 11.2 is only supported for SAP systems with an EX2 kernel or higher. Oracle 11g is released only with SAP products based on kernel 640 (640_EX2) or higher. There is no general release provided for older SAP releases 3.1I up to and including 4.6C. For these older releases, only an upgrade certification is provided for valid upgrade paths – for more information, see SAP Note 1398634. For upgrade certification, the SAP kernel needs to be EXT kernel (for releases 3.1 up to and including 4.5B) or EX2 kernel (for release 4.6C). 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.
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]

2011-12-20

PUBLIC

5/50

2.2 SAP Notes for the Upgrade Make sure that you read the following SAP Notes: Number Title Remarks 1431800 1454627 Oracle 11. see the New Features documentation from Oracle. see SAP Note 1431799.2) [page 47] 1.0.2). RECOMMENDATION Especially when you are performing a major release upgrade – that is. For example. More Information Configuring the New Features for Oracle Database 11g Release 2 (11. and Oracle Database Upgrade Assistant (DBUA) to perform the upgrade. If your database runs on a 32-bit platform (Linux 32–bit).com/technology.2. You can access the complete Oracle documentation at the Oracle Technology Network (OTN) website at www. ■ To make this documentation easier to read.8 or Oracle 10. NOTE Make sure you are using the Oracle Universal Installer (OUI) shipped with the installation CDs for Oracle Database 11g Release 2 (11. Naming Conventions We use <DBSID> for the database instance identifier and <SAPSID> for the SAP system identifier. For more information on the current patch set. Required late-breaking information 6/50 PUBLIC 2011-12-20 . only the location for 64-bit platforms is used.1 Introduction New Features ■ You use the tools Oracle Universal Installer (OUI). Make sure you are using the latest version of the software (11. replace as appropriate occurrences of 64 with 32.2).0: Central Technical Note Additional Info / Corrections to Oracle 11g Upgrade Guide Provides a starting point for information about Oracle 11g with multiple links to notes on Oracle 11g. 1.2.1 New Features For the complete list of new features of the Oracle Database 11g Release 2 (11. replace 112_64 with 112_32. MOPatch (Opatch). These can be different if your SAP system uses Multiple Components in One Database (MCOD).2.0.3 at the time of writing).1 1. when your source system is Oracle 9. Oracle SQL*Plus.0.4 or 10.oracle.5 – we recommend that you check the most important new features in the Oracle documentation.0.2.

2.2. which replaces the native CONNECT role from Oracle 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 Describes the configuration of an SAP installation with the SAP-specific database user profile SAPUPROF Contains the newest installation scripts Describes how to deinstall the Oracle 11g Release 2 (11.2) software Describes how to set ORACLE_BASE in an SAP environment 1.0 Required for upgrading Oracle client software to Oracle 11g Release 2 (11.3 Introduction More Information on SAP Service Marketplace Title Remarks Number 1398634 1431798 Oracle Database 11g: Integration into the SAP environment Oracle 11.0: Troubleshooting the Database Upgrade Oracle 11.2.sap.0: Troubleshooting the Software Installation Oracle 11.2.3 Lists the status of Oracle patch sets and interim patches for 11.2.2.1 1.0: Patches / Patch collections for 11.2.2 Oracle 11.2.2.0 Upgrade Scripts Oracle 11.0: Software Installation Oracle Software Deinstallation Oracle 11.0.2.0.2.0: Current Patch Set Oracle 11.2 Describes the shell and SQL upgrade scripts for 11.0.2.sql) Oracle Database 10g: New database role SAPCONN Using OPatch to install Oracle patches MOPatch – Install Multiple Oracle Patches in One Run BR*Tools Support for Oracle 11g SAP Database User Profile SAPUPROF Oracle 11.3 More Information on SAP Service Marketplace You can find more information as following on SAP Service Marketplace: Description Internet Address http://service.2) Describes the current Oracle security fixes Describes how to update the SAPDBA role after the upgrade Describes the new SAPCONN role.0: Setting of ORACLE_BASE in SAP Environments 1431796 1431797 1431799 1631931 1503709 1431793 1431794 850306 134592 834917 839182 1027012 1430669 1519872 1524205 1525025 1521371 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.0: Patches / Patch collections for 11.2.0: Instant Client Oracle Critical Patch Update Program Importing the SAPDBA role (sapdba_role.0: Database Parameter Settings Oracle 11.0.2.2.com/notes Title SAP Notes None 2011-12-20 PUBLIC 7/50 .3 Oracle 11.

sdn.sap.com/swdc http://service.com/ instguides Database Upgrades Oracle https://service. the guide you are now reading Oracle download area for patches and software http://service.com/irj/sdn/ Description Title Oracle Database Administration 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.sap.sap.com Oracle Download Area oracle-download 8/50 PUBLIC 2011-12-20 .1 1.sap.3 Introduction More Information on SAP Service Marketplace Internet Address www.

0.3.0.5.2 2. you need to first update the source database to at least patch set 10. 2011-12-20 PUBLIC 9/50 . You check the hardware and software requirements [page 10]. Prerequisites In the following special cases you need to obtain more information: ■ If you are upgrading from Oracle 10. 2. 5.2.2 to Oracle Database 11g Release 2 (11.4 or 10. 3.2 or 11.1 Planning Checking the Original Version of Your Database 2 Planning RECOMMENDATION Before the production upgrade.2. obtain more information. 1.2) in manual mode ■ If the source database runs Oracle 10. You can then perform the upgrade from 10. For more information in the special cases mentioned above. To check the original version of your database. 2. 4.2) upgrade at the Oracle Technology Network (OTN) website. make sure that you perform a test upgrade on your backup system.2.2. do one of the following from the environment of the source database: ■ Enter the following command: sqlplus —version ■ Enter the following commands: sqlplus / as sysdba SQL> select version from v$instance. You review the Oracle-specified kernel parameters and shell limits [page 10]. Process 1.0.0.2.5 to 11. if necessary. see the documentation for the Oracle Database 11g Release 2 (11. as described in this guide. You check additional requirements for the upgrade [page 10].0. 2.1 Checking the Original Version of Your Database You need to check the original version of the database you want to upgrade and.2. You check the original version of your database [page 9].0. You check the SAP System prerequisites [page 11].2.

see SAP Note 758563.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. You can access the complete Oracle documentation as a member of the Oracle Technology Network (OTN).4 Checking Additional Requirements for the Upgrade You need to check the additional requirements for the Oracle database upgrade as described in this section. To check for your application or product. Procedure Obtain the recommended shell limits and kernel parameters from the relevant Oracle database installation guide for your operating system. which you can find at: www. 10/50 PUBLIC 2011-12-20 . Procedure 1.2 Planning Checking Hardware and Software Requirements 2.com/notes 2.oracle. Make sure you have read the SAP Notes for the upgrade [page 6].2). and SAP kernel release 640_EX2 and above. If the recommended settings are not suitable for your system you must tune the kernel parameters accordingly.2 2.com. The complete list of hardware and software requirements for every platform is included in the Oracle documentation.com/technology/documentation Select the appropriate documentation for Oracle Database 11g Release 2 (11. Download the recommended documents from My Oracle Support (formerly Oracle Metalink) at https://support. For access to My Oracle Support.sap. Make sure your operating system and initial database version meets SAP requirements.2 is released and certified for SAP products running with SAP BASIS 640 and above. see the Product Availability Matrix (PAM) at http://service. These are only recommendations from Oracle for optimizing the system performance in production environments.sap.2 Checking Hardware and Software Requirements Procedure You need to check that you meet the hardware and software requirements for running the new Oracle release.com/pam. 2. which you can find at http://service.oracle. 2. Oracle 11.2).

Make sure that you download the complete 640_EX2 kernel: both SAPEXE. see SAP Note 1430669. download the 640_EX2 kernel from SAP Service Marketplace. In such cases we recommend you to start the OUI and the DBUA directly from the console.2 Instant Client software from: http://service. as of release 7.10 (patch level 30).2 2.20 (patch level 1) . we strongly recommend that you read document 169706. you need X-Windows software on the PC.or Release 7.2. This document provides information on all operating system prerequisites and is regularly updated. For SAP systems 7.com/swdc 8.5 Planning Checking the SAP System Prerequisites 3.5 Checking the SAP System Prerequisites Procedure 1. 1414733. In some situations the OUI and DBUA screens are not displayed correctly when started remotely. Download the Oracle Database 11g Release 2 (11.2) software and the latest patch sets and required patches or patch collection. Download the Oracle Database 11g Release 2 (11.com/oracle-download Download the latest version of the DBATOOLS (BR*Tools) to be used immediately after the database upgrade from: http://service. apply SAP Notes 1416108. You can download the patches from: http://service. The patches listed in the SAP Note referenced in SAP Note 1431800 are mandatory. Download the latest version of the Oracle 11. You need this document to review the hardware and software requirements and to configure the kernel parameters and shell limits. 7. The SAP Note with the list of patches is referenced in SAP Note 1431800.SAR.2) installation guide for your operating system from the Oracle Technology Network (OTN). To upgrade from a remote PC.SAR and SAPEXEDB.sap.com/oracle-download CAUTION 6. BR*Tools supports the Oracle Database 11g Release 2 (11.sap. RECOMMENDATION 5. 2. and 1433301 if you are running any of the following support packages: 2011-12-20 PUBLIC 11/50 .1.sap. To avoid severe database problems. If your source database is Oracle 9.2). as described in SAP Note 432861.8 and your SAP kernel is 640_REL kernel. For more information.0. If you have access to My Oracle Support. RECOMMENDATION 4. make sure that you install all these patches.XX when you are performing a major release upgrade.

02 SP02 ■ SAP_BASIS 7.01 SP06 ■ SAP_BASIS 7. The error is fixed in later support packages. For more information. you need to use DBSL (dboraslib.5 Planning Checking the SAP System Prerequisites 2.20 SP02 This resolves an error in an ABAP program that causes it to report problems during the consistency checks within transaction SE14. 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. see SAP Note 1456323.11 SP05 ■ SAP_BASIS 7.00 SP21 ■ SAP_BASIS 7. This error is seen only after the database has been upgraded to Oracle 11.2.10 SP10 ■ SAP_BASIS 7. ■ SAP_BASIS 7. 12/50 PUBLIC 2011-12-20 . 3. If your SAP system uses SAP Kernel 711.2 2.so) patch level 81 or higher.

0. Groups. Procedure Enter the following commands: echo $ORACLE_BASE touch $ORACLE_BASE/write_test rm $ORACLE_BASE/write_test If the user ora<dbsid> does not have write authorization. you run the pre-upgrade scripts [page 22]. you run the pre-upgrade scripts (Oracle 9.0. You install the database software [page 17]. 6. 3. You update the Oracle installation scripts [page 15].8. You check the software installation prerequisites [page 16]. 3. You check the directory structure [page 13]. Groups. log on to your system with the user root and enter the command: chgrp dba $ORACLE_BASE chmod 775 $ORACLE_BASE Check if you are able to start an XTERM as the Oracle user since this is the user who starts the OUI.2. 4.4.2. and Authorizations You need to check that the ora<dbsid> user has write authorization for the $ORACLE_BASE directory.8) [page 24].3 3. 7. 2.1 Checking the Correct UNIX Users. If your source database is Oracle 10. You check the correct UNIX users. For information about $ORACLE_BASE.1 Preparation Checking the Correct UNIX Users. and Authorizations 3 Preparation You have to complete the following preparations: 1. If your source database is Oracle 9. groups.0. see SAP Note 1521371.2. 5. 3. since you perform the database installation as user ora<dbsid>.2 Checking the Directory Structure You need to verify the availability and correctness of the following Oracle directories: ■ stage directory ■ Oracle inventory directory ■ Home directory 2011-12-20 PUBLIC 13/50 . and authorizations [page 13].

For the upgrade to Oracle Database 11g Release 2 (11.SAR After you have finished the extraction of all the RDBMS CDs. the following subdirectories exist under /oracle/stage/11202 or /oracle/stage/11203: ■ ■ ■ ■ ■ ■ database client grid examples gateways deinstall NOTE 2. client. When the RDBMS CDs have been mounted. For the database upgrade. If you only use a single instance database. these 2 SAR files alone are sufficient.3 3. The Oracle inventory directory maintains the inventory of all Oracle software installed on the system. If there is not enough space. Check the Oracle stage directory.2 Preparation Checking the Directory Structure Procedure 1. only the software contained within the component database is used. Ensure that the stage directories contain enough freespace prior to extraction of the SAR files. EXAMPLE For example.0.2: /oracle/stage/11202 ■ 11. 3. you can delete previous stage directories.SAR. and so on.2 or 11.0. The database components are packed in the files OR111264.SAR and OR211264.2. the following commands extract the database software (on DVDs 1 and 2): SAPCAR –xvf OR111264.3). The path to the Oracle inventory directory is mentioned in the Oracle inventory pointer 14/50 PUBLIC 2011-12-20 .0.SAR SAPCAR –xvf OR211264. The Oracle Database DVD contains a total of six or seven SAR files (depending on the platform). which include the various Oracle 11. In this case. gateways. you do not need to extract any other SAR files. If this directory does not exist. grid. create the staging directory as follows: ■ 11. usually called /oracle/stage. 1. Check the Oracle inventory directory.3: /oracle/stage/11203 2.0. For a single-instance database upgrade.2.2.2. create it manually. If it already exists it might contain software stages from previous installations or upgrades. use the SAP tool SAPCAR to extract all the RDBMS CDs to /oracle/stage/11202 or /oracle/stage/11203 as user ora<sid>. you only need to extract the database software.2 components such as database.

which are attached to SAP Note 1524205.3 Updating the Oracle Installation Scripts If a newer version is available. you need to update the installation scripts. the inventory is created in /oracle/oraInventory.loc./RUNINSTALLER -help ■ RUNINSTALLER_CHECK This script performs product-specific prerequisite checks with the following command: . 2011-12-20 PUBLIC 15/50 . By default in Oracle 11.loc points to the location where the Oracle inventory is located./RUNINSTALLER_CHECK ■ 11ginstall.loc file does not exist. After you have extracted the Oracle software to the staging area. 3. Prerequisites The SAP-specific installation scripts RUNINSTALLER.2. For more information.112/ e12255/oui2_manage_oracle_homes. we recommend that you update the Oracle Installation scripts. Before starting the installation of the new Oracle software on the database host.sh are located in directory SAP in the Oracle database software stage: ■ RUNINSTALLER This script installs the software with the following command: . enter the location where you want the inventory log files to be written to.oracle.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> ■ inst_group=dba If the Oracle Universal Installer has already been run on this host./RUNINSTALLER For help.sh This is the main script behind RUNINSTALLER and RUNINSTALLER_CHECK. If this is the first installation of Oracle database software on the host and the oraInst. and 11ginstall. generates the response file. file oraInst. you must create it at the end of the installation by running the orainstRoot. enter: .3 Preparation Updating the Oracle Installation Scripts 3.sh script as super user from the <oraInventory> location. make sure that the file oraInst. RUNINSTALLER_CHECK.htm. make sure that the variable inventory_loc in the file oraInst. From there you can download the relevant package for your release. This script supports installation in response file mode (interactive) and silent mode. see http://docs.com/cd/E11882_01/em. If this is the first time that the OUI has been executed on this host. and starts the Oracle installer.3 3.

The zip file contains the current version of the installation scripts.zip 3.3 3.2: cd /oracle/stage/11202/database ■ 11. 2.sh: ./rootpre. Prerequisites Make sure that the DISPLAY environment variable is set correctly.4 Preparation Checking the Software Installation Prerequisites Procedure Updating the Installation Scripts 1. Log on as the Oracle user ora<dbsid>. Change to the relevant directory as follows: ■ 11.sh: End of: AIX | Only valid for: AIX | 1.2.4 Checking the Software Installation Prerequisites You must check the prerequisites for the Oracle Universal Installer (OUI). call the script rootpre.2.sh End of: AIX | Procedure 1. 2.3: cd /oracle/stage/11203/database As the user root. call the script rootpre.SAVE Extract the zip file: $ cp 11ginstall-<release>-<patch-level>-complete. kernel parameters): 16/50 PUBLIC 2011-12-20 . Checking prerequisites for the OUI: ./runInstaller –executeSysPrereqs 2. 3.old $ unzip 11ginstall-<release>-<patch-level>-complete. 2. Checking operating system requirements (release. patches. 3.0. Rename the existing SAP directory as follows so that you have a saved copy of the previous version: mv SAP SAP. which is attached to SAP Note 1524205. Download the file 11ginstall_<release>_<patch_level>_complete. Copy the file to the database directory in the Oracle software stage directory.zip.0.zip /oracle/stage/11202/database $ cd /oracle/stage/11202/database $ mv SAP SAP. Change directory: cd /oracle/stage/11202/database Execute the following commands: 1. Only valid for: AIX | On AIX. 4.

0.2).0. NOTE You can install the database software while the SAP system is still running with the existing database (that is. You install the required SAP bundle patch [page 21]. you install the Oracle 11. You back up the central Oracle inventory [page 19]. You check and set the environment variables [page 17].1) before installing the new patch set release. to reduce downtime you can perform the following steps before you stop your system. 3. Starting with the Oracle 11. 4. 3. Oracle Database patch sets are full installations of the Oracle Database software. You can install the new database software while the SAP system is running with a lower patch set version.2.1 Checking and Setting the Environment Variables To install the database software. Process Flow 1. Oracle 10./RUNINSTALLER –check 4. Therefore. NOTE For more information about changes to the environment of the SAP user <sapsid>adm. Prerequisites Make sure that you set the environment variables as described below for the duration of this session only.5 Database Software Installation As part of preparations.5. You copy and adapt the old Oracle SQL*Net files [page 22].2 software. 5. You run the Oracle Universal Installer [page 20]. see Changing the Environment for the <sapsid>adm User [page 41].5 Preparation Database Software Installation cd SAP .2. Apply missing OS patches and set OS kernel parameters as recommended by the OUI. 3. 2. 2011-12-20 PUBLIC 17/50 .3 3. you need to check and set the environment variables of user ora<dbsid> because this user installs the Oracle software.2 patch set. This means that you do not need to install Oracle Database 11g Release 2 (11.

2.2.0.Solaris | LD_LIBRARY_PATH End of: HP Tru64 UNIX.UTF8 If your database still runs with the character set US7ASCII. /oracle or /oracle/<DBSID> For more information.WE8DEC AMERICAN_AMERICA. see SAP Note 1521371. <DBSID> ORACLE_SID ORACLE_HOME Make sure that it is set to the value of the current runtime Oracle home.Linux. EXAMPLE ■ When upgrading from 10.5: /oracle/<DBSID>/102_64 ■ When upgrading from 11. We recommend you to back up the old environment files before making the changes permanent. see SAP Note 102402.Linux.Solaris | $ORACLE_HOME/lib:$LIBPATH End of: AIX | Only valid for: HP Tru64 UNIX. Value <hostname>:0. For more information about WE8DEC.5 Preparation Database Software Installation CAUTION Do not make the changes to the environment permanent while the old database is still running.0. Procedure 1.2.2. You make them permanent in the database structure upgrade.Solaris | 18/50 PUBLIC 2011-12-20 .Linux.2: /oracle/<DBSID>/112_64 NLS_LANG One of the following values: AMERICAN_AMERICA.4 or 10. 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.1 or 11.3 3.0 NOTE <hostname>:0.0.0 is the host on which the Oracle Universal ORACLE_BASE Installer (OUI) is to be displayed.0. we strongly recommend moving it to WE8DEC or UTF8 before the upgrade.Solaris | $ORACLE_HOME/lib:$LD_LIBRARY_PATH End of: HP Tru64 UNIX. SAPDATA_HOME Only valid for: AIX | /oracle/<DBSID> Only valid for: AIX | LIBPATH End of: AIX | Only valid for: HP Tru64 UNIX.Linux.

oracle. The setting of the DISPLAY environment variable is described in SAP Note 432861.112/e12255/oui2_manage_oracle_homes. Make sure that the path variable does not contain the old $ORACLE_HOME/bin from the source database.2 Backing Up the Central Oracle Inventory Before you install the new Oracle database patch set software.loc ■ AIX. Or you can run the UNIX umask command and check that the returned value is 22. Linux: /etc/oraInst. If the Oracle inventory exists. Check if the temporary directory (usually /tmp) has at least 1024 MB of free space. 2011-12-20 PUBLIC 19/50 . Make a backup of your existing Oracle inventory before you start the Oracle Database 11g Release 2 (11. you need to back up the central Oracle inventory. If not.. check its location by looking at the entry in one of the following files: ■ HP-UX. set up the TEMP or TMPDIR environment variables to specify a temporary directory on the filesystem. NOTE Make sure there is only one $ORACLE_HOME/bin in your PATH or path variable.5 Preparation Database Software Installation Environment Variable Only valid for: HP-UX | Value Only valid for: HP-UX | SHLIB_PATH End of: HP-UX | $ORACLE_HOME/lib:$SHLIB_PATH End of: HP-UX | PATH or path Include $ORACLE_HOME/bin. you might have to start an X terminal (xterm) session and run the command: $ xhost + 3. Procedure 1. see http://docs. Solaris: /var/opt/oracle/oraInst.2) software installation.com/ cd/E11882_01/em.loc The location is shown as follows: inventory_loc=<path to Oracle inventory> 2.htm.3 3.5. 3. To make sure that the OUI screen can be displayed correctly on your system. where $ORACLE_HOME is the same as specified above in this table. For more information about which platform uses which location. RECOMMENDATION You can check the correctness of the new environment with the UNIX env command.

2. Confirm the default selections by choosing Next.0 export DISPLAY Bourne shell (sh) C shell (csh) Korn shell (ksh) setenv DISPLAY <host_name>:0. For more information. Procedure 1. Since you are already logged on as user root.0. 20/50 PUBLIC 2011-12-20 . ■ Install the current patch set. Choose OK and then Next.3 Installing the Oracle Database Software To install the database software.0 3. make sure that you: ■ Have updated the installation scripts as described in Updating the Oracle Installation Scripts [page 15]. CAUTION Before starting to install the Oracle software. Log on as user ora<dbsid>.2.2: cd /oracle/stage/11202/database/SAP . Make sure that the DISPLAY environment variable is set to <host_name>:0. you can switch to user ora<dbsid> by entering the following command: su – ora<dbsid>. you run the Oracle Universal Installer (OUI). 2.3 3./RUNINSTALLER ■ 11. Shell Used Command DISPLAY=<host_name>:0. Confirm the default option English and then choose Next. Confirm the default selection Single Instance Installation and then choose Next.5. see SAP Note 1524205. as described in SAP Note 1431799. Respond to the OUI as follows: Prompt or Condition Action Configure Security Updates Select Installation Option Grid Installation Options Select Product Language Do not select the checkbox.0. where <host_name> is the host on which you want to display the GUI of the Oracle Universal Installer (OUI).5 Preparation Database Software Installation 3. The runInstaller issues a warning./RUNINSTALLER 4.0 export DISPLAY=<host_name>:0. Start the OUI with the user ora<dbsid> as follows: ■ 11.0.3: cd /oracle/stage/11203/database/SAP .

you need to install the required SAP bundle patch. NOTE You must install the SAP bundle patch using the Oracle tool MOPatch. using the Oracle tool MOPatch.4 Installing the Required SAP Bundle Patch After the Oracle database software installation. 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. For more information. You only need to install the latest SAP bundle patch because these patches are cumulative. If some of the checks are displayed as Failed. in SAP Notes – as <IHRDBMS>. Result The patch set software is now installed in the installation Oracle home. choose Exit and confirm the dialog box that appears. see SAP Note 1431793.5 Preparation Database Software Installation Prompt or Condition Action Select Database Edition Specify Installation Location Privileged OS Groups Perform Prerequisite Checks Confirm the default option Enterprise Edition and then choose Next. 5. 2011-12-20 PUBLIC 21/50 . After installing the SAP bundle patch. This screen displays the operating system groups for the DBA and the operator. The SAP bundle patch also delivers a set of upgrade scripts that automate most of the pre-upgrade and post-upgrade tasks. 3. This is referred to – for example. Review the information displayed on this screen and choose Finish.5. RECOMMENDATION Summary Finish We strongly recommend you to make sure that there are no failed checks before starting the software installation. It also displays the value for ORACLE_HOME.sh script as the root user from another session. Select this option and then Next. these are dba and oper. you do not need to install any critical patch updates (CPUs). Normally. Finish the software installation by executing the root. which you can find at SAP Note 1027012. To exit the OUI. This screen displays the value for ORACLE_BASE which is set in the environment. This screen checks if all the required system prerequisites for installation of the database software have been met.3 3. which should be /oracle/DBSID/ <release>.

Set ORACLE_HOME to the new installation Oracle Home <IHRDBMS>.6 Running the Pre-Upgrade Scripts You run the Oracle pre-upgrade scripts. If your source database is Oracle 9.2.2. Procedure 1. that is.2.2. the SQL*Net files are automatically copied from the source Oracle Home to the target Oracle Home.0. 3. 11.ora. NOTE If you use the dbua. you must copy and modify the old SQL*Net files.6 Preparation Running the Pre-Upgrade Scripts Prerequisites Check SAP Note 1431800 to find a cross-reference to the current SAP Note with the list of required patches to be installed. 3.0. Log on at the operating system level as the ora<dbsid> user.0. 2. Since your database is still running in the old environment. EXAMPLE setenv ORACLE_HOME /oracle/<DBSID>/11203 3. or 11.4. 4.sap. Install the SAP bundle patch according to the instructions in the SAP bundle patch README file.3 3.2.ora file. do not start the listener with the new listener.ora. This section only applies if your source database is Oracle 10.1. Edit the new SQL*Net files by adapting all file paths for the new directory. 2.ora.8. which automatically perform various tasks and checks on your database. 10.sh wrapper to perform the database upgrade with DBUA. see Running the Pre-Upgrade Scripts (9. Log on as user ora<dbsid>.ora file at this point. and tnsnames.5 Copying and Adapting the SQL*Net Files After the database software installation.2. 3. Add the following entry to the file listener. See SAP Note 1431793.5.5.ora: ADR_BASE_<listener_name> = /oracle/DBSID/saptrace Note that this is the same value as set in the database profile parameter diagnostic_dest. Procedure 1. listener.8) [page 24].0.0.2. Be sure to adapt the value of ORACLE_HOME in the listener. sqlnet. Copy the SQL*Net parameter files from <old_ORACLE_HOME>/network/admin to <new_ORACLE_HOME>/network/admin. The scripts do the following on your pre-upgrade database: 22/50 PUBLIC 2011-12-20 .0.

2011-12-20 PUBLIC 23/50 .2 environment with the database also started up.2.0.0.2 software home): ■ 11. the scripts are installed as part of the SAP bundle patch in the relevant Oracle 11.0.2 software home directory: ■ 11.sql Result You can check the results of the pre-upgrade scripts by looking at the following log files: ■ pre_upgrade_status.log SQL> @pre_upgrade_tasks.3: cd /oracle/<DBSID>/11203/sap/ora_upgrade/pre_upgrade Execute the following commands to perform pre-upgrade tasks.sql SQL> spool off 3.6 Preparation Running the Pre-Upgrade Scripts ■ 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 pre-upgrade environment of the database to be upgraded. By default.3: /oracle/<DBSID>/11203/sap/ora_upgrade Procedure 1.2: /oracle/<DBSID>/11202/sap/ora_upgrade ■ 11.0.2.log You can run the pre-upgrade scripts as often as necessary. Change to the correct directory by entering the relevant command (since the scripts have been extracted to the Oracle 11. 2. Prerequisites You are logged on as user ora<dbsid> in the Oracle 10.2: cd /oracle/<DBSID>/11202/sap/ora_upgrade/pre_upgrade ■ 11.log ■ pre_upgrade_tasks. which can improve the performance of the upgrade process: sqlplus / as sysdba SQL> spool pre_upgrade_tasks. The directory where the upgrade scripts are installed is called ora_upgrade.2.2.3 3. Execute the following commands to check the pre-upgrade status of your database: sqlplus / as sysdba SQL> @pre_upgrade_status.

24/50 PUBLIC 2011-12-20 .7 Preparation Running the Pre-Upgrade Scripts (Oracle 9.log.8.2.0.2 environment with the database also started up. which automatically perform checks on your database.2.2 software home directory: /oracle/<DBSID>/112_64/sap/ora_upgrade Procedure 1.0.8) You run the Oracle pre-upgrade scripts.log SQL> @utlu112i.2 software home): cd /oracle/<DBSID>/112_64/sap/ora_upgrade/pre_upgrade 2.5. the scripts are installed as part of the SAP bundle patch in the relevant Oracle 11. However. Prerequisites ■ You are logged on as user ora<dbsid> in the Oracle 9.0.3 3. By default. otherwise you might have problems during the upgrade. Make sure that you check any warnings and perform the suggested corrective actions mentioned in the log file. see Running the Pre-Upgrade Scripts [page 22].2.7 Running the Pre-Upgrade Scripts (Oracle 9. This section only applies if your source database is Oracle 9.2.2. you must ignore the warning regarding the possible setting of the database parameter remote_os_authent.2 environment. If your source database is Oracle 10. NOTE You always execute these scripts as the ora<dbsid> user connected to the database as sysdba in the Oracle 9.8) CAUTION Make the changes listed in the log file. ■ The directory where the upgrade scripts are installed is called ora_upgrade. Change to the correct directory by entering the relevant command (since the scripts have been extracted to the Oracle 11. 3.sql Result You can check the results of the pre-upgrade script by looking at the following log file utlu112i. which is reported as DEPRECATED. You can run the pre-upgrade script as often as you like on the pre-upgrade Oracle 9.4 or 10.0.0.2 database. Execute the following commands to check the pre-upgrade status of your database: sqlplus / as sysdba SQL> spool utlu112i.

However.7 Preparation Running the Pre-Upgrade Scripts (Oracle 9.3 3. 2011-12-20 PUBLIC 25/50 .8) CAUTION Make the changes listed in the log file. you must ignore the warning regarding the database parameter remote_os_authent.0.2. otherwise you might have problems during the upgrade. which is reported as DEPRECATED.

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

2. 4. 3. see SAP Note 1431797. or /oracle/ <DBSID>/920_64. You upgrade the database structure [page 28]. 2011-12-20 PUBLIC 27/50 .4 4. 2. 4. 1. are not active during the upgrade. /oracle/<DBSID>/112_64. If for any reason you have problems during the upgrade you must be able to restore the database from this backup.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.1 Backing Up the Oracle Database You must have a complete and usable database backup otherwise you might lose data. Stop the SAP application server by entering the following command as user <sapsid>adm: stopsap r3 Stop the Oracle listener by entering the following command as user ora<dbsid>: lsnrctl stop NOTE Make sure that processes that log on to the database. Check that the backup is usable. Procedure 1. Make sure that you reschedule these processes when the upgrade has finished. NOTE If you have problems during the upgrade. Create a complete database backup. for example. such as CRON jobs. Procedure 1. You back up the Oracle database [page 27]. You shut down the SAP system and Oracle listener process [page 27].1 Oracle Database Upgrade Backing Up the Oracle Database 4 Oracle Database Upgrade This section describes how to upgrade the Oracle database. 2. in /oracle/<DBSID>/102_64.

Set ORACLE_HOME_SRC and ORACLE_HOME_TGT. ■ Ensure that you have write permissions on /etc/oratab.1 to 11. dbua. 1.1 Starting the Database Upgrade Assistant To upgrade the database structure.2.2. you start the Database Upgrade Assistant to perform the upgrade [page 28].0.3: setenv ORACLE_HOME_SRC /oracle/<DBSID>/102_64 setenv ORACLE_HOME_TGT /oracle/<DBSID>/11203 ■ Enter these commands to upgrade from 11.0.sap.0. ■ If your source database is Oracle 9.2.sh is a wrapper script to automate most of the post-upgrade tasks.2. Prerequisites You have installed the database software [page 17].3 or from 11. ■ Before you start the DBUA make sure that the DISPLAY environment variable is correctly set.8.0.2.3 Oracle Database Upgrade Database Structure Upgrade 4.0.2. EXAMPLE ■ Enter these commands to upgrade from 10. Process Flow Perform one of the following.3. you upgrade the database structure. Procedure 1.2.0. you need to start the Oracle Database Upgrade Assistant (DBUA).8) [page 30].8.3 Database Structure Upgrade As part of the Oracle database upgrade [page 27].0.2.3: setenv ORACLE_HOME_SRC /oracle/<DBSID>/112_64 setenv ORACLE_HOME_TGT /oracle/<DBSID>/11203 2.0.2 to 11. Start the DBUA. see Starting the Database Upgrade Assistant (Oracle 9.4 4.0.2. 4. Result Now continue with the Post-Upgrade Steps [page 35].2. depending on your source database: ■ If your source database is not Oracle 9.8) [page 30].sh sets the environment internally. The DBUA tool is a graphical tool that leads you step by step through the upgrade. Prerequisites ■ dbua.0. If your source database is Oracle 9.sap.x to 11.8.0.2. Change to the correct directory: 28/50 PUBLIC 2011-12-20 . you start the Database Upgrade Assistant to perform the upgrade (Oracle 9.

and issues warnings if necessary. 2011-12-20 PUBLIC 29/50 .sh.4 4./dbua.sh -q 4. Run DBUA as follows: ■ For interactive mode./dbua.sap. Choose Next to continue. see SAP note 1431793 or run dbua. During this step. After the upgrade. enter the following command: . For more information on how to use dbua. Solution: Run the following command: brconnect -u / -c -f stats -t oradict_stats Solution: To recompile any invalid objects. Respond appropriately to the DBUA dialogs: The Welcome screen provides information about the upgrade assistant 1. The DBUA now analyzes the database to be upgraded. The Databases screen lets you select the database to be upgraded.sap. the SQL*Net profiles are copied.3 Oracle Database Upgrade Database Structure Upgrade cd $ORACLE_HOME_TGT/sap/ora_upgrade/post_upgrade 3. enter the following command: .sh ■ For silent mode.sap. you need to analyze and act on these warnings.sql to identify any new invalid objects due to the upgrade. 2./dbua. Select the correct database and choose Next.sql. RECOMMENDATION If the DBUA warns you of issues that need to be fixed before the upgrade. Run this script in query mode initially to verify that the environment is correct: .sh -silent 2. performs pre-upgrade checks. 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.sap. use SQL*Plus to execute the script $ORACLE_HOME/rdbms/admin/utlrp.sh.sap.sh -help. 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 14 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. run ORACLE_HOME/rdbms/admin/ utluiobj.sap.

components to be upgraded. if required. Make sure that the database instance has stopped after the upgrade. 4. The upgrade process itself runs for some time. Make sure that Configure the database with Enterprise Manager is not selected and choose Next. The DBUA automatically removes the database initialization parameters that are now obsolete in Oracle Database 11g Release 2 (11.4 4. 4. see the documentation for Oracle Database 11g Release 2 (11. 6. the DBUA automatically proposes the number of parallel processes to be used for the recompilation. Review the summary of changes and choose Back to make any final adjustments.8) To upgrade the database structure. The screen Recompiling Invalid Objects lets you choose whether the DBUA has to automatically recompile all PL/SQL modules after the upgrade. you do not need to select the Backup option on this screen. delete the environment variables ORACLE_HOME_SRC and ORACLE_HOME_TGT. 30/50 PUBLIC 2011-12-20 . Since you have already performed the database backup [page 27]. Before you start it. 3. 5.2. NOTE 4. the DBUA displays a summary of the changes to be made. you need to start the Oracle Database Upgrade Assistant (DBUA).2).2 Starting the Database Upgrade Assistant (Oracle 9. Start the database upgrade by choosing Finish. removed. and choose Next. 7. 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. 5.3. select Recompile invalid objects after the upgrade.0. If the database server has multiple CPUs. The screen Management Options lets you set up the database so that it can be managed with the Enterprise Manager. parameters to be added. 6. The screen Move Database Files lets you move the database files during the upgrade process. On the screen Recovery and Diagnostic Location. depending mainly on the size of the database and the capacity of the hardware. The DBUA tool is a graphical tool that leads you step by step through the upgrade. This includes the warnings that you ignored or did not fix. Accept the default values. If you select this option. make sure that you also specify the location and the size of the flash recovery area and its files. For a complete list of obsolete and deprecated parameters. Optionally. and changed after the upgrade. Select Do not move the database files as part of the upgrade and choose Next.2). When the DBUA has completed successfully the results of the upgrade are displayed Review the changes made and exit the DBUA.3 Oracle Database Upgrade Database Structure Upgrade 3.

sql.2. see Starting the Database Upgrade Assistant [page 28]. The DBUA now analyzes the database to be upgraded.4. 2.2 directories: ● ORACLE_HOME points to /oracle/<DBSID>/112_64 ● PATH ● LD_LIBRARY_PATH./oracle/<DBSID>/112_64/sap/ora_upgrade/ post_upgrade/sapuprof_profile 3. Prerequisites CAUTION Make sure that you start the DBUA in the Oracle 11. ■ Confirm that the following environment variables point to Oracle 11. Start the DBUA as follows: .0. or LIBPATH ■ Before you start the DBUA make sure that the DISPLAY environment variable is correctly set. Choose Next to continue.sql.2 user environment. The most common warning or information messages are as follows: Message Explanation or Solution Information message: Explanation: 2011-12-20 PUBLIC 31/50 .2. Procedure 1. 2.sql.3 Oracle Database Upgrade Database Structure Upgrade This section only applies if your source database is Oracle 9./oracle/<DBSID>/112_64/sap/ora_upgrade/ post_upgrade/set_remote_os_authent. The Databases screen lets you select the database to be upgraded./oracle/<DBSID>/112_64/sap/ora_upgrade/ post_upgrade/set_compatible. Select the correct database and choose Next.0.4 4. performs pre-upgrade checks. you need to analyze and act on these warnings. and issues warnings if necessary. ■ You check the oratab entry [page 33]. ■ Ensure that you have write permissions on /etc/oratab. To do this. Switch to $ORACLE_HOME/112_64/bin./dbua -diagnosticDest /oracle/<DBSID>/saptrace -recompile_invalid_objects true initParam audit_file_dest=/oracle/<DBSID>/saptrace/audit -emConfiguration NONE upgradeTimezone -postUpgradeScripts /oracle/<DBSID>/112_64/sap/ora_upgrade/ post_upgrade/post_upgrade_tasks. carefully check the first point below. If your source database is Oracle 10. RECOMMENDATION If the DBUA warns you of issues that need to be fixed before the upgrade. SHLIB_PATH.8. Respond appropriately to the DBUA dialogs: The Welcome screen provides information about the upgrade assistant 1.

Accept the default values. 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. Information Message: Explanation: SYSAUX Tablespace No action is necessary as the tablespace is created automatically by the DBUA.0. Updating BR*Tools [page 37].sql script after the database upgrade as described in roles. select Recompile invalid objects after the upgrade. No action is necessary. 3. If the database server has multiple CPUs. The screen Recompiling Invalid Objects lets you choose whether the DBUA has to automatically recompile all PL/SQL modules after the upgrade. Information Message: Explanation: Obsolete/Deprecated The pre-upgrade check script lists the obsolete or deprecated parameters. 32/50 PUBLIC 2011-12-20 . Since you have already performed the database backup [page 27]. Select Do not move the database files as part of the upgrade and choose Next. You need to adapt all other parameters as suggested by the pre-upgrade check. you need to perform this.3 Oracle Database Upgrade Database Structure Upgrade Message Explanation or Solution Database is using a timezone file older than version 14 Warning message: Database contains schemas with stale optimizer statistics Warning message: Database contains INVALID objects prior to upgrade Upgrade of TSTZ data is done automatically using one of the postupgrade custom scripts. Warning Message Solution: Parameter Update "compatible" must be set to at least 10. After the upgrade.1. run ORACLE_HOME/rdbms/admin/utluiobj. 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. 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. 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.sql. use SQL*Plus to execute the script $ORACLE_HOME/rdbms/admin/utlrp. You need to run role granted to some user/ the sapconn_role. Parameters: No action is necessary as these parameters are automatically removed by Information Message the DBUA. For this warning. and choose Next. The screen Move Database Files lets you move the database files during the upgrade process. no further action is necessary as the DBUA automatically switches this parameter after the upgrade. 4. If the check asks for space extension in any particular Tablespace Size tablespace.4 4.

6.0.2.3 Oracle Database Upgrade Database Structure Upgrade 5. 4.0. For a complete list of obsolete and deprecated parameters. On the screen Management Options. Review the summary of changes and choose Back to make any final adjustments. and changed after the upgrade. the DBUA displays a summary of the changes to be made. On the screen SYSAUX Tablespace. Size: 2048 MB Check AUTOEXTEND ON. depending mainly on the size of the database and the capacity of the hardware. if required.2). This includes the warnings that you ignored or did not fix. 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.3. The oratab file contains information about existing databases and the corresponding Oracle Homes on the database server. Start the database upgrade by choosing Finish. parameters to be added.data1 Check Reuse Existing Filename. the results of the upgrade are displayed Review the changes made and exit the DBUA. The upgrade process itself runs for some time. 8. components to be upgraded.8) To upgrade the database structure. specify the location for the datafiles along with the size and other attributes by entering the following: Datafile: /oracle/<SID>/sapdata1/sysaux_1/sysaux. When the DBUA has completed successfully. removed. If you select this option. see the documentation for Oracle Database 11g Release 2 (11. Make sure that Configure the database with Enterprise Manager is not selected and choose Next. On the screen Recovery and Diagnostic Location. you need to check the entry for the oratab file. The DBUA automatically removes the database initialization parameters that are now obsolete in Oracle Database 11g Release 2 (11.8. Before you start it. Increment Size 100 MB Maximum Size: Unlimited Choose Next to continue.3 Checking the oratab Entry (Oracle 9. 2011-12-20 PUBLIC 33/50 .2.2). 7. you can set up the database so that it can be managed with the Enterprise Manager. DBUA will update the oratab with the new Oracle Home after or during the upgrade (dbua must have write permission). This section only applies if your source database is Oracle 9.4 4. NOTE 5. 4. make sure that you also specify the location and the size of the flash recovery area and its files. 6.

Linux | Only valid for: Solaris | /var/opt/oracle End of: Solaris | Procedure 1. ■ For upgrades with the dbua.2 source database C11:/oracle/C11/920_64:N 2.sap.3 Oracle Database Upgrade Database Structure Upgrade You do not always need to perform this step: ■ For manual upgrades. EXAMPLE The entry for a system with a <DBSID> equal to C11 is as follows: ■ Oracle 11. If this entry does not exist.2 source database C11:/oracle/C11/102_64:N.sh wrapper script. Prerequisites You can find the oratab file as follows: ■ ■ Only valid for: AIX.2.0. you can also skip this step.4 4.0.2.Linux | /etc End of: AIX.HP-UX.HP-UX. you can skip this step.2 source database: C11:/oracle/C11/11202:N ■ Oracle 11. ■ You only have to perform this step if DBUA needs to find the database and Oracle Home to be upgraded from the oratab file.1 source database: C11:/oracle/C11/112_64:N ■ Oracle 10. insert it using a text editor. ■ Oracle 9. 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. 34/50 PUBLIC 2011-12-20 .

cshrc. 14. 18.dbenv_<hostname>. You back up the database [page 39].dbenv. you need to perform the steps described here. You change the environment for the <sapsid>adm user [page 41]. .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 (. . You create a symbolic link for the data shared library [page 39]. 10. 13.1 Post-Upgrade Steps Finalizing the Environment of the ora<dbsid> User 5 Post-Upgrade Steps After the Oracle database upgrade. 5. You start the listener process [page 40]. .2) [page 47]. 11. you change the location of the JDBC driver [page 43]. If necessary.dbenv. For more information about major release upgrades and patch set upgrades. If your SAP kernel is 640_REL.sh. You create a symbolic link for the runtime Oracle home [page 36]. see the introduction to this guide [page 5]. You perform post-upgrade tasks [page 38]. 3.2. You restart the SAP system [page 46]. 1. 19. you change the national character set of your database to UTF8 [page 47].csh. 8. You only need to perform this procedure if you are doing a major release upgrade. 5. You check the upgraded database [page 36]. 12.csh. 2011-12-20 PUBLIC 35/50 . You update the SQL*Net configuration files for the <sapsid>adm and ora<sid> users [page 42]. you update the SAP kernel to 640_EX2 [page 41]. 2. If you are doing a major release upgrade. If your source database is Oracle 9. 6. 17. 15. You check the read authorization of the <sapsid>adm user [page 40]. Procedure Check the values for the environment variables as described in Checking and Setting the Environment Variables [page 17]. you finalize the environment of the ora<dbsid> user [page 35]. and so on). 7. 4. You update BR*Tools [page 37]. You check the SAP profile parameters [page 43].5 5. 16. You rename or delete the old $ORACLE_HOME/bin directory [page 40]. You update the Oracle Instant Client [page 41]. It is not necessary if you are doing a patch set upgrade. 9. You configure the new features for Oracle Database 11g Release 2 (11.

2. Procedure Upgrading from source database 11. It links the runtime Oracle home <OHRDBMS> to the installation Oracle home <IHRDBMS>. see SAP Note 1525025.0.0.2. make sure that ORACLE_HOME is set to the runtime Oracle home: /oracle/<DBSID>/112_64 5.2 Post-Upgrade Steps Creating a Symbolic Link for Runtime Oracle Home NOTE Make sure that the environment does not contain any variables that still refer to the old database release.2.0.1 1.2) software in an Oracle Database 11g Release 2 (11. detach this Oracle home from the inventory and rename the old Oracle home: mv 112_64 11201 3. For more information on this step.2 Creating a Symbolic Link for Runtime Oracle Home This procedure is only necessary for the update from 11. Procedure 1.2) environment by entering the following commands: 1. Check that the database is now running with Oracle Database 11g Release 2 (11. Change to the required directory: cd /oracle/<DBSID> Upgrading from source database 11.5 5. 4.2 Delete the old symbolic link: rm 112_64 Create a symbolic link to the new Oracle home: ln -s 11203 /oracle/<DBSID>/112_64 Restart the database.0. 36/50 PUBLIC 2011-12-20 .3 Checking the Upgraded Database You need to check the upgraded database. In particular. Change to the required directory: cd /oracle/<DBSID> If no database is still running from the old 11. Create a symbolic link to the new Oracle home: ln -s 11203 /oracle/<DBSID>/112_64 Restart the database. Log on to the database as the ora<sid> user. 5.2. 2.0.1 or 11. 4.1 Oracle home.2. 1.2. 3.2.

sap.0.log. We recommend that you continue to use the spfile.sql Check the log POST_UPGRADE_STATUS. 4.0 VALID CATPROC 11.sql and create the SAPCONN role using sapconn_role.sql: SQL> @post_upgrade_status.2.3.3.sql $ORACLE_HOME/dbs cd $ORACLE_HOME/dbs 2011-12-20 PUBLIC 37/50 .2.2. The script is automatically extracted when you extract BR*Tools. the DBUA automatically creates an spfile.4 Post-Upgrade Steps Updating BR*Tools 2. This is essential so that the new release of BR*Tools works correctly.0. 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. Execute the following commands as the ora<dbsid> user to update the SAPDBA role: cp /usr/sap/<SAPSID>/SYS/exe/run/sapdba_role.2. Do not switch back to the initialization file after the upgrade.0. If your source database was Oracle 9. you need to update the SAPDBA role using the script sapdba_role.ora.0.8. Procedure 1. if the installed patchset is Oracle 11.0.8.5 5. RECOMMENDATION If the old database used an initialization file init<DBSID>. with the latest patch level.2.0 VALID 2. For example. Download the most current version of the BR*Tools from SAP Service Marketplace at: http://service.4 Updating BR*Tools You update BR*Tools to the latest release. 5. 3.0. EXAMPLE This is an example of the output from this command: COMP ID VERSION STATUS CATALOG 11. Change to the correct directory: cd $ORACLE_HOME/sap/ora_upgrade/post_upgrade Enter the following command to start SQLPLUS: sqlplus / as sysdba Run post_upgrade_status. Check that the value for the version returned from the above command is the same level as the installed patchset.2. Perform the following steps only if your source database was Oracle 9.2.com/swdc CAUTION 2.sql.

If not executed by dbua as part of the post-upgrade scripts. 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 38/50 PUBLIC 2011-12-20 . execute the SQL script sapuprof_profile.sql from SAP note 403704. 3. Execute the SQL script sapconn_role. perform the following tasks before gathering the Oracle optimizer statistics using brconnect: 1.sql as follows: cd $ORACLE_HOME/sap/ora_upgrade/post_upgrade sqlplus / as sysdba @sapuprof_profile.sql $ORACLE_HOME/dbs cd $ORACLE_HOME/dbs sqlplus /nolog @sapconn_role 4.0. 2.2. If your source database is Oracle 9.5 Performing Post-Upgrade Tasks You need to perform certain post-upgrade tasks. change database compatibility by entering the following as the ora<dbsid> user: cd $ORACLE_HOME/sap/ora_upgrade/post_upgrade SQL> conn / as sysdba SQL> @set_compatible 2. CAUTION 3. you have to enter both commands.5 5. Check database compatibility by executing the following command: SQL> show parameter compatible If not set to 11.5 Post-Upgrade Steps Performing Post-Upgrade Tasks 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. Apply script dbcheckora11_olap. Procedure 1. Make sure that you execute this command for every SAPSCHEMA_ID in your database.sql 5.8.0. Implement SAP delivered statistics from SAP Note 1020260.sql as follows: cp /usr/sap/<SAPSID>/SYS/exe/run/sapconn_role.2. Apply script dbstatc11.sql or dbcheckora11_oltp.sql from the same note 3.

sap.2 clients.Linux. Open a command prompt and change to the directory <new_oracle_home>/sap/ora_upgrade/ post_ugprade.5 5. For more information about update statistics. create a symbolic link in $ORACLE_HOME/lib as follows: cd $ORACLE_HOME/lib Only valid for: AIX. 5.Solaris | ln –s libnnz11. 5. NOTE This step is included as part of the software installation as of patch set 11. 5.Solaris | Only valid for: HP-UX | ln –s libnnz11.0.sl End of: HP-UX | For more information.2. see the documentation SAP Database Guide: Oracle at: www. 2011-12-20 PUBLIC 39/50 .exe and enter the following commands: SQL>connect / as sysdba SQL>@post_upgrade_status.7 Backing Up the Database You need to back up your upgraded Oracle Database 11g database.so libnnz10. Procedure 1. 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.so End of: AIX. Check the Oracle database parameters against SAP Note 1431798 and adjust them if necessary. After the software installation has finished.Linux.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.com/irj/sdn/ora SAP ON ORACLE KNOWLEDGE CENTER SAP Documentation Run post_ugprade_status. see SAP Note 1449619. Update the Oracle database statistics with BRCONNECT as follows: brconnect -c -u / -f stats -t all –f collect -p 4 NOTE 6.3.2 client) can use the newer Oracle 11.sl libnnz10.sdn.sql. From this directory start sqlplus.6 Post-Upgrade Steps Creating a Symbolic Link for the Data Shared Library 4.sql This provides an overview of the status of the upgraded database.

Procedure 1.10 Checking the Read Authorization of the <sapsid>adm User You check the read authorization of the <sapsid>adm user. If you want to delete the old Oracle home. 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.2 software.2) to prevent accidental usage of the old binaries.2 and higher). 40/50 PUBLIC 2011-12-20 . Procedure Perform a full database backup. see SAP Note 1525025 (for Oracle release 11. 2. as described in Copying and Adapting the SQL*Net Files [page 22]. Start the listener: lsnrctl start Check that you can remotely connect to the database through the listener: sqlplus SAP<SAPSCHEMA_ID>/pwd@SID 5.5 5. Procedure Rename the old Oracle home directory bin with the following command: 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.8 Post-Upgrade Steps Starting the Listener Process CAUTION You risk losing data if you do not back up your database.8 Starting the Listener Process You start the listener process. you need to rename the bin directory from the old $ORACLE_HOME (from release 10. 5. This is because the SAP system running on the database server might still use the Oracle 9i client software.40 and lower) running on the database server.2 or 9. 5.9 Renaming or Deleting the Old $ORACLE_HOME/bin Directory Once the database is running correctly.

2 database.12 Updating the SAP Kernel from 640_REL to 640_EX2 If you are running a 640_REL kernel. you must update it to 640_EX2.11 Updating the Oracle Instant Client You need to ensure that the SAP system runs with at least Instant Client release 10.0. We do not support running a 640_REL kernel with an Oracle 11.0.4 or 11. performing the kernel switch as described in SAP Note 1058988.2. Procedure Update the Oracle Database Instant Client for UNIX as described in SAP Note 1431794. The Instant Client 10.5 5.2.XX kernels). NOTE You do not need to change the environment for <sapsid>adm on application servers if you are still using the old Oracle 10g clients.0. 5.8 database.2.0.2. Procedure Update your SAP kernel to 640_EX2. for example: 2011-12-20 PUBLIC 41/50 . 5. NOTE This step also applies to SAP systems running the 640_REL kernel with the Oracle 9. but only on the database server. enter the following command as the ora<dbsid> user: chmod 755 $ORACLE_HOME 5.4 Version 5 (V5) or Oracle 11.0.2 is used immediately after the kernel switch to 640_EX2 or higher (including SAP 7. If this is not true.0. set the ORACLE_HOME environment variable to point to the location of the Oracle Database 11g software installation.2. On the database server. Make sure that the <sapsid>adm user has read authorization for the directory $ORACLE_HOME. Prerequisites You have an SAP System running with 640_REL kernel and you just upgraded your Oracle 9.2.2.11 Post-Upgrade Steps Updating the Oracle Instant Client Procedure 1.2.8 database to Oracle 11. Procedure 1. 2.13 Changing the Environment for the <sapsid>adm user You have to change the environment for the <sapsid>adm user.

and so on).dbenv_<hostname>. ■ For the <sapsid>adm user.14 Post-Upgrade Steps Updating the SQL*Net Configuration Files for the <sapsid>adm and ora<sid> Users /oracle/<DBSID>/112_64 2. NOTE DBUA modifies the SQLNET profiles in the directory <new already exist when the upgrade is started. ■ If the environment variable TNS_ADMIN is not set.ora file that is used by the <sapsid>adm user: 42/50 PUBLIC 2011-12-20 .ora file that is used by the <sapsid>adm user: LISTENER_<DBSSID>. the SQL*Net files are used from the specified location (even if ORACLE_HOME is set).ora file for the <sapsid>adm and ora<sid> users after the upgrade: ■ For the ora<sid> user. it is recommended to repeat the change described above on all application servers. Add the following entry to the tnsnames. look for a tnsnames.WORLD = (ADDRESS = (COMMUNITY = SAP.5 5. 4. 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. Add the following entry to the tnsnames.ora file under /etc and use this file for the change described below in the next step. Log out and log on again as the <sapsid>adm user.csh. Check whether R3trans can connect to the database: R3trans –d 5.14 Updating the SQL*Net Configuration Files for the <sapsid>adm and ora<sid> Users You need to update the tnsnames.cshrc. Procedure Adapting the SQL*Net Files for the ora<sid> User ORACLE_HOME>/network/admin if they 1. 3. 2. you need to adapt the SQL*Net files that are located in the directory pointed to by the environment variable TNS_ADMIN. Make sure that the change to the user environment is permanently stored in the profiles (. Without this entry. Determine the SQL*Net files used by <sapsid>adm as follows: ■ If the environment variable TNS_ADMIN is set.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. you need to adapt the SQL*Net files are located in the directory $ORACLE_HOME/network/admin. .

So you need to replace occurrences of the variable <Oracle_client_major_version> with 10.15 Checking SAP Profile Parameters You have to check the following SAP profile parameters: ■ ■ ■ DIR_ORAHOME DIR_CLIENT_ORAHOME DIR_SERVER_ORAHOME Procedure 1.15 Post-Upgrade Steps Checking SAP Profile Parameters LISTENER_<DBSSID>. 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.Java. the startdb or stopdb script fails with the following error message: ORA-00119: invalid specification for system parameter LOCAL_LISTENER 5. You change the location of the JDBC driver as follows: 2011-12-20 PUBLIC 43/50 .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.2. NOTE ■ You only need to perform this procedure if your source database was Oracle 9. 2. the Oracle client major version as used in the procedure below is Oracle 10.5 5. Without this entry.WORLD = (ADDRESS = (COMMUNITY = SAP.Java Add-In | 5. 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. it is recommended to repeat the change described above on all application servers. 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. ■ At the publication time of this guide. These variables point to the ORACLE_HOME used by the application server. you might have to change the location of the JDBC driver after you have upgraded the database server or client software. Only valid for: ABAP+Java.16 Changing the Location of the JDBC Driver If you have an SAP system with Java components.

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

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

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

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

screen titles. menu names.com /example 123456 Example Example EXAMPLE EXAMPLE 48/50 PUBLIC 2011-12-20 . messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths. for example. ■ Cross-references to other documentation or published works ■ Output on the screen following a user action.sap. and key concepts of a programming language when they are surrounded by body text. program names. 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. names of variables and parameters. and names of installation. database table names. transaction codes. Arrows separating the parts of a navigation path. for example. and database tools Technical names of system objects. SAP Note 123456 ■ Words or characters quoted from the screen. pushbutton labels. and menu options. These include field labels. “Enter your <User Name>”.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. for example. for example. These include report names. SELECT and INCLUDE Keys on the keyboard http://www. upgrade. for example.

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

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