Oracle Enterprise Manager Administrator's Guide Release 2.2 Part Number A85248-01 |
Library | Service | Contents | Index

# 2
Navigator

The Navigator graphically displays network objects and allows you to administer the objects. The Navigator tree displays a direct view of the network's nodes and services, the objects they contain, and the relationships among objects. The topics discussed in this chapter include:

- Navigator Pane

- Navigator Menu

- Discovering Services

- Manipulating Objects in the Navigator

- Apache Web Servers

- Paging/Email Blackout

- Removing a Node from the Navigator

- Node Removal Failure

## Navigator Pane

The Navigator pane provides:

- Identification of the objects or services on nodes in the managed environment.

- Views of the objects in a network environment and the relationships among the objects. By expanding an object, you can display any objects it contains.

- Methods of accessing and launching administration tools on the objects.

- A source of objects with which to populate groups.

- A source of objects upon which to launch DBA tools and other integrated applications.

- A source of objects for copying with the drag and drop method.

The Navigator window can be hidden or shown by selecting Show Navigator Pane in the Console View menu. You can also hide or show the pane by clicking on the Navigator icon in the Console toolbar.

### Populating the Navigator Tree

The Navigator tree is populated with objects by selecting Discover Nodes from the Navigator menu. The types of services in the network may include, but are not limited to:

- Databases

- Groups

- Listeners

- Nodes

- Web Servers

### Expanding Objects in the Navigator

Each object type in the Navigator tree is identified by an icon and name. If there is a '+' or '-' to the left of an object's icon and name, the object is a container that can be expanded to display other objects. A container that is represented by a folder icon is a logical grouping, or collection, of one specific type of object, such as databases. Other containers are objects that hold multiple types of objects. See Figure 2-1, "Navigator Menu and Window" for an illustration of a Navigator pane.

The top-most object in the Navigator tree is the network container. The network folder can contain:

- Databases folder

- Groups folder

- Listeners folder

- Nodes folder

- Folders for additional services discovered.

You can expand tree containers to view the objects and relationships in the environment. For example, you can expand a node to view the databases and listeners on the node. If you expand a database, you can access common administration areas such as schema, instance, and security. When a connection is made to a database, an icon displays on the database in the tree. See "DBA Studio" on page 6-2 for more information on integrated database administration tools that are accessible from specific Navigator objects.

#### Figure 2-1 Navigator Menu and Window

Text description of the illustration navig2.gif

### Viewing Specific Tree Objects

In large, complex environments you may not want to view the entire network system in one tree. The Navigator has been designed to be highly flexible for viewing objects. With the Split View menu option, you can split the Navigator tree into views that are displayed in separate pages in the Navigator window. Simply click on the tab of a page to move the page and its contents to the front of the Navigator window.

### Launching Tools

To launch a database tool in the context of a database or database object, select the object in the Navigator tree that you want to access. You can then execute a tool from the Tools menu or with the Related Tools option of the right-mouse menu.

You are connected to the database according to the preferred credentials that have been set up for the database. If connection to the database fails for any reason, the Database Connect Information dialog box displays. At that point, you can enter the requisite information and optionally save that information as a preferred credential. See "Preferred Credentials" on page 1-25 for information.

## Navigator Menu

The Navigator menu allows you to manage objects in the Navigator pane. The menu options are enabled according to the object selected in the Navigator tree. Usually the Create, Create Like, Edit, and Remove menu options are available when an object is selected. See Figure 2-1, "Navigator Menu and Window" for an illustration of the Navigator menu.

Clicking on an object in the Navigator with the right mouse button, displays a context-sensitive menu of all the options you can use to manipulate the object, as well as related tools.

For information on operations for an object type, see the chapter in this guide that discusses the specific application that manipulates the object type. See Chapter 7, "DBA Management Pack" for an overview of the database application tools.

Create

Allows you to create an object of a specified type.

Create Like

Allows you to create a copy of the selected object in the Navigator.

