sapnote_0001524205

11.04.2012 of 14

SAP Note 1524205 - Oracle 11.2.0: Database SoftwareInstallation

Note Language: English Version: 53 Validity: Valid Since 10.02.2012

Summary

Symptom

Installation of Oracle Database Software

This SAP note describes the installation of Oracle Database software ofrelease 11.2.0.2 and higher in an SAP environment.

This note is valid for UNIX / Linux platforms. It cannot be applied forOracle Grid software installation!

NEWS

13 December 2011

o SAP RUNINSTALLER 11.2.0.3 patch level 039 released on SAP DVDs

20 October 2011

o 11.2.0.2 Installation scripts patch level 029 releasedPackage 11ginstall-11202-029-complete.zip contains OPatch11.2.0.1.5 and MOPatch 2.1.11.

05 May 2011

o 11.2.0.2 Installation scripts patch level 028 releasedPackage 11ginstall-11202-028-complete.zip contains OPatch11.2.0.1.3 and MOPatch 2.1.7.

31 March 2011

o Updated description for SAP Bundle Patch installationAdded description for relinking procedure

24 March 2011

o 11.2.0.2 Installation scripts patch level 022 released

Other terms

Oracle Database 11g Release 11.2.0.3Oracle Database 11g Release 11.2.0.2Oracle Database Patch Set

Reason and Prerequisites

11.04.2012 of 14


Installation of Oracle Database 11.2 Patch Sets

Check this note if you plan to upgrade your existing Oracle database to thenewest database patch set release, or if you plan to install a new Oracledatabase with the newest Oracle database patch set release.

Oracle Database 11.2 Patch Sets Are Full Installations

Starting with the first patch set for Oracle Database 11g Release 2(11.2.0.2), Oracle Database patch sets are full installations of theOracle Database software.

In the past (before release 11.2), Oracle Database patch sets consisted ofa set of files that replaced files in an existing Oracle home. Beginningwith Oracle Database 11g Release 2, patch sets are full installations thatreplace existing installations.

For further details and information about full installation patch sets seeMy Oracle Support note 1189783.1.

Oracle Database 11.2 Installation Guides

Oracle Database Installation Guides are available on Oracle TechnologyNetwork http://www.oracle.com/pls/db112/homepage.

Recommendation

It is recommended to back up the Central Inventory before you install,deinstall or clone an Oracle home, or before you attach an Oracle home toor detach an Oracle home from the Central Inventory.

Oracle Software Owner

'ora<dbsid>' for Single Instance on File SystemWhen you install your Oracle database 11.2 software on a Unix/Linuxplatform for single instance (SI) without Oracle Automatic StorageManagement (ASM), then the owner of the database software is'ora<dbsid>:dba'.

'oracle' for RAC and ASM InstallationsWhen you install your Oracle database 11.2 software in a grid environmentwith Oracle Real Application Clusters (RAC) or Oracle Automatic StorageManagement (ASM), then the owner of the software is 'oracle:oinstall'.

11.04.2012 of 14


Notation

The following notation is used in this note:

o <DBNAME>: specifies the name of the database in upper case (derivedfrom database profile parameter 'db_name' or 'db_unique_name')

o <DBSID>: value of $DB_SID like 'QO1' (upper case)When used in a path like '/oracle/<DBSID>', <DBSID> is meant asdatabase name <DBNAME>, not as instance identifier <ORACLE_SID>.

o <dbsid>: value of $DB_SID like 'qo1' (lower case)

o <1120X>: placeholder for a patch set release e.g. '11202'

o <11.2.0.X>: placeholder for a patch set release e.g. '11.2.0.2'

o <IHRDBMS>: Database Software Installation Home. The installationOracle Home directory where the Oracle RDBMS Software is installed.

o <OHRDBMS>: The runtime path of the Oracle Home where the RDBMSSoftware was installed. This is a symbolic link (softlink) to<IHRDBMS>.

o The terms 'symbolic link' and 'softlink' are equivalent.

o To make this documentation easier to read, only the location for64-bit platforms is used. If your database runs on a 32-bitplatform (Linux 32-bit), replace all occurrences of 112_64 with112_32.

Solution

Content Of This Note

