19 Installing Software Now and Upgrading Later in Silent Mode

This chapter explains how you can install only the software binaries of Enterprise Manager Cloud Control in silent mode at one point, and upgrade them at a later point.

Upgrading using the software-only mode in silent mode is only an alternative to upgrading in graphical mode as described in Chapter 18. Therefore, the two modes work the same way. The only difference is the methodology in which you implement this installation type. While the graphical mode requires you to invoke the installer and use the interview screens to capture the installation details, the silent mode requires you to invoke the installer passing a response file that already has all the installation details captured.

This chapter covers the following:

Upgrading in Software-Only Mode with 1-System Upgrade Approach
Upgrading in Software-Only Mode with 2-System Upgrade Approach

Note:

You can find the OMS and Management Agent entries in the /etc/oragchomelist file for all UNIX platforms except HPUNIX, HPia64, Solaris Sparc. On HPUNIX, HPia64, Solaris Sparc platforms, the entries are present in /var/opt/oracle/oragchomelist.

Upgrading in Software-Only Mode with 1-System Upgrade Approach

This section describes how you can upgrade in software-only mode with 1-System upgrade approach. In particular, this section covers the following:

Installing Software Binaries
After You Install
Configuring and Upgrading

Installing Software Binaries

To install the software binaries of Enterprise Manager Cloud Control, follow these steps:

Copy the following response file to an accessible location on your local host:

<Software_Location>/response/software_only.rsp

In this command, <Software_Location> refers to the location where you have downloaded software kit.
Edit the response file and enter appropriate values for the variables described in Table 19-1.

Invoke the installer:

./runInstaller -silent -responseFile <absolute_path>/software_only.rsp [-invPtrLoc <absolute_path_to_oraInst.loc>]

Note:

To invoke the installation wizard on UNIX platforms, run runInstaller. To invoke on Microsoft Windows platforms, run setup.exe.
For information about the additional, advanced options you can pass while invoking the installer, refer to Using Advanced Installer Options.
The central inventory location you enter must NOT be on a shared file system.

Deinstall the Management Agent. For instructions, refer to the chapter on deinstalling a Management Agent in the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

Note:
The Management Agent installed with the OMS is not required because you already have the Management Agent predeployed by the Enterprise Manager 12c Upgrade Console.

Editing Response File for Installing Software Binaries

Table 19-1 describes what variables you must edit and how you must edit them in the software_only.rsp response file for installing the software binaries of Enterprise Manager Cloud Control.

Table 19-1 Editing Response File for Installing Software Binaries

Parameter	Description
UNIX_GROUP_NAME	Enter the name of the UNIX group you belong to. For example, `"dba"`
INVENTORY_LOCATION	Enter the absolute path to the Central Inventory. For example, `/scratch/oracle/oraInventory`
SECURITY_UPDATES_VIA_MYORACLESUPPORT	Enter `TRUE` if you want to download and install security updates. Then, enter the credentials for the following variables: `MYORACLESUPPORT_USERNAME` `MYORACLESUPPORT_PASSWORD` Enter `FALSE` if you do not want to download and install security updates:
DECLINE_SECURITY_UPDATES	Enter `TRUE` if you want to decline the security updates. In this case, you should have entered `False` for `SECURITY_UPDATES_VIA_MYORACLESUPPORT`. Enter `FALSE` if you do not want to decline the security updates. In this case, you should have entered `TRUE` for `SECURITY_UPDATES_VIA_MYORACLESUPPORT`.
INSTALL_UPDATES_SELECTION	By default, this variable is set to `"skip"` indicating that the software updates will not be installed during installation. If you want to install the software updates from My Oracle Support, then set this variable to `"download"`. Then, enter the credentials for the following parameters: `MYORACLESUPPORT_USERNAME_FOR_SOFTWAREUPDATES` `MYORACLESUPPORT_PASSWORD_FOR_SOFTWAREUPDATES` If you want to install the software updates from a staged location, then set this variable to `"staged"`. Then, for the `STAGE_LOCATION` parameter, enter the absolute path, which leads to the `Updates` directory, where the software updates are available.
ORACLE_MIDDLEWARE_HOME_LOCATION	Enter the location where you want the installer to install Oracle WebLogic Server 11g Release 1 (10.3.5) and Java Development Kit 1.6 v24. For example, `u01/app/Oracle/Middleware`. Ensure that the middleware location has write permission to create the Oracle homes for OMS and Management Agent. If you have already installed them manually, then enter the location where you have installed them. Note: Ensure that the middleware home you enter here is used only for Enterprise Manager Cloud Control. Ensure that no other Oracle Fusion Middleware products or components are installed in the same middleware home.
PLUGIN_SELECTION	By default, mandatory plug-ins such as Oracle Database Management Plug-In, Oracle Fusion Middleware Management Plug-In, Oracle My Oracle Support Management Plug-In, and Oracle Exadata Management Plug-In get automatically installed with the Enterprise Manager system. However, if you want to install any of the other optional plug-ins that are available in the software kit (DVD or downloaded software), then enter the names of those plug-ins for this variable. For example, `PLUGIN_SELECTION={"oracle.sysman.empa","oracle.sysman.vt"}` If you want to install any plug-in that is not available in the software kit, then do the following: Manually download the plug-ins from the following URL, and store them in an accessible location. `http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-upgrade-console-502238.html` Update this variable (PLUGIN_SELECTION) to the names of those plug-ins you downloaded. Invoke the installer with the following option, and pass the location where you downloaded the plug-ins: `./runInstaller -pluginLocation <absolute_path_to_plugin_software_location>`

