Installing Oracle Enterprise Manager 10g Grid Control Release 3 on Linux x86


by John Smiley

Learn the basics of installing Oracle Enterprise Manager Grid Control 10g Release 3 on Red Hat Enterprise Linux 4 or Novell SUSE Linux Enterprise 9 from the bare metal up (for evaluation purposes only).

Contents
Overview
Part I: Installing Linux
    RHEL4
    SLES9
Part II: Configuring Linux for Oracle
    Verify System Requirements
    Create Directories
    Create the Oracle Groups and User Account
    Set Shell Limits for the oracle User
Part III: Installing Oracle
    Install the Software
Conclusion

Published March 2007


Overview

The guide provides a walk through of installing Oracle Enterprise Manager Grid Control 10g Release 3 on commodity hardware for the purpose of evaluation.  If you are new to Linux and/or Oracle, this guide is for you. It starts with the basics and walks you through an installation of Oracle Enterprise Manager Grid Control 10g Release 3 from the bare metal up.

This guide will take the approach of offering the easiest paths, with the fewest number of steps for accomplishing a task.  This approach often means making configuration choices that would be inappropriate for anything other than an evaluation.  For that reason, this guide is not appropriate for building production-quality environments, nor does it reflect best practices.

The  Linux distributions certified for Oracle Enterprise Manager Grid Control 10g Release 3 are:

  • Red Hat Enterprise Linux  4 (RHEL4)
  • Novell SUSE Linux Enterprise Server 9 (SLES9)

We will cover both of these distributions. Although Oracle Enterprise Linux is not explicitly covered here, the steps involved should mirror those required for RHEL4.

This guide is divided into three parts: Part I covers the installation of the Linux operating system, Part II covers configuring Linux for Oracle and Part III discusses the essentials of installing the Oracle Enterprise Manager Grid Control. 


Part I: Installing Linux

Hardware used for this walk through:

  • 2.5GHz P4 CPU
  • 2GB of RAM
  • Four SCSI disk drives (1 x 9GB + 3 x 36GB)
  • One Gig-E (1000 Base-T) Ethernet adapter

Your hardware does not have to match this in order to use this guide.  All that is necessary for a basic install is a single CPU, 2GB of RAM, a network interface controller (NIC), and one disk drive (IDE, SCSI, or FireWire) with at least 4.5GB of free space.

Now, let's walk through the process of installing the Linux operating system on a server. The instructions assume a fresh install of Linux (as opposed to an upgrade), that the server will be dedicated to Oracle, and that no other operating systems or data are on the server.


RHEL4

Oracle Enterprise Manager Grid Control 10g Release 3 is certified to run on Red Hat Enterprise Linux 4 (ES or AS) Update 1 or later. (Free evaluation copies of RHEL4 are available for download.) If you have update CDs, you can use the boot CD from the update instead of the boot CD from the base release to automatically apply all updates during the installation. All updates from Red Hat are supported by Oracle.

