|Oracle Enterprise Manager Configuration Guide
Part Number A96673-01
Beginning with Release 9.0 when you start the Enterprise Manager Console or various other Enterprise Manager applications, you are prompted to choose between starting the product standalone (i.e. not connecting to the middle tier Management Server) or starting the product with a Management Server connection. While starting the Console standalone allows a single administrator to perform direct database administration, starting the Console by connecting to a middle tier Management Server provides more comprehensive management capabilities, such as sharing of administrative data among multiple administrators, being proactively notified of potential problems, and automating repetitive administrative tasks. This chapter will describe how to configure the Enterprise Manager Console when it is connected to a middle tier Management Server.
The following topics will be discussed:
When you start the Enterprise Manager Console, you are prompted to choose between starting the product standalone or starting it with a Management Server connection.
Previous to starting the Console by logging into a Management Server you must first install and configure a Management Server. For installation instructions, refer to the Installation Guide. For configuration details, refer to Chapter 3, "Configuring and Controlling the Management Server".
Choose to start the Console by logging into a Management Server when you want access to functionality such as:
On Windows-based platforms, you start the Console from the Windows Start Menu.
On any supported platform, you can start the Console from the command line by using the command:
On UNIX platforms, the
oemapp part of the command line is case-sensitive and must be entered with lowercase characters.
All of the above options prompt you with the Oracle Enterprise Manager Console Login. If you want to bypass the Oracle Enterprise Manager Console Login, you can enter the following command at the command line to automatically login to the Console by connecting to a Management Server:
When the Oracle Enterprise Manager Console Login appears, select the Login to the Management Server option and if this is the first time you have logged in to the Management Server, enter the default credentials (Enterprise Manager administrator name and password) and the Management Server machine name. The default Enterprise Manager administrator name is
sysman and its password is
oem_temp. The Management Server on the node you select or enter must be one which is already configured with the repository you want to access.
The repository you use with a Management Server should not be confused with the standalone repository used with certain standalone, integrated applications.
If the name of the node where the Management Server is running does not appear in the list, you can either enter the node name in the field or follow these instructions:
If you add a Management Server using the Management Server dialog it becomes the current choice when you return to the login dialog.
Oracle Enterprise Manager may resolve the node name and use the canonical name of the machine. That name will be used in the dialogs from now on. For example,
After the initial login with
sysman/oem_temp, a security dialog appears where you can change the default
sysman password. The password you specify is not case sensitive. Other than spaces at the beginning or at the end of the password, you can specify any character in an Enterprise Manager Administrator's password.
Oracle Enterprise Manager provides a Discovery Wizard for identifying network nodes and machines and populating the Console Navigator with these discovered nodes and targets. The discovered targets, such as databases and listeners, can then be administered with Enterprise Manager.
The Console is the central location for management and therefore the window from which you would see all the targets you are managing.
During start up of the Console, any manageable targets on the machine where the Management Server is running are automatically discovered if the Intelligent Agent is installed and running on that Management Server machine. The Console Navigator then displays all those discovered targets.
To discover additional nodes and targets which reside on nodes within your environment:
If nodes have failed automatic discovery, you can click Next on the Progress page. On the Errors page, you will have the option to retry, skip, or perform a manual discovery on the failed nodes.
If no Intelligent Agent is running for some nodes which failed to be discovered, you can still add the node to the navigator, and add databases to that node using manual discovery.
During manual discovery, you will be prompted for the following information:
When a node is manually added, you cannot register events or submit jobs against the node.
Manually discovered nodes must be dropped from the Navigator before they can be automatically discovered.
If a node cannot be discovered, check if the node is down or if the node does not have an Intelligent Agent running. You can also check if you are using the TCP/IP network protocol. See the Oracle Enterprise Manager Administrator's Guide for more information on discovering nodes.
If you discover two or more targets with the exact same name, regardless of the target type, only one of the discovered targets will appear in the Navigator.
Enterprise Manager is a multi-administrator system: every person who is administering systems using Enterprise Manager has his or her own administrator account which he or she uses to log into the Console by connecting to a Management Server.
The installation of Enterprise Manager creates a Reports user and a Super Administrator named sysman. The Super Administrator
sysman can create administrators using the Manage Administrators item in the Configuration menu. In addition to an administrator name and password, each account can be tagged as a Super Administrator account or an account to which the administrator has access to only jobs and/or events.
Differences between the two types of accounts are as follows:
Most Super Administrators also have a separate account for daily operations but use their Super Administrator account for special operations only available to Super Administrators, such as creating new Enterprise Manager Administrators, configuring paging or e-mail servers, defining management regions, or granting other administrators access to targets. Using the
sysman account for daily administration work is not recommended. The Super Administrator account is similar to root on UNIX or Administrator on Windows NT and is a user which cannot be deleted or renamed. It is a user that can perform any task and therefore should be used only for setting up the environment.
Typically, all administrators share a single Enterprise Manager repository, which allows administrators to share information. The Enterprise Manager repository is one in which Management Servers share; it is not a standalone repository. Although you can set up multiple repositories, administrators using different repositories will not have access to each other's information; there is no sharing of data between repositories. Administrative data stored in the repository is filtered based on administrator permissions.
Preferred Credentials must be set up for each administrator account. When an administrator connects to managed targets through the Management Server, the preferred credentials used are those defined explicitly for that administrator.
See the Oracle Enterprise Manager Administrator's Guide for information on how Enterprise Manager administrators are created, edited, and deleted with the Manage Administrators option of the Console Configuration menu.
Beginning with Oracle 8.0.6 databases and higher, the OEM_MONITOR role is created by the Oracle database creation scripts. This role permits access to database functionality within Enterprise Manager, such as registering events against a database or browsing through the objects in a database via the Console Navigator. These types of functionality require database credentials on which to perform these operations. Rather than granting the powerful DBA role to the database credentials, many administrators prefer to provide only the necessary privileges required to do these operations. Granting the OEM_MONITOR role to the database credentials, ensures that the user has the minimum sufficient privileges required for these operations.
You must perform the following steps:
You are now ready to grant the OEM_MONITOR role to the database user that will be used as "database preferred credentials" in Enterprise Manager. In addition to granting the OEM_MONITOR role to a user, you must also ensure that the QUOTA for the user account is set to UNLIMITED.
The Continued Row event test needs to analyze results into a table so it needs both the "analyze any" and "create table" privileges.
In order for Enterprise Manager administrators to be able to successfully submit jobs, certain configuration steps must be performed:
ORACLE_HOME\NETWORKdirectory as well as read, write, update, and delete permissions to the
TEMPdirectory or the
If you do not set up the "logon as batch job" privilege, you will receive the "Failed to authenticate user" message when you try to run jobs on the node.
You must create a Windows platform user account for every managed Windows platform node which will have jobs submitted against it. Follow one of the three procedures listed below.
In addition, because the output of some jobs may be quite large, you have the option in Oracle Enterprise Manager to specify the maximum size for any job output. For details, see the Oracle Enterprise Manager Administrator's Guide.
To create a new Windows NT user account on the Windows NT machine where the Intelligent Agent is installed and grant the "log in as batch jobs" privilege to this user, perform the procedure below.
Alternately, to assign privileges to an existing local user account, perform the following steps.
The Windows NT Domain User works only if the machine is a primary domain controller (PDC); otherwise, jobs will fail with VNI-2015 "authentication error." In all non-PDC environments the account must be local to the machine.
If you have both a local and a domain user with the same name, the local user takes precedence. If you have a domain user set up, you must set the domain password to be the same as the local password in order for scheduled jobs to run when they are submitted using the domain user account.
To enable administrators to receive e-mail notifications, super administrators must first configure the e-mail server from the Console:
After completing the SMTP mail configuration, notification and schedule preferences should be specified for all administrators who want to receive e-mail notifications. See the Oracle Enterprise Manager Administrator's Guide for details.
Enterprise Manager bundles its own Paging Server which enables administrators to receive notifications on events and jobs on their pagers. Both numeric and alphanumeric pagers are supported; however, alphanumeric pagers must utilize one of the following paging service protocols:
Most paging service providers support the sending of e-mail messages to pagers. If your provider offers the option of sending e-mail; then, you can choose not to install and configure the Enterprise Manager Paging Server.
If you choose not to install our Paging Server, you can specify the e-mail address of your pager as the Receiver's Email address when you configure your e-mail notification preferences (Figure 4-4, "Email Preferences") or your paging notification preferences (Figure 4-5, "Paging Preferences").
If you specify paging via email using the paging preferences, it will be based on your pager notification's schedule and filters. In Enterprise Manager, you can distinguish the e-mail notification's schedule and filters from the pager notification's schedule and filters. Refer to Figure 4-6, "Email and Paging Filters" and Figure 4-7, "Paging Schedule" below.
Administrators can specify an email address or several email addresses separated by a comma for email notifications as well as either a phone number or an email address for paging notifications. This allows administrators to specify different schedules, filters, and message formatting for both methods of notification. See the Oracle Enterprise Manager Administrator's Guide for details.
The Enterprise Manager Paging Server is automatically installed with the Oracle Management Server on Windows NT, Windows 2000, or Windows XP; it is not installable for any UNIX platform.
The Enterprise Manager Paging Server requires a modem. Ensure that the machine on which you install the Paging Server has a modem.
While you can install the Paging Server only on certain Windows platforms, you can configure the Paging Server from the Enterprise Manager Console on any Windows or UNIX operating system.
Only one Paging Server is necessary for an Enterprise Manager deployment.
There are two most common options for deploying the Paging Server.
In the deployment shown in Figure 4-9, "Management Server on Windows NT Machine", the Console is on one machine, and the Management Server is on another Windows NT machine (connecting to repository). The Paging Server and modem are on the same Windows NT machine as the Management Server.
In the deployment shown Figure 4-10, "Management Server on UNIX Machine",
the Console is on one machine and Management Server is on another UNIX machine (connecting to the repository). The Paging Server and modem are on a Windows NT machine.
The installation of the Enterprise Manager Paging Server does not automatically start the Paging Server service nor does it configure it. After installation, you must specify the modem settings, start the Paging Server service manually, and configure the Paging Server from the Enterprise Manager Console.
To specify the modem settings:
A baud rate higher than 9600 may result in the loss of data with the paging service carrier. The baud rate of 9600 for your modem is only a recommendation. You must find the baud rate setting which is optimal for your system.
To start the Paging Server:
You can also start the paging server by typing the following at a command prompt
To enable administrators to receive paging notifications via the Enterprise Manager Paging Server, super administrators must first configure the Paging Server from the Console.
To add a paging server to the Enterprise Manager Console, perform the following operations:
If the Console is unable to find the paging server with the given hostname, an error appears.
If the paging server is found, a new paging server object is added under the Paging Configuration object in the list. The new paging server will have no paging carrier. You must add at least one paging carrier in order for paging to function.
Paging carrier name. Field accepts alphanumeric characters and underscores.
Type of paging carrier. Enterprise Manager supports alphanumeric or numeric.
TAP, FLEX-TD, or GSM. Protocol selection is only available if the carrier type is Alphanumeric.
After completing paging server configuration, notification and schedule preferences should be specified for all administrators who want to receive page notifications. See the Oracle Enterprise Manager Administrator's Guide for details.
The Enterprise Manager reporting system provides flexible reporting functionality to administrators, permitting quick and easy access to information about the status of all monitored systems in their enterprise. Administrators can create, schedule, and publish a wide variety of enterprise system reports. When published to a web site, these reports can be accessed by a wider audience, enabling anyone from administrators to managers to executives to quickly access information regarding their monitored enterprise.
In order to access published reports, ensure that the Enterprise Manager Web Site component has been installed. By default, it is installed with the Management Server under the
Oracle_Home/oem_webstage directory. In addition, the Enterprise Manager Web Site automatically installs a preconfigured Oracle HTTP Server to act as the reporting web server. This is the same HTTP Server that is used by default for the browser-based Enterprise Manager.
In order to view published reports, follow the steps documented in the sections below.
You must change the default password (
oem_temp) for the REPORTS_USER administrator. The REPORTS_USER administrator owns predefined reports.
To change the password:
The oemctl configure rws script is a command-line utility that must be run on the machine where the Management Server and reporting web server are installed.
To run the configuration utility:
You must change the
oem_temp password prior to running this script; otherwise the oemctl configure rws script will generate an error message when you run it if the REPORTS_USER password is left as the default.
In 9.2, you can put your collections in either the Oracle Management Server repository or a separate repository. If you are storing the collections in a separate database, you will have to provide the username, password, and alias for that other database.
Shut down and start up the Oracle HTTP Server after running the
oemctl configure rws command.
Note: Choosing View Published Reports from any Console menu or even accessing the Reporting web site itself directly before running oemctl configure rws will generate an error message indicating that you need to first configure the Reporting web site.
If you have installed the Oracle HTTP Server that is packaged with Enterprise Manager by default, start it by performing the following steps:
On Windows NT:
To start the Oracle HTTP Server:
You can start the Oracle HTTP Server from the command line using the command:
To stop the Oracle HTTP Server, perform the following steps:
On Windows NT:
To stop the Oracle HTTP Server:
You can stop the Oracle HTTP Server from the command line using the command:
You must have the correct TCP/IP configuration; incorrect TCP/IP configurations result in timeouts and lost connections.
Dynamic IP addresses attributed by DHCP are not supported on nodes running the Management Server or an Intelligent Agent. DHCP is supported only on Enterprise Manager clients.
When the Console connects over a dialup line, the Console machine obtains a dynamic IP address. This dynamic IP address needs to be sent by the operating system (Windows 2000, Windows NT, Windows 98) to the Enterprise Manager application.
In order for the operating system to return the correct IP address, the network communication protocol (TCP-IP) needs to be configured to obtain the IP address using the Dynamic Host Configuration Protocol (DHCP).
To specify the setting:
You must make note of your previous settings in order to return to those settings when you connect the same machine to the network via ethernet. Copy the Settings specified in IP Address, Subnet Mask and Default Gateway to a file.
If you are not running from a web browser, you may need to restart your system after making the changes.
You can set the preferred color by adding this line to the $ORACLE_HOME/sysman/config/ClientConfig.properties file:
The value can be any valid color scheme. Currently available color schemes are blue, khaki, olive, purple, red, teal, titanium, or System. The values are not case sensitive.
System are the currently known values for this property. Setting the user.color.scheme property will change the color scheme in the Console with the basic color as the named color in the property. System is the only one that takes the system default properties.
If the color scheme you are trying to use does not seem to take effect, turn on client tracing using the
oemapp trace console command. Use level two tracing. In the trace output, search for "Color Scheme." The information is at the top of the trace output. If an incorrect value is entered, the following will appear in the trace file:
You can restrict access to certain areas of database management in Oracle Enterprise Manager 9i so that the database management information will not appear in the navigator.
Because manual editing is error prone, backing up the
For example, a DBA whose role is only to create new users will only need access to Security Management. He will not need access to Schema Management, Instance Management, Storage Management, and others.
Restricting access applies to database management. You cannot customize access with this procedure for Events, Jobs, Groups, and others.
To restrict database management access:
OEMClient.propertiesfile in the client's
OEMClient.propertiesfile so that you can back out of the procedure should an error occur.
The area of management will no longer appear in the navigator under the database or databases that are managed.