Oracle® Fusion Middleware

Upgrading with the Upgrade Assistant

12c (12.2.1.2)

E77899-03

December 2016

This tool-specific reference guide provides command-line instructions and screen references for the Oracle Fusion Middleware Upgrade Assistant.

Oracle Fusion Middleware Upgrading with the Upgrade Assistant, 12c (12.2.1.2)

E77899-03

Copyright © 2013, 2016, Oracle and/or its affiliates. All rights reserved.

Primary Author:  Lisa Jamen

Contributing Author:  Priyanka Chedda

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 About Using the Oracle Fusion Middleware Upgrade Assistant

- 1.1 About the Upgrade Assistant

- 1.2 About Using the Upgrade Assistant in the Upgrade Process

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

- 1.2.2 Upgrading Product Schemas

- 1.2.3 About Using the Upgrade Assistant to Upgrade Component Configurations

- 1.3 Identifying Existing Schemas Available for Upgrade

- 1.4 Identifying Schemas that Can Be Upgraded to this Release

- 1.5 Identifying Configurations that can be Upgraded with the Upgrade Assistant

2 Using the Upgrade Assistant to Perform an Upgrade

- 2.1 Before You Begin Using the Upgrade Assistant

- 2.1.1 Creating a Complete Backup

- 2.1.1.1 Backing Up the Schema Version Registry Table

- 2.1.1.2 Maintaining Custom Domain Environment Settings

- 2.1.2 Checking for Invalid Database Objects Before an Upgrade

- 2.1.3 Creating a Non-SYSDBA User to Run the Upgrade Assistant

- 2.1.4 Stopping Servers and Processes

- 2.2 Starting the Upgrade Assistant

- 2.2.1 Upgrade Assistant Parameters

- 2.3 Running a Pre-Upgrade Readiness Check

- 2.3.1 About Running a Pre-Upgrade Readiness Check

- 2.3.2 Starting the Upgrade Assistant in Readiness Mode

- 2.3.2.1 Upgrade Assistant Parameters

- 2.3.3 Performing a Readiness Check with the Upgrade Assistant

- 2.3.4 Understanding the Readiness Report

- 2.4 Upgrading Product Schemas Using the Upgrade Assistant

- 2.5 Understanding the Component Configurations Upgrade Screens

- 2.6 Performing Post-Upgrade Procedures

- 2.6.1 Performing Basic Post-Upgrade Administrative Tasks

- 2.6.2 Verifying a Successful Schema Upgrade

- 2.6.3 Checking for Invalid Database Objects After an Upgrade

3 Performing a Silent Upgrade with a Response File

- 3.1 Creating an Upgrade Response File

- 3.2 Using the Response File to Upgrade Fusion Middleware

- 3.2.1 Upgrade Assistant Parameters

4 Troubleshooting Your Upgrade

- 4.1 Troubleshooting an Upgrade

- 4.2 Reviewing Log Files

- 4.3 Investigating Examination Failures

- 4.4 Investigating Upgrade Failures

- 4.5 Resolving Common Oracle Fusion Middleware Upgrade Assistant Errors

- 4.5.1 Ensuring there is sufficient disk space

- 4.5.2 Resolving Database Connection Problems When Upgrading Schemas

- 4.6 Attempting to Upgrade an Unsupported Domain

- 4.7 Restarting the Upgrade Assistant After a Failure

Preface

This guide describes how to use the Oracle Fusion Middleware Upgrade Assistant, including how to prepare for an upgrade, how the upgrade will affect the existing environment, and how to prepare your database and repository schemas for an upgrade.

- Audience

- Documentation Accessibility

- Related Documents
Upgrade documentation is organized by tasks in the 12c documentation library. The task-specific pages provide direct links to common upgrade procedures and related documentation.

- Conventions

Audience

This guide is intended for system administrators who are responsible for upgrading Oracle Fusion Middleware. It is assumed that the readers of this manual have knowledge of the following:

- Oracle Fusion Middleware 12c system administration and configuration information for the existing deployment

- The configuration and expected behavior of the system or systems being upgraded

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

Upgrade documentation is organized by tasks in the 12c documentation library. The task-specific pages provide direct links to common upgrade procedures and related documentation.

You can refer the Oracle Fusion Middleware Library for additional information.

- For installation information, see Fusion Middleware Installation Documentation.

- For upgrade information, including upgrade videos, see Fusion Middleware 12c Upgrade Documentation.

- For administration-related information, see Fusion Middleware 12c Administration Documentation.

- For release-related information, see Fusion Middleware 12c Release Notes.

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

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

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.2). 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 this Release
Before an upgrade, it is important to know which schemas can be upgraded to 12c (12.2.1.2). Not all schemas require an upgrade, and not all schemas can be upgraded.

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

1.1 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.2). The Upgrade Assistant can also be used to run a pre-upgrade readiness check.

The Upgrade Assistant is available at the following location in your Fusion Middleware installation:

(UNIX) ORACLE_HOME/oracle_common/upgrade/bin

(Windows) ORACLE_HOME\oracle_common\upgrade\bin

When you run the Upgrade Assistant, it performs the following tasks:

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

1.2 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 Oracle Fusion Middleware 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 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.

2. 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.

3. About Using the Upgrade Assistant to Upgrade Component Configurations
After the domain has been reconfigured, use the Upgrade Assistant to upgrade any component configurations.

1.2.1 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. The readiness check can be performed while the system is online. Readiness check is a read-only operation that scans your existing domain or database schemas and produces a text file with the results of the scan. The readiness check does not require that schemas are part of any particular domain. If your pre-upgrade environment has issues, you can correct those issues and then rerun the readiness check before you upgrade..

Alternatively, you can run the readiness check in -response mode to perform a silent readiness check using a response file. For more information on using a response file with the Upgrade Assistant, see Upgrade Assistant Parameters.

Understanding the difference between the Examine Phase and a Readiness Check

The Examine phase of the upgrade process is a separate operation from running a readiness check. Typically the readiness checks are more thorough than the checks performed during the Examine phase. The readiness check is a read-only process performed before you start the actual upgrade, while the Examine phase occurs just before you click Upgrade and identifies potential issues with the schemas and configuration data.

Note:
If you have performed any of the upgrade steps, you should not run readiness check as the results can be invalid.

Caution:
If you perform an upgrade and encounter issues that prevent a successful upgrade, you may have to revert to your backed-up, pre-upgrade environment and start the upgrade again. Running the readiness check can help identify some of these issues and prevent extended system downtime.

1.2.2 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.

1.2.3 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.

1.3 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 acount that has Oracle DBA privileges, and run the following from SQL*Plus:

SET LINE 120
COLUMN MRC_NAME FORMAT A14
COLUMN COMP_ID FORMAT A20
COLUMN VERSION FORMAT A12
COLUMN STATUS FORMAT A9
COLUMN UPGRADED FORMAT A8
SELECT MRC_NAME, COMP_ID, OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY ORDER BY MRC_NAME, COMP_ID ;

2. Examine the report that is generated. If the value in the VERSION column is at 11.1.1.7.0 or higher, and the STATUS column value is VALID, then the schema is supported for upgrade.
If an upgrade is not needed for a schema, the schema_version_registry table retains the schema at its pre-upgrade version.

3. Note the schema prefix name that was used for your existing schemas. You will use the same prefix when creating new 12c schemas.

