09 March 2011

How to Apply patch 10.2.0.5.4 in OEM Grid control

To apply patch 10.2.0.5.4 in OEM Grid control :

Download the patch p9786002_10205_Generic.zip from Metalink and copy to desired directory.

Follow these steps:

1.
Please set your <OMS_HOME> to ORACLE_HOME.

>Set ORACLE_HOME=C:\OracleHomes\oms10g

$export ORACLE_HOME=/home/OracleHomes/oms10g

Please set <ORACLE_HOME>/bin and <ORACLE_HOME>/OPatch to your PATH envirnoment variable.

In windows add this in Environment variable.

In AIX,Solaris etc, add this to your PATH variable as below :

export PATH=$PATH:/home/OracleHomes/oms10g/bin:/home/OracleHomes/oms10g/Opatch

2.
Shutdown OMS using the following command.
In case of multi-OMS environment, shutdown on all OMS machines.

$emctl stop oms

Leave EM Repository database and its listener running.

3.
Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:

$unzip p9786002_10205_Generic.zip

$cd 9786002

$opatch napply -skip_subset

Ex:

C:\Dinaz\oracle_dump\p9786002_102050_Generic\9786002\9786002>opatch napply -skip_subset

Invoking OPatch 10.2.0.4.6
Oracle Interim Patch Installer version 10.2.0.4.6
Copyright (c) 2009, Oracle Corporation.  All rights reserved.
UTIL session
Oracle Home       : C:\OracleHomes\oms10g
Central Inventory : C:\Program Files\Oracle\Inventory
   from           : n/a
OPatch version    : 10.2.0.4.6
OUI version       : 10.2.0.5.0
OUI location      : C:\OracleHomes\oms10g\oui
Log file location : C:\OracleHomes\oms10g\cfgtoollogs\opatch\opatch2010-08-31_16
-01-20PM.log
Patch history file: C:\OracleHomes\oms10g\cfgtoollogs\opatch\opatch_history.txt
Invoking utility "napply"
Checking conflict among patches...
Checking if Oracle Home has components required by patches...
Checking skip_subset
Checking conflicts against Oracle Home...
OPatch continues with these patches:   9786002
Do you want to proceed? [y|n]y
User Responded with: Y
Running prerequisite checks...
OPatch detected non-cluster Oracle Home from the inventory and will patch the lo
cal system only.
Backing up files affected by the patch 'NApply' for restore. This might take a w
hile...
Applying patch 9786002...
ApplySession applying interim patch '9786002' to OH 'C:\OracleHomes\oms10g'
Backing up files affected by the patch '9786002' for rollback. This might take a
 while...
Patching component oracle.sysman.top.oms, 10.2.0.5.0...
Copying file to "C:\OracleHomes\oms10g\sysman\admin\rollback_9786002.lst"
ApplySession adding interim patch '9786002' to inventory
Verifying the update...
Inventory check OK: Patch ID 9786002 is registered in Oracle Home inventory with
 proper meta-data.
Files check OK: Files from Patch ID 9786002 are present in Oracle Home.
The local system has been patched and can be restarted.
UtilSession: N-Apply done.
OPatch succeeded.

4.
Start the oms

From OMS_HOME

$emctl start oms

C:\OracleHomes\oms10g\BIN>emctl start oms
 If OEM is not able to acces after starting OMS, try restarting OPMN:

C:\OracleHomes\oms10g\opmn\bin>opmnctl stopall

C:\OracleHomes\oms10g\opmn\bin>opmnctl startall

No comments:

Post a Comment