The easiest and fastest way to apply the updates for a fresh install of Linux is to perform the install by using the update CDs. If Linux is already installed or you don't have the updates on CDs, they can be applied through RHN. Because this guide is designed for a fresh Linux install, you'll use the update CDs.

  1. Boot the server using the first CD.
    • You may need to change your BIOS settings to allow booting from the CD.
  2. The boot screen appears with the boot: prompt at the bottom of the screen.
    • Select Enter to continue with a graphical install on the console. (For other installation methods and options, refer to the Red Hat Installation Guide.)
    • The installer scans your hardware, briefly displays the Red Hat splash screen, and then begins a series of screen prompts.
  3. Language Selection
    • Accept the default.
  4. Keyboard Configuration
    • Accept the default.
  5. Welcome Screen
    • Click on Next.
  6. Disk Partitioning Setup
    • A thorough treatment of disk partitioning is beyond the scope of this guide, which assumes that you are familiar with disk partitioning methods.

      (WARNING: Improperly partitioning a disk is one of the surest and fastest ways to wipe out everything on your hard disk. If you are unsure how to proceed, stop and get help, or you will risk losing data!)

      This guide uses the following partitioning scheme, with ext3 for each filesystem:

      The first disk (/dev/sda) will hold all Linux and Oracle software and contains the following partitions:
      - 100MB /boot partition
      -2,048MB swap partition—Set this to at least twice the amount of RAM in the system but to no more than 2GB. (Thirty-two-bit systems do not support swap files larger than 2GB.) If you need more than 2GB of swap space, create multiple swap partitions.
      -7,150MB root partition—This partition will be used for everything, including /usr, /tmp, /var, /opt, /home, and more. This approach is purely to simplify installation for the purposes of this guide. A more robust partitioning scheme would separate these directories onto separate filesystems.

      One of the 36GB disks (/dev/sdb) was configured with a single partition containing an ext3 file system mounted as /u01.  This file system will be used for the Oracle software and database.

  7. Boot Loader Configuration
    • Accept the default.
  8. Network Configuration
    • It is usually best to configure servers with a static IP address. To do so, click on Edit .
    • A pop-up window appears. Uncheck the Configure using DHCP box, and enter the IP Address and Netmask for the server. Be sure that Activate on boot is checked, and click on OK .
    • In the Hostname box, select manually and enter the hostname.
    • In the Miscellaneous Settings box, enter the remaining network settings.
  9. Firewall Configuration
    • For the purposes of this walk-through, no firewall is configured. Select No firewall
    • Select Disabled on the "Enable SELinux" drop down list. 
    • Click on Proceed when the "Warning - No Firewall" window appears.
  10. Additional Language Support
    • Accept the default.
  11. Time Zone Selection
    • Choose the time settings that are appropriate for your area. Setting the system clock to UTC is usually a good practice for servers. To do so, click on System clock uses UTC.
  12. Set Root Password
    • Enter a password for root, and enter it again to confirm.
  13. Package Installation Defaults
    • Select Customize software packages to be installed.
  14. Package Group Selection
    • Select only the package sets shown here and leave all others unselected. 
    • Desktop
      • X Window System
      • Gnome
    • Applications
      • Graphical Internet (optional)
    • Servers
      • Do not select anything in this group.
    • Development
      • Development Tools
    • System
      • Administration Tools
      • System Tools
        • Add the package 'sysstat' by clicking on the Details link and selecting "sysstat - The sar an iostat system monitoring commands." from the Optional Packages list.
    • Miscellaneous
      • Do not select anything in this group.
    • Click on Next to proceed.
  15. Installing Packages
    • Software will be copied to the hard disk and installed. Change disks as prompted.
  16. Congratulations
    • Remove the installation media from the system, and click on Reboot .
  17. The system automatically reboots and presents a new welcome screen.
    • Click on Next.
  18. License Agreement
    • Read the license agreement. If you agree to the terms, select Yes, I agree to the License Agreement and click on Next.
  19. Date and Time
    • Set the Date and Time.
    • If you want to use an NTP server (recommended), select Enable Network Time Protocol and enter the name of the NTP server.
  20. Display
    • Accept the defaults or change as required.
  21. Red Hat Login
    • Enter your Red Hat Network login and password or create a new one.
  22. System User
    • Create an account for yourself.
    • Do not create an account for oracle at this time. Creating the oracle account is covered later in this section.
  23. Additional CDs
    • Click on Next.
  24. Finish Setup
    • Click on Next.
  25. A graphical login screen appears.
  26. Congratulations! Your RHEL4 software is now installed.

Verifying Your Installation

Once you've completed the steps above, all of the packages required for Oracle Enterprise Manager Grid Control 10g Release 3 will have been installed.  Verify this using the example below.

Required package versions (or later):
  • glibc-2.3.4-2.9
  • make-3.79
  • binutils-2.15.92.0.2-13
  • gcc-3.4.3-22.1
  • libaio-0.3.96
  • glibgc-common-2.3.4-2.9
  • setarch-1.6-1
  • pdksh-5.2.14-30
  • openmotif21-2.1.30-11
  • sysstat-5.0.5-1
  • gnome-libs-1.4.1.2.90-44.1
  • libstdc++-3.4.3-22.1
  • libstdc++devel-3.4.3-22.1
  • compat-libstdc++-296-2.96-132.7.2
  • compat-db-4.1.25-9
  • control-center-2.8.0-12
  • xscreensaver-4.18-5.rhel4.2