Notes

- If your existing schemas are not at a supported version, then you must upgrade them to a supported version before using the 12c (12.2.1.2) upgrade procedures. Refer to your pre-upgrade version documentation for more information.

- Some components, such as Oracle Enterprise Data Quality, Oracle GoldenGate Monitor and Oracle GoldenGate Veridata, support an upgrade from versions other than the standard Oracle Fusion Middleware supported versions.

- If you used an OID-based policy store in 11g, make sure that you create a new OPSS schema before you perform the upgrade. After the upgrade, the OPSS schema will remain an LDAP-based store.

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

1.4 Identifying Schemas that Can Be Upgraded to this Release

Before an upgrade, it is important to know which schemas can be upgraded to 12c (12.2.1.2). Not all schemas require an upgrade, and not all schemas can be upgraded.

When schemas are created in your database, the Repository Creation Utility (RCU) creates and maintains a table called schema_version_registry. Refer to this table before you perform an upgrade. The Schema Version After Upgrade column shows the latest version for that schema. If your schemas are already at this version, then you will not need to upgrade.

NOTE: The Schema(s) column shows the default schema name format of prefix and schema name separated by an underscore (_) character. The default prefix is DEV, but you may have created new prefixes for your schemas while using the RCU.

Table 1-1 Schemas that can be upgraded to Oracle Fusion Middleware 12c 12c (12.2.1.2)

Component Name

Schemas

Schema Version Before Upgrade

Schema Version After Upgrade

Dependencies and Additional Information

Audit ServicesFoot 1

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

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

No dependencies.

12.2.1.1 is the latest version for this schema.

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

The prefix_STB schema must be upgraded when upgrading other components, such as SOAINFRA.

12.1.3.0 is the latest version for this schema.

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

No dependencies.

12.2.1.1 is the latest version for this schema.

SOA Infrastructure (including Oracle Business Activity Monitoring, Business Process Management, and Oracle Service Bus

prefix_SOAINFRA

11.1.1.7

11.1.1.9

12.1.3

12.2.1.0

12.2.1.1

The prefix_STB schema must be upgraded first.

12.2.1.1 is the latest version for this schema.

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.1 is the latest version for this schema.

Oracle Managed File Transfer

prefix_MFT

12.1.3.0

12.2.1.0

12.2.1.1

The prefix_MDS, prefix_IAU, and prefix_UMS must also be upgraded.
12.2.1.1 is the latest version for this schema.

Oracle WebCenter Content Server

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 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

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.1 is the latest version for this schema.

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 will update two auxilary schemas, IAU_APPEND and IAU_VIEWER and add them to the schema_version_registry for 12.2.1.2. These schemas were not part of the 11g schema_version_registry table.

Footnote 2

As of release 11.1.1.7, OPSS audit data is stored in IAU common tables instead of the JPS table.

Footnote 3

When upgrading a system from a previous 12c release, the schema is called prefix_UMS.

Footnote 4

First release to support Edition-Based Redefinition (EBR) enabled schemas.

Footnote 5

First release to support Edition-Based Redefinition (EBR) enabled schemas.

1.5 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.2).

When you use the Upgrade Assistant to upgrade your configurations, it automatically determines the list of components that are configured and can be upgraded to the latest version. Before you begin the upgrade, review the list of components that can be upgraded to this release.

Caution:
Do not attempt an upgrade if you want to continue using existing Fusion Middleware 11g components that have been deprecated or not yet available for use in the 12c (12.2.1.2) release.

Component configurations that can be upgraded include:

- Common Infrastructure Services

- Oracle Data Integrator

- Oracle Enterprise Data Quality

- Oracle Forms

- Oracle GoldenGate Monitor

- Oracle GoldenGate Veridata

- Oracle HTTP Server

- Oracle MapViewer

- Oracle Reports

- Oracle Traffic Director

- Oracle User Messaging Service

- Oracle WebCenter Portal

- Oracle WebCenter Sites

- Oracle Web Services Manager

- System Components Infrastructure

- Java Required Files (JRF) Infrastructure

2 Using the Upgrade Assistant to Perform an Upgrade

The Upgrade Assistant is used in different ways to upgrade schemas, component configurations, and to perform a readiness check on your pre-upgrade environment.

Note:
The information in the following sections provides a high-level overview of how the Upgrade Assistant is used to perform an Oracle Fusion Middleware upgrade. The component-specific upgrade guides should be used when performing an actual upgrade.

- Before You Begin Using the Upgrade Assistant
This section describes some of the procedures you must perform before you begin any upgrade with the Upgrade Assistant.

- Starting the Upgrade Assistant
Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.2). Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time.

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

- Upgrading Product Schemas Using the Upgrade Assistant
Navigate through the screens in the Upgrade Assistant to upgrade the product schemas.

- Understanding the Component Configurations Upgrade Screens
Describes the basic Upgrade Assistant screens seen in most component configuration upgrades.

- Performing Post-Upgrade Procedures
Complete any additional post-upgrade configuration tasks after the upgrade to verify that your newly upgrade domain is functioning as expected. Perform only those tasks that apply to your domain configuration.

2.1 Before You Begin Using the Upgrade Assistant

This section describes some of the procedures you must perform before you begin any upgrade with the Upgrade Assistant.

Note:
You may be required to perform additional tasks before starting your actual upgrade process. Each of the component-specific upgrade guides provides a checklist that includes a complete list of a pre-upgrade tasks that must be performed before starting an upgrade.

- Creating a Complete Backup
Back up all system-critical files including all of the databases that host your Oracle Fusion Middleware schemas before you start the upgrade.

- Checking for Invalid Database Objects Before an Upgrade
To identify invalid objects that may cause the upgrade to fail, recompile database objects before you run the Upgrade Assistant.

- Creating a Non-SYSDBA User to Run the Upgrade Assistant
Oracle recommends that you create a non-SYSDBA user called FMW to run the Upgrade Assistant. This user has the privileges required to modify schemas, but does not have full administrator privileges.

- Stopping Servers and Processes
Before running the Upgrade Assistant to upgrade your schemas and configurations, you must shut down all processes and servers, including the Administration server and any managed servers.

2.1.1 Creating a Complete Backup

Back up all system-critical files including all of the databases that host your Oracle Fusion Middleware schemas before you start the upgrade.

The backup must include the SYSTEM.SCHEMA_VERSION_REGISTRY$ table so that you can restore the contents back to its pre-upgrade state if the upgrade fails.

The Upgrade Assistant Prerequisites screen prompts you to acknowledge that backups have been performed before you proceed with the actual upgrade. However, note that the Upgrade Assistant does not verify that a backup has been created.

For more information about creating a backup, see:

- Backing Up Your Environment in Oracle Fusion Middleware Administering Oracle Fusion Middleware

- Upgrading and Preparing Your Oracle Databases for 12c in Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware

In addition to creating a complete backup of your system, you must also create a backup of your schema version registry and any custom settings you want to use in your upgraded environment. See the following resources:

- Backing Up the Schema Version Registry Table
Your system backup must include the SYSTEM.SCHEMA_VERSION_REGISTRY$ table.

- Maintaining Custom Domain Environment Settings
If you modified any domain generated or server startup scripts in your pre-upgrade environment, it is important to note that these changes are overwritten during the installation, domain upgrade, and reconfiguration operations.

2.1.1.1 Backing Up the Schema Version Registry Table