1. Installation Scripts2. Procedure to Install a Full Install Patch Set3. Pre-Installation Steps4. Patch Set Software Installation4.1 For a New Installation4.2 For an Existing Installation4.3 Installing an SAP Bundle Patch (SBP)4.4 Procedure for Relinking the Oracle Software

1. SAP RUNINSTALLER Installation Scripts

The SAP-specific installation scripts RUNINSTALLER, RUNINSTALLER_CHECK, and

11.04.2012 of 14


11ginstall.sh are located in directory 'SAP' in the Oracle databasesoftware stage.

o Script RUNINSTALLER

To install the software, run:

OS> ./RUNINSTALLER

To get help, run:

OS> ./RUNINSTALLER -help

To check script version and patch level, run:

OS> ./RUNINSTALLER -version

o Script RUNINSTALLER_CHECK

To perform product specific prerequisite checks, run:

OS> ./RUNINSTALLER_CHECK

o Script 11ginstall.sh

'11ginstall.sh' is the main script behind RUNINSTALLER andRUNINSTALLER_CHECK. It supports interactive and silent modeinstallation, it generates the response file and starts the Oracleinstaller.

For help on 11ginstall.sh, run the command:

OS> /bin/sh 11ginstall.sh -help

SAP RUNINSTALLER Minimum version

For release 11.2.0.3 use installation scripts with patch level 039 (orhigher, if available).

For release 11.2.0.2 use installation scripts with patch level 022 (orhigher, if available).

Installing a newer SAP RUNINSTALLER version

Attached to this note you find zip files of the following namingconvention:

11ginstall_<release>_<patch_level>_<type>.zip

o <release>Oracle database software release e.g. 11202

o <patch_level>Patch level of the installation script.The scripts of the last 2 patch levels are attached.

o <type>

11.04.2012 of 14


- 'complete'This package type contains the installation scripts and currentversions of OPatch and MOPatch. As part of the softwareinstallation these versions get installed into the new Oraclehome.

- 'basic'This package type contains the installation scripts.In order to reduce the number of different packages thispackage type is not available any more.

1. Download the zip file 11ginstall_<release>_<patch_level>_<type>.zip tothe Oracle software stage directory '<stage>/database'.

2. Rename subdirectory SAP (if it exists) and extract the zip file.OS> cd <stage>/databaseOS> mv SAP SAP.pre-<patch_level>OS> unzip 11ginstall_<release>_<patch_level>_<type>.zip

Troubleshooting the Software Installation

In case of installation issues check the following log files and SAP notes:

1. RUNINSTALLER log file / 11ginstall.sh log fileCheck the RUNINSTALLER log file'/oracle/<DBSID>/11ginstall_<release>.log' for warning or errormessages.

2. Oracle Universal Installer (OUI) log fileCheck the OUI installation log file, typically located in/oracle/oraInventory/logs.

3. SAP note 1524205 (=this note)Ensure that you have installed the current version of the installationscripts.

4. SAP note 1431796This note contains solutions and workarounds for known installationproblems.

5. Ensure that all database installation prerequisites are met

a) Run RUNINSTALLER_CHECK

b) Check Oracle Database Installation Guide for your release and yourplatform.

2. Procedure to Install a Full Install Patch Set

As mentioned above, as of Oracle Release 11.2.0.2, the patch set softwareis a full installation package. As a consequence of this change, the way to

11.04.2012 of 14


install this patch set is has changed, too.

"In-Place" Upgrade is not supported

For SAP, installing Oracle patch set software using the "In-place" approachis not supported.

"Out-Of-Place" Upgrade

In SAP environments, database patch sets as of 11.2.0.2 are installedout-of-place into a new Oracle home. In previous releases, patch sets wereinstalled in-place into an already existing Oracle home.

"Installation Oracle Home" vs. "Runtime Oracle Home"

To avoid changes in the environment (PATH, ORACLE_HOME) of the OS users'oracle', ora<dbsid> or <sapsid>adm when upgrading to a new patch setrelease, the following approach is used:

o "Installation Oracle home" <IHRDBMS>

"Installation Oracle home" is the Oracle home path that is usedwhen the Oracle software is installed.

SAP RUNINSTALLER installs the new patch set software into the"Installation Oracle home" <IHRDBMS>.

You use the "installation Oracle home" environment to perform tasksrelated to software administration like installation of thesoftware, installing patches/SBP or relinking the software. Inaddition, DBUA and DBCA run in this environment.

