Now that OAM 11.1.2.2 is certified with EBS, lets quickly look at the upgrade steps from 11.1.2.0.1.

Pre-upgrade:

Perform a full backup of the system (database and middleware home and weblogic domain)

Upgrade:

  1. Shutdown OAM Admin and Managed Servers
  2. Upgrade WebLogic to 10.3.6, if its not 10.3.6 already
  3. Run 11.1.2.2.0 installer and select existing middleware home

  4. Upgrade database schemas:
    • Download RCU 11.1.2.2.0 and create new set up of schemas
    • Run Patch Set Assistant: $MW_HOME/oracle_common/bin/psa
    • Upgrade OPSS (Oracle Platform Security Services) policies from jps-config.xml: 
cd $MW_HOME/oracle_common/common/bin
./wlst.sh
upgradeOpss(jpsConfig="", 
            jaznData="", 
            auditStore="", 
            jdbcDriver="", 
            url="", 
            user="", 
            password=""], 
            upgradeJseStoreType="true/false"])

Check the version after the upgrade:
select version, status, upgraded from schema_version_registry where owner=’schema_name’;

Upgrading System Configuration:

rm $ORACLE_HOME/common/script_handlers/*.class
cd $ORACLE_HOME/common/bin
./wlst.sh
upgradeConfig("/Oracle/Middleware/user_projects/domains/base_domain", "sys", "pwd", "PREFIX_OAM", "jdbc:oracle:thin:@localhost:1521/orcl")

Issues to watch for:
Cannot read configuration from store error when distributing a plugin in 11.1.2.1.0 version, upgraded from 11.1.2.0.0 (Doc ID 1565445.1)
Upgraded OAM 11.1.2.1 To 11.1.2.2 Application Domains Are No Longer Found. (Doc ID 1627806.1)