17 Upgrading OMS and Repository in Silent Mode

This chapter describes how you can upgrade your existing Oracle Management Service (OMS) and Oracle Management Repository (Management Repository) in silent mode using one of the upgrade approaches. In particular, this chapter covers the following:

Upgrading with 1-System Upgrade Approach in Silent Mode
Upgrading with 2-System Upgrade Approach in Silent Mode

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 with 1-System Upgrade Approach in Silent Mode

Note:

When you upgrade using the 1-System upgrade approach, the Enterprise Manager Cloud Control Installation Wizard does not install a Management Agent with the OMS it installs. The Management Agent is predeployed using the Enterprise Manager 12c Upgrade Console. This is an expected behavior.

To upgrade your existing OMS and Management Repository with 1-System upgrade approach in silent mode, 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 software kit.
Edit the response file and enter appropriate values for the variables described in Table 17-1.
Invoke the installer:

./runInstaller -silent -responseFile <absolute_path>/upgrade.rsp

Note:
For information about the additional, advanced options you can pass while invoking the installer, refer to Using Advanced Installer Options.

Note:
To invoke the installation wizard on UNIX platforms, run runInstaller. To invoke on Microsoft Windows platforms, run setup.exe.

Using Advanced Installer Options

The following are some additional, advanced options you can pass while invoking the installer:

If you are upgrading on a host that has multiple host names (for examle, virtual host), then pass the fully qualified host name using the ORACLE_HOSTNAME argument while invoking the installer.

For example:

./runInstaller ORACLE_HOSTNAME=example.com -silent -responseFile <absolute_path>/upgrade.rsp
After the installation ends successfully, the OMS and the Management Agent start automatically. If you do not want them to start automatically, then invoke the installer with START_OMS and b_startAgent options, and set them to TRUE or FALSE depending on what you want to control.

For example, if you do not want the Management Agent to start automatically, then run the following command:

./runInstaller START_OMS=TRUE b_startAgent=FALSE -silent -responseFile <absolute_path>/upgrade.rsp

To understand the limitations involved with this advanced option, see Limitations.

Editing Response File for Upgrading with 1-System Upgrade Approach in Silent Mode

Table 17-1 describes what variables you must update and how you must update them in the upgrade.rsp response file for upgrading your OMS and Management Repository.

Table 17-1 Editing Response File for Upgrading with 1-System Upgrade Approach in Graphical Mode

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. 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.
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 `TRUE`. Retain the default setting.
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`
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 when you upgrade your Enterprise Manager. 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>`

Upgrading with 2-System Upgrade Approach in Silent Mode

To upgrade your existing OMS and Management Repository using 2-System upgrade approach in silent mode, 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 17-2.

Invoke the installer:

If this is the first Oracle product you are installing on the host, then run the following command on the host where you plan to install Oracle Management Service 12c:

./runInstaller -silent -responseFile <absolute_path>/upgrade.rsp [-invPtrLoc <absolute_path_to_inventory_directory>] -staticPortsIniFile <absolute_path_to_staticports.ini_file> [ALLOW_ONLY_SECURE_ACCESS_TO_CONSOLE=FALSE LOCK_ORACLE_MANAGEMENT_SERVICE=FALSE]

Note:
The central inventory location you enter must NOT be on a shared file system.
Otherwise, run the following command:

./runInstaller -silent -responseFile <absolute_path>/upgrade.rsp -staticPortsIniFile <absolute_path_to_file>

Note:

For information about the additional, advanced options you can pass while invoking the installer, refer to Using Advanced Installer Options.

To invoke the installation wizard on UNIX platforms, run runInstaller. To invoke on Microsoft Windows platforms, run setup.exe.

Note:

Ensure that the host on which you are invoking the installer matches with the host you entered in the Enterpriser Manager 12c Upgrade Console.

If you are invoking the installer on a different host, and if you choose to modify the host name in the Enterpriser Manager 12c Upgrade Console, then follow these steps:
1. Exit the installer.
2. Discard the backed up database.
3. Access the Enterpriser Manager 12c Upgrade Console, and change the host name in the Identify Host and Port for New Enterprise Manager System page.
4. Take a fresh backup of the database now.
5. Invoke the installer all over again, and retry the upgrade process.
In this case, you must ensure that all the Management Agents, which were already deployed and configured through the Enterpriser Manager 12c Upgrade Console before upgrading the OMS, are reconfigured with the new host name.
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 decide to change the ports in the Enterprise Manager 12c Upgrade Console instead, then follow these steps:
1. Exit the installer.
2. Discard the backed up database.
3. Change the ports in the Enterprise Manager 12c Upgrade Console.
4. Take a fresh backup of the database now.
5. Invoke the installer all over again, and retry the upgrade process.

Note:

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

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

Editing Response File for Upgrading with 2-System Upgrade Approach in Silent Mode

Table 17-2 describes what variables you must update and how you must update them in the upgrade.rsp response file for upgrading your OMS and Management Repository.

Table 17-2 Editing Response File for Upgrading with 2-System Upgrade Approach in Silent Mode

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. Enter that this location is not an NFS-mounted location. 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.
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. Note: If you have entered an NFS-mounted drive for the `ORACLE_MIDDLEWARE_HOME_LOCATION` parameter, then ensure that the location you enter for this parameter is a non-NFS-mounted location.
ONE_SYSTEM	By default, this variable is set to `TRUE.` Change the value to `FALSE.`
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.
STATIC_PORTS_FILE	The default ports are honored. If you want to accept the default ports, then skip this fiield. For information about the default ports, see the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide. If you want to use custom ports, then enter the absolute path to the `staticports.ini` file that lists the custom ports to be used for the installation. The `staticports.ini` file is available in the following location of the software kit (DVD, downloaded software): `<software_kit>/response/staticports.ini`
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 when you upgrade your Enterprise Manager. 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>`