0% found this document useful (0 votes)
12 views5 pages

N K N K: Knowledge Browse

Information in this document applies to any platform. Goal Installing on Windows Server 2008 or Windows Vista requires the use of an existing database. The default database install for OEM grid (10.1.0.4) is not supported on these platforms.

Uploaded by

Arjun Rajagopal
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
12 views5 pages

N K N K: Knowledge Browse

Information in this document applies to any platform. Goal Installing on Windows Server 2008 or Windows Vista requires the use of an existing database. The default database install for OEM grid (10.1.0.4) is not supported on these platforms.

Uploaded by

Arjun Rajagopal
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Document 951974.

1 Page 1 of 5

([Link]@[Link])

Home Knowledge Configs and Projects Certifications


Browse | Subscriptions | Authoring Wizard | Documents In Progress | Query By Attribute
Search
By n Keyword
j
k
l
m n ID
i
j
k
l
m 951974.1 Filter All Product Lines

Knowledge > Browse > Document Display

Next Steps
Install [Link] OEM on Microsoft Windows Server 2008
and Microsoft Windows Vista (Doc ID 951974.1)
Modified 13-OCT-2009 Type HOWTO Document Bookmarked

In this Document Add Comment


Goal
View Document Statistics
Solution
References
Help Us Help You

@ Created from <SR7738461.993> with ODM Rate this document

j Excellent
k
l
m
n
Applies to:
j Good
k
l
m
n

Enterprise Manager Grid Control - Version: [Link].1


j Poor
k
l
m
n
Information in this document applies to any platform. Did this resolve the problem?

j Yes
k
l
m
n
Goal j No
k
l
m
n
j Just Browsing
k
l
m
n
Installing on Windows Server 2008 or Windows Vista requires the use of an
Was this easily located?
existing database. The default database install for OEM grid ([Link]) is not
supported on these platforms. It also requires the use of the new OUI (Oracle
Universal Installer), patch 6640752, to successfully install on these platforms.
j Very Easy
k
l
m
n
j Somewhat Easy
k
l
m
n
This note is the step by step process required to successfully install Enterprise j Not Easy
k
l
m
n
Manager Grid Control using an existing database on Microsoft Windows 2008
and Microsoft Windows Vista.

Solution

Refer to the Installation guide for complete details.


Oracle® Enterprise Manager Grid Control Installation and Configuration
Guide
10g Release 5 ([Link].0)
Part Number E10953-11

1. Install a [Link] or higher database


2. Create a database 'emrep' for the grid control repository.
Make sure that it has the following initialization parameters

job_queue_processes = 10
db_block_size = 8192
timed_statistics = TRUE
open_cursors = 300

[Link] 3/31/2010
Document 951974.1 Page 2 of 5

session_cached_cursors = 200
aq_tm_processes =1
compatible = <currently installed Oracle Database release>
(default)
undo_management = AUTO
undo_retention = 10800
undo_tablespace = <any acceptable name>
processes = 150
log_buffer = 1048576
statistics_level = TYPICAL (Note that this value is specific only to
Enterprise Manager 10g Repository Database release and later.)
TEMP space (Tablespace) = 50 MB (extending to 100 MB)

pga_aggregate_target = 256 MB
Redo logs = 100 MB
db_cache_size = 384 MB (or more)
shared_pool_size = 128 MB
sga_target = 512 MB (or more)

3. Remove the DBConsole from the database

<oracle_home>\bin\emca -deconfig dbcontrol db -repos drop

4. Download patch# 6640752 for Microsoft Windows (32-Bit) from My Oracle


Support. You can access My Oracle Support at:
[Link]

5. Extract the contents of the downloaded patch to a location on your system.


For example: C:\Patch_Download

6. Download the base release, that is, Enterprise Manager 10g Grid Control
Release 2 ([Link].0) for Microsoft Windows.

7. Extract the contents of the downloaded base release to a location on your


system.
For example, C:\Base_Download

8. Ensure that your existing database is a database that is supported on


Microsoft Windows Vista or Microsoft Windows 2008. For example, Oracle
Database 10g Release 2 ([Link] or [Link]).

