Intalling OEM 10g R4 on Windows

This guide should work on most windows platform (XP, 2000, 2003 and 2008).

This document outlines installation of OEM 10g on Windows including all the errors encountered during installation and fixes to these errors and problems.

Server name: svr444

Today: 27-Jun-08

Doing a fresh Enterprise Manager 10g Release 2 Grid Control installation and upgrading it to

Disclaimer: Apply to a TEST environment first. Use on production systems is at DBAs own risk.

  • OEM 10g install with create new database option:

I did several attempts to install OEM 10g with create new database option, and they all failed with errors. OEM GRID 10.2 Installation with option new database runs for 30 minutes and during Database Configuration Assistant and data file copy gave me the following error:
ORA-12560: TNS: protocol adapter error
And other errors in inventory logs such as:
sysmanPassword 05a517cbfb62afd89d74b878620219f43c -dbsnmpPassword xxx -emConfiguration NONE -datafileJarLocation D:\Oracle\OEm10.2\db10g\assistants\dbca\templa
tes -datafileDestination D:\Oracle\OEM10.2\oradata -responseFile NO_VALUE -chara
cterset US7ASCII -obfuscatedPasswords true -sampleSchema false
Since I was unable to get a clean installation using the new database option of OEM 10g install and Oracle support was unable to provide a viable solution, therefore I decided to first install and create a new database and then install OEM 10g with existing database option. The steps are outlined in this document.

  • Database 11g and OEM 10g certification:

Installation of OEM against an 11g database tells me that the db version is invalid and should be or According to Note 412431.1 GRID 10.2 is certified with database 11g But you must first install GRID 10.2 on a 10g database, upgrade 10.2 GRID to then upgrade the repository database from 10g to 11g.

  • OEM 10g and Windows 2008 certification:
  • As of 02/07/2008 when this document was first written, according to Note 412431.1 OEM 10g Grid is not certified on Windows server 2008. But as outlined in this document, it was successfully installed on a Windows 2008.
  • OEM 10g and IPV6:
  • IPV6: In windows 2008 c:\windows\system32\drivers\etc\hosts contains ::1 for localhost I google this ::1 and it seems to be related to IPV6. Since we are not using IPV6 then I go ahead and remove ::1 so not to confuse OEM which possibly expects when it pings localhost rather than ::1

Quick overview of steps:

1) Install Database 10g R2 and apply latest patch.


This is 10.2

2) Upgrading Repository Database to

3) Install OEM 10g R2 with existing database option.

4) Upgrade Oracle Enterprise Manager to 10g R4 (Release 4).

The upgrade process then upgrades the Oracle Management Service (OMS), Oracle Management Repository and the Management Agent on the same host as the OMS to the latest Enterprise Manager 10g release 4 version.

Detail installation:

1) Install Database 10g R2 ( and apply latest patch.


Right click on setup.exe and run as admin.

I set the SID to oemrep and home to D:\Oracle\db10g

I set password to myoem10g

All pre-checked passed.

It run for 20 minutes all success:

Enterprise Manager Database Control URL:



I connect to db and increase sga size and some other parameters:

alter system set sga_MAX_size=850M scope=spfile;

alter system set sga_target=800M scope=spfile;

Also the following which was required by OEM 10g install on test runs:

alter system set aq_tm_processes=5 scope=spfile;

alter system set session_cached_cursors=300 scope=spfile;

Gracefull bounce of db.

Bounce svr444

2) Upgrading Repository Database to

The patch set is available on OracleMetaLink. Search for patch 6810189.

Graceful shutdown of db from sql prompt.

Shutdown listner, db and all other oracle services.

From command prompt unzip as the windows unzip somehow is unable to unzip this file.

Then start universal installer by running setup.exe as admin from where you unziped the patch and point the installer to the database home D:\Oracle\db10g.

àDatabase patch run successfully, it run for 10 minutes.

Here I started the db but it failed to start saying:

Instance terminated.

Log file:

ORA-00704: bootstrap process failure

ORA-39700: database must be opened with UPGRADE option

àThis is because after the db upgrade I need to start the db in upgrade mode

After upgrade to is completed:

sqlplus /nolog



Set the CLUSTER_DATABASE initialization parameter to FALSE:


Shutdown the database:


Exit and sqlplus /nolog

Connect /as sysdba

Enter the following SQL*Plus commands:


SQL> SPOOL patch.log

SQL> @?/rdbms/admin/catupgrd.sql

–>This runs for 40 minutes.


Review the patch.log file for errors and inspect the list of components that is displayed at the end of catupgrd.sql script.

This list provides the version and status of each SERVER component in the database.

If necessary, rerun the catupgrd.sql script after correcting any problems.

àLooking at patch.log for oemrep every thing looks good no errors.

Restart the database. A graceful bounce.

Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.

SQL> @?/rdbms/admin/utlrp.sql

àThis run for over 3 minutes. No errors.

àThis is the end of database upgrade.

3) Install OEM 10g R2 with existing database option.

On my first test on installing OEM 10.2 I got an error saying:

dbms_shared_pool package is not executed on the existing database

