Oracle enterprise manager console 10g install

Password Restrictions and Recommendations. Passwords cannot be Oracle reserved words. 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:. 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. Return to the dialog box shown in Figure after executing the scripts, and click OK to continue the installation.

The Configuration Assistants screen appears. At this point, the installer starts running the configuration assistants. This screen displays the name, status, and the type of each configuration tool that Oracle recommends to be run before completing the installation. Table lists all the configuration tools that are run during a typical Enterprise Manager installation Install Enterprise Manager Using a new database. Table Enterprise Manager Configuration Tools.

Footnote 1 Depending on the installation type that you have selected, any or all of the configuration tools listed in this table will be run. For more information on the installation logs that are created and their locations, see Appendix F, "Installation and Configuration Log File Locations". In case of failure of any configuration assistant, refer to the logs and re-rerun the configuration assistants as described in AppendixA, "Configuration Assistants Fail During Enterprise Manager Installation".

This log file contains all the configuration tool logs. After successfully running all the recommended configuration tools, the End of Installation screen appears. This screen displays some important information about the products you have installed. Select this option if you want to perform a complete Enterprise Manager Grid Control installation and have a qualified existing database in which to create the Management Repository. The database can be local or remote to the machine on which you are installing.

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

If you plan to use an existing database for your Management Repository creation, check all software requirements for the database and host, as well as for the repository.

Ensure that the profile of the Password Verification resource name has the "Default" value. If the Password Verification is enabled, repository creation may fail. Ensure there is sufficient physical memory available for this installation type. See Table , "Enterprise Manager Installation Options" for more information on the recommended hard disk and memory requirements.

Ensure the database release should be 9. Ensure the name of the host on which the installation is being performed is neither be localhost. See Chapter3, "Check Database Initialization Parameters" for a detailed list of database initialization parameter settings based on the Enterprise Manager deployment size.

See Chapter 1, "Preinstallation Requirements" for more information on hardware and software requirements. The initialization parameters must be set correctly for your qualified existing Enterprise Edition database to be able to run a Management Repository. You should also set all fixed parameters for your Management Repository database. The following table lists the parameters and their fixed values that must be met for successful Management Repository database creation.

These parameters are verified by Oracle Universal Installer prerequisite checks during installation. Table Fixed Initialization Parameter Values. Footnote 2 The TEMP space is an initialization parameter only when you are performing an Enterprise Manager installation using a new database. The variable parameter setting values are based on the size of the Enterprise Manager Grid Control environment. For the sake of clarity, the environment has been categorized as Small, Medium, and Large based on the number of targets in the environment, where:.

Table Variable Initialization parameter Values. Footnote 1 One redo log group with four members each of the listed size. For information on the specific values for language, territory, or character set, refer to the Globalization Support Guide of the Oracle product that you are using. A Typical Installation Scenario. If you choose to install Enterprise Manager using an existing database, you must provide the location of an existing database where the installer will create the repository.

Here again, the database should be of release 9. If you have an earlier database release installed, you must first upgrade this database instance to the specified minimum release 9.

All the Oracle homes created during the installation are placed as subdirectories under this parent directory. For example: oms10g , and agent10g. The Language Selection screen appears. Make the required language selections here, and click Next. See Figure , "Language Selection" for details. The Specify Inventory Directory and Credentials screen appears if Enterprise Manager is the first Oracle product that you are installing on the machine.

The Specify Repository Database Configuration screen appears. Figure Specify Repository Database Configuration. Specify the connection details for the existing database in which the Management Repository should be created. The Management Repository database can be created on the following database releases:. Oracle Database 10 g Release 1 The SID identifies a specific Oracle Database and distinguishes it from other databases on the computer.

Enter the password for the SYS user. You can also click Continue. Specify the full path of the file locations for the previously mentioned tablespaces.

The directories you specify for these tablespaces must already exist for repository creation to succeed. For raw devices, you must partition your disk before specifying its location. Note that raw device path names vary across volume managers. Ensure to use the right path format for your raw device locations. If you do not have the complete path for the tablespaces, click Prefill Tablespace Location. Note that the Prefill Tablespace button will be enabled only after you have specified all the Database Connection details.

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

As the name suggests, all the fields on this screen are optional, and are disabled, by default. In the Configure Email Notification section, specify an appropriate e-mail address, and the corresponding SMTP server name in this section. You will receive information on important developments and events in Grid Control, including critical alerts, at this e-mail address.

The SMTP server is the name of the mail server for example mail. If you prefer, you may also enter this information through the Enterprise Manager console after installation by clicking Patching Setup , under Setup. See Table , "Specify Proxy information - Input Fields" for a description on each of the input fields in this section. Specify the Management Service Security, and Repository Database passwords that are used to secure your entire Grid Control environment.

For example, if you have 10 g R1 To secure an agent, execute the following command from the agent Oracle home of that particular target:. See the section on Password Restrictions and Recommendations in this chapter for more information. Depending on the installation type, this screen also provides any or all of the following details:.

