Upgrading a Clustered Environment

5 Upgrading a Clustered Environment

Describes the process of upgrading to a multi-node environment and performing post-upgrade configuration tasks.

Note:

If the Oracle wallet configured with OHS is not located on the same machine where the Upgrade Assistant is being invoked, then the wallets cannot be taken care of during the upgrade process. You must perform the following steps to ensure that the wallets are available.

Propagating Domain Configuration to Another Host

After verifying that the upgrade was successful, use these steps to propagate the newly upgraded files to another host.

After you have completed your single node upgrade on HOST1, use these steps to propagate the newly upgraded files to another node (in this example the secondary host is called HOST2).

Executing the pack command on the server where the Admin Server and one of the Managed Servers is installed.

In our sample topology, you would execute the following on HOST1:

cd /14c_ORACLE_HOME/oracle_common/common/bin

./pack.sh -domain=/12c_DOMAIN_HOME -template=domainupgradetemplate.jar -template_name=domainupgradetemplate -managed=true

In this example:

14c_ORACLE_HOME refers the actual path to the 14c Oracle home directory (the installation directory for the 14c (14.1.2.0.0)bits).
Replace 12c_DOMAIN_HOME with the actual path to the upgraded domain directory.
domainupgradetemplate.jar is a sample name for the jar file you are creating, which will contain the domain configuration files.
domainupgradetemplate is the name assigned to the domain template file.
By default, the domainupgradetemplate is created in the current directory where you ran the pack command. In this example, it would be created in the following directory, but you can specify a full path for the template jar file as part of the -template argument to the pack command:
```
ORACLE_COMMON_HOME/common/bin/
```

The pack command creates a template archive (.jar) file that contains a snapshot of either an entire domain or a subset of a domain. You can use a template that contains a subset of a domain to create a Managed Server domain directory hierarchy on a remote machine.

Executing the unpack Command from the 12c Oracle Home on HOST2.

Make sure that the Administration and Managed Servers are still stopped and then execute the unpack command to create a full domain (or a subset of a domain) used for a Managed Server domain directory on the remote machine. You may use unpack only with a template compatible with your current installation.

Note:

Do not attempt to unpack the domain on top of an existing domain. Oracle recommends that you unpack the contents of the domain upgrade template jar file into a new domain location.

It is important to note that even if you use the -overwrite_domain=true argument when unpacking the domain, the contents of the existing domain will remain in place and will cause issues with when starting the servers. For this reason, Oracle recommends that you unpack the domain template jar file into a new location, or, manually delete the contents of the existing location before you unpack.

A sample unpack command code snippet is shown below.

cd /12c_ORACLE_HOME/oracle_common/common/bin

./unpack.sh -template=domainupgradetemplate.jar - domain=NEW_DOMAIN_LOCATION

In this example:

12c_ORACLE_HOME refers the actual path to the 12c Oracle home directory, the installation directory for the 14c (14.1.2.0.0).
Replace NEW_DOMAIN_LOCATION with the actual path to the upgraded domain directory.
domainupgradetemplate.jar is a sample name for the jar file you are creating, which will contain the domain configuration files.
domainupgradetemplate is the name assigned to the domain template file.

Copying the template file created on HOST 1 to HOST2.

After you perform a complete upgrade of your deployment on HOST1, and you have completed any post-upgrade configurations that apply to your new environment, you must copy the domain template to HOST2.

Use the following command to copy from HOST1 the domain upgrade template JAR file created during the upgrade.

scp domaintemplate.jar company@HOST2:14c_ORACLE_HOME/oracle_common/common/bin

Completing the following verification steps after the unpack.

Verify that settings for WLS_HOME and ORACLE_HOME located in the setDomainEnv.sh script from the 12c domain are pointing to 14c (14.1.2.0.0).
Start the Node Manager, WebLogic Administration Server, and the Managed Servers on HOST1 and HOST2 in the following order:
1. On HOST1 and HOST2, start the Node Manager.
2. On HOST1, start the WebLogic Administration Server.
3. On HOST1 and HOST2, start the Managed Servers.

For more information, see Starting Servers and Processes. Carefully review the order in which Managed Servers should be started.