Copyright (c) 1998, 2000 Oracle Corporation. All rights reserved.

Oracle Enterprise Manager
Readme
Release 2.2.0.0.0 Production


This Readme identifies differences between the delivered Oracle Enterprise Manager Release 2.2.0.0.0  product and its documented functionality. Additional information may also be included in the Release Notes located in the \relnotes\ directory at the root of the CD-ROM.  Be sure to review those Release Notes - as well as this Readme- before using the product as it may contain late-breaking information concerning Enterprise Manager.  In addition, before using any of the integrated applications (i.e. Oracle Developer Server Forms Manager, etc.), you should review the corresponding applications' Readmes; if installed, they can be found in the $ORACLE_HOME\relnotes\EM\ directory.
 
 

Table of Contents

1.  What's New in Enterprise Manager 2.2

2.  Supported Operating Systems

3.  Compatibility Information

4. Installation

5.  Console

6.  Event and Job Systems

7.  Groups

8.  Paging and Email Blackouts

9.  DBA Management Pack

10.  Oracle Management Server

11.  Enterprise Manager Configuration Assistant

12.  Enterprise Manager Migration Assistant

13.  Browser-based Enterprise Manager

14.  Apache and Oracle HTTP Servers

15.  Others
 
 
 

1.   What's New in Enterprise Manager 2.2

This section describes the new features introduced in Enterprise Manager 2.2:

1.1  Enterprise Manager Console


1.2  Performance Improvements
Significant work has been done to improve the performance of the Release 2.2 Console and DBA Studio.    Such improvements can be seen in the following areas:

For the browser-based Console, when connecting to a webserver for the first time,  a progress dialog will be displayed when downloading the jar files.
 

1.3   Support for Apache Web Servers and Oracle HTTP Server
New features that enable management of generic Apache and Oracle HTTP Server, including discovery, status events, jobs and notification.  Advanced features are incorporated into the Diagnostics Pack and include performance monitoring, advanced events, and reports.

Refer to Chapter 2:Navigator in the Oracle Enterprise Manager Administrator's Guide, Release 2.2 for information about base management and events.

Refer to Chapter 5:e-Business Management Tools and Chapter 6:Oracle Advanced Events Tests in Getting Started with the Oracle Diagnostics Pack for more information about advanced events and performance monitoring.
 

1.4  Jobs and Events System


1.5  Enhanced Notifications

Refer to Chapter 1: Console of the Oracle Enterprise Manager's Administrator's Guide, Release 2.2 for details.

1.6  Reporting


1.7  DBA Studio


1.8  Parameters for OMS Tuning
There may be special circumstances which require specific tuning of the OMS.   Tuning can be done by setting certain OMS configuration parameters in the omsconfig.properties file located in the $ORACLE_HOME\sysman\config\ directory.  Such parameters include:


Note:  Refer to the Enterprise Manager Configuration Guide for further details on the above parameters.  There are two additional parameters not documented in the Configuration Guide:

Every ping interval (determined by the oms.vdp.ping_interval parameter), the Management Server pings all the nodes it knows about.  If it detects that it was able to successfully ping a node in the previous interval and not in this interval, it would mark that node as down.  The ping can be made more tolerant to temporary network outages as follows:

The oms.vdg.conn_retries parameter specifies the number of retries that the Management Server will attempt to ping one node.  The default setting is 1.  That is, by default  the Management Server will not re-attempt to connect; it will simply try once and give up. For networks prone to temporary outages, Oracle recommends setting this parameter to 2 or 3.

The oms.vdg.conn_retries_delay parameter specifies the amount of time in seconds that the Management Server will wait between retries to establish a connection. The default setting is 5.  Oracle recommends setting this parameter based upon the typical duration of network outages.
 

1.9  Intelligent Agent version 8.1.7

Note:  For details on the above features/enhancements, please refer to the Oracle Intelligent Agent User's Guide available as part of the Oracle Enterprise Manager Documentation set, and the Oracle Intelligent Agent 8.1.7 README located in $ORACLE_HOME/network/doc directory.
 
 

2.  Supported Operating Systems

This section shows the operating systems supported by the various installed components of Enterprise Manager 2.2:
 
Enterprise Manager 2.2  Component
Windows NT/2000
Windows 95/98
Sun Solaris 2.6/2.7
HP-UX*
IBM AIX*
Compaq Tru64*
Linux*
EM Console Yes Yes Yes Yes Yes Yes Yes
Oracle Management Server Yes No Yes Yes Yes Yes Yes
DBA Management Pack Yes Yes Yes Yes Yes Yes Yes
Browser-based** EM Client (Console 
& DBA Management Pack)		 Yes, using browsers: 

a) IE 5.0 
    and 
    higher 

