Pre-Upgrade Tasks for Oracle WebCenter Components

2 Pre-Upgrade Tasks for Oracle WebCenter Components

You can use the pre-upgrade checklists to determine which tasks must be completed before you start the upgrade. The tasks that you perform will vary depending on your existing deployment and the components and configurations that are being upgraded. Do not start an upgrade until you have reviewed the list and completed all required tasks.

Note:

Before you start any upgrade, make sure that you have created a complete backup of your pre-upgrade environment. If the upgrade fails, you will have to restore from backup and restart the upgrade.

Pre-Upgrade Checklist

The Pre-Upgrade Checklist identifies tasks that can be performed before you begin your upgrade to ensure that you have a successful upgrade and limited downtime.

Upgrades are performed while the servers are down. This checklist is meant to identify important — and often time-consuming — pre-upgrade tasks that you can perform before the upgrade to limit your downtime. The more preparation you can do before you begin the upgrade process, the less time you spend offline.

Note:

The pre-upgrade procedures you perform depend on the configuration of your existing system, the components you are upgrading, and the environment that you want to create at the end of the upgrade and configuration process. Complete only those tasks that apply to your configurations or use cases.

This table describes the Pre-Upgrade Checklist. It lists all the required components and describes them in detail.

Table 2-1 Tasks to Perform Before You Upgrade Oracle Fusion Middleware

Task Description

Task	Description
Required Create a complete backup of your existing environment.	Back up all system-critical files and databases that contain any schemas that are to be upgraded. If the upgrade fails, you must restore your pre-upgrade environment and begin the upgrade again. See Creating a Complete Backup. Make sure that your backup includes the schema version registry table. See Backing Up the Schema Version Registry Table. If you have modified or customized any of the startup scripts or any of the configuration files in your existing domain (for example, setting a value for the cookie-path property), you need to copy them to the temporary directory location (outside of the existing domain) during the upgrade, and redeploy them after the upgrade.
Optional Clone your production environment to use as an upgrade testing platform.	In addition to creating a complete backup of your system files, Oracle strongly recommends that you clone your production environment. This environment can be used to test the upgrade.
Required Verify that you install and upgrade your product on a supported hardware and software configuration. CAUTION: Do not attempt an upgrade if you are unable to use the latest supported operating system. As with all supported configurations, failure to comply with these requirements may cause your upgrade to fail.	Verify that your hardware and software configurations (including operating systems) are supported by the latest certifications and requirements documents. Also make sure to use a supported JDK version before you install the product distributions. Oracle recommends that you verify this information right before you start the upgrade as the certification requirements are frequently updated. Make sure that you have applied the latest patches to your components before you upgrade. See Verifying Certification and System Requirements.
Optional Create a Non-SYSDBA user to run the Upgrade Assistant with necessary privileges.	Oracle recommends that you create the FMW user to run the Upgrade Assistant. The FMW user can run the Upgrade Assistant without any system administration privileges. See Creating a Non-SYSDBA User to Run the Upgrade Assistant.
Required If you are using auto_login wallet, you must update wallet files.	Auto_login_only wallets are the only supported wallets in 14c (14.1.2.0.0). Before upgrading to 14c (14.1.2.0.0), you must update all existing 12c (12.2.1.4.0) auto_login wallets to auto_login_only using convert_to_auto_login_only.pl. See Convert Auto_login Wallets to Auto_login_only.
Required Linux and UNIX Operating System users must set their `DISPLAY` environment variables before starting the Fusion Middleware tools.	Setting the DISPLAY Environment Variable If the `DISPLAY` environment variable is not set up properly to allow for GUI mode, you may encounter an error.

Required

Create a complete backup of your existing environment.

Back up all system-critical files and databases that contain any schemas that are to be upgraded. If the upgrade fails, you must restore your pre-upgrade environment and begin the upgrade again.

See Creating a Complete Backup.

Make sure that your backup includes the schema version registry table. See Backing Up the Schema Version Registry Table.
If you have modified or customized any of the startup scripts or any of the configuration files in your existing domain (for example, setting a value for the cookie-path property), you need to copy them to the temporary directory location (outside of the existing domain) during the upgrade, and redeploy them after the upgrade.

Optional

Clone your production environment to use as an upgrade testing platform.

In addition to creating a complete backup of your system files, Oracle strongly recommends that you clone your production environment. This environment can be used to test the upgrade.

Required

Verify that you install and upgrade your product on a supported hardware and software configuration.

CAUTION: Do not attempt an upgrade if you are unable to use the latest supported operating system. As with all supported configurations, failure to comply with these requirements may cause your upgrade to fail.

Verify that your hardware and software configurations (including operating systems) are supported by the latest certifications and requirements documents. Also make sure to use a supported JDK version before you install the product distributions.

Oracle recommends that you verify this information right before you start the upgrade as the certification requirements are frequently updated.

Make sure that you have applied the latest patches to your components before you upgrade.

See Verifying Certification and System Requirements.

Optional

Create a Non-SYSDBA user to run the Upgrade Assistant with necessary privileges.

Oracle recommends that you create the FMW user to run the Upgrade Assistant. The FMW user can run the Upgrade Assistant without any system administration privileges.

See Creating a Non-SYSDBA User to Run the Upgrade Assistant.

Required

If you are using auto_login wallet, you must update wallet files.

Auto_login_only wallets are the only supported wallets in 14c (14.1.2.0.0). Before upgrading to 14c (14.1.2.0.0), you must update all existing 12c (12.2.1.4.0) auto_login wallets to auto_login_only using convert_to_auto_login_only.pl.

See Convert Auto_login Wallets to Auto_login_only.

Required

Linux and UNIX Operating System users must set their DISPLAY environment variables before starting the Fusion Middleware tools.

Setting the DISPLAY Environment Variable

If the DISPLAY environment variable is not set up properly to allow for GUI mode, you may encounter an error.

Creating a Complete Backup

Before you start an upgrade, back up all system-critical files, including the databases that host your Oracle Fusion Middleware schemas.

The backup must include the 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.

See:

Backing Up Your Environment in Administering Oracle Fusion Middleware
Upgrading and Preparing Your Oracle Databases for 14c (14.1.2.0.0) in Planning an Upgrade of Oracle Fusion Middleware

Backing Up the Schema Version Registry Table

Your system backup must include the SYSTEM.SCHEMA_VERSION_REGISTRY$ table or the FMWREGISTRY.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. Before you run the Upgrade Assistant, make sure you back up your existing database schemas and the schema version registry.

Note:

Before you upgrade a schema using the Upgrade Assistant, you must perform a complete database backup. During the upgrade, you are required to acknowledge that backups have been performed.

Maintaining Customized Domain and Environment Settings

If you have modified any domain-generated, server startup scripts, or configuration files in your pre-upgrade environment, it is important to note that these changes are overwritten during the installation, domain upgrade, and reconfiguration operations. Save your customized files to a shared library location so that you can continue to use them after the upgrade.

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. When using the pack and unpack commands, any custom settings that you add to this file are preserved during the domain upgrade operation and are carried over to the remote servers.

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 EXISTING_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 Upgrading Oracle WebLogic Server.

Cloning Your Source Environment for Testing

Create a copy of your source environment, upgrade the cloned environment, verify that the upgraded components work as expected, and then (and only then) upgrade your environment.

Cloning your source environment for testing is recommended, but not required.

Upgrades cannot be reversed. In most cases, if an error occurs, you must stop the upgrade and restore the entire environment from backup and begin the upgrade process from the beginning. Identifying potential upgrade issues in a cloned environment can eliminate unnecessary downtime.

Note:

It is beyond the scope of this document to describe the cloning procedures for all components and operating systems. Cloning procedures are component and operating system-specific. At a high level, you install the pre-upgrade version of your component domain on a test machine, create the required schemas using the Repository Creation Utility (RCU), and perform the upgrade.

Additional benefits of running an upgrade in a cloned environment include the following:

