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, |
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, |
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 |
|
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 |
|
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
|
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 5 (12.1.0.5) is an out-of-place upgrade, therefore you must do one of the following:
Ensure that the middleware location has write permission. 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,
Important: If you are installing on an NFS-mounted drive and creating the OMS instance base directory (gc_inst) on that 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. If you are upgrading from 10g Release 5 (10.2.0.5), then it is the old OMS base directory. If you are upgrading from 11g Release 1 (11.1.0.1) or within the 12c series, then it is the middleware home. |
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.
|
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
|
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, |
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:
The connect string is used to connect to the old Management Repository, check for accrued data, and 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.
|
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 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.4, 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,
|
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.4, 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.4, 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.4, 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, 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.4, 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.4, 12.1.0.3, 12.1.0.2, and 11.1.0.1. Applicable to additional OMS upgrade of 12.1.0.4, 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.4, 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 For example, |
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, 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:
|
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, |
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, " |
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 |
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 For example, If you want to install
If you want to install any plug-in that is not available in the software kit, then do the following:
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 5 (12.1.0.5). In this case, when you invoke the installer with |