5 Upgrading a Standalone Oracle HTTP Server from a Previous 12c Release

This chapter describes the process to upgrade a Standalone Oracle HTTP Server to the latest 12c from a previous Standalone Oracle HTTP Server 12c release.

Note:

The information in this chapter assumes that you have read and performed the required pre-upgrade tasks listed in Planning an Upgrade to Oracle Fusion Middleware 12c (12.2.1.4.0) in Planning an Upgrade of Oracle Fusion Middleware.

This chapter contains the following sections:

About the Standalone Oracle HTTP Server Upgrade Process from a Previous 12c Release

Review the flowchart and roadmap for an overview of the upgrade process for Oracle HTTP Server.

Figure 5-1 shows the high-level procedures associated with a standalone Oracle HTTP Server upgrade when the starting point is another 12c release. The tools used for each step are also listed.

Figure 5-1 Upgrade Process Flowchart for Standalone Oracle HTTP Server from a Previous 12c release

Description of Figure 5-1 follows
Description of "Figure 5-1 Upgrade Process Flowchart for Standalone Oracle HTTP Server from a Previous 12c release"

The following table describes the tasks that must be completed to upgrade a standalone Oracle HTTP Server from a previous release of 12c to the latest version.

Table 5-1 Tasks for Upgrading Standalone Oracle HTTP Server from a Previous 12c Release

Task Description

Required

Verify that you are upgrading a standalone Oracle HTTP Server.

To determine which Oracle HTTP Server you have in your existing environment, see Determining whether Oracle HTTP Server is Standalone or Managed (Collocated).

Required

Complete the pre-upgrade tasks.

The pre-upgrade tasks include cloning your production environment, verifying system requirements and certifications, purging unused data, and creating a non-SYSDBA user.

For a complete list of pre-upgrade tasks, see Preparing to Upgrade Oracle HTTP Server.

Required

Install the Standalone Oracle HTTP Server.

Run the installation program to install the software. Select the installation type Standalone Oracle HTTP Server (managed independently of WebLogic server). This transfers the software to your system and creates a new Oracle home directory.

See Installing the Standalone Oracle HTTP Server.

Required

Shut down the 12c environment.

See Stopping Servers and Processes.

Required

Reconfigure your existing domain.

Run the Reconfiguration Wizard from 12c Oracle HTTP Server installation to reconfigure the existing domain.

See About Reconfiguring the Domain.

Required

Upgrade the standalone system component configurations.

See Upgrading Standalone System Component Configurations.

Required

Restart the servers and processes.

See Starting Servers and Processes.

Required

Verify the upgrade.

Your Oracle HTTP Server should continue to function as expected. If you have post-upgrade issues, you need to troubleshoot the installation and retry the upgrade.

See “Troubleshooting Oracle HTTP Server” in Administering Oracle HTTP Server.

Installing the Standalone Oracle HTTP Server

Before you begin your upgrade, download the Oracle HTTP Server 12c (12.2.1.4.0) distribution on the target system and install it by using the Oracle Universal Installer.