Examples for installation Oracle home <IHRDBMS>:'/oracle/<DBSID>/11203''/oracle/<DBSID>/11202'

o "Runtime Oracle home" <OHRDBMS>

"Runtime Oracle home" is the Oracle home path that is used to runthe instance. This path uses a symbolic link (softlink) named'112_64' (Single instance, non-ASM) and '112' in RAC or ASMenvironments.

The "Runtime Oracle home" environment is used for normal operationto run the instance.

Examples for runtime Oracle home <OHRDBMS>:'/oracle/<DBSID>/112_64': Single instance, non-ASM'/oracle/<DBSID>/112' : ASM or RAC

Advantages of "Out-Of-Place" Upgrades

o With "Out-Of-Place"-Upgrades you can install the new databasesoftware into a new location while the database is still running.

o The use of symbolic links (softlink) allows the runtime environment(PATH, <LIBRARY_PATH>, ORACLE_HOME) to remain unchanged.

11.04.2012 of 14


o As the new patch set software is installed into a new location<IHRDBMS_new>, it does not modify any files of the current Oraclehome <IHRDBMS_current>.

Consequences and Recommendations

o The database instance and other Oracle processes should always bestarted from the runtime Oracle home <OHRDBMS>.

Exception: DBUA or DBCA require the database instance to be startedfrom the installation environment with ORACLE_HOME=<IHRDBMS>.

o When the database instance is running in the runtime environment,you can not connect to the instance at the same time from theinstallation environment (and vice versa). If you try this, you get'connected to an idle instance'.

o Use the "installation Oracle home" environment to perform one ofthe following software management tasks:

- Apply an SAP Bundle Patch with mopatch

- Apply a patch with opatch

- Relink oracle software

3. Pre-Installation Steps

Before you install the new patch set software, you should perform thefollowing steps:

o Ensure that all prerequisites for the database softwareinstallation are met (OS packages, kernel and system parametersetc.).

OS> cd <stage>/SAPOS> ./RUNINSTALLER_CHECK

Instead of 'RUNINSTALLER_CHECK' you can also use the command'RUNINSTALLER -check'.

o Verify the installation settings

OS> cd <stage>/SAPOS> ./RUNINSTALLER -noinstall

4. Patch Set Software Installation

The steps to install the patch set software are slightly differentdepending on whether the software is installed for a new installation or

11.04.2012 of 14


for an existing installation.

Refer to the corresponding section below.

4.1 For a New Installation

1. Logon to the database server as the software owner 'ora<dbsid>' or'oracle'

2. Check installation prerequisites

OS> cd <stage>/database/SAPOS> ./RUNINSTALLER_CHECK

3. Check installation settings

OS> cd <stage>/database/SAPOS> ./RUNINSTALLER -noinstall

Before you install the patch set software, verify that allinstallation settings are correct.

4. Install the Oracle database patch set software

OS> cd <stage>/database/SAPOS> ./RUNINSTALLER

5. Apply current SAP Bundle Patch (SBP)For release 11.2.0.3 see SAP note 1631931.For release 11.2.0.2 see SAP note 1503709.Note that ORACLE_HOME must be set to the "installation Oracle home"<IHRDBMS>.

6. Create symbolic link (softlink) for libnnz10.so manually (if required)

For 11.2.0.3 you can skip this step. SAP RUNINSTALLER 11.2.0.3 createsthis link by default.

Note: This link is only required if you use BR*Tools linked withOracle 10g Client. For BR*Tools 7.20 (PL 15 or higher) that are linkedwith Oracle 11g Client (SAP KERNEL 7.20 EXT), you can skip this step(see SAP note 1449619).

OS> cd $ORACLE_HOME/libOS> ln -s libnnz11.so libnnz10.so

7. Create symbolic link (softlink) for Runtime Oracle home <OHRDBMS>.

For new installations this link is automatically created by theinstallation script (11.2.0.2 patch level 15 and later).

The name of the link <linkname> is '112_64' for Non-ASM (64-bit),'112_32' for Non-ASM (32-bit), '112' for ASM.

11.04.2012 of 14


OS> ln -s 11203 /oracle/<DBSID>/<linkname> #for release 11.2.0.3OS> ln -s 11202 /oracle/<DBSID>/<linkname> #for release 11.2.0.2

