Skip Headers
Oracle® Enterprise Manager Cloud Control Upgrade Guide
12c Release 2 (12.1.0.2)
E22625-16
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

A Editing Response File for Upgrading OMS and Management Repository in Silent Mode

Table A-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 in silent mode.

Table A-1 Editing Response File for Upgrading OMS and Management Repository in Silent Mode

Variable Description

UNIX_GROUP_NAME

(Required only when central inventory does not exist) Enter the name of the UNIX group you belong to.

For example, "dba"

INVENTORY_LOCATION

(Required only when central inventory does not exist) 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:

Important: If you are performing a software-only upgrade, then comment out this variable.

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.

Important: If you are performing a software-only upgrade, then comment out this variable.

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 variables:

    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 variable, enter the absolute path, which leads to the Updates directory, where the software updates are available.

Important: If you are performing a software-only upgrade, then comment out this variable.

Important: Make sure you apply patch 15951627. This patch fixes some critical, upgrade-related issues. If you do not have this patch, then manually download it from My Oracle Support using another host that has Internet connectivity, and transfer it to the local directory on this host where you are performing the installation.

ORACLE_MIDDLEWARE_HOME_LOCATION

Upgrade to 12c Release 2 (12.1.0.2) is an out-of-place upgrade, therefore you must specify an existing middleware home or enter a new middleware home where Oracle WebLogic Server and Java Development Kit are installed.

Enter the location where you have installed Oracle WebLogic Server 11g Release 1 (10.3.5) and Java Development Kit 1.6 v24. If you do not already have them installed, then enter the location where you want the installer to install them.

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.

Important: If you are performing a software-only upgrade, then comment out this variable.

ORACLE_INSTANCE_HOME_LOCATION

By default, gc_inst is considered as the OMS Instance Base directory for storing all OMS-related configuration files, and by default, it is created in the Middleware home.

  • To accept the default location and the directory name, then leave it blank.

  • 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

(Applicable only for 1-system upgrade)

Enter the base directory of the OMS you want to upgrade.

Important: If you are performing a 2-system upgrade, then comment out this variable.

ORACLE_HOSTNAME

(Applicable only for 2-system upgrade)

By default, the fully qualified name of the host on which you have invoked the installer, is considered.

  • To accept the default value, leave it blank.

  • To install with a different host name, then enter another host name.

Important: If you are performing a 1-system upgrade, then comment out this variable.

ONE_SYSTEM

By default, this variable is set to true, which indicates that you are performing a 1-system upgrade.

  • If you are indeed performing a 1-system upgrade, retain this value.

  • If you are performing a 2-system upgrade, then set it to false.

AGENT_BASE_DIR

(Applicable only for 2-system upgrade)

Enter the absolute path to the agent base directory, a location outside the Oracle Middleware home where the Management Agent can be installed.

For example, u01/app/software/agent. Ensure that this location is empty and has write permission. Also ensure that it is always maintained outside the Oracle Middleware home.

Important: If you are performing a 1-system upgrade, then comment out this variable.

OLD_DATABASE_CONNECTION_DESCRIPTION

(Applicable only for 2-system upgrade)

By default, the connect string of the old Management Repository you entered in the Preupgrade Console is considered. However, if you had not entered there, then you can enter here in the following format:

  • To connect using SID, enter the connect string in the following forma:

    (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<host_name>)(PORT=<port>)))(CONNECT_DATA=(SID=<sid>)))

    For example,

    (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=example.com)(PORT=1521)))(CONNECT_DATA=(SID=emrep)))

  • To connect using the service name, enter the connect string in the following format:

    (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<host_name>)(PORT=<port>)))(CONNECT_DATA=(SERVICE_NAME=<service_name>)))

    For example,

    (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=example.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=emrep)))

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.

IMPORTANT: Verify the value set to the GLOBAL_NAMES parameter on both the databases.

  • If the GLOBAL_NAMES parameter is set to FALSE on both the databases, then ensure that you do not change this value until the upgrade is complete, and all the Management Agents are switched over.

  • If the GLOBAL_NAMES parameter is set to TRUE on even one of the databases, and if both the databases have the same value for the GLOBAL_NAME parameter, then change the value of the GLOBAL_NAME parameter set on the new, cloned database to a value that is different from the one set on the old database.

