Upgrading SOA Suite and Business Process Management

3 Upgrading SOA Suite and Business Process Management

This section provides the end-to-end procedure for upgrading a SOA Suite with Business Process Management production installation to SOA Suite with Business Process Management 14c (14.1.2.0.0).

Note:

Oracle strongly recommends that you create a copy of your actual production environment, upgrade the cloned environment, verify that the upgraded components work as expected, and then (and only then) upgrade your production environment.

Identifying potential upgrade issues in a cloned environment can eliminate unnecessary downtime of your production environment.

About the SOA Suite and BPM Upgrade Process Flow

This flowchart and the accompanying text describe the high-level steps for upgrading the Oracle Fusion Middleware SOA Suite 12c (12.2.1.4 ) to 14c (14.1.2.0.0).

The steps you take to upgrade your existing domain will vary depending on how your domain is configured and which components are being upgraded. Follow only those steps that are applicable to your deployment.

Figure 3-1 Upgrade Process Flowchart for SOA Suite and BPM

Description of "Figure 3-1 Upgrade Process Flowchart for SOA Suite and BPM"

Table 3-1 Task Descriptions for Upgrading Oracle SOA Suite

Description	More Information
Required If you have not done so already, perform all of the required pre-upgrade tasks for the components you are upgrading.	CAUTION: Be sure to create a complete backup of your existing domain before you begin the upgrade.
Required Create a new 14c (14.1.2.0.0) Oracle home on the target host.	Create a directory for the 14c (14.1.2.0.0) binaries, for example: `1412_ORACLE_HOME`
Required You must install Fusion Middleware Infrastructure 14c (14.1.2.0.0) in a NEW Oracle home before you begin the upgrade.	CAUTION: Install the product distributions but do not use the Configuration Wizard to configure the newly installed domain. You will use the Reconfiguration Wizard during the upgrade to configure the existing domain.
Required Install SOA Suite and Business Process Management 14c (14.1.2.0.0) and any integrated SOA-integrated distributions (such as Oracle HTTP Server and Oracle Service Bus) in your newly created Oracle home.	You must install the Fusion Middleware 14c (14.1.2.0.0) distributions for each SOA-integrated product you are upgrading. For example, if you are upgrading a SOA environment with Oracle Service Bus, you must acquire the Oracle Service Bus distribution as well as the Oracle SOA Suite and BPM 14c (14.1.2.0.0) distribution.
Optional Run a pre-upgrade readiness check with the Upgrade Assistant	Run the Upgrade Assistant in Readiness Mode before you begin the upgrade to identify any potential issues with the pre-upgrade environment that could cause the upgrade to fail. If necessary, fix the issues and run the readiness check again.
Required Stop all Administration and Managed Servers.	WARNING: Failure to shut down your servers during an upgrade may lead to data corruption.
Required Run the Upgrade Assistant to upgrade the database schemas and to migrate all active (in flight) instance data.	The Upgrade Assistant will detect missing schemas and attempt to create them for you. These schemas are created using the default schema settings and cannot be modified. If you require specific settings for your schemas, use the Repository Creation Utility (RCU). NOTE: The upgrade of active instance data is started automatically when running the Upgrade Assistant. Once the data is successfully upgraded to the new 14c (14.1.2.0.0) environment, you can close the Upgrade Assistant. The closed instances will continue to upgrade through a background process.
Required Run the Reconfiguration Wizard to reconfigure the domain and node manager.	Use the Reconfiguration Wizard to update the existing domain to use the newly installed software.
Required Run the Upgrade Assistant (again) to upgrade domain configurations.	The Upgrade Assistant is used to update the reconfigured domain’s component configurations.
Required Perform the required post-upgrade configuration tasks (if needed).	Your components may not require any additional post-upgrade procedures.
Required As part of the upgrade verification process, Oracle recommends that you start the new Administration and Managed Servers and node manager to ensure there are no issues.	Oracle recommends that you ensure all of the upgraded components are working as expected before deleting your backups.
Required for Cluster Upgrades Once you have verified that the upgrade was successful, you will need to propagate the environment to the other host.	Propagating Domain Configuration to Another Host

Installing the 14c (14.1.2.0.0) Product Distributions for Oracle SOA Suite and Business Process Management

Before beginning your upgrade, use the Oracle Universal Installer to install the Oracle Fusion Middleware Infrastructure distribution, the Oracle SOA Suite and Business Process Management 14c (14.1.2.0.0) distribution, and any other SOA Suite products on the target system.

Note:

When Infrastructure is required for the upgrade, you must install the Oracle Fusion Middleware Infrastructure distribution first before you install other Fusion Middleware products. If your JDK is not supported, or you do not have a JDK installed, you must download the required Java SE JDK before you begin

Before you begin, note the following:

You must install the 14c (14.1.2.0.0) distributions into a new Oracle home. Do not attempt to reuse the existing Oracle home for this upgrade. Upgrading to 14c (14.1.2.0.0) is not a patch release.
Oracle SOA Suite requires the Oracle Fusion Middleware Infrastructure (Oracle WebLogic Server and JRF).

Installing Fusion Middleware Infrastructure creates an Oracle home directory and lays supporting software to install other Fusion Middleware products.

If your SOA domain has other SOA-integrated components, such as Oracle Service Bus, Managed File Transfer, or Oracle B2B, you must install those distributions into the same new Oracle home. Oracle Business Activity Monitoring and Business Process Management are part of the generic SOA distribution.

To install the Oracle SOA Suite component distributions:

Sign in to the target system.
Download the following distributions from Oracle Technology Network or Oracle Software Delivery Cloud to your target system:
- Fusion Middleware Infrastructure distribution (fmw_14.1.2.0.0_infrastructure_generic.jar)
- Fusion Middleware SOA Suite and Business Process Management distribution (fmw_14.1.2.0.0_soa_generic.jar)
- If you are running Managed File Transfer, Oracle Service Bus or Oracle B2B, download the Managed File Transfer distribution (fmw_14.1.2.0.0_mft_generic.jar), Oracle Service Bus (fmw_14.1.2.0.0_osb_generic.jar), and Oracle B2B (fmw_14.1.2.0.0_b2b_generic.jar)
Change to the directory where you downloaded the 14c (14.1.2.0.0) product distribution.
Start the installation program for Oracle Fusion Middleware Infrastructure:
- (UNIX) JDK_HOME/bin/java -jar fmw_14.1.2.0.0_infrastructure_generic.jar
- (Windows) JDK_HOME\bin\java -jar fmw_14.1.2.0.0_infrastructure_generic.jar

