Install oracle em

Only for Microsoft Windows Ensure that the number of characters in the agent base directory path does not exceed 25 characters. Ensure that you check the network configuration to verify that the host on which you are installing resolves to a unique host name and a static IP address that are visible to other hosts in the network. Oracle recommends that you use static IP address. If you use dynamic IP address, and if the host is rebooted, then the host might receive a new IP, and as a result, the OMS startup will fail.

Ensure that you allocate 10 GB of hard disk space for the temporary directory. Ensure that you allocate MB of space for the central inventory directory. For a typical non-HA environment, the Central Inventory oraInventory can be in a shared or non-shared location. If you use a shared location, then ensure that only one shared location is maintained per host, and no two hosts update the same shared location.

One inventory file is meant only for one host, so it must not be shared and edited by other hosts. If you have configured a shared location that is common for two or more hosts, then switch over to a non-shared location.

For a typical HA environment with primary and standby disaster recovery sites using storage replication and alias host names, the Central Inventory oraInventory for software installed on the shared storage using the alias host name should be located in a shared location that is common between the OMS host in the primary site and the OMS host in the standby site. This shared location should be located on the replicated storage so that the oraInventory can be accessed from the active site for software maintenance activities.

Ensure that you set the default file mode creation mask umask to in the shell startup file. You can always reset the variable to the original value after the installation is complete. Ensure that the max user processes parameter and the open files parameter are set to Host File Requirements.

Otherwise, the installation can fail on the product-specific prerequisite check page. Ensure that localhost is pingable and resolves to According to RFC , the following are the assumptions: A name Net, Host, Gateway, or Domain name is a text string up to 24 characters drawn from the alphabet A-Z , digits , minus sign - , and period. Note that periods are only allowed when they serve to delimit components of domain style names.

No blank or space characters are permitted as part of a name. No distinction is made between upper and lower case. The first character must be an alpha character. For Microsoft Windows only User must belong to the DBA group, and have permissions to perform the following: Act as part of the operating system, Create a token object, Log on as a batch job, and Adjust memory quotas for a process. To verify whether the install user has these rights, from the Start menu, click Settings and then select Control Panel.

Ensure that you have write permission in the Middleware home and the Oracle Management Service Instance Base location. Ensure that you have write permission in the temporary directory where the executables will be copied. Ensure that you have write permission in the location where you want to create the Central Inventory oraInventory if it does not already exist.

If the Central Inventory already exists, then ensure that you have write permission in the inventory directory. Ensure that the user who installed the existing Oracle Database has write permission in the data file locations where the data files for the new tablespaces will be copied. These tablespaces and data files are created while configuring Enterprise Manager Cloud Control. While installing with simple configuration Installing an Enterprise Manager System for a Demonstration Site Simple Configuration , the installer automatically honors the default locations so you are not prompted for them.

However, while installing with custom configuration Installing an Enterprise Manager System for a Production Site Advanced Configuration , the installer prompts you to validate or enter the locations explicitly. Ensure that the host on which the OMS is being installed and the host on which the Management Repository is being configured are located in close proximity to each other. Ideally, the round trip network latency between the two should be less than 1 millisecond.

Port Requirements. Ensure that the ports you assign within the given range to the core components of Enterprise Manager Cloud Control are free and available. For information on the core components and their port ranges, see What Ports Are Used for Installation?

Internet Connection Requirements. Oracle recommends that the host from where you are running the installer have a connection to the Internet so that the configuration information can be automatically collected and uploaded to My Oracle Support. Using the Internet connection, you can also search and download software updates from My Oracle Support using the installer. These updates should be obtained before starting the 13c installation so they can be available to the installer at the proper time.

To install Enterprise Manager Cloud Control for evaluation or demonstration purposes, use the Simple installation type. This installation type installs with default configuration settings and preferences that you need for a complete Enterprise Manager system. It does not offer too many options to customize your installation.

For example, only the default plug-ins are deployed with the installation, and you are not provided with a separate screen to manually select the other plug-ins you want to deploy.

Therefore, this installation type is primarily meant for demonstration or evaluation purposes, and small deployments, and when you do not want to worry about the granular control of the installer and want to install the Enterprise Manager system quickly, with less memory, and for monitoring fewer targets in their environment. To install Enterprise Manager Cloud Control for evaluation or demonstration purposes, follow these steps:.

