Perform these tasks to complete an out-of-place upgrade:
It is important to understand whether to perform in-place or out-of-place domain directory upgrade.
When upgrading from Oracle Fusion Middleware 11g or a previous 12c release to 12c (12.2.1.2), 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 existing 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 to , it is important to note that the existing 11g or 12c (12.1.3.0.0, 12.2.1.0.0, 12.2.1.1.0, and 12.2.1.2.0) schemas will be upgraded in-place. Your pre-upgrade environment must be shut down during the out-of-place domain directory upgrade process.
Understanding the procedure of performing an out-of-place domain directory upgrade on the same host.
Perform the following tasks to complete the out-of-place domain directory upgrade on the same host at the existing 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.
Note:
The Fusion Middleware 12c certification matrix includes only 12.1 databases. Hence, the reference to 11 in these procedures 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.
Do not stop the database before starting the upgrade.
Before running the Upgrade Assistant to upgrade your schemas and configurations, you must shut down all 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 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 in Administering Oracle Fusion Middleware.To stop your Fusion Middleware environment, follow the steps below.
Step 1: Stop System Components
To stop system components, such as Oracle HTTP Server, use the stopComponent script:
(UNIX) DOMAIN_HOME/bin/stopComponent.sh component_name
(Windows) 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) DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url
(Windows) 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, that form part of your environment:(UNIX) DOMAIN_HOME/bin/stopComponent.sh component_name
(Windows) 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) DOMAIN_HOME/bin/stopWebLogic.sh
(Windows) 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 having set the nodemanager.properties attribute QuitEnabled to true (the default is false), you can use WLST to connect to Node Manager and shut it down. For more information, see stopNodeManager in WLST Command Reference for WebLogic Server.
Make sure that you have created a complete backup of your entire pre-upgrade 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 or previous 12c 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 existing domain. to a new location using the same directory structure that was used for the existing environment. The directory structure you create for the upgrade must be identical to the structure used for the original 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 the12c (12.2.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.
Perform the upgrade on the domain you created in Task 3: Restore the 11g domain backup files to a new location..
Each component has an upgrade guide that describes the procedures required to upgrade from your Oracle Fusion Middleware 11g or previous 12c infrastructure topology to the new 12c (12.2.1.2) topology. The guides are located in the Upgrade tab of the Oracle Fusion Middleware 12c (12.2.1) online library.
FMW to run the Upgrade Assistant. This user has the privileges required to modify schemas, but does not have full administrator privileges.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.
Notes
If you created the non-SYSDBA user FMW in a previous release, you must drop and recreate this user before starting the upgrade. Running the Upgrade Assistant with an older FMW user may lead to a failed upgrade as new privileges may have been added. Oracle recommends that you drop and recreate the user instead of modifying the existing FMW user.v$xatrans$ table does not exist. You must run the XAVIEW.SQL script to create this table before creating the user. Moreover, the grant select privilege on v$xatrans$ table is required only for Oracle Identity Manager. If you do not require Oracle Identity Manager for configuration, or if you do not have the v$xatrans$ table, then remove the following line from the script:
grant select on v$xatrans$ to FMW with grant option;
welcome1 is the password. Make sure that you specify your actual password when granting privileges.
create user FMW identified by welcome1; grant dba to FMW; 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_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 sys.dbms_aq 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_REPUTIL to FMW with grant option; grant execute on dbms_job to FMW with grant option; grant select on pending_trans$ 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 select on v$xatrans$ to FMW with grant option; grant execute on sys.dbms_system 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 ALL_ENCRYPTED_COLUMNS to FMW with grant option; grant select on dba_queue_subscribers to FMW with grant option; grant execute on SYS.DBMS_ASSERT to FMW with grant option; grant select on dba_subscr_registrations to FMW with grant option; grant manage scheduler to FMW;
Note:
Oracle Database 11.2.0.3 Database Users ONLY: You must apply Oracle Patch 13036331 before you begin the upgrade. Go to My Oracle Support to download the patch.
If you do not apply this patch, then you will have to grant additional privileges for some schemas.
For most components, the Upgrade Assistant can be run in -readiness mode to perform a read-only, pre-upgrade check on your domain. If issues are detected, you can correct them before starting the actual upgrade.
-readiness mode:The screens you see will vary depending on the upgrade options you select. Consult your component-specific upgrade documentation for complete details.
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).
Understanding the procedure to perform an out-of-place upgrade on a different host.
Perform these steps to compete an out-of-place upgrade on a different host.
The Fusion Middleware 12c certification matrix includes 12.1 databases, therefore, 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 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).
Procedure to deinstall the 11g applications and domain setup.
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.