Oracle Enterprise Manager Grid Control Installation 11g Release 1 (11.1.0.1.0) on fedora Linux 14

February 3rd, 2011 | Posted in 11G, Blog, grid control | 1 Comment


Download the article in pdf here!

This article describes how you can install Enterprise Manager Grid Control using an existing, certified Oracle Database and Oracle Weblogic Server. In particular, this section covers the following:

1- Prerequisites
2- Java installation procedure
3- Weblogic Installation procedure
4- Apply patches using the Oracle Smart Update utility (if exists)
5- Oracle Enterprise Manager Grid Control Installation 11g Release 1 installation
6-Verify the installation

1- Prerequisites:

- My Hardware: 50GB of free disk with 8GB of memory
- My Operating System: Linux Fedora 14
- Operating System Groups and Users: The Oracle Software Owner User is Oracle and Oracle Inventory Group is oinstall.
Please refer to: http://download.oracle.com/docs/cd/E11857_01/install.111/e16847/appdx_creating_os_grps_usrs.htm#CIHCFFEI for more details of how to create the groups and users.
- Host Name: wissem.localdomain
- Static IP Address: 192.168.2.104
- Temporary directory must have at least 400 MB of free disk space.
- JDK Requirements: Oracle Sun JDK 1.6_18
- Install Oracle Weblogic Server 10.3.2
- Ensure that you apply patch ID WDJ7 on Oracle WebLogic Server using the Oracle Smart Update utility. This patch fixes bugs 8990616, 9100465, and 9221722.
- Ensure you install Oracle Database 11g Release 2 (11.2.0.1.0), then ensure that you apply the patch for bug# 9002336 and 9067282 (Oracle Support note 1073166.1)
- Ensure that your existing Oracle Database does NOT have Enterprise Manager Grid Control SYSMAN schema and Metadata (MDS) schema.
- Ensure that you turn on archive logging in the existing (select log_mode from v$database;)
- Set the number of processes of your Oracle database of 500 or higher.
- Set the log buffer of your Oracle database of 10485760 or higher.
- Set of session_cached_cursors value of 200 or higher.

2- Java installation procedure:
Install the jdk1.6 using the following command:
yum install java-1.6.0-openjdk

Make sure to add this line to .bash_profile under /home/oracle

JAVA_HOME=/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64

3- Weblogic Installation procedure

Download Oracle Weblogic server from http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html
Execute the following command:
java -jar wls1034_generic.jar

4- Apply patches using the Oracle Smart Update utility (if exists)

Go to your Middleware home and run the bsu.sh script (see below):

You may have an error when running the bsu.sh script. I have eddited the script and changed the java classpath to reflect my environment setup.

When the screen appears, you Insert your support ID



5- Oracle Enterprise Manager Grid Control Installation 11g Release 1 installation:

Download the Oracle grid control from otn.oracle.com website:
(make sure to check sum the zip files):
Make sure to Unzip the files in the SAME directory, otherwise, you will get an error during the grid control installation.

Execute the runInstaller:
./runInstaller

Enter your  Oracle Support Details:

On the Select Installation Type screen, select Install a new Enterprise Manager system.

Specify, the middleware installtion path, you already installed in the Weblogic installtion step.

Create WebLogic Server Domain, you can leave the default server domain and the default weblogic user name, and then specify the domain server domain password.

Before going to the next screen, make sure that Enterprise manager repository have been removed, execute the command below:

You must make sure that your Oracle database is in open state, the listener is up and running: (you can use the command lsnrctl status to check the listener status).

Specify  the host name or the static IP address where the existing database resides, the database’s listener port and its
service name or system ID (SID), and the SYS user account’s password.
The installer uses this information to connect to the existing Oracle Database where the Management Repository can be configured.

You will probably get an error, if you did not followed the prerequisites, you can fix the errors without exiting from the OUI installer:

Fix the errors, see below:

Configure Oracle Management Repository and specify the sysman password and click next

Secure Oracle Management Service: specify the agent password. This password will be used by the new Management Agents that join the Enterprise Manager.

Accept  the list of ports to be used for various components

Review the details and click to install the components

Connect as a root system user, run the allroot.sh command and then back to the Oui installer and press ok:


Finally, get the URL and paste it in the browser link address:

6- Verify the installation:

$/bin/emctl status oms

Thanks,
Wissem EL KHLIFI

Scridb filter


One Comment to “Oracle Enterprise Manager Grid Control Installation 11g Release 1 (11.1.0.1.0) on fedora Linux 14”

  1. Nice article,thanks for sharing!


Leave a Comment





Subscribe


Polls

which oracle topic interests you most?

View Results

Loading ... Loading ...


Oracle Class Tweets


Recent Posts


Recent Comments

  • Ravi: Hi, As above, I want to add a new column in to my production database (11g) that has millions of records but...
  • DACCorp: Thanks bro, it worked! XD
  • accutane: Hello there, just became alert to your blog through Google, and found that it is truly informative. I am...
  • Ayman Mohamed: Thanks for your nice article, it is very helpful
  • Moon: Thanks man you solved my problem. i was facing this error: ORA-19625: error identifying file while rman...
  • James: “To solve the issue, After fixing the /etc/hosts file, origin of this issue. I have deleted HAS, using...
  • Darrell Hanning: Awesome information, and very well presented! Stopped thinking I had screwed up in my migration, and...
  • Osama mustafa: Thanks for sharing, you need to confrim with Oracle Support about modify Hidden Parameter as you know...
  • Jaspreet: Brilliant explanation.
  • Yousuf: Very Nice… Just wanted to check you have done all patching at Node 1 only.. is there any thing need to...
  • Yousuf: Very Nice.. Thanks for sharing.. Once question.. You have executed all commands on Node 1 only.. Is there any...
  • Emir: Thanks… Great article
  • borse firmate: Thank you for another informative blog. The place else may just I am getting that kind of information...
  • leandro: why this parameter is systemwide? could you read from a asm instance from one failure group and from the...
  • Mohammad: paul, we create pfile from target database to source database and later we change database name, and...
  • Muhammad Ikram: Thanks Brother for sharing pearls of knowledge. May ALLAH reward you for this both here and...
  • rgrover: Thanks for the POST. I recently encounter similar issue. Your POST helped.
  • gopalredy: really its very use full to dbas
  • Vivian: This is awesome! Thank you so much!
  • henry zhong: CDB=DB, and PDB=SCHEMA but in a sub dictionary?