The following topics are described in this chapter:
When upgrading Oracle Fusion Middleware to 12c (12.2.1), schemas and domain directory upgrades are performed “in-place" which updates the existing 11g or 12c files during the upgrade.
If you prefer to leave your 11g domain directory intact, you can perform an out-of-place domain directory upgrade using a new domain directory on the same - or 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 shut down during the out-of-place domain directory upgrade process.
Perform the following tasks to complete the out-of-place domain directory upgrade on the same host at the existing 11g domain:
Note:
If you are upgrading domain that is on a different host, see Performing an Out-of-Place Domain Directory Upgrade on a Different Host.
Task 1: Stop all processes, including the Administration Server, Managed Servers, and Node Manager.
Task 3: Restore the 11g domain backup files to a new location.
Task 4: Install the 12.2.1 distributions in a new Oracle Home.
Task 5: Upgrade the cloned environment using the standard upgrade procedures.
Task 6: Validate that the newly upgraded domain functions as expected.
Note:
The Fusion Middleware 12c certification matrix includes 12.1 databases. Hence, the reference to 11 in this chapter is to the Fusion Middleware 11g schemas and not to the Oracle 11g database version.
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 the Oracle® Fusion Middleware Administrator's Guide.
During the upgrade you must have “read" access to the files in the backup storage:
11g Domain Home
The /nodemanager directory located in the MW_HOME/wlserver_10.3/common/
For more information, see "Backing Up Your Environment" in the Oracle® Fusion Middleware Administrator's Guide. Do not proceed with the upgrade until you have a complete backup.
Copy the files you backed up in Task 2: Backup all files from the 11g domain. to a new location using the same directory structure that was used for the existing 11g environment. The directory structure you create for the upgrade must be identical to the structure used for the original 11g environment.
You will point to this location in Task 5: Upgrade the cloned environment using the standard upgrade procedures. .
You must obtain, install and configure the 12c (12.2.1) 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.
Perform the upgrade on the domain you created in Task 3: Restore the 11g domain backup files to a new location. .
Each 12c (12.2.1) component has an upgrade guide that describes the procedures required to move from your 11g (11.1.1.6 or 11.1.1.7) or 12c (12.1.2) infrastructure topology to the new 12c (12.2.1) topology. The guides are located in the Upgrade tab of the Oracle Fusion Middleware 12c (12.2.1) online library.
Perform the usual administration tasks using the new domain and verify that the components work as expected.
You do not need to decommission the 11g Oracle home, however if you would like to remove it, see Deinstalling the 11g Applications (Optional).
Task 3: Set up the target machine (Host B) 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.2.1 distributions in a new Oracle Home. (Host B)
Task 6: Upgrade the environment using the standard upgrade procedures. (Host B)
Task 7: Validate that the newly upgraded domain functions as expected.
The Fusion Middleware 12c certification matrix includes 12.1 databases. Hence, the reference to 11 in this chapter is to the Fusion Middleware 11g schemas and not to the Oracle 11g database version.
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 the Oracle® Fusion Middleware Administrator's Guide.
During the upgrade you must have “read" access to the files in the backup storage:
11g Domain Home
The /nodemanager directory located in the MW_HOME/wlserver_10.3/common/
The host name and IP address of the target machine (Host B) must be made identical to the source host (Host A). 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 2: Backup all files from the host machine. (Host A) 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 Oracle® Fusion Middleware Administrator's Guide.
You must obtain, install and configure the 12c (12.2.1) 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.2.1) component has an upgrade guide that describes the procedures required to move from your 11g (11.1.1.6 or 11.1.1.7) or 12c (12.1.2 or 12.1.3) infrastructure topology to the new 12c (12.2.1) topology. The guides are located in the Upgrade tab of the Oracle Fusion Middleware 12c (12.2.1) online library.
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: Set up the target machine (Host B) with the 11g host name and IP address..
Perform the usual administration tasks using the new domain and verify that the components work as expected.
You do not need to decommission the 11g Oracle home, however if you would like to remove it, see Deinstalling the 11g Applications (Optional).
While not required, you can use these steps to deinstall the 11g application and domain setup after the upgrade. Do not deinstall a domain that is still being referenced by a non-upgraded component. If you are unsure, leave the domain intact.
Note:
The commands mentioned in this section must be run from the 11g Oracle Home that you are removing and not from the new home that was created as part of the 12c upgrade process.