Upgrade Oracle IAM (OES) from 11gR2 ( to 11gR2 PS2 ( lessons learned

I discussed about availability of IAM 11gR2 PS2 ( here and installation changes in IAM 11gR2 PS2 ( here. In this post I am going to cover steps to upgrade IAM (OES in specific) from 11gR2 ( to 11gR2 PS2 ( . Upgrade of other IAM component (OIM, OAM, OAAM & OPAM) to follow soon.

For upgrade (or patch) from PS1 to PS2 check Oracle Documentation IAM Upgrade Guide

Note: IAM 11gR2 PS2 ( is complete software that can also be used to patch or


High Level Upgrade Steps for OES from to

OES Upgrade has two parts

a) Upgrade OES Server
b) Upgrade OES Client i.e. OES Security Module (OESSM)


Upgrade OES Server

  • Stop OES Server (WebLogic Admin Server where OES is deployed)
  • Install Oracle IAM in same ORACLE_HOME where OES/IAM is installed



Note: Above step should upgrade ORACLE_HOME binaries from version to

  • Upgrade OPSS schema (schema for OES) using Patch Set Assistant (PSA) from version to (Yes OPSS schema for OES 11gR2 PS2 is Use $MW_HOME/oracle_common/bin/psa
Note: You must select OPSS schema used by OES Server. To find schema name and DB server details used by OES/OPSS check $DOMAIN_HOME/ config/ jdbc/ opss-jdbc.xml 
  • Upgrade OPSS (Platform Security Service) i.e. configuration file jps-config.xml and policy store to using WLST upgradeOpss
Note: upgradeOpss is for all Fusion Middleware Upgrades (SOA, WebCenter, IAM etc) and is NOT specific to OES
  • Start WebLogic Server where OES Server is deployed


Upgrade OES Client

In OES client (OESSM) side you install
a) OES Client Software
b) IAM Software – Yes, you saw it right complete IAM software is also required at client side too.

Note: OES Client Software and IAM Software must be installed in separate ORACLE_HOMES


  • Install OES CLIENT in same ORACLE_HOME where OES CLIENT is installed

Note: Above step should upgrade OES CLIENT binaries from version to

  • On CLIENT SIDE – Install IAM/OES in same ORACLE_HOME where IAM/OES installed




Note: Above step should upgrade ORACLE_HOME binaries from version to

  • Finally start WebLogic Server where OES CLIENT is configured
This completes OES upgrade



Lessons Learned in Upgrade from OES 11gR2 to OES 11gR2 PS2

  • Ensure that you take backup of Application Tier file system and Database before upgrade (obvious thing)
  • If you have too many OES policies ensure that TEMP tablespace used by OES Schema has enough free space, Check if you get ORA-01652 Unable to extend temp segment by 128 in tablespace while upgrading OPSS schema (using psa)
  • If Upgrade of OPSS schema (using psa) fails in between, it is better and quick to restore database from backup. Fix the issue and start again (avoid fixing failed attempt and continue with upgrade as upgrade may fail again) – Re-running of OPSS schema upgrade after failure may not work.
  • If upgrade of OPSS (WLST upgradeOpss) fails with OutOfMemory error like below


Traceback (innermost last):
File “<console>”, line 1, in ?
File “/oracle/apps/atul/mwoes/oracle_common/common/wlst/jpsWlstCmd.py”, line 1759, in upgradeOpss java.lang.OutOfMemoryError
java.lang.OutOfMemoryError: java.lang.OutOfMemoryError


Add JVM size in wlst.sh ($WL_HOME/common/bin/wlst.shMEM_ARGS=”-Xms4096m -Xmx4096m”  (Ensure that MEM_ARGS are added aftre “${WL_HOME}/server/bin/setWLSEnv.sh”)


Share This Post with Your Friends over Social Media!

About the Author Atul Kumar

Oracle ACE, Author, Speaker and Founder of K21 Technologies & K21 Academy : Specialising in Design, Implement, and Trainings.

follow me on:
Not found