Oracle recommends you to run the EM Prerequisite Kit before invoking the installer to ensure that you meet all the repository requirements beforehand. Even if you do not run it manually, the installer anyway runs it in the background while installing the product.

However, running it manually beforehand sets up your Management Repository even before you can start the installation or upgrade process. For information on the kit, to understand how to run it, and to know about the prerequisite checks it runs, see Overview of the EM Prerequisite Kit. However, if you plan to use a database instance that was created with a preconfigured Management Repository using the database templates offered by Oracle, then make sure you pass the following parameter while invoking the EM Prerequisite Kit.

Invoke the installation wizard as a user who belongs to the oinstall group you created following the instructions in Creating Operating System Groups and Users for Enterprise Manager Cloud Control. The installer requires about 10 GB of hard disk space in the temporary directory. If your temporary directory does not have this space, then pass the -J-Djava.

The directory specified by this parameter will also be used as the location for the Provisioning Advisor Framework PAF staging directory, which is used for copying the Software Library entities related to the deployment procedures.

The PAF staging directory is used only for provisioning activities — entities are copied for a deployment procedure, and then, deleted once the deployment procedure ends.

If you do not want to enable Oracle Configuration Manager now, go to Step 3. If the host from where you are running the installation wizard does not have a connection to the Internet, then enter only the e-mail address and leave the other fields blank.

After you complete the installation, manually collect the configuration information and upload it to My Oracle Support. On the Software Updates screen, select Search for Updates, and then select one of the following options to apply the latest software updates:.

Local Directory, if you do not have Internet connectivity on your host, and want to download the updates in offline mode and apply them while performing the installation. My Oracle Support, if you have Internet connectivity on your host, and want to connect to My Oracle Support directly via the installer to download the updates in online mode and apply them while performing the installation.

For more information on these options, and for instructions to download and apply the software updates using these options, see Are the Software Updates Applied Automatically Even for Databases That Have Oracle Management Repository Preconfigured? The Software Updates screen uses the built-in feature Auto Update to automatically download and deploy the latest recommended patches while installing or upgrading Enterprise Manager Cloud Control.

This way, you do not have to keep a manual check on the patches released by Oracle. All patches required by the installer for successful installation and upgrade are automatically detected and downloaded from My Oracle Support, and applied during the installation or upgrade, thus reducing the known issues and potential failures.

Oracle strongly recommends using this feature, and applying the software updates while the installation is in progress. For more information, see What Is a Software Update? During installation, you will be prompted for the details of a database where Oracle Management Repository can be configured.

If you plan to provide the details of a database that already has an Oracle Management Repository preconfigured using the database templates offered by Oracle, then the software updates selected on this screen cannot be automatically applied. In such a case, you must manually download and apply these software updates after the installation. For details, see step 6.

Otherwise, the Check Prerequisites screen appears. For details, see step 8. If Enterprise Manager Cloud Control is the first Oracle product you are installing on the host that is running on Microsoft Windows operating system, then the Oracle Inventory screen does not appear. On Microsoft Windows, the following is the default inventory directory:.

On the Oracle Inventory screen, do the following. You will see this screen only if this turns out to be your first ever installation of an Oracle product on the host. However, if you already have some Oracle products on the host, then the central inventory location can be found in the oraInst. The oraInst. Ensure that you have read, write, and execute permissions on the default inventory directory. Alternatively, invoke the installer with the -invPtrLoc parameter, and pass the absolute path to the oraInst.

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.

On the Prerequisite Checks screen, check the status of the prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful installation. The installation wizard runs the prerequisite checks automatically when you come to this screen. It checks for the required operating system patches, operating system packages, and so on. If some checks result in Warning or Failed status, then investigate and correct the problems before you proceed with the installation.

The screen provides details on why the prerequisites failed and how you can resolve them. After you correct the problems, return to this screen and click Rerun to check the prerequisites again. However, all package requirements must be met or fixed before proceeding any further. Otherwise, the installation might fail. If a prerequisite check fails reporting a missing package, then make sure you install the required package, and click Rerun.