To install the standalone Oracle HTTP Server:
  1. Sign in to the target system.
  2. Download the following from Oracle Technology Network or Oracle Software Delivery Cloud to your target system:
    Oracle HTTP Server (UNIX: fmw_12.2.1.4.0_ohs_linux64.bin), (Windows: setup_fmw_12.2.1.4.0_ohs_win64.exe
  3. Change to the directory where you downloaded the 12c (12.2.1.4.0) product distribution.
  4. Check that your machine meet the following requirements:
    • Ensure that the system, patch, kernel, and other requirements are met as specified in theRoadmap for Verifying Your System Environment.
    • Because Oracle HTTP Server is installed by default on port 7777, you must ensure that port 7777 is not used by any service on the nodes. To check if this port is in use, run the following command before you install Oracle HTTP Server. You must free the port if it is in use.

      netstat -an | grep 7777

  5. Enter the following command to start the installation program:
    (UNIX) ./fmw_12.2.1.4.0_ohs_linux64.bin
    (Windows) setup_fmw_12.2.1.4.0_ohs_win64.exe
  6. On UNIX operating systems, the Installation Inventory Setup screen appears if this is the first time you are installing an Oracle product on this host.
    Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location, and click Next.

    Note:

    The Installation Inventory Setup screen does not appear on Windows operating systems.
  7. On the Welcome screen, review the information to make sure that you have met all the prerequisites. Click Next.
  8. On the Auto Updates screen, select an option:
    • Skip Auto Updates: If you do not want your system to check for software updates at this time.

    • Select patches from directory: To navigate to a local directory if you downloaded patch files.

    • Search My Oracle Support for Updates: To automatically download software updates if you have a My Oracle Support account. You must enter Oracle Support credentials then click Search. To configure a proxy server for the installer to access My Oracle Support, click Proxy Settings. Click Test Connection to test the connection.

    Click Next.
  9. On the Installation Location screen, specify the location for the Oracle home directory and click Next.
    As you are installing the standard installation topology for Oracle HTTP Server in a standalone domain, you can specify an Oracle home directory of your choice. However, ensure that you install the software in a new Oracle home.
    See Selecting Directories for Installation and Configurationin Planning an Installation of Oracle Fusion Middleware.
  10. On the Installation Type screen, select Standalone HTTP Server (Managed independently of WebLogic server) and click Next.
  11. The Prerequisite Checks screen analyzes the host computer to ensure that the specific operating system prerequisites have been met.
    To view the list of tasks that are verified, select View Successful Tasks. To view log details, select View Log. If any prerequisite check fails, then an error message appears at the bottom of the screen. Fix the error and click Rerun to try again. To ignore the error or the warning message and continue with the installation, click Skip (not recommended).
  12. On the Security Updates screen, indicate how you would like to receive security updates if you already have an Oracle Support account.
    If you do not have an Oracle Support account and you are sure that you want to skip this step, clear the check box and verify your selection in the follow-up dialog box.
  13. On the Installation Summary screen, verify the installation options that you selected.
    If you want to save these options to a response file, click Save Response File and enter the response file location and name. The response file collects and stores all the information that you have entered, and enables you to perform a silent installation (from the command line) at a later time.

    Click Install to begin the installation.

  14. On the Installation Progress screen, when the progress bar displays 100%, click Finish to dismiss the installer, or click Next to see a summary.
  15. The Installation Complete screen displays the Installation Location and the Feature Sets that are installed. Review this information and click Finish to close the installer.
You have installed the Oracle HTTP Server in a standalone mode.

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 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 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 Administration Console. See Starting and Stopping Administration and Managed Servers and Node Manager.

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

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 the 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 Oracle Identity Management Components

Stop any Oracle Identity Management components, such as Oracle Internet Directory:
  • (UNIX) EXISTING_DOMAIN_HOME/bin/stopComponent.sh component_name

  • (Windows) EXISTING_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) 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 5: 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 WebLogic Server.

About Reconfiguring the Domain

Run the Reconfiguration Wizard to reconfigure your domain component configurations to 12c (12.2.1.4.0).

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

  • WebLogic Server core infrastructure

  • Domain version

Note:

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

  • The Reconfiguration Wizard does not update any of your own applications that are included in the domain.

  • Transforming a non-dynamic cluster domain to a dynamic cluster domain during the upgrade process is not supported.

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

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

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

    <!--extention-template-ref name="Oracle Identity Navigator" 
      version="11.1.1.3.0" 
      location="/u01/app/oracle/product/fmw/iam111130/common/templates/applications/oracle.oinav_11.1.1.3.0_template.jar" 
      symbol=""/-->
    
    <!--install-comp-ref name="oracle.idm.oinav" version="11.1.1.3.0" 
      symbol="oracle.idm.oinav_11.1.1.3.0_iam111130_ORACLE_HOME" 
      product_home="/u01/app/oracle/product/fmw/iam111130"/-->

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

    <!--app-deployment> 
      <name>oinav#11.1.1.3.0</name>
      <target>AdminServer</target>
      <module-type>ear</module-type>
    
      <source-path>/u01/app/oracle/product/fmw/iam111130/oinav/modules/oinav.ear_11.1.1.3.0/oinav.ear</source-path>
      <deployment-order>500</deployment-order>
      <security-dd-model>DDOnly</security-dd-model>
      <staging-mode>nostage</staging-mode>
    </app-deployment-->
    
