Kernel version:

------------------
Oracle 11g is supported only for kernel versions 640_EX2 or higher.
Planning:
========
Hardware requirements:
----------------------------
1. 1024 MB of RAM.
2. 1024 MB of free space in /tmp directory.
3. Swap space about 1.5 times the available memory for memory upto 2 GB.
For memory of 2 GB and above, the amount of swap space should be the same as th
e memory.
4. About 10-15 GB for the Oracle home directory.
3. Preparation:
============
Here we can see all the preparatory steps and Oracle 11g software installation.
1. Check ORACLE_BASE Environemntal variable is created or not.
Software Owner : 'ora<DB SID>'
HOME = /oracle/<DB SID>
ORACLE_BASE=/oracle
ORACLE_HOME=/oracle/<DBSID>/<Release>
Command to be used:
setenv ORACLE_BASE /oracle
check both ORACLE_BASE,ORACLE_HOME Environmental variables are set or not. If no
t set, please set them and update the values in ".cshrc" file.
2. Check ora<DBSID> has write authorization to $ORACLE_BASE directory:
echo $ORACLE_BASE
cd $ORACLE_BASE
touch $ORACLE_BASE/write_test
rm $ORACLE_BASE/write_test
If ora<DBSID> does not have write authoriztion to $ORACLE_BASE,
chgrp dba $ORACLE_BASE
chmod 775 $ORACLE_BASE
3. umask 022
4. Checking the Directory structure:
a) Check the Oracle Stage directory : /oracle/stage. If it does not exists, crea
te it manually.
/oracle/satge/11202
b) The software will contain six or seven SAP files which include the varoius Or
acle 11.2 components such as database,grid,gateways etc.
c) Use the SAP tool SAPCAR to extract all the SAR files to /orcle/stage/11202 wi
th ora<DBSID> user.
ex: SAPCAR xvf OR511264.SAR
After extraction you will find the following sub directories under /oracle/
stage/11202:
 database
client
grid
examples
gateways
deinstall
Note:
For a single-instance database upgrade, you only need to extract the database so
ftware. The database components are packed in the files OR111264.SAR and OR21126
4.SAR. If you only use a single instance database, these 2 SAR files alone are s
ufficient. In this case, you do not need to extract any other SAR files.
d) Check the Oracle Inventory Directory:
The Oracle inventory directory maintains the inventory of all Oracle software in
stalled on the system.
Path of Oracle Inventory directory is maintained in "oraInst.loc" file (/var/opt
/oracle for solaris)
e) Before starting the installation of the new Oracle software on the database h
ost, make sure that the file "oraInst.loc" is present in either the directory /e
tc (AIX) or directory /var/opt/oracle (Solaris) and check that it has the follow
ing entries:
inventory_loc=<location of the oracle inventory>
inst_group=dba
Note:
If the Oracle Universal Installer has already been run on this host, make sure t
hat the variable inventory_loc in the file oraInst.loc points to the location wh
ere the Oracle inventory is located. If this is the first time that the OUI has
been executed on this host, enter the location where you want the inventory log
files to be written to.
By default in Oracle 11.2, the inventory is created in /oracle/oraInventory.
If this is the first installation of Oracle database software on the host and th
e oraInst.loc file does not exist, you must create it at the end of the installa
tion by running the orainstRoot.sh script as super user from the <oraInventory>
location.
5. Updating the Oracle Installation Scripts:
The SAP Specific installation scripts RUNINSTALLER, RUNINSTALLER_CHECK, and 11gi
nstall.sh are located in directory SAP in the Oracle database software stage:
./RUNINSTALLER
./RUNINSTALLER -help
./RUNINSTALLER_CHECK (This script performs product specific prerequisite checks)
11ginstall.sh
6. Checking the prerequisites for the Oracle Universal Installer:
--> Set the environmental variable DISPALY: setenv DISPLAY 192.168.10.2:0.0
--> Login as ora<DBSID> user
--> cd /oracle/stage/11202/database/
--> ./runInstaller -executeSysPrereqs (Checking the prerequisites for the OUI)
--> cd SAP
--> ./RUNINSTALLER -CHECK (Checking Operating system requirements like release,p
atch,kernel parameters)
--> If the OUI still complains of missing patches or OS kernel parameters, you n
eed to apply these before you can proceed with the software installation.
7. Database Software Installation:
You can install the Database software while SAP system is running with existing
database (that is Oracle 10.2)
a) Checking and seting Environmental Variables: for user ora<DB SID>
Note:
The below environmental variables are applicable only for the duration of this s
ession only. Do not make the changes to the environment permanently while old da
tabase is still running.
DISPLAY -- setenv DISPLAY 192.168.10.2:0.0
ORACLE_BASE -- setenv ORACLE_BASE /oracle
ORACLE_SID -- setenv ORACLE_SID PSM
ORACLE_HOME -- setenv /ORACLE/<DB SID>/102_64
SAPDATA_HOME -- setenv /ORACLE/<DBSID>
ORACLE_HOME_SRC -- setenv ORACLE_HOME_SRC /oracle/<DBSID>/102_64
ORACLE_HOME_TGT -- setenv ORACLE_HOME_TGT /oracle/<DB SID>/11202
b) Start your X-Manager
c) Set the environmental variable for the library path:
LD_LIBRAY_PATH -- setenv $ORACLE_HOME/lib:$LD_LIBRARY_PATH
d) Include $ORACLE_HOME/bin in your PATH or path variable, where $ORACLE_HOME is
the variable that you set in the above step.
Note:
Make sure there is only one $ORACLE_HOME/bin in your PATH or path variable. Make
sure that the path variable does not contain the old $ORACLE_HOME/bin from the
source database.
e) Make sure you have atlease 1024 MB in /tmp directory.
f) Backing up the Central Oracle Inventory:
-->Check the oracle inventory file in tha below path: /var/opt/oracle/oraInst.lo
c
--> inventory_loc=<path to oracle inventory>
--> Make a backup of your existing oracle inventory before you start the Oracle
Database 11g Release software installation.
g) Installing the Oracle Database Software:

--> login as ora<dbsid>

--> setenv DISPLAY 192.168.10.2:0.0
--> cd /oracle/stage/11202/database/SAP
-->./RUNINSTALLER
--> Respond to the OUI as per upgrade guide
--> Exit and confirm the dialog box that appears
8. Installing the Required SAP Bundle Patch:
For installing the MOPATCH refer the SAP note: 1027012.

9. Copying and Adapting the SQL* Net Files:

After the database software installation, you must copy and modify the old SQL*N
et files, that is, listener.ora, sqlnet.ora, and tnsnames.ora.
--> Logon as ora<dbsid>
--> Copy the SQL* Net Parameter files from <old_ORACLE_HOME>/network/admin to <n
ew_ORACLE_HOME>/network/admin
--> Edit the new SQL*Net files by adapting all file paths for the new directory.
Be sure to adapt the value of ORACLE_HOME in the listener.ora file.
--> Add the following entry to the file listener.ora:
--> ADR_BASE_LISTENER = /oracle/DBSID/saptrace
Note:
Since your database is still running in the old environment, do not start the li
stener with the new listener.ora file at this point.
10. Running Pre Upgrade Scripts:
a)Installing Pre Upgrade scripts:
The current version of the upgrade scripts is automatically installed if the cur
rent SAP Bundle Patch is installed. No further installation is required.
To install a newer version with mopatch, download the patch and run the followin
g command:
-->$ORACLE_HOME/MOPatch/mopatch.sh -s \p9584028_112020_Generic.zip