Preface

The Oracle Enterprise Manager Configuration Guide explains how to configure Oracle^® Enterprise Manager Release 9.0.2.

Oracle Enterprise Manager is a system management tool which provides an integrated solution for managing your heterogeneous environment. The product combines a graphical console, agents, common services, and tools to provide an integrated, comprehensive systems management platform for managing Oracle products.

After you have completed the configuration procedures, refer to the Oracle Enterprise Manager online help or the Oracle Enterprise Manager Administrator's Guide for information on how to use Oracle Enterprise Manager.

For program updates and important notes on using Oracle Enterprise Manager, refer to the Oracle Enterprise Manager Readme.

Intended Audience

This guide is written for DBAs and system administrators who want to configure Oracle Enterprise Manager. You should already be familiar with Oracle and the administrative tasks you want to perform.

For general information about the Oracle9i and how it works, refer to Oracle9i Database Concepts. For information about database administration procedures, refer to the Oracle9i documentation set. The Oracle9i documentation set contains specific and thorough descriptions of the database administration tasks you can perform with Oracle Enterprise Manager tools. In addition, the Oracle9i documentation set provides recommendations on how to administer your database optimally.

You should also be familiar with the operation of your specific Microsoft Windows or Unix system. Refer to the documentation for your Windows or Unix system, if necessary.

Structure

This manual contains the following chapters and appendices:

Chapter 1, "Introduction"

This chapter provides an overview of the Oracle Enterprise Manager configuration. The introduction contains topics on Oracle Enterprise Manager architecture, deployment strategies, certification, and system and hardware requirements.

Chapter 2, "Standalone"

This chapter will describe requirements for running the Console standalone.

Chapter 3, "Configuring and Controlling the Management Server"

This chapter contains additional configuration tasks that you must perform on the middle tier Management Server machine(s) if you have chosen to deploy the entire Enterprise Manager framework (for example, Console, Management Server, and Intelligent Agents).

Chapter 4, "Configuring the Console when Connected to a Management Server"

This chapter will describe how to configure the Enterprise Manager Console when it is connected to a middle tier Management Server.

Chapter 5, "Running Enterprise Manager Console from a Web Browser"

This chapter contains information on the additional tasks you need to perform to run Enterprise Manager through a web browser.

Chapter 6, "Using the Oracle Enterprise Manager Web Site"

This chapter contains information about using the Enterprise Manager Web Site to manage the Application Server.

Chapter 7, "Tuning the Oracle Management Server"

This chapter contains information about tuning the Oracle Management Server.

Appendix A, "Directory Structure"

This appendix describes the directory structure of Oracle Enterprise Manager Release 9i.

Appendix B, "Activating Logging and Tracing"

This appendix contains information about specifying parameters for logging and tracing for Enterprise Manager.

Appendix C, "General Repository Guidelines"

This appendix provides guidelines for determining storage requirements and disk space allocation for your Oracle Enterprise Manager repository.

Appendix D, "Globalization Support"

This appendix lists the languages into which Enterprise Manager has been translated.

Appendix E, "Using Enterprise Manager on Windows 2000"

This appendix contains the difference between using Enterprise Manager on Windows NT and Windows 2000.

Appendix F, "Troubleshooting"

This appendix contains information about possible troubleshooting issues.

Appendix G, "Keyboard Navigation"

This appendix contains non-standard keys.

Documentation Set

The Oracle Enterprise Manager Release 9i documentation includes the following:

• The Oracle Enterprise Manager Readme Release 9i provides important notes on updates to the software and other late-breaking news, as well as any differences between the product's behavior and how it is documented.

• The Oracle Enterprise Manager Configuration Guide Release 9i provides information about configuring the Oracle Enterprise Manager system.

• The Oracle Enterprise Manager Concepts Guide Release 9i provides an overview of the Enterprise Manager system.

• The Oracle Enterprise Manager Administrator's Guide Release 9i describes the components and features of the Oracle Enterprise Manager system.

• The Oracle Intelligent Agent User's Guide describes how to administer the Oracle Intelligent Agent.

• The Oracle Enterprise Manager Messages Manual Release 9i contains probable causes and recommended actions for Oracle Enterprise Manager errors.

In addition to the Oracle Enterprise Manager documentation set, extensive on-line help is provided for components in Oracle Enterprise Manager.

