Recently I wrote a blog post with some quick tips for upgrading your Oracle Fusion Middleware to PS5. Well now, in this post I give fome more considerations about the update that I found out during an upgrade from patch set 2 to patch set 5.
A look into the Certification Matrix reveals that OFM 184.108.40.206.0 must run on JDK 1.7.0_02+. So no jRockit. Please be aware that JDK 7 is not certified with WLS 10.3.5. This means that while it is possible to run your 11gPS5 OFM applications in WLS 10.3.5, it will be an uncertified system. A bit confusing if you ask me…
Do not forget to shutdown the nodemanager when upgrading. If you have upgraded your middleware home and domain, and left the nodemanager running, you can’t start your server through the nodemanager. It will say that it WLS version is incorrect. Quick fix: restart the nodemanager.
OWSM SOA Suite
If your domain has OWSM installed, you have to update the OWSM predefined policies. This is especially important if you’re upgrading from PS2. If you forget this, the WorklistApp will not work.
It’s an online script, but the instructions are a bit vague. Run this script from the WLST from <MIDDLEWARE_HOME>/Oracle_SOA1/common/bin! Otherwise
upgradeWSMPolicyRepository() can’t be found.
OWSM and OSB
If you have an OSB domain with OWSM, and are upgrading from PS2, not installing the OWSM predefined policies will kill the OSB’s Project Explorer on the sbconsole. However, there’s a tricky part. Because you have an OSB only domain, there is no Oracle_SOA1/common/bin, and somehow during my upgrade WLST couldn’t find the
upgradeWSMPolicyRepository() procedure. This particular procedure comes from oracle_common/common/wlst/wsmManage.py, so if it is somehow not in your WLST path, you know where to find it.
The OSB nodemanager
Upgrading an OSB-only domain from PS2 to PS5 tends to affect the nodemanager.domains config file in the NodeManager-HOME. Inother words: the nodemanager can’t find the domain anymore. The solution is simply to use nmEnroll() in WLST to enroll your domain with the nodemanager again.
The PSA performance
The Patch Set Assistant is used for upgrading MDS or MDS+SOA-INFRA databases. A reference performance benchmark could be:
A ~200GB PS2 SOA-INFRA database took approximately 1.5hrs to upgrade to PS5. So that is not too bad. I don’t know the exact specs of the database, but it was a dataguard setup with fast enough storage to minimise that bottleneck.
Please make sure that before running the PSA, all database user rights are set as they were at installation. The DBA might follow the “Practice The Principle Of Least Privilege”, meaning that the SOA-INFRA database user might not have the appropriate set of grants needed to perform the PSA upgrade. This is especially true when you come from PS2. In this case the PSA will fail, and you’ll have to restore a database backup and start over.A few more considerations when upgrading OFM to PS5,