b)Netscape 
    4.7 and 
    higher 
(WinNT only) 

 

 Yes, using browsers: 

a) IE 5.0 
    and 
    higher 

b)Netscape 
    4.7 and 
    higher 
 

 No No No No No

* NOTE:  To obtain Enterprise Manager on these operating system platforms,  order the corresponding CD Packs for these operating systems.

**NOTE:  Release 2.2 has been certified on the following webservers; however, any webserver using standard CGI should support this version of browser-based Enterprise Manager:


 

3.  Compatibility Information

3.1  Matrix

The following table identifies which versions of Enterprise Manager are supported against which versions of the Intelligent Agent. In addition, the matrix includes which versions of Enterprise Manager can manage which versions of the Oracle Database.  Special comments are noted.
 
Enterprise Manager Release... is supported by Intelligent Agent Releases... and manages Database Releases...
2.2 8.1.7 
8.1.6.x 
8.1.5.x 
8.0.6.x 
7.3.4.x		 8.1.7 
8.1.6.x 
8.1.5.x 
8.0.6.x 
7.3.4.x
2.1.x 8.1.6.x 
8.1.5.x 
8.0.6.x 
7.3.4.x		 8.1.6.x 
8.1.5.x 
8.0.x
7.3.4.x
2.0.x 8.1.5.x 
8.0.6.x 
7.3.4.x		 8.1.5.x 
8.0.x 
7.3.x

Notes:

- An Intelligent Agent release will monitor/manage database/s of the same release or earlier.  For example, Intelligent Agent Release 8.1.7 will monitor/manage database/s release 8.1.7 and earlier.  For circumstances where a newer release of the Intelligent Agent is used to manage an older release of the database, the Intelligent Agent must be installed in its own Oracle Home, or an Oracle Home whose version is consistent with the Intelligent Agent's version.

- Intelligent Agent Releases 8.0.5 and above include Data Collection Services (Data Gatherer).

- Creation of the Enterprise Manager Repository has been certified in the following Database Releases: 8.1.7, 8.1.6.x,  8.0.6.x, and 7.3.4.x.

- Backup Management Wizards Release 2.2  support database releases 8.0.6 and above.

- Support for JServer management is only available when connected to an 8.1.7 database
 

3.2 Enterprise Manager Products and Management Servers/Repositories

The Enterprise Manager Console, DBA Management Pack, separately licensable Packs, Management Server and repository must all be of the same release.  For example, you cannot use a release 2.1 Management Server and repository with a release 2.2 Console.  Nor can you use a release 2.2 Management Server and repository with a release 2.1 Pack.   Any Enterprise Manager Release 2.2 product must use a release 2.2 Management Server and repository - where product refers to any of the following:

 Oracle Enterprise Manager Console
 Oracle DBA Management Pack
 Oracle Tuning Pack
 Oracle Diagnostics Pack
 Oracle Change Management Pack
 Oracle Management Pack for Oracle Applications
 Oracle Management Pack for SAP R/3
 Oracle Standard Management Pack
If the existing Management Server and repository are of a previous version, then you can migrate or upgrade them to the most recent version.  In the case of migrating or upgrading a Management Server and repository to Release 2.2 be sure all Enterprise Manager products you intend to use with the repository are of Release 2.2.  For instance, do not upgrade the Management Server and repository to release 2.2 if you are still using Diagnostics Pack Release 2.1 or Change Management Pack Release 2.1.  If you upgrade your Management Server and repository to Release 2.2 before obtaining the Release 2.2 Pack software you intend to use, you will not be able to use the older Pack product(s).

Refer to the Oracle Enterprise Manager Configuration Guide for further details regarding migration and upgrading.
 
 

4. Installation

4.1.  Co-Existence of Enterprise Manager 2.1 and 2.2
Enterprise Manager releases 2.1 and 2.2 can be installed in different oracle-homes on the same machine.  However, the de-install of one release will remove common registry keys and hence cause problems with the functioning of the other release.    For example, you have a machine that has EM 2.1 and EM 2.2.   Later, you decide to de-install EM 2.1.   The de-installation of EM 2.1 will cause problems with EM 2.2 applications.
To avoid this problem,  if both releases have already been installed, do not de-install any of them.    If you need to keep only one release, de-install both releases, and re-install the one you'd like to keep.

4.2  If you install the Enterprise Manager Web Site,  make sure that, besides the space requirements listed in the Summary page,  you have around 150-200 MB of  free space in your temp directory.   This space will be used by the installer for intermediate processing of files during installation.   On Windows NT platforms the temp directory is indicated by the TEMP system environment variable.   On Solaris, it is in /tmp.     (Bug 1357839)

