A lot of effort has been put in by Oracle to make this major
upgrade as smooth and easy as possible. The basic approach is to install SOA
Suite 12c in a new oracle home and upgrade the domain and schemas in place.
Customers undertaking the upgrade are primarily interested in a smooth upgrade,
minimizing the number of manual steps in the upgrade, reduce the down time to a
minimum, and minimize or eliminate any changes to client apps that use SOA APIs
or web interfaces.
The key to a successful and smooth upgrade experience are
the preupgrade preparations that you perform. The upgrade must be planned
carefully. If the preupgrade preparations are not performed, there is a
possibility that upgrade will fail in the middle or the system does not behave
properly post upgrade. The only recourse to a failed production system upgrade
is to roll it back from a full backup.
If your SOA domain includes BAM, then the upgrade is more
complex because BAM does not support inplace upgrade. Please read the
documentation carefully. The basic idea is to migrate the whole BAM
deployment to a seperate domain using export/import, remove BAM from the soa
domain during upgrade, and upgrade your soa domain to interop with the bam 11g
domain. Later slowly and carefully migrate to BAM 12c from BAM 11g.
There are six top steps that should be performed before
upgrade of your production system as a best practice.
- Can only upgrade a
domain that is 126.96.36.199 or 188.8.131.52. Migrate to a supported starting point
- Can only
upgrade a deployment using a 64 bit JVM. Migrate to 64 bit JVM before upgrade.
- Can only
upgrade a production domain not using XE DB and is not an admin server only domain.
- Can only upgrade a domain using LDAP or DB OPSS policy store. Migrate file based policy store to DB or LDAP
based policy store before upgrade.
- Can only upgrade a domain using a oracle DB of a version supported by the SOA Suite 12c certification matrix. Migrate to a
supported DB version before upgrade.
- Can only upgrade a domain based on weblogic server.
only upgrade a domain at this time with products deployed that were released in
12c. Example of products not released are OER, OSR, Webcenter, and SOA task UI exposed as portlets (which
uses webcenter libraries).
upgrade a domain at this time created with T2P or pack/unpack before SOA Suite
upgrade a domain at this time with multiple products in 12c in separate
unclustered managed servers using UMS. Examples are BAM, OSB and SOA. The
reason is because after upgrade UMS configuration is at the domain level or the
cluster level, but not at a unclustered managed server level.
Only JDK 7 is supported.
Oracle Fusion Middleware Administrator's Guide 11g
Release 1 (11.1.1)
Chapter 21 Moving from a Test to a Production Environment
Upgrade documentation and videos can be found at the