The installation wizard validates the package name as well as the version, so make sure you install the packages of the minimum versions mentioned in Package, Kernel Parameter, and Library Requirements for Enterprise Manager Cloud Control. Enter the Middleware home where you want to install the OMS and other core components. Enter the absolute path to the agent base directory, a location outside the Oracle Middleware home where the Management Agent can be installed. Ensure that this location is empty and has write permission.

Also ensure that it is always maintained outside the middleware home. The host name appears as a fully qualified name. The host name can also appear as a virtual host name if your host is configured with virtual machine. You can choose to accept the default host name and proceed with the installation. Alternatively, you can change the name if it is incorrect, or enter another host name for this host.

Ensure that the host name you enter is accessible from other hosts in the network other hosts must be able to ping this host. The host name appears as a fully qualified name, or as a virtual host name if your host is configured with virtual machine. The host name must resolve to the local host or virtual host because the host name is used for the local Oracle WebLogic Server as well as the Oracle Management Service.

Do not provide a remote host or a load balancer virtual host in this field. Do not enter an IP address. Do not use underscores in the name. Short names are allowed, but you will see a warning, so Oracle recommends that you enter a fully qualified domain name instead. Enter an administrator password, which can be used as a common password for configuring the Enterprise Manager Cloud Control. Table describes what the administrator password is used for.

The user account is automatically created during the configuration of Enterprise Manager Cloud Control. The agent registration password is used for authenticating new Management Agents that join Enterprise Manager system, where the communication between the OMS and the Management Agent is secure.

Provide details of the existing, certified database where the Management Repository needs to be created. If you have already created a database instance with a preconfigured Management Repository using the database templates offered by Oracle, then provide details about that database instance. The installer uses this information to connect to the existing database for creating the SYSMAN schema and plug-in schemas.

If you provide details of a database that already has a preconfigured Management Repository, then the installer only creates plug-in schemas. We also unlock all these user accounts. To identify whether your database is a certified database listed in the certification matrix, follow the steps outlined in Accessing the Enterprise Manager Certification Matrix.

If you are providing the details of a pluggable database PDB , then use the full service name instead of the alias. For example, pdb. If you are providing the details of a lone-pluggable database Lone-PDB , then use the full service name. For information on all the database initialization parameters that are set, and all the prerequisite checks that are run, and for instructions to run the prerequisite checks manually if they fail, see Overview of the EM Prerequisite Kit.

If you are connecting to an Oracle RAC database, and if you have specified the virtual IP address of one of its nodes, then the installation wizard prompts you with a Connection String dialog and requests you to update the connection string with information about the other nodes that are part of the cluster.

Update the connection string and click OK. If you want to test the connection, click Test Connection. Starting from DB version This is an expected behavior. Oracle Software Library Software Library is a feature within Enterprise Manager Cloud Control that acts as a repository to store software entities such as software patches, virtual appliance images, reference gold images, application software, and their associated directive scripts.

You require the Software Library for operations such as provisioning, patching, and so on. Select Configure Oracle Software Library, and enter the absolute path leading up to a unique directory name. By default, the storage location that is configured is the OMS Shared File System location, so Oracle strongly recommends that the location you enter is a mounted location on the OMS host.

This helps when you install additional OMS instances that can use the same mounted Software Library location. Configuring the Software Library at the time of installation is optional. Even if you do not select this option and configure it now, your installation will succeed. However, Oracle strongly recommends that you select this option and configure it at the time of installation so that the installer can automatically configure it for you.

This saves time and effort, and enables you to install an additional OMS, immediately after the first OMS, and configure it to use the same Software Library location.

Once the Software Library is configured, you can view the location details in the Software Library Administration Console. To access this console, from the Setup menu, select Provisioning and Patching, then select Software Library. Optional Configure a shared location for Oracle BI Publisher that is installed and configured by default. The shared storage location will act as a common location for storing the report catalog and associated management information for the first OMS you are installing now and also for the additional OMS you plan to install in the future.

If you do not have an existing shared location, create a new one and ensure that it is visible on the host where you are installing the first OMS and also on other hosts where you plan to install additional OMS instances. At install time, for the installation to be successful, you can reserve approximately MB of hard disk space for the shared directory. However, Oracle recommends that you scale it to at least 10 GB eventually, and ensure that it can be extended further in the future because the space utilization increases over a period of time as you install additional plug-ins and create more reports.

