Untitled

=========================================

Oracle Enterprise Manager

Production Version 1.5.0

Readme/Release Note A57697-01

=========================================

Table of Contents

1. Introduction

1.1 Purpose of this Document

1.2 New Features

1.3 Restricted Rights Legend

2. Tips & Techniques

2.1 Improved Concurrency by Increasing Virtual Memory

2.2 Using DBA and SQL Scripts

2.3 Applying an Action to Multiple Databases

2.4 Viewing charts in Oracle Performance Manager

2.5 No data available for Oracle Performance Manager chart

2.6 Command Line Connect String Syntax

2.7 Installing Oracle Enterprise Manager with a local database

3. Compatibility Issues

3.1 Oracle Database Compatibility Matrix

3.2 Console and Repository Compatibility

3.3 Warning About Cancelling During Pepository Creation

4. Console-Related Known Problems / Caveats

4.1 Console Problems / Caveats

5. Database & Other Application Problems / Caveats

5.1 Generic Problems

5.2 Backup Problems

5.3 Data Manager Problems

5.4 Software Manager Problems

6. Oracle Expert

6.1 Known Problems

6.2 Precautions

7. Oracle Trace

7.1 Caveats

8. Tablespace Manager

8.1 Caveats

8.2 Known Problems

9. Oracle Advanced Events

9.1 Known Problems

10. Other Oracle Performance Pack Caveats

10.1 Known Problems

11. Oracle Enterprise Manager Documentation

11.1 Online Books

1. Introduction

1.1 Purpose of this Document

This document notes differences between the delivered Oracle Enterprise Manager 1.5.0 product and its documented functionality. It also includes information on the Enterprise Manager documentation, and late-breaking information concerning this production release.

1.2 New Features

1.2.1 The paging feature in Oracle Enterprise Manager release 1.5.0 supports GSM (European standard) and TAP (US Standard). Also, paging now supports numeric pagers.

1.2.2 Schema Manager with release 1.5.0 supports Oracle8 objects.

1.3. Restricted Rights Legend

This software contains propriety information of Oracle Corporation; it is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of software is prohibited.

If this software/documentation is delivered to a U.S. Government Agency of the Department of Defense, then it is delivered with Restricted Rights and the following legend is applicable:

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure of the Programs by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, Rights in Technical Data and Computer Software (October 1988).

Oracle Corporation, 500 Oracle Parkway, Redwood Shores, CA 94065.

If this software/documentation is delivered to a U.S. Government Agency not within the Department of Defense, then it is delivered with "Restricted Rights," as defined in FAR 52.227-14, Rights in Data - General, including Alternate III (June 1987).

Product components labelled or bannered as "Beta" or "Pre-Production" releases are provided to the customer with the understanding that they are beta versions and should be used accordingly.

The information in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free.

Oracle's Advanced Networking Option can be used with Oracle Enterprise Manager version 1.5.0 for the sole purpose of managing Oracle products free of charge.

ORACLE, ORACLE7, ORACLE8, Oracle Enterprise Manager, SQL*Plus, SQLDBA, and Server Manager are registered trademarks of Oracle Corporation. All other product or company names are used for identification purposes only, and may be trademarks of their respective owners.

2. Tips & Techniques

2.1 Improved Concurrency by Increasing Virtual Memory

On MS Windows NT, you can significantly improve the ability to have the console and a number of launched applications running concurrently.

In the Control Panel, select the 'System' program item and click on the Virtual Memory option. Then, select the Change button and specify on which disk you wish to place the paging file. Generally speaking, the larger you can make this file, the better.

2.2 Using SQL, DBA and TCL Scripts

The job system allows the submission of SQL, DBA and TCL scripts. These scripts are selected by picking the name from a drop-down list. The list is populated by listing *.sql files in the following directories:

SQL Scripts: %ORACLE_HOME%\SYSMAN\SCRIPTS\SQL

DBA Scripts: %ORACLE_HOME%\SYSMAN\SCRIPTS\DBA

TCL Scripts: %ORACLE_HOME%\SYSMAN\SCRIPTS\TCL

If you have a set of scripts that you wish to run on a regular basis, copy them into the appropriate directory.

NOTE: DBA Scripts *must* specify the user and password within the script. This means that the first line of the script should connect to the required user, for example:

CONNECT SYSTEM/MANAGER;

2.3 Applying an action to Multiple Databases