To download free release notes or installation documentation, please visit the Oracle Documentation Center at http://docs.oracle.com/

Printed documentation is available for sale in the Oracle Store at http://oraclestore.oracle.com/

Related Documents

For more information, see the following resources:

• Oracle9i Database Concepts

• Oracle9i Database Administrator's Guide

• SQL*Plus User's Guide and Reference

• Oracle9i Database Error Messages

• Oracle9i Application Server Concepts

• Oracle9i Application Server Administrator's Guide

• Oracle9i Application Server Installation Guide

In North America, printed documentation is available for sale in the Oracle Store at

http://oraclestore.oracle.com/

Note: This installation guide and other platform-specific documentation are not available for purchase in printed format.

Customers in Europe, the Middle East, and Africa (EMEA) can purchase documentation from

http://www.oraclebookshop.com/

Other customers can contact their Oracle representative to purchase printed documentation.

To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at

http://otn.oracle.com/admin/account/membership.html

If you already have a username and password for OTN, then you can go directly to the documentation section of the OTN Web site at

http://otn.oracle.com/docs/index.htm

To access the database documentation search engine directly, please visit

http://tahiti.oracle.com/

Conventions

This section describes the conventions used in the text and code examples of this documentation set. It describes:

• Conventions in Text

• Conventions in Code Examples

• Conventions for Microsoft Windows Operating Systems

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.

Convention	Meaning	Example
Bold	Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both.	When you specify this clause, you create an index-organized table.
Italics	Italic typeface indicates book titles or emphasis.	Oracle9i Database Concepts Ensure that the recovery catalog and target database do not reside on the same disk.
UPPERCASE monospace (fixed-width font)	Uppercase monospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, usernames, and roles.	You can specify this clause only for a NUMBER column. You can back up the database by using the BACKUP command. Query the TABLE_NAME column in the USER_TABLES data dictionary view. Use the DBMS_STATS.GENERATE_STATS procedure.
lowercase monospace (fixed-width font)	Lowercase monospace typeface indicates executables, filenames, directory names, and sample user-supplied elements. Such elements include computer and database names, net service names, and connect identifiers, as well as user-supplied database objects and structures, column names, packages and classes, usernames and roles, program units, and parameter values. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.	Enter sqlplus to open SQL*Plus. The password is specified in the orapwd file. Back up the datafiles and control files in the /disk1/oracle/dbs directory. The department_id, department_name, and location_id columns are in the hr.departments table. Set the QUERY_REWRITE_ENABLED initialization parameter to true. Connect as oe user. The JRepUtil class implements these methods.
lowercase monospace (fixed-width font) italic	Lowercase monospace italic font represents placeholders or variables.	You can specify the parallel_clause. Run Uold_release.SQL where old_release refers to the release you installed prior to upgrading.

Conventions in Code Examples

Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace (fixed-width) font and separated from normal text as shown in this example:

SELECT username FROM dba_users WHERE username = 'MIGRATE';

The following table describes typographic conventions used in code examples and provides examples of their use.

Convention	Meaning	Example
[ ]	Brackets enclose one or more optional items. Do not enter the brackets.	DECIMAL (digits [ , precision ])
{ }	Braces enclose two or more items, one of which is required. Do not enter the braces.	{ENABLE | DISABLE}
|	A vertical bar represents a choice of two or more options within brackets or braces. Enter one of the options. Do not enter the vertical bar.	{ENABLE | DISABLE} [COMPRESS | NOCOMPRESS]
...	Horizontal ellipsis points indicate either: That we have omitted parts of the code that are not directly related to the example That you can repeat a portion of the code	CREATE TABLE ... AS subquery; SELECT col1, col2, ... , coln FROM employees;
. . .	Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example.
Other notation	You must enter symbols other than brackets, braces, vertical bars, and ellipsis points as shown.	acctbal NUMBER(11,2); acct CONSTANT NUMBER(4) := 3;
Italics	Italicized text indicates placeholders or variables for which you must supply particular values.	CONNECT SYSTEM/system_password DB_NAME = database_name
UPPERCASE	Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to distinguish them from terms you define. Unless terms appear in brackets, enter them in the order and with the spelling shown. However, because these terms are not case sensitive, you can enter them in lowercase.	SELECT last_name, employee_id FROM employees; SELECT * FROM USER_TABLES; DROP TABLE hr.employees;
lowercase	Lowercase typeface indicates programmatic elements that you supply. For example, lowercase indicates names of tables, columns, or files. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.	SELECT last_name, employee_id FROM employees; sqlplus hr/hr CREATE USER mjones IDENTIFIED BY ty3MU9;