If you already have a shared location that you were using for the Software Library or for staging gold images in the previous release of Enterprise Manager, then you can choose to use the same location. However, ensure that the directories within the shared location are unique for Oracle BI Publisher, Software Library, and staged gold images. Enter the following directory paths.

Ensure that the user account that you are using to install the first OMS has read and write permission on these paths. Do not delete these directories after the installation. The directories are required for proper functioning of Oracle BI Publisher, and therefore are required during the installation and also after the installation. If you accidently exit the installer before clicking Retry , then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.

For Microsoft Windows platforms, invoke runConfig. Once the software binaries are copied and configured, you are prompted to run the allroot. Open another window, log in as root , and manually run the scripts.

If you are installing on Microsoft Windows operating system, then you will NOT be prompted to run this script. On the Finish screen, you should see information pertaining to the installation of Enterprise Manager. Review the information and click Close to exit the installation wizard. On the Select Plug-Ins screen, select the optional plug-ins you want to install from the software kit DVD, downloaded software while installing the Enterprise Manager system.

The screen lists the mandatory plug-ins as well as the optional plug-ins. The grayed rows indicate the mandatory plug-ins that will be installed. These are non-editable fields. The installer uses this information for creating Oracle WebLogic Domain and other associated components such as the admin server, the managed server, and the node manager.

On the Database Connection Details screen, enter the fully qualified name of the host where your existing, certified Oracle Database resides, its listener port and its service name or system ID SID , and the SYS user account's password.

For Registration Password , enter a password for registering the new Management Agents that join the Enterprise Manager system. For Management Tablespace , enter the full path to the location where the data file for management tablespace mgmt. The installer uses this information for storing data about the monitored targets, their metrics, and so on. Ensure that the specified path leads up to the file name. This is required for storing configuration information collected from the monitored targets.

On the Port Configuration Details screen, customize the ports to be used for various components. You can enter a free custom port that is either within or outside the port range recommended by Oracle. However, the custom port must be greater than and lesser than Alternatively, if you already have the ports predefined in a staticports. On the Install Progress screen, view the overall progress in percentage of the installation and the status of each of the Configuration Assistants.

Configuration Assistants are run for configuring the installed components of Enterprise Manager Cloud Control. You will directly reach the Finish screen as described in Step For more information about this installation, refer to the following file available in the OMS home:. For example, if you want to use the custom name EMDomain , then run the following command:.

By default, a Provisioning Advisor Framework PAF staging directory is created for copying the Software Library entities related to the deployment procedures. The location is used only for provisioning activities—entities are copied for a deployment procedure, and then, deleted once the deployment procedure ends.

During installation, if you want to install some plug-ins that are not in the software kit DVD, downloaded software , then follow these steps:. Manually download the plug-ins from the Enterprise Manager download page on OTN, and store them in an accessible location:. Invoke the installer with the following option, and pass the location where the plug-ins you want to install are available:.

This displays a list of plug-ins available in the software kit DVD, downloaded software as well as the plug-ins available in this custom location. You can choose the ones you want to install. For example, if you do not want the Management Agent to start automatically, then run the following command:.

To understand the limitations involved with this advanced option, see Limitations. Table lists the different combinations of these advanced options, and describes the workaround to be followed for each combination:.

If this is the first Oracle product you just installed on the host, then run the oraInstroot. For example, if the inventory location specified in the oraInst.

Navigate to the Management Agent home and run the following command to see a message that confirms that the Management Agent is up and running. Navigate to the Management Agent home and run the following command to see a message that confirms that EMD upload completed successfully.

Verify if all the plug-ins were installed successfully. To do so, access the following log file from the Management Agent home, and search for the sentence WARN:Plugin configuration has failed. If you find the sentence, resolve the issue by running the AgentPluginDeploy. Optional If the repository prerequisites had failed, and if you had manually run the EM Prerequisite Kit and taken corrective actions to meet the repository requirements, then run the utility again to reset the repository settings to what it had originally:.

By default, the following targets get automatically discovered and monitored in the Enterprise Manager Cloud Control console:. Application deployments, one for the Enterprise Manager Cloud Control console and one for the platform background services. However, the other targets running on that host and other hosts do not get automatically discovered and monitored. To monitor the other targets, you need to add them to Enterprise Manager Cloud Control either using the Auto Discovery Results page, the Add Targets Manually page, or the discovery wizards offered for the targets you want to monitor.

