Oracle Enterprise Manager Installation Guide

Library

Product

Contents

Index

Console Configuration

Starting Oracle Enterprise Manager
Discovering Network Services
Starting Enterprise Manager Tools

This chapter discusses getting started with Oracle Enterprise Manager and configuring the Console when running under Microsoft Windows NT or 95.

Starting Oracle Enterprise Manager

To start the Enterprise Manager Console, select Oracle Enterprise Manager from the Oracle Enterprise Manager folder on the Start Menu to start Enterprise Manager (VOC.EXE).

Note:
Only one instance of the Oracle Enterprise Manager Console can be run on a machine. However, you can run multiple instances of the DBA tools.

Repository User Account

You need to have a user account with DBA (Database Administrator) privileges set up on the database where the repository is created. Oracle Enterprise Manager places its repository in the default tablespace of the user account where you are connected when the repository is created. Because of this, Oracle recommends that you create a new user account so that the repository is created in its own tablespace. In addition, as described in the Optimal Flexible Architecture (OFA) Standard, there are several benefits for separating segments into special purpose tablespaces. For this reason, it is recommended that you create a new tablespace and the newly-created user is customized to use this tablespace as its default tablespace.

Because Oracle Enterprise Manager does not explicitly specify the size of the tables and indexes it creates, these objects are created using the default storage parameters for the tablespace in which they are to be stored. As a result, if the tablespace runs out of space before all of the schema objects are created, an error occurs. In this case, you need to either decrease the INITIAL extent size of the user's default tablespace or increase the overall tablespace size by adding another datafile.

Use the following suggested steps before you create the Oracle Enterprise Manager repository:

From the Oracle Enterprise Manager program group, double-click on the SQL Worksheet icon.

2.

Use the Login Information dialog box to connect to an existing account on the database with system (DBA) privileges.

3.

Create a special tablespace for the Oracle Enterprise Manager repository.

      CREATE TABLESPACE reposit_tablespace DATAFILE 'datafile' size;

4.

Create a user account where the user's default tablespace is the newly-created tablespace and the user's temporary tablespace is a tablespace dedicated to temporary segments.

CREATE USER username IDENTIFIED BY password
       DEFAULT TABLESPACE reposit_tablespace
      TEMPORARY TABLESPACE temp_tablespace;

5.

Grant the SYSTEM privileges to this user account.

      GRANT DBA to username IDENTIFIED BY password;

6.

Disconnect from the administrator account.

      DISCONNECT;

7.

Exit SQL Worksheet.

Automatic Repository Creation

Oracle Enterprise Manager automatically creates the necessary repository tables when you log into a database upon startup of the Enterprise Manager Console or Performance Pack product. After you are logged into the database, select OK when the dialog displays. The process takes a few minutes to complete. If you experience problems with the automatic create process, see Manually Creating, Dropping, or Upgrading the Repository on page C-3.

If you have an existing repository from a previous release of Enterprise Manager, see Console and Repository Compatibility on page 3-3.

Using a Local NT Database

If you are using a local Oracle NT database on your PC to store the repository, perform the following steps:

1.: Double-click the Services icon in the Control Panel folder to verify that the OracleService is started.
2.: If the service is not started, click the Start pushbutton to start up the local NT Oracle database.

Console and Repository Compatibility

If an existing Enterprise Manager repository version is older than the Oracle Enterprise Manager Console version, the existing repository is automatically upgraded when you log into the repository. If you experience problems with the automatic upgrade process, see Manually Creating, Dropping, or Upgrading the Repository on page C-3.

If the Oracle Enterprise Manager Console version is older than the Enterprise Manager repository version, install a more recent, compatible version of Enterprise Manager.

Connecting to a Repository

When you start Enterprise Manager, the copyright window displays, then the Login Information dialog box appears. Use the login box to connect to the user account in the Oracle database where your Enterprise Manager repository is stored.

Oracle Enterprise Manager requires unique usernames across all repositories whether or not the repositories are in different databases. Identical users cause problems with agent notifications. The Intelligent Agents use the unique username when tracking jobs and events. The username is associated with the Console location when creating a return address for notifications.

Discovering Network Services

The Oracle Enterprise Manager Console must discover network services, such as databases, listeners, and nodes, to populate the Navigator tree, in order to manage these services for the Job Scheduling and Event Management systems. There are two methods of discovering services:

Discovery with the Navigator Discovery feature using release 7.3.3 of Intelligent Agent
Discovery with the topology.ora file

Discovering with Intelligent Agent 7.3.3

The Intelligent Agent 7.3.3 release supports the Navigator Discovery feature to populate the Navigator tree and identify the network services that the Oracle Enterprise Manager administers. The Discovery feature works only with nodes that have the Intelligent Agent release 7.3.3 or later. This agent is able to automatically discover the services, such as listeners and databases, on the node where it is running.

