Upgrading SAP Oracle 11g after fresh installation of SAP ECC 6.

0 EHP 4 on Oracle
10.2.0.4

1. For Upgrading the Oracle 11g, Minimum requirement should be Oracle

10.2.0.5
2. First we need to apply the Patch set of Oracle 10.2.0.5 and SAP Bundle Patch
For Oracle-10.2.0.5.12
For Oracle-10.2.0.5.11

2013-08
2013-05

SAP10205P_1308
SAP10205P_1305

3. Download the Latest MO patch Version 2.1.4 if not already installed in your
systems and 2.1.9 or later for Oracle 11g
a. Installing MO Patch
1. Log on to the database server as OS user ora<dbsid>
2. Download the file mopatch-<version>.zip attached to this note and
unpack it into the Oracle Home, for example, with the command:
3. unzip -d $ORACLE_HOME mopatch-<version>.zip
This creates the directory $ORACLE_HOME/MOPatch with the following
contents:
readme.txt - MOPatch documentation. Identical to this note except
for minor changes.
mopatch.sh - MOPatch utility
mpkill.sh - MOPatch kill utility
4. Downloading related SAP Bundle Patches: Download the latest SAP Bundle
Patch appropriate for your database version and your platform, either with
the SAP Download Manager or directly by selecting the SAP Bundle Patch link.
Downloading Multiple Single Patches
You must download both the generic and platform-specific Oracle database
patches appropriate for your database version and your platform.
1. Select all generic and platform-specific patches that you want to download.
Select the check boxes next to all items with title matching either of the
following patterns:
pNNNNNN_VVVVV_<PLATFORM_NAME>.zip
pNNNNNN_VVVVV_GENERIC.zip
You can easily do this by first selecting all check boxes with the "Select All"
button and then deselecting those that do not match.
Make sure that you only select items that have a title matching the patterns
mentioned above. Do not select any items where the version-part "VVVVV" of
the title does not match your database version.

2. Select the "Add to Download Basket" button. In the upcoming pop-up

window, select the "Close" button.
3. Start the SAP Download Manager.
If you have not yet installed the SAP Download Manager, you can download it
from
https://service.sap.com/swdc
-> Download Basket
-> Get Download Manager
4. Start the download from the menu bar of the SAP Download Manager:
Object -> Download all objects
Wait for the download to complete.
5. Executing MOPatch in Documentation Mode to Generate Documentation
1. Log on to the database server as OS user ora<dbsid>.
2. Change to the patch base directory and run MOPatch in documentation
mode:
$ cd <patch_base_dir>
$ /bin/sh $ORACLE_HOME/MOPatch/mopatch.sh \ -v -d -s patch-sourcepath
3. Review the execution summary printed by MOPatch. In the event of errors,
see the MOPatch log files in directory
$ORACLE_HOME/cfgtoollogs/mopatch for more details.
4. Review the README files generated in the patch base directory. Pay extra
attention to README files of patches that are marked specially in the
execution summary printed by MOPatch, since these may contain special
installation instructions.
6. Executing MOPatch to Install the Patches
1. Log on to the database server as OS user ora<dbsid>.
2. Make sure that all prerequisites for successfully running OPatch are met,
especially the following:
a. Environment variable ORACLE_HOME must be set.
b. There must be no processes running from the Oracle Home. Make
specially sure that the database instance is shut down and that the
Oracle Listener is stopped.
c. (AIX platforms only) The command slibclean must have been executed
by the super user.
3. Execute all patch-specific pre-install instructions. The stripped README
files generated by MOPatch in documentation mode provide a concise
overview of these.
4. Change to the patch base directory and run MOPatch:
$ cd <patch_base_dir>
$ /bin/sh $ORACLE_HOME/MOPatch/mopatch.sh \ -v -s patch-source-path
5. Execute all patch-specific post-install instructions. The stripped README
files generated by MOPatch in documentation mode provide a concise
overview of these.
7. Reviewing MOPatch Execution Summary and Log Files

1. Review the execution summary that MOPatch prints after it has processed
all patches.
2. In the event of patch conflicts or errors, see the MOPatch log files in
directory $ORACLE_HOME/cfgtoollogs/mopatch for more details. Follow the
instructions in section "Resolving Patch Conflicts and Errors" of this note to
resolve the issues.
8. /bin/sh $ORACLE_HOME/MOPatch/mopatch.sh -h
9.