Copyright (c) Oracle Corporation
1996, 1998. All rights reserved, worldwide.
=========================================
Oracle Enterprise Manager
Production Version 1.6.0
Readme/Release Note A63772-01
=========================================
Table
of Contents
1. Introduction
1.1 Purpose of this Document
1.2 Restricted Rights Legend
1.3 New Features with the Release
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 Command Line Connect String Syntax
2.5 Installing Oracle Enterprise Manager with a local database
2.6 Using Fixit Jobs
3. Compatibility Issues
3.1 Oracle Database Compatibility Matrix
3.2 Console and Repository Compatibility
4. Console-Related Known Problems / Caveats
4.1 Console Problems / Caveats
4.2 Windows 98-related Problems
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 Enterprise Manager Documentation
6.1 Online Books
1. Introduction
1.1 Purpose of this Document
This document notes differences
between the delivered Oracle Enterprise Manager 1.6.0 product
and its documented functionality. It also includes information
on the Enterprise Manager documentation, and late-breaking information
concerning this production release.
For Oracle Tuning Pack issues,
Oracle Change Management Pack issues, and Oracle Diagnostics Pack
issues, please refer to the separate Readmes provided with each
of those product sets.
1.2 Restricted Rights Legend
This software contains proprietary
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.6.0 for
the sole purpose of managing Oracle products free of charge.
ORACLE, ORACLE7, ORACLE8, Oracle
Enterprise Manager, SQL*Plus, 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.
1.3 New Features with this Release
1.3.1 Oracle Enterprise Manager release 1.6.0 now supports console connections over PPP Dial up links. The PPP support only works with Windows Socket version 2.0 and above.
Windows Socket version 2.0 is available from:
//www.microsoft.com/windows95/info/ws2.htm
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 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.5 Installing Oracle Enterprise
Manager with a local database
Do not install Oracle Enterprise
Manager release 1.6.0 into the same <Oracle_Home>
where you have a v8.0.3 or v8.0.4 database installed, or where
any product dependent upon Required Support Files v8.0.3 or v8.0.4
is installed.
2.6 Using Fixit Jobs
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.
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 database
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.4 8.0.5
-----------------------------------------------------------------
EM v1.3.6 yes no no
EM v1.5.0 and v1.5.5 yes yes no
EM v1.6.0 yes yes yes
-----------------------------------------------------------------
The following matrix lists the
components of Oracle Enterprise Manager Release 1.6.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.3.4 8.0.4 8.0.5
------------------------------------------------------------
Repository
Local yes Note 2 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
Data Manager yes
yes yes
Software Manager*
no/Note 1 yes 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: Must reside in a separate
Oracle Home.
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.4 repository with a version
1.6 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.
3.2.1 Although the Oracle Enterprise
Manager Configuration Guide states that the repository user account
requires the DBA role, you should be able to run the Repository
Manager as long as you have EXECUTE privilege on the DBMS_LOCK
package. All other DBA privilege requirements are product- specific.
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 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.3 Partitions, Advanced Queues and Objects are missing in the Navigator Tree. ( Bug 506273 )
4.1.4 Event script fail messages
from agent are shown as event warnings in the console. ( Bug 502620
)
4.1.5 The Event Set description
text is limited to 80 characters. (Bug 499310)
4.1.6 When logging into an OEM
repository that is already used by another Console, select "OK",
not "Cancel", to exit. (bug 600157)
4.1.7 If you are unable to add
or drop repository components or input a file name for your list
of discovered nodes using the Repository Manager wizard on Windows
95, you may have an outdated comctl32.dll file (Microsoft Windows
95 file). The latest file is available for download at: ftp://ftp.microsoft.com/softlib/mslfiles/com32upd.exe.
After downloading this file, double-click on the file to start
it. Reboot your machine before running Repository Manager again.
(Bugs 596961, 596976).
4.1.8 If you have not installed
the Oracle Diagnostics Pack, you will receive a "VOC-10374,
VOC-10551: <EVENT NAME>event is not available" error
when attempting to register the events "Oracle DB Fault"
and "Oracle DB Resource" which are supplied with the
base product. Note: you must have a separate license to use
Oracle Diagnostics Pack and these events. ( Bug 679739 )
4.2 Windows 98-related Problems
4.2.1 On Windows 98 Only: When
loading a saved script into SQL Worksheet the menu bar will gray-out.
You can correct this by clearing or executing the query. (Bug
66924)
4.2.2 On Windows 98 Only: If
you inadvertantly select an invalid drive while performing a
save in SQL Worksheet the error dialog will not allow you to
exit. The workaround is to end the process through the Task Manager
by selecting Ctrl-Alt-Del. (Bug 669877)
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 Export job does not complete
successfully on Solaris when run against a database where ORACLE_HOME
is different from the one where the agent started. (Bugs 644610,
555500)
5.4 Software Manager Problems
5.4.1 Generic Problems/Limitations:
Package and Release 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 Enterprise Manager
Documentation
Oracle Enterprise Manager documentation
includes:
Oracle Enterprise Manager Documentation Set A63774-01
Oracle Enterprise Manager Concepts Guide A63730-01
Oracle Enterprise Manager Administrator's
Guide A63731-01
Oracle Enterprise Manager Configuration Guide A63732-01
Oracle Enterprise Manager Application
Developer's Guide A63733-01
Oracle Enterprise Manager Messages Manual A63734-01
Oracle Enterprise Manager Readme A63772-01
Oracle Enterprise Manager Installation A63773-01
Oracle SNMP Support Reference Guide A64404-01
Oracle Management Pack Documentation:
Oracle Change Management Pack Documentation
Set A63781-01
Oracle Enterprise Manager Getting Started with
Oracle Change Management Pack A63780-01
Oracle Change Management Pack Readme A63777-01
Oracle Change Management Pack Installation A63790-01
Oracle Diagnostics Pack Documentation Set A63782-01
Oracle Enterprise Manager Getting Started
with Oracle Top Sessions and Oracle
Lock Manager A63797-01
Oracle Enterprise Manager Oracle Trace
Developer's Guide A63798-01
Oracle Enterprise Manager Oracle Trace
User's Guide A63799-01
Oracle Enterprise Manager Performance
Monitoring and Planning Guide A63801-01
Oracle Diagnostics Pack Readme A63778-01
Oracle Diagnostics Pack Installation A63791-01
Oracle Tuning Pack Documentation Set A63783-01
Oracle Enterprise Manager Oracle Expert
User's Guide A63796-01
Oracle Enterprise Manager Getting Started
with Oracle Tablespace Manager A63794-01
Oracle Enterprise Manager Getting Started
with Oracle SQL Analyze A63795-01
Oracle Tuning Pack Readme A63779-01
Oracle Tuning Pack Installation
A63792-01
The Oracle Enterprise Manager
Documentation Set (A63774) does not contain the Management 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 6.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 A63772: 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.
6.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.
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.