Verify the choices that you have made and click Install to start the installation. Refer to Figure , "Execute Configuration Scripts". To execute these scripts, go to the computer window, log in as root , and run these configuration scripts. Return to the Execute Configuration Scripts dialog box after executing the scripts, and click OK to continue the installation.

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

During the installation process, if the SYSMAN schema already exists in the database that you specify for the Management Repository, the installer will prompt you to manually drop the schema. If this is not done, the installer will automatically drop the schema before proceeding to the next configuration assistant. If the Oracle Management Service Configuration Assistant fails before completion, you can click Retry , which automatically cleans up the repository when the configuration tool is rerun.

To manually clean up the repository, use the following command:. Refer to Oracle Enterprise Manager Advanced Configuration for further instructions on how to drop the existing repository from the database. Select this option if you need to add an additional Management Service to your environment. Note that setting credentials for Oracle MetaLink is not necessary for this installation type, as the Management Repository is not affected. Ensure the hard disk and physical memory requirements are met.

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

The Management Repository database may also require patches to be applied, prior to successful installation. In the Repository Database Connection Details section, specify a fully qualified host name on which the Management Repository database is installed, the repository port, and the SID system identifier for the database instance.

The SID identifies a specific Oracle database and distinguishes it from other databases on the computer. See the section Password Restrictions and Recommendations in this chapter for more information. Ensure that all Management Service instances using the same repository must use the same secure password. Select the Configure Proxy check box optional if Enterprise Manager is using a proxy server for external access.

Specify the properties for the proxy server host name enter a fully qualified host name , port number, Do Not Proxy for list, and the Proxy user credentials. Specify an appropriate Realm value. This becomes a mandatory field only if the proxy server credentials have been configured using a Realm, in which case, you must specify an appropriate Realm value. A Realm is a string value that is assigned by the proxy server to indicate the secure space that requires authentication.

This screen displays a summary of the options that you have selected during the installation process. Depending on the installation type, this screen displays any or all of the following details:.

For more information on each of the previously listed details, see the Enterprise Manager online Help. The installer begins installing the selected Oracle product. These scripts and their locations are listed in the Execute Configuration Scripts dialog box that is displayed only for Linux.

To execute these scripts, go to the computer window, log in as root and run these configuration scripts. At this point, the installer starts running the recommended configuration tools. After successfully running all the recommended configuration tools, click Next.

The End of Installation screen appears. This screen tells you whether or not the installation was successful and displays some important information that you must remember about the product you have installed. Select this option to install the Management Agent in an Oracle home directory on a specified host target. Each host you wish to monitor must have a Management Agent installed.

You may also perform silent installations using a response file. Use the Agent Deploy application to perform a new agent installation standalone or cluster agent or a shared agent installation.

To see which group was used to install the Application Server, type ls -l on the command line in the directory containing opmn. To see the groups to which you belong, type groups on the command line. If you choose the Custom installation type or the Advanced database configuration option during the installation, the Installer does not display the OEM setup screens. Furthermore, you can also use DBCA after the installation to configure Database Control for a database that was not previously configured to use it.

However, if you decide to setup your own Database, you must install the Database Control manually. Setup your own Database and manually install the Database Control. The Database Control relies on various underlying technologies to discover, monitor, and administer the Oracle Database environment.

From the Database Control, you can monitor and administer a single Oracle Database instance. More information to setup your own Database can be found here:. Examples for Setup Files can be found here:. WORLD Email address for notification: martin dot zahn at akadia dot ch Email gateway for notification: mailhost Password for dbsnmp: xxxxxxx Password for sysman: xxxxxxx Password for sys: xxxxxxx.

Now wait about 10 Minutes to complete! M oracle. However, note that if you upgrade a 10g Release 1 cluster database configured with Database Control to 10g Release 2, the 10g Release 1 Database Control configuration will be retained. The 10g Release 1 Database Control has a Database Console running on each node for the real-application cluster. The console will still be started on each individual node.

If you wish to modify the configuration, use the following command:. This command reconfigures the current Database Control setup and:. You may use this command to start the console on more than one node. In this scenario, there will be two Database Control consoles running, one on node1 and the other on node5.

From either of these consoles, you can manage and monitor all targets in the cluster. The above command prompts for the database unique name for the cluster database.

This will print the current configuration onto the screen, indicating the nodes that have consoles running on them and the consoles where each agent is uploading. For configuring Enterprise Manager for a new cluster instance of a database or ASM storage, use the following command:. On cluster databases, another common operation is the creation and deletion of database instances. After you create a new instance, you can run EMCA to configure Database Control or central agent management for that instance using the command emca -addInst db.

Running EMCA does not create the actual database instance; it only configures Enterprise Manager so that you can manage the instance in a way consistent with the rest of the cluster database instances. When configuring Enterprise Manager for a new instance, run the EMCA command only after you have created the instance.

Also, run the command from a node in the cluster that already has Enterprise Manager configured for its associated database instance, as these configuration settings will be propagated to the new instance. Do not run this command from the node on which the new instance was created. Note that this option can be used only in a Real Application Clusters environment, so you do not need to use the -cluster option on the command line.

