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

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

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.2.0: Current Patch Set Oracle 11.3 Oracle 11.0 Required for upgrading Oracle client software to Oracle 11g Release 2 (11.2 Describes the shell and SQL upgrade scripts for 11.2.2) software Describes how to set ORACLE_BASE in an SAP environment 1.0.0.2.1 1.2.2.2.2) Describes the current Oracle security fixes Describes how to update the SAPDBA role after the upgrade Describes the new SAPCONN role.0: Instant Client Oracle Critical Patch Update Program Importing the SAPDBA role (sapdba_role.2.0: Troubleshooting the Software Installation Oracle 11.2.2.3 Lists the status of Oracle patch sets and interim patches for 11.2.0.3 Introduction More Information on SAP Service Marketplace Title Remarks Number 1398634 1431798 Oracle Database 11g: Integration into the SAP environment Oracle 11.com/notes Title SAP Notes None 2011-12-20 PUBLIC 7/50 .sap. 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.0: Software Installation Oracle Software Deinstallation Oracle 11.0: Patches / Patch collections for 11.2 Oracle 11.0: Patches / Patch collections for 11.0: Troubleshooting the Database Upgrade Oracle 11.0.3 More Information on SAP Service Marketplace You can find more information as following on SAP Service Marketplace: Description Internet Address http://service.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.2.2.2.2.0: Database Parameter Settings Oracle 11.0 Upgrade Scripts Oracle 11.

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

4 or 10. You check the original version of your database [page 9]. 5.2. if necessary.0. For more information in the special cases mentioned above. you need to first update the source database to at least patch set 10.1 Checking the Original Version of Your Database You need to check the original version of the database you want to upgrade and. To check the original version of your database. 2.2. 2.5. You check additional requirements for the upgrade [page 10].0.2.2 2.2. 2.1 Planning Checking the Original Version of Your Database 2 Planning RECOMMENDATION Before the production upgrade. obtain more information.0.0.2. 3. 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. see the documentation for the Oracle Database 11g Release 2 (11.2. Process 1. You check the SAP System prerequisites [page 11].5 to 11. make sure that you perform a test upgrade on your backup system.2 to Oracle Database 11g Release 2 (11. You check the hardware and software requirements [page 10].2. as described in this guide.0. Prerequisites In the following special cases you need to obtain more information: ■ If you are upgrading from Oracle 10. 1.2) in manual mode ■ If the source database runs Oracle 10. You review the Oracle-specified kernel parameters and shell limits [page 10].2 or 11. 2011-12-20 PUBLIC 9/50 . 4.3.2) upgrade at the Oracle Technology Network (OTN) website. You can then perform the upgrade from 10.0.

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

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

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

0.8. and Authorizations 3 Preparation You have to complete the following preparations: 1. You update the Oracle installation scripts [page 15]. You install the database software [page 17]. 7.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 . 3. you run the pre-upgrade scripts [page 22]. 3. 4.2.2. since you perform the database installation as user ora<dbsid>. and authorizations [page 13].0. 3. If your source database is Oracle 10. 5. groups.1 Checking the Correct UNIX Users. 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 check the directory structure [page 13]. For information about $ORACLE_BASE. 6. see SAP Note 1521371.2. Groups.0. You check the software installation prerequisites [page 16]. If your source database is Oracle 9. Groups.8) [page 24].3 3.1 Preparation Checking the Correct UNIX Users. 2. You check the correct UNIX users. 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. and Authorizations You need to check that the ora<dbsid> user has write authorization for the $ORACLE_BASE directory. you run the pre-upgrade scripts (Oracle 9.4.

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

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

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

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

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

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

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

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

Log on as user ora<dbsid>. see Running the Pre-Upgrade Scripts (9.1.2. 3. 10. which automatically perform various tasks and checks on your database. If your source database is Oracle 9.2.3 3. The scripts do the following on your pre-upgrade database: 22/50 PUBLIC 2011-12-20 . Be sure to adapt the value of ORACLE_HOME in the listener. Procedure 1.sh wrapper to perform the database upgrade with DBUA. do not start the listener with the new listener. 2.0.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. Since your database is still running in the old environment.5. Copy the SQL*Net parameter files from <old_ORACLE_HOME>/network/admin to <new_ORACLE_HOME>/network/admin. This section only applies if your source database is Oracle 10. 4.6 Running the Pre-Upgrade Scripts You run the Oracle pre-upgrade scripts. and tnsnames. Set ORACLE_HOME to the new installation Oracle Home <IHRDBMS>.ora. you must copy and modify the old SQL*Net files. 2.0.2.8.2. 3.ora. NOTE If you use the dbua. Procedure 1.sap. See SAP Note 1431793. Edit the new SQL*Net files by adapting all file paths for the new directory. Install the SAP bundle patch according to the instructions in the SAP bundle patch README file.0. 3.2.0. or 11. Add the following entry to the file listener. listener.5 Copying and Adapting the SQL*Net Files After the database software installation.0.ora file. sqlnet.2. that is.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.4.0. 11.ora.ora file at this point. EXAMPLE setenv ORACLE_HOME /oracle/<DBSID>/11203 3. Log on at the operating system level as the ora<dbsid> user.2.8) [page 24]. the SQL*Net files are automatically copied from the source Oracle Home to the target Oracle Home.

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

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

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

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

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

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

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

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

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

32/50 PUBLIC 2011-12-20 . If the check asks for space extension in any particular Tablespace Size tablespace. The screen Move Database Files lets you move the database files during the upgrade process. Updating BR*Tools [page 37]. you need to perform this. For this warning. Information Message: Explanation: SYSAUX Tablespace No action is necessary as the tablespace is created automatically by the DBUA. 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. Information Message: Explanation: Obsolete/Deprecated The pre-upgrade check script lists the obsolete or deprecated parameters. Select Do not move the database files as part of the upgrade and choose Next. Warning message: Solution: Deprecated CONNECT The default connect role is deprecated as of Oracle 10g. no further action is necessary as the DBUA automatically switches this parameter after the upgrade. After the upgrade. you do not need to select the Backup option on this screen.sql script after the database upgrade as described in roles. If the database server has multiple CPUs. use SQL*Plus to execute the script $ORACLE_HOME/rdbms/admin/utlrp. run ORACLE_HOME/rdbms/admin/utluiobj.sql to identify any new invalid objects due to the upgrade. select Recompile invalid objects after the upgrade. 4.sql. The screen Recompiling Invalid Objects lets you choose whether the DBUA has to automatically recompile all PL/SQL modules after the upgrade. 3. Since you have already performed the database backup [page 27].0.1. 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. You need to run role granted to some user/ the sapconn_role. Warning Message Solution: Parameter Update "compatible" must be set to at least 10.4 4. Accept the default values. No action is necessary. the DBUA automatically proposes the number of parallel processes to be used for the recompilation.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. You need to adapt all other parameters as suggested by the pre-upgrade check. and choose Next. Parameters: No action is necessary as these parameters are automatically removed by Information Message the DBUA.

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

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

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

4.1 or 11.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. Change to the required directory: cd /oracle/<DBSID> If no database is still running from the old 11. For more information on this step.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. Create a symbolic link to the new Oracle home: ln -s 11203 /oracle/<DBSID>/112_64 Restart the database. 2. Log on to the database as the ora<sid> user.0.2.1 1.3 Checking the Upgraded Database You need to check the upgraded database. make sure that ORACLE_HOME is set to the runtime Oracle home: /oracle/<DBSID>/112_64 5.2. see SAP Note 1525025. 1. 2. 36/50 PUBLIC 2011-12-20 .0.2. It links the runtime Oracle home <OHRDBMS> to the installation Oracle home <IHRDBMS>.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.0. In particular.0.2. Check that the database is now running with Oracle Database 11g Release 2 (11. Procedure 1.2) environment by entering the following commands: 1. 3.2.2 Creating a Symbolic Link for Runtime Oracle Home This procedure is only necessary for the update from 11.1 Oracle home.0.2. 4. 5. Change to the required directory: cd /oracle/<DBSID> Upgrading from source database 11. Procedure Upgrading from source database 11.5 5.

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

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

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

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

8 database.4 Version 5 (V5) or Oracle 11.0.0.2.2.2.11 Updating the Oracle Instant Client You need to ensure that the SAP system runs with at least Instant Client release 10. Procedure 1.11 Post-Upgrade Steps Updating the Oracle Instant Client Procedure 1.5 5. 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.2.0.8 database to Oracle 11.2 database. 5. enter the following command as the ora<dbsid> user: chmod 755 $ORACLE_HOME 5. Procedure Update your SAP kernel to 640_EX2.0. Procedure Update the Oracle Database Instant Client for UNIX as described in SAP Note 1431794. If this is not true.2. 2.XX kernels). We do not support running a 640_REL kernel with an Oracle 11. NOTE This step also applies to SAP systems running the 640_REL kernel with the Oracle 9. Prerequisites You have an SAP System running with 640_REL kernel and you just upgraded your Oracle 9. The Instant Client 10. set the ORACLE_HOME environment variable to point to the location of the Oracle Database 11g software installation. 5.12 Updating the SAP Kernel from 640_REL to 640_EX2 If you are running a 640_REL kernel.2.2 is used immediately after the kernel switch to 640_EX2 or higher (including SAP 7.13 Changing the Environment for the <sapsid>adm user You have to change the environment for the <sapsid>adm user. but only on the database server. Make sure that the <sapsid>adm user has read authorization for the directory $ORACLE_HOME.4 or 11. you must update it to 640_EX2. On the database server.0.0. for example: 2011-12-20 PUBLIC 41/50 .2.2. performing the kernel switch as described in SAP Note 1058988.

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

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

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

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

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

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

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

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

sap. .com © Copyright 2011 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. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Sign up to vote on this title
UsefulNot useful