After You Install

(For UNIX Only) After you install the software binaries, log in as a root user in a new terminal and run the allroot.sh script from the OMS home:

$<OMS_HOME>/allroot.sh

Configuring and Upgrading

To configure the software binaries of Enterprise Manager Cloud Control, follow these steps:

Copy the following response file to an accessible location on the host where you copied the software binaries of Enterprise Manager Cloud Control:

<Software_Location>/response/upgrade.rsp

In this command, <Software_Location> refers to the location where you have downloaded software kit.
Edit the response file and enter appropriate values for the variables described in Table 19-2.

Configure the software binaries by invoking the ConfigureGC.sh script passing the response you edited in the previous step:

$<MIDDLEWARE_HOME>/oms/sysman/install/ConfigureGC.sh -silent -responseFile <absolute_path>/upgrade.rsp [-invPtrLoc <absolute_path_to_oraInst.loc>]

Note:

While installing the software binaries as described in Installing Software Binaries, if you had passed the argument -invPtrLoc, then pass the same argument here as well.
For information about the additional, advanced options you can pass while invoking the script, refer to Using Advanced Script Options.
If you see an error about missing plug-ins, then manually download those plug-ins (opar files) to an accessible location, and invoke the installer once again in the following way to install the software binaries of the downloaded plug-ins. Ensure that the location to which you download the plug-ins is meant only for these missing plug-ins.

<software_kit>/runInstaller -plugininstall -pluginLocation <absolute_path_to_plugin_sw> -mwHome <absolute_path_to_middleware_home> [-invPtrLoc <absolute_path_to_oraInst.loc>]

The missing plug-ins displayed in the error message have the following format. Ensure that you download and install the same plug-in version and the same or higher plug-in update.

PluginID:PluginVersion:PluginUpdate

To download the missing plug-ins (opar files), follow these steps:
1. Navigate to the following location where you installed the software binaries, and check if the opar files you are looking for are available. If they are available, copy them to an accessible location.
  
  $<OMS_HOME>/sysman/install/undeployed_plugins
2. If the opar files are not available in the OMS home, then download them from the following URL:
  
  http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-upgrade-console-502238.html
Proceed to the next step only after you have installed these missing plug-ins.

Editing Response File for Configuring Software Binaries

Table 19-2 describes what variable you must update and how you must update them in the upgrade.rsp response file for configuring the software binaries of Enterprise Manager Cloud Control.

Table 19-2 Editing Response File for Configuring Software Binaries

