Note:
This guide is meant to be used as a reference tool for your upgrade. Always consult your component-specific upgrade documentation for detailed information about the supported upgrade starting points, as well as the prerequisites and upgrade paths for specific installation types.Use the Upgrade Assistant to upgrade supported component schemas, component configuration data, and standalone system component configurations in 11g and previous 12c releases to 12c (12.2.1.2). The Upgrade Assistant can also be used to run a pre-upgrade readiness check.
The Upgrade Assistant is available at the following location in your Fusion Middleware installation:
(UNIX) ORACLE_HOME/oracle_common/upgrade/bin
(Windows) ORACLE_HOME\oracle_common\upgrade\bin
When you run the Upgrade Assistant, it performs the following tasks:
readiness
mode, the Upgrade Assistant runs a pre-upgrade check on the schemas and component configurations associated with a domain.Note:
Before you start the Upgrade Assistant, Oracle recommends that you create a non-SYSDBA user. See Creating a Non-SYSDBA User to Run the Upgrade Assistant.Use the Upgrade Assistant in conjunction with other Oracle Fusion Middleware tools and processes to upgrade supported Fusion Middleware 11g and 12c components to the latest release.
The 11g to 12c upgrade process is different from previous releases. To understand how the Upgrade Assistant and the other upgrade tools are used, see Understanding the 12c Upgrade Process in Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware
In a typical upgrade, the Upgrade Assistant may be used several times.
Run the readiness check before you start an actual upgrade to determine if there are any issues that could prevent a successful upgrade.
The Upgrade Assistant can be run in -readiness
mode to identify potential upgrade issues before you perform an actual upgrade. The readiness check can be performed while the system is online. Readiness check is a read-only operation that scans your existing domain or database schemas and produces a text file with the results of the scan. The readiness check does not require that schemas are part of any particular domain. If your pre-upgrade environment has issues, you can correct those issues and then rerun the readiness check before you upgrade..
Alternatively, you can run the readiness check in -response
mode to perform a silent readiness check using a response file. For more information on using a response file with the Upgrade Assistant, see Upgrade Assistant Parameters.
Understanding the difference between the Examine Phase and a Readiness Check
The Examine phase of the upgrade process is a separate operation from running a readiness check. Typically the readiness checks are more thorough than the checks performed during the Examine phase. The readiness check is a read-only process performed before you start the actual upgrade, while the Examine phase occurs just before you click Upgrade and identifies potential issues with the schemas and configuration data.
Note:
If you have performed any of the upgrade steps, you should not run readiness check as the results can be invalid.Caution:
If you perform an upgrade and encounter issues that prevent a successful upgrade, you may have to revert to your backed-up, pre-upgrade environment and start the upgrade again. Running the readiness check can help identify some of these issues and prevent extended system downtime.After stopping servers and processes, use the Upgrade Assistant to upgrade supported product schemas to the current release of Oracle Fusion Middleware.
The Upgrade Assistant allows you to upgrade individually selected schemas or all schemas associated with a domain. The option you select determines which Upgrade Assistant screens you will use.
After the domain has been reconfigured, use the Upgrade Assistant to upgrade any component configurations.
During the component configuration process, the domain’s configuration files are updated to get them in-sync with the target version. As part of this process, the existing configuration data, which has been rendered invalid by the newer release, is deleted and replaced with configuration data that is compatible with the newer version.
This optional task enables you to review the list of available schemas before you begin the upgrade by querying the schema version registry. The registry contains schema information such as version number, component name and ID, date of creation and modification, and custom prefix.
You can let the Upgrade Assistant upgrade all of the schemas in the domain, or you can select individual schemas to upgrade. To help decide, follow these steps to view a list of all the schemas that are available for an upgrade:
If you are using an Oracle database, connect to the database by using an acount that has Oracle DBA privileges, and run the following from SQL*Plus:
SET LINE 120 COLUMN MRC_NAME FORMAT A14 COLUMN COMP_ID FORMAT A20 COLUMN VERSION FORMAT A12 COLUMN STATUS FORMAT A9 COLUMN UPGRADED FORMAT A8 SELECT MRC_NAME, COMP_ID, OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY ORDER BY MRC_NAME, COMP_ID ;
Examine the report that is generated. If the value in the VERSION
column is at 11.1.1.7.0
or higher, and the STATUS
column value is VALID
, then the schema is supported for upgrade.
If an upgrade is not needed for a schema, the schema_version_registry
table retains the schema at its pre-upgrade version.
Note the schema prefix name that was used for your existing schemas. You will use the same prefix when creating new 12c schemas.
Notes
If your existing schemas are not at a supported version, then you must upgrade them to a supported version before using the 12c (12.2.1.2) upgrade procedures. Refer to your pre-upgrade version documentation for more information.
Some components, such as Oracle Enterprise Data Quality, Oracle GoldenGate Monitor and Oracle GoldenGate Veridata, support an upgrade from versions other than the standard Oracle Fusion Middleware supported versions.
If you used an OID-based policy store in 11g, make sure that you create a new OPSS schema before you perform the upgrade. After the upgrade, the OPSS schema will remain an LDAP-based store.
You can only upgrade schemas for products that are available for upgrade in the Oracle Fusion Middleware release 12c (12.2.1.2). Do not attempt to upgrade a domain that includes components that are not yet available for upgrade to 12c (12.2.1.2).
Before an upgrade, it is important to know which schemas can be upgraded to 12c (12.2.1.2). Not all schemas require an upgrade, and not all schemas can be upgraded.
When schemas are created in your database, the Repository Creation Utility (RCU) creates and maintains a table called schema_version_registry
. Refer to this table before you perform an upgrade. The Schema Version After Upgrade column shows the latest version for that schema. If your schemas are already at this version, then you will not need to upgrade.
NOTE: The Schema(s) column shows the default schema name format of prefix and schema name separated by an underscore (_) character. The default prefix is DEV
, but you may have created new prefixes for your schemas while using the RCU.
Table 1-1 Schemas that can be upgraded to Oracle Fusion Middleware 12c 12c (12.2.1.2)
Component Name | Schemas | Schema Version Before Upgrade | Schema Version After Upgrade | Dependencies and Additional Information |
---|---|---|---|---|
Audit ServicesFoot 1 |
|
11.1.1.7 11.1.1.9 12.1.2.0 12.1.3.0 12.2.1.0 12.2.1.1 |
12.2.1.2 |
No dependencies. |
Metadata Services |
|
11.1.1.7 11.1.1.9 12.1.2.0 12.1.3.0 12.2.1.0 |
12.2.1.1 |
No dependencies. 12.2.1.1 is the latest version for this schema. |
Platform Security ServicesFoot 2 |
|
11.1.1.7 11.1.1.9 12.1.2.0 12.1.3.0 |
12.2.1.0 |
The 12.2.1.0 is the latest version for this schema. |
Common Infrastructure Services (LocalSvcTbl) |
|
12.1.2.0 |
12.1.3.0 |
The 12.1.3.0 is the latest version for this schema. |
User Messaging Service |
|
11.1.1.7 11.1.1.9 12.1.2.0 12.1.3.0 |
12.2.1.0 |
12.2.1.0 is the latest version for this schema. |
WebLogic Server |
|
11.1.1.7 12.1.2.0 |
12.2.1.0 |
12.2.1.0 is the latest version for this schema. |
Data Integrator (Master and Work Repository) |
|
11.1.1.7 11.1.1.9 12.1.2.0 12.1.3.0 12.2.1.0 |
12.2.1.1 |
No dependencies. 12.2.1.1 is the latest version for this schema. |
SOA Infrastructure (including Oracle Business Activity Monitoring, Business Process Management, and Oracle Service Bus |
|
11.1.1.7 11.1.1.9 12.1.3 12.2.1.0 |
12.2.1.1 |
The 12.2.1.1 is the latest version for this schema. |
Oracle Enterprise Scheduler |
|
11.1.1.7 11.1.1.9 12.1.3 12.2.1.0 |
12.2.1.1 |
12.2.1.1 is the latest version for this schema. |
Oracle Managed File Transfer |
|
12.1.3.0 12.2.1.0 |
12.2.1.1 |
The prefix_MDS, prefix_IAU, and prefix_UMS must also be upgraded.
12.2.1.1 is the latest version for this schema. |
Oracle WebCenter Content Server |
|
11.1.1.7 11.1.1.8Foot 4 11.1.1.9 |
12.2.1.0 |
The prefix_MDS schema must be upgraded first. 12.2.1.0 is the latest version for this schema. |
Oracle WebCenter Enterprise Capture |
|
11.1.1.8 |
12.2.1.0 |
The prefix_MDS and prefix_OPSS schemas must be upgraded first. 12.2.1.0 is the latest version for this schema. |
Oracle WebCenter Portal |
|
11.1.1.7Foot 5 11.1.1.8 |
12.2.1.0 |
The prefix_MDS schema must be upgraded first. 12.2.1.0 is the latest version for this schema. |
Oracle WebCenter Portal | prefix _WEBCENTER |
11.1.1.7
11.1.1.8 12.2.1.0 |
12.2.1.1 | 12.2.1.1 is the latest version for this schema. |
Oracle WebCenter Sites | prefix _WCSITES |
12.2.1.0
12.2.1.1 |
12.2.1.2 | |
Enterprise Data Quality |
|
11.1.1.7.3 12.1.3.0 12.2.1.0 |
12.2.1.1 |
12.2.1.1 is the latest version for this schema. |
GoldenGate Monitor |
|
11.2.1.0.7 12.1.3.0 |
12.2.1.0 |
12.2.1.0 is the latest version for this schema. |
GoldenGate Studio | prefix _OGGSTUDIO_REPO |
12.2.1.0 | 12.2.1.1 | 12.2.1.1 is the latest version for this schema. |
GoldenGate Veridata |
|
11.2.1.0.1 12.1.3.0 12.2.1.0 |
12.2.1.2 |
Footnote 1
When upgrading _IAU
from 11g starting points, the Upgrade Assistant will update two auxilary schemas, IAU_APPEND
and IAU_VIEWER
and add them to the schema_version_registry
for 12.2.1.2. These schemas were not part of the 11g schema_version_registry
table.
Footnote 2
As of release 11.1.1.7, OPSS audit data is stored in IAU common tables instead of the JPS table.
Footnote 3
When upgrading a system from a previous 12c release, the schema is called prefix_UMS.
Footnote 4
First release to support Edition-Based Redefinition (EBR) enabled schemas.
Footnote 5
First release to support Edition-Based Redefinition (EBR) enabled schemas.
After you have reconfigured the domain using the Reconfiguration Wizard, use the Upgrade Assistant to upgrade and configure the supported component configurations to 12c (12.2.1.2).
When you use the Upgrade Assistant to upgrade your configurations, it automatically determines the list of components that are configured and can be upgraded to the latest version. Before you begin the upgrade, review the list of components that can be upgraded to this release.
Caution:
Do not attempt an upgrade if you want to continue using existing Fusion Middleware 11g components that have been deprecated or not yet available for use in the 12c (12.2.1.2) release.Component configurations that can be upgraded include:
Common Infrastructure Services
Oracle Data Integrator
Oracle Enterprise Data Quality
Oracle Forms
Oracle GoldenGate Monitor
Oracle GoldenGate Veridata
Oracle HTTP Server
Oracle MapViewer
Oracle Reports
Oracle Traffic Director
Oracle User Messaging Service
Oracle WebCenter Portal
Oracle WebCenter Sites
Oracle Web Services Manager
System Components Infrastructure
Java Required Files (JRF) Infrastructure