Database Upgrade Guide Upgrade to Oracle Database 11g Release 2 (11.
2): UNIX
For Oracle Patch Set Release 11.2.0.2 and 11.2.0.3
Target Audience fi «£z% Technology Consultants fi «£z% System Administrators fi «£z% Database Administrators fi «£z% Developers
CUSTOMER fi «G_ꟹM/ÝSÁÙ„Ö<ޤæU$0A=µÒ5;¸ät@ž²ð %÷¨^8~ýœÔZ*€Qı@cë™JUê¸eÄ'2A"Ö,
Document History
CAUTION
Before you start the implementation, make sure you have the latest version of this document. You can find the latest version at the following location: http://service.sap.com/instguides Database Upgrades Oracle The following table provides an overview of the most important document changes.
Version Date Description
3.02 3.01 3.00 2.10 2.01 2.00 1.14 1.13 1.12 1.11 1.10 1.01 1.00
2012-10-30 2012-08-08 2011-12-20 2011-09-16 2011-05-19 2011-04-14 2010-09-10 2010-08-25 2010-08-03 2010-06-15 2010-06-09 2010-04-27 2010-04-01
Minor corrections in chapter Updating the Oracle Installation Scripts Various corrections Major update for Oracle Patch Set Release 11.2.0.3 Various corrections Various corrections Major update for Oracle Patch Set Release 11.2.0.2 Chapter Changing the Location of the JDBC Driver added Various corrections Various corrections Change to section Updating BR*Tools Major update including upgrade from Oracle 9.2.0.8 Various corrections Initial Version
2/52
CUSTOMER
2012-10-30
Table of Contents
Chapter 1 1.1 1.2 1.3 Chapter 2 2.1 2.2 2.3 2.4 2.5 Chapter 3 3.1 3.2 3.3 3.4 3.5 3.5.1 3.5.2 3.5.3 3.5.4 3.5.5 3.6 3.7 Chapter 4 4.1 4.2 4.3 4.3.1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Notes for the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . More Information on SAP Service Marketplace . . . . . . . . . . . . . . . . . . . . . . . . .
5 6 6 7
Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Checking the Original Version of Your Database . . . . . . . . . . . . . . . . . . . . . . . . 9 Checking Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . 10 Reviewing the Oracle-Specified Kernel Parameters and Shell Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Checking Additional Requirements for the Upgrade . . . . . . . . . . . . . . . . . . . . 10 Checking the SAP System Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Correct UNIX Users, Groups, and Authorizations . . . . . . . . . . . Checking the Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating the Oracle Installation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Software Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . Database Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking and Setting the Environment Variables . . . . . . . . . . . . . . . . . . . . . . Backing Up the Central Oracle Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Oracle Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Required SAP Bundle Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying and Adapting the SQL*Net Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the Pre-Upgrade Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the Pre-Upgrade Scripts (Oracle 9.2.0.8) . . . . . . . . . . . . . . . . . . . . . . Oracle Database Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing Up the Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shutting Down the SAP System and Oracle Listener Process . . . . . . . . . . . . . . Database Structure Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Database Upgrade Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 13 13 15 16 17 17 19 20 21 22 22 24 27 27 27 28 28
2012-10-30
CUSTOMER
3/52
4.3.2 4.3.3 Chapter 5 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 5.13 5.14 5.15 5.16 5.17 5.18 5.19
Starting the Database Upgrade Assistant (Oracle 9.2.0.8) . . . . . . . . . . . . . . . . . 30 Checking the oratab Entry (Oracle 9.2.0.8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Post-Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finalizing the Environment of the ora<dbsid> User . . . . . . . . . . . . . . . . . . . . Creating a Symbolic Link for Runtime Oracle Home . . . . . . . . . . . . . . . . . . . . Checking the Upgraded Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating BR*Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Post-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Symbolic Link for the Data Shared Library . . . . . . . . . . . . . . . . . . . Backing Up the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Listener Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Renaming or Deleting the Old $ORACLE_HOME/bin Directory . . . . . . . . . . Checking the Read Authorization of the <sapsid>adm User . . . . . . . . . . . . . Updating the Oracle Instant Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating the SAP Kernel from 640_REL to 640_EX2 . . . . . . . . . . . . . . . . . . . . Changing the Environment for the <sapsid>adm user . . . . . . . . . . . . . . . . . . Updating the SQL*Net Configuration Files for the <sapsid>adm and ora<sid> Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking SAP Profile Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Location of the JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the National Character Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the New Features for Oracle Database 11g Release 2 (11.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 35 36 36 37 38 39 39 40 40 40 41 41 41 42 43 43 46 47 47
4/52
CUSTOMER
2012-10-30
1
Introduction
1 Introduction
This documentation describes how to upgrade the Oracle database for the SAP system on the UNIX operating system: u¹£ì™j From source release Oracle 9.2.0.8, Oracle Database 10g Release 2 (10.2.0.4 or 10.2.0.5), Oracle Database 11g Release 2 (11.2.0.1), or higher u¹£ì™j To target release Oracle Database 11g Release 2 (11.2) (11.2.0.2 or 11.2.0.3 or higher) This guide is suitable for both major release upgrades (for example, from Oracle 9.2.0.8 or Oracle 10.2.0.5 to Oracle 11.2.0.2 or Oracle 11.2.03) and for patch set upgrades (for example, from Oracle 11.2.0.1 to 11.2.0.2 or 11.2.0.3). In both cases, the upgrade target release is the current 11.2 patch set release. This guide does not cover upgrades of Oracle databases with Real Application Clusters (RAC) Automatic Storage Management (ASM), or Exadata. We plan to document these at a later date. If your source database is Oracle 9.2.0.8, there are some differences in the procedure and these are clearly marked in the text.
CAUTION
Oracle 11.2 is only supported for SAP systems with an EX2 kernel or higher.
Implementation Considerations
u¹£ì™j For more information about implementation considerations, including the most important SAP Notes for the upgrade, see Planning [page 9]. u¹£ì™j Be sure to read the relevant SAP Notes before beginning the upgrade. These notes contain the most recent information about the upgrade, as well as corrections to the documentation. You can find the most recent version of the SAP Notes at http://service.sap.com/notes u¹£ì™j You might find useful information for the upgrade in the following Oracle documentation: u¹£ì™ Oracle 11gR2 Upgrade Companion [ID 785351.1] u¹£ì™ Operating Systems Installation and Configuration Requirements Quick Reference (8.0.5 to 11.2) [ID 169706.1] u¹£ì™j You use the tools Oracle Universal Installer (OUI), MOPatch (Opatch), Oracle SQL*Plus, and Oracle Database Upgrade Assistant (DBUA) to perform the upgrade. u¹£ì™j To make this documentation easier to read, only the location for 64-bit platforms is used. If your database runs on a 32-bit platform (Linux 32–bit), replace as appropriate occurrences of 64 with 32. For example, replace 112_64 with 112_32.
Naming Conventions
We use <DBSID> for the database instance identifier and <SAPSID> for the SAP system identifier. These can be different if your SAP system uses Multiple Components in One Database (MCOD).
2012-10-30
CUSTOMER
5/52
2.1 1.0: Database Parameter Settings Oracle 11.2.1 New Features For the complete list of new features of the Oracle Database 11g Release 2 (11.3 Describes the shell and SQL upgrade scripts for 11. RECOMMENDATION Especially when you are performing a major release upgrade – that is.2 Lists the status of Oracle patches and bundle patches for 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) Describes the Oracle Instant Client Installation and Configuration 1431796 1431797 1431799 1503709 1631931 1431793 1431794 819829 6/52 CUSTOMER 2012-10-30 .2.2 SAP Notes for the Upgrade Make sure that you read the following SAP Notes: Number Title Remarks 1431800 1454627 1398634 1431798 Oracle 11.2. see the New Features documentation from Oracle.0: Troubleshooting the Database Upgrade Oracle 11.0: Current Patch Set Oracle 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.1 Introduction New Features 1. More Information Configuring the New Features for Oracle Database 11g Release 2 (11.0: Patches / Patch collections for 11.2.2.0.0 Required for upgrading Oracle client software to Oracle 11g Release 2 (11.com/technology.2.2).0 Upgrade Scripts Oracle 11.2.2.2.0. 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. You can access the complete Oracle documentation at the Oracle Technology Network (OTN) website at www.oracle.2.2.0.3 Oracle 11.0: Patches / Patch collections for 11.2.0: Troubleshooting the Software Installation Oracle 11.0: Central Technical Note Additional Info / Corrections to Oracle 11g Upgrade Guide Oracle Database 11g: Integration into the SAP environment Oracle 11.0.2) [page 47] 1.2 Oracle 11.
2. which replaces the native CONNECT role from Oracle Describes how to use OPatch with Oracle – Windows only Describes how to use MOPatch with Oracle – UNIX only Describes the support offered by BR*Tools for Oracle 11g Describes the configuration of an SAP installation with the SAP-specific database user profile SAPUPROF Contains the newest installation scripts Describes how to deinstall the Oracle 11g Release 2 (11.com/ instguides Database Upgrades Oracle https://service.com 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.sap.2) software Describes how to set ORACLE_BASE in an SAP environment 1.1 1.3 More Information on SAP Service Marketplace You can find more information as following on SAP Service Marketplace: Description Internet Address http://service.sap.com/swdc http://service.2.sql) Oracle Database 10g: New database role SAPCONN Using OPatch to install Oracle patches MOPatch – Install Multiple Oracle Patches in One Run BR*Tools Support for Oracle 11g SAP Database User Profile SAPUPROF Oracle 11.sap.sap.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.com/notes www.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.0: Software Installation Oracle Software Deinstallation Oracle 11. the guide you are now reading Oracle download area for patches and software http://service.sdn.
.This page is left blank for documents that are printed on both sides.
3.2 2.2) in manual mode (in this guide we only describe the database upgrade using the DBUA) /jeÃ%« If the source database runs Oracle 10.0. Process 1. 5. you need to first upgrade the source database to at least patch set 10. Prerequisites In the following special cases you need to obtain more information: /jeÃ%« If you are upgrading from Oracle 10. You check the hardware and software requirements [page 10]. see the documentation for the Oracle Database 11g Release 2 (11. obtain more information. 1. You check additional requirements for the upgrade [page 10]. To check the original version of your database. if necessary.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 to Oracle Database 11g Release 2 (11. For more information in the special cases mentioned above. You review the Oracle-specified kernel parameters and shell limits [page 10]. You check the SAP System prerequisites [page 12].2. 2012-10-30 CUSTOMER 9/52 . 2. You check the original version of your database [page 9]. make sure that you perform a test upgrade on your backup system.2. 2.2.1 Planning Checking the Original Version of Your Database 2 Planning RECOMMENDATION Before the production upgrade.0. 4.5. 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) upgrade at the Oracle Technology Network (OTN) website.
2). To check for your application or product. 2. which you can find at: www.1I up to and including 4. and SAP kernel release 640_EX2 and above.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. For these older releases. Make sure you have read the SAP Notes for the upgrade [page 6].2).4 Checking Additional Requirements for the Upgrade You need to check the additional requirements for the Oracle database upgrade as described in this section.6C. see the Product Availability Matrix (PAM) at http://service. NOTE There is no general release provided for older SAP releases 3. Download the recommended documents from My Oracle Support (formerly Oracle Metalink) at https://support. For access to My Oracle Support. see SAP Note 758563. Procedure Obtain the recommended shell limits and kernel parameters from the relevant Oracle database installation guide for your operating system.oracle. These are only recommendations from Oracle for optimizing the system performance in production environments. 2.sap. only an upgrade certification is provided for valid upgrade paths – for 10/52 CUSTOMER 2012-10-30 . which you can find at http://service. Procedure 1. If the recommended settings are not suitable for your system you must tune the kernel parameters accordingly.com/pam. You can access the complete Oracle documentation as a member of the Oracle Technology Network (OTN).com/notes 2. Oracle 11.2 2.com.2 Planning Checking Hardware and Software Requirements 2. The complete list of hardware and software requirements for every platform is included in the Oracle documentation.com/technology/documentation Select the appropriate documentation for Oracle Database 11g Release 2 (11.2 is only released and certified for SAP products running with SAP BASIS 640 and above.oracle.3 Reviewing the Oracle-Specified Kernel Parameters and Shell Limits You need to review the Oracle-recommended kernel parameters and shell limits for your operating system with Oracle Database 11g Release 2 (11.
2).2 2. If you have a 640_REL kernel. Download the Oracle Database 11g Release 2 (11.8 and your SAP kernel is 640_REL kernel. more information.4 Planning Checking Additional Requirements for the Upgrade 3. make sure that you install all these patches. download the 640_EX2 kernel from SAP Service Marketplace.0.2. RECOMMENDATION 5. We do not support running a 640_REL kernel with the Oracle 11.2.com/swdc 8.sap.2 Instant Client software from: http://service. BR*Tools supports the Oracle Database 11g Release 2 (11. You can download the patches from: http://service.2) installation guide for your operating system from the Oracle Technology Network (OTN). If you have access to My Oracle Support.5B) or EX2 kernel (for release 4. You need this document to review the hardware and software requirements and to configure the kernel parameters and shell limits.6C). The patches listed in the SAP Note referenced in SAP Note 1431800 are mandatory. RECOMMENDATION 4.com/oracle-download CAUTION 6. 2012-10-30 CUSTOMER 11/52 . Make sure that you download the complete 640_EX2 kernel: both SAPEXE. To upgrade from a remote PC. you need X-Windows software on the PC.10 (patch level 30). the SAP kernel needs to be EXT kernel (for releases 3.2) software and the latest patch sets and required patches or patch collection. as described in SAP Note 432861.com/oracle-download Download the latest version of the DBATOOLS (BR*Tools) to be used immediately after the database upgrade from: http://service. For upgrade certification. If your source database is Oracle 9.sap.20 (patch level 1) . see SAP Note 1430669. The SAP Note with the list of patches is referenced in SAP Note 1431800. This document provides information on all operating system prerequisites and is regularly updated. Download the latest version of the Oracle 11.2 database. In some situations the OUI and DBUA screens are not displayed correctly when started remotely. In such cases we recommend you to start the OUI and the DBUA directly from the console. we strongly recommend that you read document 169706.1 up to and including 4.1.or Release 7. 7. as of release 7. For more information.SAR. To avoid severe database problems. you need to switch to the 640_EX2 kernel immediately after the database upgrade to Oracle 11. Download the Oracle Database 11g Release 2 (11. see SAP Note 1398634.sap.SAR and SAPEXEDB.
12/52 CUSTOMER 2012-10-30 . and 1433301 if you are running any of the following support packages: úÜ~Ö#˚ SAP_BASIS 7.10 SP10 úÜ~Ö#˚ SAP_BASIS 7. apply SAP Notes 1416108.2 2.5 Planning Checking the SAP System Prerequisites 2. The error is fixed in later support packages. apply the advanced correction from SAP Note 1417124 This correction resolves an Oracle issue that results in an ABAP short dump during statistics updates.00 SP21 úÜ~Ö#˚ SAP_BASIS 7. 3. If your SAP system uses SAP Kernel 711.02 SP02 úÜ~Ö#˚ SAP_BASIS 7.5 Checking the SAP System Prerequisites Procedure 1. If your SAP system is SAP BASIS 7xx.20 SP02 This resolves an error in an ABAP program that causes it to report problems during the consistency checks within transaction SE14.11 SP05 úÜ~Ö#˚ SAP_BASIS 7. 1414733. This error is seen only after the database has been upgraded to Oracle 11. For SAP systems 7. 2.2.01 SP06 úÜ~Ö#˚ SAP_BASIS 7. For more information.XX when you are performing a major release upgrade. you need to use DBSL (dboraslib. see SAP Note 1456323.so) patch level 81 or higher.
If your source database is Oracle 9.2 Checking the Directory Structure You need to verify the availability and correctness of the following Oracle directories: .7O6óï stage directory . 4. 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.4.0. you run the pre-upgrade scripts [page 22]. If your source database is Oracle 10. you run the pre-upgrade scripts (Oracle 9. You check the software installation prerequisites [page 16]. and Authorizations 3 Preparation You have to complete the following preparations: 1. groups. see SAP Note 1521371.0. You check the directory structure [page 13]. 3. since you perform the database installation as user ora<dbsid>. and authorizations [page 13].7O6óï Home directory 2012-10-30 CUSTOMER 13/52 .2. 6.3 3. 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. Groups.2.8) [page 24]. You update the Oracle installation scripts [page 15].1 Preparation Checking the Correct UNIX Users. 3.1 Checking the Correct UNIX Users. You check the correct UNIX users. and Authorizations You need to check that the ora<dbsid> user has write authorization for the $ORACLE_BASE directory.8. 7.7O6óï Oracle inventory directory . 2.2. For information about $ORACLE_BASE. 3. Groups.0. 5. You install the database software [page 17].
Check the Oracle inventory directory.2 components such as database. only the software contained within the component database is used. In this case. Check the Oracle stage directory.0.3 3.2. 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.SAR. If this directory does not exist. you only need to extract the database software. For a single-instance database upgrade.0.3). these 2 SAR files alone are sufficient. If there is not enough space. The path to the Oracle inventory directory is mentioned in the Oracle inventory pointer 14/52 CUSTOMER 2012-10-30 . The Oracle inventory directory maintains the inventory of all Oracle software installed on the system.2: /oracle/stage/11202 T¢ªueh 11.2 Preparation Checking the Directory Structure Procedure 1. gateways. For the database upgrade.SAR SAPCAR –xvf OR211264. the following subdirectories exist under /oracle/stage/11202 or /oracle/stage/11203: T¢ªueh T¢ªueh T¢ªueh T¢ªueh T¢ªueh T¢ªueh database client grid examples gateways deinstall NOTE 2.2. When the RDBMS CDs have been mounted. which include the various Oracle 11. grid. create the staging directory as follows: T¢ªueh 11. you can delete previous stage directories. create it manually. The Oracle Database DVD contains a total of six or seven SAR files (depending on the platform).0. If it already exists it might contain software stages from previous installations or upgrades.SAR and OR211264. 3.2 or 11. use the SAP tool SAPCAR to extract all the RDBMS CDs to /oracle/stage/11202 or /oracle/stage/11203 as user ora<sid>. EXAMPLE For example. and so on. client.3: /oracle/stage/11203 2.2. you do not need to extract any other SAR files.SAR After you have finished the extraction of all the RDBMS CDs.2. If you only use a single instance database. 1. usually called /oracle/stage. the following commands extract the database software (on DVDs 1 and 2): SAPCAR –xvf OR111264.0. The database components are packed in the files OR111264.
RUNINSTALLER_CHECK. Before starting the installation of the new Oracle software on the database host. By default in Oracle 11. make sure that the variable inventory_loc in the file oraInst. enter: .loc file does not exist. This script supports installation in response file mode (interactive) and silent mode. For more information. and starts the Oracle installer. make sure that the file oraInst.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. generates the response file. Prerequisites The SAP-specific installation scripts RUNINSTALLER./RUNINSTALLER -help ˜Y5| ‚ RUNINSTALLER_CHECK This script performs product-specific prerequisite checks with the following command: .3 Preparation Updating the Oracle Installation Scripts 3.com/cd/E11882_01/em.sh script as super user from the <oraInventory> location.sh This is the main script behind RUNINSTALLER and RUNINSTALLER_CHECK. enter the location where you want the inventory log files to be written to. and 11ginstall. you must create it at the end of the installation by running the orainstRoot. If this is the first installation of Oracle database software on the host and the oraInst.3 Updating the Oracle Installation Scripts If a newer version is available. which are attached to SAP Note 1524205. 3.loc points to the location where the Oracle inventory is located.3 3. the inventory is created in /oracle/oraInventory.htm./RUNINSTALLER For help.112/ e12255/oui2_manage_oracle_homes. file oraInst. If this is the first time that the OUI has been executed on this host. see http://docs. From there you can download the relevant package for your release. 2012-10-30 CUSTOMER 15/52 . we recommend that you update the Oracle Installation scripts.oracle./RUNINSTALLER_CHECK ˜Y5| ‚ 11ginstall.loc. After you have extracted the Oracle software to the staging area.2.sh are located in directory SAP in the Oracle database software stage: ˜Y5| ‚ RUNINSTALLER This script installs the software with the following command: . you need to update the installation scripts.
zip. Checking prerequisites for the OUI: . kernel parameters): 16/52 CUSTOMER 2012-10-30 . 2./rootpre.3: cd /oracle/stage/11203/database As the user root.zip 3.4 Checking the Software Installation Prerequisites You must check the prerequisites for the Oracle Universal Installer (OUI). The zip file contains the current version of the installation scripts. Change to the relevant directory as follows: WÙxM*£ 11.2. Prerequisites Make sure that the DISPLAY environment variable is set correctly./runInstaller –executeSysPrereqs 2. which is attached to SAP Note 1524205. 3. 2. 5.4 Preparation Checking the Software Installation Prerequisites Procedure Updating the Installation Scripts 1. patches. Download the file 11ginstall_<release>_<patch_level>_complete. 2.2. WÙx¢m=‰Â«óÀåä¹lÂù˙6Ï»JÿY®qT¾3V0ʤªSÒ-L5 On AIX.old Extract the zip file: $ unzip 11ginstall-<release>-<patch-level>-complete.2: cd /oracle/stage/11202/database WÙxM*£ 11.0.3 3.sh: . 3. Copy the file to the database directory in the Oracle software stage directory: $ cp 11ginstall-<release>-<patch-level>-complete. Log on as the Oracle user ora<dbsid>.0. call the script rootpre. Checking operating system requirements (release. call the script rootpre.sh WÙx¨m=…ł«¼Ð忹 ÂÑ˙˙ÏÃJ9Y Procedure 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. 4.sh: WÙx¨m=…ł«¼Ð忹 ÂÑ˙˙ÏÃJ9Y WÙx¢m=‰Â«óÀåä¹lÂù˙6Ï»JÿY®qT¾3V0ʤªSÒ-L5 1. Change directory: cd /oracle/stage/11202/database Execute the following commands: 1.
3 3. Apply missing OS patches and set OS kernel parameters as recommended by the OUI. 3.2 software. This means that you do not need to install Oracle Database 11g Release 2 (11.5 Database Software Installation As part of preparations.1) before installing the new patch set release.0.5 Preparation Database Software Installation cd SAP . NOTE You can install the database software while the SAP system is still running with the existing database (that is.2.2). 3. You copy and adapt the old Oracle SQL*Net files [page 22]. see Changing the Environment for the <sapsid>adm User [page 41]. 2. You can install the new database software while the SAP system is running with a lower patch set version. NOTE For more information about changes to the environment of the SAP user <sapsid>adm. 4. You install the required SAP bundle patch [page 21]. you need to check and set the environment variables of user ora<dbsid> because this user installs the Oracle software.2. Process Flow 1. You check and set the environment variables [page 17]. You run the Oracle Universal Installer [page 20]. Oracle 10.2 patch set. Starting with the Oracle 11. 2012-10-30 CUSTOMER 17/52 ./RUNINSTALLER –check 4. to reduce downtime you can perform the following steps before you stop your system. You back up the central Oracle inventory [page 19]. 3. Therefore.0. Prerequisites Make sure that you set the environment variables as described below for the duration of this session only. Oracle Database patch sets are full installations of the Oracle Database software.5. you install the Oracle 11.1 Checking and Setting the Environment Variables To install the database software. 5.
2. or 3) to 11. /oracle or /oracle/<DBSID> For more information.3 3. SAPDATA_HOME VÕ«Fª¥¬YWˆËùëY üðñÇ_ł¦ÉÆ?REÇ ÖU+ Mflˆ óF|á− /oracle/<DBSID> VÕ«Fª¥¬YWˆËùëY üðñÇ_ł¦ÉÆ?REÇ ÖU+ Mflˆ óF|á− LIBPATH VÕ«Lª¥¬QWC˶ëIQü¼ñï_¶¦±ÆùRV VÕ«Fª¥¬YWˆËùëY üðñÇ_ł¦ÉÆ?REÇ ÖU+ Dfl ‰F‹á—‹/¥ÊRçxÑfi9QZ‡õ>î!»ð®$ôý©ä.Y (where Y > X): /oracle/<DBSID>/112_64 NLS_LANG One of the following values: AMERICAN_AMERICA.X (where X = 1.§fi“-Y9ºÂr⁄W+Þ¶.2 (10.WE8DEC AMERICAN_AMERICA.2. <DBSID> ORACLE_SID ORACLE_HOME Make sure that it is set to the value of the current runtime Oracle home. see SAP Note 102402.5) to 11.<h˙‚ $ORACLE_HOME/lib:$LIBPATH VÕ«Lª¥¬QWC˶ëIQü¼ñï_¶¦±ÆùRV VÕ«Fª¥¬YWˆËùëY üðñÇ_ł¦ÉÆ?REÇ ÖU+ Dfl ‰F‹á—‹/¥ÊRçxÑfi9QZ‡õ>î!»ð®$ôý©ä.ôá©ø.2. EXAMPLE VÕ«©‘k When upgrading from 10.2. we strongly recommend moving it to WE8DEC or UTF8 before the upgrade.X: /oracle/<DBSID>/102_64 VÕ«©‘k When upgrading from 11.fl åFŁá®‹a¥°Rž§6ѳ9gZðõ5îu»Ð®. You make them permanent in the database structure upgrade.0 NOTE <hostname>:0. We recommend you to back up the old environment files before making the changes permanent. For more information about WE8DEC.0.4 or 10.0.0.2.UTF8 If your database still runs with the character set US7ASCII.<h˙‚ LD_LIBRARY_PATH VÕ«Lª¥¬QWC˶ëIQü¼ñæ_¯¦ÉÆ RXÇxÖY? . Procedure 1.ôá©ø. Value <hostname>:0. Make sure the following environment variables are not set: VÕ«©‘k TWO_TASK VÕ«©‘k ORA_NLS VÕ«©‘k ORA_NLS32 VÕ«©‘k ORA_NLS33 VÕ«©‘k ORA_NLS10 Make sure that the following environment variables are set as described: Environment Variable DISPLAY 2. see SAP Note 1521371.fl åFŁá®‹a¥°Rž§6ѳ9gZðõ5îu»Ð®.0. 2.5 Preparation Database Software Installation CAUTION Do not make the changes to the environment permanent while the old database is still running.§fi“-Y9ºÂr⁄W+Þ¶.0 is the host on which the Oracle Universal ORACLE_BASE Installer (OUI) is to be displayed.¬fi-v 18/52 CUSTOMER 2012-10-30 .¬fi-v $ORACLE_HOME/lib:$LD_LIBRARY_PATH VÕ«Lª¥¬QWC˶ëIQü¼ñæ_¯¦ÉÆ RXÇxÖY? .0.
oracle. Linux: /etc/oraInst. Check if the temporary directory (usually /tmp) has at least 1024 MB of free space.cµºý»m·°xÐ˛SÙ PATH PATH includes $ORACLE_HOME/bin of the current active ORACLE_HOME.2 -> 11. When you perform a patch set upgrade from 11. RECOMMENDATION You can check the correctness of the new environment with the UNIX env command.112/e12255/oui2_manage_oracle_homes.5 Preparation Database Software Installation Environment Variable ð"j:·ÔÝpè&