Oracle® Enterprise Manager Grid Control Advanced Installation and Configuration Guide 11g Release 1 (11.1.0.1.0) Part Number E16847-10 |
|
|
PDF · Mobi · ePub |
This chapter describes how you can upgrade an existing Oracle Management Agent 10g Release 4 or 5 (10.2.0.4.0 or 10.2.0.5.0) to Oracle Management Agent 11g Release 1 (11.1.0.1.0) in silent mode, using the agentDownload
script. In particular, this section covers the following:
You can upgrade an existing Oracle Management Agent 10g Release 4 or 5 (10.2.0.4.0 or 10.2.0.5.0) to Oracle Management Agent 11g Release 1 (11.1.0.1.0) in silent mode using the agentDownload
script. The agentDownload
script is a script that helps you upgrade Management Agents, silently without having to use the GUI screens of Enterprise Manager Grid Control. The script is available on the source host where Oracle Management Service (OMS) is installed, and it is run from the node where the Management Agent needs to be upgraded. For more information about the agentDownload
script, see Overview.
Before you begin, keep in mind the following points:
If you are upgrading a Management Agent whose software binaries were used for installing additional Management Agents, either using the Shared Agent Deployment Wizard or the nfsagentinstall
script, then before proceeding any further, read Chapter 27, "Upgrading Shared Oracle Management Agent".
Before upgrading the Management Agent, ensure that you meet the prerequisites described in Prerequisites.
To upgrade an existing Management Agent using the agentDownload
script, follow these steps:
On the destination host where you want to upgrade the Management Agent, open a browser to access the OMS URL and download the script.
UNIX Platform | Microsoft Windows Platforms |
---|---|
Using Browser
http://<oms_host>:<oms_port>/agent_download/<version>/<platform>/agentDownload.<platform> For example: http://host1.servers.com:4889/agent_download/11.1.0.0.0/linux/agentDownload.linux Using Command Line wget http://<oms_host>:<oms_port>/agent_download/<version>/<platform>/agentDownload.<platform> For example: wget http://host1.servers.com:4889/agent_download/11.1.0.0.0/linux/agentDownload.linux |
Using Browser
http://<oms_host>:<oms_port>/agent_download/<version>/<platform>/agentDownload.vbs For example: http://host1.servers.com:4889/agent_download/11.1.0.0.0/win32/agentDownload.vbs Using Command Line wget http://<oms_host>:<oms_port>/agent_download/<version>/<platform>/agentDownload.vbs For example: wget http://host1.servers.com:4889/agent_download/11.1.0.0.0/win32/agentDownload.vbs |
Run the agentDownload script on the destination host using the following command. For other options, you can use with the command, see Table 26-1.
UNIX Platform | Microsoft Windows Platforms |
---|---|
./agentDownload.<platform> -u -o <absolute_path_to_old_oracle_home> -b <absolute_path_to_new_installation_base_directory>For example: ./agentDownload.linux -u -o /john/OracleHomes/agent10g -b /peter/OracleHomes |
./agentDownload.vbs u o <absolute_path_to_old_oracle_home> b <absolute_path_to_new_installation_base_directory>For example: ./agentDownload.vbs u o /john/OracleHomes/agent10g b /peter/OracleHomes |
Note:
The-b
argument can be skipped if you have specified the installation base directory for the parameter ORACLE_AGENT_HOME_LOCATION
in the agent_download.rsp file. However, if you still pass the argument -b
in the command, then the installation base directory specified in the command is honored and the one specified in the response file is ignored.Note:
On Microsoft Windows, do the following:If you are upgrading a non-shared RAC Agent, then run the following command on every node of the cluster:
./agentDownload.vbs u o <absolute_path_to_old_oracle_home> b <absolute_path_to_new_installation_base_directory> -local
If you are upgrading a shared RAC Agent, then do the following:
(a) On one of the nodes, run the following command:
./agentDownload.vbs u o <absolute_path_to_old_oracle_home> b <absolute_path_to_new_installation_base_directory> -local
(b) On each of the other nodes, run the following command from the Oracle home of the Management Agent:
<ORACLE_HOME>/bin/agentca -u -c <comma-separated_list_of_nodes'_short_names> -r <absolute_path_to_response_file>
Here, the response file passed in the above-mentioned command contains the following parameter with the fully qualified name of the node on which you are invoking the command:
s_hostname=<fully_qualified_name_of_node>
If the Management Agent that you are upgrading was not secure, then the agentDownload script prompts you to specify the agent registration password.
The following are the arguments you can pass while running the agentDownload script:
Note:
On Microsoft Windows, do not hyphenate the arguments. For example, the-b
argument when run on Microsoft Windows is b
.Table 26-1 Arguments Supported by agentDownload Script
Options | Description |
---|---|
-b |
Specify the installation base directory for the Management Agent. |
-c |
Specify the nodes of a cluster for which you want to upgrade the Management Agent. For example, - c "node1,node2,node3" |
-d |
Indicates that you do NOT want to initiate automatic target discovery. |
-i |
Specify the inventory pointer location file. |
-l |
Indicates that the command will work only on the local host. |
-n |
Specify the cluster name. |
-N |
Indicates that you do not want to be prompted for Agent Registration Password. |
-o |
Specify the full path to the Oracle home of the Management Agent you want to upgrade. |
-p |
Specify the |
-R |
To use virtual host name (ORACLE_HOSTNAME) for this installation. If this is being used along with more than one cluster node through -c option, then -l option also needs to be passed. |
-s |
Specify the installer stage directory. |
-t |
Indicates that you do NOT want to start the Management Agent. |
-u |
Indicates that you want to upgrade. |
-v |
Specify the inventory directory location. |
-x |
Indicates you want debug output. |
-y |
Indicates that you want to decline security updates. |