Uncover and correct any upgrade issues.
Practice completing an end-to-end upgrade.
Understand the upgrade performance and how purge scripts can help.
Understand the time required to complete the upgrade.
Understand the database resource usage (such as temporary tablespace; PGA, and so on).

Note:

You can run the pre-upgrade Readiness Check on the cloned environment to help identify potential upgrade issues with your data, but you must perform a complete test upgrade on a cloned environment to ensure a successful upgrade.

Verifying Certification and System Requirements

Review the certification matrix and system requirements documents to verify that your environment meets the necessary requirements for installation. You may be required to upgrade your operating system, hardware or other software packages.

Note:

When checking the certification, system requirements, and interoperability information, be sure to check specifically for any operating system requirements. It is important for you to download software specifically designed for your operating system environment, explicitly.

WARNING:

Make sure that your current environment has been patched to the latest patch set before you begin the upgrade. Certifications are based on fully patched environments, unless stated otherwise.

Verify Your Environment Meets Certification Requirements

Oracle has tested and verified the performance of your product on all certified systems and environments. Make sure that you are installing your product on a supported hardware or software configuration.

Whenever new certifications occur, they are added to the appropriate certification document right away. New certifications can occur at any time, and for this reason the certification documents are kept outside of the documentation libraries and are available on Oracle Technology Network. See the Certification Matrix for 14c (14.1.2.0.0).

Verify System Requirements and Specifications

It is important to use both the System Requirements and Specifications document and the Oracle Fusion Middleware Certification Matrix to verify that the system requirements such as disk space, available memory, specific platform packages and patches, and other operating system-specific items are met.

Use the Oracle Fusion Middleware System Requirements and Specifications document to verify that the requirements of the Oracle Fusion Middleware Certification matrix are met. For example, if the Certification Matrix indicates that your product is certified for installation on 64-Bit Oracle Linux 8, the System Requirements and Specifications document should be used to verify that your Oracle Linux 8 system has met the required minimum specifications such as disk space, available memory, specific platform packages and patches, and other operating system-specific items. This document is updated as needed and resides outside of the documentation libraries on the Oracle Technology Network (OTN).

Note:

Do not attempt an upgrade if you are unable to meet the minimum system requirements.

Specifically, you can use the Oracle Fusion Middleware System Requirements and Specifications document to verify the following:

Processor Requirements
Java Development Kit (JDK) Requirements
General Memory and Disk Space Requirements
Product-Specific Memory and Disk Space Requirements
Network Requirements
UNIX Operating System Requirements
Windows Operating Systems Requirements
Virtualization Requirements
Database Requirements

What if my operating system is not supported?

If you are running your environment on an unsupported operating system, you will need to create a supported environment before you begin your upgrade. Do not attempt an upgrade on an unsupported operating system.

Use the migration steps for your environment.

Migrating a Managed Domain from an Unsupported Operating System

If you are currently running your managed or collocated Oracle Fusion Middleware domain on an unsupported operating system, then you must migrate your existing environment to a supported operating system before you upgrade.

After the migration, validate that all of your existing Oracle Fusion Middleware 12c (12.2.1.4.0) software is working properly on the updated machine, and only then perform the upgrade to Oracle Fusion Middleware 14c (14.1.2.0.0).

In these tasks, host refers to the existing unsupported source machine and target refers to the new supported target machine.

Note:

These steps assume that your database is located on a separate host and will not be moved.

Upgrading an operating system typically involves the following:

Caution:

These steps are provided as an example of the operating system upgrade process and may or may not include all of the procedures you must perform to update your specific operating system. Consult your operating system's upgrade documentation for more information.

Stopping Servers and Processes

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

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

Note:

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

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

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

Note:

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

Step 1: Stop System Components

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

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

You can stop system components in any order.

Step 2: Stop Any Managed Servers

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

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

When prompted, enter your user name and password.

Step 3: Stop the Administration Server

To stop the Administration Server, use the stopWebLogic script:

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

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

Step 4: Stop Node Manager

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

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

Back Up All Files from the Host Machine

