| Asset ID: |
1-71-1456141.1 |
| Update Date: | 2012-08-23 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1456141.1
:
ODA (Oracle Database Appliance): HowTo apply DB patches manually
| Related Items |
- Oracle Database Appliance
|
| Related Categories |
- PLA-Support>Database Technology>Engineered Systems>Oracle Database Appliance>DB: ODA_EST
|
In this Document
Applies to:
Oracle Database Appliance - Version Not Applicable and later
Information in this document applies to any platform.
Goal
The aim of this article is to show how a needed Oracle RDBMS fix can be applied on a ODA (Oracle Database Appliance) database
Fix
A Database running on ODA (Oracle Database Appliance) is not different from other Oracle RDBMS. The manual steps executed on installing a fix or/and a PSU on a "generic" database can be used on ODA as well.
In order to manually apply DB patches you must have ODA GI (Grid Infrastructure) upgraded to 11.2.0.3.2 or above
The steps you should follow are depending on the fix/PSU then check always the related REAMDE file. Here I'm documenting, as examples, the steps needed in order to install the "DB PSU6 (11.2.0.2.6)" on top of the existing RDBMS 11.2.0.2.5. You can use the same method to apply future DB PSU, ie PSU7 (11.2.0.2.7). We are also providing the example for applying "Exadata 11.2.0.3 BP5" on top of the existing RDBMS 11.2.0.3.2. You can use the same method to apply Exadata 11.2.0.3 BP6 on top of existing RDBMS 11.2.0.3.2. Please note that this is only for the customers do not have additional Exadata test machine and would like to leverage ODA to test the rdbms patches.
How to install DB PSU6 (11.2.0.2.6) on top of the existing ODA(2.2.0.0.0) RDBMS 11.2.0.2.5
On this scenario you have upgraded the GI to 11.2.0.3.2 and you had the need to apply DB PSU6
1. Set up the PATH env variable to pickup the 'new' OPatch bundle with GI 11.2.0.3.2
export PATH=$PATH:/u01/app/11.2.0.3/grid/OPatch
2. Check if you are running the right OPatch binary version
$ opatch version
OPatch Version: 11.2.0.3.0
OPatch succeeded.
3. Check the fix installed on your DB_Home 11.2.0.2.5
$ opatch lsinventory -detail -oh /u01/app/oracle/product/11.2.0/dbhome_1 | grep ^Patch
Patch 13343424 : applied on Tue Jan 03 17:11:54 PST 2012
Patch description: "Database Patch Set Update : 11.2.0.2.5 (13343424)"
Patch 13343447 : applied on Tue Jan 03 17:04:16 PST 2012
Patch description: "Grid Infrastructure Patch Set Update : 11.2.0.2.5 (13343447) "
4. Download/move and unzip the DB PSU6 (11.2.0.2.6) patch:13696224 on your ODA cloudfs (or in case on both nodes). The usage of ACFS is usefull because the same files are visible from both nodes.
5. Check for any conflicts between the DB PSU and any existing PSE/PSU
$ opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./13696224
Oracle Interim Patch Installer version 11.2.0.3.0
Copyright (c) 2012, Oracle Corporation. All rights reserved.
PREREQ session
Oracle Home : /u01/app/oracle/product/11.2.0/dbhome_1
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/11.2.0/dbhome_1/oraInst.loc
OPatch version : 11.2.0.3.0
OUI version : 11.2.0.2.0
Log file location : /u01/app/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/opatch2012-05-07_11-47-40AM_1.log
Invoking prereq "checkconflictagainstohwithdetail"
Prereq "checkConflictAgainstOHWithDetail" passed.
OPatch succeeded.
6. To run in silent mode, OPatch requires a response file for Oracle Configuration Manager (OCM).
Run $ORACLE_HOME/OPatch/ocm/bin/emocmrsp to generate an OCM response file.
$ /u01/app/11.2.0.3/grid/OPatch/ocm/bin/emocmrsp
7. Set ORACLE_UNQNAME env variable name to your database name
ie: export ORACLE_UNQNAME=RACVS
8. Stop the EM(Enterprise Manager) DBConsole
emctl stop dbconsole
9. As the PSU can be applyed in rolling way stop the instance on node 1
srvctl stop instance -d RACVS -i RACVS1
10. Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:
cd 13696224
opatch apply
the patch will be applied on node1 and at the end it will ask to shutdown the instance on node 2. At this time you can startup the instance on node 1 doing:
srvctl start instance -d RACVS -i RACVS1
and stop the instance on the node 2:
srvctl stop instance -d RACVS -i RACVS2
you can now continue on opatch apply above. At the end of opatch apply you can startup the instance on node2:
srvctl start instance -d RACVS -i RACVS2
11. Loading Modified SQL Files into the Database
The following steps load modified SQL files into the database. For a RAC environment, perform these steps on only one node.
cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @catbundle.sql psu apply
SQL> QUIT
12. Check if your Oracle Inventory is reflecting the PSU installation issuing:
$ opatch lsinventory -detail -oh /u01/app/oracle/product/11.2.0/dbhome_1 | grep ^Patch
or/and using oakcli command:
# oakcli show version -detail
Reading the metadata. It takes a while...
System Version Component Name Installed Version Supported Version
-------------- --------------- ------------------ -----------------
2.2.0.0.0
Controller 05.00.29.00 Up-to-date
Expander 0342 Up-to-date
SSD_SHARED E125 Up-to-date
HDD_LOCAL SA03 Up-to-date
HDD_SHARED 0A25 Up-to-date
ILOM 3.0.14.13.a r70764 Up-to-date
BIOS 12010304 Up-to-date
IPMI 1.8.10.4 Up-to-date
HMP 2.2.0 Up-to-date
OAK 2.2.0.0.0 Up-to-date
OEL 5.8 Up-to-date
GI_HOME 11.2.0.3.2(13696216, Up-to-date
13696251)
DB_HOME {
[ dbhome11203 ] 11.2.0.3.2(13696216, Up-to-date
13696251)
[ RAC ] 11.2.0.2.6(13696224, 11.2.0.3.2(13696216,
13343447) 13696251)
}
ASR Unknown 3.7
13. Verify the PSU Post Install steps were run in the DB
select substr(action_time,1,30) action_time,
substr(id,1,10) id,
substr(action,1,10) action,
substr(version,1,8) version,
substr(BUNDLE_SERIES,1,6) bundle,
substr(comments,1,20) comments
from registry$history;
ie:
ACTION_TIME ID ACTION VERSION BUNDLE
------------------------------ ---------- ---------- -------- ------
COMMENTS
--------------------
07-MAY-12 11.28.59.344085 AM 5 APPLY 11.2.0.2 PSU
PSU 11.2.0.2.5
07-MAY-12 12.44.18.866383 PM 6 APPLY 11.2.0.2 PSU
PSU 11.2.0.2.6
How to install Exadata 11.2.0.3 BP5 or higher on top of the existing ODA(2.2.0.0.0) RDBMS 11.2.0.3
On this scenario you have upgraded the GI to 11.2.0.3.2 and you have installed the DB_Home 11.2.0.3.2.
1. Set up the PATH env variable to pickup the 'new' OPatch bundle with GI 11.2.0.3.2
export PATH=$PATH:/u01/app/11.2.0.3/grid/OPatch
2. Check if you are running the right OPatch binary version
$ opatch version
OPatch Version: 11.2.0.3.0
OPatch succeeded.
3. Check the fix installed on your DB_Home 11.2.0.3.2
Patch 13696216 : applied on Fri Apr 06 20:16:57 PDT 2012
Patch description: "Database Patch Set Update : 11.2.0.3.2 (13696216)"
Patch 13696251 : applied on Fri Apr 06 20:14:59 PDT 2012
Patch description: "Grid Infrastructure Patch Set Update : 11.2.0.3.2 (13696251)"
4. Download/move and unzip the quarterly database patch for exadata (apr 2012 - 11.2.0.3.5) patch:13734832 on your ODA cloudfs (or in case on both nodes). The usage of ACFS is usefull because the same files are visible from both nodes.
5. Check for any conflicts between the DB PSU and any existing PSE/PSU
$ opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./13734832
Oracle Interim Patch Installer version 11.2.0.3.0
Copyright (c) 2012, Oracle Corporation. All rights reserved.
PREREQ session
Oracle Home : /u01/app/oracle/product/11.2.0.3/dbhome_1
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/11.2.0.3/dbhome_1/oraInst.loc
OPatch version : 11.2.0.3.0
OUI version : 11.2.0.3.0
Log file location : /u01/app/oracle/product/11.2.0.3/dbhome_1/cfgtoollogs/opatch/opatch2012-05-14_09-11-58AM_1.log
Invoking prereq "checkconflictagainstohwithdetail"
Prereq "checkConflictAgainstOHWithDetail" passed.
6. To run in silent mode, OPatch requires a response file for Oracle Configuration Manager (OCM).
Run $ORACLE_HOME/OPatch/ocm/bin/emocmrsp to generate an OCM response file.
$ /u01/app/11.2.0.3/grid/OPatch/ocm/bin/emocmrsp
7. Set ORACLE_UNQNAME env variable name to your database name
ie: export ORACLE_UNQNAME=RACVS
8. Stop the EM(Enterprise Manager) DBConsole
emctl stop dbconsole
ie:
$ emctl stop dbconsole
Oracle Enterprise Manager 11g Database Control Release 11.2.0.3.0
Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.
https://rc-voda1.it.oracle.com:1158/em/console/aboutApplication
Stopping Oracle Enterprise Manager 11g Database Control ...
... Stopped.
9. Stop all the databases
srvctl stop database -d <database_name>; ...
ie:
srvctl stop database -d rac05; srvctl stop database -d oltpa
10. Execute on both nodes the prepatch.sh script
cd <Exadata_BP5 location_path>/13734832/13696251/custom/server/13696251/custom/scripts
./prepatch.sh -dbhome /u01/app/oracle/product/11.2.0.3/dbhome_1
ie:
$ cd /cloudfs/13734832/13696251/custom/server/13696251/custom/scripts
$ ./prepatch.sh -dbhome /u01/app/oracle/product/11.2.0.3/dbhome_1
11. Apply the patch
cd <Exadata_BP5 location_path>/13734832/13734832
opatch apply
ie:
$ cd /cloudfs/13734832/13734832
$ opatch apply
Oracle Interim Patch Installer version 11.2.0.3.0
Copyright (c) 2012, Oracle Corporation. All rights reserved.
Oracle Home : /u01/app/oracle/product/11.2.0.3/dbhome_1
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/11.2.0.3/dbhome_1/oraInst.loc
OPatch version : 11.2.0.3.0
OUI version : 11.2.0.3.0
Log file location : /u01/app/oracle/product/11.2.0.3/dbhome_1/cfgtoollogs/opatch/13734832_May_14_2012_09_23_42/apply2012-05-14_09-23-42AM_1.log
Applying interim patch '13734832' to OH '/u01/app/oracle/product/11.2.0.3/dbhome_1'
Verifying environment and performing prerequisite checks...
Interim patch 13734832 is a superset of the patch(es) [ 13696216 13343438 ] in the Oracle Home
OPatch will roll back the subset patches and apply the given patch.
All checks passed.
Provide your email address to be informed of security issues, install and
initiate Oracle Configuration Manager. Easier for you if you use your My
Oracle Support Email address/User Name.
Visit http://www.oracle.com/support/policies.html for details.
Email address/User Name:
You have not provided an email address for notification of security issues.
Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: y
This node is part of an Oracle Real Application Cluster.
Remote nodes: 'rc-voda2'
Local node: 'rc-voda1'
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/u01/app/oracle/product/11.2.0.3/dbhome_1')
Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files...
Rolling back interim patch '13696216' from OH '/u01/app/oracle/product/11.2.0.3/dbhome_1'
Patching component oracle.rdbms.rsf, 11.2.0.3.0...
Patching component oracle.rdbms, 11.2.0.3.0...
Patching component oracle.sdo.locator, 11.2.0.3.0...
Patching component oracle.sysman.console.db, 11.2.0.3.0...
Updating jar file "/u01/app/oracle/product/11.2.0.3/dbhome_1/sysman/jlib/emCORE.jar" with "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13696216_Apr_3_2012_22_02_51/files//sysman/jlib/emCORE.jar/oracle/sysman/eml/ecm/sc/Operator$BuiltInIds.class"
Updating jar file "/u01/app/oracle/product/11.2.0.3/dbhome_1/sysman/jlib/emCORE.jar" with "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13696216_Apr_3_2012_22_02_51/files//sysman/jlib/emCORE.jar/oracle/sysman/eml/ecm/sc/Operator$TokenSeparatorWords.class"
Updating jar file "/u01/app/oracle/product/11.2.0.3/dbhome_1/sysman/jlib/emCORE.jar" with "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13696216_Apr_3_2012_22_02_51/files//sysman/jlib/emCORE.jar/oracle/sysman/eml/ecm/sc/Operator$Parameters.class"
Updating jar file "/u01/app/oracle/product/11.2.0.3/dbhome_1/sysman/jlib/emCORE.jar" with "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13696216_Apr_3_2012_22_02_51/files//sysman/jlib/emCORE.jar/oracle/sysman/eml/ecm/sc/Operator$Tokenizations.class"
Updating jar file "/u01/app/oracle/product/11.2.0.3/dbhome_1/sysman/jlib/emDB.jar" with "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13696216_Apr_3_2012_22_02_51/files//sysman/jlib/emDB.jar/oracle/sysman/db/adm/schm/GrantObjPrivsController.class"
Updating jar file "/u01/app/oracle/product/11.2.0.3/dbhome_1/sysman/jlib/emDB.jar" with "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13696216_Apr_3_2012_22_02_51/files//sysman/jlib/emDB.jar/oracle/sysman/db/adm/DBController.class"
Patching component oracle.sysman.oms.core, 10.2.0.4.4...
RollbackSession removing interim patch '13696216' from inventory
Rolling back interim patch '13343438' from OH '/u01/app/oracle/product/11.2.0.3/dbhome_1'
Patching component oracle.rdbms.rsf, 11.2.0.3.0...
Patching component oracle.rdbms, 11.2.0.3.0...
Patching component oracle.rdbms.dbscripts, 11.2.0.3.0...
RollbackSession removing interim patch '13343438' from inventory
OPatch back to application of the patch '13734832' after auto-rollback.
Patching component oracle.rdbms.rsf, 11.2.0.3.0...
Patching component oracle.rdbms.util, 11.2.0.3.0...
Patching component oracle.rdbms.dbscripts, 11.2.0.3.0...
Patching component oracle.rdbms.deconfig, 11.2.0.3.0...
Patching component oracle.sdo.locator, 11.2.0.3.0...
Patching component oracle.sysman.console.db, 11.2.0.3.0...
Patching component oracle.sysman.oms.core, 10.2.0.4.4...
Patching component oracle.rdbms, 11.2.0.3.0...
Verifying the update...
The local system has been patched. You can restart Oracle instances on it.
Patching in rolling mode.
The node 'rc-voda2' will be patched next.
Please shutdown Oracle instances running out of this ORACLE_HOME on 'rc-voda2'.
(Oracle Home = '/u01/app/oracle/product/11.2.0.3/dbhome_1')
Is the node ready for patching? [y|n]
y
User Responded with: Y
Updating nodes 'rc-voda2'
Apply-related files are:
FP = "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13734832_Apr_3_2012_21_06_06/rac/copy_files.txt"
DP = "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13734832_Apr_3_2012_21_06_06/rac/copy_dirs.txt"
MP = "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13734832_Apr_3_2012_21_06_06/rac/make_cmds.txt"
RC = "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13734832_Apr_3_2012_21_06_06/rac/remote_cmds.txt"
Auto-Rollback-related files are:
FR = "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13734832_Apr_3_2012_21_06_06/rac/remove_files.txt"
DR = "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13734832_Apr_3_2012_21_06_06/rac/remove_dirs.txt"
Instantiating the file "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13734832_Apr_3_2012_21_06_06/rac/remove_files.txt.instantiated" by replacing $ORACLE_HOME in "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13734832_Apr_3_2012_21_06_06/rac/remove_files.txt" with actual path.
Removing files on remote nodes...
Instantiating the file "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13734832_Apr_3_2012_21_06_06/rac/remove_dirs.txt.instantiated" by replacing $ORACLE_HOME in "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13734832_Apr_3_2012_21_06_06/rac/remove_dirs.txt" with actual path.
Removing directories on remote nodes...
Instantiating the file "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13734832_Apr_3_2012_21_06_06/rac/copy_files.txt.instantiated" by replacing $ORACLE_HOME in "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13734832_Apr_3_2012_21_06_06/rac/copy_files.txt" with actual path.
Propagating files to remote nodes...
Instantiating the file "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13734832_Apr_3_2012_21_06_06/rac/copy_dirs.txt.instantiated" by replacing $ORACLE_HOME in "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13734832_Apr_3_2012_21_06_06/rac/copy_dirs.txt" with actual path.
Propagating directories to remote nodes...
Instantiating the file "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13734832_Apr_3_2012_21_06_06/rac/make_cmds.txt.instantiated" by replacing $ORACLE_HOME in "/u01/app/oracle/product/11.2.0.3/dbhome_1/.patch_storage/13734832_Apr_3_2012_21_06_06/rac/make_cmds.txt" with actual path.
Running command on remote node 'rc-voda2':
cd /u01/app/oracle/product/11.2.0.3/dbhome_1/network/lib; /usr/bin/make -f ins_net_client.mk client_sharedlib ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1 || echo REMOTE_MAKE_FAILED::>&2
Running command on remote node 'rc-voda2':
cd /u01/app/oracle/product/11.2.0.3/dbhome_1/rdbms/lib; /usr/bin/make -f ins_rdbms.mk iextproc ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1 || echo REMOTE_MAKE_FAILED::>&2
Running command on remote node 'rc-voda2':
cd /u01/app/oracle/product/11.2.0.3/dbhome_1/rdbms/lib; /usr/bin/make -f ins_rdbms.mk client_sharedlib ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1 || echo REMOTE_MAKE_FAILED::>&2
Running command on remote node 'rc-voda2':
cd /u01/app/oracle/product/11.2.0.3/dbhome_1/rdbms/lib; /usr/bin/make -f ins_rdbms.mk ipc_relink ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1 || echo REMOTE_MAKE_FAILED::>&2
Running command on remote node 'rc-voda2':
cd /u01/app/oracle/product/11.2.0.3/dbhome_1/rdbms/lib; /usr/bin/make -f ins_rdbms.mk inid ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1 || echo REMOTE_MAKE_FAILED::>&2
Running command on remote node 'rc-voda2':
cd /u01/app/oracle/product/11.2.0.3/dbhome_1/rdbms/lib; /usr/bin/make -f ins_rdbms.mk ioracle ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1 || echo REMOTE_MAKE_FAILED::>&2
Running command on remote node 'rc-voda2':
cd /u01/app/oracle/product/11.2.0.3/dbhome_1/rdbms/lib; /usr/bin/make -f ins_rdbms.mk irenamedg ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1 || echo REMOTE_MAKE_FAILED::>&2
The node 'rc-voda2' has been patched. You can restart Oracle instances on it.
There were relinks on remote nodes. Remember to check the binary size and timestamp on the nodes 'rc-voda2' .
The following make commands were invoked on remote nodes:
'cd /u01/app/oracle/product/11.2.0.3/dbhome_1/network/lib; /usr/bin/make -f ins_net_client.mk client_sharedlib ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1
cd /u01/app/oracle/product/11.2.0.3/dbhome_1/rdbms/lib; /usr/bin/make -f ins_rdbms.mk iextproc ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1
cd /u01/app/oracle/product/11.2.0.3/dbhome_1/rdbms/lib; /usr/bin/make -f ins_rdbms.mk client_sharedlib ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1
cd /u01/app/oracle/product/11.2.0.3/dbhome_1/rdbms/lib; /usr/bin/make -f ins_rdbms.mk ipc_relink ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1
cd /u01/app/oracle/product/11.2.0.3/dbhome_1/rdbms/lib; /usr/bin/make -f ins_rdbms.mk inid ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1
cd /u01/app/oracle/product/11.2.0.3/dbhome_1/rdbms/lib; /usr/bin/make -f ins_rdbms.mk ioracle ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1
'
Patch 13734832 successfully applied
Log file location: /u01/app/oracle/product/11.2.0.3/dbhome_1/cfgtoollogs/opatch/13734832_May_14_2012_09_23_42/apply2012-05-14_09-23-42AM_1.log
OPatch succeeded.
12. Execute on both nodes the postpatch.sh script
cd <Exadata_BP5 location_path>/13734832/13696251/custom/server/13696251/custom/scripts
./postpatch.sh -dbhome /u01/app/oracle/product/11.2.0.3/dbhome_1
ie:
$ cd /cloudfs/13734832/13696251/custom/server/13696251/custom/scripts
$ ./postpatch.sh -dbhome/u01/app/oracle/product/11.2.0.3/dbhome_1
13. Check if your Oracle Inventory is reflecting the PSU installation issuing:
opatch lsinventory -detail -oh /u01/app/oracle/product/11.2.0.3/dbhome_1 | grep ^Patch
i.e.:
$ opatch lsinventory -detail -oh /u01/app/oracle/product/11.2.0.3/dbhome_1 | grep ^Patch
Patch 13734832 : applied on Mon May 14 09:27:13 PDT 2012
Patch description: "Database Patch for Exadata (APR 2012 - 11.2.0.3.5) : (13734832)"
Patch 13696251 : applied on Fri Apr 06 20:14:59 PDT 2012
Patch description: "Grid Infrastructure Patch Set Update : 11.2.0.3.2 (13696251)"
14. Loading Modified SQL Files into the Databases
Startup the instance on node 1
srvctl start instance -d <database_name> -i<instance_name>
i.e.:
srvctl start instance -dRACVS -i RACVS1
The following steps load modified SQL files into the single database. For a RAC environment, perform these steps on only one node.
cd $ORACLE_HOME
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @rdbms/admin/catbundle.sql exa apply
SQL> QUIT
Shutdown the instance
srvctl stop instance -d<database_name> -i<instance_name>
i.e.:
srvctl stop instance -d RACVS -i RACVS1
15. Startup all your databases
srvctl start database -d <database_name>; ...
ie:
srvctl start database -d rac05; srvctl start database -d oltpa
References
<NOTE:861152.1> - Do Patchset Updates (PSU's) Change the Oracle Release Version/Fifth Digit?
Attachments
This solution has no attachment