9. Edit the response file and make changes as described in this step. Make the
following changes in the response file.
The response file is available at:
C:\Base_Download\Disk1\install\response\[Link]

Make the following changes:

a. For the FROM_LOCATION parameter, specify the full path to the


[Link] file.
For example:

FROM_LOCATION="C:\Base_Download\Disk1\oms\Disk1
\stage\[Link]"

b. For the ORACLE_HOME parameter, specify the full path to the Oracle
home directory of the OMS.
For example:

[Link] 3/31/2010
Document 951974.1 Page 3 of 5

ORACLE_HOME="C:\OH102020\oms10g"

c. For the ORACLE_HOME_NAME parameter, specify the Oracle home


name for OMS.
For example:

ORACLE_HOME_NAME="oms10g2"

d. For the s_agentHome parameter, specify the full path to the Oracle home
directory of the Management Agent.
For example:

s_agentHome="C:\OH102020\agent10g"

e. For the s_agentHomeName parameter, specify the home name for


Management Agent.
For example:

s_agentHomeName="agent10g2"

Note: Ensure that the Oracle home location and the name you specify are
not already existing.

10. Run the [Link] file:

C:\Patch_Download\cd\Disk1\install\[Link] -ignoreDiskLabel -
responseFile C:\Base_Download\Disk1\install\response\[Link]

11. If the Management Agent does not restart, and if the value of
agentTZRegion in the [Link] file is GMT, then reset the time zone on
the host where the Management Agent is installed using the following command.
Here, Oracle_Home is the Oracle home directory of the Management Agent.

<Oracle_Home>\BIN>emctl resetTZ agent

12. Patch OMS to [Link].0 release.


For patching instructions, see the Release Notes provided with the [Link]
patch set.
Patch 3731593
<stage directory>\3731593\Disk1\[Link]

A Common failure during the upgrade is on the OC4J Configuration


Assistant.

To fix this failure,

[Link] 3/31/2010
Document 951974.1 Page 4 of 5

Note 788749.1 Problem: [Link].0 Upgrade on Windows 2003 Server Fails


for [Link]

Solution
1) Keep the installer session active at the failure point.

2) Navigate to .../oms10g/Apache/Apache/conf/ and archive


the existing [Link] file (verify it is only 2kB in size,
exemplary of the problem).

3) Copy the [Link] (should be about 7kb in size)


to [Link].

4) Select "Retry" in the failed installer session.

5) Watch the [Link].0 patchset installation complete


successfully.

13. Patch Management Agent to [Link].0 release.


For patching instructions, see the Release Notes provided with the [Link]
patch set.
Patch 3731593
<stage directory>\3731593\Disk1\[Link]

References

NOTE:788749.1 - Problem: [Link].0 Upgrade on Windows 2003 Server Fails


for [Link]
PATCH:6640752 - OUI CD PLACE HOLDER ON ARU FOR 10205
PATCH:3731593 - PATCHSETS FOR ENTERPRISE MANAGER GRID
CONTROL

▼Related

Products

 Enterprise Management > Enterprise Manager Consoles, Packs, and


Plugins > Enterprise Manager Grid Control > Enterprise Manager Grid
Control > Enterprise Manager Core Framework Components > Agent
Process Control (Start, Stop, Status)
Knowledge Categories

 GCS > ST > EM > Installation > Generic - Installation (Primary)


Keywords

 [Link]
 GRID CONTROL

▼Document Attributes

Author [Link]@[Link] Status REVIEW_READY

[Link] 3/31/2010
Document 951974.1 Page 5 of 5

(EXTERNAL)
Owner [Link]@[Link] Publisher
Content
Alias TEXT/X-HTML
Type
Visibility EXTERNAL Priority 3
Created Created
[Link]@[Link] 13-OCT-2009
By Date
Modified
[Link]@[Link] Modified 13-OCT-2009
By
Review
Reviewer
Date
Source AWIZ 2-5797662

Favorites Profile Help Sign Out


Copyright (c) 2008, Oracle Corporation. All Rights Reserved. Legal Notices and Terms of Use | Privacy Statement

[Link] 3/31/2010

You might also like