To see which versions of these packages are installed on your system, run the following command:
rpm -q glibc make binutils gcc libaio glibc-common
setarch pdksh openmotif21 sysstat \

gnome-libs libstdc++ libstdc++-devel compat-libstdc++-296
compat-db control-center xscreensaver


Ex: 
# rpm -q glibc make binutils gcc libaio glibc-common
setarch pdksh openmotif21 sysstat \

> gnome-libs libstdc++ libstdc++-devel compat-libstdc++-296
compat-db control-center xscreensaver

glibc-2.3.4-2.13
make-3.80-5
binutils-2.15.92.0.2-15
gcc-3.4.4-2
libaio-0.3.103-3
glibc-common-2.3.4-2.13
setarch-1.6-1
pdksh-5.2.14-30.3
openmotif21-2.1.30-11.RHEL4.4
sysstat-5.0.5-1
gnome-libs-1.4.1.2.90-44.1
libstdc++-3.4.4-2
libstdc++-devel-3.4.4-2
compat-libstdc++-296-2.96-132.7.2
compat-db-4.1.25-9
control-center-2.8.0-12.rhel4.2
xscreensaver-4.18-5.rhel4.9





SLES9

Oracle Enterprise Manager Grid Control 10g Release 3 is certified to run on SLES9 Service Pack 2 (SP2) or above. Service Packs and package updates are available from Novell, either on CDs or online via its support portal. In this guide, we will install on the SLES9 base release.

  1. Boot the server, using the SLES9 CD.
    • You may need to change your BIOS settings to allow booting from the CD.
  2. The Novell SLES installation screen appears.
    • Select Installation.
    • The installer scans your hardware and presents the YaST interface.
  3. Language Selection
    • Accept the license agreement.
    • Accept the default, English (US).
  4. Installation Settings
    • Select New Installation.
  5. Partitioning
    • A thorough treatment of disk partitioning is beyond the scope of this guide, which assumes that you are familiar with disk partitioning methods.

      (WARNING: Improperly partitioning a disk is one of the surest and fastest ways to wipe out everything on your hard disk. If you are unsure how to proceed, stop and get help, or you will risk losing data!)

      This guide uses the following partitioning scheme, with ext3 for each filesystem:

      The first disk (/dev/sda) will hold all Linux and Oracle software and contains the following partitions:
      - 100MB /boot partition
      -2,048MB swap partition—Set this to at least twice the amount of RAM in the system but to no more than 2GB. (Thirty-two-bit systems do not support swap files larger than 2GB.) If you need more than 2GB of swap space, create multiple swap partitions.
      -7,150MB root partition—this partition will be used for everything, including /usr, /tmp, /var, /opt, /home, and more. This approach is purely to simplify installation for the purposes of this guide. A more robust partitioning scheme would separate these directories onto separate filesystems.

      One of the 36GB disks (/dev/sdb) was configured with a single partition containing an ext3 file system mounted as /u01.  This file system will be used for the Oracle software and database.

  6. Software
    • Click on the link for Software.
    • The Software Selection screen appears.
    • Click on Detailed Selection.
    • The left-hand window displays a list of software selections. Click on the box next to each selection to select/deselect it.
    • Select the following software (this is the recommended set; all others should be deselected):
      - Basis Runtime System
      - YaST
      - Graphical Base System
      - Linux Tools
      - C/C++ Compiler and Tools
      - Basis Sound Libraries and Tools
      - GNOME System
      - Analyzing Tools
    • It is recommended that the following items not be installed, as they may conflict with Oracle products providing the same service:
      - Simple Webserver
      - Authentication Server (NIS, LDAP, Kerberos)
    • Install openmotif21-libs and gnome-libs-devel
      - Change the Filter selection at the top to "Package Groups"
      - Scroll down and select System --> Libraries
      - In the right-hand window, scroll down and select openmotif21-libs
    • Click on Accept
  7. Time Zone
    • Set your time zone.
  8. Click on Accept.
  9. A warning box appears. Click on Yes, install when ready to proceed.
  10. Change CDs as prompted by the installer.
  11. Confirm Hardware Detection
    • Network Cards – Click on OK.
  12. Password for "root." the system administrator.
    • Enter the root password and repeat to confirm.
  13. Configure your network interface(s), and click on Next when ready to proceed.
    • Static IP addresses are recommended for servers.
    • There is no need to configure printers, modems, ISDN adapters, or sound in order to build an Enterprise Manager server.
  14. Test Internet Connection
    • There is no need to connect to the Internet to download release notes or Linux updates. Select No, Skip This Test.
  15. Service Configuration
    • There is no need to configure CA Management or OpenLDAP Server. Select Skip Configuration.
  16. User Authentication Method
    • Select Local(/etc/passwd).
  17. Add a New Local User
    • Create an account for yourself. Do not create the oracle account at this time; we'll do that later.
  18. Release Notes
    • Click on Next
  19. Hardware Configuration
    • Confirm Hardware Detection – Graphics Cards – click on Continue.
    • There is no need to configure sound cards  – click on Skip.
    • If the graphics card and monitor have been successfully detected, click on Next. Otherwise, click on the Graphics Cards link and enter the correct information.
  20. Installation Completed
    • Click on Finish.
  21. Congratulations! Your SLES9 software is now installed.