Note:

When you install the Oracle Fusion Middleware Release 14c (14.1.2.0.0) software in preparation for upgrade, you should use the same user account that you used to install and configure the existing, pre-upgrade Oracle Fusion Middleware software. On UNIX operating systems, this ensures that the proper owner and group is applied to new Oracle Fusion Middleware 14c (14.1.2.0.0) files and directories.

On UNIX operating systems, the Installation Inventory Setup screen appears if this is the first time you are installing an Oracle product on this host.
Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location, and click Next.

Note:
The Installation Inventory Setup screen does not appear on Windows operating systems.
On the Welcome screen, review the information to make sure that you have met all the prerequisites. Click Next.
On the Auto Updates screen, select an option:
- Skip Auto Updates: If you do not want your system to check for software updates at this time.
- Select patches from directory: To navigate to a local directory if you downloaded patch files.
- Search My Oracle Support for Updates: To automatically download software updates if you have a My Oracle Support account. You must enter Oracle Support credentials then click Search. To configure a proxy server for the installer to access My Oracle Support, click Proxy Settings. Click Test Connection to test the connection.
Click Next.
On the Installation Location screen, specify the location for the Oracle home directory and click Next.
For more information about Oracle Fusion Middleware directory structure, see Understanding Directories for Installation and Configuration in Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware.
On the Installation Type screen, select the product(s) to install. Product dependencies will be automatically selected, and click Next.
The Prerequisite Checks screen analyzes the host computer to ensure that the specific operating system prerequisites have been met.
To view the list of tasks that are verified, select View Successful Tasks. To view log details, select View Log. If any prerequisite check fails, then an error message appears at the bottom of the screen. Fix the error and click Rerun to try again. To ignore the error or the warning message and continue with the installation, click Skip (not recommended).
On the Installation Summary screen, verify the installation options that you selected.
If you want to save these options to a response file, click Save Response File and enter the response file location and name. The response file collects and stores all the information that you have entered, and enables you to perform a silent installation (from the command line) at a later time.
Click Install to begin the installation.
On the Installation Progress screen, when the progress bar displays 100%, click Finish to dismiss the installer, or click Next to see a summary.
The Installation Complete screen displays the Installation Location and the Feature Sets that are installed. Review this information and click Finish to close the installer.
After you have installed the Infrastructure, repeat steps 3 through 13 to install the other product distributions.

Running a Pre-Upgrade Readiness Check

To identify potential issues with the upgrade, Oracle recommends that you run a readiness check before you start the upgrade process. Be aware that the readiness check may not be able to discover all potential issues with your upgrade. An upgrade may still fail, even if the readiness check reports success.

About Running a Pre-Upgrade Readiness Check

You can run the Upgrade Assistant in -readiness mode to detect issues before you perform the actual upgrade. You can run the readiness check in GUI mode using the Upgrade Assistant or in silent mode using a response file.

The Upgrade Assistant readiness check performs a read-only, pre-upgrade review of your Fusion Middleware schemas and WebLogic domain configurations that are at a supported starting point. The review is a read-only operation.

The readiness check generates a formatted, time-stamped readiness report so you can address potential issues before you attempt the actual upgrade. If no issues are detected, you can begin the upgrade process. Oracle recommends that you read this report thoroughly before performing an upgrade.

You can run the readiness check while your existing Oracle Fusion Middleware domain is online (while other users are actively using it) or offline.

You can run the readiness check any number of times before performing any actual upgrade. However, do not run the readiness check after an upgrade has been performed, as the report results may differ from the result of pre-upgrade readiness checks.

Note:

To prevent performance from being affected, Oracle recommends that you run the readiness check during off-peak hours.

Starting the Upgrade Assistant in Readiness Mode

Use the -readiness parameter to start the Upgrade Assistant in readiness mode.

To perform a readiness check on your pre-upgrade environment with the Upgrade Assistant:

Go to the oracle_common/upgrade/bin directory:
- (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
- (Windows) ORACLE_HOME\oracle_common\upgrade\bin
Start the Upgrade Assistant.
- (UNIX) ./ua -readiness
- (Windows) ua.bat -readiness
Note:
If the DISPLAY environment variable is not set up properly to allow for GUI mode, you may encounter the following error:
```
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified 
```
To resolve this issue, set the DISPLAY environment variable to the system name or IP address of your local workstation, and rerun Upgrade Assistant.

If you continue to receive these errors after setting DISPLAY, try launching another GUI tool, such as vncconfig. If you see the same errors, your DISPLAY environment variable may still not be set correctly.
For information about other parameters that you can specify on the command line, see:

Upgrade Assistant Parameters

When you start the Upgrade Assistant from the command line, you can specify additional parameters.

Table 3-2 Upgrade Assistant Command-Line Parameters

Parameter	Required or Optional	Description
`-readiness`	Required for readiness checks Note: Readiness checks cannot be performed on standalone installations (those not managed by the WebLogic Server).	Performs the upgrade readiness check without performing an actual upgrade. Schemas and configurations are checked. Do not use this parameter if you have specified the `-examine` parameter.
`-threads`	Optional	Identifies the number of threads available for concurrent schema upgrades or readiness checks of the schemas. The value must be a positive integer in the range 1 to 8. The default is 4.
`-response`	Required for silent upgrades or silent readiness checks	Runs the Upgrade Assistant using inputs saved to a response file generated from the data that is entered when the Upgrade Assistant is run in GUI mode. Using this parameter runs the Upgrade Assistant in silent mode (without displaying Upgrade Assistant screens).
`-examine`	Optional	Performs the examine phase but does not perform an actual upgrade. Do not specify this parameter if you have specified the `-readiness` parameter.
`-logLevel attribute`	Optional	Sets the logging level, specifying one of the following attributes: `TRACE` `NOTIFICATION` `WARNING` `ERROR` `INCIDENT_ERROR` The default logging level is `NOTIFICATION`. Consider setting the `-logLevel TRACE` attribute to so that more information is logged. This is useful when troubleshooting a failed upgrade. The Upgrade Assistant's log files can become very large if `-logLevel TRACE` is used.
`-logDir location`	Optional	Sets the default location of upgrade log files and temporary files. You must specify an existing, writable directory where the Upgrade Assistant creates log files and temporary files. The default locations are: (UNIX) `ORACLE_HOME/oracle_common/upgrade/logs` `ORACLE_HOME/oracle_common/upgrade/temp` (Windows) `ORACLE_HOME\oracle_common\upgrade\logs` `ORACLE_HOME\oracle_common\upgrade\temp`
`-help`	Optional	Displays all of the command-line options.

Performing a Readiness Check with the Upgrade Assistant

Navigate through the screens in the Upgrade Assistant to complete the pre-upgrade readiness check.

Readiness checks are performed only on schemas or component configurations that are at a supported upgrade starting point.

To complete the readiness check:

On the Welcome screen, review information about the readiness check. Click Next.
On the Readiness Check Type screen, select the readiness check that you want to perform:
- Individually Selected Schemas allows you to select individual schemas for review before upgrade. The readiness check reports whether a schema is supported for an upgrade or where an upgrade is needed.
  When you select this option, the screen name changes to Selected Schemas.
- Domain Based allows the Upgrade Assistant to discover and select all upgrade-eligible schemas or component configurations in the domain specified in the Domain Directory field.
  When you select this option, the screen name changes to Schemas and Configuration.
  Leave the default selection if you want the Upgrade Assistant to check all schemas and component configurations at the same time, or select a specific option:
  - Include checks for all schemas to discover and review all components that have a schema available to upgrade.
  - Include checks for all configurations to review component configurations for a managed WebLogic Server domain.
Click Next.
If you selected Individually Selected Schemas: On the Available Components screen, select the components that have a schema available to upgrade for which you want to perform a readiness check.
If you selected Domain Based: On the Component List screen, review the list of components that are present in your domain for which you want to perform a readiness check.

If you select a component that has dependent components, those components are automatically selected. For example, if you select Oracle Platform Security Services, Oracle Audit Services is automatically selected.
Depending on the components you select, additional screens may display. For example, you may need to:
- Specify the domain directory.
- Specify schema credentials to connect to the selected schema: Database Type, DBA User Name, and DBA Password. Then click Connect.
  
  Note:
  Oracle database is the default database type. Make sure that you select the correct database type before you continue. If you discover that you selected the wrong database type, do not go back to this screen to change it to the correct type. Instead, close the Upgrade Assistant and restart the readiness check with the correct database type selected to ensure that the correct database type is applied to all schemas.
- Select the Schema User Name option and specify the Schema Password.
  
  Note:
  The Upgrade Assistant automatically enables default credentials. If you are unable to connect, make sure that you manually enter the credentials for your schema before you continue.
Click Next to start the readiness check.
On the Readiness Summary screen, review the summary of the readiness checks that will be performed based on your selections.
If you want to save your selections to a response file to run the Upgrade Assistant again later in response (or silent) mode, click Save Response File and provide the location and name of the response file. A silent upgrade performs exactly the same function that the Upgrade Assistant performs, but you do not have to manually enter the data again.

For a detailed report, click View Log.

Click Next.
On the Readiness Check screen, review the status of the readiness check. The process can take several minutes.
If you are checking multiple components, the progress of each component displays in its own progress bar in parallel.

When the readiness check is complete, click Continue.
On the End of Readiness screen, review the results of the readiness check (Readiness Success or Readiness Failure):
- If the readiness check is successful, click View Readiness Report to review the complete report. Oracle recommends that you review the Readiness Report before you perform the actual upgrade even when the readiness check is successful. Use the Find option to search for a particular word or phrase within the report. The report also indicates where the completed Readiness Check Report file is located.
- If the readiness check encounters an issue or error, click View Log to review the log file, identify and correct the issues, and then restart the readiness check. The log file is managed by the command-line options you set.

Understanding the Readiness Report

After performing a readiness check for your domain, review the report to determine whether you need to take any action for a successful upgrade.

The format of the readiness report file is:

readiness<timestamp>.txt

Where, timestamp indicates the date and time of when the readiness check was run.

A readiness report contains the following information:

Table 3-3 Readiness Report Elements

Report Information	Description	Required Action
Overall Readiness Status: SUCCESS or FAILURE	The top of the report indicates whether the readiness check passed or completed with one or more errors.	If the report completed with one or more errors, search for FAIL and correct the failing issues before attempting to upgrade. You can re-run the readiness check as many times as necessary before an upgrade.
Timestamp	The date and time that the report was generated.	No action required.
Log file location `/oracle_common/upgrade/logs`	The directory location of the generated log file.	No action required.
Domain Directory	Displays the domain location	No action required.
Readiness report location `/oracle_common/upgrade/logs`	The directory location of the generated readiness report.	No action required.
Names of components that were checked	The names and versions of the components included in the check and status.	If your domain includes components that cannot be upgraded to this release, such as SOA Core Extension, do not attempt an upgrade.
Names of schemas that were checked	The names and current versions of the schemas included in the check and status.	Review the version numbers of your schemas. If your domain includes schemas that cannot be upgraded to this release, do not attempt an upgrade.
Individual Object Test Status: FAIL	The readiness check test detected an issue with a specific object.	Do not upgrade until all failed issues have been resolved.
Individual Object Test Status: PASS	The readiness check test detected no issues for the specific object.	If your readiness check report shows only the PASS status, you can upgrade your environment. Note, however, that the Readiness Check cannot detect issues with externals such as hardware or connectivity during an upgrade. You should always monitor the progress of your upgrade.
Completed Readiness Check of <Object> Status: FAILURE	The readiness check detected one or more errors that must be resolved for a particular object such as a schema, an index, or datatype.	Do not upgrade until all failed issues have been resolved.
Completed Readiness Check of <Object> Status: SUCCESS	The readiness check test detected no issues.	No action required.

Stopping Servers and Processes

Before you run the Upgrade Assistant to upgrade your schemas and configurations, you must shut down all of the pre-upgrade processes and servers, including the Administration Server and any managed servers.

An Oracle Fusion Middleware environment can consist of an Oracle WebLogic Server domain, an Administration Server, multiple managed servers, Java components, system components, and a database used as a repository for metadata. The components may be dependent on each other, so they must be stopped in the correct order.

Note:

The procedures in this section describe how to stop the existing, pre-upgrade servers and processes using the WLST command-line utility or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Remote Console. See Starting and Stopping Administration and Managed Servers and Node Manager.

As of release 14c (14.1.2.0.0), the WebLogic Server Administration Console has been removed. For comparable functionality, you should use the WebLogic Remote Console. For more information, see Oracle WebLogic Remote Console.

To stop your pre-upgrade Fusion Middleware environment, navigate to the pre-upgrade domain and follow the steps below:

Note:

It is important that you stop the following servers in the correct order.

Step 1: Stop System Components

To stop system components, such as Oracle HTTP Server, use the stopComponent script:

(UNIX) EXISTING_DOMAIN_HOME/bin/stopComponent.sh component_name
(Windows) EXISTING_DOMAIN_HOME\bin\stopComponent.cmd component_name

You can stop system components in any order.

Step 2: Stop Any Managed Servers

To stop a WebLogic Server Managed Server, use the stopManagedWebLogic script:

(UNIX) EXISTING_DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url
(Windows) EXISTING_DOMAIN_HOME\bin\stopManagedWebLogic.cmd managed_server_name admin_url

When prompted, enter your user name and password.

Stop SOA servers and processes in this order:

Business Activity Monitoring (BAM) Managed Server
Oracle Service Bus (OSB) Managed Server
Service-Oriented Architecture (SOA) Managed Server
Oracle Web Services Manager (OWSM) Managed Server

Step 3: Stop the Administration Server

To stop the Administration Server, use the stopWebLogic script:

(UNIX) EXISTING_DOMAIN_HOME/bin/stopWebLogic.sh
(Windows) EXISTING_DOMAIN_HOME\bin\stopWebLogic.cmd

When prompted, enter your user name, password, and the URL of the Administration Server.

Step 4: Stop Node Manager

To stop Node Manager, close the command shell in which it is running.

Alternatively, after setting the nodemanager.properties attribute QuitEnabled to true (the default is false), you can use WLST to connect to Node Manager and shut it down. See stopNodeManager in WLST Command Reference for Oracle WebLogic Server.

Upgrading Schemas with the Upgrade Assistant

If you are upgrading non-partitioned schemas, follow the steps described in Upgrading Schemas with the Upgrade Assistant. If you are upgrading partioned schemas, follow the steps described in Upgrading Partitioned Schemas.

Note:

Make sure that you select the procedure for your schema configuration. Partitioned schemas cannot be upgraded using the Upgrade Assistant.

Upgrading Product Schemas

After stopping servers and processes, use the Upgrade Assistant to upgrade your 12.2.1.4.0 schemas to the 14c (14.1.2.0.0) release of Oracle Fusion Middleware.

Note:

If your domain has the WLSSchemaDataSource data source, then you will need to verify which database user is assigned to it. If <PREFIX>_WLS_RUNTIME is assigned to it, then you need to change that to <PREFIX>_WLS . For more information, see Verify the Database User for the WLSSchemaDataSource Data Source.

Note:

As of 14c (14.1.2.0.0) the following schema changes have been made to help you prepare for an optional zero downtime upgrade to a future release:

Schemas created prior to 14c (14.1.2.0.0) with editions disabled and then upgraded to 14c (14.1.2.0.0) will become editions enabled.
Schemas created in 14c (14.1.2.0.0) will be created with editions enabled.

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.

Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 14c (14.1.2.0.0).

To start the Upgrade Assistant:

Note:

Before you start the Upgrade Assistant, make sure that the JVM character encoding is set to UTF-8 for the platform on which the Upgrade Assistant is running. If the character encoding is not set to UTF-8, then you will not be able to download files containing Unicode characters in their names. This can cause the upgrade to fail. To set the character encoding, run the following:

UNIX operating systems:

export UA_PROPERTIES="-Dfile.encoding=UTF-8 ${UA_PROPERTIES}"

Windows operating systems:

set UA_PROPERTIES=-Dfile.encoding=UTF-8 %UA_PROPERTIES%

Go to the oracle_common/upgrade/bin directory:
- (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
- (Windows) ORACLE_HOME\oracle_common\upgrade\bin
Start the Upgrade Assistant:
- (UNIX) ./ua
- (Windows) ua.bat

For information about other parameters that you can specify on the command line, such as logging parameters, see:

Upgrade Assistant Parameters

When you start the Upgrade Assistant from the command line, you can specify additional parameters.

Table 3-4 Upgrade Assistant Command-Line Parameters

Parameter	Required or Optional	Description
`-readiness`	Required for readiness checks Note: Readiness checks cannot be performed on standalone installations (those not managed by the WebLogic Server).	Performs the upgrade readiness check without performing an actual upgrade. Schemas and configurations are checked. Do not use this parameter if you have specified the `-examine` parameter.
`-threads`	Optional	Identifies the number of threads available for concurrent schema upgrades or readiness checks of the schemas. The value must be a positive integer in the range 1 to 8. The default is 4.
`-response`	Required for silent upgrades or silent readiness checks	Runs the Upgrade Assistant using inputs saved to a response file generated from the data that is entered when the Upgrade Assistant is run in GUI mode. Using this parameter runs the Upgrade Assistant in silent mode (without displaying Upgrade Assistant screens).
`-examine`	Optional	Performs the examine phase but does not perform an actual upgrade. Do not specify this parameter if you have specified the `-readiness` parameter.
`-logLevel attribute`	Optional	Sets the logging level, specifying one of the following attributes: `TRACE` `NOTIFICATION` `WARNING` `ERROR` `INCIDENT_ERROR` The default logging level is `NOTIFICATION`. Consider setting the `-logLevel TRACE` attribute to so that more information is logged. This is useful when troubleshooting a failed upgrade. The Upgrade Assistant's log files can become very large if `-logLevel TRACE` is used.
`-logDir location`	Optional	Sets the default location of upgrade log files and temporary files. You must specify an existing, writable directory where the Upgrade Assistant creates log files and temporary files. The default locations are: (UNIX) `ORACLE_HOME/oracle_common/upgrade/logs` `ORACLE_HOME/oracle_common/upgrade/temp` (Windows) `ORACLE_HOME\oracle_common\upgrade\logs` `ORACLE_HOME\oracle_common\upgrade\temp`
`-help`	Optional	Displays all of the command-line options.

Upgrading SOA Schemas Using the Upgrade Assistant

Navigate through the screens in the Upgrade Assistant to upgrade the product schemas.

Caution: Complete all required prerequisites before you begin the upgrade. For example, as of 14.1.2.0.0 if your existing domain has a WLSSchemaDataSource data source, then you must verify which database user is assigned to it. If <PREFIX>_WLS_RUNTIME is assigned to it, then you need to change that to <PREFIX>_WLS. For more information see Verify the Database User for the WLSSchemaDataSource Data Source.

To upgrade product schemas with the Upgrade Assistant:

On the Welcome screen, review an introduction to the Upgrade Assistant and information about important pre-upgrade tasks. Click Next.

Note:
For more information about any Upgrade Assistant screen, click Help on the screen.
On the Selected Schemas screen, select the schema upgrade operation that you want to perform:
- All Schemas Used by a Domain to allow the Upgrade Assistant to discover and select all components that have a schema available to upgrade in the domain specified in the Domain Directory field. This is also known as a domain assisted schema upgrade. Additionally, the Upgrade Assistant pre-populates connection information on the schema input screens.
  
  Note:
  Oracle recommends that you select All Schemas Used by a Domain for most upgrades to ensure all of the required schemas are included in the upgrade.
- Individually Selected Schemas if you want to select individual schemas for upgrade and you do not want to upgrade all of the schemas used by the domain.
  
  Caution:
  Upgrade only those schemas that are used to support your 14c (14.1.2.0.0) components. Do not upgrade schemas that are currently being used to support components that are not included in Oracle Fusion Middleware 14c (14.1.2.0.0).
Click Next.
If you selected Individually Selected Schemas: On the Available Components screen, select the components for which you want to upgrade schemas. When you select a component, the schemas and any dependencies are automatically selected.

For example, when Oracle SOA is selected, the Oracle SOA (_SOAINFRA), Audit Services (_IAU), Metadata Service (_MDS), Oracle Platform Security Services(_OPSS), and User Messaging Services (_UMS) schemas will be included in the upgrade.

When Managed File Transfer is selected, Audit Services (_IAU), Enterprise Scheduler (_ESS) and Platform Security Services (OPSS) will be included in the upgrade.
The Domain Directory screen appears when Oracle Platform Security Services or Oracle Audit Services is selected on the Available Components screen. Enter the absolute path to the existing WebLogic domain directory, or click Browse to navigate to and select the domain directory you are upgrading
On the Prerequisites screen, acknowledge that the prerequisites have been met by selecting all the check boxes. Click Next.

Note:
The Upgrade Assistant does not verify whether the prerequisites have been met.

On the Schema Credentials screen(s), specify the database connection details for each schema you are upgrading (the screen name changes based on the schema selected):

Element	Description
Database Type	The database type chosen for upgrade must be identical to the database type that was selected when RCU originally created the schema. If you select Oracle Edition-Based Redefinition (EBR) as the database type, the schema that you are upgrading also must have been created by RCU as the EBR database type. In particular, Upgrade Assistant never converts schemas from one database type to another.
Edition Name	For database type "Oracle Database enabled for edition-based redefinition" (EBR database) you will need to enter the name of an existing Edition in the Edition Name element field. The database schema upgrade will occur in the edition you have chosen.
Database Connect String	Enter the location of the database. For example, if you are selecting an Oracle database, the following URL format could be used: host:port/db_service_name Review the Fusion Middleware database requirements before starting the upgrade to ensure that the database hosting Oracle Fusion Middleware is supported and has sufficient space to perform an upgrade. See the Certification Matrix for 14c (14.1.2.0.0). Note: If your database version is no longer supported, you must upgrade to a supported version before starting an upgrade.
DBA User Name	Enter the database user name used to connect to the database. Oracle Database Users Only: If SSL authentication is used, then the DBA User Name field may be optional. If you do provide a DBA User Name, then the information will be used during the database authentication. For Oracle database users, if you are not running as SYS or SYSDBA, then user of Upgrade Assistant must have all of the privileges granted in the FMW user account. Refer to your component-specific upgrade documentation for more information on creating a non-sysdba user to run Upgrade Assistant.
DBA Password	Enter the password associated with the specified DBA database user. Oracle Database Users Only: If SSL authentication is used, then the DBA Password field may be optional. If you do provide a DBA user name and password, then the information will be used during the database authentication.
Schema User Name	Select the schema you want to upgrade from the Schema User Name drop-down menu, and then enter the password for the schema. Be sure to use the correct schema prefix for the schemas you are upgrading.
Schema Password	Enter the password associated with the specified schema user name.

On the Examine screen, review the status of the Upgrade Assistant as it examines each schema, verifying that the schema is ready for upgrade. If the status is Examine finished, click Next.
If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No in the Examination Failure dialog. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade in Upgrading with the Upgrade Assistant for information on resolving common upgrade errors.
Note:
- If you resolve any issues detected during the examine phase without proceeding with the upgrade, you can start the Upgrade Assistant again without restoring from backup. However, if you proceed by clicking Yes in the Examination Failure dialog box, you need to restore your pre-upgrade environment from backup before starting the Upgrade Assistant again.
- Canceling the examination process has no effect on the schemas or configuration data; the only consequence is that the information the Upgrade Assistant has collected must be collected again in a future upgrade session.
On the Upgrade Summary screen, review the summary of the schemas that will be upgraded and/or created.
Verify that the correct Source and Target Versions are listed for each schema you intend to upgrade.

If you want to save these options to a response file to run the Upgrade Assistant again later in response (or silent) mode, click Save Response File and provide the location and name of the response file. A silent upgrade performs exactly the same function that the Upgrade Assistant performs, but you do not have to manually enter the data again.

Click Next .
On the Upgrade Progress screen, monitor the status of the upgrade.

Caution:
Allow the Upgrade Assistant enough time to perform the upgrade. Do not cancel the upgrade operation unless absolutely necessary. Doing so may result in an unstable environment.

If any schemas are not upgraded successfully, refer to the Upgrade Assistant log files for more information.

Note:
The progress bar on this screen displays the progress of the current upgrade procedure. It does not indicate the time remaining for the upgrade.

Click Next.
If the upgrade is successful: On the Upgrade Success screen, click Close to complete the upgrade and close the wizard.

If the upgrade fails: On the Upgrade Failure screen, click View Log to view and troubleshoot the errors. The logs are available at NEW_ORACLE_HOME/oracle_common/upgrade/logs.

Note:
If the upgrade fails, you must restore your pre-upgrade environment from backup, fix the issues, then restart the Upgrade Assistant.

Verifying the Schema Upgrade

After completing all the upgrade steps, verify that the upgrade was successful by checking that the schema version in schema_version_registry has been properly updated.

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. Be sure to replace <PREFIX> with your schema prefix.

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, EDITION NAME, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY where owner like '<PREFIX>_%';

In the query result:

Verify that the EDITION NAME column appears as ORA$BASE.
Check that the number in the VERSION column matches the latest version number for that schema. For example, verify that the schema version number is 14.1.2.0.0.

Note:

Not all schema versions will be updated. Some schemas do not require an upgrade to this release and will retain their pre-upgrade version number.
The STATUS field will be either UPGRADING or UPGRADED during the schema patching operation, and will become VALID when the operation is completed.
If the status appears as INVALID, the schema update failed. You should examine the logs files to determine the reason for the failure.
Synonym objects owned by IAU_APPEND and IAU_VIEWER will appear as INVALID, but that does not indicate a failure.

They become invalid because the target object changes after the creation of the synonym. The synonyms objects will become valid when they are accessed. You can safely ignore these INVALID objects.

About Reconfiguring the Domain

Run the Reconfiguration Wizard to reconfigure your domain component configurations to 14c (14.1.2.0.0).

Note:

If the source is a clustered environment, run the Reconfiguration Wizard on the primary node only.

When you reconfigure a WebLogic Server domain, the following items are automatically updated, depending on the applications in the domain:

WebLogic Server core infrastructure
Domain version

Note:

Before you begin the domain reconfiguration, note the following limitations:

The Reconfiguration Wizard does not update any of your own applications that are included in the domain.
Transforming a non-dynamic cluster domain to a dynamic cluster domain during the upgrade process is not supported.

The dynamic cluster feature is available when running the Reconfiguration Wizard, but Oracle only supports upgrading a non-dynamic cluster upgrade and then adding dynamic clusters. You cannot add dynamic cluster during the upgrade process.

If the installation that you’re upgrading does not use Oracle Access Management (OAM), then you must edit two files to prevent the Reconfiguration Wizard from attempting to update the nonexistent OAM Infrastructure schema, which causes the upgrade to fail.

Comment out the lines in your $DOMAIN/init-info/domain-info.xml that are similar to this example:

<!--extention-template-ref name="Oracle Identity Navigator" 
  version="14.1.2.0.0" 
  location="/u01/app/oracle/product/fmw/iam111130/common/templates/applications/yourcomany.oinav_14.1.2.0.0_template.jar" 
  symbol=""/-->

<!--install-comp-ref name="oracle.idm.oinav" version="14.1.2.0.0" 
  symbol="yourcompany.idm.oinav_14.1.2.0.0_iam141200_ORACLE_HOME" 
  product_home="/u01/app/oracle/product/fmw/iam141200"/-->

and similarly comment out the lines in $DOMAIN/config/config.xml that are similar to this example:

<!--app-deployment> 
  <name>oinav#14.1.2.0.0</name>
  <target>AdminServer</target>
  <module-type>ear</module-type>

  <source-path>/u01/app/oracle/product/fmw/iam141200/oinav/modules/oinav.ear_14.1.2.0.0/oinav.ear</source-path>
  <deployment-order>500</deployment-order>
  <security-dd-model>DDOnly</security-dd-model>
  <staging-mode>nostage</staging-mode>
</app-deployment-->

Specifically, when you reconfigure a domain, the following occurs:

The domain version number in the config.xml file for the domain is updated to the Administration Server's installed WebLogic Server version.
Reconfiguration templates for all installed Oracle products are automatically selected and applied to the domain. These templates define any reconfiguration tasks that are required to make the WebLogic domain compatible with the current WebLogic Server version.
Start scripts are updated.

If you want to preserve your modified start scripts, be sure to back them up before starting the Reconfiguration Wizard.

Note:

When the domain reconfiguration process starts, you can’t undo the changes that it makes. Before running the Reconfiguration Wizard, ensure that you have backed up the domain as covered in the pre-upgrade checklist. If an error or other interruption occurs while running the Reconfiguration Wizard, you must restore the domain by copying the files and directories from the backup location to the original domain directory. This is the only way to ensure that the domain has been returned to its original state before reconfiguration.

Backing Up the Domain

Before running the Reconfiguration Wizard, create a backup copy of the domain directory.

Create a backup of the domain directory.
Before updating the domain on each remote Managed Server, create a backup copy of the domain directory on each remote machine.
Verify that the backed up versions of the domain are complete.

If domain reconfiguration fails for any reason, you must copy all files and directories from the backup directory into the original domain directory to ensure that the domain is returned entirely to its original state before reconfiguration.

Starting the Reconfiguration Wizard

Note:

Shut down the administration server and all collocated managed servers before starting the reconfiguration process. See Stopping Servers and Processes.

To start the Reconfiguration Wizard in graphical mode:

Sign in to the system on which the domain resides.
Open the command shell (on UNIX operating systems) or open a command prompt window (on Windows operating systems).
Go to the oracle_common/common/bin directory:
- (UNIX) NEW_ORACLE_HOME/oracle_common/common/bin
- (Windows) NEW_ORACLE_HOME\oracle_common\commom\bin
Start the Reconfiguration Wizard with the following logging options:
- (UNIX) ./reconfig.sh -log=log_file -log_priority=ALL
- (Windows) reconfig.cmd -log=log_file -log_priority=ALL
where log_file is the absolute path of the log file you'd like to create for the domain reconfiguration session. This can be helpful if you need to troubleshoot the reconfiguration process.
The parameter -log_priority=ALL ensures that logs are logged in fine mode.
Note:

When you run this command, the following error message might appear to indicate that the default cache directory is not valid:
```
*sys-package-mgr*: can't create package cache dir
```
You can change the cache directory by setting the environment variable CONFIG_JVM_ARGS. For example:

CONFIG_JVM_ARGS=-Dpython.cachedir=valid_directory

Reconfiguring the SOA Domain with the Reconfiguration Wizard

You must first reconfigure your existing domain using the Reconfiguration Wizard before running the Upgrade Assistant to configure domain component configurations.

Note:

If the source is a clustered environment, run the Reconfiguration Wizard on the primary node only. Use the pack/unpack utility to apply the changes to other cluster members in the domain.

To reconfigure the domain:

On the Select Domain screen, specify the location of the domain you want to upgrade or click Browse to navigate and select the domain directory. Click Next.
On the Reconfiguration Setup Progress screen, view the progress of the setup process. When complete, click Next.
During this process:
- The reconfiguration templates for your installed products, including Fusion Middleware products, are automatically applied. This updates various domain configuration files such as config.xml, config-groups.xml, and security.xml (among others).
- Scripts and other files that support your Fusion Middleware products are updated.
- The domain upgrade is validated.
On the Domain Mode and JDK screen, select the JDK to use in the domain or click Browse to navigate to the JDK you want to use. The supported JDK version for 14c (14.1.2.0.0) is 17.0.12 and later. Click Next.

Note:
You cannot change the Domain Mode at this stage. Your domain will retain its pre-upgrade domain mode. If you want to change the domain to secure mode, then after the upgrade see Changing Domain Mode Post Upgrade.

For a list of JDKs that are supported for a specific platform, see Oracle Fusion Middleware Supported System Configurations.
On the Database Configuration Type screen, select RCU Data to connect to the Server Table (<PREFIX>_STB) schema.
Note: <PREFIX> is the RCU schema prefix of the 12.2.1.4 domain that is being upgraded.

Enter the database connection details using the RCU service table (<PREFIX>_STB) schema credentials and click Get RCU Configuration.

The Reconfiguration Wizard uses this connection to automatically update the data sources required for components in your domain.

Note:
By default Oracle’s Driver (Thin) for Service connections; Versions: Any is the selected driver. If you specified an instance name in your connection details — instead of the service name — you must select Oracle’s Driver (Thin) for pooled instance connections; Versions: Any If you do not change the driver type, then the connection will fail.

If the check is successful, click Next. If the check fails, reenter the connection details correctly and try again.
On the JDBC Component Schema screen, verify that the DBMS/Service and the Host name is correct for each component schema and click Next.
On the JDBC Component Schema Test screen, select all the component schemas and click Test Selected Connections to test the connection for each schema. The result of the test is indicated in the Status column.
When the check is complete, click Next.

On the Advanced Configuration screen, you can select all categories for which you want to perform advanced configuration. For each category you select, the appropriate configuration screen is displayed to allow you to perform advanced configuration.

Note:

The optional categories that are listed on the Advanced Configuration screen depend on the resources defined in the templates you selected for the domain. Some common categories are described below.

Advanced Configuration > Managed Servers:

You must specify the actual hostname for the Listen Address for each managed server in your domain.

Do not use the default localhost or All Local Addresses option.

You must specify the actual hostname as hostname.yourcompany.com

Managed Servers >Targeting Server Groups

If you are upgrading a domain that was created in 12c (12.2.1.4.0), you MUST target your servers to the correct Server Groups during the domain reconfiguration phase of the upgrade. Failure to target these servers may result in a failed upgrade and excess downtime.

On the Managed Servers screen, target each server to the correct Server Group by selecting the correct group name from the Server Groups drop-down menu.

Verify that Each of the servers is targeted to the correct server group and should not show as Unspecified.

Component and Server	Server Group
SOA (soa_server1)	SOA-MGD-SVRS-ONLY
Oracle Service Bus - OSB (osb_server1)	OSB-MGD-SVRS-ONLY
Business Activity Monitoring - BAM (bam_server1)	BAM-MGD-SVRS-ONLY
Managed File Transfer - MFT (mft_server1)	MFT-MGD-SVRS-ONLY

Advanced Configuration > Assign Servers to Machines

If you have created servers as part of the upgrade process, then select the server name in the Servers list box and target them to the correct Node Manager Machine.

Otherwise, no action is required on this screen when you are upgrading or reconfiguring the domain.

Advanced Configuration > Assign Servers to Clusters

Cluster Upgrades Only: If you are upgrading clusters, use this screen to assign Managed Servers to clusters.

Note that only Managed Servers are displayed in the Server list box. The Administration Server is not listed because it cannot be assigned to a cluster.

Note:

When OWSMPM is in its own cluster and not part of SOA or OSB clusters:

Target only SOA-MGD-SVRS-ONLY user extensible server group to the SOA cluster

Target only OSB-MGD-SVRS-ONLY to the OSB cluster
Target WSMPM-MAN-SVER server group to OWSM

On the Configuration Summary screen, review the detailed configuration settings of the domain before continuing.
You can limit the items that are displayed in the right-most panel by selecting a filter option from the View drop-down list.

To change the configuration, click Back to return to the appropriate screen. To reconfigure the domain, click Reconfig.

Note:
The location of the domain does not change when you reconfigure it.
The Reconfiguration Progress screen displays the progress of the reconfiguration process.
During this process:
- Domain information is extracted, saved, and updated.
- Schemas, scripts, and other such files that support your Fusion Middleware products are updated.
When the progress bar shows 100%, click Next.
The End of Configuration screen indicates whether the reconfiguration process completed successfully or failed. It also displays the location of the domain that was reconfigured as well as the Administration Server URL (including the listen port). If the reconfiguration is successful, it displays Oracle WebLogic Server Reconfiguration Succeeded.
If the reconfiguration process did not complete successfully, an error message is displayed indicates the reason. Take appropriate action to resolve the issue. If you cannot resolve the issue, contact My Oracle Support.

Note the Domain Location and the Admin Server URL for further operations.

Upgrading Domain Component Configurations

After reconfiguring the domain, use the Upgrade Assistant again to upgrade the domain component configurations inside the domain to match the updated domain configuration.

Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 14c (14.1.2.0.0).

To start the Upgrade Assistant:

Note:

UNIX operating systems:

export UA_PROPERTIES="-Dfile.encoding=UTF-8 ${UA_PROPERTIES}"

Windows operating systems:

set UA_PROPERTIES=-Dfile.encoding=UTF-8 %UA_PROPERTIES%

Go to the oracle_common/upgrade/bin directory:
- (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
- (Windows) ORACLE_HOME\oracle_common\upgrade\bin
Start the Upgrade Assistant:
- (UNIX) ./ua
- (Windows) ua.bat

For information about other parameters that you can specify on the command line, such as logging parameters, see:

Upgrade Assistant Parameters

When you start the Upgrade Assistant from the command line, you can specify additional parameters.

Table 3-5 Upgrade Assistant Command-Line Parameters

Parameter	Required or Optional	Description
`-readiness`	Required for readiness checks Note: Readiness checks cannot be performed on standalone installations (those not managed by the WebLogic Server).	Performs the upgrade readiness check without performing an actual upgrade. Schemas and configurations are checked. Do not use this parameter if you have specified the `-examine` parameter.
`-threads`	Optional	Identifies the number of threads available for concurrent schema upgrades or readiness checks of the schemas. The value must be a positive integer in the range 1 to 8. The default is 4.
`-response`	Required for silent upgrades or silent readiness checks	Runs the Upgrade Assistant using inputs saved to a response file generated from the data that is entered when the Upgrade Assistant is run in GUI mode. Using this parameter runs the Upgrade Assistant in silent mode (without displaying Upgrade Assistant screens).
`-examine`	Optional	Performs the examine phase but does not perform an actual upgrade. Do not specify this parameter if you have specified the `-readiness` parameter.
`-logLevel attribute`	Optional	Sets the logging level, specifying one of the following attributes: `TRACE` `NOTIFICATION` `WARNING` `ERROR` `INCIDENT_ERROR` The default logging level is `NOTIFICATION`. Consider setting the `-logLevel TRACE` attribute to so that more information is logged. This is useful when troubleshooting a failed upgrade. The Upgrade Assistant's log files can become very large if `-logLevel TRACE` is used.
`-logDir location`	Optional	Sets the default location of upgrade log files and temporary files. You must specify an existing, writable directory where the Upgrade Assistant creates log files and temporary files. The default locations are: (UNIX) `ORACLE_HOME/oracle_common/upgrade/logs` `ORACLE_HOME/oracle_common/upgrade/temp` (Windows) `ORACLE_HOME\oracle_common\upgrade\logs` `ORACLE_HOME\oracle_common\upgrade\temp`
`-help`	Optional	Displays all of the command-line options.

Upgrading Domain Components Using the Upgrade Assistant

Navigate through the screens in the Upgrade Assistant to upgrade component configurations in the WebLogic domain.

After running the Reconfiguration Wizard to reconfigure the WebLogic domain to Oracle Analytics server, you must run the Upgrade Assistant to upgrade the domain component configurations to match the updated domain configuration.

To upgrade domain component configurations with the Upgrade Assistant:

On the Welcome screen, review an introduction to the Upgrade Assistant and information about important pre-upgrade tasks. Click Next.

Note:
For more information about any Upgrade Assistant screen, click Help on the screen.
On the next screen:
- Select All Configurations Used By a Domain. The screen name changes to WebLogic Components.
- In the Domain Directory field, enter the WebLogic domain directory path.
Click Next.
If your pre-upgrade environment has multiple WebLogic domains, but the Oracle Web Services Manager (OWSM) Policy Manager is in only one domain, and OWSM agents are in the other domains: On the OWSM Policy Manager screen, provide the credentials for the WebLogic Administration Server domain where the Oracle Web Services Manager (OWSM) Policy Manager is deployed.
On the Component List screen, verify that the list includes all the components for which you want to upgrade configurations and click Next.
If you do not see the components you want to upgrade, click Back to go to the previous screen and specify a different domain.
On the Prerequisites screen, acknowledge that the prerequisites have been met by selecting all the check boxes. Click Next.

Note:
The Upgrade Assistant does not verify whether the prerequisites have been met.
If there are remote managed servers hosting User Messaging Services (UMS) configuration files: On the UMS Configuration screen, provide the credentials to these servers so that the Upgrade Assistant can access the configuration files.

Note:
You may need to manually copy the UMS configuration files if the Upgrade Assistant is unable to locate them. See Error while Copying User Messaging Service (UMS) Configuration Files.
On the Examine screen, review the status of the Upgrade Assistant as it examines each component, verifying that the component configuration is ready for upgrade. If the status is Examine finished, click Next.
If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No in the Examination Failure dialog. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade in Upgrading with the Upgrade Assistant for information on resolving common upgrade errors.
Note:
- If you resolve any issues detected during the examine phase without proceeding with the upgrade, you can start the Upgrade Assistant again without restoring from backup. However, if you proceed by clicking Yes in the Examination Failure dialog box, you need to restore your pre-upgrade environment from backup before starting the Upgrade Assistant again.
- Canceling the examination process has no effect on the configuration data; the only consequence is that the information the Upgrade Assistant has collected must be collected again in a future upgrade session.
On the Upgrade Summary screen, review the summary of the options you have selected for component configuration upgrade.
The response file collects and stores all the information that you have entered, and enables you to perform a silent upgrade at a later time. The silent upgrade performs exactly the same function that the Upgrade Assistant performs, but you do not have to manually enter the data again. If you want to save these options to a response file, click Save Response File and provide the location and name of the response file.

Click Upgrade to start the upgrade process.
On the Upgrade Progress screen, monitor the status of the upgrade.

Caution:
Allow the Upgrade Assistant enough time to perform the upgrade. Do not cancel the upgrade operation unless absolutely necessary. Doing so may result in an unstable environment.

If any components are not upgraded successfully, refer to the Upgrade Assistant log files for more information.

Note:
The progress bar on this screen displays the progress of the current upgrade procedure. It does not indicate the time remaining for the upgrade.

Click Next.
If the upgrade is successful: On the Upgrade Success screen, click Close to complete the upgrade and close the wizard. The Post-Upgrade Actions window describes the manual tasks you must perform to make components functional in the new installation. This window appears only if a component has post-upgrade steps.

If the upgrade fails: On the Upgrade Failure screen, click View Log to view and troubleshoot the errors. The 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, then restart the Upgrade Assistant.