After the 7.3.3 Intelligent Agent is installed and running, you use the Console Navigator Discovery feature to discover the node where it is located. For information on the Navigator Discovery menu options, see the online help for the Navigator Discovery.

For more information on the Intelligent Agent, see Chapter 2, Agent Configuration.

If you had a previous version of Enterprise Manager and are now only using 7.3.3 Intelligent Agents, you should remove all of the services in the Navigator tree and delete the topology.ora file that was used by the previous release, then use the Navigator Discovery feature.

For nodes that do not have the 7.3.3 agent installed or cannot be discovered due to non-TCP network configurations, you can continue to use a topology.ora file, in addition to the Discovery feature. The entries in the topology.ora file are also used to populate the Navigator tree.

Navigator Discovery

The 7.3.3 release of the Intelligent Agent also supports the Navigator Discovery feature for locating services in the network and passing them to the Enterprise Manager Console. The 7.3.3 Intelligent Agent automatically locates the services on the node where it resides.

After the 7.3.3 Intelligent Agent is running, use the Enterprise Manager Console Navigator Discovery feature to discover the node where the 7.3.3 agent is located. When requested through the Navigator Discovery menu option, the agent passes information from the services.ora file to the Enterprise Manager Console to populate the Navigator tree.

Discovering with topology.ora

For releases of the Intelligent Agent previous to 7.3.3, Oracle Enterprise Manager requires a configuration file, topology.ora, in addition to standard SQL*Net configuration files to discover and manage network services. The topology.ora file is used in conjunction with the tnsnames.ora file to locate services in your network. The addresses of services listed in those files must match. The topology.ora file can be set up with following methods:

For your convenience, the Oracle Topology Generator has been provided with Oracle Enterprise Manager to allow you to configure the topology.ora file from an existing tnsnames.ora file. The Topology Generator can be accessed during the installation or executed separately. For information on using the Topology Generator, see Network Topology Generator on page A-12.
If SQL*Net version 2.3 has been installed and configured with the SQL*Net configuration tool Network Manager 3.1, the file has already been configured for your system. When you use Network Manager 3.1, an Enterprise Manager agent object must be selected to create the necessary agent entries in network configuration files.

Starting Enterprise Manager Tools

You can launch an Enterprise Manager database administration tool in the following ways:

Administration Toolbar

: Click on the tool's icon in the toolbar. The tool connects to default database for the toolbar. For information on connecting to other databases, see the online help for the Administration Toolbar.

2.

Independent application

: Double-click on the application icon in the Enterprise Manager program group. Enter the connect information in the Login Information dialog box.

3.

Console

: Through the Console, you can use one of the following methods:

Select the database you want to administer in the Navigator tree or in the Map window, then choose the application in the Console Tools menu or in the launch palette.
Select the database you want to administer in the Navigator tree, then choose the application from the Related Tools menu of the context-sensitive menu.
Choose the application in the Console Tools menu or in the launch palette, then enter connect information in the Login Information dialog box.

Note:
Some database administration tools do not run or have limited functionality when the Console is not running.

When a tool executes, it attempts to connect to an Oracle database. For information on connecting to an Oracle database, see the online help.

When you select a database in the Console before launching a tool, you are connected to the database according to the preferred credentials that have been set up for the database or the credentials you used to log on to the Console. If connection to the database fails for any reason, the Login Information dialog box displays.

Oracle Daemon Manager

The communication daemon is started automatically with the Oracle Enterprise Manager Console and usually does not need any special configuration. If you need to view or set the parameters for the communication daemon, use the Oracle Daemon Manager.

For example, if you start Oracle Enterprise Manager and a message displays informing you that the communication daemon cannot listen on the assigned port, run the Daemon Manager to change the port number. To change the port setting, perform the following steps:

1.: Start the Daemon Manager from the Oracle Enterprise Manager program group.
2.: Select Configuration Parameters in the left window. The parameters and values display in the right window. For information on setting the parameters, press F1 to access the online help.
3.: Double-click on the TCP/IP Port parameter in the multi-column list on the right side of the screen.
4.: Enter a valid port number.
5.: Click the Set button. The change takes effect the next time Oracle Enterprise Manager is run.
6.: Select Exit from the File menu to exit Daemon Manager.

Administration of a Remote Unix Database

Before submitting an administration task, such as database shutdown or startup, through the Oracle Enterprise Manager Job system, you need to set up the database password file on the Unix node where the database and agent are located. Set up the password file with the password file creation utility, orapwd. Enter the following line at the Unix operating system prompt:

orapwd file=$ORACLE_HOME/dbs/orapw$ORACLE_SID password=manager

Add the following line to the init.ora database initialization file:

REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE

Note:
When you log in to Oracle Enterprise Manager, connect with the SYSDBA (or SYSOPER) role to have the privileges to start up and shut down databases.

Additional Information:
Refer to the Operating system-specific documentation for your Oracle database for the exact name of the password file creation utility for your system.

Prev Next

Library

Product

Contents

Index