Make sure that you have created a complete backup of your entire 12c (12.2.1.4.0) deployment before you begin the upgrade process. These files can be used if there is an issue during the migration and you have to restart the process.

Note:

If the operating system upgrade takes place on the same machine, there is a risk of corrupting the source environment if the upgrade fails.

For general information about creating a complete backup of your existing environment, see Backing Up Your Environment in Oracle Fusion Middleware Administrator's Guide.

During the upgrade you must have access to the contents of the following:

12c_DOMAIN_HOME
12c/nodemanager directory located in 12c_ORACLE_HOME/wlserver/common/

The following steps explain how to use the pack command to create a domain template jar file. This is only one method that can be used to create a backup. Consult your own backup and recovery plans to choose the backup method that best suits your deployment.

Pack the domain that was created on the unsupported host using the pack command as follows:

cd ORACLE_HOME/oracle_common/common/bin/

./pack.sh -domain=/scratch/username/<product>_12214/user_projects/domains/base_domain -template=/scratch/<product>.jar - template_author=<user_name> -template_name=<product>_domain

Copy the domain template jar file that you just created to the new supported host.
Do not unpack the jar file. At this stage you are just copying the file to a temporary location on the new host until it is time to unpack the domain into the new 14.1.2 Oracle Home. To simplify the unpack process, consider recreating the exact same directory structure that you used in your 12.2.1.4 domain. This will ensure that the file is not overwritten.

Note:

Do not proceed with the upgrade until you have a complete backup.

Set Up the Target Machine with the 12c Host Name and IP Address

The host name and IP address of the target machine must be made identical to the host. This requires you to change the IP address and name of the source machine or decommission the source machine to avoid conflicts in the network.

The process of changing an IP address and host name vary by operating system. Consult your operating system's administration documentation for more information.

Copy the Contents of the Domain Template to the New Target Host

Unpack the contents of the generated domain template jar file on the target host. The directory structure on the target machine must be identical to the structure of the host machine.

On the target machine, navigate to the new Oracle home.
```
cd 1412_ORACLE_HOME/oracle_common/common/bin/
```

Use the unpack command to copy the files to the new target:

./unpack.sh -domain=/scratch/<username>/<product>_12214/user_projects/domains/base_domain -template=/scratch/<product>.jar -user_name=weblogic -password=<enter your password>

Install the 14c (14.1.2.0.0) Product Distributions on the Target Machine

Oracle recommends an Out-of-Place approach for upgrade. Therefore, you must install the product distributions in a new Oracle home on the target machine.

Refer to the component-specific installation guides for the component(s) you are installing.

Upgrade the Target Environment Using the Standard Upgrade Procedure

After installing the product on the target machine, you must upgrade each product component individually using an Upgrade Utility specified in the component-specific upgrade guide and complete any post-upgrade tasks.

If you are upgrading additional components, see the component-specific upgrade guide.

Note:

The Node Manager upgrade procedure requires access to the original Node Manager files. Use the 12c (12.2.1.4.0) Node Manger files that you backed up from the source machine.

Verify That the Database Hosting Oracle Fusion Middleware is Supported

You must have a supported Oracle database configured with the required schemas before you run Oracle Fusion Middleware 14c (14.1.2.0.0).

Review the Fusion Middleware database requirements before starting the upgrade to ensure that the database hosting Oracle Fusion Middleware is supported and has sufficient space to perform an upgrade. See the Certification Matrix for 14c (14.1.2.0.0).

Note:

If your database version is no longer supported, you must upgrade to a supported version before starting an upgrade.

Verify That the JDK Is Certified for This Release of Oracle Fusion Middleware

At the time this document was published, the certified JDK for 14c (14.1.2.0.0) was 17.0.12.

Refer to the Oracle Fusion Middleware Supported System Configurations information on the Oracle Technology Network (OTN) to verify that the JDK you are using is supported.

If your JDK is not supported, or you do not have a JDK installed, you must download the required Java SE JDK, from the following website:

http://www.oracle.com/technetwork/java/javase/downloads/index.html