Skip Headers. Simple Installs with typical, default configuration. As the name suggests, it is simple and quick — you are prompted to enter only the administrator password and the database connection details. Advanced Installs with custom or advanced configuration, and is more flexible — you are prompted to enter WebLogic Server details, database connection details, data file locations for tablespaces, a password for creating the SYSMAN user account, and also customize ports according to your environment.

Before You Begin Before you begin, keep these points in mind: You can install Enterprise Manager Cloud Control using the installation wizard only on a single host, that is, locally on the server where the wizard is invoked. For example:. Prerequisites Table lists the prerequisites you must meet before installing Enterprise Manager Cloud Control. Table Prerequisites for Installing Enterprise Manager Cloud Control Requirement Description Hardware Requirements Ensure that you meet the hard disk space and physical memory requirements as described in Chapter 2.

To access this matrix, follow these steps: Log in to My Oracle Support , and click the Certifications tab. Operating System Groups and Users Requirements Ensure that you create the required operating system groups and users as described in Chapter 4. Unique Host Name and Static IP Address Requirements Ensure that you check the network configuration to verify that the host on which you are installing resolves to a unique host name and a static IP address that are visible to other hosts in the network.

Temporary Directory Space Requirements Ensure that you allocate MB of space for a temporary directory where the executables can be copied.

Central Inventory Requirements Ensure that you allocate MB of space for the central inventory directory. Also ensure that you apply the patches If you use Oracle Database 11 g Release 2 For example, all these commands must return the same output: nslookup host1 nslookup host1. Permission Requirements Ensure that you have write permission in the middleware home and the Oracle Management Service Instance Base location.

Proximity Requirements Ensure that the host on which the OMS is being installed and the host on which the Management Repository is being configured are located in close proximity to each other. Installation Procedure This section describes the following: Installing with Simple Configuration Installing with Advanced Configuration Installing with Simple Configuration To install Enterprise Manager Cloud Control with simple configuration, follow these steps: Invoke the Enterprise Manager Cloud Control Installation Wizard Invoke the installation wizard as a user who belongs to the oinstall group you created following the instructions in Chapter 4.

Click Next. Install Software Updates On the Software Updates screen, select one of the following sources from where the software updates can be installed while the installation of the Enterprise Manager system is in progress.

Once the search results appear with patch numbers and their details, click the patch number to view the ReadMe associated with that patch Note: If you choose to skip installing the software updates during installation by not providing the My Oracle Support credentials, you can always register the credentials later using the Enterprise Manager Cloud Control console and view the recommended security patches.

Note: The central inventory location you enter must NOT be on a shared file system. Note: Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value.

Note: If any repository-related prerequisite check fails, see Appendix A to manually run the prerequisite check. Note: If you are connecting to an Oracle RAC database, and if you have specified the virtual IP address of one of its nodes, then the installation wizard prompts you with a Connection String dialog and requests you to update the connection string with information about the other nodes that are part of the cluster.

Note: If a configuration assistant fails, the installer stops and none of the subsequent configuration assistants are run. Installing with Advanced Configuration To install Enterprise Manager Cloud Control with advanced configuration, follow these steps: Invoke the Enterprise Manager Cloud Control Installation Wizard Invoke the installation wizard as a user who belongs to the oinstall group you created following the instructions in Chapter 4.

Note: For information about the additional, advanced options you can pass while invoking the installer, refer to Advanced Installer Options. To make yourself aware of some installation-related known issues, see Limitations. Note: If you choose to skip installing the software updates during installation by not providing the My Oracle Support credentials, you can always register the credentials later using the Enterprise Manager Cloud Control console and view the recommended security patches.

Note: You can choose to ignore the checks with Warning status by clicking Ignore. During the installation, you are prompted to execute certain configuration scripts. Return to the dialog box shown in Figure after executing the scripts, and click OK to continue the installation. The Configuration Assistants screen appears. At this point, the installer starts running the configuration assistants.

This screen displays the name, status, and the type of each configuration tool that Oracle recommends to be run before completing the installation. Table lists all the configuration tools that are run during a typical Enterprise Manager installation Install Enterprise Manager Using a new database.