Parameter	Description
ORACLE_INSTANCE_HOME_LOCATION	By default, `gc_inst` is considered as the OMS Instance Base directory for storing all OMS-related configuration files, and the by default, it is created in the middleware home. If you want to accept the default location and the directory name, then skip this variable. However, if you want to have a custom location and a custom directory name, then enter the absolute path to the custom location leading up to the custom directory name.
OLD_BASE_DIR	Enter the base directory of the OMS you want to upgrade.
ONE_SYSTEM	By default, this variable is set to `FALSE` indicating that it is 2-System upgrade. Change it to `TRUE`.
WLS_ADMIN_SERVER_USERNAME	(Applicable only if you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5)) By default, `weblogic` is the name assigned to the default user account that is created for the Oracle WebLogic Domain. If you want to accept the default name, then blank. However, if you want to have a custom name, then enter the name of your choice. Important: If you are upgrading from Enterprise Manager 11g Grid Control Release 1 (11.1.0.1) or if you are upgrading an additional OMS from 10g Release 5 (10.2.0.5) or 11g Release 1 (11.1.0.1), then comment out this variable.
WLS_ADMIN_SERVER_PASSWORD	(Applicable only if you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5)) Enter a password for the WebLogic user account. Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value. Important: If you are upgrading from Enterprise Manager 11g Grid Control Release 1 (11.1.0.1) or if you are upgrading an additional OMS from 10g Release 5 (10.2.0.5) or 11g Release 1 (11.1.0.1), then comment out this variable.
WLS_ADMIN_SERVER_CONFIRM_PASSWORD	(Applicable only if you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5)) Confirm the password for the WebLogic user account. Important: If you are upgrading from Enterprise Manager 11g Grid Control Release 1 (11.1.0.1) or if you are upgrading an additional OMS from 10g Release 5 (10.2.0.5) or 11g Release 1 (11.1.0.1), then comment out this variable.
NODE_MANAGER_PASSWORD	(Applicable only if you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5)) By default, `nodemanager` is the name assigned to the default user account that is created for the node manager. Enter a password for this node manager user account. Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value. Important: If you are upgrading from Enterprise Manager 11g Grid Control Release 1 (11.1.0.1) or if you are upgrading an additional OMS from 10g Release 5 (10.2.0.5) or 11g Release 1 (11.1.0.1), then comment out this variable.
NODE_MANAGER_CONFIRM_PASSWORD	(Applicable only if you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5)) Confirm the password for the node manager user account. Important: If you are upgrading from Enterprise Manager 11g Grid Control Release 1 (11.1.0.1) or if you are upgrading an additional OMS from 10g Release 5 (10.2.0.5) or 11g Release 1 (11.1.0.1), then comment out this variable.
WLS_ADMIN_SERVER_PASSWORD	(Applicable only if you are upgrading from Enterprise Manager 11g Grid Control Release 1 (11.1.0.1)) Enter the password for the WebLogic user account you had created for Enterprise Manager 11g Grid Control Release 1 (11.1.0.1). Important: If you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or if you are upgrading an additional OMS from 10g Release 5 (10.2.0.5) or 11g Release 1 (11.1.0.1), then comment out this variable.
ADMIN_SERVER_HOSTNAME	(Applicable only if you are upgrading an additional OMS from 10g Release 5 (10.2.0.5) or 11g Release 1 (11.1.0.1)) Enter the host name of the AdminServer that is configured for the first OMS. Important: If you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or from Enterprise Manager 11g Grid Control Release 1 (11.1.0.1), then comment out this variable.
ADMIN_SERVER_PORT	(Applicable only if you are upgrading an additional OMS from 10g Release 5 (10.2.0.5) or 11g Release 1 (11.1.0.1)) Enter the port of the AdminServer that is configured for the first OMS. Important: If you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or from Enterprise Manager 11g Grid Control Release 1 (11.1.0.1), then comment out this variable.
WLS_ADMIN_SERVER_USERNAME	(Applicable only if you are upgrading an additional OMS from 10g Release 5 (10.2.0.5) or 11g Release 1 (11.1.0.1)) By default, `weblogic` is the name assigned to the default user account that is created for the Oracle WebLogic Domain. If you want to accept the default name, then blank. However, if you want to have a custom name, then enter the name of your choice. Important: If you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or from Enterprise Manager 11g Grid Control Release 1 (11.1.0.1), then comment out this variable.
WLS_ADMIN_SERVER_PASSWORD	(Applicable only if you are upgrading an additional OMS from 10g Release 5 (10.2.0.5) or 11g Release 1 (11.1.0.1)) Enter a password for the WebLogic user account. Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value. Important: If you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or from Enterprise Manager 11g Grid Control Release 1 (11.1.0.1), then comment out this variable.
JVM_DIAGNOSTICS_TABLESPACE_LOCATION	(Applicable only if you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5)) Enter the absolute path to a location where the data file (`mgmt_ad4j.dbf`) for JVM Diagnostics data tablespace can be stored. Ensure that the specified path leads up to the file name. For example, `/home/john/oradata/mgmt_ad4j.dbf` Enterprise Manager Cloud Control requires this data file to store monitoring data related to JVM Diagnostics and Application Dependency Performance (ADP).
SYS_PASSWORD	Enter the SYS user account's password.
SYSMAN_PASSWORD	Enter the SYSMAN user account's password.
STATIC_PORTS_FILE	If you are upgrading from Enterprise Manager 11g Grid Control Release 1 (11.1.0.1.0), then skip this parameter because the same ports are carried over to Enterprise Manager Cloud Control. If you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5.0), then enter the absolute path to the `staticports.ini` file that contains ONLY the following ports: `Admin Server Http SSL Port` `Managed Server Http Port` `Managed Server Http SSL Port` `Node Manager Http SSL Port` You must skip the other ports in the `staticports.ini` file because the ports used in the earlier release will be carried over to Enterprise Manager Cloud Control. The `staticports.ini` file is available in the following location of the software kit (DVD, downloaded software): `<software_kit>/response/staticports.ini`

