1 About Using the Oracle Fusion Middleware Upgrade Assistant

Use the Upgrade Assistant to upgrade and configure supported Fusion Middleware 11g and 12c domains to 12c (12.2.1.3.0).

The Upgrade Assistant automates many common upgrade tasks including schema upgrades and domain reconfigurations. You can also use the Upgrade Assistant to perform a readiness check prior to an upgrade.

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.

• About the Upgrade Assistant
  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.3.0). The Upgrade Assistant can also be used to run a pre-upgrade readiness check.
• About Using the Upgrade Assistant in the Upgrade Process
  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.
• Identifying Existing Schemas Available for Upgrade
  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.
• Identifying Schemas that Can Be Upgraded to 12c (12.2.1.3.0)
  Before an upgrade, it is important to know which schemas can be upgraded to 12c (12.2.1.3.0). Not all schemas require an upgrade, and not all schemas can be upgraded.
• Identifying Configurations That Can Be Upgraded with the Upgrade Assistant
  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.3.0).

About the Upgrade Assistant

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.3.0). 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:

• When run in ­readiness mode, the Upgrade Assistant runs a pre-upgrade check on the schemas and component configurations associated with a domain.

• For schema upgrades, the Administration server is offline and the list of schemas to upgrade is determined by reading the domain configuration.

• For component configuration upgrades, the Administration server is offline and the list of component configurations to upgrade is determined by reading the domain configuration.

  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.

About Using the Upgrade Assistant in the Upgrade Process

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 Planning an Upgrade of Oracle Fusion Middleware

In a typical upgrade, the Upgrade Assistant may be used several times.

1. About Using the Upgrade Assistant to Create Schemas
   The Upgrade Assistant calls Repository Creation Utility (RCU) APIs internally to create missing schemas which are required for 12c. You do not have to run the RCU separately unless you want to customize the default schema settings.
2. About Using the Upgrade Assistant to Perform a Readiness Check Before an Upgrade
   Run the readiness check before you start an actual upgrade to determine if there are any issues that could prevent a successful upgrade.
3. Upgrading Product Schemas
   After stopping servers and processes, use the Upgrade Assistant to upgrade supported product schemas to the current release of Oracle Fusion Middleware.
4. About Using the Upgrade Assistant to Upgrade Component Configurations
   After the domain has been reconfigured, use the Upgrade Assistant to upgrade any component configurations.

About Using the Upgrade Assistant to Create Schemas

The Upgrade Assistant calls Repository Creation Utility (RCU) APIs internally to create missing schemas which are required for 12c. You do not have to run the RCU separately unless you want to customize the default schema settings.

The Upgrade Assistant can now detect when component schemas may be missing and must be created before the upgrade. If enabled, the Upgrade Assistant can create these schemas for you using the default tablespace and temporary tablespace settings. To customize the schema settings you must use the Repository Creation Utility to create the schemas.

Note:

If you do not want the Upgrade Assistant to create these schemas for you, you must deselect the Create missing schemas for the specified domain option.

About Using the Upgrade Assistant to Perform a Readiness Check Before an Upgrade

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. You can perform a readiness check while the system is online. It is a read-only operation that scans your existing domain or database schemas and produces a text file with the results of the scan. A 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 a readiness check before you upgrade.

Alternatively, you can run a 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, readiness checks are more thorough than the checks performed during the Examine phase. A 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, do not run a readiness check, or the results may be invalid.

Caution:

If you 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 a readiness check can help identify some of these issues and prevent extended system downtime.

Upgrading Product Schemas

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.

About Using the Upgrade Assistant to Upgrade Component Configurations

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.

Identifying Existing Schemas Available for Upgrade

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:

1. If you are using an Oracle database, connect to the database by using an account 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;
   

2. Examine the report that is generated.

   If an upgrade is not needed for a schema, the schema_version_registry table retains the schema at its pre-upgrade version.

3. Note the schema prefix name that was used for your existing schemas. You will use the same prefix when you create new 12c (12.2.1.3.0) schemas.

