Installing Oracle Enterprise Manager 11g - Misc & tips

This blog entry provides a couple of tips to be successful with Oracle Enterprise Manager Grid Control on Oracle Linux x64 system. 

The Objective of this document is to provide high-level guidelines for installing Oracle Enterprise Manager 11g Release1 (11.1.0.1.0). The instructions in this document will help in getting an 11g Grid control deployed for a Proof of Concept (POC) or a Demo to the customers. 

Oracle Enterprise Manager 11g Install Overview

Oracle Enterprise Manager 11g Release1 Install will install the following: 

Oracle Management Service 11g Release 1 

Oracle Management Agent 11g Release 1 

Configures the Management Repository in the existing, certified Oracle Database 

There are 2 major pre-requisites that a user have to full fill before  installing Oracle Enterprise Manager 11g Release1 

User has to make sure that Oracle WebLogic Server 10.3.2 is installed on the server. 

User has to make sure that certified Oracle Database is installed on the server, which will host the grid control repository. 


Step by step 

Install Oracle Linux x64

Nothing special there. The following configuration works fine.

  • just disabled Unbreakable Linux setup during the installation process
  • setup a Development platform  
  • the system must be a fully qualified one
  • enable the yum repository and download and install the Oracle Linux 5 repo file to your system.

# cd /etc/yum.repos.d
# wget http://public-yum.oracle.com/public-yum-el5.repo

Enable both the [el5_u5_base] and the [ol5_u5_base] repositories in the yum configuration file by changing enable=0 to enable=1 in those sections.

 

Install Oracle WLS 10.3.2

Nothing special there. Just apply the patch WDJ7 on top of the standard setup.

Install Oracle DataBase 11g ( Release 2 )

Nothing special there. Btw you may execute a couple of pre-configuration steps according to the system setup of your Oracle Enterprise Linux. 

OS-KERNEL systems parameters
Parameter current value  required value
semopm 32  100
 file-max 371227  6815744
ip_local_port_range 32768-61000 9000-65500
rmem-default 129024 262144
rmem-max 131071 4194304
wmem-default 129024 262144
wmem-max 131071 1048576
aio-max-rn 65536 1048576

For these modifications you have to execute some provided scripts as root when the installation process asks for it. Generally speaking, proceed as follow

  • open a terminal
  • login as root
  • run the scripts
  • continue with the setup 
Extra required packages

At least, the following packages are required for this installation :

  • libaio-devel-0.3.106
  • sysstat-7.0.2
  • unixODBC-2.2.11
  • unixODBC-devel-2.2.11
  • compat-db-2.\*

Missing packages will be listed.

	# yum install <package-name>

Post Oracle DB configuration : DB Control SYSMAN schema

a) DB Control SYSMAN schema is created in the database, as a part of the database install. User has to deconfigure it, else while doing the Grid control install it will prompt you to remove the dbconsole . 

  • Set the environment variable:
	# export ORACLE_HOME=<oracle-install-dir>/oracle/product/11.2.0/dbhome_1
	# export ORACLE_SID=orcl

  • Run the following command as user oracle:

# cd <oracle-install-dir>oracle/product/11.2.0/dbhome_1/bin

#   ./emca -deconfig dbcontrol db -repos drop

    • Provide the following input parameters:
      • SID = orcl
      • Listener port = 1521
      • Password for SYS = Betadb2010
      • Password for SYSMAN = Betadb2010
      • Do you wish to continue (Y/N) = Y

b) Log into the sqlplus as SYSMAN user : ./sqlplus “/as sysdba”

  • Run the following SQL
  • # sqlplus "/ as sysdba" 

alter database datafile '<oracle-install-dir>/oradata/orcl/undotbs01.dbf' resize 200M;

Note: Grid control requires 200Mb of space in undo tablespace.

EnterpriseManager 11g Release1 Control Grid

Nothing special there. Just follow the installation procedure and create a brand new Enterprise Manager system. 

Btw you may execute a couple of pre-configuration steps for the Oracle DataBase according to the system setup such as processes, session_cached_cursors and most probably some others

# sqlplus "/ as sysdba" 

alter system set process=<value> scope=SPFILE;

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

This blog is about Software How-to & Best Practices

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today