This is because DBMS_SHARED_POOL package has not been installed at the time of the database creation.

So I go ahead and do the fix now.

Connect as sysdba and execute the following:



àfew seconds. No errors.

Installing OEM 10g R2 with existing db:

Remove any reference to the database home from the envirment variables.

On win 2008: StartàRight click Computer àAdvanced system settings àAdvanced tab àEnvironment variables. And bounce.

Start setup.exec: right click and run as admin.

OEM home is D:\Oracle\OEM10.2

àAll pre-check successfully passed.

Database host name

Port 1521 SID oemrep

Click refill tablespace locations and Point the datafiles to D:\ORACLE\ORADATA\OEMREP

It tells you that sysman already exists, click continue and installation will drop and recreat the sysman schema. Click continue for the dispatcher message as well.

Then the installation says that I need to set job_queue_processes to a value greater that 10:

Start àGo to the db10g àAddplication dev àSQLPLUS and logon as system and run:

alter system set job_queue_processes= 20 scope=both;

Then click continue to continue install.

Point email to

SMTP mail server is

Leave metalink and configure proxy un-checked.

Set all passwords to myoem10g

check secure communications for all agents.

Installation run for 30 minutes and failed during OMS configuration assistance, detail error is:

Output generated from configuration assistant “OMS Configuration”:

Command = oracle.sysman.emcp.oms.OmsPlugIn -configureOms

Operation Stopping OPMN Processes is in progress.

Operation EM Deploying is in progress.

Operation Creating OMS Respository is in progress.

Configuration assistant “OMS Configuration” failed.

Looking at Inventory log file which is C:\Program Files\Oracle\Inventory\logs\installActions2008-07-01_04-44-15-PM.log

and which displays the following when I search for string “Operation Creating OMS Respository is in progress” detail erros from this log is:

Command = oracle.sysman.emcp.oms.OmsPlugIn has failed Exception : java.lang.Exception:

PerformSecureCommand:drain:Exception=The pipe is being closed

INFO: Configuration assistant “OMS Configuration” failed

Lokking at log file emca_repos_drop21_19_45.log located in D:\Oracle\OEM10.2\oms10g\cfgtoollogs is showing:

[30-06-2008 14:19:46] Enter SYS user’s password :

[30-06-2008 14:19:46]

[30-06-2008 14:19:46] Getting temporary tablespace from database…

[30-06-2008 14:19:46] Found temporary tablespace: TEMP

[30-06-2008 14:19:46] Checking SYS Credentials …

[30-06-2008 14:19:46] Failed

[30-06-2008 14:19:46] SYS credentials or connect string is invalid.

Investigating this problem: I connected to the database from the db10g home:

conn sys/myoem10g but I got the following error:

ORA-28009 connection as SYS should be as SYSDBA or SYSOPER

To fix this problem I did the following:

alter system set remote_login_passwordfile=shared scope=spfile;

alter system set O7_DICTIONARY_ACCESSIBILITY=true scope=spfile;

cd D:\Oracle\db10\bin

orapwd file=D:\Oracle\db10g\dbs\orapwoemrep password=myoem10g entries=5

and bounce the database.

Now from the sql prompt of db10g home I am able to connect sys/password without getting the ORA-28009

I also inserted the following line into sqlnet.ora file in $ORACLE_HOME/network/admin of the 10g db:


Going back to the OUI install session, once I click retry the OMS configuration fails again.

In an effort to get a clean install of OS and Agents I decided to abort, un-install OEM again remove the files from D:\Oracle\OEM10.2 and any registry entries referring to D:\Oracle\OEM10.2 , I also make sure that my environment variable PATH this time does include the 10g database as seen here:


Then attepmt the installation again and this time I do not click on refill tablespace locations and leave it to point to the OMS location: to D:\Oracle\OEM10.2\oms10g\oradata

Installation run for 30 minutes and gave the following error while on OMS configuration assistant.

This is the detail error: Inventory log file C:\Program Files\Oracle\Inventory\logs\installActions2008-07-01_04-44-15-PM.log says:

Operation Creating OMS Respository is in progress.

Command = oracle.sysman.emcp.oms.OmsPlugIn has failed

Exception : java.lang.Exception:

RepManager Create Repository Error = 12. Please check the log file at D:\Oracle\OEM10.2\oms10g\sysman\log\emca_repos_create18_27_24.log

INFO: Configuration assistant “OMS Configuration” failed

Log file: D:\Oracle\OEM10.2\oms10g\sysman\log\emca_repos_create18_27_24.log is showing the following:



ERROR at line 1:

ORA-01119: error in creating database file


ORA-27040: file create error, unable to create file

OSD-04002: unable to open file

O/S-Error: (OS 3) The system cannot find the path specified.

ORA-06512: at line 44

[01-07-2008 11:27:25] Failed.

[01-07-2008 11:27:25] Repository Creation failed. Failed to create Repos User.

This looks like a permission problem. To fix this I created oradata in D:\Oracle\OEM10.2\oms10g and clicked on Retry and installation run successfully for the OMS configuration assistant.

After OMS configuration assistance is successfully completed, Agent configuration assistant stops and points to the following error:

Log file: installActions2008-07-01_06-19-59-PM.log located in C:\Program Files\Oracle\Inventory\logs is showing:

Performing targets discovery and agent configuration

Command = oracle.sysman.emcp.agent.AgentPlugIn has failed Exception : java.lang.Exception: 6

INFO: Configuration assistant “Agent Configuration Assistant” failed

Log file: CfmLogger_2008-07-01_06-21-19-PM.log located in D:\Oracle\OEM10.2\agent10g\cfgtoollogs\cfgfw is showing the following:

ORA-20999: CREATE DEFAULT WEBSITE FAILED : ORA-01403: no data found


Metalink search for “Command = oracle.sysman.emcp.agent.AgentPlugIn has failed Exception” : and I found Note: 419886.1 which say to do as follow:

1. Backup the following files:



2. Then run “$AGENT_HOME/bin/agentca -f” command.

àThis run for 15 minutes and reported that it failed.

I click on Retry of the Agent configuration Assistant, it run for 15 minutest and it failed

with the same error. I google for ORA-20999: CREATE DEFAULT WEBSITE FAILED and in oracle forums some discussions suggested that this might be related to daytime saving and timezone.

Also last time I had existing agents starting to fail, the problem also was due to timezone setting in the environment. For now I decided to just click on next on my open installation and ignore the Agent config assistant failure and fix it later by re-installing agents after the OEM upgrade; which would fix any timezone and daytime saving related problem, as seen later in this document.

To get the agents to install successfully here is what I will do:

A) Un-install agents. And bounce.

Right click 10g setup and run as admin and un-install agents.

B) Apply OEM 10g R4 patch which should include timezone daytime saving patches.

Install Oracle Enterprise Manager 10g R4 (Release 4) patch.

Stop OMS services, or any services pointing to the OMS home.

setup.exe from where you unzip the patch fails to start.

start universal installer from the startàOMS and point it to stage products.xml of the patch


Point the installation to the OMS10g home (D:\Oracle\OEM10.2\oms10g). Password: myoem10g

Upgrade of OEM run for 30 minutes with a complete success message.

C) Install agents on OMS server.

Bounce the server. Then from OEM 10g staging area install with option additional agents.

From D:\Downlload\Oracle\OEM10g\OEM_10.2\B30800-01 right click on setup.exe and run as admin.

Check Additional management agents. Make sure D:\Oracle\OEM10.2 does not contain a folder agent10g and then point the install to D:\Oracle\OEM10.2

All prechecks were success.

Management server is

Management service port is the default 4889

Password is myoem10g

Installation run for 15 minuets no errors.

D) Upgrade agents on OMS server.

Bounce the server.

Install Oracle Enterprise Manager 10g R4 (Release 4).

Make sure agents are down.

setup.exe from where you unzip the patch fails to start.

start universal installer from the startàAgent10 and point it to stage products.xml of the patch


Point the installation to the agent10g home (D:\Oracle\OEM10.2\agent10g).

Upgrade of agent run for 5 minutes with a complete success message.

Bounce server.

After server restarted, from windows services I can see that Agent10g service does not start.

Log agabend.log located in D:\Oracle\OEM10.2\agent10g\sysman\log which shows the following error:

The agentTZRegion value in D:\Oracle\OEM10.2\agent10g/sysman/config/ is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.

If you modified the timezone setting in the environment, please stop the agent and exectute ‘emctl resetTZ agent’ and also execute the script mgmt_target.set_agent_tzrgn(<agent_name>, <new_tz_rgn>) to get the value propagated to repository.

Here is what to do to fix this:

From command line run:

First stop agents if they are running.


emctl stop agent

emctl status agent

emctl resetTZ agent

This should tell you that “Successfully updated


And also it would tell you to run mgmt_target.set_agent_tzrgn as sysman:

Login as the em repository user and run the script:

exec mgmt_target.set_agent_tzrgn(’′,’America/Los_Angeles’) and commit the changes

Then from Windows services start agent services

àAgent might not start but that is ok for now.

from Agent_home\bin run:

emctl status agent

and make sure the agent name on the following command matches the port listed here.

Logon to db as sysman then execute the following:

exec mgmt_target.set_agent_tzrgn(’′,’America/Los_Angeles’);


Bounce server.

Once server started up I can see from Windows services that Oracleagent10gAgent started successfully.

Done OMS and Agents are now installed on svr444 and running. Next step is to install agents on target systems.

What we do:

idbasolutions makes software that allows easy navigation into database objects, sessions, storage, wait conditions, memory structures and more, all with drill-down sub-windows in a cascading and intuitive fashion.

If you like reading our papers, please take a moment and navigate to Product Demo and lookup each modules presentations. Or navigate to Free Version Tab and download a demo copy of our software for you to keep and use at no charge. To buy please navigate to Buy tab to purchase a full copy.

Support documents such as how to install, system and database requirements and so on are available in Support tab.

Quick links to GRID and Repository db:

GRID control:


Database repository:



dba isql:

Latest Blog Items


Thank you for your interest in idbasolutions.

Contact us using this email: