1. As only the Oracle Kernel is not installed and the DB is not yet created,
should I perform everything that is documented in the SAP Bundle Patch
documentation except running the sql scripts?
Yes. You can perform the MOPatch on your newly installed DB. it is not mandatory that DB has to be created before applying MOPatch.
2.In the past, I stored my bundle patches in /oracle/stage/bundle.
After reading current Oracle 11.2.0.3.5 SAP Bundle Patch doc,
they specifiy /oracle/SID/11203/sapbundle.
No idea.. But you can download the latest DB MOPatch from service.sap.com/swdc -> database patches -> oracle 11.2.0.3 -> Select your OS version and select the MOPatch you want to download.
2. Has SAP changed its conventions?
No Idea
Steps to do as follows
2.1 Executing Pre-Installation Instructions
Unless otherwise stated, you can execute the following pre-installation instructions before you shut down the applications or the database instances.
Download file SAP_112035_201302_LINUX.zip (this SBP) to the database host.
If required, update the OPatch and MOPatch utilities to OPatch version 11.2.0.3.1 and MOPatch version 2.1.13 (see also section 1.4, "OPatch and MOPatch Utility Information").
Extract OPatch and MOPatch and install them in the Oracle Home:
unzip -qd $IHRDBMS/sapbundle SAP_112035_201302_LINUX.zip 'SBP_112035_201302/OPatch/*'
mv $IHRDBMS/OPatch $IHRDBMS/OPatch-pre-SBP_112035_201302
mv $IHRDBMS/sapbundle/SBP_112035_201302/OPatch $IHRDBMS/OPatch
unzip -qd $IHRDBMS/sapbundle SAP_112035_201302_LINUX.zip 'SBP_112035_201302/MOPatch/*'
test -d $IHRDBMS/MOPatch && mv $IHRDBMS/MOPatch $IHRDBMS/MOPatch-pre-SBP_112035_201302
mv $IHRDBMS/sapbundle/SBP_112035_201302/MOPatch $IHRDBMS/MOPatch
2.2 Installing the SAP Bundle Patch
Follow the steps below.
Stop all database applications, in particular all SAP applications.
Shut down the database instances, the listeners, and other processes associated with the Oracle Home.
After having shut down all database processes as described in the previous step, use the fuser OS command to check for stale SQL*Plus sessions:
$SBPFUSER $OHRDBMS/bin/oracle
If that command reports running processes, these are stale SQL*Plus sessions, which you can safely terminate with the kill command.
Install the SAP Bundle Patch as follows:
env ORACLE_HOME=$IHRDBMS $IHRDBMS/MOPatch/mopatch.sh -v -s SAP_112035_201302_LINUX.zip
Check the generated MOPatch report for errors or unresolved conflicts. To resolve them, refer to section 4, "Known Issues" and to section "Resolving Patch Conflicts and Errors" of SAP Note 1027012 MOPatch - Install Multiple Oracle Patches in One Run.
Start up the database instances, the listeners, and other processes associated with the Oracle Home.
For each database instance running from the Oracle home*, connect to the database instance as SYSDBA using SQL*Plus and run the post-installation script catsbp.sql:
$ cd $OHRDBMS/rdbms/admin
$ env ORACLE_HOME=$OHRDBMS $OHRDBMS/bin/sqlplus / as sysdba
SQL> @?/sapbundle/SBP_112035_201302/catsbp.sql
SQL> quit
The script evaluates the log files generated by all intermediate steps for unkown errors. If it detects such errors, refer to the log files for more information, resolve the errors and, depending on the error cause, re-start the script. The script may furthermore perform some checks on whether additional post-installation actions are required depending on the state of the database.
To avoid an extra shutdown-startup cycle of the database instance, you should implement any system parameter changes (for example, additions of events and fix controls) from section 2.3, "Executing Post-Installation Instructions" in the above step as well.
Start all database applications, in particular all SAP applications.
2.3 Executing Post-Installation Instructions
Follow the instructions listed below after installation of this SAP Bundle Patch. Except when otherwise stated, execute the instructions after starting the database instances.
Patch 16095398 (CBO Merge Patch), added in SBP 11.2.0.3.5 201302
Please use the following statements to adjust your _fix_control and event
settings in your spfile according to SAP note 1431798 with the new SBP:
ALTER SYSTEM SET "_FIX_CONTROL"=
'5099019:ON','5705630:ON','6055658:OFF','6399597:ON','6430500:ON','6440977:ON',
'6626018:ON','6972291:ON','7168184:OFF','8937971:ON','9196440:ON','9495669:ON','13077335:ON',
'13627489:ON','14255600:OFF','14595273:ON'
COMMENT='SAP_112035_201302 RECOMMENDED SETTINGS'
SCOPE=SPFILE;
ALTER SYSTEM SET EVENT=
'10027',
'10028',
'10142',
'10183',
'10191',
'10443',
'10995 level 2',
'31991',
'38068 level 100',
'38085',
'38087',
'44951 level 1024'
COMMENT='SAP_112035_201302 RECOMMENDED SETTINGS'
SCOPE=SPFILE;
Please restart the database after you have adjusted these parameters.
Patch 14264364, added in SBP 11.2.0.3.3 201209
For Database Vault systems, if Database Vault is already installed,
run the following script (for RAC systems, run the script on one of the nodes):
--- Remark:
SYS still has to be enabled to apply patches:
sqlplus secadmin @?/sap/ora_dbvault/dv_policy patch status
If not still enabled, run:
sqlplus secadmin @?/sap/ora_dbvault/dv_policy patch enable
------------
Reload the Database Vault scripts as SYSDBA
sqlplus / as SYSDBA
SQL> @?/rdbms/admin/catmacpatch.sql
Run the following command as SYSDBA
sqlplus / as SYSDBA
SQL> @?/rdbms/admin/utlrp.sql
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.