Edit

Allows you to alter or edit the object selected in the Navigator.

Remove

Allows you to delete all occurrences of the selected object in the Navigator.

If you remove a node from the Navigator tree, the node and all its services are removed from the Navigator tree.

If you remove a database, listener, or other service object from the Navigator tree the object appears again in the Navigator tree when the node that contains the service is rediscovered.

Discover Nodes

Discovers services on a node in the network. You can also display the status of network services. See "Discovering Services" on page 2-7 for more information.

Refresh All Nodes

Refreshes services for all discovered nodes.

Paging/Email Blackout

Allows a super administrator to specify paging and email blackouts for specified targets and/or services that have been previously discovered in the Navigator. Paging/email blackouts allow a super adminstrator to schedule deactivation of enhanced notification (email/paging), thus preventing Enterprise Manager administrators from being flooded with emails and pages if a managed target/service is brought down.

Ping Agent

Attempts to contact the Intelligent Agent on a specified node. If it fails, either the node is down or the Intelligent Agent isn't running. If either of these is true, no Job or Event notification will come through.

Split View

Creates a new view page in the Navigator window that contains only the currently selected object, such as a single folder, group, or user. This feature allows you to create separate views that display specific objects. For example, to create a new view that only contains the DEMO database:

1. Select the DEMO database in the tree.

2. Select the Split View menu option to create a separate view page in the Navigator pane.

3. Click on the tab of the page to move the page and its contents to the front of the Navigator pane.

Remove Split View

Removes the current split view from the Navigator. Make sure the view that you want to delete is at the front of the Navigator pane.

Find

Locates discovered databases within the Navigator Tree. It is available when you select a Database or Node icon on the tree.

Report

Allows you to generate an HTML database configuration, status, or Enterprise Manager Repository report.

Application SQL History

Displays SQL statements produced by DBA Studio. This option allows you to view the last 100 SQL statements (maximum) executed by the application you are using (i.e., DBA Studio, Schema Management, and others) against the selected database.

SQL Logging

Allows you to log SQL in a permanent status. The SQL Logging function allows you to specify the SQL logging file information and options. When you are connected to the Management Server, you can query the log. You must be logged in as super-administrator in order to enable and disable SQL Logging.

View SQL Log

Allows you to view the contents of a SQL log. All normal users can view the their own SQL logs. If you are logged in as super-administrator, you can view the SQL logs of any user. You must be logged in as super-administrator to purge a log file.

## Discovering Services

The Navigator provides service discovery functions for identifying network services and populating the Navigator tree through the Discovery Wizard.

#### Figure 2-2 Discovery Wizard

Text description of the illustration dicovery.gif

The Discovery Wizard searches the network for the nodes you specify. If that node has an Oracle Intelligent Agent running, it will be added to the Enterprise Manager Console Navigator for management along with any services running on that node. You will be able use these services as targets in jobs, events, and groups.

If there is no Oracle Intelligent Agent running, you may perform a manual configuration. This allows you to define an Oracle database on that node so that it appears in the Console Navigator. While manual configuration permits database access from the Navigator, its use is not recommended since Enterprise Manager services, such as jobs and events, will not be available.

#### Figure 2-3 Discovery Wizard: Manual Configuration

Text description of the illustration discovma.gif

When refreshing an existing node, the Discovery Wizard verifies and updates the list of services on a node that had been previously discovered. If the node was previously Manually Configured, the Discovery Wizard will check if that node now has an Oracle Intelligent Agent and if so, provide that information with the option to discover using that Intelligent Agent, or to update the previous configuration.

Note: Services on the machine where the Management Server is running are automatically discovered when you start the Console and connect to the Management Server.

#### Adding a Service

To discover new services, choose Discover Nodes from the Console Navigator menu to call up the Discovery Wizard. Any services running on that node will, if successfully discovered, appear in the Navigator. The Discovery Wizard guides you through the service discovery process. For more information on service discovery and refresh, refer to Oracle Enterprise Manager online help.