The model used for applying actions to multiple databases is "Model and Record". This means that if you wish to apply a set of actions to a number of databases, record the actions on a single database and then send the recorded actions to all the other databases.

By using the Record/Stop/Pause menu items, a script can be generated. This script should be placed in the SQL directory (see 2.2) thus allowing the job system to locate it.

2.4 Viewing charts in Oracle Performance Manager

If a chart shows up empty when running the Oracle Performance Manager application, it is probably because the window is too small, or because there are too many charts in a window. Try resizing the window, or removing charts from the window.

2.5 No data available for Oracle Performance Manager chart

If a "No data available" message box appears when trying to display a window, it is probably because one or more charts in the window had queries which did not return any data. To see if this is indeed the case, try executing the respective query or queries in the Define Chart dialog.

2.6 Command Line Connect String Syntax

When launching the console or an application from the command line, you can connect to a database using the connect string "user=<myname> password=<mypasswd> service=<mydb>".

2.7 Installing Oracle Enterprise Manager with a local database

Do not install Oracle Enterprise Manager release 1.5.0 into the same <Oracle_Home> where you have a v8.0.3 database installed, or where any product dependent upon Required Support Files v8.0.3 is installed.

3. Compatibility Issues

3.1 Oracle Console-Intelligent Agent-Database Compatibility Matrices

The Intelligent Agent is compatible with the database with which it is released and prior databases releases. For circumstances where a newer release of the Intelligent Agent is used to manage an older release of the database, the Agent must be installed in an ORACLE_HOME current with the Agent release. Older releases of the Intelligent Agent are not compatible with newer releases of the database.

The following matrix lists the releases of Oracle Enterprise Manager and the releases of Intelligent Agents with which they are certified. If a release is certified with a particular agent, then a "yes" is placed for that entry. If an Agent is not certified for a specific release, then the entry is a "no".

AGENT

C o n s o l e 7.3.4 8.0.3 8.0.4

-----------------------------------------------------------------

EM v1.3.6 yes no no

EM v1.4.x yes yes no

EM v1.5.0 yes yes yes

-----------------------------------------------------------------

The following matrix lists the components of Oracle Enterprise Manager Release 1.5.0 and their compatibilities with specific releases of the Oracle Server. If a component is certified to run with a specific server release, then a "yes" is placed for that entry. If a component is not certified to run with a specific release, then the entry is a "no". Special circumstances are noted.

ORACLE SERVER

F e a t u r e 7.2 7.3 8.0.4

--------------------------------------------------------------------

Repository

Local no yes yes

Remote yes yes yes

Service Discovery* yes yes yes

Job Control System* yes yes yes

Event Management System* yes yes yes

Database Applications

Backup Manager* yes yes yes

Instance Manager yes yes yes

Schema Manager yes yes yes

Security Manager yes yes yes

Storage Manager yes yes yes

SQL Worksheet yes yes yes

Software Manager* no no/Note 1 yes

Utility Applications

Data Manager / Export* no yes yes

Data Manager / Import* no yes yes

Data Manager / Load* no yes yes

Performance Pack

Expert yes yes yes

Lock Manager yes yes yes

Oracle Events* Note 2 yes yes

Performance Manager yes yes yes

Tablespace Manager* no yes yes

Top Sessions yes yes yes

Trace* no Note 3 yes

--------------------------------------------------------------------

* All or some functionality of these components is not available without an agent.

Note 1: OSM functionality has been certified with agents

version 8.x only

Note 2: Not available for Oracle 7 Server 7.2 for NT.

Note 3: Can support 7.3.3 with upgraded Trace job files, see Readme Section 7.1.3.

3.2 Console and Repository Compatibility

The versions of the Oracle Enterprise Manager and the Enterprise Manager repository must be compatible. For example, you cannot use a version 1.3 repository with a version 1.5 Enterprise Manager Console.

If the existing Enterprise Manager repository version is older than the Oracle Enterprise Manager Console version, the existing repository is automatically upgraded the first time you log into the repository. A dialog box displays that informs you of the upgrade.

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

4. Console-Related Known Problems / Caveats

4.1 Console Problems / Caveats

4.1.1 Console usernames must be unique across all Repositories.

4.1.2 The use of TNS_ADMIN is not supported for agent discovery on Windows NT nodes.

4.1.3 If you receive the error message "Some events do not have their values

specified." when you click the OK button from the "Create Event Set" Property Sheet, cancel out of the Property Sheet, recreate the Event Set and click the Apply button before the OK button.

