Before you patch or upgrade your Oracle product, you need to understand compatibility among product's versions. Using WebLogic Server as an example:
Oracle attempts to support binary and source-level compatibility between the current version of WebLogic Server and all versions as far back as 9.2 in the areas of persistent data, generated classes, and API compatibility. In some cases, it is impossible to avoid incompatibilities. Where incompatibilities arise, they are fully documented in the Upgrading Oracle WebLogic Server.
In this article, the following terms are described for using Oracle products:
Patching involves copying a small collection of files over an existing installation. A patch is normally associated with a particular version of an Oracle product and involves updating from one minor version of the product to a newer minor version of the same product (for example, from version 220.127.116.11.0 to version 18.104.22.168.0).
It is highly recommended that users install Patchsets (i.e., a single patch that contains a collection of patches designed to be applied together), Patch Set Updates (PSUs), Software Patch Updates (SPUs) (formerly known as Critical Patch Updates (CPUs)), and Mini and Maintenance Packs instead of patches that include only a single update. Patches that include only a single update should be installed only when the update addresses a specific issue that has been identified on the target system.
Migration typically involves moving from a third-party (non-Oracle) product to an Oracle product.
It can also be used to refer to moving an existing set of software parameters (for example, an existing configuration or existing domain) from one release to another. For example, instructions for migrating your configuration from Oracle Fusion Middleware 11g Release 1 (22.214.171.124.0) to 11g Release 1 (126.96.36.199.0) are provided in "Using Patch Assistant to Migrate from 11g Release 1 (188.8.131.52.0) to Release 1 (184.108.40.206.0)".
Using Tomcat-to-WLS migration as an example, here are the questions you need to ask yourselves:
- Is the application using just the base JSP/Servlet capabilities of Tomcat?
- Does the application extend Tomcat with JSF or other EE APIs such as JAX-RS?
- Is the application using Spring and possibly other things such as Spring MVC?
- Does the application use any other of the common frameworks such as Struts, etc.?
- Does it use Liferay or any other Portal platforms?
- What Tomcat authentication provider do you use?
Upgrade involves moving from a previous major version to a new major version. For example, an upgrade would be required to move from Oracle Application Server 10g to Oracle Fusion Middleware 11g.
For upgrading from an earlier WebLogic Server release to the latest WebLogic Server 12c Release 1 (i.e., 12.1.3), read  for details. For example, if you are currently using a WebLogic version prior to WebLogic Server 10.3.1, upgrading to version 12.1.3 is a two-stage process.
- Patching and Upgrade Tools
- How to Download WebLogic Upgrade Installer? (Xml and More)
- How to find Oracle WebLogic Server Version? (Xml and More)
- JRockit Version Information (Xml and More)
- How to Determine JDBC Driver Version Installed with WebLogic Server? (Xml and More)
- Configuring WebLogic Server with a Different JVM (Xml and More)
- Configuring JDeveloper with a Different JDK (Xml and More)
- How to Upgrade the JDK Used by Oracle WebLogic Server UNIX installations to a Different Version (Doc ID 1309855.1)
- How to use the Smart Update tool to apply patches to a WebLogic Server installation.
- Third party and Oracle products that are supported to work with the 11g versions of JDeveloper and Application Development Framework (ADF)
- Register for the free online event--Migrating Java EE applications from GLassfish to WebLogic (04/30/2014)
- Migrating Oracle B2B from Test to Production (T2P) (Chap 10 of the Book "Getting Started with Oracle SOA B2B Integration: A Hands-On Tutorial")
- This section provides a real-world scenario to replicate (clone) the test environment to production for Oracle SOA.
- Oracle Fusion Middleware provides a series of scripts for this task.
- Oracle® Fusion Middleware Patching Guide 11g Release 1 (220.127.116.11.0)
- My Oracle Support Help Release 14.2
- WebLogic Upgrade Wizard
- WebLogic Server Compatibility
- WebLogic Server 12.1.2 Install, Configure, Upgrade, and Patch (good video)
- Upgrade from an earlier WebLogic Server release to WebLogic Server 12c Release 1 (12.1.3)
- This document describes the upgrade process for Oracle product installations that include only WebLogic Server. If your installation includes other Oracle Fusion Middleware products, prior to beginning the upgrade, refer to Planning an Upgrade of Oracle Fusion Middleware and the upgrade guides for each Fusion Middleware product in your installation.
- Customers who need continued access to critical bug fixes and security fixes as well as general maintenance for Java SE 7 or older versions can get long term support through Oracle Java SE Support.
- WebLogic Server also supports whole server-level migration, where a migratable server instance, and all of its services, is migrated to a different physical machine upon failure.
- If OPatch inventory tool is used, you can use the following command to verify update status:
- ./opatch lspatches