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. RECOMMENDATION Especially when you are performing a major release upgrade – that is.0.2.2 Lists the status of Oracle patches and bundle patches for 11.2 Oracle 11.2.0 Upgrade Scripts Oracle 11.2.3 Oracle 11.1 1.2. You can access the complete Oracle documentation at the Oracle Technology Network (OTN) website at www.0: Troubleshooting the Software Installation Oracle 11.2.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.0: Current Patch Set Oracle 11.2.1 Introduction New Features 1.0: Patches / Patch collections for 11.1 New Features For the complete list of new features of the Oracle Database 11g Release 2 (11.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.0.2.2.2) [page 47] 1. see the New Features documentation from Oracle.2.0.2.0: Patches / Patch collections for 11.0 Required for upgrading Oracle client software to Oracle 11g Release 2 (11.2.0: Central Technical Note Additional Info / Corrections to Oracle 11g Upgrade Guide Oracle Database 11g: Integration into the SAP environment Oracle 11.3 Describes the shell and SQL upgrade scripts for 11. More Information Configuring the New Features for Oracle Database 11g Release 2 (11.2) Describes the Oracle Instant Client Installation and Configuration 1431796 1431797 1431799 1503709 1631931 1431793 1431794 819829 6/52 CUSTOMER 2012-10-30 . 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. when when you upgrade from 9i or 10g – we recommend that you check the most important new features in the Oracle documentation.com/technology.2).0.2.oracle.0: Troubleshooting the Database Upgrade Oracle 11.

sap.com/ instguides Database Upgrades Oracle https://service.sql) Oracle Database 10g: New database role SAPCONN Using OPatch to install Oracle patches MOPatch – Install Multiple Oracle Patches in One Run BR*Tools Support for Oracle 11g SAP Database User Profile SAPUPROF Oracle 11.1 1.0: Software Installation Oracle Software Deinstallation Oracle 11.2.sap.com/swdc http://service.sap.sap.2) software Describes how to set ORACLE_BASE in an SAP environment 1.sdn.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.com Oracle Download Area oracle-download 2012-10-30 CUSTOMER 7/52 .3 More Information on SAP Service Marketplace You can find more information as following on SAP Service Marketplace: Description Internet Address http://service. the guide you are now reading Oracle download area for patches and software http://service.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.com/notes www. which replaces the native CONNECT role from Oracle Describes how to use OPatch with Oracle – Windows only Describes how to use MOPatch with Oracle – UNIX only Describes the support offered by BR*Tools for Oracle 11g Describes the configuration of an SAP installation with the SAP-specific database user profile SAPUPROF Contains the newest installation scripts Describes how to deinstall the Oracle 11g Release 2 (11.2.0: 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.sap.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

After the upgrade. enter the following command: . Respond appropriately to the DBUA dialogs: The Welcome screen provides information about the upgrade assistant 1. Select the correct database and choose Next. RECOMMENDATION If the DBUA warns you of issues that need to be fixed before the upgrade. The Databases screen lets you select the database to be upgraded.sap. During this step.4 4. performs pre-upgrade checks.sh -silent 2. see SAP note 1431793 or run dbua.sh “œϱ For silent mode. 2012-10-30 CUSTOMER 29/52 .sap./dbua.sh -q 4. use SQL*Plus to execute the script $ORACLE_HOME/rdbms/admin/utlrp. The most common warning or information messages are as follows: Message Explanation or Solution Information message: Database is using a timezone file older than version 14 Warning message: Database contains schemas with stale optimizer statistics Warning message: Database contains INVALID objects prior to upgrade Explanation: Upgrade of TSTZ data is done automatically if the DBUA was started using dbua./dbua.sql. Solution: Run the following command: brconnect -u / -c -f stats -t oradict_stats Solution: To recompile any invalid objects.sap. Run this script in query mode initially to verify that the environment is correct: .sap. The DBUA now analyzes the database to be upgraded.sap. Choose Next to continue. 2.sql to identify any new invalid objects due to the upgrade. Run DBUA as follows: “œϱ For interactive mode.sh.sap. For more information on how to use dbua./dbua.sh -help. run ORACLE_HOME/rdbms/admin/ utluiobj. the SQL*Net profiles are copied.sh.3 Oracle Database Upgrade Database Structure Upgrade cd $ORACLE_HOME_TGT/sap/ora_upgrade/post_upgrade 3. and issues warnings if necessary. Any invalid SYS/SYSTEM objects found before upgrading the database are stored in table registry$sys_inv_objs Any invalid non-SYS/SYSTEM objects found before upgrading the database are stored in table registry $nonsys_inv_objs. you need to analyze and act on these warnings. enter the following command: .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

40 and lower) running on the database server.2) to prevent accidental usage of the old binaries. Start the listener: lsnrctl start Check that you can remotely connect to the database through the listener: sqlplus SAP<SAPSCHEMA_ID>/pwd@SID 5. Procedure Perform a full database backup. you need to rename the bin directory from the old $ORACLE_HOME (from release 10. Procedure 1. 2.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]. 5.9 Renaming or Deleting the Old $ORACLE_HOME/bin Directory Once the database is running correctly. This is because the SAP system running on the database server might still use the Oracle 9i client software. 40/52 CUSTOMER 2012-10-30 .8 Post-Upgrade Steps Starting the Listener Process CAUTION You risk losing data if you do not back up your database. see SAP Note 1525025 (for Oracle release 11.2 and higher).2 or 9. If you want to delete the old Oracle home.2 software. 5. Procedure Rename the old Oracle home directory bin with the following command: mv <old_oracle_home>/bin <old_oracle_home>/bin-old CAUTION Do not rename the entire old_oracle_home in case you have SAP systems (SAP kernel release 6.8 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.5 5.

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

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

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

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

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

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

Cþ‹¥óÊÜ•’Mtwy¥kß—”Õ(jT†´c–ñN.yRÕÛ‡. Change the file sdmrepository.sdc as follows: 1.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. Replace the old driver location with the new one: /oracle/client/<Oracle_client_major_version>x_64/instantclient/ <java_class_archive>.driverLocation.sdc: Ck Ck 2.

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

you need to change it to UTF8. 2012-10-30 CUSTOMER 47/52 .5 5.2) You need to configure the new Oracle Database 11g Release 2 (11. Procedure If necessary.2) features.19 Configuring the New Features for Oracle Database 11g Release 2 (11. If you already use a Java system or plan to use one in the future. 5. 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.18 Post-Upgrade Steps Checking the National Character Set 5.2) see SAP Note 1431800. Procedure For more information about new features with Oracle Database 11g Release 2 (11. follow SAP Note 669902 to change the national character set to UTF8. the national character set must be UTF8.18 Checking the National Character Set If your database still runs with a national character set (NLS_NCHAR_CHARACTERSET) different from UTF8.

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

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

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

.

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

Sign up to vote on this title
UsefulNot useful