4 Upgrading Oracle Traffic Director from a Previous 12c Release

You can upgrade Oracle Traffic Director from a previous 12c release to 12c ( .

Follow the steps in the following topics to perform the upgrade:

4.1 About the Oracle Traffic Director Upgrade Process

Review the roadmap for an overview of the upgrade process for Oracle Traffic Director.

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

Table 4-1 Tasks for Upgrading Oracle Traffic Director

Task Description


If you have not done so already, review the introductory topics in this guide and complete the required pre-upgrade tasks.

See Pre-Upgrade Checklist


Download and install the Oracle Fusion Middleware Infrastructure and Oracle Traffic Director 12c ( distributions into a new Oracle home.

See Installing the Product Distributions


Shut down the 11g environment (stop all Administration and Managed Servers).

WARNING: Failure to shut down your servers during an upgrade may lead to data corruption.

See Stopping Servers and Processes


Start the Upgrade Assistant to upgrade domain component configurations.

The Upgrade Assistant is used to update the domain’s component configurations.

See Upgrading the Component Configurations


Start the Upgrade Assistant to upgrade standalone system component configurations.

The Upgrade Assistant updates the standalone agent’s component configurations.

See Starting the Upgrade Assistant


Complete and verify the upgrade.

Perform the required post-upgrade configuration tasks (if needed), including starting the new Administration and Managed Servers and node manager to ensure there are no issues.

Oracle recommends that you ensure all of the upgraded components are working as expected before deleting your backups.

See Verifying the Component Configurations

4.2 Upgrading to Oracle Traffic Director 12c (

Oracle Fusion Middleware Upgrade Assistant supports an out-of-place upgrade and an in-place upgrade to 12c (

Oracle Fusion Middleware Upgrade Assistant supports an in-place upgrade to 12c ( for the following Oracle Traffic Director releases:

  • Oracle Traffic Director FMW 12c Release 2 (12.2.1)

The following topics describe how to upgrade Oracle Traffic Director to

4.2.1 Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c ( 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 Command-Line Parameters

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

Table 4-2 Upgrade Assistant Command Line Parameters

Parameter Required or Optional Description


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.



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.


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



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


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






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


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

(Windows) ORACLE_HOME\oracle_common\upgrade\logs



Displays all of the command-line options.

4.2.2 Upgrading the Component Configurations

When you run the Upgrade Assistant to upgrade the Oracle Traffic Director component configurations, consider the following points based on the Oracle Traffic Director domain.

Standalone domain upgrade:

  • Specify the location of the target domain for the upgraded Oracle Traffic Director configurations.

Collocated domain upgrade:

  • Specify the location of the domain for the upgraded Oracle Traffic Director configurations.

  • Specify the starting point for an upgrade. The options are 12c source and 11g source.

4.2.3 Verifying the Component Configurations Upgrade

Verifying the Component Configurations Upgrade.

For Oracle Traffic Director 12c Configuration:

  • The version in server.xml is modified to

  • The value of ORACLE_HOME in the scripts and in the obj.conf file are updated as the new ORACLE_HOME for local Oracle Traffic Directory instances.

4.3 Post-Upgrade Tasks

Review the following list of post-upgrade tasks you might have to perform after upgrading to Oracle Traffic Director 12c (

  • Any references in the Oracle Traffic Director configuration files to the paths outside of INSTANCE_HOME and ORACLE_HOME may not be accessible post upgrade. This should be configured manually.

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


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) DOMAIN_HOME/bin/startWebLogic.sh

  • (Windows) 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) DOMAIN_HOME/bin/startNodeManager.sh

  • (Windows) 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) DOMAIN_HOME/bin/startComponent.sh component_name

  • (Windows) 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) DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url

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

When prompted, enter your user name and password.


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) DOMAIN_HOME/bin/startComponent.sh component_name

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

You can start system components in any order.