Specifically, when you reconfigure a domain, the following occurs:
  • The domain version number in the config.xml file for the domain is updated to the Administration Server's installed WebLogic Server version.

  • Reconfiguration templates for all installed Oracle products are automatically selected and applied to the domain. These templates define any reconfiguration tasks that are required to make the WebLogic domain compatible with the current WebLogic Server version.

  • Start scripts are updated.

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

Note:

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

Follow these instructions to reconfigure the existing domain using the Reconfiguration Wizard. See Reconfiguring WebLogic Domains in Upgrading Oracle WebLogic Server.

Backing Up the Domain

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

To create a backup of the domain directory:

  1. Copy the source domain to a separate location to preserve the contents.
    (Windows) copy C:\domains\mydomain to C:\domains\mydomain_backup.
    (UNIX) cp mydomain /domains/mydomain_backup
  2. Before updating the domain on each remote Managed Server, create a backup copy of the domain directory on each remote machine.
  3. Verify that the backed up versions of the domain are complete.
If domain reconfiguration fails for any reason, you must copy all files and directories from the backup directory into the original domain directory to ensure that the domain is returned entirely to its original state before reconfiguration.

Starting the Reconfiguration Wizard

Note:

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

To start the Reconfiguration Wizard in graphical mode:

  1. Sign in to the system on which the domain resides.
  2. Open the command shell (on UNIX operating systems) or open a command prompt window (on Windows operating systems).
  3. Edition Based Database Users Only: If your schemas are configured with EBR database, a default edition name must be manually supplied before you run the Reconfiguration Wizard.
    Run the following SQL command to set the default edition:

    ALTER DATABASE DEFAULT EDITION = edition_name;

    where edition_name is the child edition name.

  4. Go to the oracle_common/common/bin directory:
    • (UNIX) NEW_ORACLE_HOME/oracle_common/common/bin
    • (Windows) NEW_ORACLE_HOME\oracle_common\commom\bin
  5. Start the Reconfiguration Wizard with the following logging options:
    • (UNIX) ./reconfig.sh -log=log_file -log_priority=ALL
    • (Windows) reconfig.cmd -log=log_file -log_priority=ALL

    where log_file is the absolute path of the log file you'd like to create for the domain reconfiguration session. This can be helpful if you need to troubleshoot the reconfiguration process.

    The parameter -log_priority=ALL ensures that logs are logged in fine mode.

    Note:

    When you run this command, the following error message might appear to indicate that the default cache directory is not valid:

    *sys-package-mgr*: can't create package cache dir
    

    You can change the cache directory by setting the environment variable CONFIG_JVM_ARGS. For example:

    CONFIG_JVM_ARGS=-Dpython.cachedir=valid_directory

Reconfiguring the Existing Domain with the Reconfiguration Wizard

Navigate through the screens in the Reconfiguration Wizard to reconfigure your existing domain.

