11G OCM Patch OEM 10.2.0.5 (5)


The saga of configuring OEM 10.2.0.5 continues on from 11G OCM Patch OEM 10.2.0.5 (4) in which the OMS (Oracle Management Server) can not connect to the OMR (Oracle Management Repository).

Investigation

OMR (Oracle Management Repository)

The bottom layer in the OEM hierarchy is the OMR (Oracle Management Repository).

The OMR (Oracle Management Repository) is in the repos database on gridctrl. I checked the connectivity to the OMR and the existence of the OMR as follows:

[oracle@gridctrl ~]$ sqlplus sysman

SQL*Plus: Release 11.1.0.7.0 - Production on Fri Jan 1 06:48:38 2010

Copyright (c) 1982, 2008, Oracle.  All rights reserved.

Enter password: 

Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning option

SQL> select count(*) from user_objects;

  COUNT(*)
----------
      5419

SQL> connect sysman@oem
Enter password: 
Connected.
SQL> select instance_name from v$instance;

INSTANCE_NAME
----------------
repos

SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning option

Both the TCP and Bequeath protocols are working from where the OMS (Oracle Management Server) is set up. The SYSMAN user account is open and has 5,419 objects. This is a very basic check.

I can assume the OMR is somewhat correct and active.

OMS (Oracle Management Server)

The next layer in the OEM hierarchy is the OMS (Oracle Management Server).

Searching Oracle Support for the error messages found in 11G OCM Patch OEM 10.2.0.5 (4), I find an article called Problem: Grid Control Install fails during Agent CA running chronos_config.pl [ID 418199.1]. This article mentions the incorrect setting for the hostname.

In my preparation for the 10G OCM Exam, I had encountered a similar problem which I got around by setting the following (See Grid Control (2)):

export ORACLE_HOSTNAME=${HOSTNAME%%.*}

I have updated the .bash_profile I set up in 11G OCM .bash_profile for GRIDCTRL.

Plan for Attempt #4

My plan for the fourth attempt to install OEM 10.2.0.5 using an existing 11G database is:

  1. Use OUI to remove the oms10g and agent10g homes.
  2. Use the procedure from 11G OCM Patch OEM 10.2.0.5 (4) to remove Remove Partial Repository.
  3. Install OEM 10.2.0.1 software only.
  4. Patch OMS 10.2.0.5 software only.
  5. Patch Agent 10.2.0.5 software only.
  6. Configure OEM 10.2.0.5 using an existing database.
Advertisements

One thought on “11G OCM Patch OEM 10.2.0.5 (5)

  1. 11G OCM Patch OEM 10.2.0.5 (6) « Yet Another OCM

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s