4.3 On Windows 95/98,  if the Oracle Home directory contains more than 20 characters, then will you will not be able to launch any of the Enterprise Manager applications from the Start Menu.   To avoid this problem, make sure the Oracle Home directory does not have more than 20 characters.   (Bug 1370534)
In cases where the Oracle Home directory needs to be more than 15 characters, work around the problem as follows:

a) Use "subst" command to substitute $ORACLE_HOME with some drive letter:
     Example:  subst  t:  c:\the-long-oracle-home-name

b)  Edit the oemapp.bat  (located in $ORACLE_HOME\bin directory) and replace all occurrences of the oracle-home directory with the substituted drive letter.
     For example, if one of the lines in oemapp.bat is:
          SET CLASSROOT=d:\the-long-oracle-home-name\classes
     The line should be modified as:
            SET CLASSROOT=t:\classes

You should now be able to launch the Enterprise Manager applications from the Start Menu.
Note that the drive letter substitution will be lost when the machine is rebooted.   Make sure the substitution is made when the machine is restarted, or add it as part of a startup batch file.

4.4  To allow EM to discover Apache and Oracle HTTP Servers, add an entry into the nmxw.ora file (located in the $ORACLE_HOME/network/agent/config directory) following the format of the example below:

<webServer>
   ServerRoot /private/iAS/1.0/Apache/Apache
   ConfigFile /private/iAS/1.0/Apache/Apache/conf/httpds.conf
   ApacheVersion Apache/1.3.9
</webServer>

Where ServerRoot is the directory path of the Apache server, ConfigFile is the directory path of the httpds.conf file, and ApacheVersion is the version number of the Apache server being used.  User can have multiple entries of the above type in this file, resulting in individually discoverable entities.

4.5  The nmxw.ora file does not get populated with the correct HTTP Server configuration data unless the server is 1) already installed, or 2) if HTTP Server is installing in the current session.  Check that the the public variable, 'b_apacheInstalling', located in ows_agentext, is set to 'TRUE'.  If it is, then nmxw.ora was populated correctly, if not, the work around for this problem is to manually set the HTTP Server information in the nmxw.ora file.  (Bug 1644803 and 1643105)

4.6  If in the \etc\hosts entry, the 'nickname' is put before the full host name (i.e. @ as dlsun1816,dlsun1816.us.oracle.com), the getFullHostName call will fail, causing dependent calls like getDomainName or mod status to fail.  To work around, set the domain name in \etc.\hosts with the nickname following the full host name (i.e. dlsun1816.us.oracle.com dlsun181).  (Bug 1587928)

4.7  Running Oracle Enterprise Manager Configuration Assistant in a silent installation session is not supported.  That is, if you edit a parent response file (i.e. SVRTYPICAL.RSP, SVRCUSTOM.RSP, OMIOMS.RSP, or OMICUSTOM.RSP) to specify that EMCA.RSP should be run after silent installation is complete and you run the parent response file, Enterprise Manager Configuration Assistant will not run.  To workaround this problem, you can either
    (1)  Launch Enterprise Manager Configuration Assistant interactively after silent installation
    (2)  Silently run Enterprise Manager Configuration Assistant as a standalone component after silent installation
(Bugs 1379570 and 1491817)

4.8  Installing Oracle Enterprise Manager Release 2.2 (and any of its components) in an existing Oracle Enterprise Manager Release 2.1.x Oracle Home is not supported.  You must install Enterprise Manager Release 2.2 in a new Oracle Home.  (Bug 1484791)

5. Console

5.1  If you select a different window after launching the Console, the login dialog will not display in the foreground.  You may need to minimize any active windows or use  ALT -> tab and select the Console application to bring the login dialog to the foreground.  (Bug 806713)

5.2  It is recommended that you use a fully qualified node name (eg. foo.us.oracle.com) when setting up the name of the Management Server for connecting from the Console.  Failing to do so may prevent launching of some of the Management Pack tools from within the Console, when the Console is running on a machine that is not in the same DNS Domain as the Management Server.  If you continue to have difficulty launching some tools from the Console you should add an entry to the local 'hosts' file for the IP Address of the host where the Management Server is running.

5.3 You may find that when items are selected in one window, previously selected items are not cleared, resulting in the appearance of two items being selected at one time.  The last item selected is the actively selected item.  Users can usually correct this problem by selecting another item in the new window.  (Bug 618771)

5.4   Syntax change in Console Tracing parameters
The OEM.  prefix has been removed from all client tracing parameters.  Hence, the tracing parameters are now:

TRACING.ENABLED
TRACING.LEVEL

In order to enable Console tracing, these parameters should be added to the clientconfig.properties file, located in the $ORACLE_HOME\sysman\config directory.   Refer to the Oracle Enterprise Manager Configuration Guide for more details.

