Skip Headers

Oracle Enterprise Manager Oracle Management Pack for SAP R/3 Readme
Release 9.0.1 for Windows NT

Part Number A88719-01

Oracle® Enterprise Manager

Oracle Management Pack for SAP R/3 Readme

Release 9.0.1 for Windows NT

January, 2002

Part No. A88719-01

This Readme identifies differences between the delivered Oracle Management Pack for SAP R/3 release 9.0.1 for Windows NT and Windows 2000 product and its documented functionality. Additional information may also be included in the Readme available on the Oracle Management Pack for SAP R/3 installation CD-ROM. Be sure to review that Readme as well as this Readme before using the product as they may contain late-breaking information concerning Oracle Enterprise Manager.

This document contains the following topics:

1 Notices and Disclaimers

1.1 License Restrictions and Warranty Disclaimer

The Programs (which include both the software and documentation) contain proprietary information of Oracle Corporation; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained 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. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation.

1.2 Restricted Rights Notice

If the Programs are delivered to the U.S. Government or anyone licensing or using the programs on behalf of the U.S. Government, the following notice is applicable:

Programs delivered subject to the DOD FAR Supplement are "commercial computer software" and use, duplication, and disclosure of the Programs, including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, Programs delivered subject to the Federal Acquisition Regulations are "restricted computer software" and use, duplication, and disclosure of the Programs shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software - Restricted Rights (June, 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.

1.3 Hazardous Applications

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle Corporation disclaims liability for any damages caused by such use of the Programs.

2 Compatibility Issues

2.1 Enterprise Manager Components and Oracle Servers

Table 1 lists the components of the Management Pack for SAP R/3 release 9.0.1 and shows their compatibility with specific releases of the Oracle server. If a component is certified to run with a specific server release, then a "yes" appears for the component for that version of the server. If a component is not certified to run with a specific release, "no" appears for the component for that version of the server.

Some of the components in the table have an asterisk at the end of their names. All or some of the functionality of these components is not available without an Intelligent Agent.

Table 1 Enterprise Manager Components and Oracle Servers  
Components  Oracle Server 7.3.4  Oracle Server 8.0.x  Oracle Server 8.1.x  Oracle Server 9.0.x 

Management Server 

yes 

yes 

yes 

yes 

Repository 

yes 

yes 

yes 

yes 

Target Discovery* 

yes 

yes 

yes 

yes 

Job System* 

yes 

yes 

yes 

yes 

Event Management System* 

yes 

yes 

yes 

yes 

DBA Management Pack 

yes 

yes 

yes 

yes 

DBA Studio 

yes 

yes 

yes 

yes 

Instance Manager 

yes 

yes 

yes 

yes 

Schema Manager 

yes 

yes 

yes 

yes 

Security Manager 

yes 

yes 

yes 

yes 

Storage Manager 

yes 

yes 

yes 

yes 

SQL*Plus Worksheet 

yes 

yes 

yes 

yes 

Backup Management Wizards 

no 

yes 

yes 

yes 

Data Management Wizards 

no 

yes 

yes 

yes 

Management Pack for SAP R/3 

yes 

yes 

yes 

yes 

2.2 Intelligent Agent and Database Compatibility

Version 9.0.1 of the Intelligent Agent is compatible with Oracle server version 7.3.4, 8.0.x, 8.1.5, 8.1.6, 8.1.7, and 9.0.1. Because the Intelligent Agent is continuously being improved from one release to the next, it is strongly recommended that you upgrade to the 9.0.1 Intelligent Agent.

2.3 Oracle Management Pack for SAP R/3 and Intelligent Agent Compatibility

To access SAP R/3 systems for performance monitoring, capacity planning, or event monitoring purposes, release 9.0.1 of the Management Pack for SAP R/3 requires an NT proxy machine that uses version 9.0.1 of the Intelligent Agent on Windows NT. The SAP R/3 Agent Extensions must also be installed into the Oracle Home for the 9.0.1 Intelligent Agent.

See the "Installing Oracle Enterprise Manager and Management Packs" chapter of the Oracle Enterprise Manager Installation Guide for Oracle Enterprise Manager with Management Pack for SAP R/3 for more information on installing the 9.0.1 Intelligent Agent and Agent Extensions on an NT proxy machine.

Also, see the "Post-Installation Configuration" chapter of the Getting Started with Oracle Management Pack for SAP R/3 manual for more information on configuring an NT proxy machine to access SAP R/3 data.

2.4 Oracle Enterprise Manager and Management Pack for SAP R/3 Compatibility

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

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 9.0.1 be sure all Oracle Enterprise Manager products you intend to use with the repository are of release 9.0.1. For instance, do not upgrade the Management Server and repository to release 9.0.1 if you are still using Diagnostics Pack release 2.2 or Change Management Pack release 2.2. If you upgrade your Management Server and repository to release 9.0.1 before obtaining the release 9.0.1 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.

2.5 Management Pack Compatibility with SAP R/3 Releases

The Management Pack for SAP R/3 9.0.1 is compatible with SAP R/3 releases 3.1 through 4.6.

3 General Notices and Issues

3.1 Quick Tour

The Quick Tour for release 2.0.4 of the Management Pack for SAP R/3 is shipped with the release 9.0.1 Management Pack for SAP R/3.

4 General Performance Considerations

As it is packaged, Oracle Enterprise Manager version 9.0.1 is expected to perform best in a three tier deployment when these guidelines are followed:

Define Management Regions for large, global deployments or deployments which span a series of WANs and LANs. Management Regions will ensure that cross regional or cross network communication does not occur. In addition, Management Regions allow for mapping nodes across firewall boundaries.


Note:

For information on defining Management Regions, a feature introduced with Enterprise Manager release 9i, refer to the Oracle Enterprise Manager Administrator's Guide


5 Known Problems/Caveats

Please read the Oracle Enterprise Manager readme file named README_EM.htm, which is located in the $Oracle_Home\relnotes\em directory.

5.1 Oracle Universal Installer

  1. Oracle Universal Installer log files can be found in C:\Program Files\Oracle\Inventory\logs\ on NT, and $Oracle_Home/../../oraInventory/logs/ on Solaris.

  2. If you exit the installation during the middle of an install, or for some reason the installation does not complete, the Universal Installer will not register the installation in its inventory. However, files may have been copied to the Oracle Home you selected, so it is recommended that you remove those files manually and restart the installation.

  3. If you have physically removed an installed product by deleting its directory (without using the Universal Installer), before installing new products, follow the standard removal process using the Universal Installer so that the install and the disk image are synchronized.

  4. If you attempt to install release 9.0.1 of Oracle Enterprise Manager or the Management Packs into an Oracle Home with a space in the name, the product will not function properly. Be sure that there are no spaces in the name of the Oracle Home into which you are installing.

5.2 Oracle Intelligent Agent

  1. Oracle Intelligent Agent log files can be found at $Oracle_Home/network/log/nmi*.log. The list of services discovered by the Intelligent Agent can be found in $Oracle_Home/network/agent/services.ora

  2. The 9.0.1 Agent will not discover SAP systems running on the same node as the Agent automatically. This means that for the Oracle Enterprise Manager Console to discover SAP systems running on Windows NT systems, the name of the SAP system must be included in the sap.conf file for a Windows NT proxy machine. See the "Post-Installation Configuration" chapter of the Getting Started with Oracle Management Pack for SAP R/3 manual for more information on configuring an NT proxy machine and entering SAP service names in the sap.conf file.

  3. See the "Post-Installation Configuration" chapter of the Getting Started with Oracle Management Pack for SAP R/3 manual if the Agent has problems when attempting to access SAP R/3 systems.

5.3 Enterprise Manager Console

  1. It is recommended that you use a fully qualified node name (for example, 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.

  2. A more detailed description of the known problems with the Oracle Enterprise Manager Console can be found in the release 9.0.1 Oracle Enterprise Manager Readme (README_EM.htm). This file is located in the $ORACLE_HOME\relnotes\em\ directory. Please read this document before using Enterprise Manager 9.0.1.

  3. Discovery does not work if the /tmp directory on the Oracle Management Server node is full.

5.4 Job and Event System

  1. When registering SAP R/3 specific events against SAP R/3 services, the name of the service has to be entered in the 'Application Instance Name' or 'Buffer Name' field in the 'Parameters' pane in the format nodename_systemid_systemnumber (example: nodename=sapsmn3, systemid=at8, systemnumber=14, results in sapsmn3_at8_14). Also, valid preferred credentials must be set in the Console for the specific service.

  2. You can only register events against SAP R/3 systems if the central instance is discovered in the Console. The event itself may then also receive a parameter other than the central instance. See Getting Started with Oracle Management Pack for SAP R/3 for more information on discovering SAP R/3 systems in the Console.

  3. (Bug 2172648) If you enter invalid credentials and attempt to register an event, the event registers but the yellow warning icon displays under the Alerts tab. When you click on the event, you receive the "Error message decode - VP_Initialize_Req vppcallbb failed" error message instead of a more accurate error message telling you that you provided invalid credentials.

5.5 Oracle Management Server

  1. You will not be able to run more than one Oracle Management Server on a single machine. This is by design.

  2. If you are running a Management Server and its repository together on the same Windows NT machine, the Management Server may not start after a restart of the machine. After ensuring that the local database for the repository has been restarted, you must manually restart the Management Server.

5.6 Performance Manager

  1. To achieve better performance when drilling down on a chart, you can pause the chart first by clicking the red traffic light icon on the toolbar.

  2. If a chart is unreadable because of an excessive number of entries, it is suggested that you change the display style from graphical to tabular. This can be done by selecting the chart title and selecting the grid button from the toolbar.

  3. Depending on the load on the SAP R/3 instance or network traffic, Performance Manager and Capacity Planner may lose their connection to the Agent if a query takes too long to complete. This problem can be avoided by increasing the connection timeout parameter for Performance Manager and Capacity Planner as follows:

    1. Edit the vtdclient.properties file in the $ORACLE_HOME\sysman\config directory.

    2. Change the number at /options/Timeout to a higher value

  4. (Bug 1003486) Deselecting the 'Application Instance Name' column in the 'Work Process Overview' Chart will have no effect. It will still show up, since it is mandatory for the client.

  5. (Bug 1006522) A drilldown from 'Active Work Processes Overview' into 'Buffer Overview' may result in offering multiple displays of the same data for each instance, depending on how many workprocesses have been found earlier. The same applies to the 'Active Work Processes CPU Usage' Chart.

  6. (Bug 850426) When the central instance of a SAP R/3 system that is being monitored goes down, the client must disconnect and then reconnect to continue monitoring.

  7. (Bug 1192709) The Application Instance Overview & Application Instance Detail charts cannot be saved as custom charts for all SAP R/3 systems.

  8. (Bug 1192653) If there is only one SAP instance, then the hierarchical chart columns cannot be sorted.

  9. (Bug 1072495) You cannot set preferred credentials from the SAP logon window for Performance Manager and Capacity Planner.

  10. (Bug 1196839) Performance Manager charts in HTML reports do not display separate SAP instances for hierarchical charts.

  11. (Bug 2182579) If you select the Application Instance Data container class for SAP R/3 data in the Performance Manager navigator, then select either the Work Process Overview or Work Process CPU Overview chart from the chart properties page and click Show Chart to view the selected chart, you receive the ODG-05560 "error failed calling collection cartridge" and ODG-05138 "error data gathering failed in RT thread" messages. You receive the same errors if you display the System at a Glance chart, then try to drill down from the Buffer Quality Overview chart to the Work Process Overview chart. Also, if you choose an SAP R/3 buffer chart from the chart properties page, it displays without any data. However, if you choose any of these charts in the Performance Manager navigator and then display them, they display properly.

  12. (Bug 2182532) When you view the SAP R/3 Buffer Overview, Buffer Size, or Buffer Quality report when running Performance Manager in your web browser, the HTML report displays without data. Also, when you view the SAP R/3 Work Process Overview or Work Process CPU Overview report when running Performance Manager in your web browser, the HTML report displays only the "Data access in progress" message. To display the correct data for any of these reports, use Performance Manager outside of a web browser, and use the Performance Manager navigator to select the chart that corresponds to the report that you were trying to view.

  13. (Bug 2181843) When you attempt to view the SAP R/3 System at a Glance report when running Performance Manager in a web browser, only a link may appear for the Application Instance Response Time report, if the data values in the Application Instance Response Time are zero. If you view the System at a Glance chart using Performance Manager outside of a web browser, the Application Instance Response Time chart displays the correct data.

  14. (Bug 1850167) When running Performance Manager in a web browser, if you select a container class for a SAP R/3 system on the Performance tab of the reporting framework, then select another container class, then select the original container class again, you will see two copies of each report in the original container class. The number of copies of the reports in the container class increases each time you select the class.

  15. (Bug 2182587) When running the console in a browser (web stage), if you want to launch Performance Manager, it is accessible only from the Diagnostics Pack palette. Therefore, if Diagnostics Pack is not installed, you cannot run Performance Manager from the web stage.

  16. (Bug 1719973) When running Performance Manager in a browser (web stage), if you select a chart and right-click, you are given the option to record a chart. However, if you choose the option to record a chart, you receive an error message because recording a chart is not supported when running Performance Manager in a browser (web stage).

5.7 Capacity Planner

  1. The maximum number of data sets (lines) that can be included in a chart is 50. It is not possible to display more than 50 data sets in a single analysis. This includes selected sources/items and their extrapolation fits.

  2. (Bug 1373218) If you are viewing a subset of the child data sources for a hierarchical chart and change the aggregation level for the chart, the chart will display the data for the newly selected aggregation level for all of the child data sources. For example, suppose that you are viewing the SAP R/3 Buffer Data chart, have selected the CALE buffer as the child data source, and are viewing data at the Hour aggregation level. If you then change the aggregation level from Hour data to Day data, the Buffer Data Chart will show Day data for all of the available SAP R/3 buffers for the selected R/3 instance (instead of showing Day data for only the CALE buffer that you originally selected).

  3. (Bug 1380410) When viewing child data source information for a hierarchical chart (for example, when viewing the CALE buffer for the SAP R/3 Buffer Data chart), you can choose the Select Items button on the chart toolbar to add or delete data sources or data items. However, the button that allows you to select different child data sources (in this example, the Select Buffer button) is not available on the Select Items dialog box. The workaround is to close the chart, and reselect the desired data sources and data items in the Capacity Planner detail view.

  4. (Bug 1216990) Renaming/adding aggregations from the pop up menu does not update the View menu.

  5. (Bug 2200775) The Oracle Capacity Planner copy collection functionality allows you to copy collection class settings from a source SAP R/3 system to a target SAP R/3 system. However, you may experience unpredictable collection behavior if you use the copy collection functionality to copy collection settings from a source SAP R/3 system where a subset of SAP R/3 classes, data sources, or data items is being collected. After the copy collection operation completes, the SAP R/3 classes, data sources, and data items that are selected for collection on the target SAP R/3 system may not be what you expect. It is recommended that you use the copy collection functionality only when all the SAP R/3 classes, data sources, and data items are selected for collection on the source SAP R/3 system. If you want to select a subset of SAP R/3 classes, data sources, and data items for collection on an SAP R/3 system, it is recommended that you manually select the SAP R/3 classes, data sources, and data items to be collected instead of using the copy collection functionality.

5.8 Documentation Errors

  1. (Bug 2183706) When you click Help for the SAP Logon dialog box for either Performance Manager or Capacity Planner, the help topic is not displayed. You can access the help topic by searching for the string "SAP Logon dialog box" on the Search page of the Help system. The Results box on the Search page displays the topics that contain this string. The Source column shows which SAP Logon dialog box topic is for Performance Manager and which is for Capacity Planner. Select the topic in the Results box and click Open to display it.

  2. The SAP Logon dialog box help topics for Performance Manager and Capacity Planner refer to the "Data Gatherer Location (Host)" field. This field does not appear in the SAP Logon dialog box, and that portion of the help text can be ignored.

  3. (Bug 2183566) The SAP Logon dialog box help topic for Performance Manager refers to the Save as Preferred Credential function. This function is not enabled for SAP systems.

6 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/.

Oracle is a registered trademark, and SQL*Plus is a trademark or registered trademark of Oracle Corporation. Other names may be trademarks of their respective owners.

Copyright © 1999, 2002, Oracle Corporation. All rights reserved.


Oracle
Copyright © 1999, 2002, Oracle Corporation.

All Rights Reserved.