Because the upgrade path to 12.1.0.3 from 12.1.0.1 was not a path I was prepared to take as described in 02 Upgrade EM12CR3p1 (2), and this was only a test system, I had no qualms about losing all of my OEM data and starting afresh.
Following the advice given in 8.1.1 Overview of the Installation Types, I choose the Simple installation type because this type was:
Meant for demo or evaluation purposes, and small deployments, and when you do not want to worry about the granular control of the installer and want to install the Enterprise Manager system quickly, with less memory, and for monitoring fewer targets in their environment
Following the procedure described in 8.4.1 Installing with Simple Configuration, I ran the following commands:
cd /opt/oracle/software/em12103p1
./runInstaller
The following software updates were found:
The installer restarted,
Two (2) warnings were raised:
Checking for sufficient physical memory...
Description:
This is a prerequisite condition to test whether the system has sufficient physical memory.
Expected result: 3900MB
Actual Result: 3024MB
Check complete. The overall result of this check is: Failed <<<<
Recommendation:
Upgrade the memory for your system in order for Oracle software to function.
Checking for sufficient swap space...
Description:
This is a prerequisite condition to test whether the sufficient swapspace is available to perform the install.
Expected result: 4096MB
Actual Result: 4031MB
Check complete. The overall result of this check is: Failed <<<<
Recommendation:
Make more swap space available to perform the install.
Both of these warnings were ignored.
Used the following installation directories during step #12:
/opt/oracle/app/middleware/12.1.0.3
/opt/oracle/app/agent/12.1.0.3
Error Message for Database Control in Repository Database
During the installation, the following message was displayed:
Enterprise Manager Database Control schema exists in the database. To proceed with the installation of Enterprise Manager Cloud Control, you must deconfigure the same by running the following command:
To deconfigure Database Control for a single instance database, do the following command on database host:
(a) Set the environment variable <ORACLE_HOME> to the database home.(b) Run the following command:
<Database ORACLE HOME>/bin/emca -deconfig dbcontrol db -repos drop -SYS_PWD <sys password> -SYSMAN_PWD <sysman password>
To deconfigure Database Control for an Real Application Clusters (RAC) database, do the following command on database host:
(a) Set the environment variable <ORACLE_HOME> to the database home.(b) Run the following command:
<Database ORACLE HOME>/bin/emca -deconfig dbcontrol db -repos drop -cluster -SYS_PWD <sys password> -SYSMAN_PWD <sysman password>
NOTE: If the existing database is on different host, then install Oracle Management Agent on the database host, to monitor the database.
Change SYSMAN Password and Unlock Account
I had to change the password for SYSMAN in REPOS as follows:
[oracle@gridctrl em12103p1]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.4.0 Production on Sat Feb 1 10:58:07 2014
Copyright (c) 1982, 2013, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> password sysman
Changing password for sysman
New password:
Retype new password:
Password changed
SQL> alter user sysman account unlock;
User altered.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Deconfigure Database Control
Deconfigure Database Control, I ran the following command:
emca -deconfig dbcontrol db -repos drop -SYS_PWD ********* -SYSMAN_PWD *********
The log for deconfiguration is as follows:
STARTED EMCA at Feb 1, 2014 10:59:06 AM
EM Configuration Assistant, Version 11.2.0.3.0 Production
Copyright (c) 2003, 2011, Oracle. All rights reserved.
Enter the following information:
Database SID: repos
Listener port number: 1521
----------------------------------------------------------------------
WARNING : While repository is dropped the database will be put in quiesce mode.
----------------------------------------------------------------------
Do you wish to continue? [yes(Y)/no(N)]: Y
Feb 1, 2014 10:59:27 AM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at /opt/oracle/app/cfgtoollogs/emca/repos/emca_2014_02_01_10_59_06.log.
Feb 1, 2014 10:59:27 AM oracle.sysman.emcp.EMDBPreConfig performDeconfiguration
WARNING: EM is not configured for this database. No EM-specific actions can be performed. Some of the possible reasons may be:
1) EM is configured with different hostname then physical host. Set environment variable ORACLE_HOSTNAME=<hostname> and re-run EMCA script
2) ORACLE_HOSTNAME is set. Unset it and re-run EMCA script
Feb 1, 2014 10:59:27 AM oracle.sysman.emcp.EMReposConfig invoke
INFO: Dropping the EM repository (this may take a while) ...
Feb 1, 2014 11:01:16 AM oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully dropped
Enterprise Manager configuration completed successfully
FINISHED EMCA at Feb 1, 2014 11:01:16 AM
The installation finally completed with the following messages:
This information is also available at:
/opt/oracle/app/middleware/12.1.0.3/oms/install/setupinfo.txt
See below for information pertaining to your Enterprise Manager installation:
Use the following URL to access:
1. Enterprise Manager Cloud Control URL: https://gridctrl.yaocm.id.au:7801/em
2. Admin Server URL: https://gridctrl.yaocm.id.au:7102/console
The following details need to be provided during the additional OMS install:
1. Admin Server Hostname: gridctrl.yaocm.id.au
2. Admin Server Port: 7102
You can find the ports details used by this deployment at : /opt/oracle/app/middleware/12.1.0.3/oms/install/portlist.ini
NOTE:
An encryption key has been generated to encrypt sensitive data in the Management Repository. If this key is lost, all encrypted data in the Repository becomes unusable.
A backup of the OMS configuration is available in /opt/oracle/app/middleware/gc_inst/em/EMGC_OMS1/sysman/backup on host gridctrl.yaocm.id.au. See Cloud Control Administrators Guide for details on how to back up and recover an OMS.
NOTE: This backup is valid only for the initial OMS configuration. For example, it will not reflect plug-ins installed later, topology changes like the addition of a load balancer, or changes to other properties made using emctl or emcli. Backups should be created on a regular basis to ensure they capture the current OMS configuration. Use the following command to backup the OMS configuration:
/opt/oracle/app/middleware/12.1.0.3/oms/bin/emctl exportconfig oms -dir <backup dir>