| 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 describes the different installation options and provides instructions to install Enterprise Manager Grid Control (Grid Control). In particular, this chapter covers the following:
Installing Enterprise Manager Grid Control Using a New Database
Installing Enterprise Manager Grid Control Using an Existing Database
The following describes the different installation options offered by Grid Control. The hard disk space represents the footprint that the components of the installation consume, and the physical memory prerequisites refer to the initial RAM required for installation, and not the operating memory.
Table 8-1 Enterprise Manager Grid Control Installation Options
| Installation Option | Description | Hard Disk Space (Oracle Homes) | Physical Memory |
|---|---|---|---|
|
Enterprise Manager 10g Grid Control Using a New Database |
Installs Grid Control on the host, and creates a Management Repository in a new Oracle Database 10g Release 1 (10.1.0.4) Enterprise Edition. Note: Grid Control consists of Oracle Management Service (OMS), Oracle Management Agent (Management Agent), Oracle Database where Management Repository is created, and OracleAS J2EE and Web Cache, against which is the middle-tier where OMS is deployed. Also note that after installing Grid Control with a new database, that is Oracle Database 10g Release 1 (10.1.0.4), even if you upgrade to any higher release using the patch sets, the database installed is not upgraded. Therefore, even if you upgrade Grid Control, the database release remains 10.1.0.4, unless you upgrade it separately out of Grid Control installation. |
|
|
|
Enterprise Manager 10g Grid Control Using an Existing Database |
Installs Grid Control on the host, and creates the Management Repository on a qualified existing database, which may be local to the host or remote. For more information on supported repository releases, Oracle Management Repository Software Requirements. Note: If the repository is on the same machine as the OMS, allow 1 GB more memory than recommended. Oracle recommends installing Grid Control and Oracle Database on separate hosts. |
|
|
|
Additional Management Service |
Installs an additional OMS and a Management Agent. Allows you to map the additional OMS to an existing Management Repository, either local or remote. |
|
|
|
Additional Management Agent |
Installs a Management Agent on the host. The OMS and Management Repository are not required on the same host as the Management Agent, but must exist within the enterprise. The Management Agent may be installed on a cluster node. Oracle recommends that the target host on which you are installing the agent have a static IP address and not DHCP. For instructions to install a Management Agent, see Installing Management Agent Using OUI. |
|
No minimum requirement |
IMPORTANT:
When you perform a Grid Control installation, this installation does not include Enterprise Manager Configuration Plug-in (EMCP) in the database Oracle home. EMCP is part of the repository database Oracle home only when you perform a standalone database installation.
No environment variable specific to Grid Control needs to be set prior to installation. The $ORACLE_HOME and $ORACLE_SID variables should not be set; Oracle directories should not appear in the PATH.
If you install Grid Control on an NFS-mounted volume that has an Apache Server running, then ensure that the LockFile is stored outside the Oracle NFS-mounted home, on a separate local file system.
You can have both, Enterprise Manager 10g Grid Control Release 1 as well as Enterprise Manager 10g Grid Control Release 2 on the same host.
On Linux, start the Oracle Universal Installer (OUI) by running the following command:
<DVD>/runInstaller
On Microsoft Windows, start the OUI by running the following command:
<DVD>/setup.exe
Installation types are predefined component sets that determine the components to be installed. The Grid Control installation involves four top-level components, each representing an installation type. Select one of the installation types described in the following sections.
This section introduces you to the first installation type offered by OUI, that is, Enterprise Manager 10g Grid Control Using a New Database. In particular, this section covers the following:
Note:
This section describes the steps required for installing the base release, that is, Enterprise Manager 10g Grid Control Release 2 (for example, 10.2.0.1 Linux or 10.2.0.2 Microsoft Windows).If you are installing Grid Control for the first time in your environment and if you want to have the latest release, then use the'Installing Software-Only and Configuring Later' option that is discussed in Installing 'Software-Only' and Configuring Later.
Note:
If you are installing Grid Control with a new database during the Daylight Savings Time (DST) period, then Oracle recommends you to use the 'Installing Software-Only and Configuring Later' option that is discussed in Installing 'Software-Only' and Configuring Later.The first installation type, that is, Enterprise Manager 10g Grid Control Using a New Database, is the default option selected when you invoke the OUI installation wizard. It performs a complete installation and is best suited when you are installing for the first time in your environment or when you want all the components to be installed.
This installation type does the following:
Installs Oracle Database 10g Release 1 (10.1.0.4) (Contains an embedded 10g Management Repository)
Installs Oracle Management Service 10g Release 2 (Deployed in Oracle Application Server 10g Release 2 (10.1.2.0.2) that gets installed along with other core components)
Installs Oracle Management Agent 10g Release 2
Configures the Oracle Database, OMS, and Management Agent
The following describes the installation process and the software components installed for this installation type.
Table 8-2 Installation Process for Installing Enterprise Manager Grid Control with a New Database
| Sequence | Action | Component Installed/Configured | Description |
|---|---|---|---|
|
1 |
Installation |
Oracle Database 10g Release 1 (10.1.0.4) |
In the specified installation directory, the installer creates a subdirectory for Oracle Database and places the software binaries in it. This Oracle Database contains an embedded Management Repository. For example, if the installation directory is /scratch/OracleHome, then the subdirectory created for the database is:
|
|
2 |
Installation |
Oracle Management Service 10g Release 2 |
Technically, the installer installs an application server, that is, Oracle Application Server 10g Release 2 (10.1.2.0.2) where the OMS is deployed. In the specified installation directory, the installer creates a subdirectory for OMS and places the software binaries in it. For example, if the installation directory is /scratch/OracleHome, then the subdirectory created for OMS is:
|
|
3 |
Installation |
Oracle Management Agent 10g Release 2 |
In the specified installation directory, the installer creates a subdirectory for the Management Agent and places the software binaries in it. The subdirectory is agent11g. For example, if the installation directory is /scratch/OracleHome, then the subdirectory created for the Management Agent is:
|
|
4 |
Configuration |
All |
The installer runs the Configuration Assistant tools to configure all the installed components: |
Before you begin, keep these points in mind:
This installation type installs the components only on a single host, and only on that host from where the OUI installation wizard is involed, that is, where the runInstaller file (or setup.exe for Microsoft Windows platforms) is invoked.
The default port for Oracle Database 10g Release 1 (10.1.0.4) provided with this installation type is 1521.
The default port for Enterprise Manager Grid Control is 4889 and the default port for Management Agent is 3872. For more information about the default ports that are assigned and the possibility of using custom ports instead of default ports, see Knowing About the Ports Used for Installation.
Oracle offers code fixes for a product based on the Oracle Lifetime Support Policy. When the license period expires for a particular product, the support for code fixes offered by Oracle also ends. For more information, see the Oracle Lifetime Support Policy available at:
http://www.oracle.com/support/library/brochure/lifetime-support-technology.pdf
When determining supportability and certification combinations for an Enterprise Manager Grid Control installation, you must consider Enterprise Manager Grid Control's framework components as well as the targets monitored by Enterprise Manager Grid Control. Oracle recommends keeping your Grid Control components and targets updated to the latest certified versions in order to receive code fixes without having to purchase an Extended Support license. For information about the certified combinations of Enterprise Manager Grid Control components and monitored targets, see My Oracle Support note.412431.1.
If the Management Agent does not start up automatically when you restart the host, then do the following:
Open the agentstup file from the Oracle home of the Management Agent:
$ORACLE_HOME/install/unix/scripts/agentstup
Edit the file to replace executingUser=$USER with executingUser=`id -un`. Then, save and exit the file.
Run the root.sh script from the Oracle home of the Management Agent:
$<ORACLE_HOME>/root.sh
Restart the Management Agent by running the following command from the Oracle home of the Management Agent:
$<ORACLE_HOME>/bin/emctl start agent
Note:
This is a one-time action to be taken. Step (a) to Step (c) will ensure that the Management Agent starts up automatically every time you restart the host in the future.Before installing Enterprise Manager Grid Control with a new database, ensure that you meet the following prerequisites.If you want, you can print out this section and write 'Yes' or 'No' against each prerequisite. This will help you to track the prerequisites you have met and the prerequisites you have not met.
Table 8-3 Prerequisites for Enterprise Manager 10g Grid Control Using a New Database
| Requirement | Description | Yes/No |
|---|---|---|
|
Hardware and Software Requirements |
Ensure that you meet the necessary hardware and software requirements for Enterprise Manager Grid Control. For information about hardware and software requirements, see Hardware Requirements and Software Requirements, respectively. |
|
|
Operating System Requirements |
Check if the operating system of the host is certified. For information about the supported operating systems, see Operating System, Browser, Target Certification. |
|
|
Package Requirements |
Verify if the package requirements for each platform are met. For information about packages to be installed for Management Agent, see Appendix D, "Platform-Specific Package and Kernel Requirements". |
|
|
Permission Requirements for Installation Directory |
Check if the installation directory, that is, the Oracle home directory is writable. |
|
|
Host List and Credentials Requirements |
Identify the host where you want to install Enterprise Manager Grid Control, and obtain the credentials of that host so that it can be accessed for installation. |
|
|
Host Name Requirement |
The host name must be a valid host name. For example, serverhost1.company.com or serverhost1. However, it cannot be an IP address. At the same time, it cannot be localhost.localdomain as strings used in the /etc/hosts file. At the time of invoking the installer, you can pass |
|
|
Installing User Requirements |
The following are the requirements:
|
|
|
Installation Directory Requirements |
If the specified Installation Directory already contains subdirectories that represent the components of Enterprise Manager Grid Control, then those subdirectories must be empty. If they are not, either delete them or keep them empty. For example, if the specified Installation Directory already has <install_dir/agent10g>, <install_dir/oms10g>, <install_dir/db10g> subdirectories, then they must be empty. |
|
|
Oracle Inventory Location Requirements |
Ensure that the Oracle Inventory ( |
|
|
Targets Monitored |
Remember that Enterprise Manager Grid Control will be able to monitor only those targets that are monitored by the Management Agent installed by the same user. |
WARNING:
The steps outlined in this section are for installing full, base releases of Enterprise Manager 10g Grid Control Release 2 or higher. For details about full, base releases and what these installation instructions can be use for, see Understanding What This Guide Helps You Install and Upgrade.To install Enterprise Manager Grid Control using a new database, follow these steps:
Select the first option (Enterprise Manager 10g Grid Control Using a New Database). By default, this option is selected when you invoke the installer.
Click Next. In the Specify Installation Location screen that appears, specify a parent directory (base directory), for example, /scratch/OracleHomes (on Linux), for the new installation. All the Oracle homes created during this installation are created as subdirectories under this parent directory. For example: db10g, oms10g, and agent10g.
Note:
Ensure you do not use symbolic links to specify the Oracle home path.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 Grid Control.
Note:
The languages that you select here change the language of Grid Control only, and not the language of the installation itself.Click Next. The Specify Inventory Directory and Credentials screen appears only if 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 (OUI) should place inventory files and directories. For example, oracle_base/oraInventory (on Linux).
Note:
If you are performing the installation on a Microsoft Windows platform, the Specify Inventory Directory and Credentials screen will not appear.On Microsoft Windows, the default inventory files location is <system drive>\Program Files\Oracle\Inventory.
Refer to the Grid Control online Help for more information on guidelines recommended by Oracle for naming the directories.
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 Next. The Product-Specific Prerequisite Checks screen appears.
At this point, the installer runs some prerequisite checks to verify if the environment meets the minimum requirements for a successful Grid Control installation.
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.
Depending on the status of the automatic checks, you must verify all warning 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.
Note:
You can also run these prerequisite checks in standalone mode, prior to starting the
runInstaller. For more information, see Running the Prerequisite Check in Standalone Mode.To stop all prerequisite checks, click Stop. At any point in time, click a prerequisite check to view its corresponding details, including the recommended user actions.
To continue with the installation without retrying, click Next.
An error message is displayed if some recommended prerequisite checks have failed.
Click No to go back and rerun the prerequisite check. Click Yes to ignore the message and continue with the installation.
Note:
It is recommended that you retry checks that were flagged with warnings, failed, or were skipped (stopped by the user) before continuing with the installation.The Specify Configuration screen appears.
You must specify the configuration details for the new database that you are creating, and select the appropriate recipients of the OSDBA and OSOPER privileges (on UNIX only).
Note:
Your Management Repository may also require patches to be applied after successful installation. See Operating System, Browser, Target Certification for more information.Specify the new Database Name and the Database File Location (location where the new database is going to reside).
Note:
It is recommended that you specify a fully qualified database name (for example,
emrep.<domain_name>), though appending the database name with the domain name is not mandatory.In the Group Specification section, select the OSDBA and OSOPER groups of which you are a member. These memberships are required to grant the SYSDBA and SYSOPER permissions that are, in turn, required to create the new database using the operating system authentication.
Click Next. The Specify Optional Configuration screen appears.
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.
In the Configure Email Notification section, 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.
The e-mail address that you specify should be associated with the SYSMAN user to receive notifications.
The SMTP Server is the name of the mail server (for example mail.acme.com). For Linux, the default SMTP server is the local host name. Use the fully qualified host name (including domain).
Note:
If you do not provide the e-mail notification information, this feature is not enabled upon installation. You may also choose to configure these settings through the Grid Control console by clicking Notification Methods under Setup. Refer to the Grid Control online Help for more information.Specify the My Oracle Support (formerly Metalink) credentials.
If you prefer, you can also enter this information through the Grid Control console after installation by clicking Patching Setup, under Setup.
Note:
Grid Control uses these credentials to search for and download patches from
http://oracle.com/support/metalink/index.htmlSpecify the Proxy Information if Grid Control is using a proxy server for external access. Table 8-4 describes each of the fields under this section.
Table 8-4 Specify Proxy information - Input Fields
| Input | Description |
|---|---|
|
Proxy Server |
Specify the proxy server host name. For example, |
|
Port |
Specify the port at which the server is listening. For example, |
|
Do Not Proxy For |
Specify the URLs that do not need the proxy server to be accessed. You can specify multiple comma-separated values. For example, .here.com, .us.mycompany.com, .uk.mycompany.com, and so on. Note that you must always specify fully qualified host names. |
|
Proxy User and Password |
Specify the user name and password only if the proxy server has been configured to use these credentials for authentication. These are optional fields. |
|
Realm |
Specify an appropriate realm value. This becomes a mandatory field only if the proxy server credentials have been configured using a realm. A realm is a string value assigned by the proxy server to indicate the secure space that requires authentication. |
|
Test Proxy |
Click this button to verify your proxy server settings. |
Note:
When you search for a patch, if the proxy properties (saved in thesysman/config/emoms.properties file) are not set, or are set incorrectly, you receive an error message indicating that Grid Control cannot access the My Oracle Support (formerly Metalink) Web site.Caution:
If the proxy server requires user authentication before providing access, you must specify these credentials here or through the Patching Setup screen under Setup in the Grid Control console.Click Next. The Specify Security Options screen appears.
You must specify the passwords that are used to secure your entire Grid Control environment. This screen has two sections - Management Service Security, and Repository Database Passwords.
Management Server Security: The password that you specify here is used to secure and lock the OMS.
Select Require Secure Communications for all agents if you want the secure OMS to communicate only with secure Management Agents. This is optional, though recommended.
For example, consider you have unsecured 10.1.n agents in the Grid and you have secured the OMS. Now, if you select the Require Secure Communications option, then all communication between the 10.2 OMS and 10.1.n agents fails (because these agents have not been secured).
Note:
To secure a Management Agent, run following command. However, note that even after securing the Management Agent, some data might still be transferred over the network without being encrypted.<AGENT_HOME>/bin/emctl secure agent
Repository Database Passwords: Specify the passwords for each of the administrative database accounts listed in Table 8-5.
Table 8-5 Repository Database Passwords
| User Account | Applies to | Description |
|---|---|---|
|
SYS |
Management Repository |
Super Administrator for the Management Repository database. |
|
SYSTEM |
Management Repository |
Administrator for the Management Repository database. |
|
DBSNMP |
Management Repository |
Monitoring user for the Management Repository database. |
|
SYSMAN |
Management Repository, Application Server, and Grid Control |
The default Grid Control Super Administrator and Owner of the Management Repository database schema and the Grid Control application user. The default ias_admin password is the same as the password assigned to the SYSMAN account. This is required to access the Oracle application server ( After the installation, if you want to change this default password, then go to the Oracle home directory of the OMS and run the following command:
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). |
You can use the same password for all four accounts, or specify a different password for each one. These passwords are used to secure the Management Repository database.
To specify a different password for each account, select Use different passwords for these accounts and specify the passwords for each account.
To specify the same password for all accounts, select Use the same password for all accounts and specify one password to be used for all database accounts.
Note:
The SYS, SYSMAN, DBSNMP, and SYSTEM users are privileged database users. You must remember the passwords that you specify for them. For more information on password restrictions and recommendations, see Oracle Database Administrator's Guide.Password Restrictions and Recommendations
The following restrictions apply to passwords:
Passwords must be between 5 and 30 characters long.
Passwords should not start with a number.
Passwords cannot be the same as the user name.
Passwords must include letters (lowercase/uppercase) and numbers only.
Note:
The SYSMAN password can include underscores (_), and hyphens (-), dollar ($), and hash (#) along with alphanumeric characters. Alphabetic characters can be uppercase or lowercase.Passwords cannot be Oracle reserved words. See Appendix I, "Oracle Reserved Words" for more information.
Note:
Oracle recommends that the passwords you specify have the following characteristics:Have at least one letter, one integer, and one special character (underscore).
Are not simple or obvious words such as welcome, account, database, or user.
Click Next. The Summary screen appears.
This screen provides a summary of the options that you have selected during the installation process. Depending on the installation type, it also provides any or all of the following details:
Global Settings
Product Languages
Space Requirements
Installed Products
Verify the choices that you have made.
Click Install to start the installation. The Install screen that appears displays the installation progress bar.
The installer seamlessly installs all Grid Control components based on the installation type you selected.
During the installation, you are prompted to execute certain configuration scripts. These scripts and their locations are listed in the Execute Configuration Scripts dialog box that appears (on UNIX only).
Note:
The Execute Configuration Scripts dialog box will not appear on Microsoft Windows. You will be directed to the Configuration Assistants screen (step 9) in the next step.Go to the computer window, log in as root, and run these configuration scripts.
Return to the dialog box (shown in Figure 8-12) 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 8-6 lists all the configuration tools that are run during a typical Grid Control installation (Install Enterprise Manager Using a new database).
Table 8-6 Grid Control Configuration Tools
| Product | Configuration ToolFoot 1 |
|---|---|
|
Oracle Repository Database |
|
|
Oracle Enterprise Manager Grid Console |
|
|
Oracle Management Agent |
|
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 B, "Installation and Configuration Log Files". In case of failure of any configuration assistant, refer to the logs and re-rerun the configuration assistants as described in Configuration Assistants Fail During Enterprise Manager Installation.
Note:
The individual log files for each configuration tool are available at the following directory:ORACLE_HOME/cfgtoollogs/cfgfw
Besides the individual configuration logs, this directory also contains cfmLogger_timestamp.log (The timestamp depends on the local time and has a format such as cfmLogger_2005_08_19_01-27-05-AM.log.). This log file contains all the configuration tool logs.
To stop running a configuration tool, select it and click Stop.
To rerun a configuration tool, select it and click Retry.
Note:
The installation is considered successful even if all the configuration tools fail, irrespective of their type (recommended/optional). However, failing to successfully run all the configuration tools results in an improperly configured product, which may not function. Refer to the Grid Control installation online Help for more information.Note:
In the event a particular configuration assistant fails, you can choose to rerun only that configuration assistant (in standalone mode). See Configuration Assistants Fail During Enterprise Manager Installation for more information.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. This information is also available in the <AGENT_HOME>/sysman/setupinfo.txt file.
For example, it might contain information about the URLs for particular Web applications.
Note:
If the Management Agent does not start up automatically when you restart the host, then do the following:Open the agentstup file from the Oracle home of the Management Agent:
$ORACLE_HOME/install/unix/scripts/agentstup
Edit the file to replace executingUser=$USER with executingUser=`id -un`. Then, save and exit the file.
Run the root.sh script from the Oracle home of the Management Agent:
$<ORACLE_HOME>/root.sh
Restart the Management Agent by running the following command from the Oracle home of the Management Agent:
$<ORACLE_HOME>/bin/emctl start agent
This is a one-time action to be taken. Step (1) to Step (3) will ensure that the Management Agent starts up automatically every time you restart the host in the future.
This section introduces you to the second installation type offered by OUI, that is, Enterprise Manager 10g Grid Control Using an Existing Database. In particular, this section covers the following:
Note:
This section describes the steps required for installing the base release, that is, Enterprise Manager 10g Grid Control Release 2 (for example, 10.2.0.1 Linux or 10.2.0.2 Microsoft Windows).If you are installing Grid Control for the first time in your environment and if you want to have the latest release, then use the'Installing Software-Only and Configuring Later' option that is discussed in Installing 'Software-Only' and Configuring Later.
The second installation type, that is, Enterprise Manager 10g Grid Control Using an Existing Database, is best suited when you already have a certified Oracle Database in your environment and when you want to use it to create the Management Repository. The existing, certified Oracle Database can be on a local or remote host. However, Oracle Real Application Clusters (RAC) databases must be on a shared disk.
To view a list of certified Oracle Database, see Document ID 412431.1 on My Oracle Support (formerly Metalink). If you want to use a RAC database, which is configured on a virtual host, as the existing database, then refer to Document ID 561441.1 on My Oracle Support (formerly Metalink).
If you want to use Oracle Database 11g as the existing database, then see Installing Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) Using Existing Oracle Database 11g.
This installation type does the following:
Installs Oracle Management Service 10g Release 2 (Deployed in Oracle Application Server 10g Release 2 (10.1.2.0.2) that gets installed along with other core components)
Installs Oracle Management Agent 10g Release 2
Configures the Management Repository (in the existing, certified Oracle Database), OMS, and Management Agent.
The following describes the installation process and the software components that are installed for this installation type.
Table 8-7 Installation Process for the Installing Enterprise Manager Grid Control with an Existing Database
| Sequence | Action | Component Installed/Configured | Description |
|---|---|---|---|
|
1 |
Installation |
Oracle Management Service 10g Release 2 |
Technically, the installer installs an application server, that is, Oracle Application Server 10g Release 2 (10.1.2.0.2) where the OMS is deployed. In the specified installation directory, the installer creates a subdirectory for OMS and places the software binaries in l seit. For example, if the installation directory is /scratch/OracleHome, then the subdirectory created for OMS is:
|
|
2 |
Installation |
Oracle Management Agent 10g Release 2 |
In the specified installation directory, the installer creates a subdirectory for the Management Agent and places the software binaries in it. The subdirectory is agent10g. For example, if the installation directory is /scratch/OracleHome, then the subdirectory created for the Management Agent is:
|
|
3 |
Configuration |
All |
The installer runs the Configuration Assistant tools to configure all the installed components:
|
Before you begin, keep these points in mind:
The existing, certified Oracle Database must NOT have a repository already created.
The default port for Enterprise Manager Grid Control is 4889 and the default port for Management Agent is 3872. For more information about the default ports that are assigned and the possibility of using custom ports instead of default ports, see Knowing About the Ports Used for Installation.
Oracle offers code fixes for a product based on the Oracle Lifetime Support Policy. When the license period expires for a particular product, the support for code fixes offered by Oracle also ends. For more information, see the Oracle Lifetime Support Policy available at:
http://www.oracle.com/support/library/brochure/lifetime-support-technology.pdf
When determining supportability and certification combinations for an Enterprise Manager Grid Control installation, you must consider Enterprise Manager Grid Control's framework components as well as the targets monitored by Enterprise Manager Grid Control. Oracle recommends keeping your Grid Control components and targets updated to the latest certified versions in order to receive code fixes without having to purchase an Extended Support license. For information about the certified combinations of Enterprise Manager Grid Control components and monitored targets, see My Oracle Support note.412431.1.
Do check the following:
If that existing database is on the same host where OMS is installed, the database gets added to the All Targets page of the Grid Control console, but you will have to provide configuration details to enable monitoring of that database. To do so, log in to Enterprise Manager Grid Control, click Targets and then click All Targets. From the list, select the database instance and click Configure. In the Configure Database Instance: Properties Page, provide the details.
If that existing database is on a different host, then ensure that that host has a Management Agent installed that points to the OMS. After that, provide configuration details in the Grid Control console to enable monitoring of that database. To provide configuration details, follow the instructions given in the previous point.
If the Management Agent does not start up automatically when you restart the host, then do the following:
Open the agentstup file from the Oracle home of the Management Agent:
$ORACLE_HOME/install/unix/scripts/agentstup
Edit the file to replace executingUser=$USER with executingUser=`id -un`. Then, save and exit the file.
Run the root.sh script from the Oracle home of the Management Agent:
$<ORACLE_HOME>/root.sh
Restart the Management Agent by running the following command from the Oracle home of the Management Agent:
$<ORACLE_HOME>/bin/emctl start agent
Note:
This is a one-time action to be taken. Step (a) to Step (c) will ensure that the Management Agent starts up automatically every time you restart the host in the future.Before installing Enterprise Manager Grid Control with an existing database, ensure that you meet the following prerequisites.If you want, you can print out this section and write 'Yes' or 'No' against each prerequisite. This will help you to track the prerequisites you have met and the prerequisites you have not met.
Table 8-8 Prerequisites for Enterprise Manager 10g Grid Control Using an Existing Database
| Requirement | Description | Yes/No |
|---|---|---|
|
Hardware and Software Requirements |
Ensure that you meet the necessary hardware and software requirements for Enterprise Manager Grid Control. For information about hardware and software requirements, see Hardware Requirements and Software Requirements, respectively. |
|
|
Operating System Requirements |
Check if the operating system of the host is certified. For information about the supported operating systems, see Operating System, Browser, Target Certification. |
|
|
Package Requirements |
Verify if the package requirements for each platform are met. For information about packages to be installed for Management Agent, see Appendix D, "Platform-Specific Package and Kernel Requirements" |
|
|
Sufficient Physical Memory |
Ensure there is sufficient physical memory available for this installation type. For information, see Understanding the Installation Types and Recommended CPU and Memory Allocation. |
|
|
Host List and Credentials Requirements |
Identify the host where you want to install Enterprise Manager Grid Control, and obtain the credentials of that host so that it can be accessed for installation. |
|
|
Host Name Requirement |
The host name must be a valid host name. For example, serverhost1.company.com or serverhost1. However, it cannot be an IP address. At the same time, it cannot be localhost.localdomain as strings used in the /etc/hosts file. At the time of invoking the installer, you can pass |
|
|
Permission Requirements for Installation Directory |
Check if the installation directory, that is, the Oracle home directory is writable. |
|
|
Installing User Requirements |
The following are the requirements:
|
|
|
Installation Directory Requirements |
If the specified Installation Directory already contains subdirectories that represent the components of Enterprise Manager Grid Control, then those subdirectories must be empty. If they are not, either delete them or keep them empty. For example, if the specified Installation Directory already has <install_dir/agent10g> and <install_dir/oms10g> subdirectories, then they must be empty. |
|
|
Existing Oracle Database Requirements |
Ensure that the existing Oracle Database is a certified database. To view a list of certified Oracle Databases, see Document ID 412431.1 on My Oracle Support (formerly Metalink). If you want to use a RAC database, which is configured on a virtual host, as the existing database, then refer to My Oracle Support note 561441.1. If you want to use Oracle Database 11g as the existing database, then see Installing Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) Using Existing Oracle Database 11g. |
|
|
Existing Oracle Database and Listener Status Requirements |
Ensure that the existing, certified Oracle Database and Listener are running. |
|
|
Password Verification Requirements |
Ensure that the profile of the Password Verification resource name has the "Default" value. If the Password Verification is enabled, repository creation may fail. |
|
|
Existing Oracle Database Configuration Requirements |
If your existing database is configured with a Database Control, then ensure that the database control is deconfigured before installing Enterprise Manager Grid Control. For commands to be used for deconfiguring the Database Control, see the first few steps in Installation Procedure. |
|
|
NLS_LANG Environment Variable Requirements |
If your operating system is Linux, then ensure the NLS_LANG environment variable is set with a value that is compatible with the operating system default locale setting and the Management Repository database character set. 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. |
|
|
Existing Oracle Database Initialization Parameters Requirements |
Verify database setting - initialization parameters. For a detailed list of database initialization parameter settings based on the Enterprise Manager deployment size, see Check Database Initialization Parameters. |
|
|
Targets Monitored |
Remember that Enterprise Manager Grid Control will be able to monitor only those targets that are monitored by the Management Agent installed by the same user. |
The initialization parameters must be set correctly for your certified existing Oracle Database Enterprise Edition, to be able to create a Management Repository. You should also set all fixed parameters for your Management Repository database.
See Also:
For more information about managing initialization parameters, refer to the Managing Initialization Parameters Using a Server Parameter File chapter of the Oracle Database Administrator's Guide.After making the changes, you must shut down and restart the database.
See Also:
For instructions on shutting down the database, refer to the Starting Up and Shutting Down chapter in the Oracle Database Administrator's Guide.Fixed Initialization Parameter Values
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.
Note:
Make sure that the Enterprise Edition database you select for your Management Repository has the fine-grained access control option set to true. This is required for successful Management Repository creation. Check
v$options for this setting.Table 8-9 Fixed Initialization Parameter Values
| Parameter | Value |
|---|---|
|
job_queue_processes |
10 |
|
db_block_size |
8192 |
|
timed_statistics |
TRUE |
|
open_cursors |
300 |
|
session_cached_cursors |
200 |
|
aq_tm_processes |
1 |
|
compatible |
<currently installed Oracle Database release> (default) |
|
undo_management |
AUTO |
|
undo_retention |
10800 |
|
undo_tablespace |
<any acceptable name> |
|
processes |
150 |
|
log_buffer |
1048576 |
|
statistics_level |
TYPICAL (Note that this value is specific only to Enterprise Manager 10g Repository Database release and later.) |
|
TEMP space (Tablespace)Foot 1 |
50 MB (extending to 100 MB) |
|
_b_tree_bitmap_plans |
false (hidden parameter) |
Footnote 1 The TEMP space is an initialization parameter only when you are performing a Grid Control installation using a new database.
Variable Initialization Parameter Values
The variable parameter setting values are based on the size of the 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:
Small = Approximately 100 monitored targets
Medium = Approximately 1000 monitored targets
Large = 10000 or more monitored targets
Table 8-10 lists the variable parameter setting values.
Table 8-10 Variable Initialization parameter Values
| Size | pga_aggregate_target | Redo logs | db_cache_size | shared_pool_size | sga_target |
|---|---|---|---|---|---|
|
Small |
256 MB |
100 MB |
384 MB (or more) |
128 MB |
512 MB (or more) |
|
Medium |
384 MB |
512 MB |
1024 MB (or more) |
384 MB |
1408 MB (or more) |
|
Large |
512 MB |
1024 MB |
2048 MB (or more) |
512 MB |
2560 MB (or more) |
Caution:
The steps outlined in this section are for installing a full, base releases of Enterprise Manager 10g Grid Control Release 2 or higher, using an existing database. For details about full, base releases and what these installation instructions can be use for, see Understanding What This Guide Helps You Install and Upgrade.To install Enterprise Manager Grid Control using an existing database, follow these steps:
If your existing database is configured with Database Control, then ensure that you deconfigure it before you begin the installation of Grid Control.
To deconfigure Database Control for a single instance database, run the following command:
<Database ORACLE HOME>/bin/emca -deconfig dbcontrol db -repos drop
To deconfigure Database Control for a Real Application Clusters (RAC) database, run the following command:
<Database ORACLE HOME>/bin/emca -deconfig dbcontrol db -repos drop - cluster
After deconfiguring the Database Control, connect to the database as SYS user and run the following SQL files from the Oracle home of the database:
<ORACLE_HOME>/rdbms/admin/dbmspool.sql
<ORACLE_HOME>rdbms/admin/prvtpool.plb
Note:
The command drops all the public synonyms starting with the following names created by any user for any schema:'MGMT$%'
'MGMT_%'
'SMP_EMD%'
'SMP_MGMT%'
'SETEMVIEWUSERCONTEXT'
'DBMS_SHARED_POOL'
'EMD_MNTR'
'ECM_UTIL'
Start Oracle Universal Installer by running the runInstaller script in Linux (<DVD>/runInstaller) from the top directory of the DVD.
In the Specify Installation Type screen, select the second option (Enterprise Manager 10g Grid Control Using an Existing Database). Click Next.
The Specify Installation Location screen appears.
Specify the full path to the parent directory (base directory), for example, /scratch/OracleHomes. All the Oracle homes created during the installation are placed as subdirectories under this parent directory. For example: oms10g, and agent10g.
Caution:
Do not use symbolic links to specify the Oracle home path.The installer by default installs the selected products in the English language.
If you want to install the product in a different language, click Product Languages.
The Language Selection screen appears. Make the required language selections here, and click Next. See Figure 8-3, "Language Selection" for details.
Click Next. The Specify Inventory Directory and Credentials screen appears if is the first Oracle product that you are installing on the machine. See Figure 8-4, "Specify Inventory Directory and Credentials" for details.
Click Next. The Product Specific Prerequisites Check screen appears.
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.
Depending on the status of the automatic checks, you must verify all warning 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. See Figure 8-5, "Product-Specific Prerequisite Checks" for details.
Note:
You can also run these prerequisite checks in standalone mode, prior to starting the
runInstaller. For more information, see Running the Prerequisite Check in Standalone Mode.Click Next. The Specify Repository Database Configuration screen appears.
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 10g Release 1 (10.1.0.4 and later), Enterprise Edition
Note:
If you are performing a Grid control installation using an existing database, ensure the database is of a 10.1.0.3 release or later.Oracle Real Application Clusters 10g Release 1 (10.1.0.4 and later)
Note:
If you are performing a Grid control installation using an existing database, ensure the existing Oracle RAC database is of a 10.1.0.3 release or later.Oracle9i Release 2 (9.2.0.6 and later), Enterprise Edition
Oracle9i Real Application Clusters Release 2 (9.2.0.6 and later)
In the Database Connection Details section, specify a fully qualified host name, listener Port number, SID (system identifier) for the database instance, and the SYS password.
The SID identifies a specific Oracle Database and distinguishes it from other databases on the computer.
Note:
When selecting an existing cluster database for creating the Management Repository, you can either specify the SID value, or use the OMS name.Enter the password for the SYS user. This account is used to create the SYSMAN user, which is the primary owner of the Management Repository schema.
In the Additional Tablespace section, specify the location for the following:
Management Tablespace Location: The MGMT_TABLESPACE tablespace holds data for the Management Repository.
Configuration Data Tablespace Location: The MGMT_ECM_DEPOT_TS tablespace holds Configuration Management data for the Management Repository.
Caution:
If the existing database that you have selected to create the repository already contains a SYSMAN schema, the installer will display an error similar to the following:"The Grid Control schema already exists in the database that you have provided."
You can choose to manually drop this schema before proceeding with the repository creation.
You can also click Continue. The installer will then automatically drop the existing schema and create a new SYSMAN schema.
For ASM (Automatic Storage Management) devices, the tablespace locations should be specified relative to the ASM disk group. For example: +<ASM Disk>/emrep/tablespace.dbf
For tuning/performance reasons, Oracle recommends placing Binary large objects (BLOBs) in their own tablespace. Because Enterprise Configuration Management data support BLOBs, the Management Repository requires two tablespaces: MGMT_TABLESPACE and MGMT_ECM_DEPOT_TS.
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. Look for the SYSAUX tablespace location, and prefill that path in the appropriate box.
Note:
The two tablespaces initially require 120 MB of disk space, with MGMT_TABLESPACE requiring 20 MB and MGMT_ECM_DEPOT_TS requiring about 100 MB. 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.
Caution:
If the
DBMS_SHARED_POOL package has not been installed at the time of the database creation, Oracle Universal Installer displays an error message and prompts you to execute this package before proceeding with the installation.
To check whether or not the DBMS_SHARED_POOL package has been installed, login to the database and execute the following query:
Select count(*) from dba_objects where OWNER = 'SYS' AND object_name = 'DBMS_SHARED_POOL' AND object_type IN ( 'PACKAGE','PACKAGE BODY') ;
This query should return a count of 2.
To install the DBMS_SHARED_POOL package, execute the following script:
<DB_HOME>/rdbms/admin/dbmspool.sql
Caution:
If you had not configure the database initialization parameters, then you might see the following error message:The existing database is not configured to meet the requirements.
To resolve this issue, you must correctly set the database initialization parameters as described in Check Database Initialization Parameters.
Click Next. The Specify Optional Configuration screen appears.
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.
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 e-mail address that you specify should be associated with the SYSMAN user to receive notifications.
The SMTP server is the name of the mail server (for example mail.acme.com). For Linux, the SMTP server must be the local host name. Use the fully qualified host name (including domain).
Specify the My Oracle Support (formerly Metalink) credentials if you are going to use a proxy server to access My Oracle Support.
If you prefer, you may also enter this information through the Grid Control console after installation by clicking Patching Setup, under Setup.
Note:
Grid Control uses the My Oracle Support (formerly Metalink) credentials to search for and download patches fromhttp://oracle.com/support/metalink/index.htmlSpecify the Proxy Information if Grid Control is using a proxy server for external access. See Table 8-4, "Specify Proxy information - Input Fields" for a description on each of the input fields in this section.
Note:
If the proxy server requires user authentication before providing access, you must specify these credentials here, or through the Patching Setup screen under Setup in the Grid Control console.Click Next. The Specify Passwords screen appears.
Specify the Management Service Security, and Repository Database passwords that are used to secure your entire Grid Control environment.
Select Require Secure Communications if you want the secure OMS to communicate only with Secure Agents. This is optional, though recommended.
For example, if you have 10g R1 (10.1.n) agents in the Grid environment and you have secured and locked the OMS, and selected the Require Secure Communications option, then all communication between the 10g R2 (10.2) OMS and 10.1 agents fails (because these agents have not been secured).
To secure a Management Agent, run the following command from the Management Agent Oracle home of that particular target. However, note that even after securing the Management Agent, some data might still be transferred over the network without being encrypted.
emctl secure agent
See the section on Password Restrictions and Recommendations in this chapter for more information.
Click Next. The Summary screen appears.
This screen provides a summary of the options that you have selected during the installation process. Depending on the installation type, this screen also provides any or all of the following details:
Global Settings
Product Languages
Space Requirements
New Installations
Installed Products
Verify the choices that you have made and click Install to start the installation. The Install screen that appears displays the installation progress bar.
The installer seamlessly installs all Grid Control components based on the installation type you selected.
During the installation, you are prompted to execute certain configuration scripts. These scripts and their locations are listed in the Execute Configuration Scripts dialog box that is displayed (only on UNIX). Refer to Figure 8-12, "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.
The Configuration Assistants screen appears. At this point, the installer starts running the recommended Configuration Assistants.
Note:
The OMS Configuration Assistant will create the repository. The repository creation log (
emca_repos_create<TimeStamp>.log For example, emca_repos_create05_13_33.log) is available at the following directory:
OMS_HOME/sysman/log/
This screen displays the name, status, and the type of each configuration tool that Oracle recommends to be run before completing the installation. Refer to Table 8-6, "Grid Control Configuration Tools" to see the list of configuration tools that are run. In case of failure of any configuration assistant, refer to the logs and re-rerun the configuration assistants as described in Configuration Assistants Fail During Enterprise Manager Installation.
Note:
If you are installing Grid Control using an existing RAC database that is configured on a virtual host, and if the OMS Configuration Assistant fails, then refer to Document ID 561441.1 on My Oracle Support (formerly Metalink) at:After successfully running all the recommended configuration tools, 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 products you have installed. For example, it might contain information about the URLs for particular Web applications.
Note:
If the Management Agent does not start up automatically when you restart the host, then do the following:Open the agentstup file from the Oracle home of the Management Agent:
$ORACLE_HOME/install/unix/scripts/agentstup
Edit the file to replace executingUser=$USER with executingUser=`id -un`. Then, save and exit the file.
Run the root.sh script from the Oracle home of the Management Agent:
$<ORACLE_HOME>/root.sh
Restart the Management Agent by running the following command from the Oracle home of the Management Agent:
$<ORACLE_HOME>/bin/emctl start agent
This is a one-time action to be taken. Step (1) to Step (3) will ensure that the Management Agent starts up automatically every time you restart the host in the future.
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:
OMS_HOME/sysman/admin/emdrep/bin/RepManager <Host name> <Port> <SID> -ACTION Drop
You may need to set the LD_LIBRARY_PATH to the ORACLE_HOME/lib directory of the OMS before running the script.
Refer to Oracle Enterprise Manager Advanced Configuration for further instructions on how to drop the existing repository from the database.
Note:
The listener that is associated with the specified database must be running. Otherwise, Management Repository creation may fail.To install Enterprise Manager Grid Control using an existing database on Microsoft Windows 2008 and Microsoft Windows Vista, follow these steps:
Download patch# 6640752 for Microsoft Windows (32-Bit) from My Oracle Support. You can access My Oracle Support at:
Extract the contents of the downloaded patch to a location on your system.
For example: C:\Patch_Download
Download the base release, that is, Enterprise Manager 10g Grid Control Release 2 (10.2.0.2.0) for Microsoft Windows.
Extract the contents of the downloaded base release to a location on your system. For example, C:\Base_Download
Ensure that your existing database is a database that is supported on Microsoft Windows Vista or Microsoft Windows 2008. For example, Oracle Database 10g Release 2 (10.2.0.3 or 10.2.0.4).
Edit the response file and make changes as described in this step. Make the following changes in the response file.
The response file is available at:
C:\Base_Download\Disk1\install\response\emnoseed.rsp
Make the following changes:
For the FROM_LOCATION parameter, specify the full path to the products.xml file.
For example:
FROM_LOCATION="C:\Base_Download\Disk1\oms\Disk1\stage\products.xml"
For the ORACLE_HOME parameter, specify the full path to the Oracle home directory of the OMS.
For example:
ORACLE_HOME="C:\OH102020\oms10g"
For the ORACLE_HOME_NAME parameter, specify the Oracle home name for OMS.
For example:
ORACLE_HOME_NAME="oms10g2"
For the s_agentHome parameter, specify the full path to the Oracle home directory of the Management Agent.
For example:
s_agentHome="C:\OH102020\agent10g"
For the s_agentHomeName parameter, specify the home name for Management Agent.
For example:
s_agentHomeName="agent10g2"
Note:
Ensure that the Oracle home location and the name you specify are not already existing.Run the setup.exe file:
C:\Patch_Download\cd\Disk1\install\setup.exe -ignoreDiskLabel -responseFile
C:\Base_Download\Disk1\install\response\emnoseed.rsp
If the Management Agent does not restart, and if the value of agentTZRegion in the emd.properties file is GMT, then reset the time zone on the host where the Management Agent is installed using the following command. Here, Oracle_Home is the Oracle home directory of the Management Agent.
<Oracle_Home>\BIN>emctl resetTZ agent
Patch OMS and Management Agent to 10.2.0.5.0 release.
For patching instructions, see the Release Notes provided with the 10.2.0.5 patch set.
This section introduces you to the third installation type offered by OUI, that is, Additional Management Service. In particular, this section covers the following:
Installing an Additional Management Service on Microsoft Windows 2008 or Microsoft Vista
Installing Additional Management Service in a 10.2.0.2 or 10.2.0.3 Environment
The third installation type, that is, Additional Management Service, installs an additional OMS to your existing Enterprise Manager Grid Control environment. This option is best suited when you already have Enterprise Manager Grid Control with a certified Oracle Database, and when you want to have another OMS for the following reasons:
When you want to balance the load on the existing OMS
When your existing OMS is running out of CPU or RAM resources
However, note that you can have multiple OMSes and still connect to just one Management Repository.
This installation type does the following:
Installs Oracle Management Service 10g Release 2 (Deployed in Oracle Application Server 10g Release 2 (10.1.2.0.2) that gets installed along with other core components)
Installs Oracle Management Agent 10g Release 2
Configures the OMS and Management Agent
Note:
If you want to install an additional OMS to connect to Oracle Database 11g, then see Installing Additional Management Service Using Existing Oracle Database 11g.The following describes the installation process and software components that are installed for this installation type.
Table 8-11 Installation Process for Installing Additional OMS
| Sequence | Action | Component Installed/Configured | Description |
|---|---|---|---|
|
1 |
Installation |
Oracle Management Service 10g Release 2 |
Technically, the installer installs an application server, that is, Oracle Application Server 10g Release 2 (10.1.2.0.2) where the OMS is deployed. In the specified installation directory, the installer creates a subdirectory for OMS and places the software binaries in it. For example, if the installation directory is /scratch/OracleHome, then the subdirectory created for OMS is:
|
|
2 |
Installation |
Oracle Management Agent 10g Release 2 |
In the specified installation directory, the installer creates a subdirectory for the Management Agent and places the software binaries in it. The subdirectory is agent10g. For example, if the installation directory is /scratch/OracleHome, then the subdirectory created for the Management Agent is:
|
|
3 |
Configuration |
All |
The installer runs the Configuration Assistant tools to configure all the installed components. |
Before you proceed with the rest of the subsections in this section, let us understand the different scenerios under which you will install an additional OMS and what is the best installation procedure or approach to be adopted for each of the scenarios.
Table 8-12 Additional OMS Installation Scenarios
| Scenarios | Installation Approach | Reference Points |
|---|---|---|
|
If you want to install an additional OMS in a complete 10.2.0.1 environment -- where the repository, the main OMS (which comes along with the full installation of Enterprise Management Grid Control), and the other additional OMS are of 10.2.0.1 release. |
Use the installer of the full release to install the 10.2.0.1 additional OMS. |
Follow the installation instructions given in Installation Procedure. |
|
If you want to install an additional OMS in an environment where the repository and the main OMS are of 10.2.0.2 or 10.2.0.3 release for Linux, or 10.2.0.3 release for Microsoft Windows. |
|
Follow the installation instructions given in Installing an Additional Management Service on Microsoft Windows 2008 or Microsoft Vista. |
|
If you want to install an additional OMS in an environment where the repository and the main OMS are of 10.2.0.4 or higher release. |
Install the additional OMS in a 'software-only' method, so that you only install the binaries immediately and configure it after it is patched to the higher release. |
Follow the installation instructions given in Installing 'Software-Only' and Configuring Later. |
Note:
If you want to install an additional OMS to connect to Oracle Database 11g, then see Installing Additional Management Service Using Existing Oracle Database 11g.Before you begin, keep these points in mind:
This installation type installs the components only on a single host, and only on that host from where the OUI installation wizard is invoked, that is, from where the runinstaller or setup.exe file is invoked. Installation on multiple hosts and remote hosts is not supported.
The default port for Enterprise Manager Grid Control is 4889 and the default port for Management Agent is 3872. For more information about the default ports that are assigned and the possibility of using custom ports instead of default ports, see Knowing About the Ports Used for Installation.
Oracle offers code fixes for a product based on the Oracle Lifetime Support Policy. When the license period expires for a particular product, the support for code fixes offered by Oracle also ends. For more information, see the Oracle Lifetime Support Policy available at:
http://www.oracle.com/support/library/brochure/lifetime-support-technology.pdf
When determining supportability and certification combinations for an Enterprise Manager Grid Control installation, you must consider Enterprise Manager Grid Control's framework components as well as the targets monitored by Enterprise Manager Grid Control. Oracle recommends keeping your Grid Control components and targets updated to the latest certified versions in order to receive code fixes without having to purchase an Extended Support license. For information about the certified combinations of Enterprise Manager Grid Control components and monitored targets, see My Oracle Support note.412431.1.
If the Management Agent does not start up automatically when you restart the host, then do the following:
Open the agentstup file from the Oracle home of the Management Agent:
$ORACLE_HOME/install/unix/scripts/agentstup
Edit the file to replace executingUser=$USER with executingUser=`id -un`. Then, save and exit the file.
Run the root.sh script from the Oracle home of the Management Agent:
$<ORACLE_HOME>/root.sh
Restart the Management Agent by running the following command from the Oracle home of the Management Agent:
$<ORACLE_HOME>/bin/emctl start agent
Note:
This is a one-time action to be taken. Step (a) to Step (c) will ensure that the Management Agent starts up automatically every time you restart the host in the future.Before installing an additional OMS, ensure that you meet the following prerequisites.If you want, you can print out this section and write 'Yes' or 'No' against each prerequisite. This will help you to track the prerequisites you have met and the prerequisites you have not met.
Table 8-13 Prerequisites for Additional Oracle Management Service
| Requirement | Description | Yes/No |
|---|---|---|
|
Hardware and Software Requirements |
Ensure that you meet the necessary hardware and software requirements for OMS. For information about hardware and software requirements, see Hardware Requirements and Software Requirements, respectively. |
|
|
Operating System Requirements |
Check if the operating system of the host is certified. For information about the supported operating systems, see Operating System, Browser, Target Certification. |
|
|
Package Requirements |
Verify if the package requirements for each platform are met. For information about packages to be installed for Management Agent, see Platform-Specific Package and Kernel Requirements. |
|
|
Sufficient Physical Memory |
Ensure there is sufficient physical memory available for this installation type. For information, see Understanding the Installation Types and Recommended CPU and Memory Allocation. |
|
|
Permission Requirements for Installation Directory |
Check if the installation directory, that is, the Oracle home directory is writable. |
|
|
Host List and Credentials Requirements |
Identify the host where you want to install OMS, and obtain the credentials of that host so that it can be accessed for installation. |
|
|
Host Name Requirement |
The host name must be a valid host name. For example, serverhost1.company.com or serverhost1. However, it cannot be an IP address. At the same time, it cannot be localhost.localdomain as strings used in the /etc/hosts file. At the time of invoking the installer, you can pass |
|
|
Installing User Requirements |
The following are the requirements:
|
|
|
Using the Same User Name, UID, GID |
Use the same user name, uid, and gid as the ones used on the host where the first OMS was installed. This is to ensure that both OMSes have access to the same, shared Oracle Software Library. For information about setting the user name, uid, and gid, see Using the Same User Name, UID, and GID. |
|
|
Installation Directory Requirements |
If the specified Installation Directory already contains subdirectories that represent the components of Enterprise Manager Grid Control, then those subdirectories must be empty. If they are not, either delete them or keep them empty. For example, if the specified Installation Directory already has <install_dir/agent10g> and <install_dir/oms10g> subdirectories, then they must be empty. |
|
|
Existing Oracle Database Requirements |
Ensure that the existing Oracle Database is a certified database. To view a list of certified Oracle Databases, see Document ID 412431.1 on My Oracle Support (formerly Metalink). If you want to use a RAC database, which is configured on a virtual host, as the existing database, then refer to My Oracle Support note 561441.1. If you want to use Oracle Database 11g as the existing database, then see Installing Additional Management Service Using Existing Oracle Database 11g. |
|
|
Existing Oracle Database and Listener Status Requirements |
Ensure that the existing, certified Oracle Database and Listener are running. |
|
|
Password Verification Requirements |
Ensure that the profile of the Password Verification resource name has the "Default" value. If the Password Verification is enabled, repository creation may fail. |
|
|
NLS_LANG Environment Variable Requirements |
If your operating system is Linux, then ensure the NLS_LANG environment variable is set with a value that is compatible with the operating system default locale setting and the Management Repository database character set. 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. |
|
|
Management Repository Requirements |
Ensure that the existing Oracle Database is already configured with Oracle Management Repository 10g Release 2. |
|
|
Management Repository emkey Requirements |
Ensure that the Management Repository has the emkey for securing OMS. If the emkey is not present in the repository, then you may be prompted with a message to run a command before proceeding any further. The command mentioned in the message is incorred. Instead, restart the database, copy
|
|
|
Targets Monitored |
Remember that Enterprise Manager Grid Control will be able to monitor only those targets that are monitored by the Management Agent installed by the same user. |
If you are installing an additional OMS on another host that will access the same, shared Oracle Software Library as the one used by the first OMS on the first host then ensure that you install the additional OMS using the same user name as the one used on the first host. Also ensure that you use the same uid and gid. This is to ensure that both the OMSes have access to the same Oracle Software Library.
Setting UID and GID Before Installing an Additional OMS
To use the same uid and gid, do these before installing the additional OMS:
Run the "id" command to check the uid and gid on both the computers, one where OMS is already installed and another where you are going to install the additional OMS.
Decide on which computer the uid and gid need to be changed. On that computer, run the following commands to open the /etc/passwd file as root:
sudo -s vi /etc/passwd
Set the uid (third column) and gid (fourth column) as the ones used in the first computer.
Save the file.
Open a new terminal, login as root, and run the following command to change the ownership of the directories:
chown <username>:<groupname> -R <directory name>
Open a new terminal, login as the OMS user, and run the "id" command to verify that the uid and gui have changed.
If the changes are reflected, you can start the installation of the additional OMS.
Setting UID and GID After Installing an Additional OMS
If you have already installed the additional OMS on the second computer before making the UID and GID settings, then do these:
Run the "id" command to check the uid and gid on both the computers where OMS is already.
Decide on which computer the uid and gid need to be changed. On that computer, stop or kill all the OMS-related processes.
Run the following commands to open the /etc/passwd file as root:
sudo -s vi /etc/passwd
Change the uid (third column) and gid (fourth column) as the ones used in the first computer.
Save the file.
Now logout from the OMS that is running on this computer and re-login to ensure that the changes are reflected.
Open a new terminal, login as root, navigate to the OMS ORACLE_HOME (for example, /scratch/oms10203), and run the following command to change the ownership of the directories:
chown <username>:<groupname> -R <directory name>
Open a new terminal, login as the OMS user, and run the "id" command again to verify that the uid and gui have changed.
In parallel, open a new terminal and access the other computer where the first OMS and the shared Oracle Software Library are present. Login to the first OMS as root and navigate to the shared Oracle Software Library directory.
For example, if you the shared location is /net/OMS1/scratch/swlib, then run the following command:
cd /scratch/swlib
Run the following commands to change the ownership of this shared Oracle Software Library directory:
chown <username>:<groupname> -R <software library directory>
Now return to the second computer where the additional OMS is installed and start all the OMS-related processes that you had stopped.
Note:
If the shared Oracle Software Library is present on a different host, say other than the ones where the first OMS and second OMS are installed, then do these on that host:Create a user that is the same as the user name used on hosts where the first OMS and the second OMS are installed.
Change the uid and gid as described from Step 1 to Step 8.
Change the ownership of this shared software library folder as described in Step 10.
This section explains how you can install a full, base release of OMS, which is part of Enterprise Manager 10g Grid Control Release 2 or higher. For details about full, base releases and what these installation instructions can be use for, see Understanding What This Guide Helps You Install and Upgrade.
This option is best suited particularly when you want to install an additional OMS in a complete 10.2.0.1 environment -- where the repository, the main OMS (which comes along with the full installation of Enterprise Management Grid Control), and the other additional OMS are of 10.2.0.1 release. To understand the other installation scenarios, see Scenarios. Identify the environment that matches with the one described in that section.
Note:
If you want to install an additional OMS using Oracle Database 11g, then see Installing Additional Management Service Using Existing Oracle Database 11g.To install an additional OMS, follow these steps:
Start Oracle Universal Installer by running the runInstaller script (<DVD>/runInstaller on Linux and /DVD/setup.exe on Microsoft Windows) from the top directory of the DVD.
In the Specify Installation Type screen, select the third option (Additional Management Service).
In the Specify Installation Location screen, specify the full path to the parent directory (base directory), for example, /scratch/OracleHomes. The OMS home created during the installation is placed as a sub-directory under this parent directory. For example: oms10g.
Note:
Ensure you do not use symbolic links to specify the Oracle home path.The installer by default installs the selected products in the English language.
If you want to install the product in a different language, click Product Languages.
The Language Selection screen is displayed. Make the required language selections here. See Figure 8-3, "Language Selection" for details.
Click Next. The Product Specific Prerequisites Check screen appears.
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.
Depending on the status of the automatic checks, you must verify all warning 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. See Figure 8-5, "Product-Specific Prerequisite Checks" for more information.
Note:
You can also run these prerequisite checks in standalone mode, prior to starting the
runInstaller. For more information on running these prerequisite checks in standalone mode, see Running the Prerequisite Check in Standalone Mode.Click Next. The Specify Repository Database Configuration screen appears.
You must configure the additional OMS to establish the connections with the existing Management Repository.
Note:
The existing Management Repository database must be one of the following releases:Oracle Database 10g Release 1 (10.1.0.4), Enterprise Edition
Oracle Real Application Clusters 10g Release 1 (10.1.0.4)
Oracle9i Database Release 2 (9.2.0.6 and later), Enterprise Edition
Oracle9i Real Application Clusters Release 2 (9.2.0.6 and later)
The Management Repository database may also require patches to be applied, prior to successful installation. See Operating System, Browser, Target Certification for more information.
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.
Note:
When selecting an existing cluster database for creating a Management Repository, you must replace the SID value with the Management Service name.Enter the password for the SYSMAN user (the default Super Administrator account for Grid Control).
In the Management Service Security section, specify the password used to secure and lock the OMS.
Select Require Secure Communications for all agents if you want the secure OMS to communicate only with Secure Agents. This is optional, though recommended.
For example, if you have 10g R1 (10.1.n) agents in the Grid environment, and you have secured the OMS and selected the Require Secure Communications option, then all communication between the Oracle Management Service 10g R2 (10.2) and Oracle Management Agent 10g R1 (10.1) fails (because these agents have not been secured).
To secure Management Agent, run the following command from the Management Agent Oracle home of that particular target. However, note that even after securing the Management Agent, some data might still be transferred over the network without being encrypted.
emctl secure agent
See the section Password Restrictions and Recommendations in this chapter for more information.
Note:
The password that you specify here must be the same as the password that you specified to secure the OMS.Ensure that all OMS instances using the same repository must use the same secure password.
Click Next. The Specify Optional Configuration screen appears.
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.
Select the Configure Proxy check box (optional) if Grid Control 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. See Table 8-4, "Specify Proxy information - Input Fields" for a description of the input fields.
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.
Click Next. The Summary screen appears.
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:
Global Settings
Product Languages
Space Requirements
New Installations
For more information on each of the previously listed details, see the Grid Control online Help.
Verify the choices that you have made and click Install to start the installation. The installer begins installing the selected Oracle product.
During the installation, you are prompted to execute certain configuration scripts. These scripts and their locations are listed in the Execute Configuration Scripts dialog box that is displayed (only for Linux). Refer to Figure 8-12, "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.
The Configuration Assistants screen appears. At this point, the installer starts running the recommended configuration tools.
This screen displays the name, status, and the type of each configuration tool that Oracle recommends to be run before completing the installation. Refer to Table 8-6, "Grid Control Configuration Tools" to see the list of configuration tools that are run. In case of failure of any configuration assistant, refer to the logs and re-rerun the configuration assistants as described in Configuration Assistants Fail During Enterprise Manager Installation.
To complete the postinstallation configurations, log in as root (in a new terminal) and run the allroot.sh script from the Oracle home directory of the OMS (oms10g).
For example,
<OMS ORACLE HOME>/allroot.sh
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. For example, it might contain information about the URLs for particular Web applications.
Note:
If the Management Agent does not start up automatically when you restart the host, then do the following:Open the agentstup file from the Oracle home of the Management Agent:
$ORACLE_HOME/install/unix/scripts/agentstup
Edit the file to replace executingUser=$USER with executingUser=`id -un`. Then, save and exit the file.
Run the root.sh script from the Oracle home of the Management Agent:
$<ORACLE_HOME>/root.sh
Restart the Management Agent by running the following command from the Oracle home of the Management Agent:
$<ORACLE_HOME>/bin/emctl start agent
This is a one-time action to be taken. Step (1) to Step (3) will ensure that the Management Agent starts up automatically every time you restart the host in the future.
To install an additional OMS on Microsoft Windows 2008 or Microsoft Vista, follow these steps:
Download patch# 6640752 for Microsoft Windows (32-Bit) from My Oracle Support. You can access My Oracle Support at:
Extract the contents of the downloaded patch to a location on your system.
For example: C:\Patch_Download
Download the base release, that is, Enterprise Manager 10g Grid Control Release 2 (10.2.0.2.0) for Microsoft Windows.
Extract the contents of the downloaded base release to a location on your system. For example, C:\Base_Download
Edit the response file and make changes as described in this step.
The response file is available at:
C:\Base_Download\Disk1\install\response\oms.rsp
Make the following changes:
For the FROM_LOCATION parameter, specify the full path to the products.xml file.
For example:
FROM_LOCATION="C:\Base_Download\Disk1\oms\Disk1\stage\products.xml"
For the ORACLE_HOME parameter, specify the full path to the Oracle home directory of the OMS.
For example:
ORACLE_HOME="C:\OH102020\oms10g"
For the ORACLE_HOME_NAME parameter, specify the Oracle home name for OMS.
For example:
ORACLE_HOME_NAME="oms10g2"
For the s_agentHome parameter, specify the full path to the Oracle home directory of the Management Agent.
For example:
s_agentHome="C:\OH102020\agent10g"
For the s_agentHomeName parameter, specify the home name for Management Agent.
For example:
s_agentHomeName="agent10g2"
Note:
Ensure that the Oracle home location and the name you specify are not already existing.Run the setup.exe file:
C:\Patch_Download\cd\Disk1\install\setup.exe -ignoreDiskLabel -responseFile
C:\Base_Download\Disk1\install\response\oms.rsp
If the Management Agent does not restart, and if the value of agentTZRegion in the emd.properties file is GMT, then reset the time zone on the host where the Management Agent is installed using the following command. Here, Oracle_Home is the Oracle home directory of the Management Agent.
<Oracle_Home>\BIN>emctl resetTZ agent
Patch OMS and Management Agent to 10.2.0.5.0 release.
For patching instructions, see the Release Notes provided with the 10.2.0.5 patch set.
Note:
The steps outlined in this section describe how you can install an additional OMS in an environment where the repository and the main OMS are of 10.2.0.2 or 10.2.0.3 release for Linux, or 10.2.0.3 release for Microsoft Windows.If you want to install an additional OMS in an environment where the repository is of 10.2.0.4 or higher release, then see Installing 'Software-Only' and Configuring Later.
If you want to install an additional OMS using Oracle Database 11g, then see Installing Additional Management Service Using Existing Oracle Database 11g.
To install an additional OMS, follow these steps:
Convert the repository version to 10.2.0.1.0 by using the following SQL statement:
UPDATE sysman.mgmt_versions SET version = '10.2.0.1.0' where component_name='CORE'; commit;
Invoke the installer from the 10.2.0.1.0 DVD and choose the Additional Management Service option.
Provide the repository credentials for the Specify Database Configuration Screen and click Next, then stop here. (Do not proceed with the install.)
Go to the database Oracle Home where the repository is available, and connect to the database through SQLplus.
Update the repository version back to what is was, that is, 10.2.0.2.0 or 10.2.0.3.0, by using the following sql statement (This code sample given below uses 10.2.0.3.0 as an example):
UPDATE sysman.mgmt_versions SET version = '10.2.0.3.0' where component_name='CORE'; commit;
Return to the installer and click Next to proceed with the installation from where you stopped.
Once the installation of the base OMS (10.2.0.1 on Linux or 10.2.0.2 on Microsoft Windows) is complete, both the Management Agent and the OMS must be shut down immediately by running the following command:
<Agent Oracle Home>/bin/emctl stop agent
<OMS Oracle Home>/opmn/bin/opmnctl stopall
Patch the OMS to 10.2.0.2 or 10.2.0.3 using the 10.2.0.2 or 10.2.0.3 patch set, respectively. Refer to the Patch Set Notes that is supplied with the patch set to understand how the OMS can be patched.
Once the OMS has been patched successfully to 10.2.0.2 or 10.2.0.3, it will start automatically.
Restart the Management Agent from the Oracle Home:
<Agent Oracle Home>/bin/emctl/start agent
This section introduces you to the Install Software-Only installation type that can be used to install only the software binaries without configuring the installation. This installation type is not part of the OUI.
This section covers the following:
Installing 'Software-Only' and Configuring Later (Silent Mode)
Installing 'Software-Only' and Configuring Later (Silent Mode) on Newly Supported Platforms
The 'Installing Software-Only and Configuring Later' installation method allows you to install only the software binaries of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1 for Linux and 10.2.0.2 for Microsoft Windows), that is, without any configuration to the installation, and move over to the latest patch set version.
This saves time and effort, and is best suited when you are installing Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or higher for the first time in your environment. Since Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or higher are patch sets, you need to have a base installation to patch it. Using the 'Installing Software-Only and Configuring Later' installation method, you can install only the software of the base release and then configure it later by applying the latest patch set (10.2.0.4 or higher).
This installation option is also best suited for the following cases:
When you want to use your existing Oracle Database 10g Release 2 (10.2.0.3 or higher) to house the Management Repository, as this release of database is supported only with Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or higher.
When you want to install Enterprise Manager Grid Control on newly supported platforms. For example, SUSE Linux Enterprise Server 10 is a new platform that is supported by Enterprise Manager 10g Grid Control Release 5 (10.2.0.5).
When you want to install Grid Control during the Daylight Savings Time (DST) period. This option helps you install only the software binaries of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1), and migrate to the latest patch set release (10.2.0.4 or higher) directly that has the fix for DST-related issues.
IMPORTANT:
The 'Installing Software-Only and Configuring Later' installation method is supported only by Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or higher.
Do NOT use this method to patch or upgrade any existing, previous release of Grid Control. For example, if you already have Enterprise Manager 10g Grid Control Release 3 (10.2.0.3), then do NOT use this method to patch or upgrade to a higher release.
On Microsoft Windows, do the following:
Replace ./runInstaller with setup.exe and run the command.
Ensure that the environment variable PATH has the value %SystemRoot%\system32;%SystemRoot% . To set it, in Windows Explorer, right-click on My Computer, select Properties. On the Advanced tab, click Environment Variables. On the Environment Variables dialog, in the System Variables pane, check for the variable PATH. Click Edit to specify the required variable value.
This section describes how you can perform the following in silent mode:
Installing Enterprise Manager Grid Control Using a New Database
Installing Enterprise Manager Grid Control Using an Existing Database
Installing Additional Management Service Using Existing Oracle Database 11g
To install Grid Control using a new database, follow these steps:
From the following URL, download the software for the full release of Enterprise Manager Grid Control that was release for your platform:
http://www.oracle.com/technology/software/products/oem/index.html
Install the base release of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1 for Linux or 10.2.0.2 for Microsoft Windows) using the following command:
For UNIX Platforms:
./runInstaller -noconfig -silent -responseFile <absolute_path>/em_with_new_db.rsp -force
For Microsoft Windows Platforms:
setup.exe -noconfig -silent -responseFile <absolute_path>/em_with_new_db.rsp -force
Note:
The em_with_new_db.rsp file is packaged with Grid Control software. Before you run this file in silent mode, ensure that you edit the file and specify all the parameters required for a successful installation. To understand the mandatory parameters you need to specify, see Using Silent Mode to Install Enterprise Manager Grid Control Using a New Database of Chapter 9, "Installing Enterprise Manager Grid Control in Silent Mode".
If you want to specify different passwords for the database accounts, then ensure that the following entry is added to the em_with_new_db.rsp file:
sl_superAdminUsers={ "SYS" , "SYSTEM" , "SYSMAN" , "DBSNMP" }
Use the -force command only when you want to install in an existing, nonempty directory.
(For UNIX Platforms Only) Log in as a root user in a new terminal and run the following scripts on the host where you installed the base release of Grid Control.
If this is the first Oracle product you just installed on the host, then run the oraInstroot.sh script from the Central Inventory:
$ORACLE_HOME/oraInventory/oraInstRoot.sh
Run the allroot.sh script from the Oracle home directory of the database (for example, db10g):
$<ORACLE_HOME>/allroot.sh
Stop all the OPMN processes by running the following command from the Oracle home directory of the OMS (for example, oms10g):
$<ORACLE_HOME>/opmn/bin/opmnctl stopall
Apply 10.2.0.4 or higher patch set to OMS:
Note:
You can download the 10.2.0.4 or higher patch set from the following location:http://www.oracle.com/technology/software/products/oem/index.html
For each patch set, you might have to download either a single ZIP file or multiple ZIP files. If you have to download more than one ZIP file, then extract the contents of the ZIP files into one directory. For more information about these ZIP files and how you can extract them, see the README file associated with the patch set.
Copy the patchset.rsp file from the <Patchset_Download_Location>/response/ directory to a location on your host.
Edit the patchset.rsp file and make the following changes:
For 10.2.0.4.0 Release:
b_softwareonly = true
s_sysPassword = <sys user password>
ORACLE_HOME = <full_path_to_Oracle_home_of_OMS>
For 10.2.0.5.0 or Higher Release:
b_softwareonly = true s_sysPassword = <sys user password> ORACLE_HOME = <full_path_to_Oracle_home_of_OMS> oracle.iappserver.st_midtier:szl_InstanceInformation={"ias_password"}
Note:
The patchset.rsp file is packaged with the Patch Set. Before editing the file, you might want to take a backup of the file to another location in order to retain the original file. Alternatively, if you want to revert to the original file, then you can always take the file from the Patch Set DVD.
The variable oracle.iappserver.st_midtier:szl_InstanceInformation is the instance password for the current Oracle Application Server 10g. While specifying the password, you must use the braces and specify the password in double quotation marks. For example, if you want to specify the password welcome1, then the syntax would be:
oracle.iappserver.st_midtier:szl_InstanceInformation={"welcome1"}
Apply 10.2.0.4 or higher patch set to the Oracle home directory of the OMS (for example, oms10g) by running the following command:
./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp -force
Note:
Use the-force command only when you want to install in an existing, nonempty directory.(ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the OMS, run root.sh.
Apply 10.2.0.4 or higher patch set to the Management Agent:
Copy the patchset.rsp file from the <Patch Set DVD>/response/ directory to a location on your host.
Edit the patchset.rsp file and make the following changes:
ORACLE_HOME = <full_path_to_Oracle_home_of_Agent>
Apply 10.2.0.4 or higher patch set to the Oracle home directory of the Management Agent (for example, agent10g) by running the following command:
./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp -force
Note:
Use the-force command only when you want to install in an existing, nonempty directory.(ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the Management Agent, run root.sh.
(For Solaris Platforms Only), check the platform ID in the following file of the Oracle home directory of the database (for example, db10g). Ensure that the platform ID is set to 23. If it is not, then change it to 23.
$<ORACLE_HOME>Inventory/ContentsXML/oraclehomeproperties.xml
Apply the interim RDBMS patch# 4329444 to the Oracle home directory of the database (for example, db10g) that houses the Management Repository.
(ONLY FOR 10.2.0.4.0 RELEASE) Apply patch# 7040389 to the Oracle home directory of the OMS (for example, oms10g).
Ensure that the runConfig.sh file in the Oracle home directory of the database (for example, db10g) has 'execute' permission.
$<ORACLE_HOME>/oui/bin/runConfig.sh
After applying the patch, make the following settings to the environment variable - PERL5LIB:
Before making changes to the environment variable, take a backup of the variable:
For UNIX Platforms:
setenv PERL5LIB_BACKUP $PERL5LIB
For Microsoft Windows Platforms:
set PERL5LIB_BACKUP=%PERL5LIB%
Now make the following settings to the environment variable:
For UNIX platforms, set it to <OMS_ORACLE_HOME>/perl/lib/5.6.1
For Microsoft Windows platforms, set it to <OMS_ORACLE_HOME>/perl/5.6.1/lib
Configure Grid Control by running the ConfigureGC.pl script from the Oracle home directory of the OMS (for example, oms10g):
For UNIX Platforms:
$<ORACLE_HOME>/perl/bin/perl <OMS ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>
For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.
For Microsoft Windows Platforms:
$<ORACLE_HOME>\perl\5.6.1\bin\MSWin32-x86\perl <OMS ORACLE HOME>\sysman\install\ConfigureGC.pl <INSTALL_BASE_DIRECTORY>
For example, if the Oracle home directory of OMS is C:/Program Files/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be C:/Program Files/oracle/gc.
After the script runs successfully, Grid Control is configured to 10.2.0.4 or higher release. To verify the release, do the following:
Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status oms
Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status agent
Note:
For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command from the Oracle home directory of the OMS:emctl secure unlock -console
If the script fails, then review the database configuration log file. The database configuration log file is available in <DB_ORACLE_HOME>/cfgtoollogs/cfgfw. Scan through the logs to see if you have the following error message:
The installer has detected that there are background dbms jobs currently running in the Repository Database.
Note:
For Agent configuration logs, go to<AGENT_ORACLE_HOME>/cfgtoollogs/cfgfw. For OMS configuration logs, go to <OMS_ORACLE_HOME>/cfgtoollogs/cfgfw.If you see the error message, then before upgrading the Management Repository, do the following:
Stop the running DBMS jobs by logging in to SQL as SYSDBA and running the following command:
SQL> exec sysman.emd_maintenance.remove_em_dbms_jobs;
Stop and restart the database.
Check the status of SYSMAN user account:
- Log in to SQLPlus as SYSDBA and run the following query:
select username,account_status from dba_users;
- Ensure that the SYSMAN user account is in 'open' status. If the account is not in open status, then run the following command:
alter user SYSMAN account unlock;
- Commit the changes by running the following command:
commit;
Rerun the ConfigureGC.pl script.
After installation is complete, restart the DBMS jobs by running the following commands, one after the other:
SQL> exec sysman.emd_maintenance.submit_em_dbms_jobs;
SQL> commit;
Caution:
The steps outlined in this section describe how you can install Enterprise Manager Grid Control using an existing database. Ensure that your existing database is one of the certified databases supported by Enterprise Manager 10g Grid Control. To see a list of certified databases, see Document ID 412431.1 on My Oracle Support (formerly Metalink).Access My Oracle Support at the following URL, select Document ID from the Quick Find menu, quote the document number, and click GO to view the document:
If you want to use Oracle Database 11g as the existing database, then see Installing Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) Using Existing Oracle Database 11g.
To install Grid Control using an existing database, follow these steps:
From the following URL, download the software for the full release of Enterprise Manager Grid Control that was release for your platform:
http://www.oracle.com/technology/software/products/oem/index.html
If your existing database is configured with Database Control, then ensure that you deconfigure it before you begin the installation of Grid Control.
To deconfigure Database Control for a single instance database, run the following command from the Oracle home directory of the database (for example, db10g):
$<ORACLE HOME>/bin/emca -deconfig dbcontrol db -repos drop
To deconfigure Database Control for a Real Application Clusters (RAC) database, run the following command from the Oracle home directory of the database (for example, db10g):
$<ORACLE HOME>/bin/emca -deconfig dbcontrol db -repos drop - cluster
After deconfiguring the Database Control, connect to the database as SYS user and run the following SQL files from the Oracle home of the database:
<ORACLE_HOME>/rdbms/admin/dbmspool.sql
<ORACLE_HOME>rdbms/admin/prvtpool.plb
Note:
The command drops all the public synonyms starting with the following names created by any user for any schema:'MGMT$%'
'MGMT_%'
'SMP_EMD%'
'SMP_MGMT%'
'SETEMVIEWUSERCONTEXT'
'DBMS_SHARED_POOL'
'EMD_MNTR'
'ECM_UTIL'
Ensure that the database initialization parameters have the correct values to create a Management Repository in the database.
For information about the initialization parameters to be edited and the values to be provided, see Check Database Initialization Parameters.
Note:
If you do not set the database initialization parameters, the installation will fail and you will find the error message "OUI-10155:Error" in the following log file:<DB_HOME>/cfgtoollogs/cfgfw/installActions<time_stamp>.log
To resolve it, set the parameters with correct values as given in Check Database Initialization Parameters, deinstall the failed Oracle homes, and then restart the installation.
Log in to the database as SYSDBA and run the following command:
@?/rdbms/admin/dbmspool.sql
commit;
Install the base release of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1 for Linux or 10.2.0.2 for Microsoft Windows) using the following command:
For UNIX Platforms:
./runInstaller -noconfig -silent -responseFile <absolute_path>/em_using_existing_db.rsp -force
For Microsoft Windows Platforms:
setup.exe -noconfig -silent -responseFile <absolute_path>/em_using_existing_db.rsp -force
Note:
The em_using_existing_db.rsp file is packaged with Grid Control software. Before you run this file in silent mode, ensure that you edit the file and specify all the parameters required for a successful installation. To understand the mandatory parameters you need to specify, see Using Silent Mode to Install Enterprise Manager Grid Control Using an Existing Database of Chapter 9, "Installing Enterprise Manager Grid Control in Silent Mode".
Use the -force command only when you want to install in an existing, nonempty directory.
Stop all the OPMN processes by running the following command from the Oracle home directory of the OMS (for example, oms10g):
$<ORACLE_HOME>/opmn/bin/opmnctl stopall
(For UNIX Platforms Only) Log in as a root user in a new terminal and run the allroot.sh script from the Oracle home directory of the OMS (for example, oms10g):
$<ORACLE_HOME>/allroot.sh
Apply 10.2.0.4 or higher patch set to OMS:
Note:
You can download the 10.2.0.4 or higher patch set from the following location:http://www.oracle.com/technology/software/products/oem/index.html
For each patch set, you might have to download either a single ZIP file or multiple ZIP files. If you have to download more than one ZIP file, then extract the contents of the ZIP files into one directory. For more information about these ZIP files and how you can extract them, see the README file associated with the patch set.
Copy the patchset.rsp file from the <Patchset_Downloaded_Location>/response/ directory to a location on your host.
Edit the patchset.rsp file and make the following changes:
For 10.2.0.4.0 Release:
b_softwareonly = true
s_sysPassword = <sys user password>
ORACLE_HOME = <full_path_to_Oracle_home_of_OMS>
For 10.2.0.5.0 or Higher Release:
b_softwareonly = true s_sysPassword = <sys user password> ORACLE_HOME = <full_path_to_Oracle_home_of_OMS> oracle.iappserver.st_midtier:szl_InstanceInformation={"ias_password"}
Note:
The patchset.rsp file is packaged with the Patch Set. Before editing the file, you might want to take a backup of the file to another location in order to retain the original file. Alternatively, if you want to revert to the original file, then you can always take the file from the Patch Set DVD.
The variable oracle.iappserver.st_midtier:szl_InstanceInformation is the instance password for the current Oracle Application Server 10g. While specifying the password, you must use the braces and specify the password in double quotation marks. For example, if you want to specify the password welcome1, then the syntax would be:
oracle.iappserver.st_midtier:szl_InstanceInformation={"welcome1"}
Apply 10.2.0.4 or higher patch set to the Oracle home directory of the OMS (for example, oms10g) by running the following command:
./runInstaller -noconfig -silent -responseFile <exact_path>/patchset.rsp
(ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the OMS, run root.sh.
(ONLY FOR 10.2.0.4.0 RELEASE) Apply the following patches depending on how the database, which houses the Management Repository, is configured:
If the database is configured on a virtual host, then apply patch# 5667255 to the Oracle home directory of the OMS.
If the database is NOT configured on a virtual host, then apply patch# 7040389 to the Oracle home directory of the OMS
Apply 10.2.0.4 or higher patch set to the Management Agent:
Copy the patchset.rsp file from the <Patch Set DVD>/response/ directory to a location on your host.
Edit the patchset.rsp file and make the following changes:
ORACLE_HOME = <full_path_to_Oracle_home_of__Agent>
Apply 10.2.0.4 or higher patch set to the Oracle home directory of the Management Agent (for example, agent10g) by running the following command:
./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp -force
Note:
Use the-force command only when you want to install in an existing, nonempty directory.(ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the Management Agent, run root.sh.
After applying the patch, make the following settings to the environment variable - PERL5LIB:
Before making changes to the environment variable PERL5LIB, take a backup of the variable:
For UNIX Platforms:
setenv PERL5LIB_BACKUP $PERL5LIB
For Microsoft Windows Platforms:
set PERL5LIB_BACKUP=%PERL5LIB%
Now make the following settings to the variable:
For UNIX platforms, set it to <OMS_ORACLE_HOME>/perl/lib/5.6.1
For Microsoft Windows platforms, set it to <OMS_ORACLE_HOME>/perl/5.6.1/lib
Configure Grid Control by running the ConfigureGC.pl script from the Oracle home directory of the OMS (for example, oms10g):
For UNIX Platforms:
$<ORACLE_HOME>/perl/bin/perl <OMS ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>
For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.
For Microsoft Windows Platforms:
$<ORACLE_HOME>\perl\5.6.1\bin\MSWin32-x86\perl <OMS ORACLE HOME>\sysman\install\ConfigureGC.pl <INSTALL_BASE_DIRECTORY>
For example, if the Oracle home directory of OMS is C:/Program Files/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be C:/Program Files/oracle/gc.
After the script runs successfully, Grid Control is configured to 10.2.0.4 or higher release. To verify the release, do the following:
Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status oms
Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status agent
Note:
For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command:emctl secure unlock -console
If the script fails, then look at the OMS configuration log file. The OMS configuration log file is available in <OMS_ORACLE_HOME>/cfgtoollogs/cfgfw. Scan through the logs to see if you have the following error message:
The installer has detected that there are background dbms jobs currently running in the Repository Database.
Note:
For Agent configuration logs, go to<AGENT_ORACLE_HOME>/cfgtoollogs/cfgfw. For Database configuration logs, go to <DB_ORACLE_HOME>/cfgtoollogs/cfgfw.If you see the error message, then before upgrading the Management Repository, do the following:
Stop the running DBMS jobs by logging in to SQL as SYSDBA and running the following command:
SQL> exec sysman.emd_maintenance.remove_em_dbms_jobs;
Stop and restart the database.
Check the status of SYSMAN user account:
- Log in to SQLPlus as SYSDBA and run the following query:
select username,account_status from dba_users;
- Ensure that the SYSMAN user account is in 'open' status. If the account is not in open status, then run the following command:
alter user SYSMAN account unlock;
- Commit the changes by running the following command:
commit;
Rerun the ConfigureGC.pl script.
After installation is complete, restart the DBMS jobs by running the following commands, one after the other:
SQL> exec sysman.emd_maintenance.submit_em_dbms_jobs;
SQL> commit;
Caution:
The steps outlined in this section describe how you can install an additional OMS in an environment where the repository and the main OMS are of 10.2.0.4 or higher release. The main OMS refers to the one that was installed with the first installation of Grid Control. If you want to install an additional OMS in a 10.2.0.3 or 10.2.0.2 environment, then see Scenarios to understand the approach to be adopted.Also, this installation method is only for new, additional OMS to be installed. If you already have an OMS of a lower release, then the only way to upgrade it is to patch it using the Patch Set.
If you want to install an additional
To install an additional OMS, follow these steps:
From the following URL, download the software for the full release of Enterprise Manager Grid Control that was release for your platform:
http://www.oracle.com/technology/software/products/oem/index.html
Ensure that the database, which houses the repository, and its listener are running.
Log in to the database as SYSDBA user and convert the repository version from 10.2.0.4.0 or higher to 10.2.0.1.0 by running the following SQL statement:
UPDATE sysman.mgmt_versions SET version = '10.2.0.1.0' where component_name='CORE'; commit;
Invoke the installer of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1):
For UNIX Platforms:
./runInstaller -noconfig -silent -responseFile additional_mgmt_service.rsp
For Microsoft Windows Platforms:
setup.exe -noconfig -silent -responseFile additional_mgmt_service.rsp
Note:
Theadditional_mgmt_service.rsp file is packaged with Grid Control software. Before you run this file in silent mode, ensure that you edit the file and specify all the parameters required for a successful installation. To understand the mandatory parameters you need to specify, see Using Silent Mode to Install Additional Management Service of Chapter 9, "Installing Enterprise Manager Grid Control in Silent Mode".Log in to the database again as SYSDBA user and convert the repository version back to what is was, that is, 10.2.0.4.0 or higher, by using the following SQL statement. The following SQL statement uses 10.2.0.4.0 as an example; therefore, it you are installing a higher release, then replace it with that release number.
UPDATE sysman.mgmt_versions SET version = '10.2.0.4.0' where component_name='CORE'; commit;
(For UNIX Platforms Only) Log in as a root user in a new terminal and run the allroot.sh script from the Oracle home directory of the OMS (for example, oms10g):
$<ORACLE_HOME>allroot.sh
Stop all the OPMN processes by running the following command from the Oracle home directory of the OMS (for example, oms10g):
$<ORACLE_HOME>/opmn/bin/opmnctl stopall
Apply 10.2.0.4 or higher patch set to OMS:
Note:
You can download the 10.2.0.4 or higher patch set from the following location:http://www.oracle.com/technology/software/products/oem/index.html
For each patch set, you might have to download either a single ZIP file or multiple ZIP files. If you have to download more than one ZIP file, then extract the contents of the ZIP files into one directory. For more information about these ZIP files and how you can extract them, see the README file associated with the patch set.
Copy the patchset.rsp file from the <Patchset_Downloaded_Location>/response/ directory to a location on your host.
Edit the patchset.rsp file and make the following changes:
For 10.2.0.4.0 Release:
b_softwareonly = true
s_sysPassword = <sys user password>
ORACLE_HOME = <full_path_to_Oracle_home_of_OMS>
For 10.2.0.5.0 or Higher Release:
b_softwareonly = true s_sysPassword = <sys user password> ORACLE_HOME = <full_path_to_Oracle_home_of_OMS> oracle.iappserver.st_midtier:szl_InstanceInformation={"ias_password"}
Note:
The patchset.rsp file is packaged with the Patch Set. Before editing the file, you might want to take a backup of the file to another location in order to retain the original file. Alternatively, if you want to revert to the original file, then you can always take the file from the Patch Set DVD.
The variable oracle.iappserver.st_midtier:szl_InstanceInformation is the instance password for the current Oracle Application Server 10g. While specifying the password, you must use the braces and specify the password in double quotation marks. For example, if you want to specify the password welcome1, then the syntax would be:
oracle.iappserver.st_midtier:szl_InstanceInformation={"welcome1"}
Apply 10.2.0.4 or higher patch set to the Oracle home directory of the OMS (for example, oms10g) by running the following command:
./runInstaller -noconfig -silent -responseFile <exact_path>/patchset.rsp
(ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the OMS, run root.sh.
Apply the following patches depending on how the database, which houses the Management Repository, is configured:
If the database is configured on a virtual host, then apply patch# 5667255 to the Oracle home directory of the OMS.
If the database is NOT configured on a virtual host, then apply patch# 7040389 to the Oracle home directory of the OMS
Apply 10.2.0.4 or higher patch set to the Management Agent:
Copy the patchset.rsp file from the <Patch Set DVD>/response/ directory to a location on your host.
Edit the patchset.rsp file and make the following changes:
ORACLE_HOME = <full_path_to_Oracle_home_of__Agent>
Apply 10.2.0.4 or higher patch set to the Oracle home directory of the Management Agent (for example, agent10g) by running the following command:
./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp -force
Note:
Use the-force command only when you want to install in an existing, nonempty directory.(ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the Management Agent, run root.sh.
After applying the patch, make the following settings to the environment variable - PERL5LIB:
Before making changes to the environment variable PERL5LIB, take a backup of the variable:
For UNIX Platforms:
setenv PERL5LIB_BACKUP $PERL5LIB
For Microsoft Windows Platforms:
set PERL5LIB_BACKUP=%PERL5LIB%
Now make the following settings to the variable:
For UNIX platforms, set it to <OMS_ORACLE_HOME>/perl/lib/5.6.1
For Microsoft Windows platforms, set it to <OMS_ORACLE_HOME>/perl/5.6.1/lib
Configure Grid Control by running the ConfigureGC.pl script from the Oracle home directory of the OMS (for example, oms10g):
For UNIX Platforms:
$<ORACLE_HOME>/perl/bin/perl <OMS ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>
For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.
For Microsoft Windows Platforms:
$<ORACLE_HOME>\perl\5.6.1\bin\MSWin32-x86\perl <OMS ORACLE HOME>\sysman\install\ConfigureGC.pl <INSTALL_BASE_DIRECTORY>
For example, if the Oracle home directory of OMS is C:/Program Files/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be C:/Program Files/oracle/gc.
After the script runs successfully, Grid Control is configured to 10.2.0.4 release. To verify the release, do the following:
Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status oms
Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status agent
Note:
For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command:emctl secure unlock -console
To install Grid Control using an existing Oracle Database 11g, follow these steps:
From the following URL, download the software for the full release of Enterprise Manager Grid Control that was release for your platform:
http://www.oracle.com/technology/software/products/oem/index.html
If your existing database is configured with Database Control, then ensure that you deconfigure it before you begin the installation of Grid Control.
To deconfigure Database Control for a single instance database, run the following command from the Oracle home directory of the database (for example, db10g):
$<ORACLE HOME>/bin/emca -deconfig dbcontrol db -repos drop
To deconfigure Database Control for a Real Application Clusters (RAC) database, run the following command from the Oracle home directory of the database (for example, db10g):
$<ORACLE HOME>/bin/emca -deconfig dbcontrol db -repos drop - cluster
After deconfiguring the Database Control, connect to the database as SYS user and run the following SQL files from the Oracle home of the database:
<ORACLE_HOME>/rdbms/admin/dbmspool.sql
<ORACLE_HOME>rdbms/admin/prvtpool.plb
Note:
The command drops all the public synonyms starting with the following names created by any user for any schema:'MGMT$%'
'MGMT_%'
'SMP_EMD%'
'SMP_MGMT%'
'SETEMVIEWUSERCONTEXT'
'DBMS_SHARED_POOL'
'EMD_MNTR'
'ECM_UTIL'
Ensure that the database initialization parameters have the correct values to create a Management Repository in the database.
For information about the initialization parameters to be edited and the values to be provided, see Check Database Initialization Parameters.
Note:
If you do not set the database initialization parameters, the installation will fail and you will find the error message "OUI-10155:Error" in the following log file:<DB_HOME>/cfgtoollogs/cfgfw/installActions<time_stamp>.log
To resolve it, set the parameters with correct values as given in Check Database Initialization Parameters, deinstall the failed Oracle homes, and then restart the installation.
Log in to the database as SYSDBA and run the following command:
@?/rdbms/admin/dbmspool.sql
commit;
(ONLY FOR Oracle Enterprise Linux (OEL) 5.X and Red Hat Enterprise Linux 5.X) If /usr/lib/libdb.so.2 does not exist, then run the following command:
ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2
Install the base release of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1 for Linux or 10.2.0.2 for Microsoft Windows) using the following command:
For UNIX Platforms:
./runInstaller -noconfig -ignoreSysPrereqs -silent -responseFile <location of em_using_existing_db.rsp> use_prereq_checker=false b_skipDBValidation=true
For Microsoft Windows Platforms:
setup.exe -noconfig -ignoreSysPrereqs -silent -responseFile <location of em_using_existing_db.rsp> use_prereq_checker=false
Note:
Theem_using_existing_db.rsp file is packaged with Grid Control software. Before you run this file in silent mode, ensure that you edit the file and specify all the parameters required for a successful installation. To understand the mandatory parameters you need to specify, see Using Silent Mode to Install Enterprise Manager Grid Control Using an Existing Database of Chapter 9, "Installing Enterprise Manager Grid Control in Silent Mode".Stop all the OPMN processes by running the following command from the Oracle home directory of the OMS (for example, oms10g):
$<ORACLE_HOME>/opmn/bin/opmnctl stopall
(For UNIX Platforms Only) Log in as a root user in a new terminal and run the allroot.sh script from the Oracle home directory of the OMS (for example, oms10g):
$<ORACLE_HOME>/allroot.sh
Apply 10.2.0.5 or higher patch set to OMS:
Note:
You can download the 10.2.0.5 or higher patch set from the following location:http://www.oracle.com/technology/software/products/oem/index.html
For each patch set, you might have to download either a single ZIP file or multiple ZIP files. If you have to download more than one ZIP file, then extract the contents of the ZIP files into one directory. For more information about these ZIP files and how you can extract them, see the README file associated with the patch set.
Copy the patchset.rsp file from the <Patchset_Downloaded_Location>/response/ directory to a location on your host.
Edit the patchset.rsp file and make the following changes:
b_softwareonly = true s_sysPassword = <sys user password> ORACLE_HOME = <full_path_to_Oracle_home_of_OMS> oracle.iappserver.st_midtier:szl_InstanceInformation={"ias_password"}
Note:
The patchset.rsp file is packaged with the Patch Set. Before editing the file, you might want to take a backup of the file to another location in order to retain the original file. Alternatively, if you want to revert to the original file, then you can always take the file from the Patch Set DVD.
The variable oracle.iappserver.st_midtier:szl_InstanceInformation is the instance password for the current Oracle Application Server 10g. While specifying the password, you must use the braces and specify the password in double quotation marks. For example, if you want to specify the password welcome1, then the syntax would be:
oracle.iappserver.st_midtier:szl_InstanceInformation={"welcome1"}
Apply 10.2.0.5 or higher patch set to the Oracle home directory of the OMS (for example, oms10g) by running the following command:
./runInstaller -noconfig -silent -responseFile <exact_path>/patchset.rsp
From the Oracle home directory of the OMS, run root.sh.
Apply 10.2.0.5 or higher patch set to the Management Agent:
Copy the patchset.rsp file from the <Patch Set DVD>/response/ directory to a location on your host.
Edit the patchset.rsp file and make the following changes:
ORACLE_HOME = <full_path_to_Oracle_home_of__Agent>
Apply 10.2.0.5 or higher patch set to the Oracle home directory of the Management Agent (for example, agent10g) by running the following command:
./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp -force
Note:
Use the-force command only when you want to install in an existing, nonempty directory.From the Oracle home directory of the Management Agent, run root.sh.
After applying the patch, make the following settings to the environment variable - PERL5LIB:
Before making changes to the environment variable PERL5LIB, take a backup of the variable:
For UNIX Platforms:
setenv PERL5LIB_BACKUP $PERL5LIB
For Microsoft Windows Platforms:
set PERL5LIB_BACKUP=%PERL5LIB%
Now make the following settings to the variable:
For UNIX platforms, set it to <OMS_ORACLE_HOME>/perl/lib/5.6.1
For Microsoft Windows platforms, set it to <OMS_ORACLE_HOME>/perl/5.6.1/lib
Configure Grid Control by running the ConfigureGC.pl script from the Oracle home directory of the OMS (for example, oms10g):
For UNIX Platforms:
$<ORACLE_HOME>/perl/bin/perl <OMS ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>
For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.
For Microsoft Windows Platforms:
$<ORACLE_HOME>\perl\5.6.1\bin\MSWin32-x86\perl <OMS ORACLE HOME>\sysman\install\ConfigureGC.pl <INSTALL_BASE_DIRECTORY>
For example, if the Oracle home directory of OMS is C:/Program Files/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be C:/Program Files/oracle/gc.
After the script runs successfully, Grid Control is configured to 10.2.0.5 or higher release. To verify the release, do the following:
Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status oms
Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status agent
Note:
For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command:emctl secure unlock -console
If the script fails, then look at the OMS configuration log file. The OMS configuration log file is available in <OMS_ORACLE_HOME>/cfgtoollogs/cfgfw. Scan through the logs to see if you have the following error message:
The installer has detected that there are background dbms jobs currently running in the Repository Database.
Note:
For Agent configuration logs, go to<AGENT_ORACLE_HOME>/cfgtoollogs/cfgfw. For Database configuration logs, go to <DB_ORACLE_HOME>/cfgtoollogs/cfgfw.If you see the error message, then before upgrading the Management Repository, do the following:
Stop the running DBMS jobs by logging in to SQL as SYSDBA and running the following command:
SQL> exec sysman.emd_maintenance.remove_em_dbms_jobs;
Stop and restart the database.
Check the status of SYSMAN user account:
- Log in to SQLPlus as SYSDBA and run the following query:
select username,account_status from dba_users;
- Ensure that the SYSMAN user account is in 'open' status. If the account is not in open status, then run the following command:
alter user SYSMAN account unlock;
- Commit the changes by running the following command:
commit;
Rerun the ConfigureGC.pl script.
After installation is complete, restart the DBMS jobs by running the following commands, one after the other:
SQL> exec sysman.emd_maintenance.submit_em_dbms_jobs;
SQL> commit;
To install an additional OMS to connect to an existing Oracle Database 11g, follow these steps:
From the following URL, download the software for the full release of Enterprise Manager Grid Control that was release for your platform:
http://www.oracle.com/technology/software/products/oem/index.html
Ensure that the database, which houses the repository, and its listener are running.
Log in to the database as SYSDBA user and convert the repository version from 10.2.0.5.0 or higher to 10.2.0.1.0 by running the following SQL statement:
UPDATE sysman.mgmt_versions SET version = '10.2.0.1.0' where component_name='CORE'; commit;
Invoke the installer of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1):
For UNIX Platforms:
./runInstaller -noconfig -silent -responseFile additional_mgmt_service.rsp use_prereq_checker=false b_skipDBValidation=true
For Microsoft Windows Platforms:
setup.exe -noconfig -silent -responseFile additional_mgmt_service.rsp use_prereq_checker=false
Note:
Theadditional_mgmt_service.rsp file is packaged with Grid Control software. Before you run this file in silent mode, ensure that you edit the file and specify all the parameters required for a successful installation. To understand the mandatory parameters you need to specify, see Using Silent Mode to Install Additional Management Service of Chapter 9, "Installing Enterprise Manager Grid Control in Silent Mode".Log in to the database again as SYSDBA user and convert the repository version back to what is was, that is, 10.2.0.5.0 or higher, by using the following SQL statement. The following SQL statement uses 10.2.0.5.0 as an example; therefore, it you are installing a higher release, then replace it with that release number.
UPDATE sysman.mgmt_versions SET version = '10.2.0.5.0' where component_name='CORE'; commit;
(For UNIX Platforms Only) Log in as a root user in a new terminal and run the allroot.sh script from the Oracle home directory of the OMS (for example, oms10g):
$<ORACLE_HOME>allroot.sh
Stop all the OPMN processes by running the following command from the Oracle home directory of the OMS (for example, oms10g):
$<ORACLE_HOME>/opmn/bin/opmnctl stopall
Apply 10.2.0.5 or higher patch set to OMS:
Note:
You can download the 10.2.0.5 or higher patch set from the following location:http://www.oracle.com/technology/software/products/oem/index.html
For each patch set, you might have to download either a single ZIP file or multiple ZIP files. If you have to download more than one ZIP file, then extract the contents of the ZIP files into one directory. For more information about these ZIP files and how you can extract them, see the README file associated with the patch set.
Copy the patchset.rsp file from the <Patch Set DVD>/response/ directory to a location on your host.
Edit the patchset.rsp file and make the following changes:
b_softwareonly = true s_sysPassword = <sys user password> ORACLE_HOME = <full_path_to_Oracle_home_of_OMS> oracle.iappserver.st_midtier:szl_InstanceInformation={"ias_password"}
Note:
The patchset.rsp file is packaged with the Patch Set. Before editing the file, you might want to take a backup of the file to another location in order to retain the original file. Alternatively, if you want to revert to the original file, then you can always take the file from the Patch Set DVD.
The variable oracle.iappserver.st_midtier:szl_InstanceInformation is the instance password for the current Oracle Application Server 10g. While specifying the password, you must use the braces and specify the password in double quotation marks. For example, if you want to specify the password welcome1, then the syntax would be:
oracle.iappserver.st_midtier:szl_InstanceInformation={"welcome1"}
Apply 10.2.0.5 or higher patch set to the Oracle home directory of the OMS (for example, oms10g) by running the following command:
./runInstaller -noconfig -silent -responseFile <exact_path>/patchset.rsp
From the Oracle home directory of the OMS, run root.sh.
Apply 10.2.0.5 or higher patch set to the Management Agent:
Copy the patchset.rsp file from the <Patch Set DVD>/response/ directory to a location on your host.
Edit the patchset.rsp file and make the following changes:
ORACLE_HOME = <full_path_to_Oracle_home_of__Agent>
Apply 10.2.0.5 or higher patch set to the Oracle home directory of the Management Agent (for example, agent10g) by running the following command:
./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp -force
Note:
Use the-force command only when you want to install in an existing, nonempty directory.From the Oracle home directory of the Management Agent, run root.sh.
After applying the patch, make the following settings to the environment variable - PERL5LIB:
Before making changes to the environment variable PERL5LIB, take a backup of the variable:
For UNIX Platforms:
setenv PERL5LIB_BACKUP $PERL5LIB
For Microsoft Windows Platforms:
set PERL5LIB_BACKUP=%PERL5LIB%
Now make the following settings to the variable:
For UNIX platforms, set it to <OMS_ORACLE_HOME>/perl/lib/5.6.1
For Microsoft Windows platforms, set it to <OMS_ORACLE_HOME>/perl/5.6.1/lib
Configure Grid Control by running the ConfigureGC.pl script from the Oracle home directory of the OMS (for example, oms10g):
For UNIX Platforms:
$<ORACLE_HOME>/perl/bin/perl <OMS ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>
For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.
For Microsoft Windows Platforms:
$<ORACLE_HOME>\perl\5.6.1\bin\MSWin32-x86\perl <OMS ORACLE HOME>\sysman\install\ConfigureGC.pl <INSTALL_BASE_DIRECTORY>
For example, if the Oracle home directory of OMS is C:/Program Files/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be C:/Program Files/oracle/gc.
After the script runs successfully, Grid Control is configured to 10.2.0.5 release. To verify the release, do the following:
Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status oms
Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status agent
Note:
For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command:emctl secure unlock -console
This section describes how you can perform the following in GUI mode:
Note:
Do not use the response file because it will not be honored in GUI mode.Note:
Ensure that your existing database is one of the certified databases supported by Enterprise Manager 10g Grid Control. To see a list of certified databases, see Document ID 412431.1 on My Oracle Support (formerly Metalink).Access My Oracle Support at the following URL, select Document ID from the Quick Find menu, quote the document number, and click GO to view the document:
f you want to use Oracle Database 11g as the existing database, then see Installing Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) Using Existing Oracle Database 11g.
To install Grid Control using an existing database, follow these steps:
If your existing database is configured with Database Control, then ensure that you deconfigure it before you begin the installation of Grid Control.
To deconfigure Database Control for a single instance database, run the following command from the Oracle home directory of the database (for example, db10g):
$<ORACLE HOME>/bin/emca -deconfig dbcontrol db -repos drop
To deconfigure Database Control for a Real Application Clusters (RAC) database, run the following command from the Oracle home directory of the database (for example, db10g):
$<ORACLE HOME>/bin/emca -deconfig dbcontrol db -repos drop - cluster
After deconfiguring the Database Control, connect to the database as SYS user and run the following SQL files from the Oracle home of the database:
<ORACLE_HOME>/rdbms/admin/dbmspool.sql
<ORACLE_HOME>rdbms/admin/prvtpool.plb
Note:
The command drops all the public synonyms starting with the following names created by any user for any schema:'MGMT$%'
'MGMT_%'
'SMP_EMD%'
'SMP_MGMT%'
'SETEMVIEWUSERCONTEXT'
'DBMS_SHARED_POOL'
'EMD_MNTR'
'ECM_UTIL'
Ensure that the database initialization parameters have the correct values to create a Management Repository in the database.
For information about the initialization parameters to be edited and the values to be provided, see Check Database Initialization Parameters.
Note:
If you do not set the database initialization parameters, the installation will fail and you will find the error message "OUI-10155:Error" in the following log file:<DB_HOME>/cfgtoollogs/cfgfw/installActions<time_stamp>.log
To resolve it, set the parameters with correct values as given in Check Database Initialization Parameters, deinstall the failed Oracle homes, and then restart the installation.
Log in to the database as SYSDBA and run the following command:
@?/rdbms/admin/dbmspool.sql
commit;
Install the base release of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1 for Linux or 10.2.0.2 for Microsoft Windows) using the following command:
For UNIX Platforms:
./runInstaller -noconfig
For Microsoft Windows Platforms:
setup.exe -noconfig
Stop all the OPMN processes by running the following command from the Oracle home directory of the OMS (for example, oms10g):
$<ORACLE_HOME>/opmn/bin/opmnctl stopall
(For UNIX Platforms Only) Log in as a root user in a new terminal and run the allroot.sh script from the Oracle home directory of the OMS (for example, oms10g):
$<ORACLE_HOME>/allroot.sh
Apply 10.2.0.4 or higher patch set to the Oracle home directory of the OMS (for example, oms10g) by running the following command:
./runInstaller -noconfig b_softwareonly=true
(ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the OMS, run root.sh.
(ONLY FOR 10.2.0.4.0 RELEASE) Apply the following patches depending on how the database, which houses the Management Repository, is configured:
If the database is configured on a virtual host, then apply patch# 5667255 to the Oracle home directory of the OMS.
If the database is NOT configured on a virtual host, then apply patch# 7040389 to the Oracle home directory of the OMS
Apply 10.2.0.4 or higher patch set to the Oracle home directory of the Management Agent (for example, agent10g) by running the following command:
./runInstaller -noconfig
(ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the Management Agent, run root.sh.
After applying the patch, make the following settings to the environment variable - PERL5LIB:
Before making changes to the environment variable PERL5LIB, take a backup of the variable:
For UNIX Platforms:
setenv PERL5LIB_BACKUP $PERL5LIB
For Microsoft Windows Platforms:
set PERL5LIB_BACKUP=%PERL5LIB%
Now make the following settings to the variable:
For UNIX platforms, set it to <OMS_ORACLE_HOME>/perl/lib/5.6.1
For Microsoft Windows platforms, set it to <OMS_ORACLE_HOME>/perl/5.6.1/lib
Configure Grid Control by running the ConfigureGC.pl script from the Oracle home directory of the OMS (for example, oms10g):
For UNIX Platforms:
$<ORACLE_HOME>/perl/bin/perl <OMS ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>
For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.
For Microsoft Windows Platforms:
$<ORACLE_HOME>\perl\5.6.1\bin\MSWin32-x86\perl <OMS ORACLE HOME>\sysman\install\ConfigureGC.pl <INSTALL_BASE_DIRECTORY>
For example, if the Oracle home directory of OMS is C:/Program Files/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be C:/Program Files/oracle/gc.
After the script runs successfully, Grid Control is configured to 10.2.0.4 or higher release. To verify the release, do the following:
Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status oms
Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status agent
Note:
For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command:emctl secure unlock -console
If the script fails, then look at the OMS configuration log file. The OMS configuration log file is available in <OMS_ORACLE_HOME>/cfgtoollogs/cfgfw. Scan through the logs to see if you have the following error message:
The installer has detected that there are background dbms jobs currently running in the Repository Database.
Note:
For Agent configuration logs, go to<AGENT_ORACLE_HOME>/cfgtoollogs/cfgfw. For Database configuration logs, go to <DB_ORACLE_HOME>/cfgtoollogs/cfgfw.If you see the error message, then before upgrading the Management Repository, do the following:
Stop the running DBMS jobs by logging in to SQL as SYSDBA and running the following command:
SQL> exec sysman.emd_maintenance.remove_em_dbms_jobs;
Stop and restart the database.
Check the status of SYSMAN user account:
- Log in to SQLPlus as SYSDBA and run the following query:
select username,account_status from dba_users;
- Ensure that the SYSMAN user account is in 'open' status. If the account is not in open status, then run the following command:
alter user SYSMAN account unlock;
- Commit the changes by running the following command:
commit;
Rerun the ConfigureGC.pl script.
After installation is complete, restart the DBMS jobs by running the following commands, one after the other:
SQL> exec sysman.emd_maintenance.submit_em_dbms_jobs;
SQL> commit;
Caution:
The steps outlined in this section describe how you can install an additional OMS in an environment where the repository and the main OMS are of 10.2.0.4 or higher release. The main OMS refers to the one that was installed with the first installation of Grid Control. If you want to install an additional OMS in a 10.2.0.3 or 10.2.0.2 environment, then see Scenarios to understand the approach to be adopted.Also, this installation method is only for new, additional OMS to be installed. If you already have an OMS of a lower release, then the only way to upgrade it is to patch it using the Patch Set.
If you want to install an additional OMS to connect to Oracle Database 11g, then see Installing Additional Management Service Using Existing Oracle Database 11g.
To install additional OMS, follow these steps:
Ensure that the database, which houses the repository, and its listener are running.
Log in to the database as SYSDBA user and convert the repository version from 10.2.0.4.0 or higher to 10.2.0.1.0 by running the following SQL statement:
UPDATE sysman.mgmt_versions SET version = '10.2.0.1.0' where component_name='CORE'; commit;
Invoke the installer of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1):
For UNIX Platforms:
./runInstaller -noconfig
For Microsoft Windows Platforms:
setup.exe -noconfig
Log in to the database again as SYSDBA user and convert the repository version back to what is was, that is, 10.2.0.4.0 or higher, by using the following SQL statement. The following SQL statement uses 10.2.0.4.0 as an example; therefore, it you are installing a higher release, then replace it with that release number.
UPDATE sysman.mgmt_versions SET version = '10.2.0.4.0' where component_name='CORE'; commit;
(For UNIX Platforms Only) Log in as a root user in a new terminal and run the allroot.sh script from the Oracle home directory of the OMS (for example, oms10g):
$<ORACLE_HOME>allroot.sh
Stop all the OPMN processes by running the following command from the Oracle home directory of the OMS (for example, oms10g):
$<ORACLE_HOME>/opmn/bin/opmnctl stopall
Apply 10.2.0.4 or higher patch set to the Oracle home directory of the OMS (for example, oms10g) by running the following command:
./runInstaller -noconfig b_softwareonly=true
(ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the OMS, run root.sh.
Apply the following patches depending on how the database, which houses the Management Repository, is configured:
If the database is configured on a virtual host, then apply patch# 5667255 to the Oracle home directory of the OMS.
If the database is NOT configured on a virtual host, then apply patch# 7040389 to the Oracle home directory of the OMS
Apply 10.2.0.4 or higher patch set to the Oracle home directory of the Management Agent (for example, agent10g) by running the following command:
./runInstaller -noconfig
(ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the Management Agent, run root.sh.
After applying the patch, make the following settings to the environment variable - PERL5LIB:
Before making changes to the environment variable PERL5LIB, take a backup of the variable:
For UNIX Platforms:
setenv PERL5LIB_BACKUP $PERL5LIB
For Microsoft Windows Platforms:
set PERL5LIB_BACKUP=%PERL5LIB%
Now make the following settings to the variable:
For UNIX platforms, set it to <OMS_ORACLE_HOME>/perl/lib/5.6.1
For Microsoft Windows platforms, set it to <OMS_ORACLE_HOME>/perl/5.6.1/lib
Configure Grid Control by running the ConfigureGC.pl script from the Oracle home directory of the OMS (for example, oms10g):
For UNIX Platforms:
$<ORACLE_HOME>/perl/bin/perl <OMS ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>
For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.
For Microsoft Windows Platforms:
$<ORACLE_HOME>\perl\5.6.1\bin\MSWin32-x86\perl <OMS ORACLE HOME>\sysman\install\ConfigureGC.pl <INSTALL_BASE_DIRECTORY>
For example, if the Oracle home directory of OMS is C:/Program Files/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be C:/Program Files/oracle/gc.
After the script runs successfully, Grid Control is configured to 10.2.0.4 release. To verify the release, do the following:
Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status oms
Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status agent
Note:
For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command:emctl secure unlock -console
Enterprise Manager Grid Control is now supported on the following new platforms:
Oracle Enterprise Linux (OEL) 5.0, 5.1, 5.2
Red Hat Enterprise Linux 5.0, 5.1, 5.2
SUSE Linux Enterprise 10
HP- UX Itanium 11.31
AIX 6.1
HP-UX PA-RISC 11.31
However, the release that is supported on these new platforms is Enterprise Manager 10g Grid Control Release 5 (10.2.0.5), which is a patch set. There was no full release in the past for these platforms. Ideally, you must install the full release and then patch it to 10.2.0.5, but since there was no full release on these platforms, you can follow the instructions outlined in this section to directly install the patch set on these platforms.
Note:
Enterprise Manager Grid Control is also supported on Microsoft Windows 2008 and Microsoft Windows Vista. For instructions to install Enterprise Manager Grid Control on these platforms, see Installing on Microsoft Windows 2008 and Microsoft Windows Vista.This section covers the following:
Installing Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) Using Existing Database
Installing an Additional Oracle Management Service Release 5 (10.2.0.5)
Note:
Before staring the installation, as a prerequisite, ensure that you have installed all the required packages and kernel parameters as described in Appendix D, "Platform-Specific Package and Kernel Requirements". Particularly, if you are installing on Oracle Enterprise Linux 5 or RedHat Enterprise Linux 5, then ensure that you have the default RPM.From the following URL, download the software for the full release of Enterprise Manager Grid Control that was release for your platform:
http://www.oracle.com/technology/software/products/oem/index.html
Note:
For example, if you are installing Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) on Red Hat Enterprise Linux 5.0, then download the full release, that is, Enterprise Manager 10g Grid Control Release 2 (10.2.0.1) released for Linux32-bit platform. Similarly, if you are installing on HP-UX Itanium, then download the full release, that is, Enterprise Manager 10g Grid Control Release 3 (10.2.0.3) that was released for HP-UX Itanium.(ONLY FOR Oracle Enterprise Linux (OEL) 5.X and Red Hat Enterprise Linux 5.X) If /usr/lib/libdb.so.2 does not exist, then run:
ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2
If your existing database is configured with Database Control, then ensure that you deconfigure it before you begin the installation of Enterprise Manager Grid Control.
To deconfigure Database Control for a single instance database, run the following command:
$ORACLE HOME/bin/emca -deconfig dbcontrol db -repos drop
Where $ORACLE_HOME is the Oracle home directory of existing Database.
After deconfiguring the Database Control, connect to the database as SYS user and run the following SQL files from the Oracle home of the database:
<ORACLE_HOME>/rdbms/admin/dbmspool.sql
<ORACLE_HOME>rdbms/admin/prvtpool.plb
Note:
The command drops all the public synonyms starting with the following names created by any user for any schema:'MGMT$%'
'MGMT_%'
'SMP_EMD%'
'SMP_MGMT%'
'SETEMVIEWUSERCONTEXT'
'DBMS_SHARED_POOL'
'EMD_MNTR'
'ECM_UTIL'
Verify whether all the database initialization parameters are set correctly. For information about the database initialization parameters, see Check Database Initialization Parameters.
Install the DBMS_SHARED_POOL package by running the below commands from the Oracle home directory of the Database:
Login to the database as sysdba
Run the below command:
SQL>@?/rdbms/admin/dbmspool.sql
SQL> commit;
Invoke the runInstaller:
./runInstaller -noconfig -ignoreSysPrereqs -silent -responseFile <location of em_using_existing_db.rsp> use_prereq_checker=false
Note:
The em_using_existing_db.rsp file is packaged with Enterprise Manager Grid Control software. Before you run this file in silent mode, ensure that you edit the file and specify all the parameters required for a successful installation. To understand the mandatory parameters you need to specify, see Using Silent Mode to Install Enterprise Manager Grid Control Using an Existing Database.If this is the first Oracle product you just installed on the host, then run the orainstRoot.sh script from the Central Inventory as a root user:
$ORACLE_HOME/oraInventory/orainstRoot.sh
Run the allroot.sh from the Oracle home of the OMS as a root user
Stop all OPMN processes by running the following command from the Oracle home directory of the OMS:
$ORACLE_HOME/opmn/bin/opmnctl stopall
Copy the patchset.rsp file from the <Patch Set DVD>/response/directory to a location on your host.
Note:
The patchset.rsp file is packaged with the Patch Set. Before editing the file, you might want to take a backup of the file to another location in order to retain the original file. Alternatively, if you want to revert to the original file, then you can always take the file from the Patch Set DVD.For 10.2.0.4.0 Release:
b_softwareonly = true s_sysPassword = <sys user password> ORACLE_HOME = <full_path_to_Oracle_home_of_OMS>
For 10.2.0.5.0 or Higher Release:
b_softwareonly = true
s_sysPassword = <sys user password>
ORACLE_HOME = <full_path_to_Oracle_home_of_OMS>
oracle.iappserver.st_midtier:szl_InstanceInformation={"ias_password"}
The variable oracle.iappserver.st_midtier:szl_InstanceInformation is the instance password for the current Oracle Application Server 10g. The ias_admin user is the administrative user for Oracle Application Server instances and is required for software update installation on middle-tiers.
While specifying the password, you must use the braces and specify the password in double quotation marks. For example, if you want to specify the password welcome1, then the syntax would be:
oracle.iappserver.st_midtier:szl_InstanceInformation={"welcome1"}
This password is same as the SYSMAN password that you specified when you first installed the Grid control in your environment.
Note:
After installing the Grid control in your environment if you change the SYSMAN password then ias_admin password will not get changed.To change the ias_admin password, go to the Oracle home directory of OMS and run the below command:
$ORACLE_HOME/bin/emctl set password <Old ias_admin password> <New ias_admin Password>
Note:
If you don't remember the old ias_admin password then follow the instructions from Document ID 280587.1 on My Oracle Support (formerly Metalink) at http://metalink.oracle.com/Apply the 10.2.0.5 patch set to the Oracle home directory of the OMS (for example, /abc/product/oms10g) by running the following command:
./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp
(ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the OMS, run root.sh.
Apply the 10.2.0.5 patch set to the Oracle home directory of the Management Agent
Copy the patchset.rsp file from the <Patch Set DVD>/response/directory to a location on yourhost.
Edit patchset.rsp to include the following:
ORACLE_HOME = < Oracle home directory of the Oracle Management Agent>
Apply the 10.2.0.5 patch set to the Oracle home directory of the Management Agent:
./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp
(ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the Management Agent, run root.sh.
Set the PERL5LIB as <ORACLE_HOME>/perl/lib/5.6.1 where <ORACLE_HOME> is the Oracle home directory of the OMS.
Execute the following script from the Oracle home directory of the OMS to complete the Grid Control 10.2.0.5 install:
$ORACLE_HOME/perl/bin/perl <ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>
For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.
After the script runs successfully, Grid Control is configured to 10.2.0.5 or higher release. To verify the release, do the following:
Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status oms
Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status agent
Note:
For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command from the Oracle home directory of the OMS:emctl secure unlock -console
From the following URL, download the software for the full release of Enterprise Manager Grid Control that was release for your platform:
http://www.oracle.com/technology/software/products/oem/index.html
Note:
For example, if you are installing Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) on Red Hat Enterprise Linux 5.0, then download the full release, that is, Enterprise Manager 10g Grid Control Release 2 (10.2.0.1) released for Linux32-bit platform. Similarly, if you are installing on HP-UX Itanium, then download the full release, that is, Enterprise Manager 10g Grid Control Release 3 (10.2.0.3) that was released for HP-UX Itanium.(ONLY FOR Oracle Enterprise Linux (OEL) 5.X and Red Hat Enterprise Linux 5.X). If /usr/lib/libdb.so.2 does not exist, then run:
ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2
Ensure that the database, which houses the repository, and its listener are running.
Log in to the database as SYSDBA user and convert the repository version from 10.2.0.5.0 to 10.2.0.1.0 by running the following SQL statement:
UPDATE sysman.mgmt_versions SET version = '10.2.0.1.0' where component_name='CORE'; commit;
Invoke the installer of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1):
./runInstaller -noconfig -ignoreSysPrereqs -silent -responseFile <location of additional_mgmt_service.rsp> use_prereq_checker=false b_skipDBValidation=true
Note:
The additional_mgmt_service.rsp file is packaged with Enterprise Manager Grid Control software. Before you run this file in silent mode, ensure that you edit the file and specify all the parameters required for a successful installation. To understand the mandatory parameters you need to specify, see Using Silent Mode to Install Additional Management Service.Log in to the database again as SYSDBA user and convert the repository version back to what is was, that is, 10.2.0.5.0, by using the following SQL statement:
UPDATE sysman.mgmt_versions SET version = '10.2.0.5.0' where component_name='CORE'; commit;
If this is the first Oracle product you just installed on the host, then run the orainstRoot.sh script from the Central Inventory as a root user:
$ORACLE_HOME/oraInventory/orainstRoot.sh
Run the allroot.sh from the Oracle home of the OMS as a root user
Stop all the OPMN processes by running the following command from the Oracle home directory of the OMS:
$ORACLE_HOME/opmn/bin/opmnctl stopall
Copy the patchset.rsp file from the <Patch Set DVD>/response/directory to a location on your host.
Note:
The patchset.rsp file is packaged with the Patch Set. Before editing the file, you might want to take a backup of the file to another location in order to retain the original file. Alternatively, if you want to revert to the original file, then you can always take the file from the Patch Set DVD.For 10.2.0.4.0 Release:
b_softwareonly = true s_sysPassword = <sys user password> ORACLE_HOME = < full_path_to_Oracle_home_of_OMS >
For 10.2.0.5.0 or Higher Release:
b_softwareonly = true
s_sysPassword = <sys user password>
ORACLE_HOME = < full_path_to_Oracle_home_of_OMS >oracle.iappserver.st_midtier:szl_InstanceInformation={"ias_password"}
The variable oracle.iappserver.st_midtier:szl_InstanceInformation is the instance password for the current Oracle Application Server 10g. The ias_admin user is the administrative user for Oracle Application Server instances and is required for software update installation on middle-tiers.
While specifying the password, you must use the braces and specify the password in double quotation marks. For example, if you want to specify the password welcome1, then the syntax would be:
oracle.iappserver.st_midtier:szl_InstanceInformation={"welcome1"}
This password is same as the SYSMAN password that you specified when you first installed the Grid control in your environment.
Note:
After installing the Grid control in your environment if you change the SYSMAN password then ias_admin password will not get changed.To change the ias_admin password, go to the Oracle home directory of OMS and run the below command:
$ORACLE_HOME/bin/emctl set password <Old ias_admin password> <New ias_admin Password>
Note:
If you do not remember the old ias_admin password then follow the instructions from Document ID 280587.1 on My Oracle Support (formerly Metalink) at http://metalink.oracle.com/Apply the 10.2.0.5 patch set to the Oracle home directory of the OMS (for example, /abc/product/oms10g) by running the following command:
./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp
(ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the OMS, run root.sh.
Apply the 10.2.0.5 patch set to the Oracle home directory of the Management Agent
Copy the patchset.rsp file from the <Patch Set DVD>/response/directory to a location on yourhost
Edit patchset.rsp to include the following:
ORACLE_HOME = < Oracle home directory of the Management agent >
Apply the 10.2.0.5 patch set to the Oracle home directory of the Agent
./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp
(ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the Management Agent, run root.sh.
Set the PERL5LIB as <ORACLE_HOME>/perl/lib/5.6.1. where <ORACLE_HOME> is the Oracle home directory of the OMS.
Execute the following script to from the Oracle home directory of the OMS to complete the 10.2.0.5.0 install:
$ORACLE_HOME/perl/bin/perl <ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>
For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.
After the script runs successfully, Grid Control is configured to 10.2.0.4 or higher release. To verify the release, do the following:
Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status oms
Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:
$<ORACLE_HOME>/bin/emctl status agent
Note:
For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command from the Oracle home directory of the OMS:emctl secure unlock -console
|
 Copyright © 1996, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|