Make sure that the JDK is installed outside of the Oracle home. The Oracle Universal Installer validates that the designated Oracle home directory is empty, and the install does not progress until an empty directory is specified. If you install JDK under Oracle home, you may experience issues in future operations. Therefore, Oracle recommends that you use install the JDK in the following directory: /home/oracle/products/jdk.

For more information on the difference between generic and platform-specific installers, see Understanding the Difference Between Generic and Platform-Specific Distributions in the Oracle Fusion Middleware Download, Installation, and Configuration Readme Files.

Verify the Database User for the WLSSchemaDataSource Data Source

This step is required if your existing domain has a WLSSchemaDataSource data source.

If your domain has the WLSSchemaDataSource data source, then you will need to verify which database user is assigned to it. If <PREFIX>_WLS_RUNTIME is assigned to it, then you need to change that to <PREFIX>_WLS .

This change is necessary due to the following changes:

The 14c (14.1.2.0.0) Upgrade Assistant uses the information in the WLSSchemaDataSource data source,when a domain-based schema upgrade is performed. That upgrade will fail if the <PREFIX>_WLS database user is not assigned to the WLSSchemaDataSource, or if <PREFIX>_WLS is not entered as the "Schema User Name" on the "WLS Schema" page of the Upgrade Assistant.
Oracle recommends that you use the 12c Oracle WebLogic Administration Console to change the database user to <PREFIX>_WLS in the WLSSchemaDataSource data source. Doing this will avoid the Upgrade Assistant failure, and also allow the Reconfiguration Wizard to pre-populate fields with the correct values.
The <PREFIX>_WLS_RUNTIME database user is reserved for use with a new WLSRuntimeSchemaDataSource, which was introduced in 14c (14.1.2.0.0). This new WLSRuntimeSchemaDataSource will be created when the 14c (14.1.2.0.0) Reconfiguration Wizard (reconfig.sh) is used to upgrade the domain.

You can use your Oracle WebLogic 12c Administration Console to change the user in the WLSSchemaDataSource from <PREFIX>_WLS_RUNTIME to <PREFIX>_WLS.

Log in the 12c (12.2.1.4.0) Administration Console.
In the administration console under Domain Structure, expand Services (by clicking the + next to it). Then click Data Sources.
If the user in Properties field contains <PREFIX>_WLS_RUNTIME , change it to<PREFIX>_WLS.
Save the change.
Use the Change Center to commit the change, if your domain is running in production mode.

Updating Policy Files when Using Enhanced Encryption (AES 256)

If you plan to use enhanced encryption, such as Advanced Encryption Standard (AES) 256, in your upgraded environment, Oracle recommends that you apply the latest required policy files to the JDK before you upgrade.

The Java platform defines a set of APIs spanning major security areas, including cryptography, public key infrastructure, authentication, secure communication, and access control. These APIs allow developers to easily integrate security mechanisms into their application code.

Some of the security algorithms used in Fusion Middleware 14c (14.1.2.0.0) require additional policy files for the JDK. See Java Cryptography Architecture Oracle Providers Documentation.

Note:

If you attempt to use enhanced encryption without applying these policy files to the JDK before you begin the upgrade, the upgrade can fail and you must restore the entire pre-upgrade environment and start the upgrade from the beginning.

Purging Unused Data

Purging unused data and maintaining a purging methodology before an upgrade can optimize the upgrade process.

Some components have automated purge scripts. If you are using purge scripts, wait until the purge is complete before starting the upgrade process. The upgrade may fail if the purge scripts are running while using the Upgrade Assistant to upgrade your schemas.

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 below must be granted to user FMW before starting the Upgrade Assistant.

Notes:

The non-SYSDBA user FMW is created solely for the purpose of running the Upgrade Assistant. After this step is complete, drop the FMW user. Note that privileges required for running the Upgrade Assistant may change from release to release.

Note:

In this example we are using the name FMW for our non-SYSDBA administrator. Substitute FMW with your admin name.

When granting privileges, make sure that you specify your actual user names and password for the schemas in your domain.