Table Enterprise Manager Configuration Tools. Footnote 1 Depending on the installation type that you have selected, any or all of the configuration tools listed in this table will be run. For more information on the installation logs that are created and their locations, see Appendix F, "Installation and Configuration Log File Locations".

In case of failure of any configuration assistant, refer to the logs and re-rerun the configuration assistants as described in AppendixA, "Configuration Assistants Fail During Enterprise Manager Installation". This log file contains all the configuration tool logs. After successfully running all the recommended configuration tools, the End of Installation screen appears. This screen displays some important information about the products you have installed.

Select this option if you want to perform a complete Enterprise Manager Grid Control installation and have a qualified existing database in which to create the Management Repository. The database can be local or remote to the machine on which you are installing.

The hardware requirements for the Management Repository and the operating system patch requirements for the host machine must be satisfied regardless of whether you choose to create a new database or use an existing database for the Management Repository during the installation session.

If you plan to use an existing database for your Management Repository creation, check all software requirements for the database and host, as well as for the repository. Ensure that the profile of the Password Verification resource name has the "Default" value. If the Password Verification is enabled, repository creation may fail. Ensure there is sufficient physical memory available for this installation type.

See Table , "Enterprise Manager Installation Options" for more information on the recommended hard disk and memory requirements. Ensure the database release should be 9. Ensure the name of the host on which the installation is being performed is neither be localhost. See Chapter3, "Check Database Initialization Parameters" for a detailed list of database initialization parameter settings based on the Enterprise Manager deployment size.

See Chapter 1, "Preinstallation Requirements" for more information on hardware and software requirements. The initialization parameters must be set correctly for your qualified existing Enterprise Edition database to be able to run a Management Repository.

You should also set all fixed parameters for your Management Repository database. The following table lists the parameters and their fixed values that must be met for successful Management Repository database creation. These parameters are verified by Oracle Universal Installer prerequisite checks during installation. Table Fixed Initialization Parameter Values. Footnote 2 The TEMP space is an initialization parameter only when you are performing an Enterprise Manager installation using a new database.

The variable parameter setting values are based on the size of the Enterprise Manager Grid Control environment. For the sake of clarity, the environment has been categorized as Small, Medium, and Large based on the number of targets in the environment, where:. Table Variable Initialization parameter Values.

Footnote 1 One redo log group with four members each of the listed size. For information on the specific values for language, territory, or character set, refer to the Globalization Support Guide of the Oracle product that you are using.

A Typical Installation Scenario. If you choose to install Enterprise Manager using an existing database, you must provide the location of an existing database where the installer will create the repository. Here again, the database should be of release 9. If you have an earlier database release installed, you must first upgrade this database instance to the specified minimum release 9.

All the Oracle homes created during the installation are placed as subdirectories under this parent directory.

For example: oms10g , and agent10g. The Language Selection screen appears. Make the required language selections here, and click Next. See Figure , "Language Selection" for details. The Specify Inventory Directory and Credentials screen appears if Enterprise Manager is the first Oracle product that you are installing on the machine.

The Specify Repository Database Configuration screen appears. Figure Specify Repository Database Configuration. Specify the connection details for the existing database in which the Management Repository should be created. The Management Repository database can be created on the following database releases:.

Oracle Database 10 g Release 1 The SID identifies a specific Oracle Database and distinguishes it from other databases on the computer. Enter the password for the SYS user.

You can also click Continue. Specify the full path of the file locations for the previously mentioned tablespaces. The directories you specify for these tablespaces must already exist for repository creation to succeed. For raw devices, you must partition your disk before specifying its location.

Note that raw device path names vary across volume managers. Ensure to use the right path format for your raw device locations. If you do not have the complete path for the tablespaces, click Prefill Tablespace Location. Note that the Prefill Tablespace button will be enabled only after you have specified all the Database Connection details. The installer then queries the database you have specified.

Ensure there is enough disk space available. If you are selecting an existing cluster database for the new Management Repository, the management tablespace file locations must be on a shared device that is accessible to all instances that provide the database service.

As the name suggests, all the fields on this screen are optional, and are disabled, by default. In the Configure Email Notification section, specify an appropriate e-mail address, and the corresponding SMTP server name in this section. You will receive information on important developments and events in Grid Control, including critical alerts, at this e-mail address. The SMTP server is the name of the mail server for example mail. If you prefer, you may also enter this information through the Enterprise Manager console after installation by clicking Patching Setup , under Setup.