Conventions for Microsoft Windows Operating Systems

The following table describes conventions for Microsoft Windows operating systems and provides examples of their use.

Convention	Meaning	Example
Choose Start >	How to start a program.	To start the Oracle Database Configuration Assistant, choose Start > Programs > Oracle - HOME_NAME > Configuration and Migration Tools > Database Configuration Assistant.
File and directory names	File and directory names are not case sensitive. The following special characters are not allowed: left angle bracket (<), right angle bracket (>), colon (:), double quotation marks ("), slash (/), pipe (|), and dash (-). The special character backslash (\) is treated as an element separator, even when it appears in quotes. If the file name begins with \\, then Windows assumes it uses the Universal Naming Convention.	c:\winnt"\"system32 is the same as C:\WINNT\SYSTEM32
C:\>	Represents the Windows command prompt of the current hard disk drive. The escape character in a command prompt is the caret (^). Your prompt reflects the subdirectory in which you are working. Referred to as the command prompt in this manual.	C:\oracle\oradata>
	The backslash (\) special character is sometimes required as an escape character for the double quotation mark (") special character at the Windows command prompt. Parentheses and the single quotation mark (') do not require an escape character. Refer to your Windows operating system documentation for more information on escape and special characters.	C:\>exp scott/tiger TABLES=emp QUERY=\"WHERE job='SALESMAN' and sal<1600\" C:\>imp SYSTEM/password FROMUSER=scott TABLES=(emp, dept)
HOME_NAME	Represents the Oracle home name. The home name can be up to 16 alphanumeric characters. The only special character allowed in the home name is the underscore.	C:\> net start OracleHOME_NAMETNSListener
ORACLE_HOME and ORACLE_BASE	In releases prior to Oracle8i release 8.1.3, when you installed Oracle components, all subdirectories were located under a top level ORACLE_HOME directory that by default used one of the following names: C:\orant for Windows NT C:\orawin95 for Windows 95 C:\orawin98 for Windows 98 This release complies with Optimal Flexible Architecture (OFA) guidelines. All subdirectories are not under a top level ORACLE_HOME directory. There is a top level directory called ORACLE_BASE that by default is C:\oracle. If you install Oracle9i release 1 (9.0.1) on a computer with no other Oracle software installed, then the default setting for the first Oracle home directory is C:\oracle\ora90. The Oracle home directory is located directly under ORACLE_BASE. All directory path examples in this guide follow OFA conventions. Refer to Oracle9i Database Getting Starting for Windows for additional information about OFA compliances and for information about installing Oracle products in non-OFA compliant directories.	Go to the ORACLE_BASE\ORACLE_HOME\rdbms\admin directory.

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle Corporation is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at

http://www.oracle.com/accessibility/

Accessibility of Code Examples in Documentation

JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle Corporation does not own or control. Oracle Corporation neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Support for Hearing and Speech Impaired Customers

Oracle Corporation provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week.

For technical questions, call:

1.800.446.2398

For non-technical questions, call:

1.800.464.2330

Component Accessibility

Java Access Bridge Setup for Oracle9i for Windows

This section contains setup information to enable Oracle9i components to use a screen reader. The following procedures are needed only if you use a screen reader.

Java Access Bridge enables assistive technologies, such as a JAWS screen reader, to read Java applications running on Windows. Assistive technologies can read Oracle9i components, such as Oracle Universal Installer, Oracle Enterprise Manager, and Oracle Database Configuration Assistant.

See Also: After installation, Java Access Bridge documentation located in: \AccessBridge-1_0\doc

This section contains these topics:

• Setup for Oracle Universal Installer

• Setup for Oracle Installed Components

Setup for Oracle Universal Installer

Install and configure Java Access Bridge for Windows before installing Oracle9i components to enable assistive technologies to read Oracle Universal Installer windows.

Before you Begin

Exit any assistive technology software that is running.

To install the Java Access Bridge:

1. From the first component CD-ROM, copy \AccessBridge\accessbridge1_0.zip to a location on your hard drive.

2. Extract the files onto your hard drive.

3. Add access-bridge.jar and jaccess-1_1.jar to the CLASSPATH user environment variable.

4. Open the Windows System Control Panel. For Windows NT or Windows 2000, choose Start > Settings > Control Panel > System.

   On Windows NT, select the Environment tab. On Windows 2000, select the Advance tab. Then, choose the Environment Variables button.

5. Add the following to the CLASSPATH user environment variable:

   ;x:\AccessBridge-1_0\installer\installerFiles\access-bridge.jar; x:\AccessBridge\installer\installerFiles\jaccess-1_1.jar

   where x:\AccessBridge-1_0 is the full path of the Access Bridge location on your hard drive.

6. Copy JavaAccessBridge.dll and WindowsAccessBridge.dll from x:\AccessBridge-1_0\installer\installerFiles\ to operating system\system32\.

Setup for Oracle Installed Components

Install and configure Java Access Bridge for Windows after installing Oracle9i components to enable assistive technologies to read Oracle9i component windows.

Perform the following steps to install and configure Java Access Bridge:

• Step 1: Install Java Access Bridge Software

• Step 2: Configure Oracle to use Java Access Bridge

Step 1: Install Java Access Bridge Software

To install the Java Access Bridge:

1. From the first component CD-ROM, copy \AccessBridge\accessbridge1_0.zip to a location on your hard drive.

2. Extract the files onto your hard drive.

3. Java Access Bridge must be installed into the subdirectory of Java Runtime Environment (JRE) 1.1.8 used by Oracle. By default, JRE 1.1.8 used by Oracle is installed in:

   C:\Program Files\Oracle\jre\1.1.8.

   The following table list the files to copy from the Java Access Bridge location on your hard drive to the appropriate subdirectory of the JRE used by Oracle.

Copy...	To...
\AccessBridge-1_0\installer\installerFiles\jaccess-1_1.jar	\lib\jaccess.jar (rename jaccess-1_1.jar to jaccess.jar)
\AccessBridge-1_0\access-bridge.jar	\lib\
\AccessBridge-1_0\JavaAccessBridge.dll	\bin\
\AccessBridge-1_0\WindowsAccessBridge.dll	\bin\

4. In the destination folder, rename jaccess-1_1.jar to jaccess.jar.

5. Use a text editor to modify \lib\awt.properties that is located in the subdirectory of JRE 1.1.8 used by Oracle.

6. Add the following lines to awt.properties:

   AWT.EventQueueClass=com.cun.java.accessibility.util.EventQueueMonitor

   AWT.assistive_technologies=com.sun.java.accessibility.AccessBridge

Step 2: Configure Oracle to use Java Access Bridge

To configure Oracle to use Java Access Bridge, set the system environment variable ORACLE_OEM_CLASSPATH to point to the installed Java Access Bridge files.

Open the Windows System Control Panel. For Windows NT or Windows 2000, choose Start > Settings > Control Panel > System.

• On Windows NT:
  1. Select the Environment tab.

  2. Select a variable in the System Variables list.

  3. In the Variable field, enter ORACLE_OEM_CLASSPATH.

  4. In the Value field, enter the full path of jaccess.jar and access-bridge.jar. For example, if JRE 1.1.8 is installed in the default location, then these paths are:

     c:\Program Files\Oracle\jre\1.1.8\lib\jaccess.jar;c:\Program Files\Oracle\jre\1.1.8\lib\access-bridge.jar

  5. Choose Set.

  6. Choose OK.

• On Windows 2000:
  1. Select the Advanced tab.

  2. Choose the Environment Variables button.

     The Environment Variables dialog displays.

  3. Choose the New button under the System Variable list.

     The New System Variable dialog displays.

  4. In the Variable Name field, enter ORACLE_OEM_CLASSPATH.

  5. In the Variable Value field, enter the full path of jaccess.jar and access-bridge.jar. For example, if JRE 1.1.8 is installed in the default location, then these paths are:

     c:\Program Files\Oracle\jre\1.1.8\lib\jaccess.jar;c:\Program Files\Oracle\jre\1.1.8\lib\access-bridge.jar

  6. Click OK to close the New System Variable dialog

  7. Click OK to close the Environment Variables dialog

  8. Click OK to close the System Properties control panel