Your system backup must include the SYSTEM.SCHEMA_VERSION_REGISTRY$ table.

Each Fusion Middleware schema has a row in the SYSTEM.SCHEMA_VERSION_REGISTRY$ table. If you run the Upgrade Assistant to update an existing schema and it does not succeed, you must restore the original schema before you can try again. Make sure you back up your existing database schemas and the schema version registry before you run the Upgrade Assistant.

Note:
Performing these backups prior to performing a schema upgrade is a prerequisite for running the Upgrade Assistant. During the upgrade you will be required to acknowledge that backups have been performed.

2.1.1.2 Maintaining Custom Domain Environment Settings

If you modified any domain generated or server startup scripts in your pre-upgrade environment, it is important to note that these changes are overwritten during the installation, domain upgrade, and reconfiguration operations.

Every domain installation includes dynamically-generated domain and server startup scripts, such as setDomainEnv. These files are replaced by newer versions during the installation and upgrade process. To maintain your custom domain-level environment settings, Oracle recommends that you create a separate file to store the custom domain information before you upgrade, instead of modifying the scripts directly.

For example, if you want to customize server startup parameters that apply to all servers in a domain, you can create a file called setUserOverrides.cmd (Windows) or setUserOverrides.sh (UNIX) and configure it to add custom libraries to the WebLogic Server classpath, specify additional command-line options for running the servers, or specify additional environment variables. Any custom settings you add to this file are preserved during the domain upgrade operation and are carried over to the remote servers when using the pack and unpack commands.

The following example illustrates startup customizations in a setUserOverrides file:

# add custom libraries to the WebLogic Server system claspath
if [ "${POST_CLASSPATH}" != "" ] ; then
POST_CLASSPATH="${POST_CLASSPATH}${CLASSPATHSEP}${HOME}/foo/fooBar.jar"
export POST_CLASSPATH
else
POST_CLASSPATH="${HOME}/foo/fooBar.jar"
export POST_CLASSPATH
fi

# specify additional java command line options for servers
JAVA_OPTIONS="${JAVA_OPTIONS}  -Dcustom.property.key=custom.value"

If the setUserOverrides file exists during a server startup, the file is included in the startup sequence and any overrides contained within this file take effect. You must store the setUserOverrides file in the domain_home/bin directory.

Note:

If you are unable to create the setUserOverrides script before an upgrade, you need to reapply your settings as described in Re-apply Customizations to Startup Scripts in Oracle Fusion Middleware Upgrading Oracle WebLogic Server.

2.1.2 Checking for Invalid Database Objects Before an Upgrade

To identify invalid objects that may cause the upgrade to fail, recompile database objects before you run the Upgrade Assistant.

If you are using an Oracle database, you can recompile database objects before running the Upgrade Assistant by connecting to the database as SYS and running the following from SQL*Plus:

SQL> @oracle_home/software/rdbms/admin/utlrp.sql

This compiles the database objects.

Then use the following query to ensure there are no invalid database objects:

SELECT owner, object_name FROM all_objects WHERE status='INVALID';

None of the database objects should be invalid before you upgrade.

If there are any invalid objects, run the utlrp.sql command again. If the problem persists, you should file a service request.

2.1.3 Creating a Non-SYSDBA User to Run the Upgrade Assistant

Oracle recommends that you create a non-SYSDBA user called FMW to run the Upgrade Assistant. This user has the privileges required to modify schemas, but does not have full administrator privileges.

SYSDBA is an administrative privilege that is required to perform high-level administrative operations such as creating, starting up, shutting down, backing up, or recovering the database. The SYSDBA system privilege is for a fully empowered database administrator. When you connect with the SYSDBA privilege, you connect with a default schema and not with the schema that is generally associated with your user name. For SYSDBA, this schema is SYS. Access to a default schema can be a very powerful privilege. For example, when you connect as user SYS, you have unlimited privileges on data dictionary tables. Therefore, Oracle recommends that you create a non-SYSDBA user to upgrade the schemas. The privileges listed in this section must be granted to user FMW before starting the Upgrade Assistant.

Notes
If you created the non-SYSDBA user FMW in a previous release, you must drop and recreate this user before starting the upgrade. Running the Upgrade Assistant with an older FMW user may lead to a failed upgrade as new privileges may have been added. Oracle recommends that you drop and recreate the user instead of modifying the existing FMW user.

By default, the v$xatrans$ table does not exist. You must run the XAVIEW.SQL script to create this table before creating the user. Moreover, the grant select privilege on v$xatrans$ table is required only for Oracle Identity Manager. If you do not require Oracle Identity Manager for configuration, or if you do not have the v$xatrans$ table, then remove the following line from the script:

grant select on v$xatrans$ to FMW with grant option;

In the example below, welcome1 is the password. Make sure that you specify your actual password when granting privileges.

create user FMW identified by welcome1;
grant dba to FMW;
grant execute on DBMS_LOB to FMW with grant option;
grant execute on DBMS_OUTPUT to FMW with grant option;
grant execute on DBMS_STATS to FMW with grant option;
grant execute on sys.dbms_aqadm to FMW with grant option;
grant execute on sys.dbms_aqin to FMW with grant option;
grant execute on sys.dbms_aqjms to FMW with grant option;
grant execute on sys.dbms_aq to FMW with grant option;
grant execute on utl_file to FMW with grant option;
grant execute on dbms_lock to FMW with grant option;
grant select on sys.V_$INSTANCE to FMW with grant option;
grant select on sys.GV_$INSTANCE to FMW with grant option;
grant select on sys.V_$SESSION to FMW with grant option;
grant select on sys.GV_$SESSION to FMW with grant option;
grant select on dba_scheduler_jobs to FMW with grant option;
grant select on dba_scheduler_job_run_details to FMW with grant option;
grant select on dba_scheduler_running_jobs to FMW with grant option;
grant select on dba_aq_agents to FMW with grant option;
grant execute on sys.DBMS_SHARED_POOL to FMW with grant option;
grant select on dba_2pc_pending to FMW with grant option;
grant select on dba_pending_transactions to FMW with grant option;
grant execute on DBMS_FLASHBACK to FMW with grant option;
grant execute on dbms_crypto to FMW with grant option;
grant execute on DBMS_REPUTIL to FMW with grant option;
grant execute on dbms_job to FMW with grant option;
grant select on pending_trans$ to FMW with grant option;
grant select on dba_scheduler_job_classes to fmw with grant option;
grant select on SYS.DBA_DATA_FILES to FMW with grant option;
grant select on SYS.V_$ASM_DISKGROUP to FMW with grant option;
grant select on v$xatrans$ to FMW with grant option;
grant execute on sys.dbms_system to FMW with grant option;
grant execute on DBMS_SCHEDULER to FMW with grant option;
grant select on dba_data_files to FMW with grant option;
grant execute on UTL_RAW to FMW with grant option;
grant execute on DBMS_XMLDOM to FMW with grant option;
grant execute on DBMS_APPLICATION_INFO to FMW with grant option;
grant execute on DBMS_UTILITY to FMW with grant option;
grant execute on DBMS_SESSION to FMW with grant option;
grant execute on DBMS_METADATA to FMW with grant option;
grant execute on DBMS_XMLGEN to FMW with grant option;
grant execute on DBMS_DATAPUMP to FMW with grant option;
grant execute on DBMS_MVIEW to FMW with grant option;
grant select on ALL_ENCRYPTED_COLUMNS to FMW with grant option;
grant select on dba_queue_subscribers to FMW with grant option;
grant execute on SYS.DBMS_ASSERT to FMW with grant option;
grant select on dba_subscr_registrations to FMW with grant option;
grant manage scheduler to FMW;