Upgrading in Software-Only Mode with 2-System Upgrade Approach

This section describes how you can upgrade in software-only mode with 2-System upgrade approach. In particular, this section covers the following:

Installing Software Binaries
Running allroot.sh Script
Configuring and Upgrading

Installing Software Binaries

To install the software binaries of Enterprise Manager Cloud Control, follow the steps outlined in Installing Software Binaries.

Note:

If the Enterprise Manager Upload Http Port and Enterprise Manager Central Console Http Port are unlocked in your existing Enterprise Manager system, then while invoking the installer, pass the arguments ALLOW_ONLY_SECURE_ACCESS_TO_CONSOLE and LOCK_ORACLE_MANAGEMENT_SERVICE.

For example,

<Software_Location>/runInstaller -invPtrLoc /home/john/software/oracle/oraInst.loc ALLOW_ONLY_SECURE_ACCESS_TO_CONSOLE=FALSE LOCK_ORACLE_MANAGEMENT_SERVICE=FALSE

If you skip passing these arguments now, and if you want to unlock the ports later, then after upgrading the OMS, run these commands from the upgraded OMS home:

$<OMS_HOME>/bin/emctl secure unlock -console

$<OMS_HOME>/bin/emctl secure unlock -upload

Running allroot.sh Script

To run the allroot.sh script, After You Install.

Configuring and Upgrading

To configure the software binaries of Enterprise Manager Cloud Control, follow these steps:

Copy the following response file to an accessible location on your local host:

<Software_Location>/response/upgrade.rsp

In this command, <Software_Location> refers to the location where you have downloaded the software kit.
Edit the response file and enter appropriate values for the variables described in Table 19-3.

Configure the software binaries by invoking the ConfigureGC.sh script passing the response you edited in the previous step:

$<MIDDLEWARE_HOME>/oms/sysman/install/ConfigureGC.sh -silent -responseFile <absolute_path>/upgrade.rsp -staticPortsIniFile <absolute_path_to_staticports.ini_file> [-invPtrLoc <absolute_path_to_inventory_directory>]

Note:

While installing the software binaries as described in Installing Software Binaries, if you had passed the argument -invPtrLoc, then pass the same argument here as well.
For information about the additional, advanced options you can pass while invoking the script, refer to Using Advanced Script Options.
The staticports.ini file is available at the following location of the software kit (DVD, downloaded software, and so on):

<software_kit>/response/staticports.ini
In the staticports.ini file, ensure that the ports you enter for Enterprise Manager Upload Http Port and Enterprise Manager Upload Http SSL Port match with the unsecure and secure ports you entered in the Enterprise Manager 12c Upgrade Console.
If you see an error about missing plug-ins, then manually download those plug-ins (opar files) to an accessible location, and invoke the installer once again in the following way to copy the software binaries of the downloaded plug-ins. Ensure that the location to which you download the plug-ins is meant only for these missing plug-ins.

<software_kit>/runInstaller -plugininstall -pluginLocation <absolute_path_to_plugin_sw> -mwHome <absolute_path_to_middleware_home> [-invPtrLoc <absolute_path_to_oraInst.loc>]

To download the missing plug-ins (opar files), follow these steps:
1. Navigate to the following location where you installed the software binaries, and check if the opar files you are looking for are available. If they are available, copy them to an accessible location.
  
  $<OMS_HOME>/sysman/install/undeployed_plugins
