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

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

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

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

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

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

10 SP10 ■ SAP_BASIS 7. The error is fixed in later support packages.so) patch level 81 or higher. see SAP Note 1456323. For more information. apply the advanced correction from SAP Note 1417124 This correction resolves an Oracle issue that results in an ABAP short dump during statistics updates.2. ■ SAP_BASIS 7.11 SP05 ■ SAP_BASIS 7.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 uses SAP Kernel 711. 12/50 PUBLIC 2011-12-20 .01 SP06 ■ SAP_BASIS 7. If your SAP system is SAP BASIS 7xx.02 SP02 ■ SAP_BASIS 7. 3.00 SP21 ■ SAP_BASIS 7. This error is seen only after the database has been upgraded to Oracle 11.5 Planning Checking the SAP System Prerequisites 2. you need to use DBSL (dboraslib.2 2.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

2) software in an Oracle Database 11g Release 2 (11.0. 2.1 or 11. In particular. For more information on this step.2. Change to the required directory: cd /oracle/<DBSID> If no database is still running from the old 11.2) environment by entering the following commands: 1. 5.3 Checking the Upgraded Database You need to check the upgraded database. Procedure 1. 3. 4. Procedure Upgrading from source database 11.2 Creating a Symbolic Link for Runtime Oracle Home This procedure is only necessary for the update from 11.2.2.2.2. Log on to the database as the ora<sid> user. Check that the database is now running with Oracle Database 11g Release 2 (11.0.0. It links the runtime Oracle home <OHRDBMS> to the installation Oracle home <IHRDBMS>.2.1 Oracle home.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. Create a symbolic link to the new Oracle home: ln -s 11203 /oracle/<DBSID>/112_64 Restart the database. detach this Oracle home from the inventory and rename the old Oracle home: mv 112_64 11201 3.5 5. 1. see SAP Note 1525025.1 1.0. 2. 36/50 PUBLIC 2011-12-20 . 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. Change to the required directory: cd /oracle/<DBSID> Upgrading from source database 11. make sure that ORACLE_HOME is set to the runtime Oracle home: /oracle/<DBSID>/112_64 5.

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

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

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

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

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

■ For the <sapsid>adm user.5 5.csh.WORLD = (ADDRESS = (COMMUNITY = SAP. the startdb or stopdb script fails with the following error message: ORA-00119: invalid specification for system parameter LOCAL_LISTENER Adapting the SQL*Net Files for the <sapsid>adm User 1. 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.cshrc.ora file that is used by the <sapsid>adm user: 42/50 PUBLIC 2011-12-20 . it is recommended to repeat the change described above on all application servers. you need to adapt the SQL*Net files that are located in the directory pointed to by the environment variable TNS_ADMIN. ■ If the environment variable TNS_ADMIN is not set. 3.ora file that is used by the <sapsid>adm user: LISTENER_<DBSSID>. 2.14 Post-Upgrade Steps Updating the SQL*Net Configuration Files for the <sapsid>adm and ora<sid> Users /oracle/<DBSID>/112_64 2. Check whether R3trans can connect to the database: R3trans –d 5. 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. Procedure Adapting the SQL*Net Files for the ora<sid> User ORACLE_HOME>/network/admin if they 1. Add the following entry to the tnsnames. look for a tnsnames. Log out and log on again as the <sapsid>adm user. .dbenv_<hostname>. Determine the SQL*Net files used by <sapsid>adm as follows: ■ If the environment variable TNS_ADMIN is set. Add the following entry to the tnsnames.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. 4. and so on). the SQL*Net files are used from the specified location (even if ORACLE_HOME is set).14 Updating the SQL*Net Configuration Files for the <sapsid>adm and ora<sid> Users You need to update the tnsnames. Without this entry.

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

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

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

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

2) see SAP Note 1431800. This note provides links to other SAP notes that describe how to configure or activate each new feature. 5.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. you need to change it to UTF8.2) features. 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. 2011-12-20 PUBLIC 47/50 . follow SAP Note 669902 to change the national character set to UTF8. the national character set must be UTF8.19 Configuring the New Features for Oracle Database 11g Release 2 (11.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. Procedure If necessary.5 5.

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

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

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