5.5   When running the console on AIX,  there is a JRE bug that prevents you from populating groups and doing other drag-and-drop operations in the console.   (Oracle Bug 1341098).  To populate groups,  launch the console on any other supported operating system, and populate groups from that other console.

5.6  In the Enterprise Manager console, Net8 Assistant can only be launched from the Tools menu.  It cannot be launched from the Service Management drawer on the left side of the console.   (Bug 1367384)

5.7  Before scheduling an Enterprise Report or DBA Studio Configuration Report, you must first apply certain patches to all three tiers of the Enterprise Manager framework:

- Apply patch IA_<version of Intelligent Agent>_001110_BUG1486038.TAR (for example, if your Intelligent Agent is version 7.3.4, then apply patch IA_73400_001110_BUG1486038.TAR,  if the Intelligent Agent is version 8.0.6 then apply patch IA_80600_001110_BUG1486038.TAR, etc.) on the node to which the report generation job has been submitted.  If you do not apply this patch, links to specific service reports will be broken and/or the report job will fail - regardless of the version of the Intelligent Agent that is used.  Obtain the appropriate Agent version of the patch and instructions for applying the patch from http://metalink.oracle.com or contact Oracle Support.

- Apply patch OMS_22000_001110_BUG1493517.TAR to all the Management Server Release 2.2 machines; all the Enterprise Manager Console Release 2.2 machines, and all the DBA Studio Release 2.2 machines.  If you do not apply this patch, links to specific service reports will be broken and/or the report job will fail.  Obtain the patch OMS_22000_001110_BUG1493517.TAR and instructions for applying the patch from http://metalink.oracle.com or contact Oracle Support.

6. Event and Job Systems

6.1   Manually Clearing Events
There are 5 advanced events that do not automatically clear:

 Database Alert
 Data Block Corruption
 Session Terminated
 Archiver Hung
 Data Gatherer Alert

This means if any of these events trigger, and these conditions are manually resolved, the event does not automatically clear because there is no way to automatically detect the condition has been resolved.

Hence, after resolving the problem for which the event fired, you need to manually clear the event as follows:
 a) In the Events Alerts tab in the EM console, move the triggered event to the History tab.
 b) In the History tab, delete this particular event occurrence.

These steps should clear the event, and also reset (i.e. change to green) any red flags in the group pane that may have been set in alarm due to the event.

6.2  Duplicate Events
In Enterprise Manager 2.2, if your events are registered against an 8.1.7 Agent,  then you can submit duplicate events.   Duplicate events are those which have the same event tests using the same parameters registered against the same target.  This means, for example,  the Tablespace Full test with alert threshold of 80% and warning threshold of 60% can be registered more than once against the same USERS tablespace.    You CANNOT, however, have this same event test within the same Event.     So for this example, the duplicate Tablespace full tests need to belong to different Events.

Duplicate events are NOT allowed with pre-8.1.7 Agents.    To determine the version of the agent running on a particular node,  right-click on the node in the Navigator tree in the EM Console, and select "Properties".

In Enterprise Manager 2.1 running with 8.1.6 and earlier Agents,  duplicate events are NOT allowed.

In Enterprise Manager 2.0.4 running with 8.1.5 and earlier Agents, duplicate events are also NOT allowed.

6.3 Synonymous Event Tests
Synonymous events tests are tests that monitor the same metric within the same Event but with different parameters.    An example is two Tablespace Full event tests registered against different tablespaces but are part of the same Event.

Synonymous event tests are supported with Enterprise Manager 2.2 and all its supported agents.

6.4  Migrating synonymous events from EM 2.0.4 repository
If you are upgrading from an EM 2.0.4 to EM 2.2 repository, and you have synonymous events in EM 2.0.4  (where synonymous events are those that have multiple of the same event test but with different parameters), then after the repository upgrade,  you need to de-register and re-register these synonymous events after bringing up the 2.2 Console.

6.5 When you select to refresh job or event history and there is a large amount of history to refresh, the pane may initially appear blank.  To fix adjust the location of the scroll bar.  (Bug 819774)

6.6  Running jobs on Windows 2000 nodes
When running jobs on Windows 2000 nodes, jobs may fail with this error:  "Could not find c:\winnt\temp\21041345280.99".   Windows 2000 allows different operating system level security settings, and this error could be caused by insufficient privileges for the TEMP directory.  If this problem occurs, make sure the TEMP directory allows any user to create, update, and delete files in it.  The TEMP directory is the directory  which is referred to by the TEMP environment variable.  Verify also that the directory pointed to by the TMP environment variable also has create, update and delete privileges.     Finally, you will need to re-submit the job.