To reconfigure the domain with the Reconfiguration Wizard:
  1. On the Select Domain screen, specify the location of the domain you want to upgrade or click Browse to navigate and select the domain directory. Click Next.
  2. On the Reconfiguration Setup Progress screen, view the progress of the setup process. When complete, click Next.
    During this process:
    • The reconfiguration templates for your installed products, including Fusion Middleware products, are automatically applied. This updates various domain configuration files such as config.xmlconfig-groups.xml, and security.xml (among others).

    • Schemas, scripts, and other such files that support your Fusion Middleware products are updated.

    • The domain upgrade is validated.

  3. On the Domain Mode and JDK screen, select the JDK to use in the domain or click Browse to navigate to the JDK you want to use. The supported JDK version for 12c (12.2.1.4.0) is 1.8.0_211 and later. Click Next.

    Note:

    You cannot change the Domain Mode at this stage.
    For a list of JDKs that are supported for a specific platform, see Oracle Fusion Middleware Supported System Configurations.
  4. On the JDBC Data Sources screen, configure the JDBC data sources defined in your domain source.
    The JDBC data sources associated with the products for which you are creating the domain are listed in the lower half of the screen. A JDBC data source contains a pool of database connections that are created when the data source instance is created, deployed or targeted, or at server startup. Applications look up a data source on the JNDI tree, and then request a connection. When the applications no longer need the connections, they return the connections to the connection pool in the data source.
    From the Data Source Name drop-down list, select the data source(s) for which you want to specify the settings. The values that you specify are displayed in the appropriate columns in the data source list, for the selected data source.
    For Oracle RAC Configuration for data sources, you can select one of the three options:
    • Convert to GridLink
    • Convert to RAC multi data source
    • Don’t convert

    For more information about each option, click Help.

    After specifying the details, click Next.
    If you do not select any data sources on the JDBC Data Sources screen, the following warning displays:
    Missing Driver
    Click Ok to proceed without verification, click Cancel to return to the JDBC Data Sources page.
    In this case, if you click Ok, the data sources are not verified.
  5. On the JDBC Data Sources Test screen, select the check box for the data source connection you configured on the JDBC Data Sources screen and click Test Selected Connections to test the data source connection.

    Note:

    To test the database connections, the database to which you are connecting must be running. If you do not want to test the connections at this time, do not select any data sources. Click Next to continue.
  6. On the Database Configuration Type screen, select RCU Data to connect to the Server Table (_STB) schema.
    Enter the database connection details using the RCU service table (_STB) schema credentials and click Get RCU Configuration.
    The Reconfiguration Wizard uses this connection to automatically configure the data sources required for components in your domain.

    Note:

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

    Note:

    For any existing 12c (12.2.1.3.0) datasource, the reconfiguration will preserve the existing values. For new datasources where the schema was created for 12c (12.2.1.4.0) by the RCU, the default connection data will be retrieved from the _STB schema. If no connection data for a given schema is found in the _STB schema, then the default connection data is used.
    If the check is successful, click Next. If the check fails, reenter the connection details correctly and try again.

    Note:

    If you are upgrading from 12c (12.2.1.3.0), and your database has _OPSS or _IAU 12c (12.2.1.3.0) database schemas, you must manually enter database connection details for those schemas. These schemas were not required in 12c and had to be created manually. Users could assign any name to these schemas, therefore the Reconfiguration Wizard does not recognize them. When providing connection information for _IAU, use the IAU_APPEND user information.
  7. On the JDBC Component Schema Test screen, select all the component schemas and click Test Selected Connections to test the connection for each schema. The result of the test is indicated in the Status column.
    When the check is complete, click Next.
  8. The Node Manager screen is only displayed if the domain you are reconfiguring is currently using a per host Node Manager.
    On the Node Manager screen, select the Node Manager configuration to use for the reconfigured domain. The resulting configuration depends on the combination of options you select for Node Manager Type  and Node Manager Configuration.

    Table 5-2 Field Descriptions for Node Manager Screen

    Option Description
    Per Domain Default Location

    If you select this option, the Node Manager home is redefined to DOMAIN_NAME/nodemanager and you cannot edit the Node Manager home.

    Per Domain Custom Location

    Select this option if you want the per domain Node Manager configuration files to be created in a specific location for this domain. Specify the directory in the Node Manager Home field, or click Browse to use the navigation tree to select the location. The specified directory must be empty. The nodemanager.properties and nodemanager.domains files are created in this directory.

    Node Manager Home

    If you selected the Per Domain Custom Location option, click Browse to navigate to the directory location that you want to use to store the per domain Node Manager configuration.

    Manual Node Manager Setup

    If you select this option, creation of the Node Manager configuration for the domain is skipped and the remaining fields cannot be modified. If you want to use Node Manager in the domain, you must manually configure Node Manager as described in Completing the Node Manager Configuration. The reconfigured domain will still use a per host Node Manager configuration.

    You should also select this option if your existing domain is not configured to use Node Manager and you do not want to use Node Manager in the reconfigured domain.

    For more information about Node Manager configuration, see Administering Node Manager for Oracle WebLogic Server.

    Node Manager Configuration Select one of the following two options. These fields are not available if you selected Manual Node Manager Setup.
    Create New Configuration A per domain Node Manager configuration is automatically created for the reconfigured domain using default settings in nodemanager.properties. If necessary, you can modify nodemanager.properties after the domain has been successfully reconfigured.
    Migrate Existing Configuration The existing per host Node Manager configuration is migrated to a per domain configuration for the reconfigured domain. This does not include environment-specific settings for ListenAddress, ListenPort, StartScriptName, JavaHome, and LogFile.
    Node Manager Home If you selected the Migrate Existing Configuration option, enter or browse to the Node Manager home directory that you want to migrate to the reconfigured domain.
    Apply Oracle Recommended Defaults

    If you selected the Migrate Existing Configuration option, select this check box if you want to use Oracle-recommended defaults in the nodemanager.properties file. Deselect this check box if you want to continue using the settings in the nodemanager.properties file being migrated.

    Oracle-recommended properties with default values are as follows:

    LogLimit=0
    AuthenticationEnabled=true
    LogLevel=INFO
    DomainsFileEnabled=true
    NativeVersionEnabled=true
    LogToStderr=true
    SecureListener=true
    LogCount=1
    StopScriptEnabled=false
    QuitEnabled=false
    LogAppend=true
    StateCheckInterval=500
    CrashRecoveryEnabled=false
    StartScriptEnabled=true
    LogFormatter=weblogic.nodemanager.server.LogFormatter
    ListenBacklog=50
    Node Manager Credentials: Username and Password Specify the username and password that you want to use to start Node Manager in the reconfigured domain.
  9. On the Advanced Configuration screen, you can select all categories for which you want to perform advanced configuration. For each category you select, the appropriate configuration screen is displayed to allow you to perform advanced configuration.

    Note:

    The categories that are listed on the Advanced Configuration screen depend on the resources defined in the templates you selected for the domain.
    For this upgrade, select none of the options and click Next.
  10. On the Configuration Summary screen, review the detailed configuration settings of the domain before continuing.
    You can limit the items that are displayed in the right-most panel by selecting a filter option from the View drop-down list.
    To change the configuration, click Back to return to the appropriate screen. To reconfigure the domain, click Reconfig.

    Note:

    The location of the domain does not change when you reconfigure it.
  11. The Reconfiguration Progress screen displays the progress of the reconfiguration process.
    During this process:
    • Domain information is extracted, saved, and updated.

    • Schemas, scripts, and other such files that support your Fusion Middleware products are updated.

    When the progress bar shows 100%, click Next.
  12. The End of Configuration screen indicates whether the reconfiguration process completed successfully or failed. It also displays the location of the domain that was reconfigured as well as the Administration Server URL (including the listen port). If the reconfiguration is successful, it displays Oracle WebLogic Server Reconfiguration Succeeded.
    If the reconfiguration process did not complete successfully, an error message is displayed indicates the reason. Take appropriate action to resolve the issue. If you cannot resolve the issue, contact My Oracle Support.
    Note the Domain Location and the Admin Server URL for further operations.

