Last week I discussed about OAM (Access Manager) 11g certification with E-Business Suite R12 for Single Sign-On here . Under this certification OAM 11g should be with BP02 (Bundle Patch 02) i.e. 11.1.1.3.2. In this post I am going cover how to apply patches in OAM 11g and update OAM from 11.1.1.3.0 to 11.1.3.2 (10368022).
I discussed about Bundle Patch in OAM 10g earlier here In today’s post I am going to cover steps to apply patch in OAM 11g and prepare it for integration with E-Business Suite R12.
Patches in Oracle Access Manager are grouped together and named as bundle patch (BP). These bundle patches are specific to installer release which means, there is BP01, BP02 … BP0N for OAM 10.1.4.2; similarly there is Bundle Patch 01, 02 for OAM 10.1.4.3 and 11.1.1.3 resp.
As of today (3 May 2011) latest available BP for OAM 11.1.1.3 is on BP02 (10368022), OAM 10.1.4.3 is BP07 (11682261) and OAM 10.1.4.2 is BP11 (8829778) . For more information refer metalink note 736372.1 OAM Bundle Patch Release History .
.
Key points to install OAM 11.1.1.3 BP02 (10368022)
1. Bundle Patch (BP) in OAM 11g are applied using opatch utility in ORACLE_HOME/OPatch (where ORACLE_HOME should be set to OAM 11g software i.e. Oracle_IDM1/2)
2. You should be on at least OAM 11.1.13.0 or OAM 11gR1 BP01 i.e. 11.1.1.3.1
3. OAM 11g BP02 i.e. 11.1.1.3.2 is Server Side patch only i.e. No patching for WebGate or AccessGate is required (This is applicable just for BP02 as of today)
4. If you are planning to apply BP02 on OAM server with BP01 already applied i.e. 11.1.1.3.1, then there is no need to remove BP01 from system (BP02 can be applied on top of BP01)
5. Use opatch to install OAM bundle patch (Note that there are two opatch, one in each ORACLE_HOME under MW_HOME i.e. one in oracle_common and second in Oracle_IDM1. Your ORACLE_HOME environment should be set to Oracle_IDM1/2 where OAM is installed) .
6. If you are not familiar with oraInventory then learn more about oraInventory here
7. If you use opatch with flag auto (-auto) then make sure Node Manageris configured and you can start OAM server from WebLogic Console (set StartScriptEnabled to true in nodemanager.properties). With option -auto, opatch bounces OAM Managed Server (Admin Server and Node Manager should be running).
If you are planning to run opatch with option -auto on machine with multiple domains then look Neha’s post here
8. List Oracle Access Manager (OAM) version and applied patches using $ORACLE_HOME/ OPatch/ opatch lsinventory (where Oracle Home is pointing to directory in which OAM software is installed) Make sure that you get correct output like
___
Oracle IDM Suite 11.1.1.3.0
There are 1 products installed in this Oracle Home.
___
9. Perform prereq. steps mentioned in READ ME of patch (10368022)
10. Shutdown OAM Managed server (This is required only if you are applying patch without -auto mode)
11. Apply patch using opatch apply
12. Test patch by running “opatch lsinventory”
You should see output like
_____
Oracle IDM Suite 11.1.1.3.0
There are 1 products installed in this Oracle Home.
Interim patches (1) :
Patch 10368022 : applied on Fri May 06 16:28:33 BST 2011
Unique Patch ID: 13559507
Created on 1 Feb 2011, 04:21:35 hrs PST8PDT
Bugs fixed:
10021199, 10023607, 10074740, 10023625, 9977946, 10246619, 10368022
10366135, 9927123, 10028066, 10063987, 10358262, 10374715, 10186552
9980958, 9919231, 10216429, 10414606, 10119361, 10637364, 9887832
10268728, 10014363, 10395803, 10324002, 10414487, 10101919, 9936384
10268943, 9908111, 10231560, 10168999, 9956832, 9979140, 9927402
10030171, 11662235, 10015029, 10094106, 10046811, 9947699, 9916485
_____________
.
References