6.7 User-Defined SQL Test
If a query used for a User-Defined SQL Test returns a string that contains spaces or other special characters (e.g. $, {, }, [, ]), then the event test will not work properly (Bug 1368019).   As a workaround, use the TRANSLATE function to replace the space or special character with a regular character, such as "_" (underbar).

For example, if your query is:
select name from v$sysstat where name='user calls';

Use this instead:
select translate(name, ' ', '_') from v$sysstat where name='user calls';

Remember to set the threshold values according to how you used the translate function.    In this example, you would set the Alert threshold to be user_calls.

6.8  System Class events on Windows 2000
Due to differences in the performance registry metrics between Windows NT and Windows 2000, the following o/s node events (under the System folder)  do not work on Windows 2000 (bug 1380614):

% Total Processor Time
 % Total User Time
% Total Priviledged Time
Total Interrupts/sec
% Total DPC Time
% Total Interrupt Time
Total DPCs Queued/sec
Total DPC Rate
Total DPC Bypasses/sec
Total APC Bypasses/sec

If you register any of these events against a Windows 2000 node,  other Windows-specific node events will not work properly.    To fix this problem, you need to de-register all events that contain any of the above event tests,  and stop and re-start the Agent on the Windows 2000 node.
There is a patch for the 8.1.7 Agent on Windows 2000 that will prevent the latter problem from occurring (patch for bug 1380614).    After the patch is applied, any attempt to register the events listed above will result in an error:  "This event is not available on this target. Please deregister."   Other Windows-specific node events, however, will not be affected, and you will not need to stop/restart the Agent.

6.9  Network Interface and Physical Disk events on Windows 2000
On Windows 2000, the Network Interface Class and Physical Disk Class node events do not work properly without an Agent patch.   (Bug 1379645)   Contact Oracle Worldwide Support for the patch to this bug.    Also, when setting up parameters for these events, you cannot specify individual network interface names or physical disk names that contain spaces in them, e.g.  "3Com Etherlink PCI".    You need to specify "*" (which means all) for network interface names and physical disk names.
 
 

7. Groups

7.1  If you select the Group folder or a specific Group in the Navigator tree, and then select the Create Group menu item under the Navigator main menu nothing occurs. As a workaround, select the Create Group menu item under the Group main menu or do a right mouse click and select Create.  (Bug 1283307)

7.2   When running the console on AIX,  there is a JRE bug that prevents you from populating groups and doing other drag-and-drop operations in the console.   (Oracle Bug 1341098).  To populate groups,  launch the console on any other supported operating system, and populate groups from that other console.
 
 

8. Paging and Email Blackouts

8.1 You can not set a Paging and Email Blackout for a particular day of the week and have the blackout extend past midnight on the day specified.  For example, you can not create a two hour Blackout which starts at 11:30 PM on Wednesday and lasts until 1:30 AM on Thursday.  To do this, you must create two separate Blackouts:  one for Wednesday from 11:30 PM until 12:00 PM and another for Thursday from 12:01 AM until 1:30 AM. (Bug 1036820)

8.2 When defining a Blackout that will be run "On Interval",   the Effective Period for the blackout should NOT have an End date.   (For example, the effective period should be something like this:    From:  07/30/00    To: <don't specify>)    If an End date is provided, there will be problems running the blackout on the last cycle of that period.    Avoid this problem by keeping the End date unspecified.  (Bug 1367312)

8.3 After defining a blackout on a target for 1)a particular day of the week or 2)a particular time interval every day, you may intermittently receive emails/pages for jobs and events on the target, despite the blackout. This is a known issue in Enterprise Manager 2.2 and we are working to provide a patch fix(bug 1490954).  Please contact Oracle Support to receive an update on this issue.
 

9.  DBA Management Pack

9.1 If a schema name contains a "." delimiter, when viewing objects under this schema, their details will appear to be empty.  (Bug 1055740)

9.2 To use the Summary Advisor wizard, you need to have an external procedure agent setup in the listener.ora and tnsnames.ora files. Refer to the Net8 Administrator's Guide for more information.

9.3  OS Authentication will work only when connecting directly to a database (client/server mode). OS Authentication is not supported when connecting through the Management Server.

9.4  "SP2-0738 Restricted command" error while running SQL*Plus Worksheet:   no server side file system access is allowed when SQL*Plus connects to OMS.  In this case, a script is attempted to be executed on the OMS machine, where SQL*Plus process is run in restricted mode. For security reasons only client side scripts are allowed through the "Run Local Script..." menu.   Se the  SQL*Plus Worksheet Help for additional information.

9.5 Replication (server side) must be installed before using DBA Studio Replication management option to define a replication environment.  If Replication is not installed all Wizard driven tasks will fail.