Upgrading Standalone System Component Configurations

Use the Upgrade Assistant to upgrade the standalone agent’s component configurations when the agent is managed by OPMN. The standalone component configuration upgrade does not support upgrade of a standalone agent that is not managed by OPMN.

Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.4.0). 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:

Note:

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

  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

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

Table 5-3 Upgrade Assistant Command-Line Parameters

Parameter Required or Optional Description

-readiness

Required for readiness checks

Note: Readiness checks cannot be performed on standalone installations (those not managed by the WebLogic Server).

Performs the upgrade readiness check without performing an actual upgrade.

Schemas and configurations are checked.

Do not use this parameter if you have specified the -examine parameter.

-threads

Optional

Identifies the number of threads available for concurrent schema upgrades or readiness checks of the schemas.

The value must be a positive integer in the range 1 to 8. The default is 4.

-response

Required for silent upgrades or silent readiness checks

Runs the Upgrade Assistant using inputs saved to a response file generated from the data that is entered when the Upgrade Assistant is run in GUI mode. Using this parameter runs the Upgrade Assistant in silent mode (without displaying Upgrade Assistant screens).

-examine

Optional

Performs the examine phase but does not perform an actual upgrade.

Do not specify this parameter if you have specified the -readiness parameter.

-logLevel attribute

Optional

Sets the logging level, specifying one of the following attributes:

  • TRACE

  • NOTIFICATION

  • WARNING

  • ERROR

  • INCIDENT_ERROR

The default logging level is NOTIFICATION.

Consider setting the -logLevel TRACE attribute to so that more information is logged. This is useful when troubleshooting a failed upgrade. The Upgrade Assistant's log files can become very large if -logLevel TRACE is used.

-logDir location

Optional

Sets the default location of upgrade log files and temporary files. You must specify an existing, writable directory where the Upgrade Assistant creates log files and temporary files.

The default locations are:

(UNIX)

NEW_ORACLE_HOME/oracle_common/upgrade/logs
NEW_ORACLE_HOME/oracle_common/upgrade/temp

