Applying Patchset and upgrading Grid Control Management Agent
Applying Patchset and Upgrading Grid Control Management
Agent
This OBE explains how Enterprise Manager Grid Control can
be used for applying patchsets to Grid Control Management Agents of a given
release or upgrade them from one major release version to another. This OBE
also highlights the differences in the process of application of the patchset
and upgrading of an agent.
Approximately 1 hour
This OBE covers the following topics:
 Place
the cursor over this icon to load and view all the screenshots for this tutorial.
The screenshots will not reflect the specific environment
you are using. They are provided to give you an idea of where to locate specific
functionality in the Oracle Enterprise Manager 10g Grid Control console.
Enterprise Manager Grid Control enables you to either
perform mass deployment of patchsets or upgrade Oracle Management Agents.
Oracle releases patchsets on a regular
interval over a major release of a product. For Example: For 10.2.0.1 Agent
installation you can apply the latest patchsets(10.2.0.3 or 10.2.0.4).
Grid Control Management Agent upgrades are performed
when a new version of Management Agent is available. Enterprise Manager Grid
Control enables you to upgrade Grid Control Management Agents from one version
to another version. For Example: for a 10.1.0.x agent installation you might
want to upgrade it to 10.2.0.x.
| |
|
 Use
Patch Agent wizard to apply patchsets to Grid Control Management Agents
of similar series. For Example: Apply patchsets to update Management Agents
from version 10.1.0.x to 10.1.0.4 or from version 10.2.0.x to 10.2.0.4.
|
|
Use
Agent Deploy application for upgrading Grid Control Management Agents
from one version to another version. For Example: Use Agent Deploy application
to upgrade Management Agent of version 10.1.0.x to 10.2.0.x
|
|
Applying
patchset is an in-place operation that means that the oracle home location
will not change after applying the patchsets. This process updates oracle
home with the latest binaries and files from the patchset.
|
|
Agent
Deploy application is an out-of-place operation where the upgraded agent
resides in a new oracle home location.
|
In this lesson you will see how to apply a patchset using
the Patch Agent wizard and upgrade a Grid Control Management Agent using the
Agent Deploy application.
Back to Topic List
You can use the Patch Agent option
of the Grid Control to update an existing Oracle Management Agent. The Grid
Control simplifies the process of patching Oracle Management Agent with these
features:
Critical
Patch Advisories: This page lists all the critical software patch advisories
for Oracle products. It includes their corresponding Impact areas, a brief description
of each advisory, the number of Affected Hosts and Oracle homes for each advisory.
Critical Patch Advisories also provides support for Remedies. You can select
an advisory and view the calculated remedies from the context of that Advisory,
as well as the affected Oracle homes.
Online
Patching: This feature allows you to connect to OracleMetaLink via Enterprise
Manager, perform a search and download the required patches/patchsets, and apply.
Offline
Patching: This feature allows you to perform all the patching activities from
the Patch Cache. That is, even when the OMS is not connected to OracleMetaLink
via Internet, you can perform a search, download and apply a patch/patchset.
See View/Upload Patch, and Offline Patching Settings for more information.
Note: Grid Control also let you search for an
Oracle patch (or patchset) that interests you at the OracleMetaLink Web site.
To enable Grid Control to search for patches at OracleMetaLink and to provide
critical patch advisories, you must specify valid OracleMetaLink credentials.
Perform the following steps to use the Patch Wizard to update
the management agent to 10.2.0.3.0:
|
1.
|
Open the browser and enter the
following URL:
http://<management
service hostname>.<domain>:<port>/em/
The default port value on a clean machine is 7777. However,
if there are other instances running on the machine, then the port may
be different.
The login page will be displayed. Enter the User Name
and Password, and then click the Login button.
|
| 2. |
Before you start the Patch Wizard confirm that you have setup the Patching
and Metalink Settings correctly. Click the Setup link.
|
| 3. |
Click the Patching Setup link from the left navigation bar.
|
|
4.
|
Make sure that the MetaLink credentials are properly setup. Once you
confirm it, click the Deployments tab to access the Patch Wizard.
|
| 5. |
Click the Patch Agent link under the Patching section.
|
| 6. |
Specify the Patch Number as 3822442,
select Linux x86 from the Platform drop-down list and click the
Search button.
Note: You can use Deployment Procedures to patch any Oracle software
except Oracle Management Agent. To patch Oracle Management Agent,
use patch wizard approach by clicking the Patch Agent link.
|
| 7. |
Select the patchset that is for the 10.2.0.3 release and click the Next
button.
|
| 8. |
In this step the Patch Wizard will automatically detect all the existing
10.2.0.1 agents and list them in the Available Targets section. Select
the agent that you want to patch with the latest patchset and click the
Move button to move it to the Selected Targets section.
|
| 9. |
Click the Next button.
|
| 10. |
Preferred credentials simplify access to managed targets by storing target
login credentials in the Management Repository. With preferred credentials
set, users can access an Enterprise Manager target that recognizes those
credentials without being prompted to log into the target. Use the "Preferences"
Global link on right hand top of the page to set preferred credentials
for any enterprise manager target.
If the preferred credentials have been set for the agent that is being
patched then you can choose "Use Oracle Home Preferred Credentials"
option button. For this exercise Preferred Credentials for this agent
are not set so keep the "Override Oracle Home Preferred Credentials"
option button selected and specify the host credentials. Click the Next
button.
|
| 11. |
Make sure that the Apply option button is selected and click the Next
button.
Note: You can use the Provide custom patching script option button
to configure Oracle Configuration Manager (OCM). If you select it you
will have to provide the necessary values to the different parameters
in the script.
|
| 12. |
Schedule the patch job for immediate execution and click the Next
button.
|
| 13. |
Review your settings and click the Finish button.
|
| 14. |
The job is submitted. You can click the View Job button to see the progress
of the job execution.
|
| 15. |
You can track the job execution from the job execution page.
|
| 16. |
When the Patch job is successfully completed you should see the status
as Succeeded.
Note: You can access all the jobs that are submitted from the
Grid Console from the Jobs tab.
|
Back to Topic List
For a major upgrade, use Agent Deploy application. Agent Deploy
is a J2EE application that is used for mass deployment of Oracle Management
Agents. The Upgrade Agent option in this application will help you upgrade an
existing Management Agent installation to a release 10.2 Management Agent.
Before upgrading an Oracle Management Agent version
10.1.x.x to the latest version available you need to first assess the requirements.
You need to download the required Agent Upgrade kits from the following location:
http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html
Ensure that you download the right kit based on the Operating System and the
hardware of the host where the Oracle Management Agent is deployed. Perform
the following steps to upgrade an agent on a host:
| 1. |
Before upgrading Oracle Management Agent, you need to check its version.
Click Setup to check the version of the Oracle Management Agent.
|
| 2. |
Click the Agents sub tabbed page.
|
| 3. |
The current version of the Oracle Management Agent is displayed. Since
the current version of the Oracle Management Agent is 10.1.x.x, you need
to use the Upgrade Agent option. Click the Deployments tabbed page
to upgrade the agent.
|
| 4. |
Click Install Agent link in the Agent Installation section.
|
| 5. |
The Install Agent page is displayed. Click the Upgrade Agent link.
Note: This option helps you upgrade from one release to another,
and not patch a particular release. So if you want to apply a patch set
on a 10.2.0.2 Management Agent and make it 10.2.0.3 Management Agent,
then do not use this option; use the Patch Agent wizard in the Deployments
page.
|
| 6. |
The Agent Upgrade: Installation Details page is displayed. In the Existing
Agent Home field under the Source Agent Information section, enter
the location of the Agent Home of the host that you want upgrade.
Note: You need to enter the current location
of the Agent Home that you want to upgrade. This is not the same as the
Oracle Management Server (OMS) Agent Home location.
|
| 7. |
In the Version section, select the version from the dropdown list
to which you want the Agent to be upgraded.
|
| 8. |
In the Provide Host List text box under the Hosts section, specify
all the hosts (hostnames or IP addresses) on which you want to upgrade
the Agent. Alternatively, you click the Get Host Names From File
button to select the file that contains a list of all the required hostnames.
If you have more than one host on which you want to upgrade the Agent,
you can use a comma (,), or a white space as a separator.
|
| 9. |
In the OS Credential section, specify the appropriate operating
system user credentials. Select Run root.sh option if you want
to execute this script. The user must have sudo user privileges to run
the root.sh script.
|
| 10. |
In the Destination section, specify the location where you want
to install the upgraded Agent Home. Enterprise Manager Grid Control creates
a new sub-directory for the Agent Home in the specified location.
Note: A new Agent Home is created for the Upgrade
Agent task in your host.
|
| 11. |
In the Additional Parameters text box, enter any additional parameters
that you want to pass during installation.
|
| 12. |
In the Management Server Security section, specify the Management
Server Registration Password for secure communications between the
Agent and OMS.
|
| 13. |
In the Additional Scripts section, you may enter any pre-installation
or post-installation scripts. You can select Run as Super User
option if you want to run these scripts as root.
Note: The pre-installation and post-installation scripts must be
available on all the hosts. These files are not copied onto the hosts
from the source software location during installation.
Click Continue to upgrade the Oracle Management Agent.
|
| 14. |
In the New Agent Installation: Oracle Configuration Manager Details
Page, you need to specify the License Agreement option, the Registration
and the Connection Details.
You can either accept or decline the Oracle Configuration Manager License
Agreement. If you decline the license agreement, Oracle Configuration
Manager will be installed but not configured.
The Registration section enables you to link your service requests with
the appropriate configuration information for a quicker support. By default,
all the fields are disabled. To enable these fields and specify the proxy
server settings, check the Enable Oracle Configuration Manager option.
Enter the following details:
Customer Identification
Number (CSI): Enter the Customer Identification Number that uniquely identifies
your organization.
Metalink Account
Username: Enter the username of your Oracle Metalink Account. This is
used to identify the configuration data that is being uploaded to Oracle.
Country Code: Select
your country code from the drop down list.
Under the Connection Details, if you are using a proxy server to access
the Internet, you must provide the proxy server configuration details
here. By default, all the fields in this section are disabled. To enable
these fields and specify the proxy server settings, check the Enable Proxy
option. Specify the following information:
Proxy Server and
Proxy Port: Enter the host name and port number of the proxy server. These
fields are mandatory.
Proxy Username and
Proxy Password: If the proxy server requires authentication, you must
specify the credentials in the Proxy Username and Proxy Password fields.
Select Accept License Agreement option.
|
| 15. |
Click Continue.
|
| 16. |
This page displays the Agent Upgrade is in progress.
|
| 17. |
Once the agent is successfully upgraded, the status page is displayed.
The Session Details section provides a link to the pre-requisite details
page and the installation details page. Click the Status Home button
to view the details.
|
| 18. |
The Status page displays that the Agent was successfully upgraded.
|
Back to Topic List
In this lesson, you learned how to:
Back to Topic List
Back to Topic List
Place the cursor over this icon to hide all screenshots.
|
Bookmark