9.6 An Index Organized Table (IOT) containing columns with LONG/LONG RAW data type cannot be partitioned,  when the column with LONG/LONG RAW datatype is not a primary key column, the error message will not be displayed correctly and partitions are allowed to be entered.   If an IOT contains a column with LONG/LONG RAW data type and it is a primary key,  an error message "Table with LONG/LONG RAW datatype columns cannot be partitioned" is correctly displayed.

9.7  Scheduling of Database Reports will fail if the user is logged on as SYSDBA  and the password for the user is different for connecting as Normal and SYSDBA.  The workaround is to connect as Normal for scheduling reports.  Note that connect as SYSDBA will be ignored for Scheduling of Reports. (bug 1360896)

9.8 Replication wizards can only be launched from DBA Studio:  if using an Enterprise Manager console, first launch DBA Studio then launch the Replication Wizards. (bug 1365244)

9.9  In order to use SQL*Plus Worksheet in a language other than English, you must first modify the dbappscfg.properties file located in the DRIVE_LETTER:\ORACLE_HOME\sysman\config\ directory.  Modify this file by setting SQLPLUS_SYSTEMROOT to be the value of the location where the Windows NT operating system is installed.  (Bug 1389242)

9.10 You can view existing functional indexes and "Create like" functional indexes on a table but you cannot create new functional indexes on a  table. (bug 1373747)

9.11  In DBA Studio, when editing the stored configuration, if you select  "Edit" from the right-mouse context menu and then click "OK" on the Edit Stored Configuration dialog that appears, there is an exception seen on the standard error from where dbastudio was launched.  However, the changes made will still be saved.  To exit out of the dialog box, click "Cancel".   Alternatively, you can edit the stored configuration by selecting and editing the parameters directly in the Init Parameters property page.  (bug 1377721)
 

10.  Oracle Management Server (OMS)

10.1  Creation of the OMS Service on Windows
On Windows NT and Windows 2000,  the creation of the OMS as a service is now performed by the Enterprise Manager Configuration Assistant (EMCA).  This means the OMS service will only be created if,  during the install,  you used EMCA to create a new repository or to use an existing repository.

The OMS service is created with a "Manual" startup type.  This was designed to prevent attempts to automatically start up an improperly or insufficiently configured OMS.   Once the OMS has been properly configured and tested,  you can change the OMS service type to "Automatic", if desired.   You can do this in the following way:

  - Invoke the Control Panel's Services option
  - Select the OMS Service (named "Oracle<oracle-home-name>ManagementServer")
  - Click on the "Startup" button, and select the appropriate Startup type radio button.

10.2  Enhanced OMS Startup
When starting the OMS via the oemctrl utility,  a progress indicator will be displayed as the OMS is attempting to start up.   Only when the OMS is fully started will a message be displayed indicating the OMS is started.    An appropriate error will occur if the OMS encounters problems during the startup.    If you use oemctrl  to start the OMS on Windows NT/2000, then after it has started, the "Started" status will also be reflected in its corresponding service in the Control Panel.

When starting the OMS as a service on Windows NT/2000,  the status will show "Started" only after the OMS has been fully started.

If any problems are encountered during startup, refer to the oms.nohup file located in the $ORACLE_HOME/sysman/log directory.

10.3  OMS Shutdown
On Windows NT and 2000,  when shutting down the OMS as a service from the Control Panel, a dialog will appear asking for credentials to perform the shutdown.   The credentials supplied should be a valid Enterprise Manager superuser account.

10.4  OMS Status
A new oemctrl option is available to find out the OMS status:   oemctrl ping oms
This option is a good way to find out if the OMS is available.    It does not require credentials.

10.5  Connections from Solaris to HP or Siemens SNI
If your OMS is running on a Solaris node and the EM repository database is running on either an HP 10.20 node or a Siemens SNI node,  then you need to set the following SQLNET.ORA parameter on the OMS node:

DISABLE_OOB=ON

The SQLNET.ORA file is located in the $ORACLE_HOME/network/admin directory, where $ORACLE_HOME is the directory where the OMS is installed.
This parameter will prevent sqlnet connection hangs that are caused by differences in the way Sun's and HP's/Siemen's TCP layers handle simultaneous urgent messages on the same socket.

After you set this parameter, you need to stop and re-start the OMS.

10.6  Do not set sqlnet.authentication_services=(NTS) in the sqlnet.ora file that resides in the Oracle Home where Oracle Enterprise Manager Release 2.2 has been installed.
 
 

11.    Enterprise Manager Configuration Assistant

11.1  Pre-2.2 repositories
Existing pre-2.2 repositories are NOT upgraded automatically during installation.   An upgrade to the repository will impact existing users that use it via the various Enterprise Manager products.     Do not upgrade a repository until all the users of that repository have upgraded their software to 2.2:  Console, DBA Studio, Management Packs.     Once you've scheduled the appropriate time for the repository upgrade, use EMCA to perform the upgrade.