Notes:

• If your existing schemas are not from a supported version, then you must upgrade them to a supported version before using the 12c (12.2.1.3.0) 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 the earlier versions, make sure to create a new OPSS schema before you perform the upgrade. After the upgrade, the OPSS schema remains an LDAP-based store.

• You can only upgrade schemas for products that are available for upgrade in Oracle Fusion Middleware release 12c (12.2.1.3.0). Do not attempt to upgrade a domain that includes components that are not yet available for upgrade to 12c (12.2.1.3.0).

Identifying Schemas that Can Be Upgraded to 12c (12.2.1.3.0)

Before an upgrade, it is important to know which schemas can be upgraded to 12c (12.2.1.3.0). 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 (12.2.1.3.0)

Component Name	Schemas	Schema Version Before Upgrade	Schema Version After Upgrade	Dependencies and Additional Information
Audit ServicesFoot 1	prefix_IAU	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	12.2.1.3	No dependencies.
Metadata Services	prefix_MDS	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	12.2.1.3	No dependencies.
Platform Security ServicesFoot 2	prefix_OPSS	11.1.1.7 11.1.1.9 12.1.2.0 12.1.3.0	12.2.1.0	The prefix_IAU schema must be upgraded first. 12.2.1.0 is the latest version for this schema.
Common Infrastructure Services (LocalSvcTbl)	prefix_STB	12.1.2.0 12.1.3.0 12.2.1.0 12.2.1.1 12.2.1.2	12.2.1.3	The prefix_STB schema must be upgraded when upgrading other components, such as SOAINFRA.
User Messaging Service	prefix_ORASDPM prefix_UMSFoot 3	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	prefix_WLS	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)	prefix_ODI_REPO	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	12.2.1.3	No dependencies.
SOA Infrastructure (including Oracle Business Activity Monitoring, Business Process Management, and Oracle Service Bus	prefix_SOAINFRA	11.1.1.7 11.1.1.9 12.1.3 12.2.1.0 12.2.1.1 12.2.1.2	12.2.1.3	The prefix_STB schema must be upgraded first.
Oracle Enterprise Scheduler	prefix_ESS	11.1.1.7 11.1.1.9 12.1.3 12.2.1.0 12.2.1.1 12.2.1.2	12.2.1.3	No dependencies.
Oracle Managed File Transfer	prefix_MFT	12.1.3.0 12.2.1.0 12.2.1.1 12.2.1.2	12.2.1.3	The prefix_MDS, prefix_IAU, and prefix_UMS must also be upgraded.
Oracle WebCenter Content Server	prefix_OCS prefix_OCSSEARCH	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 Content: Imaging	prefix_IPM	11.1.1.2.1	12.2.1.3
Oracle WebCenter Content: Records	prefix_URM	11.1.1.7.0 11.1.1.8.0 11.1.1.9.0	12.2.1.0	12.2.1.0 is the latest version for this schema.
Oracle WebCenter Enterprise Capture	prefix_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	prefix_PORTLET prefix_ACTIVITIES prefix_DISCUSSIONS prefix_DISCUSSIONS_CRAWLER	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	12.2.1.3
Enterprise Data Quality	prefix_EDQCONFIG prefix_EDQRESULTS prefix_EDQSTAGING	11.1.1.7.3 12.1.3.0 12.2.1.0 12.2.1.1 12.2.1.2	12.2.1.3
GoldenGate Monitor	prefix_OGGMON	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	prefix_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 updates two auxiliary schemas, IAU_APPEND and IAU_VIEWER and adds them to the schema_version_registry for 12c (12.2.1.3.0). 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.

Identifying Configurations That Can Be Upgraded with the Upgrade Assistant

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.3.0).

When you use the Upgrade Assistant to upgrade your configurations, it automatically determines the 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 Fusion Middleware 11g components that have been deprecated or are not yet available for use in the 12c (12.2.1.3.0) release.

Component configurations that can be upgraded include:

• Oracle Internet Directory

• 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