4.2 For an Existing Installation

Installing a patch set into an existing database installation consists ofthe following steps:

1. Installation of the new software("Software Upgrade")

2. Upgrading the database to the new release("Database Structure Upgrade")

3. Post-Upgrade Steps

Step 1: Install the software ("Software Upgrade")

1. Logon to the database server as the software owner 'ora<dbsid>' or'oracle'

2. Check installation prerequisites

OS> cd <stage>/database/SAPOS> ./RUNINSTALLER_CHECK

3. Check installation settings

OS> cd <stage>/database/SAPOS> ./RUNINSTALLER -noinstall

Before you install the patch set software, verify that allinstallation settings are correct.

4. Install the Oracle database patch set software

OS> cd <stage>/database/SAPOS> ./RUNINSTALLER

5. Apply current SAP Bundle Patch (SBP)For release 11.2.0.3 see SAP note 1631931.For release 11.2.0.2 see SAP note 1503709.Note that ORACLE_HOME must be set to the "installation Oracle home"<IHRDBMS>.

6. Create symbolic link (softlink) for libnnz10.so manually (if required)

For 11.2.0.3 you can skip this step. SAP RUNINSTALLER 11.2.0.3 creates

11.04.2012 of 14


this link by default.

Note: This link is only required if you use BR*Tools linked withOracle 10g Client. For BR*Tools 7.20 (PL 15 or higher) that are linkedwith Oracle 11g Client (SAP KERNEL 7.20 EXT), you can skip this step(see SAP note 1449619).

OS> cd $ORACLE_HOME/libOS> ln -s libnnz11.so libnnz10.so

7. The next step is to upgrade the database.

Step 2: Upgrade the database ("Database Structure Upgrade")

The following steps to perform the Database Structure Upgrade are based onthe SAP specific upgrade scripts (see SAP note 1431793).

1. Shutdown the SAP system.

2. Logon to the database server with the database administrator accountand open a new shell.

From this shell the following steps are performed.

3. Specify Source and Target Oracle home.Details are described in SAP note 1431793.

dbua.sap.sh requires source and target Oracle homes to be set in theenvironment variables ORACLE_HOME_SRC and ORACLE_HOME_TGT.ORACLE_HOME_TGT must be set to the installation Oraclehome <IHRDBMS>.

- Examples how to specify Source Oracle home

Database Upgrade from release 10.2.0.X:OS> setenv ORACLE_HOME_SRC /oracle/<DBSID>/102_64

Database Upgrade from release 11.2.0.1 or 11.2.0.2OS> setenv ORACLE_HOME_SRC /oracle/<DBSID>/112_64

- Examples how to specify Target Oracle home

Database Upgrade to release 11.2.0.2OS> setenv ORACLE_HOME_TGT /oracle/<DBSID>/11202

Database Upgrade to release 11.2.0.3OS> setenv ORACLE_HOME_TGT /oracle/<DBSID>/11203

4. Goto upgrade scripts directory.Prerequisite: patch 9584028 (current SBP) must be installed (see SAPnote 1431793). If this directory does not exist, the patch is notinstalled.

11.04.2012 of 14


OS> cd $ORACLE_HOME/sap/ora_upgrade/post_upgrade

5. For help on upgrade options, see SAP note 1431793, or run

OS> ./dbua.sap.sh -help

6. First run in query mode to verify that source and target Oracle homeare correct.

OS> ./dbua.sap.sh -query

During this step Oracle Net configuration files tnsnames.ora,listener.ora and sqlnet.ora are copied from source to target Oraclehome.

7. Start the upgrade:Prerequisite: Database is up and running from the source Oracle home.If the database is shutdown, start the instance.

OS> ./dbua.sap.sh [-silent]

Go through DBUA assistant and confirm with 'Next'. At the end, startthe upgrade with 'Finish'.

You can ignore either of the error messages ORA-32006 / ORA-32004reported by DBUA. They are related to the parameter settingremote_os_authent=true which is currently still required for SAP.

8. Stop the database instance (if required)

If you are using upgrade scripts older than May 2011, then this stepis required. Starting May 2011, this step is performed automatically(see SAP note 1431793).

During the database upgrade, the instance is running in theinstallation Oracle home environment. Before you can switch to theruntime Oracle home environment, stop the instance.OS> sqlplus / as sysoperSQL> shutdown immediateSQL> exit