11.2  Upgrading repositories via EMCA
To perform an upgrade of a repository, you must explicitly run EMCA and select the Upgrade option.  Once you have selected the Upgrade option and logged-in using a DBA-privileged account,  EMCA will present existing repositories that are upgradable.   If a repository is not in the list, it means it is not upgradable by EMCA.    Select the repository you wish you upgrade, then continue.

If you're running EMCA on Windows NT or 2000, the EMCA upgrade will also create the OMS service if it has not yet been created.
 
 

12.  Enterprise Manager Migration Assistant

12.1    Preferred credentials for some services may not be migrated correctly from a release 1.x repository to a release 2.2 repository if that node was discovered with one of the 4 NT agents; 8.0.6, 8.1.5, 8.1.6 and 8.1.7.  If you have discovered services with one of these agents,  then prior to starting the migration process,  set the preferred credentials that were discovered through these agents manually within the version 2.2 console that is using a newly created 2.2 repository.  (Bug 751627)
 
 

13.  Browser-based Enterprise Manager

13.1  If after logging into browser-based Enterprise Manager, you find the Console has hung, verify (1) that no proxies have been set in your web browser and (2) that the version of MSVCRT.DLL that is being used is later than version 5.00.7303.  You can check the version of MSVCRT.DLL by searching for this dll in the system path.  At times, the dll found first in the path may not be the one being used (this dll may be loaded from c:\winnt40\system32\).  To verify which dll is being used try to rename the dll while the console is hung (Windows NT explorer will not allow you to rename a dll in use).  The version of a dll can be determined by viewing its properties.  To replace the dll, do the following:
From a dos shell:
cd to the directory where the dll exists.
rename msvcrt.dll _msvcrt.dll
copy the correct version of msvcrt.dll into the original directory
reboot your machine

13.2  When connecting to the webserver for the first time, jar files will get downloaded.  The browser process may seem to consume a lot of memory during the download.   When the download is complete, exit out of the browser and re-start it before launching the EM Console.

13.3  When launching the EM Console, DBA Studio, or SQL Worksheet from the Enterprise Manager index page (i.e. EMWebSite.html),  a separate browser window will be created to run the selected applet.  This will allow you to use the original browser window for other purposes.
Do not close this separate browser window;   closing it will also cause the applet to stop.

13.4  If you try to access 'Take a Quick Tour' from the Help main menu in the web-enabled Console, you may receive the following exception:

java.lang.NullPointerException
    at java.net.URLConnection.guessContentTypeFromStream(Compiled Code)
    at sun.net.www.URLConnection.getContentType(Compiled Code)
    at sun.awt.image.URLImageSource.getDecoder(Compiled Code)
    at sun.awt.image.InputStreamImageSource.doFetch(Compiled Code)
    at sun.awt.image.ImageFetcher.fetchloop(Compiled Code)
    at sun.awt.image.ImageFetcher.run(Compiled Code)
To workaround this problem, launch the Quick Tours from the EMWebSite.html index page.  (Bugs 1346011, 1342541, 1357093)

13.5  Running browser-based Enterprise Manager from Netscape Navigator on a Windows 2000 machine is not supported.  There is a problem in that after you  launch one Oracle JInitiator applet (i.e. Console, DBA Studio, etc.) in Netscape and then exit Netscape, the netscape.exe process is not killed and consumes 100% of CPU resources. If you launch a Netscape again and try to launch another JInitiator applet the performance is extremely slow because it doesn't get enough CPU cycles.  (Oracle JInitiator Bug 1192841)

Note:  Running browser-based Enterprise Manager Release 2.2 from Netscape Navigator Release 4.7 and higher, or Internet Explorer Release 5.0 and higher on other Windows-based operating systems (i.e. Windows NT 4.0, Windows 98, Windows 95) is supported.  In addition, running the product from Internet Explorer on Windows 2000 is also supported.

13.6  If you log on to a machine as one operating system user to install Oracle JInitiator 1.1.7.30; log off of the machine, and then log back on as a different operating system user to launch browser-based Enterprise Manager Release 2.2, Netscape will throw an exception. To workaround this problem, log on as the operating system user who installed JInitiator to launch browser-based Enterprise Manager. (Bug 1385928)

13.7  If the website is installed in multiple languages, and is intended to be used for multiple languages, then the URL to be used is:  http://<machine>:3339/EMWebSite_xx.html   where xx is the language abbreviation (e.g  fr means French).  If the intent is to use the website for a single language other than English, then you may copy EMWebSite_xx.html to EMWebSite.html and retain the URL http://<machine>:3339.   If the intent is to use the website for English, use the URL http://<machine>:3339   (Bug 1403799)
 
 