After running the command emca -addInst db, enter the following information for the node and database:. To deconfigure Enterprise Manager for a specific database instance typically before the database instance is deleted , use the inverse command, emca -deleteInst db. Running EMCA does not delete the database instance; it only removes the Enterprise Manager configuration so that you will no longer be able to manage the instance with Enterprise Manager. Ensure that you run the EMCA command before you delete the actual cluster database instance.

Also, ensure that you run the command from a different node and not from the node on which the database instance will be deleted. For example, by default, you access Database Control using port in 10g Release 2, as in:. Alternatively, you can explicitly assign ports after configuring Database Control using the following command:.

The following list summarizes the EMCA command-line arguments that control the standard Database Control port assignments:. For example, if you set this port to , you can then display the Database Control Console using the following URL:. The default port can be changed if the user wants to configure a specific port for Database Console.

This port is used by the Database Control Management Agent, which is monitoring and administering the database for the Database Control. The following section describes some troubleshooting tips to consider when using EMCA to configure the Database Control:.

If you change the listener port of the database after you have configured Database Control, the database status will appear as down. To reconfigure Database Control so it uses the new listener port, run the EMCA command using the -config dbcontrol db [-cluster] command-line arguments.

This is because the upgrade involves altering the instance's Oracle Home, port, or other target-associated properties. However, some of these targets on the host s will not be updated successfully during the upgrade if they are managed by a 10g Release 2 Grid Control Agent. To update these targets, in the Home page for the upgraded database or ASM target, click the "Monitoring Configuration" link.

On this page, you can update the required properties such as Oracle Home, listener port and so on to the correct values. When the database host name including the domain name or the IP address changes, deconfigure and then reconfigure the Database Console with the repository create command. Run the following command:. When the TNS configuration is changed, set the environment variable and then run the following command:.

As part of the effort to make Oracle products, services, and supporting documentation accessible and usable to the disabled community, Enterprise Manager offers several features that make management data available to users of assistive technology.

To enable these features and provide for full accessibility, you must modify two configuration settings, which are described in the following sections:. Enterprise Manager takes advantage of user interface development technologies that improve the responsiveness of some user operations. For example, when you navigate to a new record set in a table, Enterprise Manager does not redisplay the entire HTML page.

However, this performance-improving technology is generally not supported by screen readers. To disable this feature, and as a result, make the Enterprise Manager HTML pages more accessible for disabled users, use the following procedure. To locate the uix-config. Change the value of the accessibility-mode property from inaccessible to accessible. Throughout Enterprise Manager, charts are used to display performance data.

For most users, these charts provide a valuable graphical view of the data that can reveal trends and help identify minimum and maximum values for performance metrics. However, charts do not convey information in a manner that can be read by a screen reader. To remedy this problem, you can configure Enterprise Manager to provide a complete textual representation of each performance chart. By default, support for the textual representation of charts is disabled. When textual description for charts is enabled, Enterprise Manager displays a small icon for each chart that can be used as a drill-down link to the textual representation.

Figure shows an example of the icon that displays beneath Enterprise Manager charts when you have enabled the textual representation of charts. To locate the web. Open the web. Remove comments from this section by deleting the first line and the last line of this section so that the section consists of only these 4 lines:.

Restart the Management Service if you are modifying a Grid Control Console installation or restart the Database Control if you are modifying an Oracle Database 10g installation. As a result, Enterprise Manager can be reconfigured after installation so you can: Implement Enterprise Manager security and firewall features.

Maintain and troubleshoot the Enterprise Manager components as your business grows. All rights reserved. Run the following command to configure the Database Console which will automatically detect the ASM instance: emca -config dbcontrol db -repos create.

For information on the current cluster configuration, you can run: emca -displayConfig dbcontrol —cluster The above command prompts for the database unique name for the cluster database. For configuring Enterprise Manager for a new cluster instance of a database or ASM storage, use the following command: emca -addInst db On cluster databases, another common operation is the creation and deletion of database instances. After running the command emca -addInst db, enter the following information for the node and database: Node name: node2 Database Unique Name: EM Database SID: EM To deconfigure Enterprise Manager for a specific database instance typically before the database instance is deleted , use the inverse command, emca -deleteInst db.

Alternatively, you can explicitly assign ports after configuring Database Control using the following command: emca -reconfig ports [-cluster] Note: You can also use the following EMCA command-line arguments to configure Database Control after you have installed and configured Oracle Database 10g. Run the following command: emca -deconfig dbcontrol db -repos drop emca -config dbcontrol db -repos create or emca -deconfig dbcontrol db emca -config dbcontrol db -repos recreate.

To enable these features and provide for full accessibility, you must modify two configuration settings, which are described in the following sections: Enabling Enterprise Manager Accessibility Mode Providing Textual Descriptions of Enterprise Manager Charts 1.

Differences in the location of configuration files is noted where applicable. For real application cluster agent install, this directory contains sysman files.

This directory contains the log files for the Management Agent. Prints the version information associated with EMCA. Creates a new Database Control management repository. Drops the current Database Control management repository. Drops the current Database Control management repository and then recreates a new one.

Performs the operation for a cluster database or ASM instance.