(Windows)

NEW_ORACLE_HOME\oracle_common\upgrade\logs
NEW_ORACLE_HOME\oracle_common\upgrade\temp

-help

Optional

Displays all of the command-line options.

Upgrading Standalone System Component Configurations Using the Upgrade Assistant

Navigate through the screens in the Upgrade Assistant to upgrade standalone system component configurations.

To upgrade the existing 12c domain using the Upgrade Assistant:
  1. On the Welcome screen, review an introduction to the Upgrade Assistant and information about important pre-upgrade tasks. Click Next.

    Note:

    For more information about any Upgrade Assistant screen, click Help on the screen.
  2. On the Standalone Components screen, select Standalone System Component Configurations.
    Select Update an Existing Domain and enter the location of the existing 12c domain in the Domain Directory field. You can also click Browse to select the existing domain directory by using the navigation tree. Click Next.

    Note:

    • The Create a New Domain option should only be used if you are upgrading from version 11g.

    • If you have already created a new 12c standalone domain for your upgraded 11g system components, you can extend the standalone domain with the standalone Oracle HTTP Server by using the Update an Existing Domain option.

    • The Update an Existing Domain option should only be used if you are upgrading from a previous 12c release (12.1.2.0.0, 12.1.3.0.0, 12.2.1.0.0, 12.2.1.1.0, 12.2.1.2.0, and 12.2.1.3.0) to the latest 12c release (12.2.1.4.0).

  3. On the Component List screen, verify that the list includes all the components for which you want to upgrade configurations and click Next.
    If you do not see the components you want to upgrade, click Back to go to the previous screen and specify a different domain.
  4. On the Prerequisites screen, acknowledge that the prerequisites have been met by selecting all the check boxes. Click Next.

    Note:

    The Upgrade Assistant does not verify whether the prerequisites have been met.
  5. On the Instance Directories screen, select 12c Source and click Next.
    You do not need to enter the Oracle instance directories when upgrading to the latest 12c release from a previous 12c release.
  6. On the Examine screen, review the status of the Upgrade Assistant as it examines each standalone component, verifying that the standalone component configuration is ready for upgrade. If the status is Examine finished, click Next.
    If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No in the Examination Failure dialog. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade in Upgrading with the Upgrade Assistantfor information on resolving common upgrade errors.

    Note:

    • If you resolve any issues detected during the examine phase without proceeding with the upgrade, you can start the Upgrade Assistant again without restoring from backup. However, if you proceed by clicking Yes in the Examination Failure dialog box, you need to restore your pre-upgrade environment from backup before starting the Upgrade Assistant again.

    • Canceling the examination process has no effect on the configuration data; the only consequence is that the information the Upgrade Assistant has collected must be collected again in a future upgrade session.

  7. On the Upgrade Summary screen, review the summary of the options you have selected for component configuration upgrade.
    The response file collects and stores all the information that you have entered, and enables you to perform a silent upgrade at a later time. The silent upgrade performs exactly the same function that the Upgrade Assistant performs, but you do not have to manually enter the data again. If you want to save these options to a response file, click Save Response File and provide the location and name of the response file.

    Click Upgrade to start the upgrade process.

  8. On the Upgrade Progress screen, monitor the status of the upgrade.

    Caution:

    Allow the Upgrade Assistant enough time to perform the upgrade. Do not cancel the upgrade operation unless absolutely necessary. Doing so may result in an unstable environment.
    If any components are not upgraded successfully, refer to the Upgrade Assistant log files for more information.

    Note:

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

    Click Next.

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

    If the upgrade fails: On the Upgrade Failure screen, click View Log to view and troubleshoot the errors. The logs are available at ORACLE_HOME/oracle_common/upgrade/logs. Note If the upgrade fails you must restore your pre-upgrade environment from backup, fix the issues, then restart the Upgrade Assistant.

Verifying the Domain-Specific-Component Configurations Upgrade

To verify that the domain-specific-component configurations upgrade was successful, sign in to the Administration console and the Oracle Enterprise Manager Fusion Middleware Control and verify that the version numbers for each component is 12.2.1.4.0.

To sign in to the Administration Console, go to: http://administration_server_host:administration_server_port/console

To sign in to Oracle Enterprise Manager Fusion Middleware Control Console, go to: http://administration_server_host:administration_server_port/em