CREATE USER FMW IDENTIFIED BY "<FMW password>";
GRANT pdb_dba TO FMW;
GRANT MANAGE SCHEDULER TO FMW;
GRANT USE ON EDITION ORA$BASE TO FMW WITH GRANT OPTION;
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_aq 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 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_job 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 EXECUTE ON SYS.DBMS_ASSERT 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 dba_objects TO FMW WITH GRANT OPTION;
GRANT SELECT ON dba_queue_subscribers TO FMW WITH GRANT OPTION;
GRANT SELECT ON dba_subscr_registrations TO FMW WITH GRANT OPTION;
GRANT EXECUTE ON DBMS_RLS TO FMW WITH GRANT OPTION;
GRANT READ ON CTXSYS.CTX_PENDING TO FMW WITH GRANT OPTION;
GRANT SELECT ON SYS.V_$PARAMETER TO FMW WITH GRANT OPTION;
GRANT CREATE PROCEDURE TO FMW;
GRANT SELECT ON dba_users TO FMW WITH GRANT OPTION;
GRANT ALL ON sys.v_$parameter TO FMW WITH GRANT OPTION;

Identifying Existing Schemas Available for Upgrade

This optional step can be used before an upgrade to query the schema version registry table. This table contains schema information such as the schema owner, version number, component name and ID, date of creation and modification, and custom prefixes.

You can let the Upgrade Assistant upgrade all of the schemas in the domain, or you can select individual schemas to upgrade. To help decide, follow these steps to view a list of all the schemas that are available for an upgrade:

If you are using an Oracle database, connect to the database by using an account that has Oracle DBA privileges, and run the following from SQL*Plus:

SET LINE 120
COLUMN MRC_NAME FORMAT A14
COLUMN COMP_ID FORMAT A20
COLUMN VERSION FORMAT A12
COLUMN STATUS FORMAT A9
COLUMN UPGRADED FORMAT A8
SELECT MRC_NAME, COMP_ID, OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY WHERE OWNER LIKE UPPER('<PREFIX>_%');

Examine the report that is generated.

Notes:

After the upgrade you can generate the report again to see the updated versions of your schemas. If an upgrade was not needed for a schema, the schema_version_registry table retains the schema at its pre-upgrade version.
If your existing schemas are not from a supported version, then you must upgrade them to a supported version before using the 14c (14.1.2.0.0) upgrade procedures. Refer to your pre-upgrade version documentation for more information.
If you used an OID-based policy store in the earlier versions, make sure to create a new OPSS schema before you perform the upgrade. After the upgrade, the OPSS schema remains an LDAP-based store.
You can only upgrade schemas for products that are available for upgrade in Oracle Fusion Middleware release 14c (14.1.2.0.0). Do not attempt to upgrade a domain that includes components that are not yet available for upgrade to 14c (14.1.2.0.0).

Convert Auto_login Wallets to Auto_login_only

Before upgrading the Oracle HTTP Server (OHS) instance to 14c (14.1.2.0.0), all existing OHS auto_login wallets must be converted to auto_login_only using convert_to_auto_login_only.pl.

As of Oracle HTTP Server (OHS) 14c (14.1.2.0.0), Auto_login_only wallets are the only supported wallets. You will need to identify and convert any auto_login wallets to auto_login_only before starting the server.

Identify all auto_login wallets. The auto_login wallets will have 2 additional files:
```
cwallet.sso
ewallet.p12
```

Use the convert_to_auto_login_only.pl script to convert each auto_login wallet to auto_login_only.

Usage:
perl <path_to_convert_to_auto_login_only.pl> <auto_login_wallet directory> <auto_login_only_wallet directory>
<Password of auto_login_wallet>
auto_login_wallet directory - Directory path to the existing auto_login wallet directory
auto_login_only_wallet directory - Directory path to the new auto_login_only wallet directory, directory will be created
by the tool
Password of auto_login_wallet - Optional: Password of the existing auto_login wallet