Note:

Oracle Database 11.2.0.3 Database Users ONLY: You must apply Oracle Patch 13036331 before you begin the upgrade. Go to My Oracle Support to download the patch.

If you do not apply this patch, then you will have to grant additional privileges for some schemas.

2.1.4 Stopping Servers and Processes

Before running the Upgrade Assistant to upgrade your schemas and configurations, you must shut down all 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 such as Identity Management 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 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 Administration Console. See Starting and Stopping Administration and Managed Servers and Node Manager in Administering Oracle Fusion Middleware.

To stop your Fusion Middleware environment, follow the steps below.

Step 1: Stop System Components

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

- (UNIX) DOMAIN_HOME/bin/stopComponent.sh component_name

- (Windows) DOMAIN_HOME\bin\stopComponent.cmd component_name

You can stop system components in any order.

Step 2: Stop the Managed Servers

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

- (UNIX) DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url

- (Windows) DOMAIN_HOME\bin\stopManagedWebLogic.cmd managed_server_name admin_url

When prompted, enter your user name and password.

Step 3: Stop Oracle Identity Management ComponentsStop any Oracle Identity Management components, such as Oracle Internet Directory, that form part of your environment:

- (UNIX) DOMAIN_HOME/bin/stopComponent.sh component_name

- (Windows) DOMAIN_HOME\bin\stopComponent.cmd component_name

Step 4: Stop the Administration Server

When you stop the Administration Server, you also stop the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.

To stop the Administration Server, use the stopWebLogic script:

- (UNIX) DOMAIN_HOME/bin/stopWebLogic.sh

- (Windows) DOMAIN_HOME\bin\stopWebLogic.cmd

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

Step 5: Stop Node Manager

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

Alternatively, after having set the nodemanager.properties attribute QuitEnabled to true (the default is false), you can use WLST to connect to Node Manager and shut it down. For more information, see stopNodeManager in Oracle Fusion Middleware WLST Command Reference for WebLogic Server.

2.2 Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.2). Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time.

To start the Upgrade Assistant:

1. Go to the oracle_common/upgrade/bin directory:

- (UNIX) ORACLE_HOME/oracle_common/upgrade/bin

- (Windows) ORACLE_HOME\oracle_common\upgrade\bin

2. 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

2.2.1 Upgrade Assistant Parameters

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

Table 2-1 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 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 will create 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.

2.3 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.

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

- Performing a Readiness Check with the Upgrade Assistant
Navigate through the screens in the Upgrade Assistant to complete the pre-upgrade readiness check.

- Understanding the Readiness Report
After performing a readiness check for your domain, review the report to determine if you need to take any action for a successful upgrade.

2.3.1 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 checks during off-peak hours.

2.3.2 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:

1. Go to the oracle_common/upgrade/bin directory:

- (UNIX) ORACLE_HOME/oracle_common/upgrade/bin

- (Windows) ORACLE_HOME\oracle_common\upgrade\bin

2. 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

2.3.2.1 Upgrade Assistant Parameters

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

Table 2-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 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 will create 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.

2.3.3 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:

1. On the Welcome screen, review information about the readiness check. Click Next.

2. 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.

3. 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 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.

CAUTION
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 and specify the Schema Password.

Click Next to start the readiness check.

4. On the Readiness Summary screen, review the summary of the readiness checks 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.

5. 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.

6. 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.

2.3.4 Understanding the Readiness Report

After performing a readiness check for your domain, review the report to determine if 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 2-3 Readiness Report Elements

Report Information

Description

Required Action

Overall Readiness Status: SUCCESS or FAILURE

The top of the report indicates whether the Upgrade 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_HOME/oracle_common/upgrade/logs

The directory location of the generated log file.

No action required.

Readiness report location

ORACLE_HOME/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, then 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, then 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, then 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.

Here is a sample Readiness Report file. Your report may or may not include all of these checks.

Upgrade readiness check completed with one or more errors.

This readiness check report was created on Tue May 30 11:15:52 EDT 2016
Log file is located at: ORACLE_HOME/oracle_common/upgrade/logs/ua2016-05-30-11-14-06AM.log
Readiness Check Report File: ORACLE_HOME/oracle_common/upgrade/logs/readiness2016-05-30-11-15-52AM.txt

Starting readiness check of components.

Oracle Metadata Services
Starting readiness check of Oracle Metadata Services.
Schema User Name: DEV11_MDS
Database Type: Oracle Database
Database Connect String: machinename@yourcompany.com
VERSION Schema DEV11_MDS is currently at version 12.1.1.1.0.  Readiness checks will now be performed.
Starting schema test:  TEST_REQUIRED_TABLES  Test that the schema contains all the required tables
Completed schema test: TEST_REQUIRED_TABLES --> Test that the schema contains all the required tables +++ PASS
Starting schema test:  TEST_REQUIRED_PROCEDURES  Test that the schema contains all the required stored procedures
EXCEPTION     Schema is missing a required procedure: GETREPOSITORYFEATURES
Completed schema test: TEST_REQUIRED_PROCEDURES --> Test that the schema contains all the required stored procedures +++ FAIL
Starting schema test:  TEST_REQUIRED_VIEWS  Test that the schema contains all the required database views
Completed schema test: TEST_REQUIRED_VIEWS --> Test that the schema contains all the required database views +++ PASS
Starting index test for table MDS_ATTRIBUTES:  TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table MDS_ATTRIBUTES: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting index test for table MDS_COMPONENTS:  TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes
Completed index test for table MDS_TXN_LOCKS: TEST_REQUIRED_INDEXES --> Test that the table contains all the required indexes +++ PASS
Starting schema test:  TEST_REQUIRED_TRIGGERS  Test that the schema has all the required triggers
Completed schema test: TEST_REQUIRED_TRIGGERS --> Test that the schema has all the required triggers +++ PASS
Starting schema test:  TEST_MISSING_COLUMNS  Test that tables and views are not missing any required columns
Completed schema test: TEST_MISSING_COLUMNS --> Test that tables and views are not missing any required columns +++ PASS
Starting schema test:  TEST_UNEXPECTED_TABLES  Test that the schema does not contain any unexpected tables
Completed schema test: TEST_UNEXPECTED_TABLES --> Test that the schema does not contain any unexpected tables +++ PASS
Starting schema test:  TEST_UNEXPECTED_PROCEDURES  Test that the schema does not contain any unexpected stored procedures
Completed schema test: TEST_UNEXPECTED_PROCEDURES --> Test that the schema does not contain any unexpected stored procedures +++ PASS
Starting schema test:  TEST_UNEXPECTED_VIEWS  Test that the schema does not contain any unexpected views
Completed schema test: TEST_UNEXPECTED_VIEWS --> Test that the schema does not contain any unexpected views +++ PASS
Starting index test for table MDS_ATTRIBUTES:  TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Completed index test for table MDS_ATTRIBUTES: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Completed index test for table MDS_LABELS: TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes +++ PASS
Starting index test for table MDS_LARGE_ATTRIBUTES:  TEST_UNEXPECTED_INDEXES --> Test that the table does not contain any unexpected indexes
Starting schema test:  TEST_UNEXPECTED_TRIGGERS  Test that the schema does not contain any unexpected triggers
Completed schema test: TEST_UNEXPECTED_TRIGGERS --> Test that the schema does not contain any unexpected triggers +++ PASS
Starting schema test:  TEST_UNEXPECTED_COLUMNS  Test that tables and views do not contain any unexpected columns
Completed schema test: TEST_UNEXPECTED_COLUMNS --> Test that tables and views do not contain any unexpected columns +++ PASS
Starting datatype test for table MDS_ATTRIBUTES:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Completed datatype test for table MDS_ATTRIBUTES: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
Starting datatype test for table MDS_COMPONENTS:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
Starting permissions test:  TEST_DBA_TABLE_GRANTS  Test that DBA user has privilege to view all user tables
Completed permissions test: TEST_DBA_TABLE_GRANTS --> Test that DBA user has privilege to view all user tables +++ PASS
Starting schema test:  TEST_ENOUGH_TABLESPACE  Test that the schema tablespaces automatically extend if full
Completed schema test: TEST_ENOUGH_TABLESPACE --> Test that the schema tablespaces automatically extend if full +++ PASS
Starting schema test:  TEST_USER_TABLESPACE_QUOTA  Test that tablespace quota for this user is sufficient to perform the upgrade
Completed schema test: TEST_USER_TABLESPACE_QUOTA --> Test that tablespace quota for this user is sufficient to perform the upgrade +++ PASS
Starting schema test:  TEST_ONLINE_TABLESPACE  Test that schema tablespaces are online
Completed schema test: TEST_ONLINE_TABLESPACE --> Test that schema tablespaces are online +++ PASS
Starting schema test:  TEST_DATABASE_VERSION  Test that the database server version number is supported for upgrade
INFO   Database product version: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Completed schema test: TEST_DATABASE_VERSION --> Test that the database server version number is supported for upgrade +++ PASS
Finished readiness check of Oracle Metadata Services with status: FAILURE.

