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 fi«£z% Technology Consultants fi«£z% System Administrators fi«£z% Database Administrators fi«£z% Developers

CUSTOMER fi«G_ꟹM/ÝSÁÙ„Ö<Ž¤æU$0A=µÒ5;¸ät@ž²ð%÷ ¨^8~ýœÔZ*€Qı@cë™JUê¸eÄ'2A"Ö,

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.02 3.01 3.00 2.10 2.01 2.00 1.14 1.13 1.12 1.11 1.10 1.01 1.00

2012-10-30 2012-08-08 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

Minor corrections in chapter Updating the Oracle Installation Scripts Various corrections 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/52

CUSTOMER

2012-10-30

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 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

2012-10-30

CUSTOMER

3/52

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/52

CUSTOMER

2012-10-30

1

Introduction

1 Introduction

This documentation describes how to upgrade the Oracle database for the SAP system on the UNIX operating system: u¹£ì™j 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 u¹£ì™j 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.
Implementation Considerations

u¹£ì™j For more information about implementation considerations, including the most important SAP Notes for the upgrade, see Planning [page 9]. u¹£ì™j 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 u¹£ì™j You might find useful information for the upgrade in the following Oracle documentation: u¹£ì™ Oracle 11gR2 Upgrade Companion [ID 785351.1] u¹£ì™ Operating Systems Installation and Configuration Requirements Quick Reference (8.0.5 to 11.2) [ID 169706.1] u¹£ì™j You use the tools Oracle Universal Installer (OUI), MOPatch (Opatch), Oracle SQL*Plus, and Oracle Database Upgrade Assistant (DBUA) to perform the upgrade. u¹£ì™j To make this documentation easier to read, only the location for 64-bit platforms is used. If your database runs on a 32-bit platform (Linux 32–bit), replace as appropriate occurrences of 64 with 32. For example, replace 112_64 with 112_32.
Naming Conventions

We use <DBSID> for the database instance identifier and <SAPSID> for the SAP system identifier. These can be different if your SAP system uses Multiple Components in One Database (MCOD).

2012-10-30

CUSTOMER

5/52

