| Oracle® Enterprise Manager Grid Control Installation and Configuration Guide 10g Release 5 (10.2.0.5.0) Part Number E10953-15 |
|
|
View PDF |
| Oracle® Enterprise Manager Grid Control Installation and Configuration Guide 10g Release 5 (10.2.0.5.0) Part Number E10953-15 |
|
|
View PDF |
This chapter provides information that helps you prepare better for a Enterprise Manager Grid Control (Grid Control) installation. Oracle recommends you to read this chapter before proceeding with the installation.
This chapter contains the following sections:
Installing Enterprise Manager Grid Control As the First Oracle Software
Understanding Enterprise Manager Grid Control Configuration Plug-in (EMCP)
This guide helps you install only the full releases of Enterprise Manager 10g Grid Control Release 2 or higher. A 'full release' refers to the first, complete Enterprise Manager 10g Grid Control Release 2 or higher software that was released for a particular platform.
A full release comprises all three components that form the Grid Control, mainly Oracle Management Service (OMS), Oracle Management Repository (Management Repository), and Oracle Management Agent (Management Agent). You can use the full release to install either all three components or only an additional OMS or Management Agent.
You can also use this guide to upgrade an existing Enterprise Manager 10g Grid Control Release 1 (10.1.0.4) or higher release to a full release of Enterprise Manager 10 Grid Control Release 2 or higher. For example, you can use this guide to upgrade an existing Enterprise Manager 10g Grid Control Release 1 (10.1.0.4) to Enterprise Manager 10g Grid Control Release 2 (10.2.0.1).
The following shows the full releases of Enterprise Manager 10g Grid Control Release 2 or higher that were released for various platforms. Use this guide for installing only these releases.
| Full Release | Targeted Platforms |
|---|---|
| Enterprise Manager 10g Grid Control Release 2 (10.2.0.1.1) (RECUT) | Linux x86 |
| Enterprise Manager 10g Grid Control Release 2 (10.2.0.1) |
|
| Enterprise Manager 10g Grid Control Release 2 (10.2.0.2.1) (RECUT) | Microsoft Windows (32-Bit) |
| Enterprise Manager 10g Grid Control Release 3 (10.2.0.3) |
|
In addition, there have been Patch Sets released periodically to patch these full releases and move them to higher releases. For example, Enterprise Manager 10g Release 2 (10.2.0.2) Patch Set was released for Linux x86 platform. The patch set helps you patch Enterprise Manager 10g Grid Control Release 2 (10.2.0.1) for Linux x86 and move it to Release 2 (10.2.0.2).
This guide does not describe the patching procedures. The patching procedures are furnished in the Patch Set Notes document that is packaged with the Patch Set, not in this guide. You can download the Patch Sets and the relevant Patch Set Notes from My Oracle Support (formerly Metalink).
Note:
Patch Sets help you to only patch any previous releases of Enterprise Manager Grid Control and (or) Management Agent; they DO NOT upgrade your existing releases to newer full releases, say Enterprise Manager 10g Grid Control Release 1 (10.1.0.4) to Enterprise Manager 10g Grid Control Release 2 (10.2.0.1).If you do not have a previous release, but want to have the most recent release of Grid Control, then first install a full release and then use the Patch Sets to patch it to a higher release.
You can download the Grid Control software from Oracle Technology Network (OTN) at:
http://www.oracle.com/technology/software/products/oem/index.html
Note:
Before you download the software, Oracle recommends you to read the Enterprise Manager 10g Grid Control Certification matrix. The certification matrix shows the operating systems and browser versions on which Grid Control and Management Agent are certified.The Enterprise Manager 10g Grid Control Certification matrix is available on My Oracle Support (formerly Metalink) at:
Login and select the Certify tab. On the Certify page, click View Certifications by Product and select Enterprise Manager 10g Grid Control, and then click Submit.
Verify that the file size of your downloaded software matches the file size displayed on OTN. After downloading the software, run the cksum command against the downloaded file to ensure that the file size of the downloaded software is the same as the file size on OTN.
For example, if you are downloading the Management Agent software of Release 10.2.0.3 for Linux x86 operating system, then you should see something like the following on OTN:
For Linux x86
|x| Linux_Grid_Control_agent_download_10_2_0_3_0.zip (317,120,712 bytes) (cksum - 2359676224)
The (cksum - 2359676224) value is the file size that you need to check. To do so, run the following command:
$ cksum Linux_Grid_Control_agent_download_10_2_0_3_0.zip
Verifying Platform Information
Note that a 32-bit Grid Control software (both Grid Control and Management Agent) can be installed only on a 32-bit operating system that is running on a 32-bit hardware. Similarly, a 64-bit Grid Control software can be installed only on a 64-bit operating system that is running on a 64-bit hardware.
Do not try to try install a 32-bit software on a 64-bit platform or vice versa; the installation may proceed, but will fail eventually. Therefore, ensure that you use the right software download for the right platform.
To verify the platform for which the software is downloaded, check the shiphomeproperties.xml file available in the /Disk1/stage directory.
The shiphomeproperties.xml file provides the platform information as shown here:
<?xml version="1.0" standalone="yes" ?> <ORACLEHOME_INFO> <ARU_PLATFORM_INFO> <ARU_ID>46</ARU_ID> <ARU_ID_DESCRIPTION>Linux x86</ARU_ID_DESCRIPTION> </ARU_PLATFORM_INFO> </ORACLEHOME_INFO>
You can see the platform information in the <ARU_ID_DESCRIPTION> syntax. The following table lists the platform names that may be enclosed in this syntax, and describes whether the names represent a 32-bit or 64-bit software.
Table 4-1 Verifying Platform Information
| Platform Specified in the ARU_ID_DESCRIPTION Syntax | Platform Name | 32-bit / 64-bit |
|---|---|---|
|
Linux x86 |
Linux x86 |
32-bit |
|
Win 32 |
Microsoft Windows (32-bit) |
32-bit |
|
win 64 |
Microsoft Windows (64-bit AMD64) |
64-bit |
|
Solaris |
Solaris Operating System (SPARC 64-bit) |
64-bit |
|
HPUNIX |
HPUX PA-RISC(64-bit) |
64-Bit |
|
AIX |
AIX |
64-bit |
|
HPI |
HP_IA64 |
64-bit |
|
Linux AMD |
Linux x86-64 |
64-bit |
|
Linux Itanium |
linux_ia64 |
64-bit |
|
Linux PPC |
IBM Power Based Linux |
64-bit |
|
zLinux |
linux_zseries64 |
64-bit |
|
Decunix |
HP Tru64 UNIX |
64-bit |
|
Solaris AMD64 |
Solaris Operating System (x86-64) |
64-bit |
|
Solaris AMD32 |
Solaris Operating System (x86) |
32-bit |
All OTN files have been archived using Info-ZIP's highly portable Zip utility. After downloading one or more of the archives, you will need the UnZip utility to extract the files.
You must unzip the archive on the platform for which it was intended. For example, if you download the software for the Linux operating system version of Grid Control, then you must unzip the file on a Linux operating system. If you unzip the file on a Microsoft Windows computer and then move the stage area to a Linux computer, then the staged area files will get corrupted. This is because Microsoft Windows does not preserve the case sensitivity or the permission bits of Linux file names.
If you plan to store the files on a DVD-ROM, create a DVD-ROM from the contents of the zip file (extracted contents) and not the Zip files itself; you need the unzipped contents of the Zip files to do the installation.
To set the mount point manually, complete these steps:
DVD-ROM users: Insert the Grid Control DVD-ROM into the DVD-ROM drive.
Start Oracle Universal Installer by executing the runInstaller script for Linux from the top directory of the DVD.
Alternatively, you can change the directory to the ORACLE_BASE, the root directory where you will install the Oracle home, then specify the full path to <DVD>/runInstaller in OUI.
prompt> cd
prompt> mount_point/10.2<DVD>/runInstaller
This launches Oracle Universal Installer using which you install Grid Control.
Although the installation media in your media pack contain many Oracle components, you are permitted to use only those components for which you have purchased licenses. Oracle Support Services does not provide support for components for which licenses have not been purchased.
For more information refer to Oracle Enterprise Manager Licensing Information.
The directories in which you install the Grid Control components are called the Oracle homes. During installation, you specify the full path to a directory that contains all the Oracle homes as subdirectories. This parent directory is called the Oracle home directory or base directory.
If you choose to install Grid Control using a new database on a computer with no other Oracle software installed, Oracle Universal Installer creates an Oracle base directory for you. If Oracle software is already installed, then one or more Oracle base directories already exist. In the latter case, Oracle Universal Installer offers you a choice of Oracle base directories into which to install Oracle Database.
You are not required to create an Oracle base directory before installation, but you can do so if required. You can set the ORACLE_BASE environment directory, which Oracle Universal Installer will recognize.
Note:
You can choose to create a new Oracle base directory, even if other Oracle base directories exist on that system.Names of Oracle homes can contain only alphanumeric characters and underscores.
ATTENTION:
Spaces are not allowed anywhere in the Oracle home directory path. The installer validates this. If you have spaces in the Oracle home directory path, the installation will fail.Grid Control is installed on multiple Oracle homes within the Oracle base directory. This means that a typical Grid Control installation creates three Oracle homes in different Oracle home directories. For example, oms10g, db10g, and agent10g.
Note:
You must ensure that you install this product into a new Oracle home directory. You cannot install products from one release of Grid Control into an Oracle home directory of a different release. For example, you cannot install 10g R2 (10.2) software into an existing Oracle9i home directory. If you attempt to install this release into an Oracle home directory that contains software from an earlier Oracle release, the installation will fail.You can install this release more than once on the same system, as long as each installation is done in a separate Oracle home directory.
Generally, you cannot install Grid Control in an existing Oracle home, unless the Oracle home is empty.
If Grid Control is the first Oracle product that you are installing, the installer prompts you to specify an inventory directory (also called the oraInventory directory). This inventory directory is used by the installer to place all the installer files and directories on the computer. The installer automatically sets up subdirectories for each Oracle product to contain the inventory data.
The inventory directory is separate from the Oracle home directory.
When you specify the Oracle inventory directory path, you must also select the appropriate operating system group name that will own the Oracle inventory directories. The group that you select must have write permissions on the Oracle inventory directories.
If you have a previous version of Grid Control installed on the computer, the installer uses the existing inventory directory. Ensure that you have write permissions on that directory. The best way of ensuring this is to run the installer as the same operating system user who installed the existing release of Grid Control.
By default, the installer installs Grid Control with text in English and in the operating system language. If you need additional languages, select the required languages in the Select Languages screen of the installer.
When you select additional languages to install, the installer also installs fonts required to display the languages.
For some components, languages are installed only if you select them during installation. In this case, if you access the application in a language that is not available, it reverts to the server locale language.
For other components, available languages are installed regardless of what you select during installation. In this case, however, fonts are installed only for the languages that are explicitly selected. When you access the application, it uses text in your language because the language was installed. However, if you do not have the appropriate fonts to render the text, the text appears as square boxes. This usually applies to the Chinese, Japanese, and Korean languages.
Default Port for Enterprise Manager Grid Control
The default port for Grid Control is 4889. This is the unsecured port, that is HTTP port. If 4889 is not available, then the first available free port from the range 4889 to 4897 is selected. The default secured port, that is HTTPS port, is 1159. If 1159 is not available, then the first available free port from the range 4898 to 4908 is selected.
Default Port for Management Agent
The default port for Management Agent is 3872. The same port is used for both HTTP and HTTPS. If 3872 is not available, then the first available free port from the range 1830 to 1849 is selected.
If you want to use custom ports instead of default ports, then update the staticports.ini file with suitable custom port numbers for the component names. The staticports.ini file is available in the installation DVD-ROM at the following location:
<DVD>/response/
While assigning custom pots, consider the following:
Port numbers cannot be greater than 65536.
If you use a port number less than 1024 for a component, you must run the component as the root user.
If you use a port number less than 1024 for a component, the installer cannot start up the component at the end of installation. You may need to configure the component first before you can start it up. See the appropriate component documentation for details.
You do not have to specify port numbers for all components in the staticports.ini file. If a component is not listed in the file, the installer uses the default port number for that component.
To invoke runInstaller (setup.exe on Microsoft Windows) with the staticports.ini option, run the following command:
./<runInstaller or setup.exe> -staticPortsIniFile <location>/staticport.ini
Once the installation is complete, you can check the ORACLE_HOME/install/portlist.ini file to view the assigned ports.
The installer verifies that the ports specified in the file are available (free) by reading the Properties file in all the Oracle homes. If the installer detects that a specified port is not available, it displays a message.
A port is considered to be free only if:
There are no Oracle products assigned to that port.
There are no processes running on that port.
The installer does not assign a port that is not available. To fix this:
Edit the staticports.ini file to specify a different port.
Click Retry. The installer rereads thestaticports.ini file and verifies the entries in the file again.
Note:
The
staticports.ini file uses the same format as the ORACLE_HOME/install/portlist.ini file, which is created after an Oracle Application Server installation. If you have installed Oracle Application Server and you want to use the same port numbers in another installation, you can use the portlist.ini file from the first installation as the staticports.ini file for subsequent installations.For view the format of staticports.ini file, see Appendix F, "Formats for the Staticports.ini File".
In some cases, despite providing custom ports in the staticports.ini file, the installer may resort to default ports. For information about the circumstances under which the installer may use default ports instead of custom ports, see Appendix F, "Causes for the Installer to Use Default Ports".
The installer prompts you to specify the passwords that are used to secure your entire Grid Control environment. This includes the OMS and the Management Repository passwords. One of the database passwords that you specify is the password required to access the application server (ias_admin). The ias_admin user is the administrative user for Oracle Application Server instances. To manage Oracle Application Server instances using Application Server Control, you must log in as ias_admin. Ensure the passwords you specify have all the required permissions.
The following restrictions apply to passwords:
Passwords must be between 5 and 30 characters long.
Passwords cannot be the same as the user name.
Passwords must include only lowercase or uppercase alphanumeric characters.
Note:
The SYSMAN password can include underscore (_), hyphen (-), dollar ($), and hash (#) along with alphanumeric characters. Alphabetic characters can be lowercase or uppercase.Passwords have at least one letter, one integer, and one special character (underscore).
Passwords cannot be Oracle reserved words. See Appendix I, "Oracle Reserved Words" for a complete list of reserved words.
Oracle recommends that the passwords that you specify are not simple or obvious words, such as welcome, account, database, or user.
After the installation,
If you want to change this default password, you can do so after the Grid Control installation by going to the Oracle home directory of the OMS and running the following command:
ORACLE_HOME/bin/emctl set password <old_default_password> <new_password>
Note:
If you do not remember the old ias_admin password, then follow the instructions outlined in Document ID 280587.1 that is available on My Oracle Support (formerly Metalink).The management audit log package of the scheme owner uses the UTIL package. For this package to function properly, the Grid Control schema user (for example, sysman) must have permissions to execute this package.
To grant permissions, run this command (where sysman is the schema user):
grant execute on utl_file to sysman;
Do NOT run OMS on a machine that is DHCP enabled. Oracle strongly suggests that you use a static host name or IP address assigned on the network for Grid Control components to function properly.
For more information, refer to My Oracle Support note 428665.1 at:
At least once during installation, the installer prompts you to log in as the root user and run a script. You must log in as root because the script edits files in the /etc directory.
When you perform an Grid Control installation, this installation does not include the Enterprise Manager Configuration Plug-in (EMCP) in the database Oracle home. EMCP is part of the Management Repository Oracle home only when you perform a standalone database installation.
The following are the prerequisite checks that the installer runs for each installation type.
Table 4-2 Prerequisites Checks for Each Installation Type
| Installation Type | Component Name | Checks |
|---|---|---|
|
Installing Enterprise Manager Using New Database |
|
|
|
Installing Enterprise Manager Using Existing Database |
|
|
|
Installing Additional Management Service |
|
|
|
Installing Additional Management Agent |
|
|
Footnote 1 Disallowed component = oracle.rsf.oracore_rsf.
Footnote 2 The name of the host on which the installation is being performed should neither be localhost.localdomain nor an IP address. It must be a valid host name. At the time of invoking the installer, you can pass ORACLE_HOSTNAME=<host_name> -local as an argument.
You can run the prerequisite check in standalone mode prior to starting the runInstaller. This helps you identify and resolve issues that might otherwise cause the installation to fail.
Table 4-3 lists the prerequisite check that is run for each installation type followed by the command that you must execute to run these checks:
Table 4-3 Installation Type and the Corresponding Prerequisite Check
| Installation Type | Component Name | -entryPoint Value |
|---|---|---|
|
Installing Enterprise Manager Using a New Database |
|
|
|
Installing Enterprise Manager Using an Existing Database |
|
|
|
Installing an Additional Management Service |
|
|
|
Installing an Additional Management Agent |
|
|
To run the prerequisite checker in standalone mode, execute the following command:
<DVD>/install/runInstaller -prereqchecker PREREQ_CONFIG_LOCATION=<DVD>/rdbms/Disk1/stage/prereq -entryPoint <entryPoint Value> -prereqLogLoc <log location> -silent -waitForCompletion
For the prerequisite checker to run successfully, ensure that the file path specified in --prereqLogLoc exists on the host.
Note:
On Microsoft Windows, replace/runInstaller with setup.exe and execute the command.
|
 Copyright © 1996, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|