Note:

After upgrade, make sure you run the administration tools from the new 12c (12.2.1.4.0) Oracle home directory and not from the previous Oracle home directory.

During the upgrade process, some OWSM documents, including policy sets and predefined documents such as policies and assertion templates, may need to be upgraded. If a policy set or a predefined document is upgraded, its version number is incremented by 1.

If you created the FMW user to run the Upgrade Assistant, ensure that you delete the account after verifying your upgrade was successful.

Verifying the Upgrade

You can verify that the upgrade is successful if you are able to start the Node Manager and the Standalone Oracle HTTP Server properly.

If you experience post-upgrade issues, you need to troubleshoot the installation and retry the upgrade. See Troubleshooting Oracle HTTP Serverin Administrator's Guide for Oracle HTTP Server.

If you are not able to start the newly upgraded environment, a possible cause could be the use of MD5 certificates in your Oracle wallet. To check whether you are using MD5 signatures and how to replace them with SHA-2 certificates, see Replacing Certificate Signed Using MD5 Algorithm with Certificate Signed Using SHA-2 Algorithm .

Starting the Node Manager

Server instances in a WebLogic Server production environment are often distributed across multiple domains, machines, and geographic locations. Node Manager is a WebLogic Server utility that enables you to manage (start, shut down, and restart) your Oracle HTTP Server instance.

On Windows operating systems, Oracle recommends that you configure Node Manager to run as a startup service. This allows Node Manager to start up automatically each time the system is restarted. For more information, see Running Node Manager as a Startup Service in Administering Node Manager for Oracle WebLogic Server.

Note:

On UNIX platforms, do not run Node Manager as the root user.

    Starting the Standalone Oracle HTTP Server

    After the upgrade, start the standalone Oracle HTTP Server.

    To start the standalone Oracle HTTP Server:
    1. Go to the DOMAIN_HOME/bin directory:
      (UNIX) ORACLE_HOME/user_projects/domains/<domain name>/bin
      (WINDOWS) ORACLE_HOME\user_projects\domains\<domain name>\bin
    2. Enter the command to start the standalone server.
      On UNIX operating systems:
      ./startComponent.sh ohs_name
      On Windows operating systems:
      startComponent.cmd ohs_name
      See Starting and Stopping System Components in Administering Oracle Fusion Middleware.

    Starting Servers and Processes

    After a successful upgrade, restart all processes and servers, including the Administration Server and any Managed Servers.

    The components may be dependent on each other so they must be started in the correct order.

    Note:

    The procedures in this section describe how to start servers and process using the WLST command line 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 start your Fusion Middleware environment, follow the steps below:

    Step 1: Start the Administration Server

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

    To start the Administration Server, use the startWebLogic script:

    • (UNIX) NEW_DOMAIN_HOME/bin/startWebLogic.sh

    • (Windows) NEW_DOMAIN_HOME\bin\startWebLogic.cmd

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

    Step 2: Start Node Manager

    To start Node Manager, use the startNodeManager script:

    • (UNIX) NEW_DOMAIN_HOME/bin/startNodeManager.sh

    • (Windows) NEW_DOMAIN_HOME\bin\startNodeManager.cmd

    Step 3: Start Oracle Identity Management Components

    Start any Oracle Identity Management components, such as Oracle Internet Directory, that form part of your environment:
    • (UNIX) NEW_DOMAIN_HOME/bin/startComponent.sh component_name

    • (Windows) NEW_DOMAIN_HOME\bin\startComponent.cmd component_name

    Step 4: Start the Managed Servers

    To start a WebLogic Server Managed Server, use the startManagedWebLogic script:

    • (UNIX) NEW_DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url

    • (Windows) NEW_DOMAIN_HOME\bin\startManagedWebLogic.cmd managed_server_name admin_url

    When prompted, enter your user name and password.

    Note:

    The startup of a Managed Server will typically start the applications that are deployed to it. Therefore, it should not be necessary to manually start applications after the Managed Server startup.

    Step 5: Start System Components

    To start system components, such as Oracle HTTP Server, use the startComponent script:

    • (UNIX) NEW_DOMAIN_HOME/bin/startComponent.sh component_name

    • (Windows) NEW_DOMAIN_HOME\bin\startComponent.cmd component_name

    You can start system components in any order.