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 SAP Notes for the Upgrade Make sure that you read the following SAP Notes: Number Title Remarks 1431800 1454627 1398634 1431798 Oracle 11.3 Describes the shell and SQL upgrade scripts for 11.3 Oracle 11.0 Required for upgrading Oracle client software to Oracle 11g Release 2 (11.2.2.0: Patches / Patch collections for 11.0: Central Technical Note Additional Info / Corrections to Oracle 11g Upgrade Guide Oracle Database 11g: Integration into the SAP environment Oracle 11.0. RECOMMENDATION Especially when you are performing a major release upgrade – that is.2.0: Troubleshooting the Database Upgrade Oracle 11.2. when when you upgrade from 9i or 10g – we recommend that you check the most important new features in the Oracle documentation.2.2.2) [page 47] 1.2.1 1.0: Patches / Patch collections for 11.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.2 Lists the status of Oracle patches and bundle patches for 11.0: Database Parameter Settings Oracle 11. More Information Configuring the New Features for Oracle Database 11g Release 2 (11.2.2) Describes the Oracle Instant Client Installation and Configuration 1431796 1431797 1431799 1503709 1631931 1431793 1431794 819829 6/52 CUSTOMER 2012-10-30 .2.2.1 Introduction New Features 1.2.0.0 Upgrade Scripts Oracle 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.2.1 New Features For the complete list of new features of the Oracle Database 11g Release 2 (11.com/technology.0: Current Patch Set Oracle 11.0. see the New Features documentation from Oracle.0.2.2.0: Troubleshooting the Software Installation Oracle 11. You can access the complete Oracle documentation at the Oracle Technology Network (OTN) website at www.2 Oracle 11.

1 1.sap.com/notes www.sap.sap.2) software Describes how to set ORACLE_BASE in an SAP environment 1.com Oracle Download Area oracle-download 2012-10-30 CUSTOMER 7/52 .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.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.com/ instguides Database Upgrades Oracle https://service.2.com/swdc http://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. the guide you are now reading Oracle download area for patches and software http://service.sap.sdn.sap.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. 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.0: Software Installation Oracle Software Deinstallation Oracle 11.2.3 More Information on SAP Service Marketplace You can find more information as following on SAP Service Marketplace: Description Internet Address http://service.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

