2 Pre-Installation Requirements

Recommended CPU and Memory Allocation for Enterprise Manager Deployments

Table 2–2 and Table 2–3 approximate the host, CPU, and physical memory requirements for a first-time Enterprise Manager installation (typical scenario with 2 - 3 GHz machines), based on experiences with real-world Enterprise Manager deployments.

Temporary Disk Space Requirements on HP-UX

To determine the amount of free disk space available in the /tmp directory, enter the following command:

# bdf /tmp

If there is less than 1.2 GB of disk space available in the /tmp directory, then complete one of the following steps:

• Delete unnecessary files from the /tmp directory.

• Set the TEMP and TMPDIR environment variables to a writable directory with at least 1.2 GB of available disk space.

• Extend the file system that contains the /tmp directory. If required, contact your system administrator for information about extending file systems.

Resource Allocation Considerations

Carefully consider resource allocation when choosing the disk on which to install the Management Service and Management Repository database. Enterprise Manager's out-of-box monitoring starts generating information upon installation, meaning that resource consumption begins immediately. As such, consider the base system resource consumption prior to installing. Select your installation locations strategically, taking into account system load, memory usage, and disk input/output.

For example, you can split the input/output load across disks. Avoid installing the Management Repository database or the Management Service on the swap volume, a volume with a busy state (as per iostat) of 10% or more, or on a memory-constrained system. As with any data-intensive application, if your Management Repository is going to service a large number of targets, it is important to tune the database appropriately to maximize input/output capacity. Refer to the Database Performance Tuning Guide for more information.

While adding more resources can help alleviate potential problems (for instance, adding a second disk spindle dedicated to the Management Service on a system), understanding and accounting for resource allocation is the best way to achieve strategic setup and good performance.

Operating System Certifications

The operating system platforms certified for Enterprise Manager Grid Control components are the following:

Refer to the Oracle Technology Network Website's "Certify and Availability" page for the latest information on all supported platforms.

Browser Certifications for the Enterprise Manager Console

The browser versions that are certified for viewing the Grid Control console are:

• Internet Explorer 6.0 (SP2)

• Netscape 7.2

• Mozilla 1.7

• Firefox 1.0.4

• Safari 1.2

Certified Enterprise Manager Targets

Table 2-5 identifies the Oracle targets and components that Enterprise Manager Grid Control can manage.

Required Packages on Linux

The following (or later) packages must be running on your Linux systems.

Red Hat Enterprise Linux 3.0

• glibc-2.2.4-31.7

• make-3.79

• binutils-2.11.90.0.8-12

• gcc-2.96

• openmotif21-2.1.30-11

Red Hat Enterprise Linux 4.0

• 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

SUSE Linux Enterprise Server 9

• glibc-2.2.4-31.7

• make-3.79

• binutils-2.11.90.0.8-12

• gcc-2.96

• openmotif21-2.1.30-11

Required Packages on Solaris

The following (or later) package versions must be running on your Solaris systems:

• SUNWarc

• SUNWbtool

• SUNWhea

• SUNWlibm

• SUNWlibms

• SUNWsprot

• SUNWsprox

• SUNWtoo

• SUNWi1of

• SUNWxwfnt

To check if the required operating system packages have been installed on your system, enter the following command:

prompt> pkginfo SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprot SUNWsprox SUNWtoo SUNWi1 of SUNWxwfnt

Checking for 32-bit and 64-bit Application Support

Check whether your system is configured to support 32-bit and 64-bit applications by entering the following command:

prompt> /usr/bin/isainfo -v

Checking for Patches

To determine the patches that have been installed on a Solaris system, follow these steps:

1. Run the showrev command with the -p option. The following command saves the sorted output to a file called patchList.

2. Enter the following command:

   prompt> showrev -p | sort > patchList
    
   

3. Open the file in a text editor and search for the patch numbers.

Required Packages on HP-UX

The following (or later) package versions must be running on your HP-UX systems:

HP-UX 11i V1 (11.1)

• For installation on HP-UX 11.11, the following packages or later versions are required:

  • HP-UX 11i June 2003 Consolidated Quality Patch Bundle

  • Jun03GQPK11i_Aux_Patch