14. Apache and iAS Web Servers

14.1  UNIX Issues

14.1.1  If Apache or iAS is configured to listen at a port number below 1024, the user must have root privileges  in order to start the Oracle HTTP Listener.  In order for administrators to start and shut down the web server using the EM Console, they need to set the Preferred Credentials for the web server node for "root" privilege if the server is listening at a  port number below 1024.  Otherwise, configure the standalone server to listen at a port number higher than 1024.

14.1.2  EM parses the HTTP Listener configuration file, httpd(s).conf, linearly.  Because of this, directives such as 'Listen', 'IfDefine', 'VirtualHost', 'ResourceConfig', and 'Directory' are not supported (any values specified here will either be ignored or read as variables and will cause the discovery script to fail).  To configure Apache and iAS for discovery by the EM Agent, use the following directives:

'Port' -- used to set the port number of the web server target
'Location' -- used to set the server status URL

14.1.3  Include files are ignored by the EM web server discovery script.  The discovery script doesn't interpret any files in the HTTP Listener configuration file, httpd(s).conf, that contain the 'include' verb.
 

14.2  NT Issues

14.2.1  If two or more instances of Apache are started that use the same Apache configuration file, the PID is overwritten by the PID for the most recently started job.  If a user submitts a shutdown job from the EM Console, only the most recently submitted Apache instance will be stopped.  The user should verify that all instances of Apache are stopped when attempting to do a shutdown.

14.2.2  If using generic Apache for NT, when the 'Startup' job is launched from the Console, an error message will be returned stating that there was no output from the job and that the job failed.  This is incorrect.  An Apache instance will be started, but will not be seen from EM or in the NT Services window.  If the user then starts a new instance of Apache from EITHER the NT Services window or from the EM console, they will encounter the problem outlined above in 14.2.1, since the new Apache PID will overwrite the PID of the first instance.  This is not an issue in iAS Apache for NT.
 
 

15. Others

15.1  When Enterprise Manager, or any application integrated with Enterprise Manager, is launched on Windows 95 or Windows 98 there will be a DOS window launched along with that particular application.  Do not close this DOS window.  If you close the DOS window, you will terminate whatever Enterprise Manager application you originally launched. (Bug 1161051)

15.2  The JRE is installed by various Oracle products.   However, there is only one shared JRE per system.  Hence, if after installing Enterprise Manager Release 2.2 you install a previous release of Enterprise Manager (i.e. Release 2.0 or 2.1), the JRE (Java Runtime Environment) installed as part of Release 2.2 will be downgraded automatically; no error messages will appear.  This downgrade from JRE Release 1.1.7.30o to JRE Release 1.1.7.5o or 1.1.7.24o will cause problems for Enterprise Manager Release 2.2.  Consequently, do no install Enterprise Manager Release 2.0 or 2.1 after installing Enterprise Manager Release 2.2.

Installing a pre-8.1.7 Oracle database will also cause the same problem of downgrading the JRE.

If you run into this situation, you can workaround the problem by re-installing JRE Release 1.1.7.30o from the CD-ROM you installed Enterprise Manager Release 2.2 (most likely from a Release 8.1.7 CD-ROM). Re-install the JRE by re-installing Oracle Universal Installer; as the Installer has a dependency on the JRE.

15.3  For non-English versions of Enterprise Manager,  certain inconsistencies may appear in the non-English versions of the online help.  Refer to the documentation for the most up-to-date information.

15.4  On Windows 2000,  numeric paging is not supported.  Instead of using numeric pages, send text messages via alphanumeric pagers.  (Bug 1373113)

15.5  The Enterprise Manager Configuration Guide incorrectly documents how to perform the following tasks on Windows 2000:

Accurate instructions for these actions are described below:

To Manipulate Windows 2000 Services:
1)  Go to Start menu > Settings > Control Panel > Administrative Tools > Services
2)  Select the service that you wish to manipulate.
3)  Right-mouse click and select the action you wish to perform (start, stop, etc.).  To modify the Startup Type, right-mouse click and select Properties and edit the Startup Type as needed.

To Create New Windows 2000 User:
1)  Go to Start menu > Settings > Control Panel > Users and Passwords
2)  From the Users and Passwords screen that appears you can add new users.

To Assign Privileges to Windows 2000 User:
1)  Go to Start menu > Settings > Control Panel > Administrative Tools > Local Security Policy
2)  Select Local Policies in the tree on the left.
3)  Select User Rights Assignment in the tree on the left.
4)  Find and select the appropriate privilege on the right.
5)  Right-mouse click and select Security...  From the Local Security Policy Setting screen that appears you can add which user should have the specified privilege.

For additional information, refer to the Windows 2000 help and documentation. (Bug 1387787)