To run the prerequisite checker in standalone mode, execute the following command:

<DVD>/runInstaller -prereqchecker PREREQ_CONFIG_LOCATION=<DVD>/rdbms/Disk1/stage/prereq -entryPoint <component name>_Core -prereqLogLoc <log location> -silent -waitForCompletion

Substitute the data in contained within the angled brackets (< >) with the appropriate prerequisite check component name. For example, if you want to run the prerequisite check for the first installation type, execute the following command:

<DVD>/runInstaller -prereqchecker PREREQ_CONFIG_LOCATION=<DVD>/rdbms/Disk1/stage/prereq -entryPoint oracle.sysman.top.em_seed_Core -prereqLogLoc <log location> -silent -waitForCompletion

After performing the standalone prerequisite check you can also check for the operating system packages that are installed on your system. To check if the required operating system packages have been installed on your system, enter the following command:

rpm -qa | grep <package name>

for example: rpm -qa | grep glibc

Oracle Universal Installer will be launched. The first screen will show you different installation options. As you want to install Grid Control using a new database keep the default option selected and click the Next button. When you choose this option all the components namely Repository, Management Service and the Agent are installed as a part of the installation. In this installation, Oracle Database Enterprise Edition version 10.1.0.4.0 is installed and used as the repository.

Using this screen you can also choose to install Grid Control using an existing database, install an additional management service or an additional management agent. For more information about the other installation options click here.

Specify the parent directory where one or more ORACLE_HOME directories will be created. This should be an empty directory. All the Oracle homes such as db10g, oms10g, and agent10g are created under this parent directory during this installation. Click the Next button.

Note: The selected products are installed in the English language by default. If you want to install the product in a different language, click Product Languages. The Language Selection screen appears. Choose the languages that you want to use to run Enterprise Manager. The languages that you select here change the language of Enterprise Manager only, and not the language of the installation itself.

The Specify Inventory Directory and Credentials screen appears only if Enterprise Manager Grid Control is the first Oracle product that you are installing on the machine. Specify the full path to the directory where Oracle Universal Installer should place inventory files and directories. In this directory the installer will automatically set up subdirectories for each product to store inventory data. 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. Click the Next button.

The installer will perform few prerequisite checks. Early detection of system environment problems such as insufficient disk space, missing patches, inappropriate hardware, and so on results in a smoother installation later. This screen displays the name, type, and status for all prerequisite checks designed for the installation. Automatic checks are run first, followed by optional and manual checks. When all the checks are executed successfully click the Next button.

Depending on the status of the automatic checks, you must verify all warnings and manual checks. At some point, if you have stopped the prerequisite check and want to rerun these checks, select the checks that you want to rerun and click Retry. As each check runs, a progress bar is shown, and test details (expected results, actual results, error messages, instructions) are displayed in the details section at the bottom of the screen.

The prerequisite check details can be found under /home/oracle/oraInventory/logs.

After all the prerequisite checks are successfully completed, specify the repository database name and its location. Click the Next button. The repository database name should be unique.

As the name suggests, all the fields on this screen are optional, and are disabled by default. Select the required check box to enable the corresponding fields. Specify an appropriate e-mail address, and the corresponding SMTP server name. You will receive important information on the condition of the monitored targets, including critical alerts at this e-mail address. Specify the OracleMetaLink credentials. Specify the Proxy Information if Enterprise Manager is using a proxy server for external access. Click the Test Proxy button to check your proxy server connectivity.

Click the OK button.

Click the Next button. You can also do these optional configurations after the installation is over using the Grid Control console.

In Enterprise Manager version 10.2.0.x the communication between the he Oracle Management Service (OMS) and the agent can either be secure (over HTTPS between a secured agent and the Oracle Management Server) or insecure (over HTTP between a insecure agent and the Oracle Management Server). The Oracle Management Service always runs in a secure mode and can further have a "locked" or "unlocked" state. If it is unlocked then both secure and insecure agents can talk to the Oracle Management service. If it is locked then only secure agents can talk to it. Select Require Secure Communications for all agents checkbox if you want the secure OMS to communicate only with secure Management Agents. This is optional,though recommended.

In the Repository Database Passwords section, you can either specify different passwords for different user accounts or have same password for all the accounts. In the example below, we have the same password for all the user accounts. After specifying the passwords, click the Next button.

The installer seamlessly installs all Grid Control components based on the installation type you selected.

As a part of the installation you need to execute the allroot.sh file located under $ORACLE_HOME as a root user.

To do so open a new terminal window, login as root user, navigate to the $ORACLE_HOME directory and execute the allroot.sh file as shown below. allroot.sh will execute the root.sh files for each ORACLE_HOME created under the parent directory.

After the allroot.sh file is executed successfully, switch back to the installer screen and click the OK button.

As a part of the installation the installer will launch configuration assistants to configure and start the components. This screen displays the name, status, and the type of each configuration tool that Oracle recommends to be run before completing the installation.

The individual log files for each configuration tool are available at the following directory: ORACLE_HOME/cfgtoollogs/cfgfw

The configuration log files for each component namely the repository, management service and the agent are stored in their respective ORACLE_HOME directory under /cfgtoollogs/cfgfw directory.

To stop running a configuration tool, select it and click Stop. To rerun a configuration tool, select it and click Retry.

To know about how to run configuration assistants in standalone mode, click here.

The database configuration assistant will create and start the database instance for the repository.

Check whether all the configuration assistants are executed successfully.

When the configuration assistants configures and starts all the components, the installation is complete. This screen displays some important information about the products you have installed. This information is also available in the <AGENT_HOME>/sysman/setupinfo.txt file.

Click the Exit button to close the Oracle Universal Installer.

Click here to find out more about the Enterprise Manager Grid Control Installation Log Files.

Click Yes to confirm.