Purpose:
This document describes in
detail the Steps for Installing Enterprise Manager 12.1.0.2(12C Release 2) in
graphical mode. It includes the following:
- Prerequisites
- Installation Types
- Advanced Installer Options
- Post Installation Tasks
- Installation log location
Software:
Download the following software
- Oracle Database 11gR2 (11.2.0.3) (x86_64)
- Enterprise Manager Cloud Control 12c Release 2
(12.1.0.2) (x86_64)
How to Install Enterprise Manager Cloud
Control 12.1.0.2 (12c R2):
Before
You Begin:
1. Oracle Management
Service 12c Release 2 (12.1.0.2) can communicate with Oracle Management Agent
12c Release 1 (12.1.0.1) and Oracle Management Agent 12c Release 2 (12.1.0.2),
and not with any earlier release of the Management Agent.
Whereas, Oracle Management
Service 12c Release 1 (12.1.0.1) can communicate only with Oracle Management
Agent 12c Release 1 (12.1.0.1), and not with any earlier release or higher
release of the Management Agent.
Agent 12.1.0.1
|
Agent 12.1.0.2
|
|
OMS
12.1.0.1
|
YES
|
NO
|
OMS
12.1.0.2
|
YES
|
YES
|
3. Ensure that there are
no white spaces in the name of the directory where you download and run the
Enterprise Manager Cloud Control software from. For example, do not download
and run the software from a directory titled "EM12C Software" because
there is a white space between the two words of the directory name.
4. You must not set the
ORACLE_HOME and ORACLE_SID environment variables. You must ensure that the
Oracle directories do NOT appear in the PATH.
Prerequisites:
You
need to ensure the following mandatory pre-requisites are met before you begin
the installation:
1. Hardware Requirements: System Requirements
1. Hardware Requirements: System Requirements
The
system requirements for running the installation program are listed in Table
2-1 .
Component
|
Requirement
|
Platform configuration
|
A supported configuration of hardware, operating
system, JDK, and database specific to the product you are installing.
|
Processor
|
1-GHz CPU
|
Hard disk drive
|
A complete installation (including SDKs) requires
approximately 3.9 GB of disk space. This includes temporary disk space that
is needed during installation. Depending on the components you choose to
install, and the installer that you are using, less disk space may be needed.
|
Memory
|
A minimum of 1 GB RAM, although Oracle recommends
2 GB of RAM.
|
Color bit depth display
|
For graphical-mode installation, 8-bit color
depth (256 colors) is required.
For console-mode and silent-mode installation,
there is no color bit depth requirement.
|
JDK
|
The installation program requires a Java run-time
environment (JRE) to run. A JRE is bundled in the Windows 32-bit and Linux
x86 installation programs, as well as in some UNIX installation programs
(those with file names ending in .bin).
For other platforms, the installation program
does not install a JDK. File names for these installation programs end
in .jar. To run the.jar installation programs, you must have the
appropriate version of the JDK installed on your system, and include
the bin directory
of the JDK at the beginning of the PATH variable definition.
Note: It
is important that you use a JDK because the installation process assigns
values to JAVA_HOME and
related variables to point to the JDK directory. All scripts installed by the
installation program use this JDK by default, including scripts to start
sample applications, the Configuration Wizard, and other development tools.
|
WebLogic
Server Installation User
The
user account you use when installing WebLogic Server is important. Please
review the following information before deciding which user account to use:
- If you are using the Generic Package installer or the Linux 64-bit installer, Oracle recommends that you set the umask to 027 on your system prior to installation. This ensures that WebLogic Server file permissions will be set properly during installation. Use the following command: umask 027
You
must enter this command in the same terminal window from which you plan to run
the WebLogic Server installer.
- When installing WebLogic Server on a UNIX or Linux operating system, do not run the installation program as the root user.
- When using a WebLogic Server Upgrade installer
to upgrade an existing WebLogic Server installation on Linux or UNIX
operating systems, you must run the Upgrade installer using the same user
ID as was used to perform the initial WebLogic Server installation.
- If you are installing the software in graphical mode on a UNIX or
Linux machine, you must set the DISPLAY environment variable before
running the installer.
- Make sure that you are installing your product
on a supported hardware or software configuration.
The
files in the temporary directory require approximately 2.5 times the space that
is ultimately required for the installation.
By
default, the installation program uses the following temporary directories:
- UNIX platforms—system-dependent temporary
directory
Note:
If
you do not have enough temporary space to run the installation program, you are
prompted to specify an alternate directory or exit the installation program.
To make
sure that you have adequate temporary space, you may want to allocate an
alternate directory for this purpose. To do so, follow the instructions
provided in Table 2-2.
Platform
|
Procedure
|
UNIX
|
Enter the following option on the command line
when you start the installation program:
-Djava.io.tmpdir=tmpdirpath
Here, tmpdirpath is the full path of the directory you want to designate as a temporary
storage area for the installation program.
|
Ensure that you meet the hard disk space and physical memory requirements as
mentioned in Oracle Enterprise Manager Cloud Control Basic Installation Guide
12c Release 2 (12.1.0.2)
2. Operating System Requirements:
a) Certified Operating System:
Ensure that you install Enterprise Manger Cloud Control only on certified operating system .
b) OS Package Requirements:
Identifying Installed Packages
a) Certified Operating System:
Ensure that you install Enterprise Manger Cloud Control only on certified operating system .
b) OS Package Requirements:
Identifying Installed Packages
To identify the packages already installed on
your system, run the following command. If the command does not list the
packages listed in Package Requirements for Oracle Management Service or
Package Requirements for Oracle Management Agent, then install them manually.
Note:
The following command is meant only for Linux x86
and x86-64 platforms. To know the command for other platforms, contact your
system administrator or refer to the platform-specific manual.
rpm
-qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE}(%{ARCH})\n" | grep
glibc
The
command lists all the packages installed on the system. The 32-bit ones are
appended with (i386) or (i686), and the 64-bit ones are appended with(x86_64).
For
example, if you run the command on a 32-bit system, you should see something
similar to the following:
glibc-devel-2.3.4-2.43(i386)
glibc-headers-2.3.4-2.43(i386)
glibc-2.3.4-2.43(i686)
compat-glibc-headers-2.3.2-95.30(i386)
glibc-profile-2.3.4-2.43(i386)
glibc-utils-2.3.4-2.43(i386)
glibc-kernheaders-2.4-9.1.103.EL(i386)
glibc-common-2.3.4-2.43(i386)
compat-glibc-2.3.2-95.30(i386)
For
example, if you run the command on a 64-bit system, you should see something
similar to the following:
glibc-common-2.3.4-2.43(x86_64)
glibc-devel-2.3.4-2.43(x86_64)
glibc-profile-2.3.4-2.43(x86_64)
glibc-headers-2.3.4-2.43(x86_64)
glibc-utils-2.3.4-2.43(x86_64)
glibc-2.3.4-2.43(x86_64)
Table 3-1 lists
the packages required on different platforms (32-bit and 64-bit) for installing
a new Enterprise Manager system or an additional OMS.
Platform
|
32-Bit Packages for 32-Bit Platform
|
64-Bit Packages for 64-Bit Platform
|
Oracle Linux 6.x
(Red Hat 6 Kernel and
Unbreakable Enterprise Kernel (UEK))
|
|
|
Oracle Linux 5.x
Red Hat Enterprise Linux 5.x
|
|
In addition, install the 32-bit version as well
as the 64-bit version of glibc-devel-2.5-49 to avoid any linking errors while
installing the OMS. The installer checks for this package, so if this package
is not installed, the installer displays an error.
|
Package Requirements for Oracle Management Agent
Table 3-2 lists the packages required on different platforms
(32-bit and 64-bit) for installing a Management Agent. Table 3-2 Package Requirements for Oracle Management Agent
Platform
|
32-Bit Packages for 32-Bit Platform
|
64-Bit Packages for 64-Bit Platform
|
Oracle Linux 6.x
(Red Hat 6 Kernel and Unbreakable Enterprise
Kernel (UEK))
|
|
|
Oracle Linux 5.x
Red Hat Enterprise Linux 5.x
|
|
Oracle Linux 5.x and Red
Hat Enterprise Linux 5.x, where x <= 5 [for example, Oracle Linux 5.3]
Oracle Linux 5.x and Red
Hat Enterprise Linux 5.x, where x > 5 [for example, Oracle Linux 5.6]
|
Ensure that you set the file descriptor to a minimum of 4096. Verify the current value for file descriptors using the command: /bin/sh -c "ulimit -n"
If the current value is less than 4096, then as root user, update the /etc/security/limits.conf file as shown below
<UID> hard nofile 4096
Host File Requirements:
1. Ensure proper entries are there in etc/hosts file as shown below and also no duplicate entries for the same IP address:
127.0.0.1 localhost.localdomain localhost
<IP ADDRESS> <HOSTNAME.DOMAINNAME> <ALIAS/SHORT NAME>
2. Ensure that you check the network configuration to verify that the host on which you are installing resolves to a unique host name and a static IP address that is visible to other hosts in the network. You must use a static IP address. If you use a dynamic IP address, the installation might fail.
3. Verify the Hostname resolution for OMS Server.
If the DNS is configured you can issue the following commands from any server in the network:
$ nslookup <IP adddress of the OMS machine>
$ nslookup <hostname.domain of the OMS machine>
$ nslookup <hostname of the OMS machine>
Existing Database Version Requirement:
Download
Software
Unpack
Files
Unzip the files.
#11.2.0.3
unzip
p10404530_112030_Linux-x86-64_1of7.zip
unzip
p10404530_112030_Linux-x86-64_2of7.zip
You should now have a single directory
called "database" containing installation files.
Hosts
File
The "/etc/hosts" file must
contain a fully qualified name for the server.
<IP-address> <fully-qualified-machine-name> <machine-name>
For example.
127.0.0.1 localhost.localdomain localhost
192.168.0.181 G1.localdomain G1
Automatic
Setup
If you plan to use the
"oracle-rdbms-server-11gR2-preinstall" package to perform all your
prerequisite setup, follow the instructions at http://public-yum.oracle.com to setup the yum repository
for OL, then perform the following command.
# yum
install oracle-rdbms-server-11gR2-preinstall
All necessary prerequisites will
be performed automatically.
Manual
Setup
Oracle recommend the following minimum
parameter settings.
fs.suid_dumpable
= 1
fs.aio-max-nr
= 1048576
fs.file-max
= 6815744
kernel.shmall
= 2097152
kernel.shmmax
= 536870912
kernel.shmmni
= 4096
kernel.sem
= 250 32000 100 128
net.ipv4.ip_local_port_range
= 9000 65500
net.core.rmem_default
= 262144
net.core.rmem_max
= 4194304
net.core.wmem_default
= 262144
net.core.wmem_max
= 1048586
The current values can be tested using
the following command.
/sbin/sysctl
-a | grep <param-name>
Add or amend the following lines in the
"/etc/sysctl.conf" file.
fs.suid_dumpable
= 1
fs.aio-max-nr
= 1048576
fs.file-max
= 6815744
kernel.shmall
= 2097152
kernel.shmmax
= 536870912
kernel.shmmni
= 4096
#
semaphores: semmsl, semmns, semopm, semmni
kernel.sem
= 250 32000 100 128
net.ipv4.ip_local_port_range
= 9000 65500
net.core.rmem_default=4194304
net.core.rmem_max=4194304
net.core.wmem_default=262144
net.core.wmem_max=1048586
Run the following command to change the
current kernel parameters.
/sbin/sysctl
-p
Add the following lines to the
"/etc/security/limits.conf" file.
oracle soft nproc
2047
oracle hard nproc
16384
oracle soft nofile
4096
oracle hard nofile
65536
oracle soft stack
10240
Install the following packages if they
are not already present.
# From
Oracle Linux 6 DVD
cd
/media/cdrom/Server/Packages
rpm
-Uvh binutils-2*x86_64*
rpm
-Uvh glibc-2*x86_64* nss-softokn-freebl-3*x86_64*
rpm
-Uvh glibc-2*i686* nss-softokn-freebl-3*i686*
rpm
-Uvh compat-libstdc++-33*x86_64*
rpm
-Uvh glibc-common-2*x86_64*
rpm
-Uvh glibc-devel-2*x86_64*
rpm
-Uvh glibc-devel-2*i686*
rpm
-Uvh glibc-headers-2*x86_64*
rpm
-Uvh elfutils-libelf-0*x86_64*
rpm
-Uvh elfutils-libelf-devel-0*x86_64*
rpm
-Uvh gcc-4*x86_64*
rpm
-Uvh gcc-c++-4*x86_64*
rpm
-Uvh ksh-*x86_64*
rpm
-Uvh libaio-0*x86_64*
rpm
-Uvh libaio-devel-0*x86_64*
rpm
-Uvh libaio-0*i686*
rpm
-Uvh libaio-devel-0*i686*
rpm
-Uvh libgcc-4*x86_64*
rpm
-Uvh libgcc-4*i686*
rpm -Uvh
libstdc++-4*x86_64*
rpm
-Uvh libstdc++-4*i686*
rpm
-Uvh libstdc++-devel-4*x86_64*
rpm
-Uvh make-3.81*x86_64*
rpm
-Uvh numactl-devel-2*x86_64*
rpm
-Uvh sysstat-9*x86_64*
rpm
-Uvh compat-libstdc++-33*i686*
rpm
-Uvh compat-libcap*
cd /
eject
Note. This will install all the
necessary 32-bit packages for 11.2.0.1. From 11.2.0.2 onwards many of these are
unnecessary, but having them present does not cause a problem.
Create the new groups and users.
groupadd
-g 501 oinstall
groupadd
-g 502 dba
groupadd
-g 503 oper
groupadd
-g 504 asmadmin
groupadd
-g 506 asmdba
groupadd
-g 505 asmoper
useradd
-u 502 -g oinstall -G dba,asmdba,oper oracle
passwd
oracle
Note. We are not going to use the
"asm" groups, since this installation will not use ASM.
Additional
Setup
Disable secure linux by editing the
"/etc/selinux/config" file, making sure the SELINUX flag is set as
follows.
SELINUX=disabled
Once the change is complete, restart
the server.
Create the directories in which the
Oracle software will be installed.
mkdir
-p /u01/app/oracle/product/11.2.0/db_1
chown
-R oracle:oinstall /u01
chmod
-R 775 /u01
Login as root and issue the following
command.
xhost
+<machine-name>
Login as the oracle user and add the
following lines at the end of the ".bash_profile" file.
#
Oracle Settings
TMP=/tmp;
export TMP
TMPDIR=$TMP;
export TMPDIR
ORACLE_HOSTNAME=ol6-112.localdomain;
export ORACLE_HOSTNAME
ORACLE_UNQNAME=DB11G;
export ORACLE_UNQNAME
ORACLE_BASE=/u01/app/oracle;
export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/product/11.2.0/db_1;
export ORACLE_HOME
ORACLE_SID=DB11G;
export ORACLE_SID
PATH=/usr/sbin:$PATH;
export PATH
PATH=$ORACLE_HOME/bin:$PATH;
export PATH
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib;
export LD_LIBRARY_PATH
CLASSPATH=$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib;
export CLASSPATH
Installation
Log into the oracle user. If you are
using X emulation then set the DISPLAY environmental variable.
DISPLAY=<machine-name>:0.0;
export DISPLAY
Start the Oracle Universal Installer
(OUI) by issuing the following command in the database directory.
./runInstaller
Check for following
options and complete installation.
1.
Configure Security
Updates
2.
Select Install Option
3.
System Class
4.
Node Selection
5.
Select Install Type
6.
Typical Install
Configuration
7.
Create Inventory
8.
Perform Prerequisite
Checks
9.
Summary
10.
Install Product
11.
Database
Configuration Assistant
12.
Database
Configuration Assistant 2
13.
Execute Configuration
Scripts
14.
Finish
15.
Post Installation
Edit the
"/etc/oratab" file setting the restart flag for each instance to 'Y'.DB11G:/u01/app/oracle/product/11.2.0/db_1:Y
1. Ensure that the existing database is a certified database as mentioned in Enterprise Manager Certification Matrix.
2. Ensure that the database is patched with all the Patch Set Updates (PSU) or Critical Patch Updates (CPU) released for that release. Also ensure that you apply the patches.
3. The database can also have the Automatic Memory Management (AMM) feature enabled.
4. Ensure that this database is dedicated to Enterprise Manager.
5. DB Control SYSMAN schema is created in the database as part of the database install. You need to deconfigure it using the following command:
a.) Set the ORACLE_HOME and ORACLE_SID environment variable:
For example:-
export ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
export ORACLE_SID=orcl
b.) $ORACLE_HOME/bin/emca -deconfig dbcontrol db -repos drop
6. Ensure that pre-requisite DB parameters are set as mentioned in install guide.
Make the following initialization
parameter changes and restart the instance.
sqlplus
/ AS SYSDBA
ALTER
SYSTEM SET processes=300 SCOPE=SPFILE;
ALTER
SYSTEM SET session_cached_cursors=200 SCOPE=SPFILE;
ALTER
SYSTEM SET sga_target=2G SCOPE=SPFILE;
ALTER
SYSTEM SET shared_pool_size=600M SCOPE=SPFILE;
ALTER
SYSTEM SET pga_aggregate_target=1G SCOPE=SPFILE;
ALTER
SYSTEM SET job_queue_processes=20 SCOPE=SPFILE;
-- May
be required if using older versions of DB.
--ALTER
SYSTEM SET log_buffer=10485760 SCOPE=SPFILE;
--ALTER
SYSTEM SET open_cursors=300 SCOPE=SPFILE;
--
Restart the instance.
SHUTDOWN
IMMEDIATE
STARTUP
If you have done a default installation
as described here, the UNDO tablespace will be autoextensible. If you have done
a custom installation make sure the UNDO tablespace is at least 200M in size.
Also, make sure you have 3 redo logs of at least 300M to prevent a warning
during the installation.
The database installation is now
complete.
Installing User Requirements:
1. (For UNIX only) The installation must NOT be run by a root user.
Central Inventory Location Requirements:
Ensure that the Central Inventory (oraInventory) is not in a shared location. When you use the /etc/oraInst.loc file, ensure that the inventory location specified there is not pointing to a shared location. If it is, change it to a non-shared location by following the MOS document 1092645.1
Internet Connection Requirement:
Oracle recommends that the host from where you are running the installer has a connection to the Internet so that the configuration information can be automatically collected and uploaded to My Oracle Support.
Installation Types:
1. Simple InstallationThe simple installation type installs with default configuration settings and preferences that you need for a complete Enterprise Manager system. It does not offer too many options to customize your installation. This installation type is 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.
2. Advanced Installation
The Advanced installation type is meant for Administrators who wants custom or advanced and more flexible configuration. It prompts you for WebLogic Server details, database connection details, data file locations for tablespaces, password for creating SYSMAN account and also customize ports.
Advanced installation type helps you with the EM planning:
- Small
- Medium
- Large
Select
the deployment size from the drop down next to 'Deployment Size' list to
indicate the number of targets you plan to monitor, the number Management
Agents you plan to have, and the number of concurrent user sessions you plan
have.
Deployment Size
|
Targets Count
|
Management Agents Count
|
Concurrent User Session Count
|
Small
|
Up to 999
|
Up to 99
|
Up to 10
|
Medium
|
Between 1000 and 9999
|
Between 100 and 999
|
Between 10 and 24
|
Large
|
10,000 or more
|
1000 or more
|
Between 25 and 50
|
To install Enterprise
Manager Cloud Control 12.1.0.2 with simple configuration:
Make the following directories to hold
the management server and agent.
$ mkdir
-p /u01/app/oracle/oms12cr2
$ mkdir
-p /u01/app/oracle/agent12cr2
Unzip the Cloud Control media, the
start the installation by running the "runInstller" script.
$ mkdir
em12cr2
$ unzip
-d em12cr2 em12cr2_linux64_disk1.zip
$ unzip
-d em12cr2 em12cr2_linux64_disk2.zip
$ unzip
-d em12cr2 em12cr2_linux64_disk3.zip
$ cd
em12cr2
$
./runInstaller
If you wish to receive support
information, enter the required details, or uncheck the security updates
checkbox and click the "Next" button. Click the "Yes"
button the subsequent warning dialog.
If you wish to check for updates, enter
the required details, or check the "Skip" option and click the
"Next" button.
If you have performed the prerequisites
as described, the installation should pass all prerequisite checks. Click the
"Next" button.
Select the "Create a new
Enterprise Manager System" and "Simple" options, then click the
"Next" button.
Enter the middleware and agent
locations, then click the "Next" button.
Enter the administrator password and
database repository details, then click the "Next" button.
On the first warning dialog, click the
"Yes" button to disable the stats gathering job.
If you have any additional warnings,
check they don't look like show-stoppers, then click the "OK" button
to continue. If you are happy with the review
information, click the "Install" button.
Wait while the installation and
configuration take place.
When prompted, run the root scripts,
then click the "OK" button.
Make note of the URLs, then click the
"Close" button to exit the installer. A copy of this information is
available in the
"/u01/app/oracle/Middleware/oms/install/setupinfo.txt" file.
The login screen is available from a
browser using the URL provided in the previous screen
("https://ol6-em12cr2.localdomain:7803/em"). Log in with the username
"sysman" and the password you specified during your installation.
Once logged in, you are presented with
a with the "License Agreement" screen. Click the "I Agree"
button and you are presented with the homepage selector screen. Select the
desired homepage (I chose Summary) and click the "Preview" button.
You are presented with the selected
screen as the console homepage.
Post Installation Tasks:
Verify the OMS status:
$<OMS_HOME>/bin/emctl
status oms
Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.2.0
Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
WebTier is Up
Oracle Management Server is Up
Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.2.0
Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
WebTier is Up
Oracle Management Server is Up
Verify the Agent status:
$<AGENT_HOME>/bin/emctl
status agent
Verify the Agent upload:
$<AGENT_HOME>/bin/emctl
upload
Installation Log
location:
Installation logs:
oraInventory/logs/*.*
<ORACLE_HOME>/cfgtoollogs/oui/*.*
Configuration Logs:
<ORACLE_HOME>/cfgtoollogs/cfgfw/*
Specific Configuration
logs:
Configuration Assistant
|
Log Location
|
Repository configuration logs
|
<OMS_ORACLE_HOME>/sysman/log/schemamanager/*
|
OMS configuration logs
|
<OMS_ORACLE_HOME>/cfgtoollogs/omsca/*
|
PluginCA configuration logs
|
<OMS_ORACLE_HOME>/cfgtoollogs/pluginca/*
|
Agent configuration logs
|
<AGENT_ORACLE_HOME>/cfgtoollogs/cfgfw/*
|
Startup/Shutdown
Use the following commands to turn on
all components installed by this article.
#!/bin/bash
export
ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1
export
OMS_HOME=/u01/app/oracle/oms12cr2/oms
export
AGENT_HOME=/u01/app/oracle/agent12cr2/core/12.1.0.2.0
# Start
everything
$ORACLE_HOME/bin/dbstart
$ORACLE_HOME
$OMS_HOME/bin/emctl
start oms
$AGENT_HOME/bin/emctl
start agent
Use the following commands to turn off
all components installed by this article.
#!/bin/bash
export
ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1
export
OMS_HOME=/u01/app/oracle/oms12cr2/oms
export
AGENT_HOME=/u01/app/oracle/agent12cr2/core/12.1.0.2.0
# Stop
everything
$OMS_HOME/bin/emctl
stop oms -all
$AGENT_HOME/bin/emctl
stop agent
$ORACLE_HOME/bin/dbshut
$ORACLE_HOME
Next
Steps for upgrading existing agents :
Upgrade the
existing management agents by deploying the 12c agent software on the hosts
where we are upgrading the existing 10g agent. All these tasks are done from
the
Upgrade
Console in the 12c OEM Grid Control using mass deployment. We can do this in a
piecemeal manner and do not have to upgrade all the agents to 12c in one go. So
we will have both the 10g and 12c Grid Control environments running side by
side until we migrated all the 10g agents to 12c.
Note that
the 12c OMS can only communicate with the 12c agent and not any other agent
version.
Deinstalling Enterprise Manager
System in Graphical Mode
a. Prerequisites.
b. Deinstallation
Procedure .
c. After
You Deinstall .
Note:
Prerequisites
Before you deinstall Enterprise
Manager Grid Control, follow these steps:
1.
Backup grid repository
database and software.
2.
Delete Oracle Management
Service (OMS) by running the following command from the Oracle home of the OMS.
This command automatically stops the OMS, Oracle WebLogic Server, and also
Oracle WebTier.
3.
Shut down Oracle
Management Agent (Management Agent) by running the following command from the
Oracle home of the Management Agent:
<ORACLE_HOME>/bin/emctl stop
agent
4.
If you want to deinstall
the entire Enterprise Manager Grid Control system, including Oracle Management
Repository (Management Repository) that is configured in your database, then
after deleting all the OMSes and the Management Agents, follow these steps:
a.
Drop the Enterprise
Manager Grid Control schema (SYSMAN schema) and the Metadata schema (MDS
schema) from the Management Repository by running the following command from
the Oracle home of the OMS:
<ORACLE_HOME>/sysman/admin/emdrep/bin/RepManager
<database_host> <repository_database_port>
<repository_database_sid> -action dropall -dbUser
<repository_database_user> -dbPassword
<repository_database_password> -dbRole
<repository_database_user_role> -reposName <repository_name>
-reposPassword <repository_password> -mwHome <middleware_home>
-mwOraHome <middleware_ora_home> -oracleHome <oracle_home>
b.
Manually delete the data
files
mgmt.dbf and mgmt_ecm_depot1.dbf from the Oracle home of the database.
WARNING:
Once the Management Repository is dropped, it CANNOT
be retrieved. Therefore, drop the Management Repository ONLY IF you want to
deinstall the entire Enterprise Manager Grid Control system, that is, all your
OMSes, Management Agents, and also the Management Repository. If you want to
deinstall only an OMS (additional OMS installation), then do not drop the
Management Repository.
Deinstallation Procedure:
To deinstall Enterprise
Manager Grid Control, follow these steps:
1.
Invoke the installer from
the Oracle home of the OMS by running the following command:
2.
In the Enterprise Manager
Grid Control Installation Wizard, on the My Oracle Support Details screen,
click Installed
Products.
3.
On the Inventory screen,
select the following and click Remove.
o Oracle home of the OMS (
oms11g).
For example,
/u01/app/Oracle/Middleware/oms11g
o Oracle home of the Management Agent (
agent11g).
For example,
/u01/app/Oracle/Middleware/agent11g
o Oracle home of Oracle WebTier (
Oracle_WT) that is present in the Oracle Middleware Home.
For example,
/u01/app/Oracle/Middleware/Oracle_WT
o Common directory (
oracle_common) that is present in the Oracle Middleware Home.
For example,
/u01/app/Oracle/Middleware/oracle_common
o Oracle Management Service Instance Base (
gc_inst or any other custom name specified by you) that is
present in the parent directory of the Oracle Middleware Home.
For example,
/u01/app/Oracle/gc_inst
Note:
If the parent directory of
the Oracle Middleware Home did not have write permission,
then the Oracle Management Service Instance Base might have been created in the
Oracle Middleware Home.
After You Deinstall
After you deinstall the
Oracle homes, follow these steps:
1.
Verify whether the Oracle
homes and other directories were successfully deinstalled. To do so, follow
these steps:
a.
Invoke the installer from
the Oracle home of the OMS by running the following command:
$<ORACLE_HOME>/oui/bin/runInstaller
Note:
For Microsoft Windows,
invoke
setup.exe.
b.
In the Enterprise Manager
Grid Control Installation Wizard, on the My Oracle Support Details screen, click Installed Products.
c.
On the Inventory screen,
check whether or not the Oracle homes and other directories you deinstalled
appear. If the deinstallation was successful, then those Oracle homes and
directories should not appear.
2.
The Oracle homes you deinstalled
are deregistered from the central inventory and the
oratab file. However, some files might still remain in these
Oracle homes. You might also see the OMS instance base directory and the Oracle
home for Web Tier. You can manually delete these files and directories.
You must also manually delete all auto-start scripts
present in the
/etc/rc.d/ directory. For example, /etc/rc.d/rc3.d/S98gcstartup.Deinstall 11g Grid Control Agent Home
Example :
export ORACLE_HOME=/u01/oracle/agent11g
TEST:> ./runInstaller -deinstall -silent
“REMOVE_HOMES={/u01/oracle/agent11g}” -removeallfiles
Starting Oracle Universal Installer…
Checking swap space: must be greater than 500
MB. Actual 8192 MB Passed
Preparing to launch Oracle Universal Installer
from /tmp/OraInstall2011-11-28_11-09-42AM.
Please
wait …oasd:/u01/oracle/agent11g/oui/bin>
Oracle Universal Installer, Version 11.1.0.8.0 Production
Copyright (C) 1999, 2010, Oracle. All rights
reserved.
Starting deinstall
Deinstall in progress (Monday, November 28,
2011 11:09:53 AM WST) Configuration assistant “Agent Deinstall Assistant”
succeeded Configuration assistant “Oracle Configuration Manager Deinstall”
succeeded ……………………………………………………… 100% Done.
Deinstall successful
End of install phases.(Monday, November 28,
2011 11:10:47 AM WST) End of deinstallations
Please check
‘/u01/oracle/oraInventory/logs/silentInstall2011-11-28_11-09-42AM.log’
for more details.
ControlC to quit.
oasd:/u01/oracle> cd agent11g
ksh: agent11g: not found
oasd:/u01/oracle>
So the deinstall with parameter
-removeallfiles also gets rid of the agent11g directory.
No comments:
Post a Comment