2. If the opar files are not available in the OMS home, then download them from the following URL:
  
  http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-upgrade-console-502238.html
Proceed to the next step only after you have installed these missing plug-ins.

Note:

If you encounter any validation error, then follow these steps:

Discard the backed up database.
Resolve the issue in the Enterprise Manager 12c Upgrade Console.
Take a fresh backup of the database now.
Invoke the installer all over again, and retry the upgrade process.

Editing Response File for Configuring Software Binaries

Table 19-3 describes how you can edit the different variables included in the upgrade.rsp response file.

Table 19-3 Editing Response File for Configuring Software Binaries

Parameter	Description
ORACLE_INSTANCE_HOME_LOCATION	By default, `gc_inst` is considered as the OMS Instance Base directory for storing all OMS-related configuration files, and the by default, it is created in the middleware home. If you want to accept the default location and the directory name, then skip this variable. However, if you want to have a custom location and a custom directory name, then enter the absolute path to the custom location leading up to the custom directory name.
ONE_SYSTEM	By default, this variable is set to `FALSE` indicating that it is 2-System upgrade. Retain the default value.
OLD_DATABASE_CONNECTION_DESCRIPTION	Enter the connect string in the following format to connect to the old Management Repository. With SID `(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<host_name>)(PORT=<port>)))(CONNECT_DATA=(SID=<sid>)))` With Service Name `(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<host_name>)(PORT=<port>)))(CONNECT_DATA=(SERVICE_NAME=<service_name>)))` The connect string is used to connect to the old Management Repository, check for accrued data, and seamlessly transfer it to the upgraded Management Repository. Accrued data refers to the data that was uploaded to the old Management Repository from the time it was backed up till the time it was upgraded.
OLD_DATABASE_SYSMAN_PASSWORD	Enter the SYSMAN password of the old Management Repository.
WLS_ADMIN_SERVER_USERNAME	By default, `weblogic` is the name assigned to the default user account that is created for the Oracle WebLogic Domain. If you want to accept the default name, then blank. However, if you want to have a custom name, then enter the name of your choice.
WLS_ADMIN_SERVER_PASSWORD	Enter a password for the WebLogic user account. Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value.
WLS_ADMIN_SERVER_CONFIRM_PASSWORD	Confirm the password for the WebLogic user account.
NODE_MANAGER_PASSWORD	By default, `nodemanager` is the name assigned to the default user account that is created for the node manager. Enter a password for this node manager user account. Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value.
NODE_MANAGER_CONFIRM_PASSWORD	Confirm the password for the node manager user account.
WLS_ADMIN_SERVER_PASSWORD	Comment out this variable.
ADMIN_SERVER_HOSTNAME	Comment out this variable.
ADMIN_SERVER_PORT	Comment out this variable.
WLS_ADMIN_SERVER_USERNAME	Comment out this variable.
WLS_ADMIN_SERVER_PASSWORD	Comment out this variable.
JVM_DIAGNOSTICS_TABLESPACE_LOCATION	(Applicable only if you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5)) Enter the absolute path to a location where the data file (`mgmt_ad4j.dbf`) for JVM Diagnostics data tablespace can be stored. Ensure that the specified path leads up to the file name. For example, `/home/john/oradata/mgmt_ad4j.dbf` Enterprise Manager Cloud Control requires this data file to store monitoring data related to JVM Diagnostics and Application Dependency Performance (ADP).
DATABASE_HOSTNAME	Enter the fully qualified name of the host where the existing database resides. For example, `example.com` If you are connecting to an Oracle RAC Database, and if the nodes have virtual host names, then enter the virtual host name of one of its nodes. The connection to the database is established with a connect string that is formed using only this virtual host name, and the installation ends successfully. However, if you want to update the connect string with other nodes of the cluster, then after the installation, do the following: Open the following file: `<OMS_Instance_Home>/em/EMGC_OMS#/emgc.properties` Enter the other nodes for the variable `EM_RESPOS_CONNECTDESCRIPTOR`.
LISTENER_PORT	Enter the listener port to connect to the existing database. For example, `1532`
SERVICENAME_OR_SID	Enter the service name or the system ID (SID) of the existing database. For example, `orcl`
SYS_PASSWORD	Enter the SYS user account's password.
SYSMAN_PASSWORD	Enter the SYSMAN user account's password.