The following commands use the default wallet as an example. You must adjust the directory path for your specific environment -DOMAIN_HOME and ORACLE_HOME environment variables must be set prior to running following commands:

Linux/Unix:
cd $DOMAIN_HOME/config/fmwconfig/components/OHS/ohs1/keystores/
$ORACLE_HOME/perl/bin/perl $ORACLE_HOME/ohs/common/bin/convert_to_auto_login_only.pl default default/auto_login_only
Windows:
cd %DOMAIN_HOME%\config\fmwconfig\components\OHS\ohs1\keystores
%ORACLE_HOME%\perl\bin\perl %ORACLE_HOME%\ohs\common\bin\convert_to_auto_login_only.pl default default\auto_login_only

Update all wallet directives to use the new auto_login_only_wallet directory.

Sample entries (you must adjust the directory path for your specific environment):

#SSLWallet "${ORACLE_INSTANCE}/config/fmwconfig/components/${COMPONENT_TYPE}/instances/${COMPONENT_NAME}/keystores
/default"
SSLWallet "${ORACLE_INSTANCE}/config/fmwconfig/components/${COMPONENT_TYPE}/instances/${COMPONENT_NAME}/keystores/default
/auto_login_only"
#WLSSLWallet "${ORACLE_INSTANCE}/config/fmwconfig/components/${COMPONENT_TYPE}/instances/${COMPONENT_NAME}/keystores
/default"
WLSSLWallet "${ORACLE_INSTANCE}/config/fmwconfig/components/${COMPONENT_TYPE}/instances/${COMPONENT_NAME}/keystores
/default/auto_login_only"

Note:

The convert_to_auto_login_only.pl script does not import requested certificates (CSRs). If a certificate signing request (CSR) is required, then a new auto_login_only wallet will need to be created.

After the upgrade you will need to run another script to remove version information from the files located in the htdocs directory. See unresolvable-reference.html#GUID-FA91B77F-3539-40AC-83CE-AB638C491453.

Setting the DISPLAY Environment Variable

If the DISPLAY environment variable is not set up properly to allow for GUI mode, you may encounter an error.

Linux and UNIX Operating System Users:

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.

Performing the Oracle WebCenter Pre-Upgrade Tasks

Before upgrading to Oracle WebCenter products 14c (14.1.2.0.0), perform pre-upgrade tasks that apply to your environment.

The pre-upgrade tasks for Oracle WebCenter include the following:

Pre-Upgrade Task	More Information
Disable all deprecated or obsolete components before upgrade.	Disabling Obsolete Components Before Upgrade
Export metadata for Portlet Producer Applications	Exporting Metadata for Portlet Producer Applications
Complete the pre-upgrade tasks for Oracle WebCenter Content (if you will be upgrading Content or WebCenter Content Web UI).	Performing Pre-Upgrade Tasks for WebCenter Content
Complete the pre-upgrade tasks for Oracle WebCenter Enterprise Capture (if you will be upgrading Enterprise Capture).	Performing Pre-Upgrade Tasks for Oracle WebCenter Enterprise Capture

Disabling Obsolete Components Before Upgrade

The following components should be disabled before the upgrade because they are obsolete or disabled.

Note:

Failure to disable these components may cause the upgrade to fail and content servers will not be able to start.

CheckoutAndOpenInNative
CIS_Helper
ContentTrackerReports
SiteStudioExternalApplications
FormEditor (which uses the now deprecated FCKEditor)
proxyconnections8
UrmAgent
PDFExportConverter (IBR)
Folders_g

For more information about disabling components, see Enabling or Disabling a Component Using the Component Manager in Administering Oracle WebCenter Content.

Exporting Metadata for Portlet Producer Applications

If your application is consuming any preconfigured portlet producers, which includes the WSRP Parameter Form Portlet, the sample WSRP portlet producers, and sample PDK-Java portlet producers, then you need to run the exportPortletClientMetadata WLST command to export portlet client metadata and producer customizations and personalizations for WebCenter Portal.

exportPortletClientMetadata(appName='webcenter', fileName='/tmp/portletClientExport.ear')