Skip Headers
Oracle® Enterprise Manager Cloud Control Upgrade Guide
12c Release 4 (12.1.0.4)

E22625-29
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

A Editing the Response File for Upgrading Oracle Management Service and Oracle 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 Parameters of the upgrade.rsp File for Upgrading OMS in Silent Mode

Parameter Name Applicable Upgrade Approach Data Type Are Double Quotes Needed for the Values? Description

UNIX_GROUP_NAME

Applicable to all upgrade approaches for normal upgrade as well as software-only upgrade.

String

Yes

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

For example, "dba".

INVENTORY_LOCATION

Applicable to all upgrade approaches for normal upgrade as well as software-only upgrade.

String

Yes

(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

Applicable to all upgrade approaches for normal upgrade.

Not applicable to software-only upgrade. Therefore, comment out this parameter for this upgrade approach.

Boolean

Yes

  • Enter TRUE if you want to download and install security updates. Then, enter the credentials for the following variables in double quotes:

    MYORACLESUPPORT_USERNAME

    MYORACLESUPPORT_PASSWORD

  • Enter FALSE if you do not want to download and install security updates:

DECLINE_SECURITY_UPDATES

Applicable to all upgrade approaches for normal upgrade.

Not applicable to software-only upgrade. Therefore, comment out this parameter for this upgrade approach.

Boolean

No

  • 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

Applicable to all upgrade approaches of normal upgrade.

Not applicable to software-only upgrade. Therefore, comment out this parameter for this upgrade approach.

String

Yes

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 in double quotes:

    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, in double quotes.

    For this option, as a prerequisite, you must have already downloaded the software updates. For instructions, see Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

ORACLE_MIDDLEWARE_HOME_LOCATION

Applicable to all upgrade approaches of normal upgrade.

Not applicable to software-only upgrade. Therefore, comment out this parameter for this upgrade approach.

String

Yes

Upgrade to 12c Release 4 (12.1.0.4) 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.6) and Java Development Kit 1.6.0.43.0. 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.

ORACLE_INSTANCE_HOME_LOCATION

Applicable to all upgrade approaches for normal upgrade as well as software-only upgrade.

String

Yes

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 outside the Middleware home.

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

  • To have a custom location and a custom directory name, enter the absolute path to the custom location leading up to the custom directory name.

Important: If you are creating the OMS instance base directory (gc_inst) on an NFS-mounted drive, then after you install, move the lock files from the NFS-mounted drive to a local file system location. Modify the lock file location in the httpd.conf file to map to a location on a local file system. For instructions, refer to Section 5.1.4.

OLD_BASE_DIR

Applicable only to 1-system upgrade approach for normal upgrade as well software-only upgrade.

Not applicable to 2-system upgrade approach and 1-system upgrade approach on a different host. Therefore, comment out this parameter for these upgrade approaches.

String

Yes

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

ORACLE_HOSTNAME

Applicable only to 2-system upgrade approach and 1-system upgrade approach on a different host for normal upgrade.

Not applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade. Not applicable for 2-system upgrade approach and 1-system upgrade approach on a different host for software-only upgrade. Therefore, comment out this parameter for these upgrade approaches.

String

Yes

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.

ONE_SYSTEM

Applicable to all upgrade approaches for normal upgrade as well as software-only upgrade.

Boolean

No

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 to 2-system upgrade approach and 1-system upgrade approach on a different host for normal upgrade.

Not applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade. Not applicable to 2-system upgrade approach and 1-system upgrade approach on a different host for software-only upgrade. Also not applicable for additional OMS upgrade. Therefore, comment out this parameter for these upgrade approaches.

String

Yes

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.

OLD_DATABASE_CONNECTION_DESCRIPTION

Applicable only to 2-system upgrade approach and 1-system upgrade approach on a different host for normal upgrade as well as software-only upgrade.

Not applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade. Also not applicable for additional OMS upgrade. Therefore, comment out this parameter for this upgrade approach.

String

Yes

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

    "(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.

OLD_DATABASE_SYSMAN_PASSWORD

Applicable only to 2-system upgrade approach and 1-system upgrade approach on a different host for normal upgrade as well as software-only upgrade.

Not applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade. Also not applicable for additional OMS upgrade. Therefore, comment out this parameter for this upgrade approach.

String

Yes

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.

WLS_ADMIN_SERVER_USERNAME

Applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade of 10.2.0.5. Applicable to 2-system upgrade approach and 1-system upgrade approach on a different host for normal upgrade as well as software-only upgrade of 10.2.0.5 and 11.1.0.1.

Not applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade of 12.1.0.3, 12.1.0.2, and 11.1.0.1. Not applicable to additional OMS upgrade. Therefore, comment out this parameter for these upgrade approaches.

String

Yes

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.

WLS_ADMIN_SERVER_PASSWORD

Applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade of 10.2.0.5. Applicable to 2-system upgrade approach and 1-system upgrade approach on a different host for normal upgrade as well as software-only upgrade of 10.2.0.5 and 11.1.0.1.