Verifying Your Installation

Once you've completed the steps above, all of the packages required for Oracle Enterprise Manager Grid Control 10g Release 3 will have been installed.  Verify this using the example below.

Required package versions (or later):
  • glibc-2.2.4-31.7
  • gcc-2.96
  • openmotif21-libs-2.1.30MLI4-119.1 (Note:  The Oracle supplied installation docs specify openmotif21-libs-2.1.30-11.  This package does not exist in SLES9.  Use the openmotif21-libs package instead).
  • make-3.79
  • binutils-2.11.90.0.8-12
To see which versions of these packages are installed on your system, run the following command as root:
rpm -q glibc gcc openmotif21-libs make binutils

Ex:
# rpm -q glibc gcc openmotif21-libs make binutils
glibc-2.3.3-98.47
gcc-3.3.3-43.34
openmotif21-libs-2.1.30MLI4-119.4
make-3.80-184.1
binutils-2.15.90.0.1.1-32.10
If any of the package versions on your system are missing or the versions are earlier than those specified above, you can download and install the updates from the Novell SUSE Linux Portal.

Additional steps for SLES9 only:

Create the following symbolic links:
ln -sf /usr/bin/perl /usr/local/bin/perl
ln -sf /bin/fuser /sbin/fuser
Edit /etc/hosts to remove "localhost" from the IPV6 address list.

Before:
# special IPv6 addresses
::1             localhost ipv6-localhost ipv6-loopback

After:
# special IPv6 addresses
::1              ipv6-localhost ipv6-loopback



Part II: Configuring Linux for Oracle

Now that the Linux software is installed, you need to configure it for Oracle. This section walks through the steps required to configure Linux for Oracle Enterprise Manager Grid Control 10g Release 3.

Verifying System Requirements

To verify that your system meets the minimum requirements for a Oracle Enterprise Manager Grid Control 10g Release 3, log in as root and run the commands below.

To check the amount of RAM and swap space available, run this:
grep MemTotal /proc/meminfo
grep SwapTotal /proc/meminfo

Ex:
# grep MemTotal /proc/meminfo
MemTotal: 2083256 kB
# grep SwapTotal /proc/meminfo
SwapTotal: 4194304 kB

The minimum RAM required is 2GB, and the minimum required swap space is 4GB. Swap space should be twice the amount of RAM for systems with 2GB of RAM or less and between one and two times the amount of RAM for systems with more than 2GB.

You also need 4.5GB of available disk space for the Oracle Enterprise Manager Grid Control 10g Release 3 software. The /tmp directory needs at least 400MB of free space. To check the available disk space on your system, run the following command:

df -h

Ex:
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 6.8G 1.3G 5.2G 20% /
/dev/sda1 99M 17M 77M 18% /boot
/dev/sdb1 36G 232M 99% /u01

