11G OCM Patch OEM 10.2.0.5 (6)


Attempt #4 to install OEM 10.2.0.5 is now underway using the plan from 11G OCM Patch OEM 10.2.0.5 (5).

1. Use OUI to remove the oms10g and agent10g homes.

Shut Down All OEM Processes

Shut down all running processes by running the following commands:

cd /opt/oracle/app/oms10g/opmn/bin
./opmnctl stopall
cd /opt/oracle/app/agent10g/bin
./emctl stop agent

A sample run is as follows:

[oracle@gridctrl ~]$ cd /opt/oracle/app/oms10g/opmn/bin
[oracle@gridctrl bin]$ ./opmnctl stopall
opmnctl: stopping opmn and all managed processes...
[oracle@gridctrl bin]$ cd /opt/oracle/app/agent10g/bin
[oracle@gridctrl bin]$ ./emctl stop agent
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.  
Copyright (c) 1996, 2009 Oracle Corporation.  All rights reserved.
Agent is Not Running

Remove the OMS10G and AGENT10G Homes

Run the following commands to bring up the OUI so that the homes can be removed:

cd /opt/oracle/software/Linux_Grid_Control_full_102010
./runInstaller

Click on Installed Products at the bottom of the main menu. Then select the following homes on the dialogue:

  • oms10g
  • agent10g

Click on deinstall Remove.

2. Remove OMR (Oracle Management Repository)

Use the procedure from 11G OCM Patch OEM 10.2.0.5 (4) to Remove Partial Repository.

3. Install OEM 10.2.0.1 software only

To install OEM 10.2.0.1, I used the procedure from 11G OCM Install OEM 10.2.0.1 (4).

The result is:

The installation of Oracle Management Agent was successful.

Ran the /opt/oracle/app/oms10g/allroot.sh.

4. Patch OMS 10.2.0.5 software only

Instead of the single patch response file for both OMS and OMA, I had in 11G OCM Patch OEM 10.2.0.5 (1), I have a separate one for each of them.

4.1 Stopped All OPMN Processes

In contrast to my earlier attempt, I had to stop the OPMN processes using the procedure in 11G OCM Patch OEM 10.2.0.5 (1).

4.2 Created the Patchset Response File

The new patchset reponse file is called /home/oracle/oms10g_patchset.rsp which has the contents listed in 11G OCM Patch OEM 10.2.0.5 (1).

4.3 Install the 10.2.0.5 Patchset into OMS10G Home

To install the 10.2.0.5 patchset into OMS10G Home, I used the following command:

/opt/oracle/software/OEM/3731593/Disk1/runInstaller -noconfig -silent -responseFile /home/oracle/oms10g_patchset.rsp

Everything seemed to be satisfactory. Ran /opt/oracle/app/oms10g/root.sh without any problems.

5. Patch OMA 10.2.0.5 software only

5.1 Created the Patchset Response File

The new patchset reponse file is called /home/oracle/agent10g_patchset.rsp which has the contents listed in 11G OCM Patch OEM 10.2.0.5 (1).

5.2 Install the 10.2.0.5 Patchset into AGENT10G Home

To install the 10.2.0.5 patchset into AGENT10G Home, I used the following command:

/opt/oracle/software/OEM/3731593/Disk1/runInstaller -noconfig -silent -responseFile /home/oracle/agent10g_patchset.rsp

Everything seemed to be satisfactory. Ran /opt/oracle/app/agent10g/root.sh without any problems.

6. Configure OEM 10.2.0.5 using an existing database.

Using the script from 11G OCM Patch OEM 10.2.0.5 (4), I started the configuration of OEM 10.2.0.5 with an existing 11G database.

The results are:

Base Directory: /opt/oracle/app

 Starting ito execute Configuration Assistants: 

Running the configuration assistants using the following command:
/opt/oracle/app/oms10g/oui/bin/runConfig.sh INV_PTR_LOC=/opt/oracle/app/oms10g/oraInst.loc ORACLE_HOME=/opt/oracle/app/oms10g ACTION=configure MODE=perform COMPONENT_XML={encap_oms.1_0_0_0_0.xml}  RESPONSE_FILE=/opt/oracle/app/agent10g/responsefile 
perform - mode is starting for action: configure


perform - mode finished for action: configure

You can see the log file: /opt/oracle/app/oms10g/cfgtoollogs/oui/configActions2010-01-01_05-32-57-PM.log

Configuration Assistants failed with errors. Please check the above log. 
 For more details also check /opt/oracle/app/oms10g/cfgtoollogs/cfgfw/CfmLogger_<LATEST_TIME_STAMP>.log

The log, /opt/oracle/app/oms10g/cfgtoollogs/cfgfw/CfmLogger_2010-01-01_05-32-57-PM.log, shows:

INFO: oracle.sysman.top.oms:PerformSecureCommand:runCmd:Performing Command=/opt/oracle/app/oms10g/bin/emctl status oms -secure 
INFO: oracle.sysman.top.oms:Secure Command = /opt/oracle/app/oms10g/bin/emctl status oms -secure  has failed. OMS Status Returned=
2
'Oracle Enterprise Manager 10g Release 5 Grid Control  
Copyright (c) 1996, 2009 Oracle Corporation.  All rights reserved.
Checking the security status of the OMS at location set in /opt/oracle/app/oms10g/sysman/config/emoms.properties...   Done.
OMS is running but has not been secured. No HTTPS Port available.

So we are back to the same problem, the agent is not secured.

Advertisements

3 thoughts on “11G OCM Patch OEM 10.2.0.5 (6)

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

  2. 11G OCM Install OEM 10.2.0.5 With New Database « Yet Another OCM

  3. 2010 in review « 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