If you are running the 12.1.3.0 version of Oracle Fusion Middleware IAU Schemas, and those schemas were upgraded from an 11g release (11.1.1.7 and later) or 12c (12.1.2.0), your readiness check may fail with the following error:

Starting index test for table IAU_COMMON:  TEST_REQUIRED_INDEXES --> Test
that the table contains all the required indexes
INFO Audit schema index DYN_EVENT_CATEGORY_INDEX in table IAU_COMMON is
missing the required columns or index itself is missing. This maybe caused by
a known issue, anyway, this missing index will be added in 12.2.2 upgrade.
INFO Audit schema index DYN_EVENT_TYPE_INDEX in table IAU_COMMON is
missing the required columns or index itself is missing. This maybe caused by
a known issue, anyway, this missing index will be added in 12.2.2 upgrade.
INFO Audit schema index DYN_TENANT_INDEX in table IAU_COMMON is missing
the required columns or index itself is missing. This maybe caused by a known
issue, anyway, this missing index will be added in 12.2.2 upgrade.
INFO Audit schema index DYN_USER_INDEX in table IAU_COMMON is missing
the required columns or index itself is missing. This maybe caused by a known
issue, anyway, this missing index will be added in 12.2.2 upgrade.
INFO Audit schema index DYN_COMPONENT_TYPE_INDEX in table IAU_COMMON is
missing the required columns or index itself is missing. This maybe caused by
a known issue, anyway, this missing index will be added in 12.2.2 upgrade.
INFO Audit schema index DYN_USER_TENANT_INDEX in table IAU_COMMON is
missing the required columns or index itself is missing. This maybe caused by
a known issue, anyway, this missing index will be added in 12.2.2 upgrade.
Completed index test for table IAU_COMMON: TEST_REQUIRED_INDEXES --> Test
that the table contains all the required indexes +++ FAIL

Note:
You can ignore the missing index error in the readiness report. This is a known issue. The corresponding missing index is added during the schema upgrade operation. This error does not occur if the schema to be upgraded was created in 12c using the RCU.

2.4 Upgrading Product Schemas Using the Upgrade Assistant

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

The following table describes the basic Upgrade Assistant screens seen in most schema upgrades. Your components may include additional custom screens. These custom screens are documented in your component-specific upgrade documentation.

Note:
The Upgrade Assistant screens displayed when you upgrade your schemas vary depending on the options you select and the contents of your pre-upgrade environment. Always use your component-specific upgrade guides to complete an upgrade.

Table 2-4 Upgrading Schemas: Navigating the Upgrade Assistant Screens

Screen Title

Description

Welcome

This screen provides an overview of the Upgrade Assistant and information about important pre-upgrade tasks.

Schemas

This screen allows you to select the schema upgrade operation that you want to perform. The options change depending on which of the following options you select::

- Individually Selected Schemas

- All Schemas Used by a Domain

Available Components

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.

All Schema Component List

When you select All Schemas Used by a Domain this read-only screen displays all the components and schemas found in the specific domain directory that are included in the upgrade.

Prerequisites

This screen requires you to acknowledge that all prerequisites have been met before you continue with the upgrade. Check the boxes before you continue.

NOTE: Thee Upgrade Assistant will not verify that the prerequisites have been met. For example, the Upgrade Assistant cannot detect if the servers and processes have been stopped as required.

Schema Credentials Screen

The screen name changes based on the type of schema selected ("MDS Schema", for example).

This screen requires you to enter the information needed to connect to the selected schema and the database that hosts the schema on this screen.

You will need to know the following:

- Database Type

Select the database type from the drop-down menu. The types of databases available in the menu varies, depending on the schema you are about to upgrade.

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 using the EBR database type. For example, the Upgrade Assistant never converts schemas from one database type to another.

- 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

If you are using a Microsoft SQL Server or IBM DB2 database, then select the database type from the drop-down menu, and review the text below the field, which provides the syntax required for each database type.

NOTE: The Upgrade Assistant accepts other valid forms of connection strings. For example, the Oracle Database TNS style connection string may also be used.

- DBA User Name

Enter the database user name used to connect to the database.

NOTE: The DBA user must have sufficient privileges to run the Upgrade Assistant, but the user does not have to have SYS/SYSDBA privileges. A non-sysdba user can now be used. See Creating a Non-SYSDBA User to Run the Upgrade Assistant

On certain database platforms user names are case sensitive, and the DBA user name might consist of lower case letters. The Upgrade Assistant connects to the name the user enters and does not convert the user name to upper case.

- DBA Password

Enter the password associated with the specified DBA database user.

Click Connect to connect to the database then select the schema to be upgraded. If the schema that is to be upgraded was created by RCU in a prior Fusion Middleware release then you will see a drop-down menu listing the possible schema names.

NOTE: The component ID or schema name changed for UCSUMS schema as of release 12.1.2.0, so 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_ORASDPM or prefix_UMS, depending on the starting point for the upgrade.

- Schema Owner

Select the schema user name from the drop-down list or enter the user name of the schema, for example, DEV11g_MDS.

NOTE: All Oracle Fusion Middleware schema names consist solely of upper case characters on all database platforms. Also, all schema names are stored as upper case in the schema_version_registry table. If you type lower case letters in the Schema User Name field, the Upgrade Assistant converts the name to upper case

- Schema Owner Password

Enter the password associated with the specified schema user name.

- Edition Name

When Oracle Database enabled for edition-based redefinition is selected as the database type, you must specify the existing edition name.

NOTE: Before upgrading an EBR-enabled schema from Fusion Middleware 11g release or from a previous 12c release, you must first connect to the database server and create an edition on the database server for 12c (12.2.1.2). The new edition for 12c (12.2.1.2) must be a child of your 11.1.1.7.0, 11.1.1.9.0, 12.1.2.0, 12.1.3.0, 12.2.1.0, or 12.2.1.1 edition.

For more information on creating an edition on the server for edition-based redefinition, see "Creating an Edition on the Server for Edition-Based Redefinition" in Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware.

Examine

This screen displays the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade.

The Upgrade Assistant examines each component to be sure it meets a minimum set of criteria before you begin the upgrade process.

Upgrade Assistant displays the schema Source Version of the schema on this screen if the information is listed in the schema version registry table. If the schema was not created using RCU, or the source version cannot be found, the source version will display unavailable

Status Definitions:

- in progress — The Upgrade Assistant is examining the upgrade items for the component.

- pending — The component will be examined when the Upgrade Assistant finishes the preceding component.

- failed — Upgrade items were missing or did not meet upgrade criteria. The Upgrade Assistant cannot upgrade the component until the issues have been resolved. Click View Log to troubleshoot the errors and then restart the Upgrade Assistant.

- succeeded — Upgrade items were found and are valid for upgrade.

- canceled — 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.

- upgrade not necessary— The component is already at the upgraded version or the component was upgraded in a previous run of the Upgrade Assistant.

- skipped— A dependent component has failed resulting in the examine of this component to be skipped.

Note:
Issues detected during the Examination phase may be resolved and the Upgrade Assistant can be started again. However, once the upgrade phase has started, you will need to restore your pre-upgrade environment from backup before starting the Upgrade Assistant again.

Upgrade Summary

This screen allows you to review a summary of the options you have selected before you start the upgrade process.

- Reviewing the Upgrade Summary
Expand and collapse the tree to show or hide details about the data provided in the wizard screens, such as schema details and Oracle WebLogic domain directory information.

The Summary screen also displays the Source Version of the schema being upgraded and the resulting Target Version post upgrade. Make sure that both versions are correct before proceeding with the upgrade.

- Starting the Upgrade Process
Click Upgrade to start the upgrade process.

If you are upgrading a schema, verify that you have a backup of the database that hosts the schema.

- Save Response File
The Save Response File option creates a file that can be used as input to the Upgrade Assistant. The response file collects all the information that you have entered through the Upgrade Assistant's graphical user interface screens, and enables you to perform a silent upgrade at a later time. The silent upgrade performs exactly the same function that the Upgrade Assistant wizard performs, but you do not have to manually enter the data again.

Upgrade Progress

This screen displays the status of the upgrade process.

CAUTION: Do not cancel the upgrade process once it has started. Doing so may leave your components in an inconsistent state requiring a restore from backup.

Upgrade Success

This screen displays if 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. Note, however, that there may be additional post-upgrade tasks to perform. Consult your upgrade documentation.

Upgrade Failure

This screen displays if the upgrade failed for the specified component schema(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 were modified during this operation.

2.5 Understanding the Component Configurations Upgrade Screens

Describes the basic Upgrade Assistant screens seen in most component configuration upgrades.

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.

Use the Upgrade Assistant to upgrade the component configurations as described in this section.

Note:
This topic should be used for reference only. The Upgrade Assistant screens displayed when you upgrade your component configurations will vary depending on the options you select and the contents of your pre-upgrade environment. Always use your component-specific upgrade guides to complete an upgrade.

Table 2-5 Upgrade Assistant Screens: Upgrading Oracle WebLogic Component Configurations

Screen

Description

Welcome

This screen provides an overview of the Upgrade Assistant and some information about important pre-upgrade tasks.

All Configurations Used by a Domain

This screen appears when All Configurations Used by a Domain is selected as the upgrade type.

The All Configurations Used by a Domain option is used to upgrade component configurations for a managed WebLogic Server domain. Configuration upgrades are performed offline. You must enter the domain directory for the domain that you are upgrading.

WebLogic Server Component List

This screen appears 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.

Prerequisites

This screen requires you to acknowledge that all prerequisites have been met before you continue with the upgrade. Check the boxes before you continue.

NOTE: The Upgrade Assistant will not verify that the prerequisites have been met. For example, the Oracle Fusion Middleware Upgrade Assistant cannot detect if the servers and processes have been stopped as required.

Examine

This screen displays the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade.

The Upgrade Assistant examines each component to be sure it meets a minimum set of criteria before you begin the upgrade process.

Upgrade Assistant displays the schema Source Version of the schema on this screen if the information is listed in the schema version registry table. If the schema was not created using RCU, or the source version cannot be found, the source version will display unavailable

Status Definitions:

- in progress — The Upgrade Assistant is examining the upgrade items for the component.

- pending — The component will be examined when the Upgrade Assistant finishes the preceding component.

- failed — Upgrade items were missing or did not meet upgrade criteria. The Upgrade Assistant cannot upgrade the component until the issues have been resolved. Click View Log to troubleshoot the errors and then restart the Upgrade Assistant.

- succeeded — Upgrade items were found and are valid for upgrade.

- canceled — 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.

- upgrade not necessary— The component is already at the upgraded version or the component was upgraded in a previous run of the Upgrade Assistant.

- skipped— A dependent component has failed resulting in the examine of this component to be skipped.

Note:
Issues detected during the Examination phase may be resolved and the Upgrade Assistant can be started again. However, once the upgrade phase has started, you will need to restore your pre-upgrade environment from backup before starting the Upgrade Assistant again.

Upgrade Summary

Use this screen to review a summary of the options you have selected and to start the upgrade process.

Upgrade Progress

This screen shows the status of the upgrade process.

CAUTION: Do not cancel the upgrade process once it has started. Doing so may leave your components in an inconsistent state requiring a restore from backup.

Upgrade Success

This screen displays if 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. Note, however, that there may be additional post-upgrade tasks to perform.

Upgrade Failure

This screen displays if 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.

2.6 Performing Post-Upgrade Procedures

Complete any additional post-upgrade configuration tasks after the upgrade to verify that your newly upgrade domain is functioning as expected. Perform only those tasks that apply to your domain configuration.

After a successful upgrade it is important to verify that the servers can be started, the schema versions have been updated in the registry table, and the component configurations are correct. In some cases you may need to perform additional post-upgrade tasks based on the contents of your domain. Review the entire list of tasks to determine which are applicable.

NOTE: If you are unable to complete one or more of these tasks in your newly upgraded environment, see Troubleshooting Your Upgrade. Always refer to your component-specific upgrade documentation for more information on post-upgrade procedures.

- Performing Basic Post-Upgrade Administrative Tasks
Review the list of post-upgrade tasks and perform those that apply to your upgraded environment and domain configurations.

- Verifying a Successful Schema Upgrade

- Checking for Invalid Database Objects After an Upgrade
If you are using an Oracle database, recompile database objects after running the Upgrade Assistant.

2.6.1 Performing Basic Post-Upgrade Administrative Tasks

Review the list of post-upgrade tasks and perform those that apply to your upgraded environment and domain configurations.

These administrative tasks are optional, but Oracle strongly recommends that you verify your upgrade by performing the tasks.

Table 2-6 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 Oracle Fusion Middleware"

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.

"Starting and Stopping Applications"

Configuring Secure Sockets Layer (SSL)

Learn how to set up secure communications among between Oracle Fusion Middleware components using SSL.

"Configuring SSL in Oracle Fusion Middleware"

Deploying Applications

Learn how to deploy your applications to Oracle Fusion Middleware.

"Deploying Applications"

Monitoring Oracle Fusion Middleware

Learn how to keep track of the status of Oracle Fusion Middleware components.

"Monitoring Oracle Fusion Middleware"

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.

Oracle Fusion Middleware Installing and Configuring 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 Oracle Fusion Middleware 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 Oracle Fusion Middleware Developing Oracle Coherence Applications for Oracle WebLogic Server.

2.6.2 Verifying a Successful Schema Upgrade

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 ;

Validate that the numbers in the "VERSION" column are updated. It is possible that some schemas will remain at their pre-upgrade version if there were no changes required. For more information, see Table 1-1.

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.

2.6.3 Checking for Invalid Database Objects After an Upgrade

If you are using an Oracle database, recompile database objects after running the Upgrade Assistant.

To determine if any database objects were corrupted during the upgrade, recompile the database objects by connecting to the database as SYS and running the following from SQL*Plus:

SQL> @oracle_home/software/rdbms/admin/utlrp.sql

This will compile the database objects that were upgraded by Oracle Fusion Middleware 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.

3 Performing a Silent Upgrade with a Response File

Silent or “hands free” upgrades can be performed using a response file. The response file can only be created after you have provided the information in the Upgrade Assistant screens.

The following topics describe how you can upgrade the supported Oracle Fusion Middleware components using a response file. The response file collects all the information that you have entered through the Upgrade Assistant's graphical user interface screens, and performs exactly the same function that the Upgrade Assistant wizard performs.

Note:
You must run the Upgrade Assistant in GUI mode first to generate the response file that will be used to complete your silent upgrade.

- Creating an Upgrade Response File
You must run the Oracle Fusion Middleware Upgrade Assistant in graphical mode to generate a response file.

- Using the Response File to Upgrade Fusion Middleware
You can use a response file to record the information that you have entered through the Oracle Fusion Middleware Upgrade Assistant's screens, allowing you to later perform the same actions using the command line. Starting the Oracle Fusion Middleware Upgrade Assistant in this way is also known as silent mode.

3.1 Creating an Upgrade Response File

You must run the Oracle Fusion Middleware Upgrade Assistant in graphical mode to generate a response file.

The Save Response File option on the Upgrade Summary screen creates a file that uses the information you have already provided in the Oracle Fusion Middleware Upgrade Assistant screens. The response file enables you to use the saved information instead of manually entering data through the Oracle Fusion Middleware Upgrade Assistant wizard screens.

Once you select the Save Response File option, you will be prompted for a name and location where you want to create this response file. After it is created, you can use it exactly as-is to replicate the upgrade options on other systems, or modify it as needed.

3.2 Using the Response File to Upgrade Fusion Middleware

You can use a response file to record the information that you have entered through the Oracle Fusion Middleware Upgrade Assistant's screens, allowing you to later perform the same actions using the command line. Starting the Oracle Fusion Middleware Upgrade Assistant in this way is also known as silent mode.

Note:

You must run the Oracle Fusion Middleware Upgrade Assistant in GUI mode first to generate the response file that can be used to complete a silent readiness check or upgrade.

To start the Oracle Fusion Middleware Upgrade Assistant using a response file:

1. Navigate to the /upgrade/bin directory:
(UNIX) ORACLE_HOME/oracle_common/upgrade/bin

(Windows) ORACLE_HOME\oracle_common\upgrade\bin

2. Enter the following command to start the Oracle Fusion Middleware Upgrade Assistant using a response file:
(UNIX) ./ua -response response_file[-examine] [-logLevel log_level] [-logDir log_directory] [-threads number]

(Windows) ua.bat -response response_file[-examine] [-logLevel log_level] [-logDir log_directory] [-threads number]
For information about the optional command line parameters, see:

- Upgrade Assistant Parameters

3.2.1 Upgrade Assistant Parameters

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

Table 3-1 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 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 will create 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.

4 Troubleshooting Your Upgrade

Troubleshooting common problems and issues that may occur while you are using the Upgrade Assistant to upgrade your Oracle Fusion Middleware deployment to this release.

- Troubleshooting an Upgrade
It is useful to understand the errors you might get while running the Upgrade Assistant. And it is equally important to know how to troubleshoot them.

- Reviewing Log Files
You must not delete the Log files. They help diagnose and correct the problem while running Oracle Fusion Middleware Upgrade Assistant.

- Investigating Examination Failures
Learn about identifying and troubleshooting failures that might occur during the examination phase of the upgrade.

- Investigating Upgrade Failures
Learn about identifying and troubleshooting Upgrade failures.

- Resolving Common Oracle Fusion Middleware Upgrade Assistant Errors
If errors occur while you are running the Oracle Fusion Middleware Upgrade Assistant, you must correct the conditions that caused them before you try the upgrade again.

- Attempting to Upgrade an Unsupported Domain
Do not attempt to upgrade the schemas or domain configurations in an unsupported domain.

- Restarting the Upgrade Assistant After a Failure
You must resolve errors before you restart the Upgrade Assistant.

4.1 Troubleshooting an Upgrade

It is useful to understand the errors you might get while running the Upgrade Assistant. And it is equally important to know how to troubleshoot them.

If errors occur while you are running the Upgrade Assistant, use the following steps to troubleshoot the problem:

NOTE: Your corrective course of action will depend on the phase in which the error occurred.

1. Locate and open the Oracle Fusion Middleware Upgrade Assistant log file with a text editor:

For the location of the log file, see Reviewing Log Files.

2. To verify the correct version of Oracle Fusion Middleware Upgrade Assistant jar file run the following command:

unzip -p ua.jar META-INF/MANIFEST.MF

You can run this command only after you change directory to the jlib directory:.

cd ORACLE_HOME/oracle_common/upgrade/jlib

Note:
The output of the unzip -p ua.jar META-INF/MANIFEST.MF command identifies the development label that was used to build the Oracle Fusion Middleware Upgrade Assistant, and that information identifies the date and version of the Oracle Fusion Middleware Upgrade Assistant software that was run. If you raise a Service Request you need to provide this information to Oracle.

3. Locate any error messages that are identified by number; for example, UPGAST-00091.

4. Look up the error in the Oracle Fusion Middleware Error Messages guide.

The description of the error in the should include a description of the cause of the error, as well as the action you should take to resolve the error.

5. Based on whether or not you can locate an error message and the error message description, do the following:

- If, by reviewing the log files and error message descriptions, you are able to identify a solution to the upgrade failure, you can implement your solution and then re-start the Oracle Fusion Middleware Upgrade Assistant and perform the upgrade again.
When you re-run the Oracle Fusion Middleware Upgrade Assistant, any components that were upgraded successfully during the previous run will not be affected. However, the Oracle Fusion Middleware Upgrade Assistant will attempt to upgrade any components that were not upgraded successfully during a previous run of the utility.

- Contact Oracle Support for any errors that are not documented or that cannot be resolved by following documented actions. Note that some errors that occur will require the repository to be restored from backup, the problem to be resolved, and another upgrade to be run. Note that Oracle Support requires both the UA.log file and if present, the UA.out file, to be provided for troubleshooting purposes. Provide complete logs and not just excerpts of those files.

Note:

If you get any errors during Examination phase, and no components or schemas have been upgraded yet, run the readiness check. The types of checks performed by the readiness check are more thorough than Examination phase of upgrade.

Errors that occur during or after the upgrade, however, require you to restore your environment from your backup copies, correct the errors and then restart the upgrade process from the beginning.

4.2 Reviewing Log Files

You must not delete the Log files. They help diagnose and correct the problem while running Oracle Fusion Middleware Upgrade Assistant.

When running the Oracle Fusion Middleware Upgrade Assistant, you can alter the contents of your log files by specifying a different -logLevel from the command line. The default value is -logLevel NOTIFICATION. You can alter the location of your log files using the -logDir parameter. You can obtain a more detailed logging information by running the Oracle Fusion Middleware Upgrade Assistant with -logLevel TRACE parameter. However, in some situations, this can cause the log file to become very large.

Note:
TRACE messages are not included in the Oracle Fusion Middleware Upgrade Assistant Log File Viewer. To view TRACE messages you must use another tool of your choice

Tip:
To expedite the review process, search for the word "ERROR".

For more information on understanding error messages in your log files, see Resolving Common Oracle Fusion Middleware Upgrade Assistant Errors.

Log files are stored in the following default directory:

On UNIX operating systems:

ORACLE_HOME/oracle_common/upgrade/logs/ua<timestamp>.log

On Windows operating systems:

ORACLE_HOME\oracle_common\upgrade\logs\ua<timestamp>.log

Some components will create a second log file called ua<timestamp>.out, also in the same location.

Where, timestamp states the actual date and time when the Oracle Fusion Middleware Upgrade Assistant was run.

For database schema upgrades of certain components, there can also be an output (.out) file that will contain the screen output of commands that were run in a shell process or as PL/SQL scripts. You can locate these output files in the same default directory.

In the event that there are questions or issues about an upgrade failure that cannot be resolved with the information in this guide, it will be important to retain the log files. If you must raise a service request, you must upload the entire Oracle Fusion Middleware Upgrade Assistant .log file and the .out files (if available) along with the service request.

4.3 Investigating Examination Failures

Learn about identifying and troubleshooting failures that might occur during the examination phase of the upgrade.

To determine the cause of an examination failure:

1. Note the name of the failed component in the Upgrade Assistant dialog or command-line output.

2. Open the following Upgrade Assistant log file.

For the location of the log file, see Reviewing Log Files.

3. In the log file, search for the message Starting to examine component_name.

To complete the upgrade, resolve the issues and then launch the Upgrade Assistant again, or, if possible, click Back to return to a previous screen and make the necessary changes.

Note:
The readiness check feature performs checks to a far greater level of detail than the Examination phase. If examine fails you should run the Upgrade Assistant with the -readiness parameter and make sure the report does not show any test failures.

Issues detected during the Examination phase can be resolved without restoring from backup. However, if you attempt to resolve an examination error in a way that changes the state of the system, you need to restore the entire system to the pre-upgrade state (before any upgrade operations were attempted).

Issues detected during the Upgrade cannot be resolved (during Upgrade) without restoring from backup. The pre-upgrade environment must be restored from backup to the original pre-upgrade state.

4.4 Investigating Upgrade Failures

Learn about identifying and troubleshooting Upgrade failures.

To determine the cause of an upgrade failure:

1. Note the name of the failed component in the Oracle Fusion Middleware Upgrade Assistant dialog or command-line output.

2. Open the Upgrade log file:

For the location of the log file, see Reviewing Log Files.

3. Search for the message Starting to upgrade component_name.

To complete the upgrade, restore the entire environment using your pre-upgrade backup, to a point in time before any upgrade operations were attempted, resolve the issues and then launch the Oracle Fusion Middleware Upgrade Assistant again. You will have to start the upgrade process from the beginning to ensure a successful (complete) upgrade.

Note:
You should be backing up all databases with RMAN and be able to do a point-in-time recovery from those backups. If the Fusion Middleware repository for your domains spans multiple Oracle Database server, you must restore from each of those backups.

4.5 Resolving Common Oracle Fusion Middleware Upgrade Assistant Errors

If errors occur while you are running the Oracle Fusion Middleware Upgrade Assistant, you must correct the conditions that caused them before you try the upgrade again.

This section provides descriptions of the most common upgrade errors. For a complete list of Fusion Middleware errors, see the Oracle Fusion Middleware Error Messages guide.

- Ensuring there is sufficient disk space

- Resolving Database Connection Problems When Upgrading Schemas

4.5.1 Ensuring there is sufficient disk space

If an upgrade fails due to the database server running out of disk space, you must restore the database server environment from backups, add sufficient disk space or remove unwanted files (such as temp or trace files) from the database server, and then retry the upgrade.

NOTE: Once a database schema upgrade has failed due to this class of error, you cannot simply add more disk space and retry the upgrade. The schemas have been left in an inconsistent state and may have been marked "INVALID". You cannot recover from this error without restoring the original database state from backups.

The following examples show some insufficient disk space errors you may encounter:

ORA-01658: unable to create INITIAL extent for segment in tablespace

Cause: The existing schema tablespace does not have sufficient space to complete the upgrade.

Action: Make sure that the tablespace has sufficient room (space) for a successful upgrade. Oracle recommends that you add more data files to the existing database tablespaces, otherwise the upgrade will fail.

ORA-01114: IO error writing block to file <block number>

Cause: The device on which the file resides is probably offline. If the file is a temporary file, then it is also possible that the device has run out of space. This could happen because disk space of temporary files is not necessarily allocated at file creation time.

Action: Restore access to the device or remove unnecessary files to free up space.

ORA-09945: Unable to initialize the audit trail file

Cause: The system is unable to write header information to the file being used as the audit trail. The audit_trail_dest or audit trail destination is full for generation of audit file.

Action: Free up space and retry the operation.

4.5.2 Resolving Database Connection Problems When Upgrading Schemas

If you have trouble connecting to a database when using the Upgrade Assistant to upgrade a component schema, try connecting to the database using another tool, such as SQL*Plus. This will help you troubleshoot the problem by verifying that the database is up and running and available on the network.

4.6 Attempting to Upgrade an Unsupported Domain

Do not attempt to upgrade the schemas or domain configurations in an unsupported domain.

If you receive an error stating that the specified domain cannot be upgraded, you must first upgrade the domain to a supported version. Do not attempt to upgrade schemas or domain configurations in an unsupported domain.

4.7 Restarting the Upgrade Assistant After a Failure

You must resolve errors before you restart the Upgrade Assistant.

If the Upgrade Assistant fails during the upgrade phase, or only partially upgrades your components, try to resolve the issues and then follow these steps:

1. Restore the entire 11g or 12c environment to your pre-upgrade backup.

2. Restart the Upgrade Assistant.

If you continue to experience upgrade failures, consider setting -logLevel to TRACE so that more information is logged. This is useful when troubleshooting a failed upgrade, but be sure to reset -logLevel to NOTIFICATION after the issue has been resolved to avoid performance issues.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2018, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.