The example shows that the /tmp directory does not have its own filesystem. (It's part of the root filesystem for this guide.)

Configuring the Linux Kernel Parameters

Oracle Enterprise Manager 10g Release 3 requires the kernel parameter settings shown below. The values given are minimums, so if your system uses a larger value, don't change it.

Red Hat Enterprise Linux 4

kernel.sem = 250 32000 100 128
kernel.shmmax = 536870912
kernel.shmmni = 4096
kernel.shmall = 2097152
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default=262144
net.core.wmem_default=262144
net.core.rmem_max=262144
net.core.wmem_max=262144

SUSE Linux Enterprise Server 9

kernel.sem = 250 32000 100 128
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.shmall = 2097152
fs.file-max = 65536

Note:  The Oracle supplied documentation indicates that kernel.shmmin should be set to 1 and that kernel.shmseg should be set to 10.  The shmmin and shmseg parameters cannot be changed in /etc/sysctl.conf in SLES9 and are built into the kernel.  If you are using a pre-built kernel provided by Novell, the default values for these parameters are adequate.  See MetaLink Note: 345052.1 for more information.

If you have just installed Linux, the kernel parameters will all have their default values and you can just cut and paste the following commands while logged in as root. 

Red Hat Enterprise Linux 4

cat >> /etc/sysctl.conf <<EOF
kernel.sem = 250 32000 100 128
kernel.shmmax = 536870912
kernel.shmmni = 4096
kernel.shmall = 2097152
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default=262144
net.core.wmem_default=262144
net.core.rmem_max=262144
net.core.wmem_max=262144
EOF
/sbin/sysctl -p

Ex:
# cat >> /etc/sysctl.conf <<EOF
> kernel.sem = 250 32000 100 128
> kernel.shmmax = 536870912
> kernel.shmmni = 4096
> kernel.shmall = 2097152
> fs.file-max = 65536
> net.ipv4.ip_local_port_range = 1024 65000
> net.core.rmem_default=262144
> net.core.wmem_default=262144
> net.core.rmem_max=262144
> net.core.wmem_max=262144
> EOF
# /sbin/sysctl -p
net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.sysrq = 0
kernel.core_uses_pid = 1
kernel.sem = 250 32000 100 128
kernel.shmmax = 536870912
kernel.shmmni = 4096
kernel.shmall = 2097152
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default = 262144
net.core.wmem_default = 262144
net.core.rmem_max = 262144
net.core.wmem_max = 262144

SUSE Linux Enterprise Server 9

cat >> /etc/sysctl.conf <<EOF
kernel.sem = 250 32000 100 128
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.shmall = 2097152
fs.file-max = 65536
EOF
/sbin/sysctl -p
/sbin/chkconfig boot.sysctl on

Red Hat and SUSE

Run the following commands as root to verify your settings:

/sbin/sysctl -a | grep shm
/sbin/sysctl -a | grep sem
/sbin/sysctl -a | grep file-max
/sbin/sysctl -a | grep ip_local_port_range
/sbin/sysctl -a | grep rmem_default
/sbin/sysctl -a | grep rmem_max
/sbin/sysctl -a | grep wmem_default
/sbin/sysctl -a | grep wmem_max

Ex:
# /sbin/sysctl -a | grep shm
kernel.shmmni = 4096
kernel.shmall = 2097152
kernel.shmmax = 536870912
kernel.shm-use-bigpages = 0
# /sbin/sysctl -a | grep sem
kernel.sem = 250 32000 100 128
# /sbin/sysctl -a | grep file-max
fs.file-max = 65536
# /sbin/sysctl -a | grep ip_local_port_range
net.ipv4.ip_local_port_range = 1024 65000
# /sbin/sysctl -a | grep rmem_default
net.core.rmem_default = 262144
# /sbin/sysctl -a | grep rmem_max
net.core.rmem_max = 262144
# /sbin/sysctl -a | grep wmem_default
net.core.wmem_default = 262144
# /sbin/sysctl -a | grep wmem_max
net.core.wmem_max = 262144

Create the Oracle Groups and User Account

Next, create the Linux groups and user account that will be used to install and maintain the Oracle Enterprise Manager Grid Control 10g Release 3 software. The user account will be called oracle, and the group will be oinstall. Execute the following commands as root:

/usr/sbin/groupadd oinstall
/usr/sbin/useradd -m -g oinstall oracle
id oracle

Ex:
# /usr/sbin/groupadd oinstall
# /usr/sbin/useradd -m -g oinstall oracle
# id oracle
uid=501(oracle) gid=502(oinstall) groups=502(oinstall)

Set the password on the oracle account:

passwd oracle

Ex:
# passwd oracle
Changing password for user oracle.
New password:
Retype new password:
passwd: all authentication tokens updated successfully.

Create Directories

Now create directories to store the Oracle Enterprise Manager Grid Control 10g Release 3 software and its files.

The following assumes that the directories are being created in the root filesystem. This is done for the sake of simplicity and is not recommended as a general practice. These directories would normally be created as separate filesystems.

Issue the following commands as root:

mkdir -p /u01/app/oracle
chown -R oracle:oinstall /u01/app/oracle
chmod -R 775 /u01/app/oracle

Setting Shell Limits for the oracle User

Oracle recommends setting limits on the number of processes and open files each Linux account may use. To make these changes, cut and paste the following commands as root:

cat >> /etc/security/limits.conf <<EOF
* soft nproc 2047
* hard nproc 16384
* soft nofile 2048
* hard nofile 65536
EOF

cat >> /etc/pam.d/login <<EOF
session required /lib/security/pam_limits.so
EOF

For RHEL4, use the following:

cat >> /etc/profile <<EOF
if [ \$USER = "oracle" ]; then
if [ \$SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
umask 022
fi
EOF

cat >> /etc/csh.login <<EOF
if ( \$USER == "oracle" ) then
limit maxproc 16384
limit descriptors 65536
umask 022
endif
EOF

For SLES 9, use the following:

cat >> /etc/profile.local <<EOF
if [ \$USER = "oracle" ]; then
if [ \$SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
umask 022
fi
EOF

cat >> /etc/csh.login.local <<EOF
if ( \$USER == "oracle" ) then
limit maxproc 16384
limit descriptors 65536
umask 022
endif
EOF


Part III: Installing Oracle Enterprise Manager Grid Control 10g Release 3

Installing Oracle Enterprise Manager Grid Control 10g Release 3 is a two step process.  First, install OEM Grid Control 10g Release 2, then upgrade Release 2 to Release 3.  Please note that there is no way to directly install Release 3.  

Both OEM Grid Control 10g Release 2 and the Release 3 upgrade software for Linux can be downloaded from OTN. Oracle offers a development and testing license free of charge. However, no support is provided and the license does not permit production use. A full description of the license agreement is available on OTN.

The easiest way to make the Oracle Enterprise Manager Grid Control 10g Release 3 distribution media available on your server is to download them directly to the server.

Use the graphical login to log in as oracle.

Create a directory to contain the Oracle Enterprise Manager Grid Control 10g Release 2 distribution:

mkdir grid10gR2

Download Oracle Enterprise Manager Grid Control 10g Release 2 from OTN, then unzip and extract the files:

cd grid10gR2
unzip Linux_Grid_Control_full_102010_disk1.zip
unzip Linux_Grid_Control_full_102010_disk2.zip
unzip Linux_Grid_Control_full_102010_disk3.zip

Next, create a directory to contain the Oracle Enterprise Manager Grid Control 10g Release 3 upgrade distribution:

mkdir grid10gR3

After downloading Oracle Enterprise Manager Grid Control 10g Release 3 from OTN, unzip and extract the file:

cd grid10gR3
unzip GridControl_10.2.0.3_Linux.zip

Install the Enterprise Manager Grid Control Software

Log in using the oracle account.

For SLES9 only, set the LD_ASSUME_KERNEL environment variable to 2.4.21
Ex:
LD_ASSUME_KERNEL=2.4.21; export LD_ASSUME_KERNEL

Change directory to the location where you extracted the Oracle Enterprise Manager Grid Control 10g Release 2 software.
Ex:
$ cd grid10gR2

Start the Oracle Universal Installer.

$ ./runInstaller
  1. Specify Installation Type
    • Select Enterprise Manager 10g Grid Control Using a New Database
    • Click on Next
  2. Specify Installation Location
    • Parent Directory:  /u01/app/oracle
      Note:  No part of this path may include symbolic links.  Use of symbolic links in the parent directory path will lead to a failed installation.  This is a known bug and will be fixed in a future release.
    • Click on Next
  3. Specify Inventory Directory and Credentials
    • Inventory Directory: /u01/app/oracle/oraInventory
    • Operating System group name:  oinstall
    • Click on Nexttr
  4. Product-specific Prerequisite Checks
    • The operating system package requirements used by the Installer are different from those given in the documentation.  If you have followed the instructions in this guide and still get a status of Warning for this item, click the check box between the Type and Status columns.  The Status will change to User Verified and you will be allowed to continue.
    • Click on Next
  5. Specify Configuration
    • If necessary, change the Database Administrator (OSDBA) group and Database Operator (OSOPER) group to oinstall
    • Click on Next
  6. Specify Optional Configuration
    • Optional:  if you have a MetaLink account, select Configure Metalink and enter your MetaLink user name and password.
    • Click on Next
  7. Specify Security Options
    • Management Service Security
      • Enter a password and confirm
    • Repository Database Passwords
      • Select Use the same password for all accounts
      • Enter a password and confirm
    • Click on Next
  8. Privileged Operating System Groups
    • If necessary, change the Database Administrator (OSDBA) group and Database Operator (OSOPER) group to oinstall
    • Click on Next
  9. Summary
    • Click on Install
  10. Install
    • The Oracle Universal Installer will install the following three products.  No action is necessary on your part.
      • Oracle Database
      • Oracle Management Service
      • Oracle Management Agent
  11. Execute Configuration Scripts
    • At the end of the installation, a pop up window will appear indicating that scripts need to be run as root.  Login as root and run the indicated scripts.
    • Click on OK when finished.
  12. Configuration Assistants
    • The configuration assistants should succeed without any action on your part.
  13. End of Installation
    • Make note of the URLs presented in the summary, and click on Exit when ready.
This completes the installation of Oracle Enterprise Manager Grid Control 10g Release 2.  Now proceed to the next section to upgrade to OEM Grid Control 10g Release 3.

Upgrading OEM Grid Control 10g Release 2 to Release 3
There are now three components installed on the host, each with its own ORACLE_HOME:
  1. Repository
    ORACLE_HOME=/u01/app/oracle/db10g
  2. Oracle Management Service (OMS)
    ORACLE_HOME=/u01/app/oracle/oms10g
  3. Management Agent
    ORACLE_HOME=/u01/app/oracle/agent10g

The OEM Grid Control 10g Release 3 pach must be applied to both the OMS and Agent components.  The repository is automatically upgraded when the OMS is upgraded.

Before upgrading to OEM Grid Control 10g Release 3, stop OEM Grid Control Release 2 using the following command as root.  This will stop all three components (repository, OMS, and agent.:
# /etc/init.d/gcstartup stop

Change directory to the location where you extracted the Oracle Enterprise Manager Grid Control 10g Release 3 software.
$ cd grid10gR3

Before upgrading the OMS to Release 3, the database requires a patch. Install the patch using the OPatch utility as shown in the example below.

Unzip the database patch.
$
unzip p4329444_10104_LINUX.zip

Change directories to the patch directory.
$
cd 4329444

Set the ORACLE_HOME environment variable for the database.
$
export ORACLE_HOME=/u01/app/oracle/db10g

Run the OPatch utility to apply the patch.
$ $ORACLE_HOME/OPatch/opatch apply

Invoking OPatch 10.2.0.1.0

Oracle interim Patch Installer version 10.2.0.1.0
Copyright (c) 2005, Oracle Corporation. All rights reserved..


Oracle Home : /u01/app/oracle/db10g
Central Inventory : /u01/app/oracle/oraInventory
from : /u01/app/oracle/db10g/oraInst.loc
OPatch version : 10.2.0.1.0
OUI version : 10.2.0.1.0
OUI location : /u01/app/oracle/db10g/oui
Log file location : /u01/app/oracle/db10g/cfgtoollogs/opatch/opatch-2007_Feb_11_16-51-12-PST_Sun.log

ApplySession applying interim patch '4329444' to OH '/u01/app/oracle/db10g'
Invoking fuser to check for active processes.
Invoking fuser on "/u01/app/oracle/db10g/bin/oracle"

OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.


Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/u01/app/oracle/db10g')

Is the local system ready for patching?

Do you want to proceed? [y|n]
y
User Responded with: Y
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '4329444' for restore. This might take a while...
Backing up files affected by the patch '4329444' for rollback. This might take a while...

Patching component oracle.rdbms, 10.1.0.4.0...
Updating archive file "/u01/app/oracle/db10g/lib/libserver10.a" with "lib/libserver10.a/qerix.o"
Running make for target ioracle
ApplySession adding interim patch '4329444' to inventory

The local system has been patched and can be restarted.


OPatch succeeded.

Start the repository database and listener using the following command as root.
# /u01/app/oracle/db10g/install/unix/scripts/seedstup startup

Return to the previous directory and unzip the OEM 10g Release 3 patch.
$ cd ..
$ unzip p3731593_10203_linux.zip

Change directories to the Disk1 subdirectory of the patch.
$ cd 3731593/Disk1

Apply the Release 3 patch to the OMS component

Set the ORACLE_HOME environment variable to the OMS home.
$ export ORACLE_HOME=/u01/app/oracle/oms10g

Start the Oracle Universal Installer.

./runinstaller
  1. Specify Home Details
    • Name:  Select the OMS Oracle Home (ex: oms10g)
    • Path:  Verify the path is correct (ex: /u01/app/oracle/oms10g)
    • Click on Next
  2. Repository Database Administrator Password
    • SYS Password:  Enter the SYS password for the repository database
    • Click on Next
  3. Oracle Configuration Manager Registration (Optional)
    • Click on Enable Oracle Configuration Manager
    • Accept the License Agreement
    • Enter your MetaLink CSI number and username
    • Click on Next
  4. Summary
    • Click on Install
  5. Configuration Assistants
    • Wait until all of the configuration assistants have completed.  This may take a while.
  6. End of Installation
    • Click on Exit

Apply the Release 3 patch to the Management Agent component

Set the ORACLE_HOME environment variable to the Agent home.
$ export ORACLE_HOME=/u01/app/oracle/agent10g

Start the Oracle Universal Installer.

./runinstaller
  1. Specify Home Details
    • Name:  Select the Agent Oracle Home (ex: agent10g)
    • Path:  Verify the path is correct (ex: /u01/app/oracle/agent10g)
    • Click on Next
  2. Oracle Configuration Manager Registration (Optional)
    • Click on Enable Oracle Configuration Manager
    • Accept the License Agreement
    • Enter your MetaLink CSI number and username
    • Click on Next
  3. Summary
    • Click on Install
  4. End of Installation
    • Click on Exit

Oracle Enterprise Manager Grid Control 10g Release 3 is now installed and ready for use.


Conclusion

Now that your Oracle Enterprise Manager Grid Control 10g Release 3 environment is up and running, you can begin exploring the many new features offered in this release.  If you're unsure where to begin, chapter 10, "Getting Started with Enterprise Manager" of the Oracle Enterprise Manager Grid Control Installation and Basic Configuration Guide, is a good place to start.  More information is available within the Oracle Enterprise Manager Documentation Library.  OTN also has a number of guides designed to help you get the most out of Oracle Enterprise Manager Grid Control 10g Release 3. 


John Smiley [jrsmiley@gmail.com] works as a senior database engineer for a major online retailer and is an Oracle Certified Master DBA with 20 years of experience with Oracle databases running on all major platforms.  He specializes in engineering high volume, high availability database systems.
E-mail this page
Printer View Printer View
Oracle Is The Information Company About Oracle | Oracle RSS Feeds | Careers | Contact Us | Site Maps | Legal Notices | Terms of Use | Privacy