Important: If you are performing a 1-system upgrade, then comment out this variable.

OLD_DATABASE_SYSMAN_PASSWORD

(Applicable only for 2-system upgrade)

Enter the SYSMAN password of the old Management Repository.

The password is used to connect to the old Management Repository using the connect string entered either in the Preupgrade Console or in the previous variable; 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

Important: If you are performing a 1-system upgrade, then comment out this variable.

WLS_ADMIN_SERVER_USERNAME

(Applicable only for 1-system upgrade of 10g Release 5 (10.2.0.5), and 2-system upgrade of 10g Release 5 (10.2.0.5) and 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.

  • To accept the default name, leave this variable blank.

  • To have a custom name, then enter the name of your choice.

Important: If you are performing a 1-system upgrade of 11g Release 1 (11.1.0.1) or 12c Release 1 (12.1.0.1), or if you are upgrading an additional OMS from 10g Release 5 (10.2.0.5), 11g Release 1 (11.1.0.1), or 12c Release 1 (12.1.0.1), then comment out this variable.

WLS_ADMIN_SERVER_PASSWORD

(Applicable only for 1-system upgrade of 10g Release 5 (10.2.0.5), and 2-system upgrade of 10g Release 5 (10.2.0.5) and 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 performing a 1-system upgrade of 11g Release 1 (11.1.0.1) or 12c Release 1 (12.1.0.1), or if you are upgrading an additional OMS from 10g Release 5 (10.2.0.5), 11g Release 1 (11.1.0.1), or 12c Release 1 (12.1.0.1), then comment out this variable.

WLS_ADMIN_SERVER_CONFIRM_PASSWORD

(Applicable only for 1-system upgrade of 10g Release 5 (10.2.0.5), and 2-system upgrade of 10g Release 5 (10.2.0.5) and 11g Release 1 (11.1.0.1))

Confirm the password for the WebLogic user account.

Important: If you are performing a 1-system upgrade of 11g Release 1 (11.1.0.1) or 12c Release 1 (12.1.0.1), or if you are upgrading an additional OMS from 10g Release 5 (10.2.0.5), 11g Release 1 (11.1.0.1), or 12c Release 1 (12.1.0.1), then comment out this variable.

NODE_MANAGER_PASSWORD

(Applicable only for 1-system upgrade of 10g Release 5 (10.2.0.5), and 2-system upgrade of 10g Release 5 (10.2.0.5) and 11g Release 1 (11.1.0.1))

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 performing a 1-system upgrade of 11g Release 1 (11.1.0.1) or 12c Release 1 (12.1.0.1), or if you are upgrading an additional OMS from 10g Release 5 (10.2.0.5), 11g Release 1 (11.1.0.1), or 12c Release 1 (12.1.0.1), then comment out this variable.

NODE_MANAGER_CONFIRM_PASSWORD

(Applicable only for 1-system upgrade of 10g Release 5 (10.2.0.5), 2-system upgrade of 10g Release 5 (10.2.0.5) and 11g Release 1 (11.1.0.1))

Confirm the password for the node manager user account.

Important: If you are performing a 1-system upgrade of 11g Release 1 (11.1.0.1) or 12c Release 1 (12.1.0.1), or if you are upgrading an additional OMS from 10g Release 5 (10.2.0.5), 11g Release 1 (11.1.0.1), or 12c Release 1 (12.1.0.1), then comment out this variable.

WLS_ADMIN_SERVER_PASSWORD

(Applicable only for 1-system upgrade of 11g Release 1 (11.1.0.1) and 12c Release 1 (12.1.0.1))

Enter the password for the WebLogic user account you had created for the old Enterprise Manager system.

Important: If you are upgrading 10g Release 5 (10.2.0.5), or if you are upgrading an additional OMS from 10g Release 5 (10.2.0.5), 11g Release 1 (11.1.0.1), or 12c Release 1 (12.1.0.1), then comment out this variable.

ADMIN_SERVER_HOSTNAME

(Applicable only for 1-system upgrade)

Enter the host name of the AdminServer that is configured for the first OMS. This is required for creating a new WebLogic domain (GCDomain) for the upgraded OMS on the same host as the Admin Server used by the earlier release of the OMS you are upgrading.

Important: If you are upgrading the first OMS of 10g Release 5 (10.2.0.5), then comment out this variable.

ADMIN_SERVER_PORT

(Applicable only for 1-system upgrade)

Enter the port of the AdminServer that is configured for the first OMS. This is required for creating a new WebLogic domain (GCDomain) for the upgraded OMS on the same port as the Admin Server used by the earlier release of the OMS you are upgrading.

Important: If you are upgrading the first OMS of 10g Release 5 (10.2.0.5), then comment out this variable.

WLS_ADMIN_SERVER_USERNAME

(Applicable only for 1-system upgrade)

By default, weblogic is the name assigned to the default user account that is created for the Oracle WebLogic Domain.

  • To accept the default name, then leave it blank.

  • To have a custom name, then enter the name of your choice.

Important: If you are upgrading the first OMS of 10g Release 5 (10.2.0.5), then comment out this variable.

WLS_ADMIN_SERVER_PASSWORD

(Applicable only for 1-system upgrade)

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 the first OMS of 10g Release 5 (10.2.0.5), then comment out this variable.

JVM_DIAGNOSTICS_TABLESPACE_LOCATION

(Applicable for 1-system upgrade and 2-system upgrade)

(Applicable only if you are upgrading 10g Release 5 (10.2.0.5))

During upgrade, an additional tablespace called JVM diagnostics data tablespace is created for storing all JVM-related monitoring data. Enter the absolute path to a location where the data file (mgmt_ad4j.dbf) for this tablespace can be stored. Ensure that the entered path leads up to the file name.

For example, /home/john/oradata/mgmt_ad4j.dbf

Important: If you are upgrading 11g Release 1 (11.1.0.1) or 12c Release 1 (12.1.0.1), then comment out this variable.

DATABASE_HOSTNAME

(Applicable only for 2-system upgrade)

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:

  1. Open the following file:

    <OMS_Instance_Home>/em/EMGC_OMS#/emgc.properties

  2. Enter the other nodes for the variable EM_RESPOS_CONNECTDESCRIPTOR.

Important: If you are performing a 1-system upgrade, then comment out this variable.

LISTENER_PORT

(Applicable only for 2-system upgrade)

Enter the listener port to connect to the existing database.

For example, 1532

Important: If you are performing a 1-system upgrade, then comment out this variable.

SERVICENAME_OR_SID

(Applicable only for 2-system upgrade)

Enter the service name or the system ID (SID) of the existing database.

For example, orcl

Important: If you are performing a 1-system upgrade, then comment out this variable.

SYS_PASSWORD

Enter the SYS user account's password.

SYSMAN_PASSWORD

Enter the SYSMAN user account's password.

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. The plug-ins are available in the Disk1/plugins directory.

For example,

If you want to install 12.1.0.2.0_oracle.sysman.empa_2000_0.opar and 12.1.0.2.0_oracle.sysman.vt_2000_0.opar, then enter the plug-in IDs in the following way:

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:

  1. 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

  2. Update this variable (PLUGIN_SELECTION) to the names of those plug-ins you downloaded.

  3. 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>

You might have a plug-in version deployed to the earlier release of Enterprise Manager that is not supported in Enterprise Manager Cloud Control 12c Release 2 (12.1.0.2), for example, EBS 2.0 and 3.0 plug-in versions. In this case, when you invoke the installer with -pluginLocation argument, make sure you do NOT provide the software of the higher version of the unsupported plug-in even if the higher version is available for download. This ensures that the unsupported version is removed while upgrading to 12c Release 2 (12.1.0.2). After you upgrade, you can deploy the higher version directly from the Plug-In Manager.