Version 12.03 January 2011
This document provides an overview of the changes made to the HP Operations Smart Plug-in for SAP (SPI for SAP) 12.03 for HP Operations Manager for Windows 9.00 version. Release notes contain important information not included in the product manuals or online help.
In This Version
Documentation Updates
Installation Notes
Known Problems, Limitations, and Workarounds
Enhancements and Fixes
Verified Environments
Documentation Errata
Local Language Support
Support
Legal Notices
This version of the SPI for SAP includes new features, feature enhancements, and other changes.
The first page of this release notes document contains the following identifying information:
To check for recent updates or to verify that you are using the most recent edition, visit the following URL:
http://h20230.www2.hp.com/selfsolve/manuals
NOTE: To view files in PDF format (*.pdf), Adobe Acrobat Reader must be
installed on your system. To download Adobe Acrobat Reader, go to the following URL:
http://www.adobe.com
The HP Operations Smart Plug-in for SAP Installation and Configuration Guide lists the hardware and software requirements for the SPI for SAP for HPOM for Windows and provides instructions for installing and configuring the software. The document is available on the HP Operations Smart Plug-in DVD set in the following location:
<DVD_Drive>\Documentation\SPI Guides\SAP_Install_Config.pdf
Before starting the installation of the SPI for SAP, read the installation requirement section from the HP Operations Smart Plug-in for SAP Installation and Configuration Guide. If you are upgrading from a previous version of the SPI for SAP, you will need to look at the "Obsoleted Software Versions " section, too. When performing the installation or upgrade, note the additional information in: SPI for SAP Transport Numbers. For more information about the localized versions of the SPI for SAP, see Local Language Support.
See the Support Matrix (SUMA) link to find the Support Matrix for this product that lists the supported HP Operations Manager, application servers, HP Performance Agent, HP Performance Manager, and HP Reporter version at this location: HP Support matrices.
For information on the archived obsolescence programs, refer to the Obsolescence Archive link Obsolescence Archive link.
For a list of the current SAP R/3 transport numbers provided with the SPI for SAP, see the following file on the HPOM for Windows management server after you have successfully installed the SPI for SAP software:
%OvShareDir%\Packages\SAPTransports\readme
NOTE: The read-me file for the SPI for SAP transports provides information about additional transport files for the CCMS-based trees for the Enterprise Portal monitor.
When you import the SPI for SAP transports into SAP, note the following important points:
This section lists known problems that could not be fixed before the release of the SPI for SAP software. Click the item in the list immediately below to see a more-detailed description of the problem.
| SYMPTOM: | The SAP GUI is needed for many operator-initiated actions defined in the SPI for SAP, but it is not part of the SPI for SAP installation media. | |
|---|---|---|
| SOLUTION: | Install the SAP GUI on the HPOM management server and any remote consoles. The SAP GUI is included on the SAP Presentation CD. For more information, see Installing the SAP GUI section from the HP Operations Smart Plug-in for SAP Installation and Configuration Guide. |
| SYMPTOM: | The number of logged in users reported by the collector is different from the users reported in the SAP transaction SM04. | |
|---|---|---|
| SOLUTION: | The collector counts the `itouser' as a fully logged-in user. Therefore, some differences may occur. . |
| SYMPTOM: | The user can deploy a configuration-file policy of one particular subtype
(same application/subgroup/file combination; for example.
SAP-SPI/global/r3itosap.cfg) that has already been deployed
to that node with a different value/content.
Both policies appear in the node's policy inventory, but at the file-system level, the second deployment overwrites the configuration file. The state of the system is inconsistent and the user cannot tell which policy wrote the current content of the configuration file. On Unix managed nodes the error does not occur, but an error message is issued when the user tries to redeploy a config-file policy of the same subtype as an already existing one. However, a message does appears in the HPOM for Windows console. | |
|---|---|---|
| SOLUTION: | To prevent this problem, deploy only the configuration file policies of unique
subtypes (e.g. SAPSPI/global/r3monsap.cfg) to Windows
managed nodes.
To get your system back to a consistent state if this problem occurred, undeploy all configuration-file policy subtypes (e.g. for example: application/subgroup/filename), and redeploy the correct ones. |
| SYMPTOM: | Monitors of type snapshot send duplicate messages to the message browser and the overall performance of the SPI for SAP is very slow. | |
|---|---|---|
| SOLUTION: | Check to see if you have entered a managed node twice in any
of the configuration files, for example: once using a short host name
(sapsystem) and once using a fully qualified name
(sapsystem.domain.company.com). If there are two entries,
the monitor binaries will open two connections to the SAP system for
each monitor call, thus consuming more resources and sending messages
twice.
Each system must be configured only once in the configuration files, preferably with its fully qualified name. |
| SYMPTOM: | The SPI for SAP monitors take a very long time to obtain information from the SAP system. | |
|---|---|---|
| SOLUTION: | Check how often you use the CP (Contains Pattern) option in your configuration files. The CP option consumes both time and system resources. You should try as much as possible to replace the CP option with an EQ operation. If this is not feasible, try to avoid using a fully unqualified CP, for example; CP*. Instead, try whenever possible to qualify the CP option with a pattern, for example; CP MY_JOB*. |
| SYMPTOM: | If you launch SPI for SAP tools such as Write Statistical Records
on a remote-console system, in some
cases you see popup windows telling you that certain dll's are not located in the specified path, for example:
The dynamic link library opcapi.dll could not be found in the
specified path | |
|---|---|---|
| SOLUTION: | For the Statistical-records tools in the SPI for SAP group to work correctly on a remote console system, you need to deploy an HPOM agent to the remote console. |
| SYMPTOM: | The error 534 appears because the database DLL is corrupt, missing or out of date. The error 534 appears in the HP Reporter status pane. | |
|---|---|---|
| SOLUTION: | Check the systems available in the SAP R/3 group under “Discovered Systems” in Reporter. Since the SPI for SAP reports show the data collected from the systems available in the SAP R/3 group, there should be atleast one system with sufficient data under this group. If systems are available, then check whether required data is available in the reporter database tables, or run gatherCoda command against the systems in the SAP R/3 group to collect the data.
Error 534 may occur when the reporter database or the table structure is missing or outdated. Check whether the reporter DSN is configured to the right reporter database. |
| SYMPTOM: | The HPOM for Windows service tree shows multiple subtrees for a virtual SAP instance inside a cluster, even though the new "Host-Mapping" feature is used to virtualize the cluster instance. A subtree is shown for each physical node of the cluster. | |
|---|---|---|
| SOLUTION: | In the current release, there is no solution to this problem. |
| SYMPTOM: | No statistical records are provided by the SPI for SAP performance monitors. | |
|---|---|---|
| SOLUTION: | You need to ensure that you have written the
r3perfstat.cfg settings into the SAP System after adding
all login information into the r3itosap.cfg file. To write
the new configuration you have saved in the r3itosap.cfg
file to the SAP System, select the appropriate SAP system in the
navigation pane and launch the "Write Statistical Records" tool, which you
can find in the "SAP R/3 Admin" tools group. |
| SYMPTOM: | When r3sd runs on a machine hosting both an SAP central
instance and an SAP application server, both of which belong to the same
SID, the SPI for SAP displays the service-discovery information twice. | |
|---|---|---|
| SOLUTION: | On the managed node where the problem occurs, use the environment variable SAPOPC_SAPPROFILEDIR to define the list of profile directories. Make sure that you include only one instance of the profile directory, for example; either the local path (including the drive letter) or the UNC notation. |
| SYMPTOM: | If the service-discovery tool, r3sd, is running under the system
account and the SAP installation directory is specified in UNC syntax,
for example; "\\server...", SAP instances are not
discovered for managed nodes running Microsoft Windows, and the R3-Info tool
completes its run but does not produce any output. | |
|---|---|---|
| SOLUTION: | Either specify a local path to the SAP installation using the environment variable SAPOPC_SAPPROFILEDIR (only possible on SAP central instances), or configure the HPOM agent to run under a different user account to enable it to access network paths using the UNC notation. |
| SYMPTOM: | The default configuration of the r3montra policy lists the polling interval as 0 hours, 0
minutes, and 0 seconds. When you modify this policy and try to save the changes, the monitored system
complains that the scheduling interval cannot be less than 5 seconds, which can lead to the impression that
the monitor is not scheduled to run.
| |
|---|---|---|
| SOLUTION: | The problem is in the policy editor and does not affect the running of the monitor itself. In fact, the r3montra
policy is scheduled by default to run once a day ("1d"), and both the HPOM for Windows database and the
agents handle the policy schedule correctly. The setting of "0 hours, 0 minutes, 0 seconds" can safely be ignored
and does not affect the r3montra functionality. If you want to modify this policy, a value of "24
hours" should be entered in the scheduling section.
|
| SYMPTOM: | You cannot configure r3monjob to send a WARNING message if the run time for a
batch job exceeds 5 minutes and then a CRITICAL message if the run time for the same batch job
exceeds 10 minutes.
| |
|---|---|---|
| SOLUTION: | With the current version of the SPI for SAP, it is not possible to configure more than one threshold with the same alert type for a given batch job. |
| SYMPTOM: | The SAP process monitor r3monpro cannot determine the status of the SAP
systems it is monitoring. As a result, it assumes that the SAP instance is available and
does not suppress any messages.
| |
|---|---|---|
| SOLUTION: |
r3monpro needs to know where to find both its own history
file r3monpro.his and, in addition, the r3status
history file r3status.his, which it uses to determine
whether a monitored SAP instance is available or not. Both history files
must reside in the location defined by the HistoryPath keyword in
r3monpro's configuration file r3monpro.cfg. If
r3monpro cannot locate the r3status.his
history file, it assumes that the monitored SAP instance is available, and
does not suppress any messages.
Make sure that the history files |
| SYMPTOM: | SPI for SAP policies resides on the management server even after you remove the SPI. These policies can be accessed from the Agent policies grouped by type group. | |
|---|---|---|
| SOLUTION: | After removing the SPI for SAP, remove the policies manually from the Agent policies grouped by type group. |
| SYMPTOM: | Multiple instances are not supported on SAP Netweaver 7.0 . | |
|---|---|---|
| SOLUTION: | The SAP Netweaver 7.0 java instance monitoring is possible through remote monitoring, but not multiple instance support. For more information, see QCCR1A91931.. |
| SYMPTOM: | Failed to create metric definition.xml on Linux DCE node. | |
|---|---|---|
| SOLUTION: | Failed to run the "Create SPI SAP NetWeaver Config" tool from management server with DCE Agent on managed node. The r3mon_ca script prepares the command to execute the java code. The command expects the jar files to be under "/var/opt/OV/bin/OpC/monitor" but the files will be deployed to the instrumentation directory. Apply the workaround mentioned in the QCCR1A100051. |
| SYMPTOM: | Failed to upload service map on DCE node. | |
|---|---|---|
| SOLUTION: | This is an agent issue. For more information, see QCCR1A99300. |
| SYMPTOM: | Few files are missing when you execute the Version Verify tool . | |
|---|---|---|
| SOLUTION: | For more information, see QCCR1A99193. |
| SYMPTOM: | On a clustered Windows node, the SAP ABAP dispatch monitor r3mondisp is unable to locate SAP profile on SAP system SID. The following message appears: Unable to locate SAP profile for ABAP dispatcher monitoring on SAP System SID:nn on host myhost.domain.com |
|
|---|---|---|
| SOLUTION: | Change the user from $AGENT_USER to any other user who has the privilege to access the profile file from shared disk. |
This section provides information about patches and fixes that have been produced to address problems with current or previous versions of the SPI for SAP software.
To display information about a problem that has been fixed for this release, click the appropriate reference-number link in the following list:
QCCR1A25715 : r3monale should filter on message types as well
QCCR1A59157 : Request of integration information and support with OVPA
QCCR1A25850 : r3perfagent stops immediately after starting it
QCCR1A25875 : Can't get SAP SPI to launch SAP GUI
The following fixes are made in the current release of SPI for SAP. You can click the reference number that links to the HP Software Online Support web site.
QCCR1A25624 : Service Discovery for a cluster creates MAP with wrong Host Name
QCCR1A25812 : SAP SPI messages from virtual nodes not shown in service tree
QCCR1A72381 : r3mondisp doesn't find dpmonPath
QCCR1A91886 : Upgrading R3PERF doesn't install new datasources
QCCR1A92879 : File name collision detected upon distribution of instrumentation to HTTPS nodes
QCCR1A98184 - Performance Monitor metrics STATRECS_PERF and WLSUM_PERF DataCollection issue
QCCR1A97931 - r3monusr ignores APSERVER setting
For information about the platforms, operating systems, and product versions which the Smart Plug-in for SAP supports, see the "Installation Requirements" section in the HP Operations Smart Plug-in for SAP Installation and Configuration Guide.
This section lists errors or omissions in the current SPI for SAP product documentation, which could not be corrected before the product release.
The following are the issues related to WLSUM performance monitor which could not be documented in the HP Operations Smart Plug-in for SAP Reference Guide .
| SYMPTOM: | The new SPI for SAP performance monitors, DOCSTAT and WLSUM_PERF, do not collect any data. | |
|---|---|---|
| SOLUTION: | In order to collect useful data from the SAP performance component, you have to schedule the SAP report RSCOLL00 to run once an hour on your SAP R/3 System. For more information about how to schedule standard reports or jobs in a SAP component, see the SAP OSS note 16083. |
Reports do not show data from the hour between 00:00 and 01:00:
| SYMPTOM: | Work-load and user reports using data gathered by the SPI for SAP performance monitor WLSUM_PERF do not show any results for the period between midnight (00:00) and 1 a.m. (01:00). | |
|---|---|---|
| SOLUTION: | This is due to a difference between the way SAP and the SPI for SAP handle time. Try to avoid scheduling reports to start between 00:00 and 01:00: schedule reports to run after 01:30 instead. |
| SYMPTOM: | The SPI for SAP WLSUM reports show irregular values for data that should be continuous. For example, a report for an SAP System normally shows around 1000 dialog steps per hour, but for one hour it shows no steps at all, and for the following hour it shows 2000 steps, which is double the usual amount. | |
|---|---|---|
| SOLUTION: | The data collection for the WLSUM monitor is based on the internal SAP job "COLLECTOR_FOR_PERFORMANCEMONITOR". If this job does not run correctly or at the correct time, the data usually collected by the WLSUM_PERF monitor run will only be picked up by subsequent runs of the SPI for SAP performance monitor and, as a result, displayed in the wrong place. Note that you can use the SPI for SAP job monitor, r3monjob, to monitor the behavior of the internal SAP performance-collector job "COLLECTOR_FOR_PERFORMANCEMONITOR".
|
In addition to the English-language version of the SPI for SAP, version 12.03 of the SPI for SAP will also be available for the following environments:
The Japanese-language version 12.03 of the SPI for SAP provides the following localized elements:
To activate the Japanese environment, follow these steps:
%OvShareDir%\Packages\SAPTransports\readme
r3monal connects to a
Japanese SAP server with Japanese as the connection language, set the environment variable
SAP_CODEPAGE=8000 to ensure that the messages that r3monal sends display
Japanese characters correctly.Please visit the HP Software support web site at:
http://www.hp.com/managementsoftware/support
This web site provides contact information and details about the products, services, and support that HP Software offers.
HP Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valuable support customer, you can benefit by being able to:
NOTE: Most of the support areas require that you register as an HP Passport user and log in. Many also require an active support contract. To find more information about support access levels, go to the following URL:
http://h20230.www2.hp.com/new_access_levels.jsp
To register for an HP Passport ID, go to the following URL:
©Copyright 1998 - 2011 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
For information about third-party license agreements, see the spi-thirdparty-license-agreements directory on the product installation DVD-ROM.
The information contained herein is subject to change without notice.