| Oracle® Enterprise Manager Grid Control Quick Installation Guide for AIX 5L Based Systems (64-bit) 10g Release 2 (10.2) Part Number B28033-01 |
|
|
View PDF |
| Oracle® Enterprise Manager Grid Control Quick Installation Guide for AIX 5L Based Systems (64-bit) 10g Release 2 (10.2) Part Number B28033-01 |
|
|
View PDF |
Grid Control Quick Installation Guide
10g Release 2 (10.2)
B28033-01
April 2006
Oracle Enterprise Manager Grid Control Quick Installation Guide for AIX 5L Based Systems (64-bit), 10g Release 2 (10.2)
B28033-01
Copyright © 1996, 2006, Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, and PeopleSoft are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.
This guide describes how to quickly install Oracle Enterprise Manager Grid Control on AIX 5L Based Systems (64-bit). It includes information about the following:
This guide describes how to perform a basic installation of Oracle Enterprise Manager Grid Control into a new database or into an existing database.
The procedures in this guide describe how to:
Configure your system to support the following installation types:
"Enterprise Manager Grid Control Using a New Database" installation type, which installs the Management Service, central Management Agent, and Management Repository database on a single host
"Enterprise Manager Grid Control Using an Existing Database" installation type, which installs the Management Service and central Management Agent on one host, and installs the Management Repository in an existing, qualified database
Note:
For performance reasons, Oracle recommends that you do not install both the Management Service and Management Repository on the same host. Refer to "Hardware Requirements" for more information.Mount the product disk
Install Grid Control using Oracle Universal Installer's interactive mode
Find more information about other installation scenarios
This guide covers only the basic installation type described above and does not describe how to complete the following tasks:
Install Grid Control in any non-interactive mode
Configure your system to support installation of an additional Management Service or Management Agent
Upgrade an existing installation to the latest version
Install Grid Control on Real Application Clusters
Troubleshoot your installation session
Configure post-installation settings
Use Enterprise Manager Grid Control
Require secure communications between all Management Agents and the secure Management Service
For more information about installing Oracle Enterprise Manager Grid Control, including tasks not described in this manual, refer to Oracle Enterprise Manager Installation and Basic Configuration.
Note:
The entire documentation library for Enterprise Manager can be found on the Oracle Technology Network:http://www.oracle.com/technology/documentation/oem.html
This site may contain later versions of all books, including Oracle Enterprise Manager Installation and Basic Configuration. The installation procedures documented in this guide apply to all platforms. For platform specific information, refer to the Oracle Enterprise Manager Quick Installation Guide for the specific platform.
The system or systems must meet the minimum hardware and software requirements given in the following sections.
Even though Oracle Universal Installer runs prerequisite checks on your system to verify that it meets the listed requirements, to make sure that prerequisite checks do not fail, you should verify the requirements before running Oracle Universal Installer.
Note:
Only requirements for the Management Service and/or Management Repository host(s) are given here. Management Agent and other requirements can be found in Oracle Enterprise Manager Installation and Basic Configuration.The system or systems must meet the minimum hardware requirements for hard disk space, available memory, processor speed, and operating memory.
The hard disk requirements are:
9 GB for the "Enterprise Manager Grid Control Using a New Database" installation type
5 GB for the "Enterprise Manager Grid Control Using an Existing Database" installation type
To determine the amount of free disk space available in the /tmp directory, enter the following command:
# df /tmp
If there is less than 1300 MB 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 1300 MB 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.
For Agent Push Deployment, make sure that /tmp has 1300 MB of disk space available on the target machine.
The available operating memory requirements for installation are:
To install "Enterprise Manager Grid Control Using a New Database," a minimum of 1 GB of available operating memory for the host
To install "Enterprise Manager Grid Control Using an Existing Database," a minimum of 1 GB of available operating memory for the node
The hardware requirements to run Enterprise Manager are:
Minimum of 2 GB of free physical memory for the host running the Management Service
Minimum of 2 GB of free physical memory for the Management Repository node
Refer to Oracle Enterprise Manager Grid Control Installation and Basic Configuration for recommended CPU and memory allocation for the Management Service and Management Repository for Enterprise Manager deployments of various size.
The system or systems must meet the minimum software requirements for operating system, packages, and kernel parameters.
The operating system must be one of the following, with the listed (or later) kernel version if you are installing the new database:
AIX 5L Version 5.2
AIX 5L Version 5.3
Note:
To determine which version of AIX is installed, enter the following command:# oslevel
5.2.0.0
The packages required for the supported AIX versions are listed below:
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)
To determine whether the required filesets are installed and committed, enter a command similar to the following:
# lslpp -l bos.adt.base bos.adt.lib bos.adt.libm \ bos.perf.perfstat bos.perf.libperfstat
Note:
If a fileset is not installed and committed, you need to install it. Refer to your operating system or software documentation for information on handling filesets.To determine whether an authorized program analysis report (APAR) is installed, enter a command similar to the following:
# /usr/sbin/instfix -i -k " IY43980, IY44810,..."
If an APAR is not installed, you need to install it. For installing and downloading the APAR, refer to: https://techsupport.services.ibm.com/server/aix.fdc
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:
Configure Shell Limits
Verify that the shell limits shown in the following table are set to the values shown. The procedure following the table describes how to verify and set the values.
| Shell Limit (As Shown in smit) | Recommended Value |
|---|---|
| Soft FILE size | -1 (Unlimited) |
| Soft CPU size | -1 (Unlimited) |
| Soft DATA segment | -1 (Unlimited) |
| Soft STACK size | -1 (Unlimited) |
To view the current value specified for these shell limits and change them, follow these steps:
Enter the following command:
# smit chuser
In the User Name field, enter the user name of the Oracle software owner, for example oracle.
Scroll down the list and verify that the value shown for the soft limits listed in the table is -1. If necessary, edit the existing value.
When you have finished making changes, press F10 to exit.
Configure System Configuration Parameters
Verify that the maximum number of processes allowed per user is set to 2048 or higher. The procedure above describes how to verify and set the value.
Enter the following command:
# smit chgsys
Verify that the value shown for Maximum Number of Processes allowed per user is greater than or equal to 2048. If necessary, edit the existing value.
When you have finished making changes, press F10 to exit.
Switch user to "root" user:
$ su - root
If necessary, enter a command similar to the following to eject the currently mounted disk and to remove it from the drive:
# /usr/sbin/umount /SD_DVD
Insert the disk into the drive.
Enter a command similar to the following:
# /usr/sbin/mount -rv cdrfs /dev/cd0 /SD_DVD
In this example, /SD_DVD is the disk mount point directory and /dev/cd0 is the device name for the disk device.
If Oracle Universal Installer displays the Disk Location dialog box, then enter the disc mount point directory path. For example: /SD_DVD
Once you have configured your system to meet hardware and software requirements, start Oracle Universal Installer (OUI) and install Grid Control as follows:
Start OUI by executing the following command from the top directory of the DVD:
./runInstaller
Alternately, you can change directory to the Parent Directory (the root directory where you will install the Oracle home) and specify the full path to the runInstaller script.
The following table describes the recommended action for each OUI screen for the first two installation types.
If you need more assistance, click Help on that screen. If you have trouble with the installation, check out the "Troubleshooting" chapter of Oracle Enterprise Manager Grid Control Installation and Basic Configuration.
| Installation Screen | Recommended Action |
|---|---|
| Specify Installation Type | Select one of the installation types provided. The complete installation type is chosen by default. |
| Specify Installation Location | Specify the "parent" directory location for the installation. All Oracle homes created during installation will be placed as subdirectories under the parent directory. |
| Language Selection | Select the languages to run Grid Control in. The language you specify here is not the language of the installation session. |
| Specify Inventory Directory and Credentials | Appears only during the first installation of Oracle products on a system.
Specify the full path of the Oracle Inventory directory. Make sure to select the appropriate operating group. |
| Product-Specific Prerequisite Checks | Verify that all prerequisite checks succeed.
OUI checks the system to verify that it is configured correctly to support your Oracle software. If you have met all hardware and software requirements in this guide, all of the checks should pass. If a check fails, review the cause of failure, rectify the problem, and retry the check. You can also choose to manually verify failed checks if you are satisfied that your system meets the requirements. |
| Specify Configuration | Appears only for the "Enterprise Manager Grid Control Using a New Database" installation type.
Specify the name of the database you want to create, as well as the location to store the Management Repository files. Choose a file location outside of the Oracle home. Select the OSDBA and OSOPER groups that you are a member of. These memberships are required to grant the SYSDBA and SYSOPER privileges required to create the new database. |
| Specify Repository Database Configuration | Appears only for the "Enterprise Manager Grid Control Using an Existing Database" installation type.
Specify the database connection details for your existing, qualified database, as well as the locations for the new Management Repository tablespaces. |
| Specify Optional Configuration | All parameters can be configured through Grid Control after installation.
If you want, set the parameters for email notification, OracleMetaLink credentials, and proxy configuration settings. |
| Specify Security Options | Appears only for the "Enterprise Manager Grid Control Using a New Database" installation type.
Specify password used to secure the Management Service, as well as passwords to secure the Management Repository Database. |
| Specify Passwords | Appears only for the "Enterprise Manager Grid Control Using an Existing Database" installation type.
Specify the password used to secure the Management Service, as well as the SYSMAN password. |
| Summary | Review the information displayed here, then click Install. |
| Install | This screen displays status information while the product is being installed. |
| Execute Configuration Scripts | When prompted, read the instructions and run the scripts listed here. You must run the scripts as root from a terminal window. |
| Configuration Assistants | Displays status information for configuration assistants |
| End of Installation | Contains important information about your installation, including the URLs configured for your applications. Make a note of these URLs.
The port numbers used in these URLs are recorded in the following file: $ORACLE_HOME/install/portlist.ini |
In addition to performing a complete Grid Control installation, either using the embedded database or an existing, qualified one, you can perform the following other installation or upgrade operations:
Install an additional Management Service.
Install Management Agents in one of the following ways:
Interactive: Choose the Additional Management Agent installation type in Oracle Universal Installer.
Silent: Edit the appropriate response file to pre-fill values normally provided during interactive installation.
NFS Mounted Installation: NFS mount the software bits for installing the agent on a NetApp Filer disk to run the installation on each host.
The agentDownload Script: Launch this script on each target host to "pull" files from a central staging location.
The Agent Deploy Application: Launch this application from a central staging location to "push" files to multiple target hosts. This is the recommended method for installing Management Agents.
Install Enterprise Manager Grid Control into a Real Application Clusters environment.
Upgrade a previous, qualified version of Enterprise Manager Grid Control. Existing versions of Enterprise Manager will be automatically detected.
Refer to Oracle Enterprise Manager Grid Control Installation and Basic Configuration for detailed information and instructions on all of the above operations.
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.
This document includes the following sections:
Accessibility Instructions - Delete This Section After Reading
TTY Access to Oracle Support Services
Documentation Accessibility