#### Refreshing a Service

Refreshing a node verifies and updates the list of services on a node that has been previously discovered. You can refresh the discovery of a node by selecting a node from the Navigator, clicking the right mouse button, and choosing Refresh Node from the context-sensitive menu.

To refresh an existing service, choose Refresh Nodes from the Console Navigator menu to call up the Refresh Wizard. The Refresh Wizard performs a "rediscovery" of any node selcted in the Console Navigator. This menu option is greyed out until a specific node is selected from the Navigator Nodes folder.

#### Removing a Service

Select a node or service from the Console Navigator. Using the right-mouse button, choose Delete from the context-sensitive menu.

### Pinging the Intelligent Agent

Pinging the Intelligent Agent on a monitored node allows you to check whether the Management Server can communicate with the Intelligent Agent on a monitored node. Proper Intelligent Agent operation is required for successful service discovery. If discovery is successful, the discovered node and services appear in the Navigator tree. If discovery has failed, an error message displays.

The following are common problems if the service discovery has failed:

- The node must have an Oracle Intelligent Agent started and running.

- TCP/IP network protocol must be used.

- If a database has not been discovered, make sure an entry for the database is in the tnsnames.ora file on the node where the Intelligent Agent is running. On a UNIX platform, check the oratab file.

- If a database has not been discovered, you may need to stop and restart the Intelligent Agent if the database was not configured or installed when the Intelligent Agent was last started. When the Intelligent Agent starts, database entries are written to the services.ora file in the ORACLE_HOME/network/agent directory (Unix example).

### Determining Node Properties

Since Enterprise Manager allows you to manage a heterogeneous environment, there will be situations where you may need to determine operational properties of that node (network name, operating system and version, and Intelligent Agent version). For example, you may want to find out which version of the Intelligent Agent is running on each node within your enterprise to determine which nodes require Intelligent Agent updates. To determine node properties:

1. Select the desired node in the Navigator.

2. Using the context-sensitive menu (right mouse button), choose Properties.

   A popup window displaying the node name, operating system and version (Intelligent Agent version 8.1.7 is required to determine operating system information), and Intelligent Agent version,

3. Click OK to dismiss the popup.

## Manipulating Objects in the Navigator

The Navigator interface provides easy manipulation of the services and objects in your managed network from the Enterprise Manager Console. From the Navigator, you can apply some or all functions available from the Console and any integrated applications to selected objects.

### Administering Objects

To administer an object, select the object in the Navigator tree and choose the administration task from the Navigator menu, or use the menu options available when you click the right mouse button on the object. The menu options available vary according to the object selected. See "Navigator Menu" on page 2-5 for more information. When you create or edit an object, the property sheet for that object displays. For information on the property sheets, see the chapter on the DBA tool that administers the object.

### Copying Navigator Objects

You can drag and drop some objects in the navigator to make copies of the object in different locations. For example, you can drag and drop a database user or role from one database to another to add that user or role to another user. However, if you drag and drop a group that resides within another group to a different group, it will move the group instead of copying it.

## Apache Web Servers

Apache web server management allows you to discover and monitor the server's operational status via the Event system. Additional functionality (extra job tasks and event tests) are available when the e-Business Management Tools (part of the Diagnostics Pack) are installed.

### Discovering Apache Web Servers

You discover a web server as you would any other managed service from the Enterprise Manager Console. See "Discovering Services" on page 2-7. The discovery process does not require the web server to be running. Once discovered, you set the server access authorization through the Enterprise Manager Preferred Credentials (Node). See "Preferred Credentials" on page 1-25.

Important: When running on UNIX, if the web server is listenting on a port number less than 1024, the administrator must have root privileges in order to submit startup or shutdown jobs to the server.

### Determining the Status of Apache Web Server

Select Edit Web Server from the context-sensitive menu to display the Edit Web Server General Page. Information displayed pertaining to the selected web server includes:

- Server Name: Server's Internet host name. Example: xyz-machine.your_company.com. If this machine does not have a registered DNS name, an IP address will appear.

- Port: The network port to which the web server listens.

- Version: Apache server version number.

- Server Root Directory: The top-level directory where all web server-related files (configuration, error, and log files) are stored.

- Configuration File Location: Location of the web server configuration file.

- Status URL: The location of the Apache-generated HTML page that provides the current server statistics in an easily readable form.

## Paging/Email Blackout

Paging/Email Blackout allows an administrator with super administrator privileges to suspend paging and email notifications for specified targets and/or services that have been previously discovered in the Navigator. Paging/email blackouts deactivate enhanced notification (email/paging), thus preventing Enterprise Manager administrators from being flooded with emails and pages if a managed target/service is brought down. For example, if a target is brought down on a regular basis for scheduled maintenance, a super administrator administrator can schedule a paging/email blackout for that target to prevent enhanced notification during the maintenance period.

### Specifying Total Paging/Email Blackout

Total paging/email blackout specifies that a blackout be started immediately with an indefinite duration. The super administrator must manually turn off Total Paging/Email before any new blackout schedules can take effect or existing blackout schedules resume. To specify a total paging/email blackout:

1. Choose Paging/Email Blackout from the Navigator menu.

2. Check Total Paging/Email Blackout.

3. Click OK.

Note: You can also access Total Paging/Email Blackout menu item from a target's context-sensitive menu in the Enterprise Manager Navigator.

### Defining a Paging/Email Blackout

To define a paging/email blackout for a specific node:

1. Select a target from the Navigator and then choose Paging/Email Blackout from the Navigator menu. Optionally, you can select an object in the Navigator and access Paging/Email Blackout through the context-sensitive menu.

2. Click Create. The requisite naming and scheduling UI are displayed. Important: Be sure that Total Paging/Email Blackout is not checked for either the specific service or its parent target.

3. Specify a Blackout Name. All Blackout names for this node/service must be unique. Note: the Target name reflects the node/service selected in the Navigator and is not editable from this dialog.

4. Select an Occurrence

   Select the frequency that you want the paging/email blackout to occur. The choices are Once, On Interval, On Day(s) of Week, and On Date(s) of Month.

   - Once--schedules the blackout only one time beginning and ending on the dates and times you choose.

   - On Interval--allows you to schedule a specific time interval between paging/email blackout periods. The interval can be a combination of hours and minutes, or number of days. Select the value you want to change and click on the scroll buttons. You can also type in a new value. Select an Effective Period in which your blackout schedule will be valid.

   - On Day(s) of Week--allows you to schedule the blackout on one or multiple days (Sunday, Monday, etc.) of the week. Click on the days of the week to select the days you want the blackout period scheduled and set a start time or duration. Select an Effective Period in which your blackout schedule will be valid.

   - On Day(s) of Month--allows you to schedule the blackout on one or multiple days (1 - 31) of the month. Click on the dates of the month to select the dates you want the blackout period scheduled and set a start time or duration. Select an Effective Period in which your blackout schedule will be valid.

5. Click OK.

Important: When selecting On Day(s) of Month or On Day(s) of Week , be aware that each day terminates at 12:00 A.M. This is important when scheduling paging/email blackout periods that span the day change (12:00 A.M.). For example, if you wish to schedule a blackout that begins on Tuesday at 10:00 P.M and lasts for six hours, you must define two blackout periods: Tuesday from 10:00 P.M. to 11:59 P.M. Wednesday from 12:00 A.M. to 4:00 A.M.

### Making a Copy of an Existing Blackout Schedule

To schedule a paging/email blackout schedule for a node that is identical to that of another managed node:

1. Choose Paging/Email Blackout from the Navigator menu. Optionally, you can select an object in the Navigator and access Paging/Email Blackout through the context-sensitive menu.

2. Select a Blackout Schedule entry from the Blackout Name list.