4.1.4 Listener jobs and events will not work properly if the name of the node on which the listener is running has an underscore in it. (Bug 586883)

4.1.5 Partitions, Advanced Queues and Objects are missing in the Navigator Tree. ( Bug 506273 )

4.1.6 Event script fail messages from agent are shown as event warnings in the console. ( Bug 502620 )

4.1.7 The Event Set description text is limited to approximately 60-80 characters. ( Bug 499310 )

4.1.8 When entering service information into the Manually Define Services Wizard, the database name needs to match what is defined in the visible services parameter in snmp.ora ( Bug 505110 )

4.1.9 Each event must use a unique fixit job on each destination where it is

registered. Also, when a single agent is monitoring multiple databases on a destination, create a unique event and fixit job for each database.

4.1.10 If the 'Run OS Command' Job Task is executing an operating system command that requires interaction, it hangs with the status of "started". To avoid this, redirect input and/or suppress operating system confirmations and requests.

4.1.11 When logging into an OEM repository that is already used by another Console if you would like to exit select "OK", not "Cancel" (bug 600157)

4.1.12 If you are unable to launch the Quick Tour from the Oracle Enterprise Manager release 1.5.0 console make sure you are using Microsoft Internet Explorer or Netscape Navigator v4.0 or later. Alternatively you may launch the Quick Tour from Microsoft Explorer: double-click on the file: em.htm in <oracle_home>/sysman/qtour/voc/us/ (Bug 600290, 597149, 590708)

5. Database and Other Applications - Problems / Caveats

5.1 Generic Problems

5.1.1 After installing Discoverer 2000 3.0.8 - on top of Oracle Enterprise Manager - the application may crash and a Dr. Watson message may appear. (Bug 568628). A workaround to this problem is to manually copy mmdus32.dll, mmdx32.ocx and mmtx32.ocx from the Oracle Enterprise Manager CD (or Oracle DB CD) into the oracle_home\bin directory. This overwrites the files which Discoverer installed which are causing the problem. Discoverer continues to work after these files have been copied. An alternative is to deinstall and reinstall Oracle Enterprise Manager.

5.2 Backup Problems

5.2.1 Container Filtering is not implemented within the Oracle Backup Manager.

5.2.2 Backup to tape is not supported for databases on Windows NT when using the OS backup.

5.2.3 A target database version 8.0.3 and version 8.0.4 can not share the same recovery catalog.

5.2.4 A target EBU database must have a 7.3.4 (or later) agent to register the target with the EBU catalog. If the agent is 7.3.3 or earlier the register job fails with the error: invalid command name "NETWORK"

5.3 Data Manager Problems

5.3.1 Running an export job against a 7.3.x db on Unix fails with ora-942 exp-8, if using a 8.0.x Intelligent Agent. Running an export job against 8.0.x works. The problem occurs because the export utility uses the Oracle8 oracle home where the agent is running. On NT the problem does not occur because of the naming of the utility exp72.exe, exp73.exe etc.

5.4 Software Manager Problems

5.4.1 Generic Problems/Limitations:

Packages and Releases names cannot be longer than 10 characters.

Deinstallation of multiple products can be done in multiple tasks, one product per task or, the products to be deinstalled all need to be highlighted by holding down the "shift" key and selecting them. (bug 566356)

If two packages with the same name are created by two different OSM console users only the first one created will be recognized. Use of unique package names is recommended.

If a package created and distributed to multiple hosts is later on deleted from any of the hosts it exists on, the package on the original host becomes invalid. Workaround is to use a remaining valid package. (bug 601672)

5.4.2 NT Problems/Limitations:

Install of a 16-bit Package requires NT Service Pack 2 to be installed on the target node.

Note: Although distributing 16-bit packages remains a functionality of OSM, it is no longer supported (i.e. no future testing/fixes/enhancements will be made).

Staging areas from which releases are created must be on the remote node's local volume or CD drive (a limitation of how the agent privileges work on Windows NT).

5.4.3 Oracle File Packager Limitations