2: cd /oracle/<DBSID>/11202/sap/ora_upgrade/pre_upgrade S=Ç÷ 11.2 software home): S=Ç÷ 11.2. see Running the Pre-Upgrade Scripts (9.2.log You can run the pre-upgrade scripts as often as necessary.0.0. 2012-10-30 CUSTOMER 23/52 . By default. 10.2.8) [page 24].2.0.2.6 Preparation Running the Pre-Upgrade Scripts This section only applies if your source database is Oracle 10.2.2: /oracle/<DBSID>/11202/sap/ora_upgrade S=Ç÷ 11. If your source database is Oracle 9.8.log SQL> @pre_upgrade_tasks.3: /oracle/<DBSID>/11203/sap/ora_upgrade Procedure 1.0.0. the scripts are installed as part of the SAP bundle patch in the relevant Oracle 11.0.sql Result You can check the results of the pre-upgrade scripts by looking at the following log files: S=Ç÷ pre_upgrade_status. Prerequisites You are logged on as user ora<dbsid> in the Oracle 10.2 software home directory: S=Ç÷ 11. The directory where the upgrade scripts are installed is called ora_upgrade.2.5. Execute the following commands to check the pre-upgrade status of your database: sqlplus / as sysdba SQL> @pre_upgrade_status.0.3 3.0. Change to the correct directory by entering the relevant command (since the scripts have been extracted to the Oracle 11.sql SQL> spool off 3.0.2. or 11.2 environment with the database also started up. 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.2.1.2.4.log S=Ç÷ pre_upgrade_tasks.0. 11. 2. which can improve the performance of the upgrade process: sqlplus / as sysdba SQL> spool pre_upgrade_tasks.2.3: cd /oracle/<DBSID>/11203/sap/ora_upgrade/pre_upgrade Execute the following commands to perform pre-upgrade tasks.

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

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

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

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

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

sap. After the upgrade. and issues warnings if necessary.sh. use SQL*Plus to execute the script $ORACLE_HOME/rdbms/admin/utlrp.3 Oracle Database Upgrade Database Structure Upgrade cd $ORACLE_HOME_TGT/sap/ora_upgrade/post_upgrade 3. performs pre-upgrade checks./dbua. Solution: Run the following command: brconnect -u / -c -f stats -t oradict_stats Solution: To recompile any invalid objects. For more information on how to use dbua. Run this script in query mode initially to verify that the environment is correct: ./dbua. RECOMMENDATION If the DBUA warns you of issues that need to be fixed before the upgrade. enter the following command: . The Databases screen lets you select the database to be upgraded.sql to identify any new invalid objects due to the upgrade.sap. During this step./dbua.sql. Any invalid SYS/SYSTEM objects found before upgrading the database are stored in table registry$sys_inv_objs Any invalid non-SYS/SYSTEM objects found before upgrading the database are stored in table registry $nonsys_inv_objs. Choose Next to continue.sap.sh “œϱ For silent mode.sh -q 4. The DBUA now analyzes the database to be upgraded. Respond appropriately to the DBUA dialogs: The Welcome screen provides information about the upgrade assistant 1. see SAP note 1431793 or run dbua. 2012-10-30 CUSTOMER 29/52 .sh -help. the SQL*Net profiles are copied. 2.sap. enter the following command: .sh.sh -silent 2. Select the correct database and choose Next. Run DBUA as follows: “œϱ For interactive mode.sap. you need to analyze and act on these warnings. run ORACLE_HOME/rdbms/admin/ utluiobj.sap.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: 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. Accept the default values. The DBUA tool is a graphical tool that leads you step by step through the upgrade. 6.2). you do not need to select the Backup option on this screen. 5. The screen Management Options lets you set up the database so that it can be managed with the Enterprise Manager. parameters to be added. 6. Since you have already performed the database backup [page 27]. the DBUA displays a summary of the changes to be made. If the database server has multiple CPUs. see the documentation for Oracle Database 11g Release 2 (11. The screen Recompiling Invalid Objects lets you choose whether the DBUA has to automatically recompile all PL/SQL modules after the upgrade. The upgrade process itself runs for some time. delete the environment variables ORACLE_HOME_SRC and ORACLE_HOME_TGT.3 Oracle Database Upgrade Database Structure Upgrade 3. components to be upgraded. Make sure that the database instance has stopped after the upgrade. select Specify Flash Recovery Area if you have set up a restore point on the database to facilitate database recovery in the event of problems. This includes the warnings that you ignored or did not fix. 5. 3. 30/52 CUSTOMER 2012-10-30 . 4. 7.0. Before you start it. On the screen Recovery and Diagnostic Location. and changed after the upgrade. 4. If you select this option. if required. The DBUA automatically removes the database initialization parameters that are now obsolete in Oracle Database 11g Release 2 (11.2).2 Starting the Database Upgrade Assistant (Oracle 9. the DBUA automatically proposes the number of parallel processes to be used for the recompilation. select Recompile invalid objects after the upgrade. you need to start the Oracle Database Upgrade Assistant (DBUA). Review the summary of changes and choose Back to make any final adjustments.4 4.3. The screen Move Database Files lets you move the database files during the upgrade process. Select Do not move the database files as part of the upgrade and choose Next.2. Optionally. removed. and choose Next. Make sure that Configure the database with Enterprise Manager is not selected and choose Next. depending mainly on the size of the database and the capacity of the hardware. For a complete list of obsolete and deprecated parameters. NOTE 4. Start the database upgrade by choosing Finish. make sure that you also specify the location and the size of the flash recovery area and its files. When the DBUA has completed successfully the results of the upgrade are displayed Review the changes made and exit the DBUA.

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

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

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

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—é\.

1 source database: C11:/oracle/C11/112_64:N û_*j¼› Oracle 10. û_*j¼› Oracle 9. EXAMPLE The entry for a system with a <DBSID> equal to C11 is as follows: û_*j¼› Oracle 11.0.2.0. insert it using a text editor.2.‹$óÍlŸ.2 source database C11:/oracle/C11/102_64:N.2 source database: C11:/oracle/C11/11202:N û_*j¼› Oracle 11. Make sure that the oratab file contains the following entry: <DBSID>:<old_ORACLE_HOME>:N Where old_ORACLE_HOME stands for the path to the old oracle software installation. 34/52 CUSTOMER 2012-10-30 . If this entry does not exist.2 source database C11:/oracle/C11/920_64:N 2.ÞÆ»łÏæÉVŠ²±5ÿF0º Procedure 1.

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

36/52 CUSTOMER 2012-10-30 . Procedure Upgrading from source database 11.0.2.3 Checking the Upgraded Database You need to check the upgraded database.2. 5. 1.5 5.1 Oracle home. For more information on this step.2.2.2) software in an Oracle Database 11g Release 2 (11.2. Change to the required directory: cd /oracle/<DBSID> If no database is still running from the old 11.1 1. 3.0. Create a symbolic link to the new Oracle home: ln -s 11203 /oracle/<DBSID>/112_64 Restart the database. Check that the database is now running with Oracle Database 11g Release 2 (11. Procedure 1. see SAP Note 1525025. 2. Log on to the database as the ora<sid> user. make sure that ORACLE_HOME is set to the runtime Oracle home: /oracle/<DBSID>/112_64 5. 4. 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 Creating a Symbolic Link for Runtime Oracle Home This procedure is only necessary for the update from 11.2.0. 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. 2. It links the runtime Oracle home <OHRDBMS> to the installation Oracle home <IHRDBMS>.0.0. Change to the required directory: cd /oracle/<DBSID> Upgrading from source database 11.2) environment by entering the following commands: 1.1 or 11. detach this Oracle home from the inventory and rename the old Oracle home: mv 112_64 11201 3.

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

5 Performing Post-Upgrade Tasks You need to perform certain post-upgrade tasks. change database compatibility by entering the following as the ora<dbsid> user: cd $ORACLE_HOME/sap/ora_upgrade/post_upgrade SQL> conn / as sysdba SQL> @set_compatible 2.sql from SAP note 403704. CAUTION 3. perform the following tasks before gathering the Oracle optimizer statistics using brconnect: 1.sql from the same note 3.sql or dbcheckora11_oltp.sql $ORACLE_HOME/dbs cd $ORACLE_HOME/dbs sqlplus /nolog @sapconn_role 4. Implement SAP delivered statistics from SAP Note 1020260. execute the SQL script sapuprof_profile.5 5. Apply script dbstatc11. 2.8. Make sure that you execute this command for every SAPSCHEMA_ID in your database. Gather Oracle optimizer statistics by executing the following commands as the ora<dbsid> user: brconnect -u / -c -f stats -t system_stats brconnect -u / -c -f stats -t oradict_stats 38/52 CUSTOMER 2012-10-30 .sql 5. 3. Execute the SQL script sapconn_role.0.2. Check database compatibility by executing the following command: SQL> show parameter compatible If not set to 11.2. If not executed by dbua as part of the post-upgrade scripts.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. Procedure 1.0.sql as follows: cd $ORACLE_HOME/sap/ora_upgrade/post_upgrade sqlplus / as sysdba @sapuprof_profile.sql as follows: cp /usr/sap/<SAPSID>/SYS/exe/run/sapconn_role. Apply script dbcheckora11_olap. If your source database is Oracle 9. you have to enter both commands.

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

40/52 CUSTOMER 2012-10-30 . 5. 5.8 Starting the Listener Process You start the listener process. 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.9 Renaming or Deleting the Old $ORACLE_HOME/bin Directory Once the database is running correctly.8 Post-Upgrade Steps Starting the Listener Process CAUTION You risk losing data if you do not back up your database. Procedure 1.2 software. see SAP Note 1525025 (for Oracle release 11.40 and lower) running on the database server. If you want to delete the old Oracle home. 2. you need to rename the bin directory from the old $ORACLE_HOME (from release 10.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.2 and higher).10 Checking the Read Authorization of the <sapsid>adm User You check the read authorization of the <sapsid>adm user. as described in Copying and Adapting the SQL*Net Files [page 22]. Procedure Perform a full database backup. Procedure Rename the old Oracle home directory bin with the following command: mv <old_oracle_home>/bin <old_oracle_home>/bin-old CAUTION Do not rename the entire old_oracle_home in case you have SAP systems (SAP kernel release 6.2 or 9.2) to prevent accidental usage of the old binaries. This is because the SAP system running on the database server might still use the Oracle 9i client software.

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

cshrc. á^fl³¾Æ If the environment variable TNS_ADMIN is not set.ora file under /etc and use this file for the change described below in the next step. . Determine the SQL*Net files used by <sapsid>adm as follows: á^fl³¾Æ If the environment variable TNS_ADMIN is set.ora file for the <sapsid>adm and ora<sid> users after the upgrade: á^fl³¾Æ For the ora<sid> user.WORLD = (ADDRESS = (COMMUNITY = SAP. Procedure Adapting the SQL*Net Files for the ora<sid> User ORACLE_HOME>/network/admin if they 1. 2. the SQL*Net files are used from the specified location (even if ORACLE_HOME is set).WORLD)(PROTOCOL = TCP)(HOST = <hostname>)(PORT = <listener_port>)) NOTE Although this entry is only needed on the database server or on central systems where the startdb or stopdb scripts are used.5 5.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.dbenv_<hostname>. Without this entry. Check whether R3trans can connect to the database: R3trans –d 5. Log out and log on again as the <sapsid>adm user.csh. you need to adapt the SQL*Net files are located in the directory $ORACLE_HOME/network/admin. NOTE DBUA modifies the SQLNET profiles in the directory <new already exist when the upgrade is started. 3.14 Updating the SQL*Net Configuration Files for the <sapsid>adm and ora<sid> Users You need to update the tnsnames. á^fl³¾Æ For the <sapsid>adm user. look for a 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 . 4. and so on). Add the following entry to the tnsnames. it is recommended to repeat the change described above on all application servers. Make sure that the change to the user environment is permanently stored in the profiles (. Add the following entry to the tnsnames. the startdb or stopdb script fails with the following error message: ORA-00119: invalid specification for system parameter LOCAL_LISTENER Adapting the SQL*Net Files for the <sapsid>adm User 1.

WORLD = (ADDRESS = (COMMUNITY = SAP.5 5. These variables point to the ORACLE_HOME used by the application server. ‡h·=¯~}¡ùd˙‰ƒý⁄ÂVbã(×QŁo_8Y~7°+|ôÙ¼m:x.=†!n‘—º°Gƒ0T¨mµ¬˝²ï3ñ¥’E˘Íj.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. Set DIR_SERVER_ORAHOME in the default profile to the value of the ORACLE_HOME environment variable of the ora<dbsid> user on the database server. it is recommended to repeat the change described above on all application servers.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.15 Post-Upgrade Steps Checking SAP Profile Parameters LISTENER_<DBSSID>. 2. the startdb or stopdb script fails with the following error message: ORA-00119: invalid specification for system parameter LOCAL_LISTENER 5. Without this entry. Set DIR_ORAHOME and DIR_CLIENT_ORAHOME in the instance profiles to the corresponding values of the ORACLE_HOME environment variable of the <sapsid>adm user.

the Oracle client major version as used in the procedure below is Oracle 10. 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.Òí–YÀ“ܯghÔÈq 5. you might have to change the location of the JDBC driver after you have upgraded the database server or client software. You change the location of the JDBC driver as follows: 2012-10-30 CUSTOMER 43/52 .16 Changing the Location of the JDBC Driver If you have an SAP system with Java components. NOTE ‡h·Ò−° You only need to perform this procedure if your source database was Oracle 9.2. So you need to replace occurrences of the variable <Oracle_client_major_version> with 10. ‡h·Ò−° At the publication time of this guide.

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

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

driverLocation.yRÕÛ‡. Change the file sdmrepository.sdc as follows: 1. Replace the old driver location with the new one: /oracle/client/<Oracle_client_major_version>x_64/instantclient/ <java_class_archive>.sdc: Ck Ck 2. Cþ‹¥óÊÜ•’Mtwy¥kß—”Õ(jT†´c–ñN.jar 5.|Øû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.yYÕø‡. Change to the correct directory containing the file sdmrepository.|éûÜ×ã /usr/sap/<SAPSID>/JC<instance_number>/SDM/program/config Cô‹¥óÂÜÙ’dw"¥'ü—‰Õ~jS†{c Cþ‹¥óÊÜ•’Mtwy¥kß—”Õ(jT†´c–ñN.

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

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

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

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

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

.

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

Sign up to vote on this title
UsefulNot useful