• Make sure that Motif 2.1 Development Environment (X11MotifDevKit.MOTIF21-PRG)B.11.11.01 is installed

  Either install this package or create symbolic links as follows:

  1. Log in as root.

  2. Change directory to /usr/lib as follows:

     # cd /usr/lib

  3. Create the required links:

     # ln -s libX11.3 libX11.sl
     # ln -s libXIE.2 libXIE.sl
     # ln -s libXext.3 libXext.sl
     # ln -s libXhp11.3 libXhp11.sl
     # ln -s libXi.3 libXi.sl
     # ln -s libXm.4 libXm.sl
     # ln -s libXp.2 libXp.sl
     # ln -s libXt.3 libXt.sl
     # ln -s libXtst.2 libXtst.sl
     
     

• The following patches or later are required:

  • PHCO_28123, cumulative SAM patch

  • PHKL_29198, Psets Enablement Patch

  • PHNE_28476, Cumulative STREAMS Patch

  • PHNE_28923, LAN product cumulative patch

  • PHSS_28871, ld(1) and linker tools cumulative patch

  • PHSS_28880, HP aC++ -AA runtime libraries (aCC A.03.50)

  • PHCO_26331, mountall cumulative patch

  • PHCO_29109, Pthread enhancement and fixes

  • PHKL_25468, eventport (/dev/poll) pseudo driver

  • PHKL_25842, Thread Abort

  • PHKL_25993, thread nostop for NFS, rlimit, Ufalloc fix

  • PHKL_25994, Thread NOSTOP, Psets Enablement, Ufalloc

  • PHKL_25995, eventport syscalls; socket close(2); ufalloc

  • PHKL_26468, Shared mutex synchronization support patch

  • PHKL_28489, copyin EFAULT, LDCD access type

• To determine whether a bundle, a product, or fileset is installed, enter a command similar to the following, where "level" refers to the bundle, patch or fileset.

  # /usr/sbin/swlist -l level |more

HP-UX 11i V2 (11.23)

• For installation on HP-UX 11.23, the following packages or later versions are required:

  • Patch Bundle for HP-UX 11i V2 (B.11.23), September 2004

  • BUNDLE11i, Revision B.11.23.0409.3

• The following patches or later are required:

  • PHSS_31849:linker + fdp cumulative patch

  • PHSS_31852: aC++ Runtime (PA A.03.61)

Required Packages on AIX

The follwoing packages must be running on your AIX systems:

AIX 5L Version 5.2

The following filesets must be installed and committed:

• bos.adt.base

• bos.adt.lib

• bos.adt.libm

• bos.perf.libperfstat

• bos.perf.perfstat

• bos.perf.proctools

The following Authorized Problem Analysis Reports (APARs) must be installed:

• IY43980: libperfstat.h not ANSI-compliant

• IY44810: DSI IN BMRECYCLE

• IY45462: Definition of isnan() in math.h incorrect

• IY45707: J2 READAAHEAD/CIO INTERACTION

• IY46214: dropping partial connections leaves them on so_q0

• IY46605: exec of 32 bit application can fail on 64 bit kernel

• IY48525: SDK 1.4.1 32-BIT SR1: CA141-20030930

• IY51801: race condition in aio_nwait_timeout

• IY76141: CHILD PROCESS UNABLE TO LOAD A MODULE. (If AIX 5.2 Maintenance Level 07)

AIX 5L Version 5.3

The following filesets must be installed and committed:

• bos.adt.base

• bos.adt.lib

• bos.adt.libm

• bos.perf.libperfstat

• bos.perf.perfstat

• bos.perf.proctools

The following Authorized Problem Analysis Reports (APARs) must be installed:

• IY70159: KRTL relocation problem

• IY66513: Parsing of LDR_CNTRL value fails

• IY68989: write to mmapped space hangs

• IY76141: CHILD PROCESS UNABLE TO LOAD A MODULE. (If AIX 5.2 Maintenance Level 07)

# lslpp -l bos.adt.base bos.adt.lib bos.adt.libm \
bos.perf.perfstat bos.perf.libperfstat 

