OEM Grid Control Upgrade Continued :
Installation Procedure:
For upgrading to Enterprise Manager Grid Control 10.2.0.x.x to 10.2.0.5, you must manually download from metalink and extract the 10.2.0.5 Patch Set.
Download and extract the Patch Set:.
1. Download the p3731593_102050_<platform name>.zip patch set installation archive to any directory.
2. Enter the following command to unzip and extract the installation files:
$ unzip p3731593_102050_<platform name>.zip
This extracts the files to the "3731593" directory.
NOTE:
The same Patch Set can be used for upgrading Oracle Management Service, Grid Control Repository (sysman schema), and Management Agent.
Upgrading Oracle Management Service:
The pre-installation tasks can be broadly categorized based on the following types of upgrade that you can perform:
• Upgrading First Oracle Management Service and repository
• Upgrading Additional Oracle Management Services
• Upgrading Management Agent
Upgrading The Oracle Management Service And Repository:
To upgrade multiple Oracle Management Services (OMS), shut down all the OMS's, apply the 10.2.0.5 patch set to any one of the OMSs, so that the associated Management Repository (sysman schema) is also upgraded, then apply the patch set to the rest of the Oracle Management Services.
Note:
This Patch set will upgrade only the Grid Control repository (sysman schema) and not the database, which contains the Grid Control repository.
Be sure that you first upgrade the Oracle Management Service (OMS), and then the Management Agent before upgrading the database that contains the Grid Control repository.
The steps to be taken before upgrading the first OMS are:
• While applying the OMS patch set, leave the repository database and listener instance running.
• Make sure that you follow all the pre-installation tasks before going ahead with upgrade process.
• Shut down all OMS instances attached to the Grid Control repository, from the respective Oracle homes in their respective hosts.
Also stop the Application Server components that run in each Oracle home directory of the Oracle Management Service (OMS).
Note:
If you have multiple Oracle Management Services then you must stop all the OMS instances. When you upgrade the first OMS, the Patch Set also upgrades the Grid Control repository, and since the other OMS instances connect to the same Grid Control repository, they must also be stopped.
Stopping the Management Agents is not mandatory, and as a result, there may be an increase in the number of Agent-related log files. However, this is harmless and can be ignored.
To stop all the Grid Control components on a host, follow these steps:
1. Stop the Oracle Management Service (OMS) by running the following command from the Oracle home directory of the OMS, where $ORACLE_HOME is the Oracle home directory of the Oracle Management Service:
$ORACLE_HOME/bin/emctl stop oms
C:\OracleHomes\oms10g\BIN>emctl stop oms
2. Stop the Application Server Control Console, which is used to manage the Oracle Application Server instance used to deploy the Management Service:
$ORACLE_HOME/bin/emctl stop iasconsole
C:\OracleHomes\oms10g\BIN>emctl stop iasconsole
3. Stop all the application server components, such as Oracle HTTP Server and OracleAS Web Cache by running the following command from the Oracle home directory of the OMS.
$ORACLE_HOME/opmn/bin/opmnctl stopall
C:\OracleHomes\oms10g\opmn\bin>opmnctl stopall
4. Wait for sometime to ensure that all the OPMN processes are stopped and TCP ports are released.
5. Set the Oracle_Home to your Oracle home directory of the Oracle Management Services before applying the patch set.
• Apply the 10.2.0.5 Patch Set either interactively by executing the runInstaller (For Microsoft Windows, setup.exe) or silently by using the response file.
After you have upgraded the first OMS and the Grid Control repository (sysman schema) to version 10.2.0.5, the first OMS starts up automatically and you must then patch the unpatched OMS's to version 10.2.0.5.
Warning:
Do not start an OMS that has not been patched to version 10.2.0.5.
For example: assume there are four version 10.2.0.2 Oracle Management Services labeled OMS A, B, C, and D. In the previous section, all four OMS's are down and you decide to patch OMS B first. After you patch OMS B to version 10.2.0.5, the Enterprise Manager Repository is also patched and OMS B is now up and running. However OMS A, C, and D remain down.
You can then patch OMS A, C, and D in parallel or in serial to version 10.2.0.5 but you must not bring up the unpatched version of those OMS's at any time prior to patching them to version 10.2.0.5.
Upgrading Management Agent:
The Management Agent can be upgraded in two ways - either one host at a time using Oracle Universal Installer, or many hosts at a time using Patch Wizard from Grid Control.
Upgrading Management Agent - One Host At A Time
To upgrade Management Agents, one host at a time, using OUI, follow these steps:
1. Login to the specific host where the Management Agent is running.
2. Change directory to the Oracle home directory for the Management Agent and stop the Management Agent. For cluster Agent, stop the Agent on all cluster nodes.
$ORACLE_HOME/bin/emctl stop agent
C:\OracleHomes\agent10g\BIN>emctl stop agent
3. Ensure that $ORACLE_HOME is set to the Oracle home directory of the Management Agent that is intended for patching.
Set oracle_home = C:\OracleHomes\agent10g
4. Extract the software and then run the ./runInstaller executable from the 3731593/Disk1 subdirectory. (For Microsoft Windows, run setup.exe) and proceed with the upgrade.
Post Installation Tasks:If you had upgraded multiple Oracle Management Services (OMS) by applying the patch set to one of the OMS's first, and then subsequently upgraded the remaining OMS's, the OMS restarts automatically once the upgrade is complete. If the Agents are shutdown prior to the OMS upgrade, they must be restarted manually.
Start all the agents :
1.C:\OracleHomes\agent10g\BIN>emctl status agent
If its not up start the agent with command “ emctl start agent”
2.C:\OracleHomes\oms10g\BIN>emctl status oms
If its not up start the oms with command “ emctl start oms”
3.C:\OracleHomes\oms10g\BIN>emctl status iasconsole
Oracle Enterprise Manager 10g Release 5 Grid Control
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
Oracle 10g Application Server Control is not running.
C:\OracleHomes\oms10g\BIN>emctl start iasconsole
4.C:\OracleHomes\oms10g\opmn\bin>opmnctl startall
opmnctl: starting opmn and all managed processes...
sys password : dba
ias_admin password : dba123
Installation Procedure:
For upgrading to Enterprise Manager Grid Control 10.2.0.x.x to 10.2.0.5, you must manually download from metalink and extract the 10.2.0.5 Patch Set.
Download and extract the Patch Set:.
1. Download the p3731593_102050_<platform name>.zip patch set installation archive to any directory.
2. Enter the following command to unzip and extract the installation files:
$ unzip p3731593_102050_<platform name>.zip
This extracts the files to the "3731593" directory.
NOTE:
The same Patch Set can be used for upgrading Oracle Management Service, Grid Control Repository (sysman schema), and Management Agent.
Upgrading Oracle Management Service:
The pre-installation tasks can be broadly categorized based on the following types of upgrade that you can perform:
• Upgrading First Oracle Management Service and repository
• Upgrading Additional Oracle Management Services
• Upgrading Management Agent
Upgrading The Oracle Management Service And Repository:
To upgrade multiple Oracle Management Services (OMS), shut down all the OMS's, apply the 10.2.0.5 patch set to any one of the OMSs, so that the associated Management Repository (sysman schema) is also upgraded, then apply the patch set to the rest of the Oracle Management Services.
Note:
This Patch set will upgrade only the Grid Control repository (sysman schema) and not the database, which contains the Grid Control repository.
Be sure that you first upgrade the Oracle Management Service (OMS), and then the Management Agent before upgrading the database that contains the Grid Control repository.
The steps to be taken before upgrading the first OMS are:
• While applying the OMS patch set, leave the repository database and listener instance running.
• Make sure that you follow all the pre-installation tasks before going ahead with upgrade process.
• Shut down all OMS instances attached to the Grid Control repository, from the respective Oracle homes in their respective hosts.
Also stop the Application Server components that run in each Oracle home directory of the Oracle Management Service (OMS).
Note:
If you have multiple Oracle Management Services then you must stop all the OMS instances. When you upgrade the first OMS, the Patch Set also upgrades the Grid Control repository, and since the other OMS instances connect to the same Grid Control repository, they must also be stopped.
Stopping the Management Agents is not mandatory, and as a result, there may be an increase in the number of Agent-related log files. However, this is harmless and can be ignored.
To stop all the Grid Control components on a host, follow these steps:
1. Stop the Oracle Management Service (OMS) by running the following command from the Oracle home directory of the OMS, where $ORACLE_HOME is the Oracle home directory of the Oracle Management Service:
$ORACLE_HOME/bin/emctl stop oms
C:\OracleHomes\oms10g\BIN>emctl stop oms
2. Stop the Application Server Control Console, which is used to manage the Oracle Application Server instance used to deploy the Management Service:
$ORACLE_HOME/bin/emctl stop iasconsole
C:\OracleHomes\oms10g\BIN>emctl stop iasconsole
3. Stop all the application server components, such as Oracle HTTP Server and OracleAS Web Cache by running the following command from the Oracle home directory of the OMS.
$ORACLE_HOME/opmn/bin/opmnctl stopall
C:\OracleHomes\oms10g\opmn\bin>opmnctl stopall
4. Wait for sometime to ensure that all the OPMN processes are stopped and TCP ports are released.
5. Set the Oracle_Home to your Oracle home directory of the Oracle Management Services before applying the patch set.
• Apply the 10.2.0.5 Patch Set either interactively by executing the runInstaller (For Microsoft Windows, setup.exe) or silently by using the response file.
After you have upgraded the first OMS and the Grid Control repository (sysman schema) to version 10.2.0.5, the first OMS starts up automatically and you must then patch the unpatched OMS's to version 10.2.0.5.
Warning:
Do not start an OMS that has not been patched to version 10.2.0.5.
For example: assume there are four version 10.2.0.2 Oracle Management Services labeled OMS A, B, C, and D. In the previous section, all four OMS's are down and you decide to patch OMS B first. After you patch OMS B to version 10.2.0.5, the Enterprise Manager Repository is also patched and OMS B is now up and running. However OMS A, C, and D remain down.
You can then patch OMS A, C, and D in parallel or in serial to version 10.2.0.5 but you must not bring up the unpatched version of those OMS's at any time prior to patching them to version 10.2.0.5.
Upgrading Management Agent:
The Management Agent can be upgraded in two ways - either one host at a time using Oracle Universal Installer, or many hosts at a time using Patch Wizard from Grid Control.
Upgrading Management Agent - One Host At A Time
To upgrade Management Agents, one host at a time, using OUI, follow these steps:
1. Login to the specific host where the Management Agent is running.
2. Change directory to the Oracle home directory for the Management Agent and stop the Management Agent. For cluster Agent, stop the Agent on all cluster nodes.
$ORACLE_HOME/bin/emctl stop agent
C:\OracleHomes\agent10g\BIN>emctl stop agent
3. Ensure that $ORACLE_HOME is set to the Oracle home directory of the Management Agent that is intended for patching.
Set oracle_home = C:\OracleHomes\agent10g
4. Extract the software and then run the ./runInstaller executable from the 3731593/Disk1 subdirectory. (For Microsoft Windows, run setup.exe) and proceed with the upgrade.
Post Installation Tasks:If you had upgraded multiple Oracle Management Services (OMS) by applying the patch set to one of the OMS's first, and then subsequently upgraded the remaining OMS's, the OMS restarts automatically once the upgrade is complete. If the Agents are shutdown prior to the OMS upgrade, they must be restarted manually.
Start all the agents :
1.C:\OracleHomes\agent10g\BIN>emctl status agent
If its not up start the agent with command “ emctl start agent”
2.C:\OracleHomes\oms10g\BIN>emctl status oms
If its not up start the oms with command “ emctl start oms”
3.C:\OracleHomes\oms10g\BIN>emctl status iasconsole
Oracle Enterprise Manager 10g Release 5 Grid Control
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
Oracle 10g Application Server Control is not running.
C:\OracleHomes\oms10g\BIN>emctl start iasconsole
4.C:\OracleHomes\oms10g\opmn\bin>opmnctl startall
opmnctl: starting opmn and all managed processes...
sys password : dba
ias_admin password : dba123
No comments:
Post a Comment