2.1 1. when when you upgrade from 9i or 10g – we recommend that you check the most important new features in the Oracle documentation.0 Required for upgrading Oracle client software to Oracle 11g Release 2 (11.0: Current Patch Set Oracle 11. You can access the complete Oracle documentation at the Oracle Technology Network (OTN) website at www.1 Introduction New Features 1.2.2 SAP Notes for the Upgrade Make sure that you read the following SAP Notes: Number Title Remarks 1431800 1454627 1398634 1431798 Oracle 11.0: Database Parameter Settings Oracle 11.2.2.2.2) Describes the Oracle Instant Client Installation and Configuration 1431796 1431797 1431799 1503709 1631931 1431793 1431794 819829 6/52 CUSTOMER 2012-10-30 .0: Instant Client Oracle Instant Client Installation and Configuration on Unix Provides a starting point for information about Oracle 11g with multiple links to notes on Oracle 11g. see the New Features documentation from Oracle.2.2).0 Upgrade Scripts Oracle 11.0.oracle.0: Patches / Patch collections for 11.2.0.2.2 Lists the status of Oracle patches and bundle patches for 11.2.0: Troubleshooting the Database Upgrade Oracle 11. RECOMMENDATION Especially when you are performing a major release upgrade – that is.2) [page 47] 1.2.0.2.0.2.2.3 Oracle 11.3 Describes the shell and SQL upgrade scripts for 11. Required late-breaking information Provides information about integration of Oracle 11g products and options within SAP Provides information about Oracle initialization parameters that need to be reset to their default values or that need to be removed Describes software installation problems and solutions or workarounds Describes database upgrade problems and solutions or workarounds Describes the current Oracle patch set Lists the status of Oracle patches and bundle patches for 11.2 Oracle 11.1 New Features For the complete list of new features of the Oracle Database 11g Release 2 (11.com/technology.0: Central Technical Note Additional Info / Corrections to Oracle 11g Upgrade Guide Oracle Database 11g: Integration into the SAP environment Oracle 11.2.0: Troubleshooting the Software Installation Oracle 11.0: Patches / Patch collections for 11. More Information Configuring the New Features for Oracle Database 11g Release 2 (11.

3 Introduction More Information on SAP Service Marketplace Title Remarks Number 850306 134592 834917 839182 1027012 1430669 1519872 1524205 1525025 1521371 Oracle Critical Patch Update Program Importing the SAPDBA role (sapdba_role.0: Setting of ORACLE_BASE in SAP Environments Describes the current Oracle security fixes Describes how to update the SAPDBA role after the upgrade Describes the new SAPCONN role.1 1.com Oracle Download Area oracle-download 2012-10-30 CUSTOMER 7/52 .2) software Describes how to set ORACLE_BASE in an SAP environment 1.sap.3 More Information on SAP Service Marketplace You can find more information as following on SAP Service Marketplace: Description Internet Address http://service.sap.sap.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.0: Software Installation Oracle Software Deinstallation Oracle 11.com/notes www.sap. the guide you are now reading Oracle download area for patches and software http://service.2.2.com/swdc http://service.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.com/ instguides Database Upgrades Oracle https://service.com/irj/sdn/ Title SAP Notes Oracle Database Administration None SAP Database Guide: Oracle SAP ON ORACLE KNOWLEDGE CENTER Documentation ora SAP None Upgrade to Oracle Database <Version>: UNIX SAP Software Distribution Center Oracle Database Upgrade Guide – that is.sdn.

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

2012-10-30 CUSTOMER 9/52 . You check additional requirements for the upgrade [page 10]. 2. see the documentation for the Oracle Database 11g Release 2 (11.1 Planning Checking the Original Version of Your Database 2 Planning RECOMMENDATION Before the production upgrade. You check the hardware and software requirements [page 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. you need to first upgrade the source database to at least patch set 10. make sure that you perform a test upgrade on your backup system. 3.2) upgrade at the Oracle Technology Network (OTN) website. Process 1. Prerequisites In the following special cases you need to obtain more information: /jeÃ%« If you are upgrading from Oracle 10.2 to Oracle Database 11g Release 2 (11. 2.0. You check the original version of your database [page 9]. do one of the following from the environment of the source database: /jeÃ%« Enter the following command: sqlplus —version /jeÃ%« Enter the following commands: sqlplus / as sysdba SQL> select version from v$instance.2) in manual mode (in this guide we only describe the database upgrade using the DBUA) /jeÃ%« If the source database runs Oracle 10. 4. 1.5. 5. if necessary.2. You review the Oracle-specified kernel parameters and shell limits [page 10].2. You check the SAP System prerequisites [page 12].2 2. 2.0. obtain more information.2. For more information in the special cases mentioned above.

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

5B) or EX2 kernel (for release 4.com/swdc 8.2 database. the SAP kernel needs to be EXT kernel (for releases 3.0. 2012-10-30 CUSTOMER 11/52 . You need this document to review the hardware and software requirements and to configure the kernel parameters and shell limits. as described in SAP Note 432861. If you have access to My Oracle Support. see SAP Note 1398634.4 Planning Checking Additional Requirements for the Upgrade 3. BR*Tools supports the Oracle Database 11g Release 2 (11.com/oracle-download CAUTION 6.2).com/oracle-download Download the latest version of the DBATOOLS (BR*Tools) to be used immediately after the database upgrade from: http://service. download the 640_EX2 kernel from SAP Service Marketplace.or Release 7.sap. For more information. RECOMMENDATION 4. If you have a 640_REL kernel.sap. This document provides information on all operating system prerequisites and is regularly updated. see SAP Note 1430669.sap.1. We do not support running a 640_REL kernel with the Oracle 11. Make sure that you download the complete 640_EX2 kernel: both SAPEXE. To upgrade from a remote PC. In some situations the OUI and DBUA screens are not displayed correctly when started remotely. In such cases we recommend you to start the OUI and the DBUA directly from the console. we strongly recommend that you read document 169706. You can download the patches from: http://service. Download the latest version of the Oracle 11.20 (patch level 1) . The SAP Note with the list of patches is referenced in SAP Note 1431800.2.8 and your SAP kernel is 640_REL kernel. you need to switch to the 640_EX2 kernel immediately after the database upgrade to Oracle 11.6C).2) software and the latest patch sets and required patches or patch collection.10 (patch level 30).SAR. RECOMMENDATION 5. more information. make sure that you install all these patches.2 Instant Client software from: http://service. The patches listed in the SAP Note referenced in SAP Note 1431800 are mandatory. For upgrade certification. Download the Oracle Database 11g Release 2 (11. Download the Oracle Database 11g Release 2 (11.SAR and SAPEXEDB.2) installation guide for your operating system from the Oracle Technology Network (OTN).1 up to and including 4. 7. If your source database is Oracle 9.2.2 2. you need X-Windows software on the PC. as of release 7. To avoid severe database problems.

For more information.11 SP05 úÜ~Ö#˚ SAP_BASIS 7.02 SP02 úÜ~Ö#˚ SAP_BASIS 7. 1414733.5 Checking the SAP System Prerequisites Procedure 1. and 1433301 if you are running any of the following support packages: úÜ~Ö#˚ SAP_BASIS 7. see SAP Note 1456323. 2. apply SAP Notes 1416108.10 SP10 úÜ~Ö#˚ SAP_BASIS 7.5 Planning Checking the SAP System Prerequisites 2. 3.01 SP06 úÜ~Ö#˚ SAP_BASIS 7.2 2. you need to use DBSL (dboraslib.XX when you are performing a major release upgrade. If your SAP system is SAP BASIS 7xx.20 SP02 This resolves an error in an ABAP program that causes it to report problems during the consistency checks within transaction SE14. The error is fixed in later support packages. For SAP systems 7. If your SAP system uses SAP Kernel 711. 12/52 CUSTOMER 2012-10-30 .00 SP21 úÜ~Ö#˚ SAP_BASIS 7.so) patch level 81 or higher. This error is seen only after the database has been upgraded to Oracle 11. 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.

since you perform the database installation as user ora<dbsid>.0.7O6óï Oracle inventory directory . If your source database is Oracle 9. 2. You update the Oracle installation scripts [page 15].4. you run the pre-upgrade scripts (Oracle 9. groups.1 Checking the Correct UNIX Users.7O6óï stage directory . You check the correct UNIX users. and Authorizations You need to check that the ora<dbsid> user has write authorization for the $ORACLE_BASE directory.8) [page 24]. 4. and Authorizations 3 Preparation You have to complete the following preparations: 1. Groups. 3.2 Checking the Directory Structure You need to verify the availability and correctness of the following Oracle directories: . You check the directory structure [page 13]. see SAP Note 1521371. 3.0. You install the database software [page 17].7O6óï Home directory 2012-10-30 CUSTOMER 13/52 .0. 7.3 3. 5. If your source database is Oracle 10. you run the pre-upgrade scripts [page 22].2.2. For information about $ORACLE_BASE. and authorizations [page 13]. 6. 3. 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. Groups.2.1 Preparation Checking the Correct UNIX Users.8. 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].

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

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

call the script rootpre. 4. Checking operating system requirements (release./runInstaller –executeSysPrereqs 2.zip 3. call the script rootpre.0.old Extract the zip file: $ unzip 11ginstall-<release>-<patch-level>-complete.4 Checking the Software Installation Prerequisites You must check the prerequisites for the Oracle Universal Installer (OUI).3 3.3: cd /oracle/stage/11203/database As the user root. WÙx¢m=‰«óÀåä¹lÂù˙6Ï»JÿY®qT¾3V0ʤªSÒ-L5 On AIX.sh WÙx¨m=…ł«¼Ð忹 ÂÑ˙˙ÏÃJ9Y Procedure 1. Prerequisites Make sure that the DISPLAY environment variable is set correctly. 2.zip. Checking prerequisites for the OUI: . Change directory: cd /oracle/stage/11202/database Execute the following commands: 1. 3.2: cd /oracle/stage/11202/database WÙxM*£ 11. 2. Copy the file to the database directory in the Oracle software stage directory: $ cp 11ginstall-<release>-<patch-level>-complete. 3. patches.2. which is attached to SAP Note 1524205. The zip file contains the current version of the installation scripts.sh: . 2. Log on as the Oracle user ora<dbsid>.0. 5./rootpre.4 Preparation Checking the Software Installation Prerequisites Procedure Updating the Installation Scripts 1. kernel parameters): 16/52 CUSTOMER 2012-10-30 .zip /oracle/stage/112_64/database Go to this directory: $ cd /oracle/stage/112_64/database Rename the existing SAP directory as follows so that you have a saved copy of the previous version: mv SAP SAP.2. Change to the relevant directory as follows: WÙxM*£ 11. Download the file 11ginstall_<release>_<patch_level>_complete.sh: WÙx¨m=…ł«¼Ð忹 ÂÑ˙˙ÏÃJ9Y WÙx¢m=‰«óÀåä¹lÂù˙6Ï»JÿY®qT¾3V0ʤªSÒ-L5 1.

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

0 is the host on which the Oracle Universal ORACLE_BASE Installer (OUI) is to be displayed. 2.0.0. see SAP Note 102402.ôá©ø.flåFŁá®‹a¥°Rž§6ѳ9gZðõ5îu»Ð®.0.2 (10.0 NOTE <hostname>:0.<h˙‚ LD_LIBRARY_PATH VÕ«Lª¥¬QWC˶ëIQü¼ñæ_¯¦ÉÆ RXÇxÖY? .4 or 10.§fi“-Y9ºÂr⁄W+Þ¶.X (where X = 1. we strongly recommend moving it to WE8DEC or UTF8 before the upgrade.flåFŁá®‹a¥°Rž§6ѳ9gZðõ5îu»Ð®.0.2. Make sure the following environment variables are not set: VÕ«©‘k TWO_TASK VÕ«©‘k ORA_NLS VÕ«©‘k ORA_NLS32 VÕ«©‘k ORA_NLS33 VÕ«©‘k ORA_NLS10 Make sure that the following environment variables are set as described: Environment Variable DISPLAY 2. see SAP Note 1521371.2.<h˙‚ $ORACLE_HOME/lib:$LIBPATH VÕ«Lª¥¬QWC˶ëIQü¼ñï_¶¦±ÆùRV VÕ«Fª¥¬YWˆËùëY üðñÇ_ł¦ÉÆ?REÇÖU+ Dfl‰F‹á—‹/¥ÊRçxÑfi9QZ‡õ>î!»ð®$ôý©ä. EXAMPLE VÕ«©‘k When upgrading from 10. You make them permanent in the database structure upgrade.5 Preparation Database Software Installation CAUTION Do not make the changes to the environment permanent while the old database is still running.Y (where Y > X): /oracle/<DBSID>/112_64 NLS_LANG One of the following values: AMERICAN_AMERICA.2.¬fi-v 18/52 CUSTOMER 2012-10-30 .3 3. SAPDATA_HOME VÕ«Fª¥¬YWˆËùëY üðñÇ_ł¦ÉÆ?REÇÖU+ MflˆóF|á− /oracle/<DBSID> VÕ«Fª¥¬YWˆËùëY üðñÇ_ł¦ÉÆ?REÇÖU+ MflˆóF|á− LIBPATH VÕ«Lª¥¬QWC˶ëIQü¼ñï_¶¦±ÆùRV VÕ«Fª¥¬YWˆËùëY üðñÇ_ł¦ÉÆ?REÇÖU+ Dfl‰F‹á—‹/¥ÊRçxÑfi9QZ‡õ>î!»ð®$ôý©ä. <DBSID> ORACLE_SID ORACLE_HOME Make sure that it is set to the value of the current runtime Oracle home.UTF8 If your database still runs with the character set US7ASCII. Value <hostname>:0.WE8DEC AMERICAN_AMERICA.ôá©ø. We recommend you to back up the old environment files before making the changes permanent.§fi“-Y9ºÂr⁄W+Þ¶.0. or 3) to 11. Procedure 1. /oracle or /oracle/<DBSID> For more information.2.2.X: /oracle/<DBSID>/102_64 VÕ«©‘k When upgrading from 11.5) to 11.¬fi-v $ORACLE_HOME/lib:$LD_LIBRARY_PATH VÕ«Lª¥¬QWC˶ëIQü¼ñæ_¯¦ÉÆ RXÇxÖY? . For more information about WE8DEC.

Linux: /etc/oraInst. see http://docs.loc The location is shown as follows: inventory_loc=<path to Oracle inventory> 2.cµºý»m·°xÐ ˛SÙ $ORACLE_HOME/lib:$SHLIB_PATH ð"j0·ÔÕp±&0Olªø.2 -> 11.oracle.htm. Or you can run the UNIX umask command and check that the returned value is 22. Procedure 1. If the Oracle inventory exists. PATH can only include one $ORACLE_HOME/ bin. Solaris: /var/opt/oracle/oraInst. To make sure that the OUI screen can be displayed correctly on your system. When you perform a patch set upgrade from 11. For more information about which platform uses which location. This means that you have to adapt PATH when ORACLE_HOME is changed.5 Preparation Database Software Installation Environment Variable ð"j:·ÔÝpè&O½lñø`cflºÉ»`·…xç ÏSŠø}ófl?ÓU9ntX2È Value ð"j:·ÔÝpè&O½lñø`cflºÉ»`·…xç ÏSŠø}ófl?ÓU9ntX2È SHLIB_PATH ð"j0·ÔÕp±&0Olªø. 3.2. RECOMMENDATION You can check the correctness of the new environment with the UNIX env command.com/ cd/E11882_01/em. When you perform a major upgrade from 10. 2012-10-30 CUSTOMER 19/52 . Make a backup of your existing Oracle inventory before you start the Oracle Database 11g Release 2 (11.loc ð"jÕ4y AIX. you might have to start an X terminal (xterm) session and run the command: $ xhost + 3. If not. set up the TEMP or TMPDIR environment variables to specify a temporary directory on the filesystem.5.112/e12255/oui2_manage_oracle_homes.2 Backing Up the Central Oracle Inventory Before you install the new Oracle database patch set software. Check if the temporary directory (usually /tmp) has at least 1024 MB of free space. The setting of the DISPLAY environment variable is described in SAP Note 432861.cµºý»m·°xÐ ˛SÙ PATH PATH includes $ORACLE_HOME/bin of the current active ORACLE_HOME.3 3. you need to modify PATH after the upgrade. you need to back up the central Oracle inventory.2 to 11.2) software installation. the run-time Oracle home path does not change and therefore no change in PATH is required. check its location by looking at the entry in one of the following files: ð"jÕ4y HP-UX.2.

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. For more information about how to install Oracle database 11. Log on as user ora<dbsid> or oracle (Oracle software owner)./RUNINSTALLER 4. Make sure that the DISPLAY environment variable is set to <host_name>:0. see SAP note 1524205. For more information about the current patch set.2). 20/52 CUSTOMER 2012-10-30 .2./RUNINSTALLER IJZû¾é 11.2.5.0.0 3. Confirm the default option English and then choose Next. Confirm the default selection Single Instance Installation and then choose Next. Start the OUI with the user ora<dbsid> as follows: IJZû¾é 11. make sure that you have updated the installation scripts as described in Updating the Oracle Installation Scripts [page 15]. where <host_name> is the host on which you want to display the GUI of the Oracle Universal Installer (OUI).3 3. Choose OK and then Next.2 software. Shell Used Command DISPLAY=<host_name>:0.3 Installing the Oracle Database Software Starting with the first patch set for Oracle Database 11g Release 2 (11. 2. The runInstaller issues a warning. Confirm the default selections by choosing Next.3: cd /oracle/stage/11203/database/SAP .0 export DISPLAY Bourne shell (sh) C shell (csh) Korn shell (ksh) setenv DISPLAY <host_name>:0. You only need to install the current Oracle database patch set. Since you are already logged on as user root.0.5 Preparation Database Software Installation 3.0.0.2: cd /oracle/stage/11202/database/SAP . see SAP note 1431799. you can switch to user ora<dbsid> by entering the following command: su – ora<dbsid>. CAUTION Before starting to install the Oracle software. Oracle Database patch sets are full installations of the Oracle database software. Procedure 1.2.0 export DISPLAY=<host_name>:0.

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

ora file at this point. Since your database is still running in the old environment. do not start the listener with the new listener. which automatically perform various tasks and checks on your database. If not available. add the following entry to the file listener. Log on as user ora<dbsid>. Set ORACLE_HOME to the new installation Oracle Home <IHRDBMS>.6 Running the Pre-Upgrade Scripts You run the Oracle pre-upgrade scripts. the SQL*Net files are automatically copied from the source Oracle Home to the target Oracle Home. Procedure 1. Prerequisites Check SAP Note 1431800 to find a cross-reference to the current SAP Note with the list of required patches to be installed. see SAP Note 1431793. 3. See SAP Note 1431793. Install the SAP bundle patch according to the instructions in the SAP bundle patch README file. 2.ora. 22/52 CUSTOMER 2012-10-30 .ora: ADR_BASE_<listener_name> = /oracle/DBSID/saptrace Note that this is the same value as set in the database profile parameter diagnostic_dest.sh wrapper to perform the database upgrade with DBUA. Be sure to adapt the value of ORACLE_HOME in the listener. Log on at the operating system level as the ora<dbsid> user. 3. Copy the SQL*Net parameter files from <old_ORACLE_HOME>/network/admin to <new_ORACLE_HOME>/network/admin.5. 4.ora. 3. sqlnet. listener.6 Preparation Running the Pre-Upgrade Scripts The SAP bundle patch also delivers a set of upgrade scripts that automate most of the pre-upgrade and post-upgrade tasks. and tnsnames. Edit the new SQL*Net files by adapting all file paths for the new directory.sap.5 Copying and Adapting the SQL*Net Files After the database software installation. that is. Procedure 1.ora file. you must copy and modify the old SQL*Net files. 2.ora. For more information.3 3. EXAMPLE setenv ORACLE_HOME /oracle/<DBSID>/11203 3. NOTE If you use the dbua.

8) [page 24]. 2012-10-30 CUSTOMER 23/52 .2.6 Preparation Running the Pre-Upgrade Scripts This section only applies if your source database is Oracle 10. Execute the following commands to check the pre-upgrade status of your database: sqlplus / as sysdba SQL> @pre_upgrade_status.2. or 11.0.3: /oracle/<DBSID>/11203/sap/ora_upgrade Procedure 1.0.2.sql Result You can check the results of the pre-upgrade scripts by looking at the following log files: S=Ç÷ pre_upgrade_status.2. see Running the Pre-Upgrade Scripts (9. Change to the correct directory by entering the relevant command (since the scripts have been extracted to the Oracle 11. The directory where the upgrade scripts are installed is called ora_upgrade.2 software home): S=Ç÷ 11.2: /oracle/<DBSID>/11202/sap/ora_upgrade S=Ç÷ 11.0. 11.0. the scripts are installed as part of the SAP bundle patch in the relevant Oracle 11.2 environment with the database also started up.sql SQL> spool off 3.8.2.2: cd /oracle/<DBSID>/11202/sap/ora_upgrade/pre_upgrade S=Ç÷ 11.3: cd /oracle/<DBSID>/11203/sap/ora_upgrade/pre_upgrade Execute the following commands to perform pre-upgrade tasks.log S=Ç÷ pre_upgrade_tasks. Prerequisites You are logged on as user ora<dbsid> in the Oracle 10.5.2. which can improve the performance of the upgrade process: sqlplus / as sysdba SQL> spool pre_upgrade_tasks.2.2.2 software home directory: S=Ç÷ 11. 10.0.1.4.0.log SQL> @pre_upgrade_tasks. The scripts do the following on your pre-upgrade database: S=Ç÷ Provide information on the database S=Ç÷ Suggest any changes that you need to make to the database before you start the upgrade S=Ç÷ 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.log You can run the pre-upgrade scripts as often as necessary. By default. 2.3 3.0.0.2. If your source database is Oracle 9.0.0.2.2.

otherwise you might have problems during the upgrade.7 Running the Pre-Upgrade Scripts (Oracle 9.2 environment.2 software home directory: /oracle/<DBSID>/112_64/sap/ora_upgrade Procedure 1.2.2 software home): cd /oracle/<DBSID>/112_64/sap/ora_upgrade/pre_upgrade 2. 3.8. You can run the pre-upgrade script as often as you like on the pre-upgrade Oracle 9. which is reported as DEPRECATED.log SQL> @utlu112i. Make sure that you check any warnings and perform the suggested corrective actions mentioned in the log file.0.0.sql Result You can check the results of the pre-upgrade script by looking at the following log file utlu112i.3 3.2. If your source database is Oracle 10.8) CAUTION Make the changes listed in the log file.2.2.0. see Running the Pre-Upgrade Scripts [page 22].2. 24/52 CUSTOMER 2012-10-30 . This section only applies if your source database is Oracle 9. By default. ùQ°º² The directory where the upgrade scripts are installed is called ora_upgrade.5.4 or 10. However. 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. NOTE You always execute these scripts as the ora<dbsid> user connected to the database as sysdba in the Oracle 9. Prerequisites ùQ°º² You are logged on as user ora<dbsid> in the Oracle 9. which automatically perform checks on your database.0.0. you must ignore the warning regarding the possible setting of the database parameter remote_os_authent.7 Preparation Running the Pre-Upgrade Scripts (Oracle 9.8) You run the Oracle pre-upgrade scripts.2 database.log.2 environment with the database also started up. the scripts are installed as part of the SAP bundle patch in the relevant Oracle 11.

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

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

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

8) [page 30]. EXAMPLE W¢C¡Ÿ Enter these commands to upgrade from 10.0.2. Prerequisites W¢C¡Ÿ dbua.sh sets the environment internally. Start the DBUA.0.sap.0.3 or from 11.sh is a wrapper script to automate most of the post-upgrade tasks. see Starting the Database Upgrade Assistant (Oracle 9.2.0.3. W¢C¡Ÿ Ensure that you have write permissions on /etc/oratab.2.3 Database Structure Upgrade As part of the Oracle database upgrade [page 27].2.0. The DBUA tool is a graphical tool that leads you step by step through the upgrade.2.0. depending on your source database: W¢C¡Ÿ If your source database is not Oracle 9.8.8.0.sap.1 Starting the Database Upgrade Assistant To upgrade the database structure. 4. Change to the correct directory: 28/52 CUSTOMER 2012-10-30 . If your source database is Oracle 9. Procedure 1.2. 1.x to 11.8) [page 30]. you start the Database Upgrade Assistant to perform the upgrade [page 28].0. Prerequisites You have installed the database software [page 17].2 to 11. Set ORACLE_HOME_SRC and ORACLE_HOME_TGT. W¢C¡Ÿ If your source database is Oracle 9. you start the Database Upgrade Assistant to perform the upgrade (Oracle 9.3: setenv ORACLE_HOME_SRC /oracle/<DBSID>/112_64 setenv ORACLE_HOME_TGT /oracle/<DBSID>/11203 2.0. dbua. W¢C¡Ÿ Before you start the DBUA make sure that the DISPLAY environment variable is correctly set.3 Oracle Database Upgrade Database Structure Upgrade 4.2.3: setenv ORACLE_HOME_SRC /oracle/<DBSID>/102_64 setenv ORACLE_HOME_TGT /oracle/<DBSID>/11203 W¢C¡Ÿ Enter these commands to upgrade from 11.0.2. you upgrade the database structure.8. Result Now continue with the Post-Upgrade Steps [page 35]. Process Flow Perform one of the following.4 4.1 to 11.2.2.0.2. you need to start the Oracle Database Upgrade Assistant (DBUA).

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

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

Respond appropriately to the DBUA dialogs: The Welcome screen provides information about the upgrade assistant 1. Prerequisites Æ^[éˆK You check the oratab entry [page 33]. If your source database is Oracle 10. you need to analyze and act on these warnings.4 4. 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: Explanation: Upgrade of TSTZ data is done automatically using one of the postupgrade custom scripts. No action is necessary.sql.2.sql. The Databases screen lets you select the database to be upgraded. and issues warnings if necessary. use SQL*Plus to execute the script $ORACLE_HOME/rdbms/admin/utlrp.4.8.sql.0. Choose Next to continue. 2012-10-30 CUSTOMER 31/52 . Æ^[éˆK Ensure that you have write permissions on /etc/oratab.0./oracle/<DBSID>/112_64/sap/ora_upgrade/ post_upgrade/sapuprof_profile 3.sql. Procedure 1. see Starting the Database Upgrade Assistant [page 28]./oracle/<DBSID>/112_64/sap/ora_upgrade/ post_upgrade/set_compatible. Æ^[éˆK Before you start the DBUA make sure that the DISPLAY environment variable is correctly set. 2. Go to <target Oracle home>/bin. performs pre-upgrade checks.2.3 Oracle Database Upgrade Database Structure Upgrade This section only applies if your source database is Oracle 9. The DBUA now analyzes the database to be upgraded./oracle/<DBSID>/112_64/sap/ora_upgrade/ post_upgrade/set_remote_os_authent./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. Select the correct database and choose Next. Start the DBUA as follows: . RECOMMENDATION If the DBUA warns you of issues that need to be fixed before the upgrade. 2. 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.

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

For a complete list of obsolete and deprecated parameters. you can set up the database so that it can be managed with the Enterprise Manager. if required. Check AUTOEXTEND ON.3 Oracle Database Upgrade Database Structure Upgrade 4. the results of the upgrade are displayed Review the changes made and exit the DBUA.0.3. removed. 4. Make sure that Configure the database with Enterprise Manager is not selected and choose Next. components to be upgraded. Before you start it. 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. Prerequisites You can find the oratab file as follows: 2012-10-30 CUSTOMER 33/52 . you need to check the entry for the oratab file. you can skip this step. 7. You do not always need to perform this step: {CñÉ‚k For manual upgrades. This section only applies if your source database is Oracle 9. When the DBUA has completed successfully.2. and changed after the upgrade.8.8) To upgrade the database structure. This includes the warnings that you ignored or did not fix. {CñÉ‚k For upgrades with the dbua.2). Increment Size 100 MB Maximum Size: Unlimited Choose Next to continue. The upgrade process itself runs for some time. 6.2. The oratab file contains information about existing databases and the corresponding Oracle Homes on the database server.3 Checking the oratab Entry (Oracle 9. NOTE 5. depending mainly on the size of the database and the capacity of the hardware. Review the summary of changes and choose Back to make any final adjustments.sh wrapper script. On the screen Management Options. 8. {CñÉ‚k You only have to perform this step if DBUA needs to find the database and Oracle Home to be upgraded from the oratab file.2). DBUA will update the oratab with the new Oracle Home after or during the upgrade (dbua must have write permission). parameters to be added.sap. the DBUA displays a summary of the changes to be made. you can also skip this step.4 4.0. see the documentation for Oracle Database 11g Release 2 (11.

4 4.3 Oracle Database Upgrade Database Structure Upgrade û_*–ŽGL„é.

X‹4óŒlMŸÞÍ»×ÏáÉKŠ©±|ÿÆ0⁄\ıý87Ь½¤“³ÉÁÖ<@oæÖ¾ý˜{ÌÀ¶˛qí û_*j¼› û_*j¼› /etc û_*‘ŽGL—é\.

7‡¬ł¤¨³œÁ#<d û_*–ŽGL„é.‹$óÍlŸ)Þ໯ϼÉlŠ‰±kÿ³0ž\èý.

X‹4óŒlMŸÞÍ»×ÏáÉKŠ©±|ÿÆ0Ł\¼ý.

7−¬⁄¤´³ŠÁ#<d /var/opt/oracle û_*‘ŽGL—é\.

0.ÞÆ»łÏæÉVŠ²±5ÿF0º Procedure 1. û_*j¼› Oracle 9.2 source database C11:/oracle/C11/920_64:N 2.2 source database C11:/oracle/C11/102_64:N. If this entry does not exist. 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. insert it using a text editor.2.2.1 source database: C11:/oracle/C11/112_64:N û_*j¼› Oracle 10.0. EXAMPLE The entry for a system with a <DBSID> equal to C11 is as follows: û_*j¼› Oracle 11.2 source database: C11:/oracle/C11/11202:N û_*j¼› Oracle 11.‹$óÍlŸ. 34/52 CUSTOMER 2012-10-30 .

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

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

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

Check database compatibility by executing the following command: SQL> show parameter compatible If not set to 11.0. CAUTION 3.0. 3.8. Make sure that you execute this command for every SAPSCHEMA_ID in your database.5 Performing Post-Upgrade Tasks You need to perform certain post-upgrade tasks. perform the following tasks before gathering the Oracle optimizer statistics using brconnect: 1.sql 5.2. 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. you have to enter both commands.sql as follows: cd $ORACLE_HOME/sap/ora_upgrade/post_upgrade sqlplus / as sysdba @sapuprof_profile. Implement SAP delivered statistics from SAP Note 1020260.sql from SAP note 403704.2.sql or dbcheckora11_oltp. 2. 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/52 CUSTOMER 2012-10-30 .5 5. Apply script dbcheckora11_olap.sql $ORACLE_HOME/dbs cd $ORACLE_HOME/dbs sqlplus /nolog @sapconn_role 4. execute the SQL script sapuprof_profile.sql as follows: cp /usr/sap/<SAPSID>/SYS/exe/run/sapconn_role. Procedure 1.sql from the same note 3. If your source database is Oracle 9.5 Post-Upgrade Steps Performing Post-Upgrade Tasks x¤Þ€ º —§ÞÍ–ÔJœ’¹Gªš„6‡˜ÍËU‰ûÞ…†×Ç´)Tõî©©? sqlplus /nolog @sapdba_role <SAPSCHEMA_ID> x¤Þª º—þÞ‡–ÄJÇܹoª»„W‡)ÍU– x¤Þ€ º —§ÞÍ–ÔJœ’¹Gªš„6‡˜ÍËU‰ûÞ…†×ÌŠ)cõß©©? sqlplus /nolog @sapdba_role <SAPSCHEMA_ID>DB x¤Þª º—þÞ‡–ÄJÇܹdªŸ„`‡˘ÍU– NOTE If you have an ABAP+Java system. Execute the SQL script sapconn_role. If not executed by dbua as part of the post-upgrade scripts. Apply script dbstatc11.

com/irj/sdn/ora SAP ON ORACLE KNOWLEDGE CENTER SAP Documentation Run post_ugprade_status.ôHqŠ/yŠœ£U ln –s libnnz11. From this directory start sqlplus.sl s0ÇýCÌçŠï|DáGÞþxz¡”Îfiùµ©fBlËrn For more information.3O¼ .sl libnnz10. 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 clients.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. Procedure 1. see the documentation SAP Database Guide: Oracle at: www.2. Open a command prompt and change to the directory <new_oracle_home>/sap/ora_upgrade/ post_ugprade. For more information about update statistics. 5. NOTE This step is included as part of the software installation as of patch set 11.sql. create a symbolic link in $ORACLE_HOME/lib as follows: cd $ORACLE_HOME/lib s0Ç÷CÌŠçÎï3DñG–þ4z•”úfiôµıfulˇr(¶ˇ*ÇÊh8±Çiê¡!|V9{=Çàâ. 5.7 Backing Up the Database You need to back up your upgraded Oracle Database 11g database.so libnnz10.sdn.2 client) can use the newer Oracle 11. After the software installation has finished.3. 5.0.sql This provides an overview of the status of the upgraded database.so s0ÇýCÌçŠï|DáGÞþxz¨”×fi„µÇfVlr|ãˇǸc8åÇIê©=|J9p=\àÍ s0Ç÷CÌŠçÎï3DñG–þ4z•”úfiôµıfulˇr(¶ˇ#ÇÓ˛8ßÇ}êh3 ln –s libnnz11.5 5. see SAP Note 1449619.exe and enter the following commands: SQL>connect / as sysdba SQL>@post_upgrade_status.sap. Check the Oracle database parameters against SAP Note 1431798 and adjust them if necessary. 2012-10-30 CUSTOMER 39/52 . Update the Oracle database statistics with BRCONNECT as follows: brconnect -c -u / -f stats -t all –f collect -p 4 NOTE 6.

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

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

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

These variables point to the ORACLE_HOME used by the application server. 2.WORLD = (ADDRESS = (COMMUNITY = SAP. 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. ‡h·=¯~}¡ùd˙‰ƒý⁄ÂVbã(×QŁo_8Y~7°+|ôÙ¼m:x. it is recommended to repeat the change described above on all application servers.15 Post-Upgrade Steps Checking SAP Profile Parameters LISTENER_<DBSSID>.=†!n‘—º°Gƒ0T¨mµ¬˝²ï3ñ¥’E˘Íj.15 Checking SAP Profile Parameters You have to check the following SAP profile parameters: ‡h·Ò−° ‡h·Ò−° ‡h·Ò−° DIR_ORAHOME DIR_CLIENT_ORAHOME DIR_SERVER_ORAHOME Procedure 1. Without this entry. 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.WORLD)(PROTOCOL = TCP)(HOST = <hostname>)(PORT = <listener_port>)) NOTE Although this entry is only needed on the database server or on central systems where the startdb or stopdb scripts are used.5 5. the startdb or stopdb script fails with the following error message: ORA-00119: invalid specification for system parameter LOCAL_LISTENER 5.

NOTE ‡h·Ò−° You only need to perform this procedure if your source database was Oracle 9. you might have to change the location of the JDBC driver after you have upgraded the database server or client software. the Oracle client major version as used in the procedure below is Oracle 10. 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. 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. ‡h·Ò−° At the publication time of this guide.2.Òí–YÀ“ܯghÔÈq 5. You change the location of the JDBC driver as follows: 2012-10-30 CUSTOMER 43/52 .

–G8·d”&−£öîU·B³ŽÞ ó(•3ú¼Łw–8§?Â&©£óî°B|ŽÐËÅ´â(ϺNùQ 8›Á§ºGÎaŸ4#È<|Ä'gðÓ7flıÉ|. Make sure that you nonetheless replace the old driver location in all locations belonging to your SAP system.IDXXXXXXX/ IDXXXXXXX. Procedure 1. start the J2EE Engine .5 5. Use the Edit mode to replace the driver location in the following property sheets that contain the string rdbms.ConfigTool by double-clicking the configtool.jar In the same directory as in the first step.driverLocation= followed by the driver location: ó(oÌ cluster_data/Propertysheet instance.sh file.jar ó(oÌ ojdbc14. which is one of the following: ó(oÌ classes12. 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 a text editor to change the JDBC driver location. where XXXXXXX is the instance number 44/52 CUSTOMER 2012-10-30 .driverLocation. 3.jar.B»¬ùÁ)Ÿ— /usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee/configtool ó(−3ú´Ł. ó(•3ú¼Łw–8§?Â&©£óî°B|ŽÐËÅ´â#ÏŽNÎQ. CAUTION Do not change the file <java_class_archive>.JavaParameters 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.properties. 2.properties as follows: 1. Change to Configuration Editor mode.–G8·d”&†£ÕîbƒB8Žè’ÅââÏÃNòQ.properties: ó(oÌ ó(oÌ 2.jar ó(oÌ ojdbc6. you use the J2EE Engine Config Tool to change the JDBC driver location.jar ó(oÌ ojdbc5.16 Post-Upgrade Steps Changing the Location of the JDBC Driver ó(oÌ In files that are located in the database.8Á‚ /usr/sap/<SAPSID>/JC<instance_number>/j2ee/configtool ó(−3ú´Ł. Replace the old driver location with the new one: /oracle/client/<Oracle_client_major_version>x_64/instantclient/ <java_class_archive>. ó(oÌ In files that are not located in the database. 1. CAUTION Depending on your SAP version.8ÔÁ„ºÎ8aš4|È[|ì'ð7È Open the file with your text editor and search for the property rdbms.

There might be several IDXXXXXX.yYÕø‡. Replace the old driver location with the new one: /oracle/client/<Oracle_client_major_version>x_64/instantclient/ <java_class_archive>.properties: Ck Ck 2.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 bootstrap. 3. 3.ConfigTool. Close the J2EE Engine .|éûÜ×ã /usr/sap/<SAPSID>/JC<instance_number>/j2ee/cluster/bootstrap Cô‹¥óÂÜÙ’dw"¥'ü—‰Õ~jS†{c Cþ‹¥óÊÜ•’Mtwy¥kß—”Õ(jT†´c–ñN. Change the file bootstrap.yRÕÛ‡. Change to the correct directory containing the instance profile <SAPSID>_JC<instance_number>_<host>: /usr/sap/<SAPSID>/SYS/profile 2.5 5. 3. Open the file with your text editor and search for the property j2ee/dbdriver. Change the driver location in the instance profile as follows: 1. If you have more than one server or dispatcher you must modify all relevant property sheets.jar 4. Ck Ck cluster_data/dispatcher/IDXXXX/kernel/propertysheet ConfigurationManager cluster_data/server/IDXXXX/kernel/propertysheet ConfigurationManager where XXXX is the instance number NOTE 3.properties as follows: 1. Cþ‹¥óÊÜ•’Mtwy¥kß—”Õ(jT†´c–ñN.JavaParameters properties in the property sheet.

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.|ØûW×ÕéØ-u@y˝oˇ'’‰JÝÛfýu⁄Ç]á°µaï?@á™´ /usr/sap/<instance_ID>/DVEBMGS<instance_number>/j2ee/cluster/bootstrap Cô‹¥óÂÜÙ’dw"¥'÷—¨ÕIjb†ðc=–ªNmyrÕ¢‡|éû ×þé>؈uEyCo~’fiJ˝Û: Open the file with your text editor and search for the property rdbms. Change to the correct directory containing the file sdmrepository. Cþ‹¥óÊÜ•’Mtwy¥kß—”Õ(jT†´c–ñN.yRÕÛ‡.jar 5.|éûÜ×ã /usr/sap/<SAPSID>/JC<instance_number>/SDM/program/config Cô‹¥óÂÜÙ’dw"¥'ü—‰Õ~jS†{c Cþ‹¥óÊÜ•’Mtwy¥kß—”Õ(jT†´c–ñN.driverLocation.sdc: Ck Ck 2.sdc as follows: 1.yYÕø‡.

|ØûW×ÕéØ-u@y˝oˇ'’‰JÝÛfýu⁄Ç]á°µaï?@á™´ /usr/sap/<SAPSID>/DVEBMGS<instance_number>/SDM/program/config Cô‹¥óÂÜÙ’dw"¥'÷—¨ÕIjb†ðc=–ªNmyrÕ¢‡|éû ×þé>؈uEyCo~’fiJ˝Û: Search for the following text: 2012-10-30 CUSTOMER 45/52 .

uš° ¨1−×h¨%wýb»⁄µÈK˜×$Ðæ¯C]în. Change the file templateconfigurator.ÉT #F’— 2Ö»H âûGKbÙš@ Òu‡U Open the file with your text editor and search for the property RDBMS_DRIVER_LOCATION.properties: uš_(f uš_(f 2. Procedure 1.jar 6. If R3trans connects without problems. 3.properties as follows: 1.ýA»‡µžL˜˘$Þ uš° ¨1−×h¨%wýb»⁄µÈK˜×$Ðæ¯C]îe.ýA»‡µžL˜˘$Þ uš° ¨1−×h¨%wýb»⁄µÈK˜×$Ðæ¯C]îe.ýJ»¡µ©}˜fi$èæôC îE. replace the old driver location with the new one: /oracle/client/<Oracle_client_major_version>x_64/instantclient/ <java_class_archive>.17 Post-Upgrade Steps Starting the SAP System <Param type="String" hide="false" name="jarPaths" encrypted="false" displayName="Driver Paths (separated by .17 Starting the SAP System You need to restart the SAP system.)"> 3.properties: uš_(f uš_(f 2.5 5. 3. If required.vÉ_ FÍ— 2Š» çû˘KÙµ@Ò´‡ øÔÑ©ZBâåh÷áufiX° /usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee/deploying ušº ¨9−”îݡxÂó%.ýJ»¡µ©}˜fi$èæôC îE. Replace the old driver location with the new one: /oracle/client/<Oracle_client_major_version>x_64/instantclient/ <java_class_archive>. Change to the correct directory containing the file templateconfigurator. Change to the correct directory containing the file rdb. Change the file rdb. 46/52 CUSTOMER 2012-10-30 . uš° ¨1−×h¨%wýb»⁄µÈK˜×$Ðæ¯C]în.jar ušº ¨9−”îݡxÂó%.UÉh #FF— /usr/sap/<SAPSID>/JC<instance_number>/j2ee/deploying ušº ¨9−”îݡxÂó%.Ùô@"Ò±‡Mø¸ü©PBoå] 5. Replace the old driver location with the new one: /oracle/client/<Oracle_client_major_version>x_64/instantclient/ <java_class_archive>. 2.vÉ_ FÍ— 2Š» çû˘KÙµ@Ò´‡ øÔÑ©ZBâåh÷áufiX° /usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee ušº ¨9−”îݡxÂó%.UÉh #FF— /usr/sap/<SAPSID>/JC<instance_number>/j2ee ušº ¨9−”îݡxÂó%.driverLocation. start the SAP system: startsap Check the new Oracle version using SAP transaction ST04.ÉT #F’— 2Í»C çûUK.properties as follows: 1.ÉT #F’— 2Ö»H âûGKbÙš@ Òu‡U Open the file with your text editor and search for the property rdbms.ýJ»¡µ©}˜fi$èæôC îE.jar 7.

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

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

Sybase 365. Duet. OS/390. iBooks. Google Mobile. RIM. BlackBerry Storm2. StreamWork. PartnerEdge. and MultiWin are trademarks or registered trademarks of Citrix Systems Inc. Redbooks. Google Mobile Ads. iPhone. BlackBerry Pearl. X/Open. ICA. RACF. UNIX. Microsoft. Dalvik and Android are trademarks or registered trademarks of Google Inc. Business Objects and the Business Objects logo. SQL Anywhere. DB2 Universal Database. iPad. POWER6+. WinFrame.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www. POWER7. Google Data API. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Google Mail. Google Store. System p.sap. Gmail. Power Systems. System i5. Informix. iAnywhere. SAP. DB2 Connect. Tivoli. BlackBerry PlayBook. PowerPoint. Wi-Fi is a registered trademark of Wi-Fi Alliance. BBM. IOS is a registered trademark of Cisco Systems Inc.com © Copyright 2012 SAP AG. HACMP. PowerVM. Google Updater. World Wide Web Consortium. System p5. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. AIX. SAP HANA. OS/2. Web Intelligence. Safari. zEnterprise. Apple. BlackBerry Curve. and Motif are registered trademarks of the Open Group. Linux is the registered trademark of Linus Torvalds in the United States and other countries. GPFS. Google Apps. and Xcode are trademarks or registered trademarks of Apple Inc. XIV. BlackBerry. BlackBerry Storm. iPod. BusinessObjects. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Massachusetts Institute of Technology. PostScript. Google Voice. BladeCenter. DB2. Google Maps. Siri. App Store. Excel. Adobe. and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company. POWER6. Intelligent Miner. System z10. PowerHA. HTML. Retina. System x. and Visual Studio are registered trademarks of Microsoft Corporation. and Smarter Planet are trademarks or registered trademarks of IBM Corporation. RETAIN. YouTube. System Storage. POWER. 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. XML. WebSphere. and W3C are trademarks or registered trademarks of W3C®. z/VM. All rights reserved. iPhoto. Power Architecture. Acrobat. and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. PowerPC. SAP NetWeaver. Oracle and Java are registered trademarks of Oracle and its affiliates. System z. Google Sync. Silverlight. OSF/1. System i. Storwize. Crystal Reports. MetaFrame. 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. VideoFrame. 2012-10-30 CUSTOMER 49/52 . SAP BusinessObjects Explorer. and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. ByDesign. Sybase and Adaptive Server. IBM. z/ OS. Crystal Decisions. BlackBerry Torch. INTERMEC is a registered trademark of Intermec Technologies Corporation. iTunes. the Adobe logo. Bluetooth is a registered trademark of Bluetooth SIG Inc. z10. Objective-C. pureScale. Multi-Touch. R/3. Xcelsius. Outlook. Google Checkout. XHTML. Citrix. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. Google Mobile Updater. Windows. Business Objects is an SAP company. BlackBerry Bold. Google App Engine. Program Neighborhood.

as is any decompilation of these components.Crossgate. Documentation in the SAP Service Marketplace You can find this document at the following address: http://service. without representation or warranty of any kind. National product specifications may vary. Disclaimer Some components of this product are based on Java™. and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. if any. Nothing herein should be construed as constituting an additional warranty.com/instguides 50/52 CUSTOMER 2012-10-30 . Data contained in this document serves informational purposes only. These materials are subject to change without notice. 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. Crossgate is an SAP company. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited. All other product and service names mentioned are the trademarks of their respective companies. and SAP Group shall not be liable for errors or omissions with respect to the materials.sap. m@gic EDDY. B2B 360°. 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. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only.

.

All rights reserved. The information contained herein may be changed without prior notice.sap.com © Copyright 2012 SAP AG. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www. .

Sign up to vote on this title
UsefulNot useful