Note:
Before starting the Upgrade Assistant, refer to Planning an Upgrade of Oracle Fusion Middleware and 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.This section describes the following:
The Oracle Fusion Middleware Upgrade Assistant is used to upgrade supported 11g and 12c component schemas, component configurations, and standalone system component configurations to Fusion Middleware 12c (12.2.1). As of release 12c (12.2.1), the Upgrade Assistant can also be used to run a pre-upgrade readiness check.
oracle_common/upgrade/bin/ua
oracle_common\upgrade\bin\ua
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. You must perform this check while the domain is online.Note:
Before you start the Upgrade Assistant, Oracle recommends that you create a non-SYSDBA user.The Upgrade Assistant is used in conjunction with other Fusion Middleware tools and processes to complete an upgrade of supported 11g and 12c components to 12c (12.2.1) upgrade.
The 11g to 12c upgrade process is very different from previous releases. To understand how the Upgrade Assistant and the other upgrade tools are used in the upgrade process, see Understanding the 12c Upgrade Process
In a typical upgrade, the Upgrade Assistant may be used several times, as described below:
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. Readiness check does not require schemas to be a 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..
Note:
The upgrade steps that can only be performed by the Upgrade Assistant are checked by the readiness check feature.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 Starting the Upgrade Assistant in Response File Mode.
Note that the Examine phase of the upgrade process is a separate operation. 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. The Examine phase occurs just before you click Upgrade and identifies potential issues with the schemas and configuration data.
Note:
Readiness check must only be run before you start with an actual upgrade. If you have performed any of the upgrade steps, you should not run readiness check as the results can be invalid.For more information on running a pre-upgrade readiness check, see Running a Pre-Upgrade Readiness Check .
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.
The Upgrade Assistant provides two options for upgrading schemas: Individually Selected Schemas and All Schemas Used By a Domain.
Individually Selected Schemas
This option enables you to choose which component schemas to upgrade. Select this option when you have component schemas within the domain that you do not want to upgrade.
For example, if you want to make a trial run of Upgrade Assistant by creating schemas with RCU that are outside the domain, and then use Upgrade Assistant to upgrade them.
All Schemas Used By a Domain
This option allows the Upgrade Assistant to detect all of the available schemas within the specified domain and include them in the upgrade.
Once the schemas are upgraded, you will use the separate Reconfiguration Wizard to reconfigure the existing domain.
For more information on using the Reconfiguration Wizard, see "Reconfiguring WebLogic Domains".
The Upgrade Assistant identifies and includes all the schemas that are available for an upgrade. You can also select the schemas you want to upgrade. If you want to review the list of available schemas before you begin the upgrade, query the schema version registry.
Tip:
Compare the information you collect from the schema version registry and the corresponding schemas to determine whether there are schemas in your domain that are not available for an upgrade yet.
If you are using an Oracle database, connect to the database as a user having Oracle DBA privileges, and run the following from SQL*Plus to get the current version numbers:
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 ;
The following report is generated when saved to a SQL script, for example version.sql.
If the number in the "VERSION" is at 11.1.1.6.0 or higher, and the STATUS column 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 schemas at their pre-upgrade version after the 12.2.1 upgrade.
Notes about the schemas that need to be upgraded
For most components, the only schema version starting points that are valid for upgrading are 11g Release 1 (11.1.1.6, 1.1.1.7, 11.1.1.8, or 11.1.1.9) or 12c (12.1.2 or 12.1.3). If your schemas are not at a supported version, then you must upgrade them before using the 12c (12.2.1) upgrade procedures.
Some components, such as Oracle Enterprise Data Quality and Oracle Golden Gate Veridata, support an upgrade from versions other than the standard Oracle Fusion Middleware supported versions.
Refer to your component-specific installation and upgrade documentation for additional information about the schemas that are required for your upgrade.
If you used a file-based policy store in 11g, then you must reassociate the file-based policy store with a database-based security store before running the Upgrade Assistant.
For more information see Reassociating a File-Based Policy Store Before Upgrade.
If you used an OID-based policy store in 11g, make sure that you have created new 12c OPSS schemas before upgrade.
You can only upgrade schemas for products that are available for upgrade in the Oracle Fusion Middleware 12c (12.2.1) release. Do not attempt to upgrade a domain that includes components that are not yet available for upgrade to 12c (12.2.1) .
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 as some schemas may not require an 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)
| Component Name | Schema(s) | Schema Version Before Upgrade | Schema Version After Upgrade | Dependencies and Additional Information |
|---|---|---|---|---|
|
AS Common Schemas |
||||
|
Audit Services1 |
|
11.1.1.6 11.1.1.7 11.1.1.9 12.1.2 12.1.3 |
12.2.1 |
No dependencies. 12.2.1 is the latest version for this schema. |
|
Metadata Services |
|
11.1.1.6. 11.1.1.7 11.1.1.9 12.1.2 12.1.3 |
12.2.1 |
No dependencies. 12.2.1 is the latest version for this schema. |
|
Platform Security Services2 |
|
11.1.1.6 11.1.1.7 11.1.1.9 12.1.2 12.1.3 |
12.2.1 |
The |
|
Common Infrastructure Services (LocalSvcTbl) |
|
12.1.2 12.1.3 |
12.1.3 |
The |
|
User Messaging Service |
|
11.1.1.6 11.1.1.7 11.1.1.9 12.1.2 12.1.3 |
12.2.1 |
When upgrading a system that is a new installation of 12.2.1 the schema name will be called |
|
WebLogic Diagnostic Framework |
|
11.1.1.6 11.1.1.7 12.1.2 |
12.2.1 |
|
|
Oracle Data Integrator |
||||
|
Data Integrator (Master and Work Repository) |
|
11.1.1.6 11.1.1.7 11.1.1.9 12.1.2 12.1.3 |
12.2.1 |
None. |
|
Oracle SOA Suite |
||||
|
SOA Infrastructure (including Oracle Business Activity Monitoring, Business Process Management, and Oracle Service Bus |
|
11.1.1.6 11.1.1.7 11.1.1.9 12.1.3 |
12.2.1 |
The |
|
Oracle Enterprise Scheduler |
|
11.1.1.6 11.1.1.7 11.1.1.9 12.1.3 |
12.2.1 |
|
|
Oracle Managed File Transfer |
|
12.1.3 |
12.2.1 |
The prefix_MDS, prefix_IAU, and prefix_UMS must also be upgraded. |
|
Oracle WebCenter |
||||
|
Oracle WebCenter Content Server |
|
11.1.1.6 11.1.1.7 11.1.1.83 11.1.1.9 |
12.2.1 |
The prefix_MDS schema must be upgraded first. |
|
Oracle WebCenter Enterprise Capture |
|
11.1.1.8 |
12.2.1 |
The prefix_MDS and prefix_OPSS schemas must be upgraded first. |
|
Oracle WebCenter Portal |
|
11.1.1.74 11.1.1.8 |
12.2.1 |
The prefix_MDS schema must be upgraded first.. |
|
Oracle Enterprise Data Quality |
||||
|
Enterprise Data Quality |
|
11.1.1.7.3 12.1.3 |
12.2.1 |
|
|
Oracle Golden Gate Monitor |
||||
|
Golden Gate Monitor |
|
11.1.1.7 12.1.3 |
12.2.1 |
|
|
Oracle Golden Gate Veridata |
||||
|
Veridata |
|
11.2.1 12.1.3 |
12.2.1 |
|
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. After you run the Upgrade Assistant for schema upgrades, you will use the Reconfiguration Wizard to reconfigure your domain. The Upgrade Assistant is used again, after the reconfiguration, to upgrade any remaining configuration properties.
You can use the Upgrade Assistant to upgrade the following component configurations to 12c (12.2.1):
Oracle Data Integrator (ODI)
Oracle Enterprise Data Quality (EDQ)
Oracle Forms
Oracle Reports
Oracle Golden Gate Monitor (OGGMON)
Oracle Golden Gate Veridata
Oracle HTTP Server (OHS)
JRF Infrastructure
Oracle MapViewer
Oracle Managed File Transfer (MFT)
Oracle Traffic Director (OTD)
Oracle User Messaging Service (UMS)
Oracle WebCenter Content (WCC)
Oracle Web Services Manager
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 12.2.1 release
If you want to continue to use them with your upgraded components, review the Interoperability and Compatibility guide for this release before you upgrade. You will need to determine if an upgrade will cause any incompatibility issues with your Fusion Middleware 11g components.
This section describes the procedures you must perform before you run the Upgrade Assistant:
Review the pre-upgrade checklist to make sure that all pre-upgrade requirements have been met. Also verify that you have completed all of the component-specific pre-upgrade tasks for each component you are upgrading.
Oracle Fusion Middleware Pre-Upgrade Checklist
Note:
In addition to the Oracle Fusion Middleware Pre-Upgrade Checklist, each component may require additional component-specific tasks to be completed before upgrade. Always consult your component-specific upgrade documentation before starting an upgrade.Before running Upgrade Assistant, shut down all Oracle Fusion Middleware Managed Servers, Administration Servers, and system components (such as OHS) that may be using the schemas or configuration data you want to upgrade.
In addition, the databases that contain Fusion Middleware database schemas must be quiesced before running Upgrade Assistant. You can either shutdown and restart the database server, or ensure that there are no other database users operating on the same database instance that will be upgraded by Upgrade Assistant. Failure to do so may result in an incomplete or failed upgrade.
If you are running Node Manager, you should also stop Node Manager. You can do this by closing the console window in which Node Manager is running, or by using the stopNodeManager WLST command.
Instructions for stopping an Oracle Fusion Middleware environment are provided in "Stopping an Oracle Fusion Middleware Environment".
The Upgrade Assistant is used to upgrade schemas, component configurations and standalone system components.
Note:
The Upgrade Assistant should be run by a non-SYSDBA user whenever possible. The steps to create a non-SYSDBA user are described in Creating a Non-SYSDBA User.If you run the Upgrade Assistant from an Oracle home that contains components with any schemas, then the Schemas upgrade option is shown. The Upgrade Assistant only lists the components that are candidates for schema upgrade. You can select the schemas you want to upgrade from the component list.
Table 1-2 shows the screens that are displayed when you run the Upgrade Assistant to upgrade schemas and they vary depending on the options you select.
Table 1-2 Upgrading Schemas: Navigating the Upgrade Assistant Screens
| Screen Title | When does the screen appear? | Description |
|---|---|---|
|
Always. |
This screen provides an overview of the Upgrade Assistant and some information about important pre-upgrade tasks. |
|
|
Always. |
Select the schema upgrade operation that you want to perform on this screen. The options on the screens change depending on what you select from the following:
|
|
|
When you select Individually Selected Schemas. |
This screen provides a list of installed Oracle Fusion Middleware components that have schemas that can be upgraded. When you select a component, the schemas and any dependencies are automatically selected. |
|
|
When you select All Schemas Used by a Domain. |
This screen is read-only, and it displays all the components and schemas found in the specific domain directory that are included in the upgrade. |
|
|
Always. |
This screen requires you to acknowledge that all prerequisites have been met before you continue with the upgrade. Check the boxes before you continue. |
|
|
Always. |
Enter the information required to connect to the selected schema and the database that hosts the schema on this screen. The screen name changes based on the type of schema selected ("MDS Schema", for example). Since the component ID or schema name is changed for UCSUMS schema as of release 12.1.2, the Upgrade Assistant does not automatically recognize the possible schemas and display them in a drop-down list. You must manually enter the name in a text field. The name can be either prefix_ |
|
|
Always. |
This screen displays the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade.
Note: Issues detected during the Examination phase can be fixed without restoring from backup. |
|
|
Always. |
Review a summary of the options you have selected and to start the upgrade process on this screen. |
|
|
Always. |
This screen displays the status of the upgrade process. |
|
|
When the upgrade is successful. |
The upgrade is successful. The Post-Upgrade Actions window describes the manual tasks you must perform to make the component function in the new installation. |
|
|
When the upgrade fails. |
The upgrade failed for the specified component(s). You must restart the Upgrade Assistant. The Upgrade Assistant logs are available at
ORACLE_HOME/oracle_common/upgrade/logs.
Note: If the upgrade fails you must restore your pre-upgrade environment from backup, fix the issues and then restart the Upgrade Assistant. You cannot fix the issues and restart the Upgrade Assistant because the files are modified during this operation. |
For SOA Suite and BPM Upgrades Only:
The upgrade of active and closed SOA instance data to 12c (12.2.1) happens automatically as part of the SOA schema upgrade process with the Upgrade Assistant. For more information, see Administering and Monitoring the Upgrade of SOA Instance Data.
If you are running the Upgrade Assistant from an Oracle home that contains managed WebLogic domain components, then the All Configurations Used by a Domain upgrade option is available.
After upgrading the component schemas, you must run the Reconfiguration Wizard to reconfigure the domain. For more information, see "Reconfiguring an Oracle WebLogic Domain with the Reconfiguration Wizard". After the reconfiguring the domain, use the Upgrade Assistant again to upgrade the component configurations as described in this section.
The Upgrade Assistant will display the following screens when upgrading a WebLogic component configurations, such as Oracle Web Services Manager (OWSM).
Table 1-3 Upgrade Assistant Screens: Upgrading Oracle WebLogic Component Configurations
| Screen | When Screen Appears | Description |
|---|---|---|
|
Always. |
This screen provides an overview of the Upgrade Assistant and some information about important pre-upgrade tasks. |
|
|
When All Configurations Used by a Domain is selected as the upgrade type, the screen name is WebLogic Components. |
Select the All Configurations Used by a Domain option to upgrade component configurations for a managed WebLogic Server domain. Configuration upgrades are offline in 12.2.1. You must enter the domain directory for the domain that you are upgrading now. |
|
|
Only when the All Configurations Used by a Domain option is selected. |
This screen provides a list of components that will be included in the WebLogic domain's component configuration upgrade. The name of the domain is provided along with the list of components located within the domain. |
|
|
Always. |
This screen requires you to acknowledge that all prerequisites have been met before you continue with the upgrade. You must check the boxes before you can continue. |
|
|
Only when there are remote managed servers hosting UMS 11g configuration files, that is, when the required configuration files are not locally accessible at the Administration Server. |
This screen specifies the login credentials of the remote managed servers hosting your UMS 11g configuration files. The Upgrade Assistant automatically copies remote configuration files if all necessary prerequisites are met and the required login information is provided. |
|
|
Always. |
This screen displays the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade. |
|
|
Always. |
Use this screen to review a summary of the options you have selected and to start the upgrade process. |
|
|
Always. |
This screen shows the status of the upgrade process. |
|
|
Or |
Always. |
The upgrade was successful. The Post-Upgrade Actions window describes the manual tasks you must perform to make the component function in the new installation. Or: The upgrade failed for the specified component(s) and Upgrade Assistant will have to be restarted. |
The following topics provide information about basic tasks performed after the upgrade is complete. Some of the tasks may not apply to your environment, as you may not be upgrading the products listed.
Always refer to your component-specific upgrade documentation for more information on post-upgrade procedures.
NOTE: You should be able to successfully complete the tasks described in this section after an upgrade. If you are unable to complete one or more of these tasks in your newly upgraded environment, see Troubleshooting Your Upgrade .
This section describes some common administration tasks you will likely want to perform on your newly upgraded domain.
NOTE: The administrative tasks in the table below are optional. Only perform those tasks that apply to your upgraded environment.
Table 1-4 Basic Post-Upgrade Administration Tasks
| Task | Description | More Information |
|---|---|---|
|
Starting and stopping products and servers |
Learn how to start and stop Oracle Fusion Middleware, including the Administration Server, Managed Servers, and components. Performing these tasks will validate that the upgrade was successful. |
|
|
Starting and stopping upgraded applications. |
Learn how to start your upgraded applications in the new 12.2.1 environment to verify they are working as expected. |
|
|
Configuring Secure Sockets Layer (SSL) |
Learn how to set up secure communications among between Oracle Fusion Middleware components using SSL. |
|
|
Deploying Applications |
Learn how to deploy your applications to Oracle Fusion Middleware. |
|
|
Monitoring Oracle Fusion Middleware |
Learn how to keep track of the status of Oracle Fusion Middleware components. |
|
|
Adding a Web Tier front-end to your WebLogic domain |
Oracle Web Tier hosts Web pages (static and dynamic), provides security and high performance along with built-in clustering, load balancing, and failover features. In particular, the Web Tier contains Oracle HTTP Server. |
|
|
Tuning and configuring Coherence for your topology. |
The standard installation topology includes a Coherence cluster that contains storage-enabled Managed Coherence Servers. This configuration is a good starting point for using Coherence, but depending upon your specific requirements, consider tuning and reconfiguring Coherence to improve performance in a production environment. |
For information about Coherence clusters, see "Configuring and Managing Coherence Clusters" For information about tuning Coherence, see Administering Oracle Coherence. For information about storing HTTP session data in Coherence, see "Using Coherence*Web with WebLogic Server". For more information about creating and deploying Coherence applications, see Developing Oracle Coherence Applications for Oracle WebLogic Server. |
You can use the following SQL command to verify that the schema version in schema_version_registry has been properly upgraded:
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 ;
All the numbers in the "VERSION" column should be the versions specified during your pre-upgrade check . For more information, see Identifying Schemas that Can be Upgraded with the Upgrade Assistant.
In the query results, the STATUS field will be either "UPGRADING" or "UPGRADED" during the schema patching operation, and will become "VALID" when the operation is finished.
If the status appears as "INVALID" then the schema upgrade failed. You should examine the logs files to determine the reason for the failure.
If you are using an Oracle database, you should recompile database objects after running the Upgrade Assistant by connecting to the database as SYS and running the following from SQL*Plus:
SQL>@/rdbms/admin/utlrp.sql
This will compile the database objects that were upgraded by Upgrade Assistant.
Then issue the following query to ensure there are no longer any invalid database objects:
SELECT owner, object_name FROM all_objects WHERE status='INVALID';
None of the database objects for the upgraded schema should be invalid at this point. If there are any, run the utlrp.sql command again and check again. If the problem persists, you should file a service request.
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. These schemas were not part of the 11.1.1.6 or 11.1.1.7 schema_version_registry table.
As of release 11.1.1.7, OPSS audit data is stored in IAU common tables instead of the JPS table. When upgrading _OPSS schemas to 12.2.1 from 11.1.1.6, any existing data in the JPS table can remain unchanged for reporting or auditing purposes, and there is no need to upgrade JPS table with extra columns.
First release to support Edition-Based Redefinition (EBR) enabled schemas
First release to support Edition-Based Redefinition (EBR) enabled schemas