A stage created by Oracle File Packager must contain the Oracle Installer in order to be distributed/installed via OSM. In this case you can create first a stage that has only the latest version of the Installer (ex: if your stage is "stg", copy the "installer" directory from the CD and the nt.prd file to "stg"; edit nt.prd to remove all lines except the first two starting with "ntinstver" and "ntinstall) then when staging with OFP use "stg" as your staging directory. (bug 601054)

6. Oracle Expert

6.1 Known Problems

6.1.1 Any workload request containing SQL that utilizes a dblink to attach to a database is not validated against the database referenced by the dblink.

6.1.2 The Cancel process does not work when importing workload from an .XDL file.

6.1.3 Source lines greater than 1024 bytes in import files may cause a syntax error.

6.1.4 Oracle Expert expects the following tables to exist in the target database being tuned in order to perform collection. If any of these tables do not exist during collection, errors may result.

dba_tab_columns dba_constraints dba_users

dba_data_files dba_objects dba_indexes

dba_segments dba_ind_columns dba_tables

dba_rollback_segs dba_sequences dba_views

dba_tablespaces dba_synonyms dba_ts_quotas

dba_clusters

6.1.8 If structure tuning is performed on a database with a very large number of users (greater than 1000), the resulting Analysis report is very large and it may not be possible to load it into conventional editors, like Notepad.

6.1.9 If a SQL statement is greater than 8K bytes, an error occurs when attempting to edit the Request that contains the statement. The error reads "Error while attempting to load attribute for display". The Request property sheet is still displayed, but the SQL text is not visible.

6.1.10 In order to use the Oracle Expert "Autotune" feature, you must first select a database from the Oracle Expert Navigator window. Once started, Autotune will continue to run until the Autotune menu - Stop function is invoked for the selected database or the system is rebooted.

6.1.11 If you stop an Oracle Expert "Autotune" session, then attempt to restart it, you may receive a notice that username/password is invalid. If so, select "retry" and re-enter the username/password.

6.2 Precautions

6.2.1 It is currently possible to run more than one Oracle Expert session against the same repository. Oracle Expert does not have integral support for avoiding data conflicts between sessions. Do not run more than one session against the repository at any one time. However, if this is required, each PC session should access a different tuning session.

6.2.2 Two Oracle Expert users should not run the same tuning session (from the same repository) at the same time.

6.2.3 Do not attempt to use Oracle Expert to tune the SYS or System schema.

7. Oracle Trace

7.1 Caveats

7.1.1 In order to use Oracle Trace to collect data for an Oracle8 database, you must set the value of the ORACLE_TRACE_ENABLE parameter in your init<sid>.ora to TRUE.

7.1.2 In non-multi-threaded-server collections, when a collection is stopped all data is not flushed to the .dat file until some action (for example, an SQL command) is performed against the database by each process that is part of the collection.

7.1.3 In order to use the Oracle Trace Manager application to collect data for an Oracle 7.3.3 server, the Oracle Trace Tcl job scripts located in the 7.3.3 Oracle home must be replaced. If you want to use Oracle Trace Manager for this configuration, please contact Oracle support to receive an updated set of Oracle Trace Tcl job scripts to replace those located in oracle_home/network/agent/jobs/oracle/otrace/general.

7.1.4 When a collection is started for an Oracle 7.3.3 server, data is collected only for those users who are logged in at the time the collection is started. Users who log in after the collection has started are not included as part of the collection. This restriction does not apply to Oracle8.

7.1.5 If while using the format operation in Oracle Trace Manager, the format status remains 'running', then the format may have completed and the format job completion message may have been lost. If you suspect this, you can check by resubmitting the format for the collection as a "partial" format. A partial format operation only formats that portion of the collection that was not previously formatted. A successfully completed partial format therefore verifies that the collection is completly formatted.

7.1.6 If using Oracle Trace Manager to discover products in an Oracle8 oracle_home, note that the SQL*Net product definition file has been removed for the Oracle 8.0.3 server release. Therefore, the Oracle Trace Manager does not discover SQL*Net products for that Oracle8 release.

7.1.7 Note that the "cross-product" functionality referenced in the Oracle Trace Users Guide that was removed from the Oracle 8.0.3 server release has been re-introduced for the Oracle 8.0.4 release.

7.1.8 On NT, the Oracle Trace reference files are unable to extend beyond the default number of records for each file. These files and their associated default number of records are: process.dat (100 records), regid.dat (200 records) and collect.dat (5 records). The number of records generated for each of these files is based on the following factors: 1 process.dat record is created for each database connection, 1 collect.dat record is created for each collection that is initiated by the Oracle Trace Manager application, and 2 regid.dat records are created for each database session.

This condition is indicated as follows: For Oracle Trace collections on NT in an Oracle 7.3.3 environment, "file full" errors are reported. For Oracle Trace collections on NT in an Oracle 8.0.3 environment, a collection failing to start, with the message "EPC-00020: could not get access to mem" is reported.

You can avoid or correct errors for these files by running otrccref found in oracle_home/bin, with the following arguments:

-p# to set the maximum number of process records

-c# to set the maximum number of collection records

-r# to set the maximum number of registration records

where # = the number of records

example: otrccref -p200 -c10 -r400

7.1.9 The directory, <oracle_home>/otrace/admin/fdf, should only contain files with the .fdf extension.

7.1.10 Oracle Trace for Oracle 8.0.4 adds new data items to Oracle Trace collection formatter event tables for calculated elapsed time per event. Existing formatter tables will be upgraded to this new format automatically. However, if you attempt to format a pre-8.0.4 collection to these upgraded tables, you may receive an error <column does not exist>. To avoid this problem, you may want to create separate sets of formatter tables for pre-8.0.4 collections and for 8.0.4 collections.

8. Tablespace Manager

This section describes new information, known problems, restrictions, and precautions for Tablespace Manager.

8.1 Caveats

8.1.1 Do not move database objects to the TEMPORARY tablespace. Doing so will cause the objects to be lost.

8.1.2 Defragmentation and reorganization jobs can be submitted to execute at any time. However, to minimize inconvenience to other users who need access to the affected tables, it is recommended that the jobs be submitted to run off-hours. These jobs place locks on all affected tables to prevent updates while the defragmentation and reorganization are taking place.

8.1.3 To submit a job against any database, including the local database, use the appropriate service name during logon. The job system requires that all jobs are submitted with a valid destination as the service name. To see a list of all available job destinations, logon to the console and then select 'Create Job'.

8.1.4 When you wish to analyze objects and list chained rows into a table, the CHAINED_ROWS table must exist prior to job execution. Tablespace Manager does not create the chained rows table.

8.1.5 Note that the "Export Direct" option has been removed from the Reorganization Wizard in this release.

8.2 Known Problems

8.2.1 "Filter folder" does not work.

8.2.2 On Win95, when the Segments page becomes active, the controls are sometimes drawn in their original position, regardless of the current size of the application window. If this happens, by resizing the window all the controls are redrawn at the proper size and position.

9. Oracle Advanced Events

9.1 Known Problems

9.1.1 The Lock Limit event does not use the DML_LOCKS setting (bug 598280) a patch for this bug may be available; please contact Oracle Support.

9.1.2 The Probe Event notification may not function properly for monitoring an Oracle 7.2 database (bug 588199). A patch for this bug may be available for your platform; please contact Oracle Support.

9.1.3 The User Blocks event may fail with the following error "inserted value too large for column", (bug 597058). A patch for this bug may be available for your platform; please contact Oracle Support.

10. Other Oracle Performance Pack Caveats

10.1 Known Problems

10.1.1 For the TopSessions application, if the automatic refreshinterval is shorter than the time it takes to do a refresh, TopSessions is in a continuous loop. To break the loop, click on the "Refresh Mode" button on the toolbar to toggle back to the manual refresh mode.

10.1.2 The Apply button in the New/Modify Chart dialog in the Performance Manager is always greyed out.

10.1.3 TopSessions is not certified to run against 7.0.x and 7.1.x versions of the Oracle database. Do not run the TopSessions SMPTSI70 and SMPTSI71 SQL scripts in the ORACLE_HOME\SYSMAN\ADMIN\RDBMS70 and RDBMS71 directories.

10.1.4 Do not leave TopSessions on auto-refresh with very short refresh intervals (under 20 seconds) for extended periods of time (several hours). Doing so may cause excessive system resource usage.

10.1.4 When using the Oracle Performance Manager 'Record' function, after selecting 'Stop Recording', and entering 'Format/Playback Login' data, the recorded chart data is formatted to tables in the Oracle database service entered by the user. During this formatting process, the user does not see the 'Oracle Trace Formatter Status' window that is described in the Oracle Enterprise Manager Performance Monitoring User's Guide. Instead, a DOS window briefly appears because you do not see the Trace Status window. If the format fails for some reason, you do not get any visual indication of the failure until you attempt to playback the collection and see that your collection is not present in the list. If this happens, you should look at the EPC_ERROR.LOG file on your system to determine why the format failed, fix the problem, and then format the collection using the command line interface. You can format the collection by hand by going out to a DOS window and running the Trace command-line formatter. The command would be:

otrcftm <your_collection_name.cdf> <username> <password> <service>

The username, password, and service are the same as what you supplied in the Performance Manager when you stopped the collection.

10.1.5 The Oracle Performance Manager allows you to create your own charts (refered to as User-Defined charts). If you created User-Defined charts with the Oracle Performance Manager 1.2.2 release and then upgraded to release 1.3.5, the 1.2.2 User-Defined chart definitions stored in your Enterprise Manager Repository were not upgraded properly. To correct this, either before or after you upgrade your Enterprise Manager Repository from 1.3.5 to 1.4, you can convert the User-Defined chart definitions to the correct format by running the following command for your Repository from a DOS window:

vmmupgr username password service

where <username password service> = your Enterprise Manager Repository.

It is strongly advised that you export your Enterprise Manager Repository before running this or any other upgrade script.

11. Oracle Enterprise Manager Documentation

Oracle Enterprise Manager documentation includes:

A57691: Oracle Enterprise Manager Oracle Expert User's Guide

A57690: Oracle Enterprise Manager Oracle Trace User's Guide

A57692: Oracle Enterprise Manager Oracle Trace Developer's Guide

A57689: Oracle Enterprise Manager Performance Monitoring User's Guide

A57696: Oracle Enterprise Manager Configuration Guide

A57695: Oracle Enterprise Manager Application Developer's Guide

A57694: Oracle Enterprise Manager Administrator's Guide

A57693: Oracle Enterprise Manager Messages Manual

A53704: Oracle SNMP Support Reference Guide

A57699: Oracle Enterprise Manager Concepts Guide

A57698: Oracle Enterprise Manager Installation (CD Insert)

The guides listed above are included in the A58162: Oracle Enterprise Manager with Performance Pack Documentation Set. The Oracle Enterprise Manager Documentation Set (A57688) does not contain the Performance Pack guides. The documents are available online in HTML format (.HTM). The HTML guides can be installed as an option with the Oracle Enterprise Manager product. For more information, see 10.1 Online Books.

Hardcopies of the books are orderable as a documentation set or individually. You can also order this readme/release note separately. The part is A57697: Oracle Enterprise Manager Readme. Printed copies of the Oracle Enterprise Manager Configuration Guide, Oracle Enterprise Manager Concepts Guide, and Oracle Enterprise Manager Readme are shipped with the Enterprise Manager distribution kit.

Note: Oracle Parallel Server (OPS) support is described in the Oracle Parallel Server Support for the Oracle Enterprise Manager Console Guide.

11.1. Online Books

Oracle Enterprise Manager documentation is installed as an option of Enterprise Manager. The documentation is in HTML format (file extension .HTM).

You can view the documents with any web browser. Choose the Open File or Open Local option of the browser to locate the OEMDOC.HTM file in the <DRIVE:>\<ORACLE_HOME>\SYSMAN\DOC\ directory. The OEMDOC.HTM file is the master TOC for the Enterprise Manager docs.

Note: If the .HTM file extension has an existing association with a web browser application on your system, then simply double-click on the Oracle Enterprise Manager book icon that has been installed in the Enterprise Manager program group.

You can view any specific guide by loading the TOC.HTM file of the book you want to view in the appropriate book directory in the <DRIVE:>\<ORACLE_HOME>\SYSMAN\DOC\ directory. For example, if the default Windows NT ORACLE_HOME is used during installation, you would load the C:\ORANT\SYSMAN\DOC\ADMNUSER\TOC.HTM file to view the Administrator's Guide.

The document directories under \<ORACLE_HOME>\SYSMAN\DOC\ are:

\ADMNUSER Oracle Enterprise Manager Administrator's Guide

\CONCEPTS Oracle Enterprise Manager Concepts Guide

\PERFUSER Oracle Enterprise Manager Performance Monitoring Guide

\TRCUSER Oracle Trace User's Guide

\TRCDEV Oracle Trace Developer's Guide

\SNMP Oracle SNMP Support Reference Guide

\XPUSER Oracle Expert User's Guide

\APPDEV Oracle Enterprise Manager Application Developer's Guide

\ERRMSGS Oracle Enterprise Manager Error Messages Manual

\INSTALL Oracle Enterprise Manager Installation Insert

\CONFIG Oracle Enterprise Manager Configuration Guide

Note: You can view the documentation on the Enterprise Manager CD if you prefer not to install it. Access the HTML documents as described previously by substituting <CD DRIVE:>\NT_86x\ for \<ORACLE_HOME>\ in the instructions.