Not applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade of 12.1.0.3, 12.1.0.2, and 11.1.0.1. Not applicable to additional OMS upgrade. Therefore, comment out this parameter for these upgrade approaches.

String

Yes

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

Applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade of 10.2.0.5. Applicable to 2-system upgrade approach and 1-system upgrade approach on a different host for normal upgrade as well as software-only upgrade of 10.2.0.5 and 11.1.0.1.

Not applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade of 12.1.0.3, 12.1.0.2, and 11.1.0.1. Not applicable to additional OMS upgrade. Therefore, comment out this parameter for these upgrade approaches.

String

Yes

Confirm the password for the WebLogic user account.

NODE_MANAGER_PASSWORD

Applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade of 10.2.0.5. Applicable to 2-system upgrade approach and 1-system upgrade approach on a different host for normal upgrade as well as software-only upgrade of 10.2.0.5 and 11.1.0.1.

Not applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade of 12.1.0.3, 12.1.0.2, and 11.1.0.1. Not applicable to additional OMS upgrade. Therefore, comment out this parameter for these upgrade approaches.

String

Yes

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

Applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade of 10.2.0.5. Applicable to 2-system upgrade approach and 1-system upgrade approach on a different host for normal upgrade as well as software-only upgrade of 10.2.0.5 and 11.1.0.1.

Not applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade of 12.1.0.3, 12.1.0.2, and 11.1.0.1. Not applicable to additional OMS upgrade. Therefore, comment out this parameter for these upgrade approaches.

String

Yes

Confirm the password for the node manager user account.

WLS_ADMIN_SERVER_PASSWORD

Applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade of 12.1.0.3, 12.1.0.2, and 11.1.0.1. Applicable to additional OMS upgrade of 12.1.0.3, 12.1.0.2, 11.1.0.1, and 10.2.0.5.

Not applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade of 10.2.0.5. Not applicable to 2-system upgrade approach and 1-system upgrade approach on a different host for normal upgrade as well as software-only upgrade of 10.2.0.5 and 11.1.0.1. Therefore, comment out this parameter for these upgrade approaches.

String

Yes

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

JVM_DIAGNOSTICS_TABLESPACE_LOCATION

Applicable to all upgrade approaches for normal upgrade as well as software-only upgrade of 10.2.0.5.

Not applicable to any of the upgrade approaches for normal upgrade as well as software-only upgrade of 12.1.0.2, 12.1.0.3, and 11.1.0.1. Therefore, comment out this parameter for these upgrade approaches.

String

Yes

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_deepdive.dbf) for this tablespace can be stored. Ensure that the entered path leads up to the file name.

For example, "/home/john/oradata/mgmt_deepdive.dbf".

DATABASE_HOSTNAME

Applicable to 2-system upgrade approach and 1-system upgrade approach on a different host for normal upgrade as well as software-only upgrade.

Not applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade. Therefore, comment out this parameter for this approach.

String

Yes

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.

LISTENER_PORT

Applicable to 2-system upgrade approach and 1-system upgrade approach on a different host for normal upgrade as well as software-only upgrade.

Not applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade. Therefore, comment out this parameter for this approach.

String

Yes

Enter the listener port to connect to the existing database.

For example, "1532".

SERVICENAME_OR_SID

Applicable to 2-system upgrade approach and 1-system upgrade approach on a different host for normal upgrade as well as software-only upgrade.

Not applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade. Therefore, comment out this parameter for this approach.

String

Yes

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

For example, "orcl".

SYS_PASSWORD

Applicable to all upgrade approaches for normal upgrade as well as software-only upgrade.

String

Yes

Enter the SYS user account's password.

SYSMAN_PASSWORD

Applicable to all upgrade approaches for normal upgrade as well as software-only upgrade.

String

Yes

Enter the SYSMAN user account's password.

REPOSITORY_BACKUP_DONE

Applicable to 1-system upgrade approach for normal upgrade as well as software-only upgrade.

Not applicable to 2-system upgrade approach and 1-system upgrade approach on a different host for normal upgrade as well as software-only upgrade.

Boolean

No

As a prerequisite, you must back up the Management Repository before you start upgrading your Enterprise Manager system. If you have taken a backup, then set this parameter to TRUE. Otherwise, set it to FALSE

PLUGIN_SELECTION

Applicable to all upgrade approaches for normal upgrade as well as software-only upgrade.

String List

Yes

(A comma-separated list of plug-in names, where the plug-in names must be in double quotes)

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, Oracle Exadata Management Plug-In, and Oracle Cloud Framework 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. Access the following Enterprise Manager download page on Oracle Technology Network (OTN):

    http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-upgrade-console-502238.html

  2. Expand the section that lists the software binaries and plug-ins for your upgrade path.

  3. From the Download Plug-ins section, manually download the plug-ins and store them in an accessible location.

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

  5. 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 4 (12.1.0.4). 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 4 (12.1.0.4). After you upgrade, you can deploy the higher version directly from the Plug-In Manager.