Oracle
Enterprise Manager Grid Control 11g Installation
Here I will show you the steps that I performed to Install the Grid
Control.
There are two major prerequisites for installing Oracle Enterprise
Manager (OEM): Oracle WebLogic Server and a certified Oracle
Database.
Grid
Control (GC) Cheat Sheet
1. Ensure the Oracle database version can be monitored by Grid
Control in Metalink Note 412431.1 "Oracle Enterprise Manager 10g
Grid Control Checker"
2. Request firewall ports to be opened for 2 way traffic between
your target and your Grid Control server. Test by issuing telnet
commands on port 4889 from your target to your Grid Control server.
3. Download the appropriate agent software version according to the
Metalink note above. The downloads are about 500Mb and are here http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html
4. Install the software according to Oracle installation
documentation on their website. When the installer asks for the
Repository server, add the IP of your Grid Control server port
4889. The agent registration password is the current SYSMAN
password5. Ensure an agent entry has been added to the Oratab file
on your target server. If not, add one yourself
Post Installation
Configuration:
1. Add your target machine name to the grid control server hosts
table.
2. Add GC machine name to target hosts table.
3. All licensed options are selected by default when you add install
a new agent. To remove them go into SETUP - MANAGEMENT PACK ACCESS.
"Search Database" and ensure all boxes are unchecked. "Search Host"
and ensure all boxes are unchecked.
4. Logon to Grid Control and add passwords in PREFERENCES -
PREFERRED CREDENTIALS. Enter passwords for HOST, DATABASE and ASM
(if using ASM)
5. Now add the DBSNMP monitoring password. Go to TARGETS - ALL
TARGETS - "Targets Not Configured". Click on the number next to
"Targets Not Configured" which is a hyperlink. Locate the target
from your new server and click Configure. Then you will then enter
DBMSP password. Set this is the SYS password. Save click NEXT,
SUBMIT, OK.
6. Turn on default Alerts on PREFERENCES - RULES. Check "Database
Availability and Critical States" and click CREATE LIKE. Copy this
rule and append your site name to the rule name, eg "Database
Availability and Critical States XXXX". Save this new rule and check
PUBLIC. Click SETUP-ADMINISTRATORS-CREATE and add a new SYSMAN
account and email address to receive these alerts. Eg XXXX_SYSMAN.
7. If desired customize your database alert log monitoring. Follow
Metalink Note:405396.1 and Note:330996.1.
Check
Pre-Requisites Here
Oracle® Enterprise Manager Grid Control Basic Installation Guide
http://download.oracle.com/docs/cd/E11857_01/install.111/e15838.pdf
Download
GRIDCONTROL_11.1.0.1.0_WIN32,
WIN32_11GR2_DATABASE, WEBLOGIC, AND JDK
Oracle WebLogic Server
11gR1
(10.3.2) - Package Installer
http://www.oracle.com/technetwork/middleware/ias/downloads/wls-main-097127.html
Install Java (JDK)
Execute File: 1-Java jdk-6u22-windows-i586
Weblogic Installation
http://download.oracle.com/docs/cd/E12840_01/common/docs103/install/prepare.html
Execute File: 2-wls1033_oepe111150_win32(Weblogic)
After the Installation is performed, run the Quick Start creating a
new
WebLogic Domain and accepting all the Defaults. Example:
DOMAIN_NAME = DBA_DOMAIN
User / Passwd = weblogic / weblogic12
Domain Location:
C:\Oracle\Middleware\user_projects\domains\DBA_DOMAIN
Admin Server URL: http:\\DAFGWin32bitDBA:7001\console
DB
Installation
Here we will be creating a DB to hold all the Objects for the OEM.
DB Name = OEM
Access = system / mypass
Enterprise Manager Database Control URL - (OEM) : https://DAFGWin32bitDBA:1158/em
Your database configuration files have been installed in
C:\oracle\app
while other components selected for installation have been installed
in
C:\oracle\app\product\11.2.0\dbhome_1.
Be cautious not to accidentally delete these configuration files.
Apply
Patch p10100100_112010_WINNT to the Database
- Set this variables:
set
ORACLE_HOME=C:\Oracle\app\product\11.2.0\dbhome_1
%ORACLE_HOME%/OPatch/opatch
lsinventory
- Stop all the Oracle services
- Go to the Folder with the patch:
cd
C:\TEMP\p10100100_112010_WINNT\10100100
- Ensure that the directory containing the OPatch script appears in
your PATH setting. Enter the following command to run OPatch:
echo %PATH%
C:\oracle\app\product\11.2.0\dbhome_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem
set
PATH=C:\oracle\app\product\11.2.0\dbhome_1\OPatch;%PATH%
echo %PATH%
- Apply the Patch
opatch apply
- Inspect the opatch<timestamp>.log file generated in
%ORACLE_HOME%\cfgtoollogs\opatch for any errors.
cd
%ORACLE_HOME%\cfgtoollogs\opatch
- Start the OracleService<SID> and Oracle Listener Services if
already not started.
- For each database instance running out of the ORACLE_HOME being
patched, connect to the database using SQL*Plus as SYSDBA and run
catcpu.sql as follows:
cd %ORACLE_HOME%\Bundle\Patch6
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catcpu.sql
SQL> QUIT
- Check the following log files in
$ORACLE_HOME/cfgtoollogs/catbundle
for any errors:
cd
%ORACLE_HOME%/cfgtoollogs/catbundle
catbundle_WINBUNDLE_<database
SID>_APPLY_<TIMESTAMP>.log
catbundle_WINBUNDLE_<database
SID>_GENERATE_<TIMESTAMP>.log
- To ensure all dependant objects are valid after running
catcpu.sql:
cd %ORACLE_HOME%\rdbms\admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql
To check for invalid objects, execute the following statement:
SQL> SELECT OBJECT_NAME
FROM
DBA_OBJECTS WHERE STATUS = 'INVALID';
Deconfigure
the
Database
Control
- Ensure that your existing, certified Oracle Database does NOT have
Database Control SYSMAN schema.
To do so, log in to the database as SYS user and run the following
query:
SELECT COUNT(*) FROM ALL_USERS
WHERE USERNAME='SYSMAN';
If the result of this query is 1, then the database has this schema,
so
deconfigure it.
To deconfigure Database Control for a standalone database, run the
following command from the Oracle home of the database as the user
who
installed the database. If the command hangs, then restart the
database
and rerun the command.
cd %ORACLE_HOME%/bin/
emca -deconfig dbcontrol db
-repos drop
- Existing Database Not to Have SYSMAN and SYSMAN_MDS Schema
Verify whether your database has Enterprise Manager Grid Control
SYSMAN
schema and MDS schema.
To do so, log in to the database as SYS user and run the following
query:
SELECT COUNT(*) FROM ALL_USERS
WHERE USERNAME IN ('SYSMAN','SYSMAN_MDS');
Before dropping the schema, set the environment variable
LD_LIBRARY_PATH to the ORACLE_HOME/lib directory of the OMS.
Also set the ORACLE_HOME to the Oracle home of the OMS.
Drop the schema by running the following command from the Oracle
home
of the OMS.
$<ORACLE_HOME>/sysman/admin/emdrep/bin/RepManager
<repository_database_host> <repository_database_port>
<repository_database_sid> -action dropall -dbUser
<repository_database_user> -dbPassword
<repository_database_password> -dbRole
<repository_database_user_role> -mwHome
<middleware_home>
-mwOraHome <oms_oracle_home> -oracleHome
<oms_oracle_home>
If you are dropping the schemas that belong to a 10g Release 2
(10.2.x.x) Management Repository, then run previous command without
these arguments: -mwHome <middleware_home> -mwOraHome
<middleware_ora_home> -oracleHome <oracle_home>
Note:
For Microsoft Windows, invoke RepManager.bat.
RepManager 11.1 supports -action dropall (drops SYSMAN as well as
SYSMAN_MDS) and -action drop (drops only SYSMAN).
RepManager 10.2.0.5 supports -action drop (drops only SYSMAN).
After dropping the schema, manually delete the database files
mgmt.dbf
and mgmt_ecm_depot1.dbf.
You can find these files by running the following command as SYS:
SELECT FILE_NAME FROM
DBA_DATA_FILES WHERE UPPER (TABLESPACE_NAME) LIKE 'MGMT%';
Setting
Database Initialization Parameters
compatible
10.2.0.1.0 or higher
remote_login_passwordfile
SHARED
or
EXCLUSIVE
statistics_level
TYPICAL
timed_statistics
TRUE
undo_management
AUTO
workarea_size_policy
AUTO
b_block_size
8192 or
greater
job_queue_processes
10 or greater
log_buffer
10485760 or greater
open_cursors
300
or
greater
processes
500 or greater
session_cached_cursors
200
or greater
Check
Other Settings
- Fine-Grained Access
Control
Requirements
Ensure that the fine-grained access control option is set to TRUE in
the existing, certified Oracle Database so that the Management
Repository can be created. To verify this, run the following
command:
select value from v$option
where
parameter = 'Fine-grained access control';
- UNDO Tablespace Size
Requirements
Ensure that the UNDO tablespace has a minimum space of 200 MB. To
verify this, run the following query:
SELECT
SUM(DECODE(autoextensible,'YES',200*1024*1024+1,bytes)) total
FROM dba_data_files f,
dba_tablespaces s
WHERE s.contents = 'UNDO'
AND s.tablespace_name =
f.tablespace_name;
Note: The result of this query is in bytes.
If the minimum space is less than 200 MB, then set it to 200 MB by
running the following command:
alter database datafile
<location datafile> resize 200M;
- UNDO Tablespace and
Temporary Tablespace Settings Requirements
Ensure that the UNDO tablespace and the TEMP tablespace are
autoextensible in the existing, certified Oracle Database. To verify
this, run the following command:
select count(*) from
dba_temp_files where tablespace_name='TEMP' and
AUTOEXTENSIBLE
<> 'YES';
select count(*) from
dba_data_files where tablespace_name='UNDOTBS' and AUTOEXTENSIBLE
<> 'YES';
If the result of the query is 0, then the tablespace is
autoextensible;
if not, then you will need to change it to make it autoextensible
- Installing User
Requirements
Ensure that you meet the following requirements:
(For UNIX only) The installation must NOT be run by a root user.
(For Microsoft Windows only) User must be part of the ORA-DBA group
and
have administrator permissions.
(For Microsoft Windows only) User must belong to the DBA group, and
have permissions to perform the following: Act as part of the
operating
system, Create a token object, Log on as a batch job, and Adjust
memory
quotas for a process.
To verify whether the agent user has these rights, from the Start
menu,
click Settings and then select Control Panel. From the Control Panel
window, select Administrative Tools, and from the Administrative
Tools
window, select Local Security Settings. In the Local Security
Settings
window, from the tree structure, expand Local Policies, and then
expand
User Rights Assignment.
Installation
Procedure
for
the Grid
Nothing Special here, just execute the setup.exe File.
Installation
Process
for LINUX
http://oracleinnotiive.wordpress.com/2010/08/02/oracle-enterprise-manager-11g-grid-control-installation-guide/
Grid
Control
Management Agent Instructions for Microsoft Windows x86
(Windows 32-bit) 11g Release 1
(11.1.0.1.0)
This document contains the following sections:
1. Introduction
2. Download the Management Agent software
3 Fresh Installation of 11.1.0.1.0 Management Agent
4. Upgrading Management Agent to latest version 11.1.0.1.0
1. Introduction
NOTE: The agent software discussed here DOES upgrade your existing
installation of Management Agents from version 10.2.0.4 or higher to
latest 11.1.0.1.0 version and can also be used for deploying fresh
11.1.0.1.0 Management Agents on hosts.
2. Download the Management
Agent software
The Management Agent software can be downloaded in two ways:
2.1 Automatic download
from
Grid Control console using "Download Agent software" feature
The Management Agent software is available on My Oracle Support Web
site and can be downloaded using the "Download Agent Software"
feature
in the Grid Control console itself. Refer to the "Procuring Oracle
Management Agent Software" in the Enterprise Manager Grid
Control
Advanced Installation and Configuration Guide available at:
http://www.oracle.com/technology/documentation/oem.html
This URL takes you to the Enterprise Manager documentation library
page, and this URL may appear in many parts of the Readme. Access
this
URL to reach the library page, and from the table, click View
Library.
On the following page, click the Documentation tab, and then
click the name of the document you want to access.
2.2 Manual download from
the
Oracle Technology Network (OTN)
Download the Win32_Grid_Control_agent_download_11.1.0.1.0.zip file
from
the Oracle Technology Network (OTN):-
http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html
After downloading the software, verify that the size of the
downloaded
software matches with the size (bytes) displayed along with the
download link. Follow the instructions outlined in section
"Procuring
Enterprise Manager Grid Control Software" of the Enterprise Manager
Grid Control Advanced Installation and Configuration Guide available
at:
http://www.oracle.com/technology/documentation/oem.html
3. Fresh Installation of
11.1.0.1.0 Management Agent
There are various methods for installing fresh 11.1.0.1.0 Management
Agent in your environment.
3.1 Methods for Mass
deployment of Management Agent
One Time Setup
- If you have downloaded the Agent software from
the
Grid Control
console using the "Download Agent software" link, then no
manual
setup is required. Skip to the next section on methods for mass
deployment
- If you have manually downloaded the Agent
software
from Oracle Technology Network (OTN) then perform the following
steps:
a. Copy the Agent
downloaded file to the Oracle home directory of the OMS
<ORACLE_HOME>\sysman\agent_download\11.1.0.1.0
Note: If
<ORACLE_HOME>\sysman\agent_download\11.1.0.1.0 directory
doesn't
exist then create it manually.
b. Go to the Oracle home
directory of the Oracle Management Service(OMS)
<ORACLE_HOME>\sysman\agent_download\11.1.0.1.0
c. Run the following
command to unzip the software
<ORACLE_HOME>\bin\unzip
Win32_Grid_Control_agent_download_11.1.0.1.0.zip
Methods for Mass
Deployment
of Management Agents
Once the Agent software is staged in the staging location under the
OMS oracle home mentioned above then either of the following methods
can be used for mass agent deployment:
3.1.1
Agent Deploy Application
Agent Deploy application allows you to "push" the
Management Agents
on multiple hosts in a single window from the Grid Control console
itself.
Details on using this method can be found in
Enterprise Manager Grid Control Basic Installation guide:
http://www.oracle.com/technology/documentation/oem.html
3.1.2
Agent Clone
Agent Clone application automates the cloning of
Management Agents
based on existing pre-patched reference installations. It allows
deployment of Management Agents on multiple hosts in a single change
window from the Grid Control console itself.
Refer to “Cloning Management Agent “ described in
the Enterprise
Manager Grid Control Advanced Installation and Configuration Guide
available at:
http://www.oracle.com/technology/documentation/oem.html
3.1.3
AgentDownload script
An alternate option to pushing the agents to
multiple hosts is to
"pull" the Management Agent software and configure it based on
\demand.
Go to the Oracle home directory of the OMS
<ORACLE_HOME>\sysman\agent_download\11.1.0.1.0 directory then
run
this command:
mv agent_download.rsp.bak agent_download.rsp
Then follow the instructions listed out in
“Installing the
Agent Using the agentDownload Script “of the Enterprise Manager Grid
Control Advanced Installation and Configuration Guide available at:
http://www.oracle.com/technology/documentation/oem.html
3.2. Silent installation
of
Management Agent
For Management Agent silent installation, copy the <Stage
location>\response\additional_agent.rsp file to a location on the
local machine and modify the value Unspecified entries accordingly
in
the response file.
Invoke the runInstaller by executing:
<stage location>\agent\Win32\setup.exe -silent -responseFile
<absolute path of the response file>\additional_agent.rsp
For detailed information on using silent installation method to
install
the Management Agent please refer to “Installing Oracle Management
Agent Using Response File” described in the Enterprise Manager Grid
Control Advanced Installation and Configuration Guide available at:
http://www.oracle.com/technology/documentation/oem.html
3.3. NFS Mounted Agent
Installation
Enterprise Manager 11g R1 allows you to install a single Agent on a
shared NFS filesystem, and then have multiple hosts share that same
ORACLE_HOME. Details on installing a NFS mounted agent can be found
in
section "Installing Oracle Management Agent Using Shared Oracle
Home"
of the Enterprise Manager Grid Control Advanced Installation and
Configuration Guide available at:
http://www.oracle.com/technology/documentation/oem.html
4. Upgrading Management
Agent
to latest version 11.1.0.1.0
4.1 Upgrading Oracle
Management Agent Release 1 (10.1.0.x) to Oracle Management Agent
11g
Release 1 (11.1.0.1.0)
If your Additional Management Agent version is 10.1.0.x and you want
to
upgrade it to 11.1.0.1.0 version then:
Step 1: You have to first upgrade your Management Agent to version
10.2.0.4 or 10.2.0.5.
Step 2: Then upgrade it to version 11.1.0.1.0
Refer to the Chapter “Upgrading Oracle Management Agent Using Agent
Upgrade Wizard" of Enterprise Manager Grid Control Advanced
Installation and Configuration Guide for instructions, available
here:
http://www.oracle.com/technology/documentation/oem.html
4.2 Upgrading Oracle
Management Agent Release 2 (10.2.0.x) to Oracle Management Agent
11g
Release 1 (11.1.0.1.0)
If you have Additional Management Agent version 10.2.0.3 or lower
and
want to upgrade it to 11.1.0.1.0 version then:
Step 1: Apply 10.2.0.4 or 10.2.0.5 patchset to the Management Agent.
Follow the steps from the section "Upgrading Management Agent" of
the respective version of Release note.
Step 2: Upgrade 10.2.0.4 or 10.2.0.5 version of Management Agent to
11.1.0.1.0. Follow the steps from the Chapter “Upgrading Oracle
Management Agent Using Agent Upgrade Wizard" of Enterprise
Manager Grid Control
Advanced Installation and Configuration Guide available here:
http://www.oracle.com/technology/documentation/oem.html
Troubleshooting
11g Grid Control
Installation
- tips and solutions
http://gavinsoorma.com/2010/10/11g-grid-control-installation-tips-and-solutions/
Cleaning
Errors
METALINK NOTE
Grid Control 11g install fails at OMS configuration stage. [ID
1135493.1]
Solution
1. Use the .../oms11g/sysman/admin/emdrep/bin/RepManager to remove
the
repository from the database:
....oms11g/sysman/admin/emdrep/bin/RepManager -action dropall
2. Remove the current grid control (using the OUI to properly update
the inventory) and WebLogic Server 10.3.3 installation.
3. Try the installation again using WebLogic Server 10.3.2
Solution
1.Remove Grid Control 11g
Start the OUI from the Grid Control OMS
$ORACLE_HOME/oui/bin/runInstaller
Press De-Install Products
Select all product installed for Grid Control 11g
oms11g,
agent11g,
common11g
webteir11g
Once completed make sure the directories for these Grid Control
ORACLE_HOMEs do not exist.
2.Remove Weblogic Server 10.3.3
Go to the Web Logic Server Home
(WLS_ORACLE_HOME/wlserver_10.3/uninstall) and invoke the
uninstall.sh
$ cd /scratch/oracle/middleware/wlserver_10.3/uninstall
$ ./uninstall.sh
3.Install Weblogic Server 10.3.2
4.Install Grid Control 11g