This chapter describes the process of upgrading your Fusion Middleware 11g domain directory to Release 12c (12.1.2) on a separate host.
The following topics are described in this chapter:
Section A.1, "About Upgrading a Domain Directory Out-of-Place"
Section A.2, "Performing an Out-of-Place Domain Directory Upgrade"
When upgrading Oracle Fusion Middleware to 12c (12.1.2), schemas and domain directory upgrade are performed "in-place" which updates the exisiting 11g files during the upgrade.
If you prefer to leave your 11g domain directory intact, you can perform an out-of-place domain directory upgrade on a different host using the steps described in this chapter.
Caution:
When performing an out-of-place domain directory upgrade, it is important to note that the 11g schemas will be upgraded in-place. Your 11g environment must be taken down during the out-of-place domain directory upgrade process.
Perform the following tasks to complete the out-of-place domain directory upgrade:
Note:
The tasks below refer to Host A as the existing 11g domain host and Host B as the new 12.1.2 domain host. The affected host is identified in each tasks.
Task 3, "Set up the target machine with the 11g host name and IP address."
Task 4, "Restore the 11g domain backup from Host A to Host B."
Task 5, "Install the 12.1.2 distributions in a new Oracle Home. (Host B)"
Task 6, "Upgrade the environment using the standard upgrade procedures. (Host B)"
You must stop all processes, including the Administration Server, Managed Servers, and Node Manager, if they are started on the host. For example, to stop the Administration Server:
DOMAIN_HOME/bin/stopWebLogic.sh username password [admin_url]
Make sure that you have created a complete backup of your entire 11g 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.
For more information on backing up your files, see "Backing Up Your Environment" in Administering Oracle Fusion Middleware.
During the upgrade you must have access to the contents of the following:
11g Domain Home
The /nodemanager directory located in the MW_HOME/wlserver_10.3/common/
Note:
Some of the backup and recovery procedures described in "Backing Up Your Environment" in Administering Oracle Fusion Middleware are product-specific. Do not proceed with the upgrade until you have a complete backup.
The host name and IP address of the target machine must be made identical to the host. This will require 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.
Restore the files you backed up in Task 3 using the same directory structure that was used in 11g. The directory structure on Host B must be identical to the structure used on Host A.
For detailed information about restoring your files to the target machine, see "Recovering Your Environment" in Administering Oracle Fusion Middleware.
You must obtain, install and configure the 12c (12.1.2) product distributions for the components you will be upgrading.
For detailed instructions, see Planning an Installation of Oracle Fusion Middleware and the component-specific installation guides for the component(s) you are installing.
Each 12c (12.1.2) component has an upgrade guide that describes the procedures required to move from your 11g (11.1.1.6.0 or 11.1.1.7.0) topology to the new 12c (12.1.2) topology. The guides are located in the Upgrade tab of the Oracle Fusion Middleware 12c (12.1.2) online library.
Tip:
The Node Manager upgrade procedure requires access to the original Node Manager files. Use the 11g Node Manger files that were backed up from the source machine as part of Task 3.