See Table , "Specify Proxy information - Input Fields" for a description on each of the input fields in this section. Specify the Management Service Security, and Repository Database passwords that are used to secure your entire Grid Control environment. For example, if you have 10 g R1 To secure an agent, execute the following command from the agent Oracle home of that particular target:.

See the section on Password Restrictions and Recommendations in this chapter for more information. Depending on the installation type, this screen also provides any or all of the following details:. Verify the choices that you have made and click Install to start the installation. Refer to Figure , "Execute Configuration Scripts". To execute these scripts, go to the computer window, log in as root , and run these configuration scripts. Return to the Execute Configuration Scripts dialog box after executing the scripts, and click OK to continue the installation.

At this point, the installer starts running the recommended Configuration Assistants. Refer to Table , "Enterprise Manager Configuration Tools" to see the list of configuration tools that are run. This screen tells you whether or not the installation was successful, and displays some important information that you must remember about the products you have installed.

For example, it might contain information about the URLs for particular Web applications. During the installation process, if the SYSMAN schema already exists in the database that you specify for the Management Repository, the installer will prompt you to manually drop the schema. If this is not done, the installer will automatically drop the schema before proceeding to the next configuration assistant.

If the Oracle Management Service Configuration Assistant fails before completion, you can click Retry , which automatically cleans up the repository when the configuration tool is rerun. To manually clean up the repository, use the following command:. Refer to Oracle Enterprise Manager Advanced Configuration for further instructions on how to drop the existing repository from the database. Select this option if you need to add an additional Management Service to your environment.

Note that setting credentials for Oracle MetaLink is not necessary for this installation type, as the Management Repository is not affected. Ensure the hard disk and physical memory requirements are met.

Besides the database release, ensure the repository release is The Oracle Management Service OMS home created during the installation is placed as a sub-directory under this parent directory. For example: oms10g. The Language Selection screen is displayed. Make the required language selections here. You must configure the additional Management Service to establish the connections with the existing Management Repository. The Management Repository database may also require patches to be applied, prior to successful installation.

In the Repository Database Connection Details section, specify a fully qualified host name on which the Management Repository database is installed, the repository port, and the SID system identifier for the database instance. The SID identifies a specific Oracle database and distinguishes it from other databases on the computer. See the section Password Restrictions and Recommendations in this chapter for more information. Ensure that all Management Service instances using the same repository must use the same secure password.

Select the Configure Proxy check box optional if Enterprise Manager is using a proxy server for external access. Specify the properties for the proxy server host name enter a fully qualified host name , port number, Do Not Proxy for list, and the Proxy user credentials.

Specify an appropriate Realm value. This becomes a mandatory field only if the proxy server credentials have been configured using a Realm, in which case, you must specify an appropriate Realm value.

A Realm is a string value that is assigned by the proxy server to indicate the secure space that requires authentication. This screen displays a summary of the options that you have selected during the installation process. Depending on the installation type, this screen displays any or all of the following details:. For more information on each of the previously listed details, see the Enterprise Manager online Help. The installer begins installing the selected Oracle product.

These scripts and their locations are listed in the Execute Configuration Scripts dialog box that is displayed only for Linux. To execute these scripts, go to the computer window, log in as root and run these configuration scripts.

At this point, the installer starts running the recommended configuration tools. After successfully running all the recommended configuration tools, click Next. The End of Installation screen appears. This screen tells you whether or not the installation was successful and displays some important information that you must remember about the product you have installed.

Select this option to install the Management Agent in an Oracle home directory on a specified host target. Each host you wish to monitor must have a Management Agent installed. You may also perform silent installations using a response file. Use the Agent Deploy application to perform a new agent installation standalone or cluster agent or a shared agent installation. To see which group was used to install the Application Server, type ls -l on the command line in the directory containing opmn.

To see the groups to which you belong, type groups on the command line. You may be a member of several groups. Note that it is not sufficient to be a member of the group used to install the Application Server; that group must be your current group. Use the newgrp command to change to the group used to install the Application Server. Oracle recommends installing all software using a single group. In the Specify Installation Type screen, select the fourth option Additional Management Agent , and specify the parent directory path and installation name.

The agent home created during the installation is placed as a sub-directory under this parent directory. For example: agent10g.