3. Click Create Like. A new entry is created in the list prefixed by "Copy of."

4. Modify the blackout period parameters (such as Blackout Name) as desired and click OK.

### Turning Blackout Schedules On and Off

Once you have defined one or more paging/email blackout periods for a node/service, they persist in the Blackout Name list associated with the node/service until deleted. You can turn paging/email blackout on or off by checking the box located to the left of the individual blackout name. You can edit the Occurrence parameters to reflect the present date and time. Paging/email blackouts are set ON by default.

### Deleting Paging/Email Blackout Periods

1. Choose Paging/Email Blackout from the Navigator menu. Optionally, you can select an object in the Navigator and access Paging/Email Blackout through the context-sensitive menu.

2. Select the desired Blackout Name.

3. Click Delete.

### Viewing Blackout Periods

Once you have defined blackout periods on multiple nodes, you can view them by selecting the desired target in the Console Navigator and choosing Paging/Email Blackout from the Navigator menu. If you select a high-level folder from the Navigator, such as Databases, Groups, or Nodes, rather that an individual target, all blackout periods defined in the container type are displayed.

## Removing a Node from the Navigator

Before removing a discovered node from the Enterprise Manager Navigator, you must remove all jobs and events submitted against that node. If the Intelligent Agent is down when you attempt to remove the node, and jobs and events have not been cleared previously, Enterprise Manager will allow you to remove the node. However, when the Intelligent Agent is restarted and the node re-discovered, the Intelligent Agent will be out of sync with the Oracle Management Server. The following example illustrates how this situation can occur.

1. You register an event with the Intelligent Agent on a managed node.

2. The Intelligent Agent goes down.

3. You remove the node from the Navigator without removing the event.

4. The Intelligent Agent is started and the node is rediscovered.

5. The Console Event window is clear.

6. You attempt to register the same event with the managed node.

7. Enterprise Manager displays a message stating the event is already registered even though it is not.

The Intelligent Agent remembers the current status of jobs and events through a series of generated files. Oracle Intelligent Agents 8.0.6 (Oracle 8.0) and higher and Intelligent Agents 8.1.6 (Oracle 8.1) and higher automatically synchronize with the Oracle Management Server by removing old Intelligent Agent overhead files. For older versions of the Intelligent Agent, you must remove these files manually.

To manually remove the Intelligent Agent overhead files:

1. Stop the Intelligent Agent (if it is currently running).

2. Go to the Intelligent Agent directory ($ORACLE_HOME/network/agent or $ORACLE_HOME/net80/agent (Windows NT))

3. Delete files with the following extensions: .q, .jou, .inp

4. Restart the Intelligent Agent.

## Node Removal Failure

Typically, node removal from the Navigator fails because of problems encountered by the Management Server. The following are the most probable causes.

- The Management Server encountered an error condition while accessing the repository. Check the Management Server log for detailed error messages. (ORACLE_HOME/sysman/log/oms.log). If problem resolution is not obvious from the error messages, contact Oracle Support.

- The Management Server could not open a database session to the repository. Ensure that the repository is up and running. You may have to shut down other Enterprise Manager applications that may be connected to the repository. Check the Management Server log for more detailed error messages.

- Different DNS servers may resolve node names in different ways. For example, if a Management Server is running on a machine whose DNS server resolves a particular node as "A", the Management Server discovers the node as "A". Next, the Management Server is run on another machine whose DNS server resolves the same node as "B". If you switch back to running the Management Server on the first machine (originally resolved the node as "A"), attempting to remove the node from the Console Navigator will now fail since the repository entries will be out of sync.

The solution is to run the Management Server on the machine from which you last discovered the node. In the example above, you would need to run the Management Server on the second machine (resolved the node as "B") and then remove the node from the Navigator. Always ensure that the DNS setup is consistent for all nodes where the Management Server is run.

| Copyright © 1996-2000, Oracle Corporation. All Rights Reserved. |
Library | Service | Contents | Index