# /usr/sbin/instfix -i -k " IY43980, IY44810,..."

Kernel Parameter Requiements on Linux

The systems must have at least the following recommended kernel parameters:

Red Hat Enterprise Linux 3.0 and SUSE Linux Enterprise Server 9

• semmsl = 250

• semmns = 32000

• semopm = 100

• semmni = 128

• shmmax = 2147483648

• shmmni = 4096

• shmall = 2097152

• shmmin = 1

• shmseg = 10

• filemax = 65536

Red Hat Enterprise Linux 4.0

• semmsl = 250

• semmsl2 = 250

• semmns = 32000

• semopm = 100

• semmni = 128

• shmmax = 536870912

• shmmni = 4096

• shmall = 2097152

• filemax = 65536

• ip_local_port_range = 1024 65000

• rmem_default = 262144

• rmem_max = 262144

• wmem_default = 262144

• wmem_max = 262144

To check your kernel parameter settings, run the commands listed in the following table.

To change your kernel parameter settings, use any text editor to create or edit the /etc/sysctl.conf file to add or modify the necessary entries. You may need to reboot your system after changing kernel parameters.

For example, your /etc/sysctl.conf file may look like this:

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

By specifying the values in the /etc/sysctl.conf file, they persist when you restart the system.

On SUSE systems only, enter the following command to ensure that the system reads the /etc/sysctl.conf file when it restarts:

# /sbin/chkconfig boot.sysctl on

Kernel Parameter Requirements on Solaris

The system must have at least the following recommended kernel parameters:

Solaris 8 and 9

Verify that the following kernel parameters have been set to a equal to or greater than the value specified in this table:

Solaris 10

On Solaris 10, verify that the kernel parameters shown in the following table are set to values equal to or greater than the recommended values. The table also lists the resource controls that replace the /etc/system file for a specific kernel parameter.

# grep noexec_user_stack/etc/system
# /usr/sbin/sysdef | grep SEM
# /usr/sbin/sysdef | grep SHM

#id -p //to verify the project ID
uid = 0 (Root) gid = 0 (Root) projid = 1 (user.root)
#prctl -n project.max-shm-memory -i project user.root
#prctl -n project.max=sem-ids -i project user.root

Kernel Parameter Requirements on HP-UX

Verify that the kernel parameters listed in the table are set to the values greater than or equal to the recommended value shown. The procedure following the table describes how to verify and set the values.

Configure Shell Limits and System Configuration Parameters on AIX

On AIX systems, you do not need to configure the kernel parameters. However, Oracle recommends that you set shell limits and system configuration parameters as described in this section.

Management Repository Software Requirements

The embedded Oracle10g Database Release 1 (10.1.0.4), Enterprise Edition, is supported for Management Repository creation. Otherwise, you may only install the Management Repository in one of the following existing databases:

• Oracle 10g Database Release 1 (10.1.0.4 and higher), Enterprise Edition

  
  

  Note: If you are performing an Enterprise Manager Grid control installation using an existing database, ensure the database is of a 10.1.0.3 release or higher.

  
  

• Oracle 10g Real Application Clusters Database Release 1 (10.1.0.4 and higher)

  
  

  Note: If you are performing an Enterprise Manager Grid control installation using an existing database, ensure the existing RAC database is of a 10.1.0.3 release or higher.

  
  

• Oracle 9i Database Release 2 (9.2.0.6 and higher), Enterprise Edition

• Oracle 9i Real Application Clusters Database Release 2 (9.2.0.6 and higher)

Note that the Enterprise Edition database you use for the Management Repository must have fine-grained access control turned on.

When using an existing database for the repository, be sure that all software, patch, and tuning requirements are met for the existing database and host, as well as for the repository.

Management Service Software Requirements

The Management Service has no additional software requirements.

The Oracle Management Service is installed with and deployed on the Oracle Application Server. As a result, when you install the Oracle Management Service, the installation procedure first installs Oracle Application Server.

Specifically, the installation procedure installs the Oracle Application Server J2EE and Web Cache installation type. The Management Service is deployed on its own OC4J container in this application server instance.