9. When the instance is stopped, exit from this shell.

OS> exit

Step 3: Post-Upgrade Steps

1. Logon to the database server with the database administrator accountand open a new shell.

From this shell the following steps are performed.

2. If the database was upgraded from 10.2 adapt the environment variablesin the .dbenv-scripts (ORACLE_HOME, PATH, <LIBRARY_PATH>) as described

11.04.2012 of 14


in the "SAP Database Upgrade Guide for Oracle Release 11.2". ForORACLE_HOME use runtime Oracle home path <OHRDBMS>, not installationOracle home path <IHRDBMS>.

3. Deinstall the old Oracle home softwware.

For deinstalling Oracle database software of release 11.2, see SAPnote 1525025.

4. Create symbolic link (softlink) for Oracle home runtime location.This step is only required if the symbolic link has not been alreadycreated after/during the installation of the software.

OS> ln -s <release> /oracle/<DBSID>/112_64

Example for release 11.2.0.2:OS> ln -s 11202 /oracle/<DBSID>/112_64

5. Start the instance.

Start instance (and other processes like listener) with the newsoftware from the runtime environment.

4.3 Installing an SAP Bundle Patch (SBP)

The procedure to install an SBP depends on whether you install the SBPonline or offline.

SBP Installation Procedure (OFFLINE)

The installation of an SBP in offline mode basically consists of thefollowing two main steps:

1. Installing the SAP Bundle Patch Software with MOPatchYou perform this step as the software owner from the installationenvironment.

2. Executing Post-Installation InstructionsYou can perform this step either from the installation or from theruntime environment.

It is necessary to execute the post-installation instructions evenwhen a database is created or upgraded after the installation of anSBP.

SBP Installation Procedure (ONLINE)

1. Check that the database instance is running in the runtimeenvironment.

11.04.2012 of 14


2. Follow the instructions from the SBP Readme and install the SBP inonline mode in the runtime environment.

4.4 Procedure for Relinking the Oracle Software

Relinking Oracle software is performed in the installation environment.

1. Logon to the database server as the software owner

2. From a shell with runtime environment:Shut down the instance, the listener, and other processes associatedwith the Oracle Home.

3. Open a new shell

a) Configure the installation environment.

b) Relink the software.

c) Exit from the shell.

4. From a shell with runtime environment:Start up all instances, listeners, and other processes associated withthe Oracle Home.

Appendix

Summary of changes in installation scripts patch level 29- packaged with OPatch 11.2.0.1.5 and MOPatch 2.1.11

Summary of changes in installation scripts patch level 28

- added size check of oracle executable to better detect link errors- dedicated script exit codes for installation success, error, etc.- changed creation of symbolic link (relative instead of full path)- automatic cleanup of files that were temporarily created- several other smaller improvements and changes

Summary of changes in installation scripts patch level 22

- added additional check for successful installation (checking OUI return code is not sufficient)- implemented /oracle/oraInventory as default location for Oracle Inventory (only for first time installations)- new option -oracle_base- improved check for empty target Oracle home- several smaller changes and improvements

11.04.2012 of 14


Header Data

Release Status: Released for CustomerReleased on: 10.02.2012 08:48:00Master Language: EnglishPriority: Recommendations/additional infoCategory: ConsultingPrimary Component: BC-DB-ORA Oracle

Secondary Components:BC-DB-ORA-INS Installation SAP System withOracle

The Note is release-independent

Related Notes

Number Short Text

1554661 Configuration of environment for 'oracle' user

1550133 Oracle Automatic Storage Management (ASM)

1525025 Oracle 11.2.0: Oracle Software Deinstallation

1521371 Oracle 11.2.0: Setting of ORACLE_BASE in SAP environments

1503709 Oracle 11.2.0: Patches / Patch collections for 11.2.0.2

1431799 Oracle 11.2.0: Current Patch Set

1431796 Oracle 11.2.0: Troubleshooting the Software Installation

Attributes

Attribute Value

Database system Oracle 11.2

Attachments

FileType

File Name Language Size

ZIP 11ginstall-11202-028-complete.zip E 1.410 KB



sapnote_0001524205

Documents

cd sap os

cd database sap os

cd oracle home lib os

database software installationos

oracle 10g client

oracle 11g client

database administrator account

target oracle home