1 Getting Started with Enterprise Manager Grid Control

After the installation, Enterprise Manager Grid Control (Grid Control) is automatically started. You can immediately log in to Grid Control with the SYSMAN account and begin using Enterprise Manager.

This chapter describes Enterprise Manager's ready-to-use configuration, recommends the tasks to be performed after installation to begin customizing it for your particular environment, and contains information on how to configure the Management Agent and the Oracle Management Service (OMS). The following topics are covered in this chapter:

• Enterprise Manager's Ready-To-Use Configuration

• Using the Enterprise Manager Grid Control Console for the First Time

• Controlling the Management Repository, Service, and Agent

Enterprise Manager's Ready-To-Use Configuration

At install time, the following tasks are automatically performed, with no user interaction required:

• The default super administrator SYSMAN account is created with the password you specified.

• The SYSMAN account is automatically configured to receive e-mail notifications if you provided the e-mail notification settings at installation time.

• E-mail notifications are set up with default Notification Rules for the critical conditions.

• Supported targets located on the same host machine as the Management Agent are automatically discovered.

Default Super Administrator: SYSMAN

A default super administrator account, SYSMAN, is created with the password you specified during the installation. After installation, you can immediately log in to the Grid Control Console with this user name and password to perform management tasks. The SYSMAN account owns the database schema containing the Management Repository.

See Also:

Setting Up Enterprise Manager for Your Environment chapter of Oracle Enterprise Manager Concepts to learn more about the SYSMAN user account

E-mail Notifications

The SYSMAN account is automatically configured to receive e-mail notifications from Enterprise Manager if, during installation, you specified the Outgoing (SMTP) Mail Server and SYSMAN e-mail address. Also, as part of the self-monitoring feature, a script is created that enables the user to be notified by e-mail in the event that Enterprise Manager stops unexpectedly.

Note:

If you do not specify the mail server, there will be no notification. If you specify the mail server, but not the e-mail address, the system is set up to send e-mail notifications, but the SYSMAN account does not receive any notifications. If you did not specify the information during installation, you can set up e-mail notification afterwards using Enterprise Manager Grid Control.

Notification Rules

E-mail notifications are set up with default Notification Rules for the critical conditions that could occur for all supported target types. For example, for the database target type, a rule is created such that e-mail notifications are sent when any database becomes unavailable, or if any of its key performance metrics (Datafile Usage percentage, Archiver Hung Error Stack, Tablespace Space Used%, and others) becomes critical. The e-mail notifications are sent to the e-mail address associated with the SYSMAN account. These rules are public; when other administrators are created, they can subscribe to them later.

See Also:

For more information on the notification rules, in Enterprise Manager, click Preferences, then Rules. Click Help on that page.

Automatic Discovery

The first time the Management Agent is started, most supported targets that are located on the same host machine as the Management Agent are automatically discovered, and default monitoring levels and data collections are automatically enabled.

All targets, such as Oracle Collaboration Suite targets, Web applications, clusters, and Beacons are discovered automatically during the installation phase itself. But, you must manually discover the targets that have been installed after the Management Agent installation.

Caution:

If you are performing an Oracle RAC agent installation on Microsoft Windows, only the host and cluster targets are discovered (automatically) during the installation phase. To discover all other targets, you must execute the following command on each node:

<AGENT_HOME>/bin/agentca -d

See Also:

• To view a list of certified targets for Grid Control, see Operating System, Browser, Target Certification.

• Managing Oracle Collaboration Suite available on Oracle Technology Network, for instructions on discovering Oracle Collaboration Suite targets

• Adding Targets to Be Monitored and Administered by Enterprise Manager in the Oracle Enterprise Manager online Help for information on manual discovery

Troubleshooting Issues Concerning Target Discovery

If you are unable to discover targets on a Management Agent host, check for the following problems.

When the Management Agent is installed, an automatic discovery is performed to detect any existing Oracle9i Application Server release 9.0.2 or 9.0.3 instances. If the 9.0.2 or 9.0.3 Oracle9iAS instances were installed by a different OS user than the user that installs the Management Agent, then the file protections on targets.xml file within that Oracle9i Application Server installation may prevent the Management Agent from reading the file. This prevents the discovery of that Oracle9i Application Server instance.

To confirm that this is the problem, check the Management Agent logs located at AGENT_HOME/sysman/log/ for permission denied errors, where AGENT_HOME is the Oracle home for the Management Agent. To correct the problem, set the file permissions so that it can be read by the user who installed the Management Agent.

This problem does not occur when discovering other existing Oracle Application Server versions on a machine.

See Also:

Configuring Database and ASM Targets for Monitoring for more information, if you encounter problems monitoring Oracle Database 10g or ASM targets

Using the Enterprise Manager Grid Control Console for the First Time

Enterprise Manager Grid Control provides a Web-based console for managing your entire enterprise.

The first column describes actions that you may want to perform; the second contains considerations and reasons for performing the action; the third helps you navigate to the appropriate online Help page in Enterprise Manager.

All Help topics are contained within the Setting Up Enterprise Manager directory of the online Help.

Enabling or Disabling the Licensed Function

Before you begin using Enterprise Manager Grid Control, you must first set the access levels according to your licensing agreement with Oracle. To do this, perform the following steps using a super administrator account, such as SYSMAN.

1. After you log in using SYSMAN, in the Grid Control console, click Setup, then Management Pack Access.

2. Select Grant Access or Remove Access for each pack, according to the terms of your licensing agreement.

3. Click Apply to save your changes. Once access is removed, the function associated with the selected pack is no longer available for any targets managed by Enterprise Manager Grid Control.

Controlling the Management Repository, Service, and Agent

The OMS and the Grid Control console are automatically started after the Enterprise Manager installation. This section provides information on how to manipulate the Management Agent and OMS after installation.

See Also:

• Understanding the Directory Structure section of Oracle Enterprise Manager Advanced Configuration for information on Enterprise Manager's directory structure

• Oracle Enterprise Manager Advanced Configuration for information on configuring Enterprise Manager components, such as Management Agents and Beacons for use in a firewall environment

Starting the Management Repository Database

If you need to start the Management Repository database, use SQL*Plus to connect to Oracle as SYSDBA, and then issue the STARTUP command.

Caution:

During a restart of a machine, the repository database startup script runs automatically only if you have performed the Enterprise Manager installation using a new database.

For all other Enterprise Manager installation types, you will have to manually start the repository database on reboot.

See Also:

• Maintaining and Troubleshooting the Enterprise Repository chapter of Oracle Enterprise Manager Advanced Configuration for instructions on managing the repository database, such as how to drop the repository schema

• Starting Up and Shutting Down chapter in the Oracle Database Administrator's Guide for detailed instructions on starting up a database

Starting and Stopping the OMS

The relevant emctl commands are listed in Table 1-0.

You must be in the OMS_HOME/bin directory to issue the emctl commands, where OMS_HOME is the Oracle Application Server home directory in which the OMS is installed and deployed.

Note:

To execute the opmnctl commands, you must be in the OMS_HOME/opmn/bin directory.

Table 1-1 Commands to Start and Stop OMS

If you want to	Enter the following command
Start the OMS	emctl start oms
Stop the OMS	emctl stop oms
Verify status of the OMS	emctl status oms
Verify status of all OPMN processes	opmnctl status
Start all components of Oracle Application Server, including OMS and Web Cache	opmnctl startall
Stop all components of Oracle Application Server, including OMS and Web Cache	opmnctl stopall

Note:

Use the same emctl commands on Microsoft Windows as well, to perform the above-mentioned actions. Optionally, you can use emctl.bat and opmnctl.bat on Microsoft Windows, though the extension is not mandatory.

Caution:

During a reboot of a machine, the OMS startup script runs automatically to start the OMS only if you have performed the Enterprise Manager installation using a new database. In this case, you do not have to manually start the OMS.

For all other Enterprise Manager installation types, you will have to manually start the OMS on reboot.

See Also:

Starting and Stopping Enterprise Manager Components section of the Introduction to Enterprise Manager Advanced Configuration chapter of Oracle Enterprise Manager Advanced Configuration at

http://otn.oracle.com/documentation/oem.html

Starting and Stopping the Management Agent

The relevant emctl commands for UNIX are listed in Table 1-0.

You must be in the <AGENT_HOME>/bin directory to issue the emctl commands, where AGENT_HOME is the Oracle home directory for your Management Agent. Note that this directory is different than the <AS_HOME>/bin directory, which is for the Oracle Application Server Control Agent.

Table 1-2 Commands to Start and Stop Management Agent

If you want to	Enter the following command
Start the Management Agent	emctl start agent
Stop the Management Agent	emctl stop agent
Verify status of the Management Agent	emctl status agent

Note:

On Microsoft Windows, the services are started automatically by the operating system.

Caution:

During a restart of a machine, the agent startup script runs automatically to start the Management Agent only if you have performed the Enterprise Manager installation using a new database, or have installed only the Management Agent.

For all other Enterprise Manager installation types, you will have to manually start the agent when you restart the machine.

See Also:

Starting and Stopping Enterprise Manager Components section of the Introduction to Enterprise Manager Advanced Configuration chapter of Oracle Enterprise Manager Advanced Configuration at:

http://otn.oracle.com/documentation/oem.html

Starting Oracle Application Server Console

Oracle Application Server Control console is the Web-based management tool for Oracle Application Server and is used to monitor the Enterprise Manager targets.

After successful Enterprise Manager installation, you must manually start the Application Server console before starting the Enterprise Manager console.

To start the Application Server console, go to the OMS Oracle home and execute the start iasconsole command. The usage is as follows:

<OMS_HOME>/bin/emctl start iasconsole

Accessing Oracle Application Server Console from Enterprise Manager Grid Control Console

To access the Oracle Application Server console from the Enterprise Manager Grid Control console, follow these steps:

1. Log in to Enterprise Manager Grid Control.

2. Click Targets and then All Targets.

3. From the Search list, select Oracle Application Server, and click Go.

4. From the results table, click the name of the Oracle Application Server that was installed with Enterprise Manager Grid Control to view its home page.

5. On the Oracle Application Server Home page, from the Related Links section, click Administer to access the Application Server console.

Note:

To secure the OMS, run the following command from the Oracle home directory of the OMS:

<Oracle_Home>/bin/emctl secure oms

The above-mentioned command secures only OMS but does not secure the Oracle Application Server that was installed with Enterprise Manager Grid Control. This is an expected behaviour, and it is not required to secure the Oracle Application Server that was installed with Enterprise Manager Grid Control.

However, if you have a standalone Oracle Application Server and if you want to secure that, then run the following command:

emctl secure em

Accessing Enterprise Manager Grid Control

To log in to the Grid Control console, use the following URL:

http://<oms_hostname>.<domain>:<port>/em

or

https://<oms_hostname>.<domain>:<port>/em

If you are uncertain about the port number, you can refer to one of the following files:

• ORACLE_HOME/install/setupinfo.txt as displayed by Oracle Universal Installer at the end of the installation

• ORACLE_HOME/install/portlist.ini on the OMS machine

• <OMS Home>/sysman/config/emoms.properties

  Here, check the properties oracle.sysman.emSDK.svlt.ConsoleServerPort and oracle.sysman.emSDK.svlt.ConsoleServerHTTPSPort for unsecure and secure ports respectively.

When the login dialog box appears, enter the user name and password for the super administrator SYSMAN.

Note:

To secure the OMS, run the following command from the Oracle home directory of the OMS:

<Oracle_Home>/bin/emctl secure oms

The above-mentioned command secures only OMS but does not secure the Oracle Application Server that was installed with Enterprise Manager Grid Control. This is an expected behaviour, and it is not required to secure the Oracle Application Server that was installed with Enterprise Manager Grid Control.

However, if you have a standalone Oracle Application Server and if you want to secure that, then run the following command:

emctl secure em

See Also:

• Enterprise Manager Security chapter of Oracle Enterprise Manager Advanced Configuration for more information on Grid Control security

• Viewing a Summary of the Ports Assigned During the Application Server Installation section of the Configuring Firewalls chapter of Oracle Enterprise Manager Advanced Configuration for more information on port settings

• Viewing and Modifying Application Server Port Assignments in the Enterprise Manager online Help.

Unlock the DBSNMP User Account

To unlock the DBSNMP user account:

1. From the Grid Control console, navigate to the Database Home page and click Administration to display the list of administration functions.

2. Under Users and Privileges, click Users to display the list of all user accounts. If you are prompted to log in to the database, make sure to use a database user account with DBA privileges such as SYSTEM.

3. Find and select the DBSNMP user account, select Unlock User from the Actions menu, and click Go to confirm your choice.

4. Set the DBSNMP password as described in the Set Monitoring Credentials section. Once the password is set, monitoring can begin.

Set Monitoring Credentials

You must reset the monitoring credentials for database and ASM targets if the passwords you specified during installation were different from the defaults that Enterprise Manager expects. If you change a password at any time, make sure to update all components using that password as well.

This section contains the following subsections:

• Setting Monitoring Credentials for Database Targets

• Setting Monitoring Credentials for ASM Targets

Setting Monitoring Credentials for Database Targets

To set the monitoring credentials for a single-instance or cluster Oracle Database 10g target:

1. From the Grid Control console, navigate to the Configure Database: Properties page:

   1. On the Targets tab, click Databases to display the list of database targets.

   2. Find and select the database target and click Monitoring Configuration.

   Enterprise Manager displays the Configure Database: Properties page.

2. Enter the correct password for the DBSNMP user in the Monitor Password field and click Test Connection to verify the monitoring credentials.

3. If the connection is successful, click Next, then click Submit.

You should now be able to view the complete Database Home page for the Oracle Database 10g target. For more information, see Specifying New Target Monitoring Credentials in Oracle Enterprise Manager Advanced Configuration.

Setting Monitoring Credentials for ASM Targets

Note:

You must ensure the DBSNMP password that is required to monitor database targets is correctly set, before proceeding to set the monitoring credentials for the Automatic Storage Management targets.

To set the monitoring credentials for an ASM target:

1. From the Grid Control console, click All Targets on the Targets tab to display a list of all managed targets.

2. Find and select the ASM target that you want to modify.

3. Click Configure to display the ASM Monitoring Configuration page.

4. Enter the ASM SYS password in the Password field and click OK.

You should now be able to view the complete home page for the ASM target without any Management Agent or collection errors. For more information, see Specifying New Target Monitoring Credentials in Oracle Enterprise Manager Advanced Configuration.

Privileges Required for Accessing the Database Performance Tab

The following privileges are required for accessing the Performance tab of a database target:

• create session

• select_catalog_role

• select any dictionary

If you do not have these privileges, you may see an error while accessing the Performance tab.